Public report of jacklandrin/OnlySwitch, published 14 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 14 November 2026, 21:42 UTC · Survey ID cd_419ad9ef663646f7a6afb7c77b57ea8d
jacklandrin/OnlySwitch
Measured 14 November 2026, 21:41 UTC, at code version 2db3c8b
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
Up 2 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 medium codebase: 85,644 lines of product code in 36 projects, tests not counted · Estimated rebuild effort: about 0.9 person-years · Weakest lens: Production Readiness, 34
Findings by how serious they are
45 critical965 serious82 minor
29 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 21:41 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
47of 47 dimensions measured by tools.
1042of 1092 findings point to an exact file and line, so you can open each one in the code. The other 50 concern the repository as a whole, such as missing documentation.
47dimensions across 9 lenses, read from 85,644 lines of product code in 36 projects.
jacklandrin/OnlySwitch falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 54 out of 100 and is rated Adequate, and none of its 45 critical findings concern security.
Production Readiness, at 34, is the weakest lens and counts most in the score. The best first step is making the tests check their results, worth about 9 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 7 points. Raising Production Readiness to 70 would lift the score to about 70.
Giving each kind of identifier a type of its own would take care of the 40 identifiers passed around as plain numbers or text.
The product code is 85,644 lines, about €130,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 34 to 70, the lowest score rated Strong, the score would rise from 54 to about 70.
Code composition: what the lines of code are
Product code 65%Tests 35%
New since the last survey: 897 findings
These 897 critical or serious findings weren't in the previous survey, on 28 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
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: 398 findings
These 398 critical or serious findings were in the previous survey, on 28 October 2026, and are gone from this one. The first 100 are listed here.
God Classes · MethodTooLong: RemoteAppFeature.body OnlySwitchRemote/App/RemoteAppFeature.swift
God Classes · MethodTooLong: PromptDialogueReducer.body Modules/Sources/OnlyAgent/Dialogue/PromptDialogueReducer.swift
God Classes · FileTooLong: Dependencies/RemoteConnectionClient+Live.swift OnlySwitchRemote/Dependencies/RemoteConnectionClient+Live.swift
God Classes · MethodTooLong: SwitchType.barInfo Modules/Sources/Switches/SwitchType.swift
God Classes · MethodTooLong: PairingFeature.body OnlySwitchRemote/Features/Pairing/PairingFeature.swift
God Classes · TooManyMethods: RemoteConnectionRuntime OnlySwitchRemote/Dependencies/RemoteConnectionClient+Live.swift
God Classes · FileTooLong: SystemMonitor/MacSystemMonitorCollector.swift OnlySwitch/Features/SystemMonitor/MacSystemMonitorCollector.swift
God Classes · ClassTooLong: RemoteAppFeature OnlySwitchRemote/App/RemoteAppFeature.swift
God Classes · MethodTooLong: RemoteAccessSettingsFeature.body OnlySwitch/Features/RemoteAccess/Settings/RemoteAccessSettingsFeature.swift
God Classes · FileTooLong: Host/RemotePeerSession.swift OnlySwitch/Features/RemoteAccess/Host/RemotePeerSession.swift
Rebuild cost: about €130,000 · Estimate
Cost to rebuild
€43,000 to €220,000, for 716 to 2,271 hours of work, about 0.9 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.8 at a score of 54. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 85,644 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 Assertions commented out finding(s) in Test Quality — start with OnlySwitchTests.swift.
Raises the score by about 9 points · Low effort · Test Quality
2
Add a CI workflow that builds and runs the test suite on every push/PR.
Raises the score by about 7 points · Medium effort · CI/CD gates
3
Resolve the 224 No assertions finding(s) in Test Quality — start with RemoteScreenshotsFeatureTests.swift (22), EverySwitchTests.swift (17), RemoteAppFeatureTests.swift (17).
Raises the score by about 6 points · High effort · Test Quality
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €130,000 to build again, about 0.9 person-years of work. Its weakest lens is Production Readiness, at 34 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
One cause behind 42 Domain Modelling findings · Common cause
42 findings in the Domain Modelling lens come from the same cause. The code models the business as objects, such as an order or a customer, and each object should guard its own rules: an order, for example, should refuse to be shipped before it has been paid. Here the objects don't do that. Some objects only hold data, while the rules that should keep that data valid sit elsewhere in the code. Identifiers, such as order numbers and customer numbers, are passed around as plain numbers or text, so nothing stops the code from using one kind where another belongs. Because all of these findings have the same cause, fixing it once, in the business objects themselves, deals with them together.
Based on: Rich vs anemic domain model (2 findings) · Strongly-typed ids (40 findings)
What to do: Give each business object the methods that enforce its rules, such as a method for shipping an order that first checks it has been paid, and let only those methods change its data. Give each kind of identifier a type of its own, so an order number can't be used where a customer number belongs.
If you do one thing first · First action
Resolve the 1 Assertions commented out finding(s) in Test Quality. Of all the actions in this report, it raises the score most for the work it takes: about 9 points for low effort, because it clears the 1 Test Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.5 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 4% to 9% on every change. The history of the code shows how much it changes: about 149,339 lines over the last 90 days, which is about 605,653 lines a year. At that pace, the extra work comes to an estimated 57.6 to 345.4 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
39 modules, with 186 dependencies between them. One loop runs through 27 of the modules, marked above the diagonal.
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.
Modules~DesktopPetSkinKit uses Modules~Extensions, so a change to Modules~Extensions can break Modules~DesktopPetSkinKit, while a change to Modules~DesktopPetSkinKit can't break Modules~Extensions.
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.
5→13 Modules~DesktopPetSkinKit uses Modules~Designpart of a loop✕
Connections
7 pairs of types, where a type in Modules~DesktopPetSkinKit uses a type in Modules~Design.
Modules~DesktopPetSkinKit uses Modules~Design, so a change to Modules~Design can break Modules~DesktopPetSkinKit, while a change to Modules~DesktopPetSkinKit can't break Modules~Design.
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.
6→9 Modules~DisplayBrightness uses Modules~OnlyAgentpart of a loop✕
Connections
1 pair of types, where a type in Modules~DisplayBrightness uses a type in Modules~OnlyAgent.
Modules~DisplayBrightness uses Modules~OnlyAgent, so a change to Modules~OnlyAgent can break Modules~DisplayBrightness, while a change to Modules~DisplayBrightness can't break Modules~OnlyAgent.
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.
6→11 Modules~DisplayBrightness uses Modules~DesktopPetpart of a loop✕
Connections
3 pairs of types, where a type in Modules~DisplayBrightness uses a type in Modules~DesktopPet.
Modules~DisplayBrightness uses Modules~DesktopPet, so a change to Modules~DesktopPet can break Modules~DisplayBrightness, while a change to Modules~DisplayBrightness can't break Modules~DesktopPet.
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.
6→12 Modules~DisplayBrightness uses Modules~Extensionspart of a loop✕
Connections
14 pairs of types, where a type in Modules~DisplayBrightness uses a type in Modules~Extensions.
Modules~DisplayBrightness uses Modules~Extensions, so a change to Modules~Extensions can break Modules~DisplayBrightness, while a change to Modules~DisplayBrightness can't break Modules~Extensions.
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.
6→13 Modules~DisplayBrightness uses Modules~Designpart of a loop✕
Connections
5 pairs of types, where a type in Modules~DisplayBrightness uses a type in Modules~Design.
Modules~DisplayBrightness uses Modules~Design, so a change to Modules~Design can break Modules~DisplayBrightness, while a change to Modules~DisplayBrightness can't break Modules~Design.
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.
6→30 Modules~DisplayBrightness uses Modules~AppFeaturepart of a loop✕
Connections
1 pair of types, where a type in Modules~DisplayBrightness uses a type in Modules~AppFeature.
Modules~DisplayBrightness uses Modules~AppFeature, so a change to Modules~AppFeature can break Modules~DisplayBrightness, while a change to Modules~DisplayBrightness can't break Modules~AppFeature.
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.
6→34 Modules~DisplayBrightness uses Modules~Aphroditepart of a loop✕
Connections
4 pairs of types, where a type in Modules~DisplayBrightness uses a type in Modules~Aphrodite.
Modules~DisplayBrightness uses Modules~Aphrodite, so a change to Modules~Aphrodite can break Modules~DisplayBrightness, while a change to Modules~DisplayBrightness can't break Modules~Aphrodite.
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.
Modules~RemoteCore uses Modules~DisplayBrightness, so a change to Modules~DisplayBrightness can break Modules~RemoteCore, while a change to Modules~RemoteCore can't break Modules~DisplayBrightness.
Position
Below the diagonal: Modules~RemoteCore uses a module listed above it, which is the healthy direction.
7→8 Modules~RemoteCore uses Modules~RemoteTransportpart of a loop✕
Connections
14 pairs of types, where a type in Modules~RemoteCore uses a type in Modules~RemoteTransport.
Modules~RemoteCore uses Modules~RemoteTransport, so a change to Modules~RemoteTransport can break Modules~RemoteCore, while a change to Modules~RemoteCore can't break Modules~RemoteTransport.
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.
7→12 Modules~RemoteCore uses Modules~Extensionspart of a loop✕
Connections
54 pairs of types, where a type in Modules~RemoteCore uses a type in Modules~Extensions. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Modules~RemoteCore uses Modules~Extensions, so a change to Modules~Extensions can break Modules~RemoteCore, while a change to Modules~RemoteCore can't break Modules~Extensions.
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.
7→13 Modules~RemoteCore uses Modules~Designpart of a loop✕
Connections
41 pairs of types, where a type in Modules~RemoteCore uses a type in Modules~Design. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Modules~RemoteCore uses Modules~Design, so a change to Modules~Design can break Modules~RemoteCore, while a change to Modules~RemoteCore can't break Modules~Design.
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.
Modules~RemoteTransport uses Modules~RemoteCore, so a change to Modules~RemoteCore can break Modules~RemoteTransport, while a change to Modules~RemoteTransport can't break Modules~RemoteCore.
Position
Below the diagonal: Modules~RemoteTransport uses a module listed above it, which is the healthy direction.
8→12 Modules~RemoteTransport uses Modules~Extensionspart of a loop✕
Connections
11 pairs of types, where a type in Modules~RemoteTransport uses a type in Modules~Extensions.
Modules~RemoteTransport uses Modules~Extensions, so a change to Modules~Extensions can break Modules~RemoteTransport, while a change to Modules~RemoteTransport can't break Modules~Extensions.
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.
8→13 Modules~RemoteTransport uses Modules~Designpart of a loop✕
Connections
3 pairs of types, where a type in Modules~RemoteTransport uses a type in Modules~Design.
Modules~RemoteTransport uses Modules~Design, so a change to Modules~Design can break Modules~RemoteTransport, while a change to Modules~RemoteTransport can't break Modules~Design.
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.
8→27 Modules~RemoteTransport uses Modules~Authenticatorpart of a loop✕
Connections
1 pair of types, where a type in Modules~RemoteTransport uses a type in Modules~Authenticator.
Modules~RemoteTransport uses Modules~Authenticator, so a change to Modules~Authenticator can break Modules~RemoteTransport, while a change to Modules~RemoteTransport can't break Modules~Authenticator.
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.
8→30 Modules~RemoteTransport uses Modules~AppFeaturepart of a loop✕
Connections
1 pair of types, where a type in Modules~RemoteTransport uses a type in Modules~AppFeature.
Modules~RemoteTransport uses Modules~AppFeature, so a change to Modules~AppFeature can break Modules~RemoteTransport, while a change to Modules~RemoteTransport can't break Modules~AppFeature.
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.
Modules~OnlyAgent uses Modules~DesktopPetSkinKit, so a change to Modules~DesktopPetSkinKit can break Modules~OnlyAgent, while a change to Modules~OnlyAgent can't break Modules~DesktopPetSkinKit.
Position
Below the diagonal: Modules~OnlyAgent uses a module listed above it, which is the healthy direction.
Modules~OnlyAgent uses Modules~RemoteTransport, so a change to Modules~RemoteTransport can break Modules~OnlyAgent, while a change to Modules~OnlyAgent can't break Modules~RemoteTransport.
Position
Below the diagonal: Modules~OnlyAgent uses a module listed above it, which is the healthy direction.
9→11 Modules~OnlyAgent uses Modules~DesktopPetpart of a loop✕
Connections
1 pair of types, where a type in Modules~OnlyAgent uses a type in Modules~DesktopPet.
Modules~OnlyAgent uses Modules~DesktopPet, so a change to Modules~DesktopPet can break Modules~OnlyAgent, while a change to Modules~OnlyAgent can't break Modules~DesktopPet.
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.
9→12 Modules~OnlyAgent uses Modules~Extensionspart of a loop✕
Connections
77 pairs of types, where a type in Modules~OnlyAgent uses a type in Modules~Extensions. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Modules~OnlyAgent uses Modules~Extensions, so a change to Modules~Extensions can break Modules~OnlyAgent, while a change to Modules~OnlyAgent can't break Modules~Extensions.
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.
9→13 Modules~OnlyAgent uses Modules~Designpart of a loop✕
Connections
91 pairs of types, where a type in Modules~OnlyAgent uses a type in Modules~Design. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Modules~OnlyAgent uses Modules~Design, so a change to Modules~Design can break Modules~OnlyAgent, while a change to Modules~OnlyAgent can't break Modules~Design.
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.
9→30 Modules~OnlyAgent uses Modules~AppFeaturepart of a loop✕
Connections
3 pairs of types, where a type in Modules~OnlyAgent uses a type in Modules~AppFeature.
Modules~OnlyAgent uses Modules~AppFeature, so a change to Modules~AppFeature can break Modules~OnlyAgent, while a change to Modules~OnlyAgent can't break Modules~AppFeature.
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.
9→34 Modules~OnlyAgent uses Modules~Aphroditepart of a loop✕
Connections
25 pairs of types, where a type in Modules~OnlyAgent uses a type in Modules~Aphrodite.
Modules~OnlyAgent uses Modules~Aphrodite, so a change to Modules~Aphrodite can break Modules~OnlyAgent, while a change to Modules~OnlyAgent can't break Modules~Aphrodite.
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.
117 pairs of types, where a type in Modules~OnlyRemoteFeature uses a type in Modules~RemoteCore. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Modules~OnlyRemoteFeature uses Modules~RemoteCore, so a change to Modules~RemoteCore can break Modules~OnlyRemoteFeature, while a change to Modules~OnlyRemoteFeature can't break Modules~RemoteCore.
Position
Below the diagonal: Modules~OnlyRemoteFeature uses a module listed above it, which is the healthy direction.
Modules~OnlyRemoteFeature uses Modules~RemoteTransport, so a change to Modules~RemoteTransport can break Modules~OnlyRemoteFeature, while a change to Modules~OnlyRemoteFeature can't break Modules~RemoteTransport.
Position
Below the diagonal: Modules~OnlyRemoteFeature uses a module listed above it, which is the healthy direction.
Modules~OnlyRemoteFeature uses Modules~OnlyAgent, so a change to Modules~OnlyAgent can break Modules~OnlyRemoteFeature, while a change to Modules~OnlyRemoteFeature can't break Modules~OnlyAgent.
Position
Below the diagonal: Modules~OnlyRemoteFeature uses a module listed above it, which is the healthy direction.
10→11 Modules~OnlyRemoteFeature uses Modules~DesktopPetpart of a loop✕
Connections
4 pairs of types, where a type in Modules~OnlyRemoteFeature uses a type in Modules~DesktopPet.
Modules~OnlyRemoteFeature uses Modules~DesktopPet, so a change to Modules~DesktopPet can break Modules~OnlyRemoteFeature, while a change to Modules~OnlyRemoteFeature can't break Modules~DesktopPet.
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.
10→12 Modules~OnlyRemoteFeature uses Modules~Extensionspart of a loop✕
Connections
99 pairs of types, where a type in Modules~OnlyRemoteFeature uses a type in Modules~Extensions. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Modules~OnlyRemoteFeature uses Modules~Extensions, so a change to Modules~Extensions can break Modules~OnlyRemoteFeature, while a change to Modules~OnlyRemoteFeature can't break Modules~Extensions.
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.
10→13 Modules~OnlyRemoteFeature uses Modules~Designpart of a loop✕
Connections
56 pairs of types, where a type in Modules~OnlyRemoteFeature uses a type in Modules~Design. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Modules~OnlyRemoteFeature uses Modules~Design, so a change to Modules~Design can break Modules~OnlyRemoteFeature, while a change to Modules~OnlyRemoteFeature can't break Modules~Design.
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.
10→30 Modules~OnlyRemoteFeature uses Modules~AppFeaturepart of a loop✕
Connections
14 pairs of types, where a type in Modules~OnlyRemoteFeature uses a type in Modules~AppFeature.
Modules~OnlyRemoteFeature uses Modules~AppFeature, so a change to Modules~AppFeature can break Modules~OnlyRemoteFeature, while a change to Modules~OnlyRemoteFeature can't break Modules~AppFeature.
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.
10→34 Modules~OnlyRemoteFeature uses Modules~Aphroditepart of a loop✕
Connections
55 pairs of types, where a type in Modules~OnlyRemoteFeature uses a type in Modules~Aphrodite. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Modules~OnlyRemoteFeature uses Modules~Aphrodite, so a change to Modules~Aphrodite can break Modules~OnlyRemoteFeature, while a change to Modules~OnlyRemoteFeature can't break Modules~Aphrodite.
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.
Modules~DesktopPet uses Modules~DesktopPetSkinKit, so a change to Modules~DesktopPetSkinKit can break Modules~DesktopPet, while a change to Modules~DesktopPet can't break Modules~DesktopPetSkinKit.
Position
Below the diagonal: Modules~DesktopPet uses a module listed above it, which is the healthy direction.
Modules~DesktopPet uses Modules~RemoteTransport, so a change to Modules~RemoteTransport can break Modules~DesktopPet, while a change to Modules~DesktopPet can't break Modules~RemoteTransport.
Position
Below the diagonal: Modules~DesktopPet uses a module listed above it, which is the healthy direction.
Modules~DesktopPet uses Modules~OnlyAgent, so a change to Modules~OnlyAgent can break Modules~DesktopPet, while a change to Modules~DesktopPet can't break Modules~OnlyAgent.
Position
Below the diagonal: Modules~DesktopPet uses a module listed above it, which is the healthy direction.
Modules~DesktopPet uses Modules~OnlyRemoteFeature, so a change to Modules~OnlyRemoteFeature can break Modules~DesktopPet, while a change to Modules~DesktopPet can't break Modules~OnlyRemoteFeature.
Position
Below the diagonal: Modules~DesktopPet uses a module listed above it, which is the healthy direction.
11→12 Modules~DesktopPet uses Modules~Extensionspart of a loop✕
Connections
59 pairs of types, where a type in Modules~DesktopPet uses a type in Modules~Extensions. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Modules~DesktopPet uses Modules~Extensions, so a change to Modules~Extensions can break Modules~DesktopPet, while a change to Modules~DesktopPet can't break Modules~Extensions.
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.
11→13 Modules~DesktopPet uses Modules~Designpart of a loop✕
Connections
27 pairs of types, where a type in Modules~DesktopPet uses a type in Modules~Design. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Modules~DesktopPet uses Modules~Design, so a change to Modules~Design can break Modules~DesktopPet, while a change to Modules~DesktopPet can't break Modules~Design.
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.
11→30 Modules~DesktopPet uses Modules~AppFeaturepart of a loop✕
Connections
4 pairs of types, where a type in Modules~DesktopPet uses a type in Modules~AppFeature.
Modules~DesktopPet uses Modules~AppFeature, so a change to Modules~AppFeature can break Modules~DesktopPet, while a change to Modules~DesktopPet can't break Modules~AppFeature.
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.
11→34 Modules~DesktopPet uses Modules~Aphroditepart of a loop✕
Connections
17 pairs of types, where a type in Modules~DesktopPet uses a type in Modules~Aphrodite.
Modules~DesktopPet uses Modules~Aphrodite, so a change to Modules~Aphrodite can break Modules~DesktopPet, while a change to Modules~DesktopPet can't break Modules~Aphrodite.
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.
Modules~Extensions uses Modules~RemoteTransport, so a change to Modules~RemoteTransport can break Modules~Extensions, while a change to Modules~Extensions can't break Modules~RemoteTransport.
Position
Below the diagonal: Modules~Extensions uses a module listed above it, which is the healthy direction.
Modules~Extensions uses Modules~DesktopPet, so a change to Modules~DesktopPet can break Modules~Extensions, while a change to Modules~Extensions can't break Modules~DesktopPet.
Position
Below the diagonal: Modules~Extensions uses a module listed above it, which is the healthy direction.
12→13 Modules~Extensions uses Modules~Designpart of a loop✕
Connections
12 pairs of types, where a type in Modules~Extensions uses a type in Modules~Design.
Modules~Extensions uses Modules~Design, so a change to Modules~Design can break Modules~Extensions, while a change to Modules~Extensions can't break Modules~Design.
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.
Modules~Design uses Modules~Extensions, so a change to Modules~Extensions can break Modules~Design, while a change to Modules~Design can't break Modules~Extensions.
Position
Below the diagonal: Modules~Design uses a module listed above it, which is the healthy direction.
13→34 Modules~Design uses Modules~Aphroditepart of a loop✕
Connections
3 pairs of types, where a type in Modules~Design uses a type in Modules~Aphrodite.
Modules~Design uses Modules~Aphrodite, so a change to Modules~Aphrodite can break Modules~Design, while a change to Modules~Design can't break Modules~Aphrodite.
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.
Modules~AppUninstaller uses Modules~OnlyAgent, so a change to Modules~OnlyAgent can break Modules~AppUninstaller, while a change to Modules~AppUninstaller can't break Modules~OnlyAgent.
Position
Below the diagonal: Modules~AppUninstaller uses a module listed above it, which is the healthy direction.
Modules~AppUninstaller uses Modules~Extensions, so a change to Modules~Extensions can break Modules~AppUninstaller, while a change to Modules~AppUninstaller can't break Modules~Extensions.
Position
Below the diagonal: Modules~AppUninstaller uses a module listed above it, which is the healthy direction.
Modules~AppUninstaller uses Modules~Design, so a change to Modules~Design can break Modules~AppUninstaller, while a change to Modules~AppUninstaller can't break Modules~Design.
Position
Below the diagonal: Modules~AppUninstaller uses a module listed above it, which is the healthy direction.
14→34 Modules~AppUninstaller uses Modules~Aphroditepart of a loop✕
Connections
2 pairs of types, where a type in Modules~AppUninstaller uses a type in Modules~Aphrodite.
Modules~AppUninstaller uses Modules~Aphrodite, so a change to Modules~Aphrodite can break Modules~AppUninstaller, while a change to Modules~AppUninstaller can't break Modules~Aphrodite.
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.
Modules~Defines uses Modules~Design, so a change to Modules~Design can break Modules~Defines, while a change to Modules~Defines can't break Modules~Design.
Position
Below the diagonal: Modules~Defines uses a module listed above it, which is the healthy direction.
Modules~DisplayDDC uses Modules~Extensions, so a change to Modules~Extensions can break Modules~DisplayDDC, while a change to Modules~DisplayDDC can't break Modules~Extensions.
Position
Below the diagonal: Modules~DisplayDDC uses a module listed above it, which is the healthy direction.
Modules~DisplayDDC uses Modules~Design, so a change to Modules~Design can break Modules~DisplayDDC, while a change to Modules~DisplayDDC can't break Modules~Design.
Position
Below the diagonal: Modules~DisplayDDC uses a module listed above it, which is the healthy direction.
Modules~Networking uses Modules~RemoteTransport, so a change to Modules~RemoteTransport can break Modules~Networking, while a change to Modules~Networking can't break Modules~RemoteTransport.
Position
Below the diagonal: Modules~Networking uses a module listed above it, which is the healthy direction.
Modules~Networking uses Modules~Extensions, so a change to Modules~Extensions can break Modules~Networking, while a change to Modules~Networking can't break Modules~Extensions.
Position
Below the diagonal: Modules~Networking uses a module listed above it, which is the healthy direction.
Modules~Networking uses Modules~Design, so a change to Modules~Design can break Modules~Networking, while a change to Modules~Networking can't break Modules~Design.
Position
Below the diagonal: Modules~Networking uses a module listed above it, which is the healthy direction.
Modules~OnlySwitchPersistence uses Modules~Extensions, so a change to Modules~Extensions can break Modules~OnlySwitchPersistence, while a change to Modules~OnlySwitchPersistence can't break Modules~Extensions.
Position
Below the diagonal: Modules~OnlySwitchPersistence uses a module listed above it, which is the healthy direction.
Modules~OnlySwitchPersistence uses Modules~Design, so a change to Modules~Design can break Modules~OnlySwitchPersistence, while a change to Modules~OnlySwitchPersistence can't break Modules~Design.
Position
Below the diagonal: Modules~OnlySwitchPersistence uses a module listed above it, which is the healthy direction.
18→30 Modules~OnlySwitchPersistence uses Modules~AppFeaturepart of a loop✕
Connections
1 pair of types, where a type in Modules~OnlySwitchPersistence uses a type in Modules~AppFeature.
Modules~OnlySwitchPersistence uses Modules~AppFeature, so a change to Modules~AppFeature can break Modules~OnlySwitchPersistence, while a change to Modules~OnlySwitchPersistence can't break Modules~AppFeature.
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.
Modules~PrivilegedHelperCore uses Modules~Extensions, so a change to Modules~Extensions can break Modules~PrivilegedHelperCore, while a change to Modules~PrivilegedHelperCore can't break Modules~Extensions.
Position
Below the diagonal: Modules~PrivilegedHelperCore uses a module listed above it, which is the healthy direction.
Modules~PrivilegedHelperCore uses Modules~Design, so a change to Modules~Design can break Modules~PrivilegedHelperCore, while a change to Modules~PrivilegedHelperCore can't break Modules~Design.
Position
Below the diagonal: Modules~PrivilegedHelperCore uses a module listed above it, which is the healthy direction.
Modules~RadioBrowser uses Modules~RemoteTransport, so a change to Modules~RemoteTransport can break Modules~RadioBrowser, while a change to Modules~RadioBrowser can't break Modules~RemoteTransport.
Position
Below the diagonal: Modules~RadioBrowser uses a module listed above it, which is the healthy direction.
Modules~RadioBrowser uses Modules~OnlyAgent, so a change to Modules~OnlyAgent can break Modules~RadioBrowser, while a change to Modules~RadioBrowser can't break Modules~OnlyAgent.
Position
Below the diagonal: Modules~RadioBrowser uses a module listed above it, which is the healthy direction.
Modules~RadioBrowser uses Modules~Extensions, so a change to Modules~Extensions can break Modules~RadioBrowser, while a change to Modules~RadioBrowser can't break Modules~Extensions.
Position
Below the diagonal: Modules~RadioBrowser uses a module listed above it, which is the healthy direction.
Modules~RadioBrowser uses Modules~Design, so a change to Modules~Design can break Modules~RadioBrowser, while a change to Modules~RadioBrowser can't break Modules~Design.
Position
Below the diagonal: Modules~RadioBrowser uses a module listed above it, which is the healthy direction.
20→30 Modules~RadioBrowser uses Modules~AppFeaturepart of a loop✕
Connections
2 pairs of types, where a type in Modules~RadioBrowser uses a type in Modules~AppFeature.
Modules~RadioBrowser uses Modules~AppFeature, so a change to Modules~AppFeature can break Modules~RadioBrowser, while a change to Modules~RadioBrowser can't break Modules~AppFeature.
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.
20→34 Modules~RadioBrowser uses Modules~Aphroditepart of a loop✕
Connections
10 pairs of types, where a type in Modules~RadioBrowser uses a type in Modules~Aphrodite.
Modules~RadioBrowser uses Modules~Aphrodite, so a change to Modules~Aphrodite can break Modules~RadioBrowser, while a change to Modules~RadioBrowser can't break Modules~Aphrodite.
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.
Modules~Scheduler uses Modules~RemoteCore, so a change to Modules~RemoteCore can break Modules~Scheduler, while a change to Modules~Scheduler can't break Modules~RemoteCore.
Position
Below the diagonal: Modules~Scheduler uses a module listed above it, which is the healthy direction.
Modules~Scheduler uses Modules~OnlyAgent, so a change to Modules~OnlyAgent can break Modules~Scheduler, while a change to Modules~Scheduler can't break Modules~OnlyAgent.
Position
Below the diagonal: Modules~Scheduler uses a module listed above it, which is the healthy direction.
Modules~Scheduler uses Modules~OnlyRemoteFeature, so a change to Modules~OnlyRemoteFeature can break Modules~Scheduler, while a change to Modules~Scheduler can't break Modules~OnlyRemoteFeature.
Position
Below the diagonal: Modules~Scheduler uses a module listed above it, which is the healthy direction.
33 pairs of types, where a type in Modules~Scheduler uses a type in Modules~Extensions. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Modules~Scheduler uses Modules~Extensions, so a change to Modules~Extensions can break Modules~Scheduler, while a change to Modules~Scheduler can't break Modules~Extensions.
Position
Below the diagonal: Modules~Scheduler uses a module listed above it, which is the healthy direction.
Modules~Scheduler uses Modules~Design, so a change to Modules~Design can break Modules~Scheduler, while a change to Modules~Scheduler can't break Modules~Design.
Position
Below the diagonal: Modules~Scheduler uses a module listed above it, which is the healthy direction.
21→30 Modules~Scheduler uses Modules~AppFeaturepart of a loop✕
Connections
1 pair of types, where a type in Modules~Scheduler uses a type in Modules~AppFeature.
Modules~Scheduler uses Modules~AppFeature, so a change to Modules~AppFeature can break Modules~Scheduler, while a change to Modules~Scheduler can't break Modules~AppFeature.
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.
21→34 Modules~Scheduler uses Modules~Aphroditepart of a loop✕
Connections
26 pairs of types, where a type in Modules~Scheduler uses a type in Modules~Aphrodite. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Modules~Scheduler uses Modules~Aphrodite, so a change to Modules~Aphrodite can break Modules~Scheduler, while a change to Modules~Scheduler can't break Modules~Aphrodite.
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.
Modules~Screenshots uses Modules~DisplayBrightness, so a change to Modules~DisplayBrightness can break Modules~Screenshots, while a change to Modules~Screenshots can't break Modules~DisplayBrightness.
Position
Below the diagonal: Modules~Screenshots uses a module listed above it, which is the healthy direction.
Modules~Screenshots uses Modules~RemoteTransport, so a change to Modules~RemoteTransport can break Modules~Screenshots, while a change to Modules~Screenshots can't break Modules~RemoteTransport.
Position
Below the diagonal: Modules~Screenshots uses a module listed above it, which is the healthy direction.
Modules~Screenshots uses Modules~OnlyAgent, so a change to Modules~OnlyAgent can break Modules~Screenshots, while a change to Modules~Screenshots can't break Modules~OnlyAgent.
Position
Below the diagonal: Modules~Screenshots uses a module listed above it, which is the healthy direction.
Modules~Screenshots uses Modules~DesktopPet, so a change to Modules~DesktopPet can break Modules~Screenshots, while a change to Modules~Screenshots can't break Modules~DesktopPet.
Position
Below the diagonal: Modules~Screenshots uses a module listed above it, which is the healthy direction.
66 pairs of types, where a type in Modules~Screenshots uses a type in Modules~Extensions. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Modules~Screenshots uses Modules~Extensions, so a change to Modules~Extensions can break Modules~Screenshots, while a change to Modules~Screenshots can't break Modules~Extensions.
Position
Below the diagonal: Modules~Screenshots uses a module listed above it, which is the healthy direction.
Modules~Screenshots uses Modules~Design, so a change to Modules~Design can break Modules~Screenshots, while a change to Modules~Screenshots can't break Modules~Design.
Position
Below the diagonal: Modules~Screenshots uses a module listed above it, which is the healthy direction.
22→30 Modules~Screenshots uses Modules~AppFeaturepart of a loop✕
Connections
2 pairs of types, where a type in Modules~Screenshots uses a type in Modules~AppFeature.
Modules~Screenshots uses Modules~AppFeature, so a change to Modules~AppFeature can break Modules~Screenshots, while a change to Modules~Screenshots can't break Modules~AppFeature.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→34 Modules~Screenshots uses Modules~Aphroditepart of a loop✕
Connections
31 pairs of types, where a type in Modules~Screenshots uses a type in Modules~Aphrodite. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Modules~Screenshots uses Modules~Aphrodite, so a change to Modules~Aphrodite can break Modules~Screenshots, while a change to Modules~Screenshots can't break Modules~Aphrodite.
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.
Modules~Switches uses Modules~RemoteTransport, so a change to Modules~RemoteTransport can break Modules~Switches, while a change to Modules~Switches can't break Modules~RemoteTransport.
Position
Below the diagonal: Modules~Switches uses a module listed above it, which is the healthy direction.
Modules~Switches uses Modules~Extensions, so a change to Modules~Extensions can break Modules~Switches, while a change to Modules~Switches can't break Modules~Extensions.
Position
Below the diagonal: Modules~Switches uses a module listed above it, which is the healthy direction.
Modules~Switches uses Modules~Design, so a change to Modules~Design can break Modules~Switches, while a change to Modules~Switches can't break Modules~Design.
Position
Below the diagonal: Modules~Switches uses a module listed above it, which is the healthy direction.
Modules~SystemMonitor uses Modules~RemoteCore, so a change to Modules~RemoteCore can break Modules~SystemMonitor, while a change to Modules~SystemMonitor can't break Modules~RemoteCore.
Position
Below the diagonal: Modules~SystemMonitor uses a module listed above it, which is the healthy direction.
Modules~SystemMonitor uses Modules~Extensions, so a change to Modules~Extensions can break Modules~SystemMonitor, while a change to Modules~SystemMonitor can't break Modules~Extensions.
Position
Below the diagonal: Modules~SystemMonitor uses a module listed above it, which is the healthy direction.
Modules~SystemMonitor uses Modules~Design, so a change to Modules~Design can break Modules~SystemMonitor, while a change to Modules~SystemMonitor can't break Modules~Design.
Position
Below the diagonal: Modules~SystemMonitor uses a module listed above it, which is the healthy direction.
24→30 Modules~SystemMonitor uses Modules~AppFeaturepart of a loop✕
Connections
1 pair of types, where a type in Modules~SystemMonitor uses a type in Modules~AppFeature.
Modules~SystemMonitor uses Modules~AppFeature, so a change to Modules~AppFeature can break Modules~SystemMonitor, while a change to Modules~SystemMonitor can't break Modules~AppFeature.
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.
Modules~Tailscale uses Modules~RemoteTransport, so a change to Modules~RemoteTransport can break Modules~Tailscale, while a change to Modules~Tailscale can't break Modules~RemoteTransport.
Position
Below the diagonal: Modules~Tailscale uses a module listed above it, which is the healthy direction.
Modules~Tailscale uses Modules~OnlyAgent, so a change to Modules~OnlyAgent can break Modules~Tailscale, while a change to Modules~Tailscale can't break Modules~OnlyAgent.
Position
Below the diagonal: Modules~Tailscale uses a module listed above it, which is the healthy direction.
Modules~Tailscale uses Modules~Extensions, so a change to Modules~Extensions can break Modules~Tailscale, while a change to Modules~Tailscale can't break Modules~Extensions.
Position
Below the diagonal: Modules~Tailscale uses a module listed above it, which is the healthy direction.
Modules~Tailscale uses Modules~Design, so a change to Modules~Design can break Modules~Tailscale, while a change to Modules~Tailscale can't break Modules~Design.
Position
Below the diagonal: Modules~Tailscale uses a module listed above it, which is the healthy direction.
25→30 Modules~Tailscale uses Modules~AppFeaturepart of a loop✕
Connections
1 pair of types, where a type in Modules~Tailscale uses a type in Modules~AppFeature.
Modules~Tailscale uses Modules~AppFeature, so a change to Modules~AppFeature can break Modules~Tailscale, while a change to Modules~Tailscale can't break Modules~AppFeature.
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.
25→34 Modules~Tailscale uses Modules~Aphroditepart of a loop✕
Connections
2 pairs of types, where a type in Modules~Tailscale uses a type in Modules~Aphrodite.
Modules~Tailscale uses Modules~Aphrodite, so a change to Modules~Aphrodite can break Modules~Tailscale, while a change to Modules~Tailscale can't break Modules~Aphrodite.
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.
Modules~Utilities uses Modules~Extensions, so a change to Modules~Extensions can break Modules~Utilities, while a change to Modules~Utilities can't break Modules~Extensions.
Position
Below the diagonal: Modules~Utilities uses a module listed above it, which is the healthy direction.
Modules~Utilities uses Modules~Design, so a change to Modules~Design can break Modules~Utilities, while a change to Modules~Utilities can't break Modules~Design.
Position
Below the diagonal: Modules~Utilities uses a module listed above it, which is the healthy direction.
Modules~Authenticator uses Modules~RemoteCore, so a change to Modules~RemoteCore can break Modules~Authenticator, while a change to Modules~Authenticator can't break Modules~RemoteCore.
Position
Below the diagonal: Modules~Authenticator uses a module listed above it, which is the healthy direction.
Modules~Authenticator uses Modules~RemoteTransport, so a change to Modules~RemoteTransport can break Modules~Authenticator, while a change to Modules~Authenticator can't break Modules~RemoteTransport.
Position
Below the diagonal: Modules~Authenticator uses a module listed above it, which is the healthy direction.
Modules~Authenticator uses Modules~Extensions, so a change to Modules~Extensions can break Modules~Authenticator, while a change to Modules~Authenticator can't break Modules~Extensions.
Position
Below the diagonal: Modules~Authenticator uses a module listed above it, which is the healthy direction.
Modules~Authenticator uses Modules~Design, so a change to Modules~Design can break Modules~Authenticator, while a change to Modules~Authenticator can't break Modules~Design.
Position
Below the diagonal: Modules~Authenticator uses a module listed above it, which is the healthy direction.
Modules~Authenticator uses Modules~Scheduler, so a change to Modules~Scheduler can break Modules~Authenticator, while a change to Modules~Authenticator can't break Modules~Scheduler.
Position
Below the diagonal: Modules~Authenticator uses a module listed above it, which is the healthy direction.
Modules~Authenticator uses Modules~Screenshots, so a change to Modules~Screenshots can break Modules~Authenticator, while a change to Modules~Authenticator can't break Modules~Screenshots.
Position
Below the diagonal: Modules~Authenticator uses a module listed above it, which is the healthy direction.
27→34 Modules~Authenticator uses Modules~Aphroditepart of a loop✕
Connections
6 pairs of types, where a type in Modules~Authenticator uses a type in Modules~Aphrodite.
Modules~Authenticator uses Modules~Aphrodite, so a change to Modules~Aphrodite can break Modules~Authenticator, while a change to Modules~Authenticator can't break Modules~Aphrodite.
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.
Modules~StickerView uses Modules~Extensions, so a change to Modules~Extensions can break Modules~StickerView, while a change to Modules~StickerView can't break Modules~Extensions.
Position
Below the diagonal: Modules~StickerView uses a module listed above it, which is the healthy direction.
Modules~StickerView uses Modules~Design, so a change to Modules~Design can break Modules~StickerView, while a change to Modules~StickerView can't break Modules~Design.
Position
Below the diagonal: Modules~StickerView uses a module listed above it, which is the healthy direction.
Modules~StickerView uses Modules~Defines, so a change to Modules~Defines can break Modules~StickerView, while a change to Modules~StickerView can't break Modules~Defines.
Position
Below the diagonal: Modules~StickerView uses a module listed above it, which is the healthy direction.
28→34 Modules~StickerView uses Modules~Aphroditepart of a loop✕
Connections
8 pairs of types, where a type in Modules~StickerView uses a type in Modules~Aphrodite.
Modules~StickerView uses Modules~Aphrodite, so a change to Modules~Aphrodite can break Modules~StickerView, while a change to Modules~StickerView can't break Modules~Aphrodite.
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.
Modules~SoundMixerEQ uses Modules~Extensions, so a change to Modules~Extensions can break Modules~SoundMixerEQ, while a change to Modules~SoundMixerEQ can't break Modules~Extensions.
Position
Below the diagonal: Modules~SoundMixerEQ uses a module listed above it, which is the healthy direction.
Modules~SoundMixerEQ uses Modules~Design, so a change to Modules~Design can break Modules~SoundMixerEQ, while a change to Modules~SoundMixerEQ can't break Modules~Design.
Position
Below the diagonal: Modules~SoundMixerEQ uses a module listed above it, which is the healthy direction.
Modules~SoundMixerEQ uses Modules~Authenticator, so a change to Modules~Authenticator can break Modules~SoundMixerEQ, while a change to Modules~SoundMixerEQ can't break Modules~Authenticator.
Position
Below the diagonal: Modules~SoundMixerEQ uses a module listed above it, which is the healthy direction.
29→30 Modules~SoundMixerEQ uses Modules~AppFeaturepart of a loop✕
Connections
2 pairs of types, where a type in Modules~SoundMixerEQ uses a type in Modules~AppFeature.
Modules~SoundMixerEQ uses Modules~AppFeature, so a change to Modules~AppFeature can break Modules~SoundMixerEQ, while a change to Modules~SoundMixerEQ can't break Modules~AppFeature.
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.
29→34 Modules~SoundMixerEQ uses Modules~Aphroditepart of a loop✕
Connections
3 pairs of types, where a type in Modules~SoundMixerEQ uses a type in Modules~Aphrodite.
Modules~SoundMixerEQ uses Modules~Aphrodite, so a change to Modules~Aphrodite can break Modules~SoundMixerEQ, while a change to Modules~SoundMixerEQ can't break Modules~Aphrodite.
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.
Modules~AppFeature uses Modules~DesktopPetSkinKit, so a change to Modules~DesktopPetSkinKit can break Modules~AppFeature, while a change to Modules~AppFeature can't break Modules~DesktopPetSkinKit.
Position
Below the diagonal: Modules~AppFeature uses a module listed above it, which is the healthy direction.
Modules~AppFeature uses Modules~DisplayBrightness, so a change to Modules~DisplayBrightness can break Modules~AppFeature, while a change to Modules~AppFeature can't break Modules~DisplayBrightness.
Position
Below the diagonal: Modules~AppFeature uses a module listed above it, which is the healthy direction.
81 pairs of types, where a type in Modules~AppFeature uses a type in Modules~RemoteCore. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Modules~AppFeature uses Modules~RemoteCore, so a change to Modules~RemoteCore can break Modules~AppFeature, while a change to Modules~AppFeature can't break Modules~RemoteCore.
Position
Below the diagonal: Modules~AppFeature uses a module listed above it, which is the healthy direction.
33 pairs of types, where a type in Modules~AppFeature uses a type in Modules~RemoteTransport. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Modules~AppFeature uses Modules~RemoteTransport, so a change to Modules~RemoteTransport can break Modules~AppFeature, while a change to Modules~AppFeature can't break Modules~RemoteTransport.
Position
Below the diagonal: Modules~AppFeature uses a module listed above it, which is the healthy direction.
Modules~AppFeature uses Modules~OnlyAgent, so a change to Modules~OnlyAgent can break Modules~AppFeature, while a change to Modules~AppFeature can't break Modules~OnlyAgent.
Position
Below the diagonal: Modules~AppFeature uses a module listed above it, which is the healthy direction.
Modules~AppFeature uses Modules~DesktopPet, so a change to Modules~DesktopPet can break Modules~AppFeature, while a change to Modules~AppFeature can't break Modules~DesktopPet.
Position
Below the diagonal: Modules~AppFeature uses a module listed above it, which is the healthy direction.
438 pairs of types, where a type in Modules~AppFeature uses a type in Modules~Extensions. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Modules~AppFeature uses Modules~Extensions, so a change to Modules~Extensions can break Modules~AppFeature, while a change to Modules~AppFeature can't break Modules~Extensions.
Position
Below the diagonal: Modules~AppFeature uses a module listed above it, which is the healthy direction.
250 pairs of types, where a type in Modules~AppFeature uses a type in Modules~Design. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Modules~AppFeature uses Modules~Design, so a change to Modules~Design can break Modules~AppFeature, while a change to Modules~AppFeature can't break Modules~Design.
Position
Below the diagonal: Modules~AppFeature uses a module listed above it, which is the healthy direction.
Modules~AppFeature uses Modules~Defines, so a change to Modules~Defines can break Modules~AppFeature, while a change to Modules~AppFeature can't break Modules~Defines.
Position
Below the diagonal: Modules~AppFeature uses a module listed above it, which is the healthy direction.
Modules~AppFeature uses Modules~Networking, so a change to Modules~Networking can break Modules~AppFeature, while a change to Modules~AppFeature can't break Modules~Networking.
Position
Below the diagonal: Modules~AppFeature uses a module listed above it, which is the healthy direction.
Modules~AppFeature uses Modules~OnlySwitchPersistence, so a change to Modules~OnlySwitchPersistence can break Modules~AppFeature, while a change to Modules~AppFeature can't break Modules~OnlySwitchPersistence.
Position
Below the diagonal: Modules~AppFeature uses a module listed above it, which is the healthy direction.
Modules~AppFeature uses Modules~PrivilegedHelperCore, so a change to Modules~PrivilegedHelperCore can break Modules~AppFeature, while a change to Modules~AppFeature can't break Modules~PrivilegedHelperCore.
Position
Below the diagonal: Modules~AppFeature uses a module listed above it, which is the healthy direction.
Modules~AppFeature uses Modules~RadioBrowser, so a change to Modules~RadioBrowser can break Modules~AppFeature, while a change to Modules~AppFeature can't break Modules~RadioBrowser.
Position
Below the diagonal: Modules~AppFeature uses a module listed above it, which is the healthy direction.
Modules~AppFeature uses Modules~Scheduler, so a change to Modules~Scheduler can break Modules~AppFeature, while a change to Modules~AppFeature can't break Modules~Scheduler.
Position
Below the diagonal: Modules~AppFeature uses a module listed above it, which is the healthy direction.
Modules~AppFeature uses Modules~Screenshots, so a change to Modules~Screenshots can break Modules~AppFeature, while a change to Modules~AppFeature can't break Modules~Screenshots.
Position
Below the diagonal: Modules~AppFeature uses a module listed above it, which is the healthy direction.
175 pairs of types, where a type in Modules~AppFeature uses a type in Modules~Switches. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Modules~AppFeature uses Modules~Switches, so a change to Modules~Switches can break Modules~AppFeature, while a change to Modules~AppFeature can't break Modules~Switches.
Position
Below the diagonal: Modules~AppFeature uses a module listed above it, which is the healthy direction.
Modules~AppFeature uses Modules~SystemMonitor, so a change to Modules~SystemMonitor can break Modules~AppFeature, while a change to Modules~AppFeature can't break Modules~SystemMonitor.
Position
Below the diagonal: Modules~AppFeature uses a module listed above it, which is the healthy direction.
Modules~AppFeature uses Modules~Tailscale, so a change to Modules~Tailscale can break Modules~AppFeature, while a change to Modules~AppFeature can't break Modules~Tailscale.
Position
Below the diagonal: Modules~AppFeature uses a module listed above it, which is the healthy direction.
Modules~AppFeature uses Modules~Authenticator, so a change to Modules~Authenticator can break Modules~AppFeature, while a change to Modules~AppFeature can't break Modules~Authenticator.
Position
Below the diagonal: Modules~AppFeature uses a module listed above it, which is the healthy direction.
Modules~AppFeature uses Modules~StickerView, so a change to Modules~StickerView can break Modules~AppFeature, while a change to Modules~AppFeature can't break Modules~StickerView.
Position
Below the diagonal: Modules~AppFeature uses a module listed above it, which is the healthy direction.
Modules~AppFeature uses Modules~SoundMixerEQ, so a change to Modules~SoundMixerEQ can break Modules~AppFeature, while a change to Modules~AppFeature can't break Modules~SoundMixerEQ.
Position
Below the diagonal: Modules~AppFeature uses a module listed above it, which is the healthy direction.
30→34 Modules~AppFeature uses Modules~Aphroditepart of a loop✕
Connections
100 pairs of types, where a type in Modules~AppFeature uses a type in Modules~Aphrodite. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Modules~AppFeature uses Modules~Aphrodite, so a change to Modules~Aphrodite can break Modules~AppFeature, while a change to Modules~AppFeature can't break Modules~Aphrodite.
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.
Modules~WebBrowser uses Modules~OnlyAgent, so a change to Modules~OnlyAgent can break Modules~WebBrowser, while a change to Modules~WebBrowser can't break Modules~OnlyAgent.
Position
Below the diagonal: Modules~WebBrowser uses a module listed above it, which is the healthy direction.
Modules~WebBrowser uses Modules~Extensions, so a change to Modules~Extensions can break Modules~WebBrowser, while a change to Modules~WebBrowser can't break Modules~Extensions.
Position
Below the diagonal: Modules~WebBrowser uses a module listed above it, which is the healthy direction.
Modules~WebBrowser uses Modules~Design, so a change to Modules~Design can break Modules~WebBrowser, while a change to Modules~WebBrowser can't break Modules~Design.
Position
Below the diagonal: Modules~WebBrowser uses a module listed above it, which is the healthy direction.
Modules~WebBrowser uses Modules~AppFeature, so a change to Modules~AppFeature can break Modules~WebBrowser, while a change to Modules~WebBrowser can't break Modules~AppFeature.
Position
Below the diagonal: Modules~WebBrowser uses a module listed above it, which is the healthy direction.
31→34 Modules~WebBrowser uses Modules~Aphroditepart of a loop✕
Connections
7 pairs of types, where a type in Modules~WebBrowser uses a type in Modules~Aphrodite.
Modules~WebBrowser uses Modules~Aphrodite, so a change to Modules~Aphrodite can break Modules~WebBrowser, while a change to Modules~WebBrowser can't break Modules~Aphrodite.
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.
Modules~XcodeCleaner uses Modules~OnlyAgent, so a change to Modules~OnlyAgent can break Modules~XcodeCleaner, while a change to Modules~XcodeCleaner can't break Modules~OnlyAgent.
Position
Below the diagonal: Modules~XcodeCleaner uses a module listed above it, which is the healthy direction.
Modules~XcodeCleaner uses Modules~Extensions, so a change to Modules~Extensions can break Modules~XcodeCleaner, while a change to Modules~XcodeCleaner can't break Modules~Extensions.
Position
Below the diagonal: Modules~XcodeCleaner uses a module listed above it, which is the healthy direction.
Modules~XcodeCleaner uses Modules~Design, so a change to Modules~Design can break Modules~XcodeCleaner, while a change to Modules~XcodeCleaner can't break Modules~Design.
Position
Below the diagonal: Modules~XcodeCleaner uses a module listed above it, which is the healthy direction.
Modules~XcodeCleaner uses Modules~AppFeature, so a change to Modules~AppFeature can break Modules~XcodeCleaner, while a change to Modules~XcodeCleaner can't break Modules~AppFeature.
Position
Below the diagonal: Modules~XcodeCleaner uses a module listed above it, which is the healthy direction.
32→34 Modules~XcodeCleaner uses Modules~Aphroditepart of a loop✕
Connections
3 pairs of types, where a type in Modules~XcodeCleaner uses a type in Modules~Aphrodite.
Modules~XcodeCleaner uses Modules~Aphrodite, so a change to Modules~Aphrodite can break Modules~XcodeCleaner, while a change to Modules~XcodeCleaner can't break Modules~Aphrodite.
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.
repository uses Modules~Extensions, so a change to Modules~Extensions can break repository, while a change to repository can't break Modules~Extensions.
Position
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
repository uses Modules~PrivilegedHelperCore, so a change to Modules~PrivilegedHelperCore can break repository, while a change to repository can't break Modules~PrivilegedHelperCore.
Position
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
repository uses Modules~AppFeature, so a change to Modules~AppFeature can break repository, while a change to repository can't break Modules~AppFeature.
Position
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
Modules~Aphrodite uses Modules~DisplayBrightness, so a change to Modules~DisplayBrightness can break Modules~Aphrodite, while a change to Modules~Aphrodite can't break Modules~DisplayBrightness.
Position
Below the diagonal: Modules~Aphrodite uses a module listed above it, which is the healthy direction.
Modules~Aphrodite uses Modules~RemoteCore, so a change to Modules~RemoteCore can break Modules~Aphrodite, while a change to Modules~Aphrodite can't break Modules~RemoteCore.
Position
Below the diagonal: Modules~Aphrodite uses a module listed above it, which is the healthy direction.
Modules~Aphrodite uses Modules~RemoteTransport, so a change to Modules~RemoteTransport can break Modules~Aphrodite, while a change to Modules~Aphrodite can't break Modules~RemoteTransport.
Position
Below the diagonal: Modules~Aphrodite uses a module listed above it, which is the healthy direction.
Modules~Aphrodite uses Modules~OnlyAgent, so a change to Modules~OnlyAgent can break Modules~Aphrodite, while a change to Modules~Aphrodite can't break Modules~OnlyAgent.
Position
Below the diagonal: Modules~Aphrodite uses a module listed above it, which is the healthy direction.
Modules~Aphrodite uses Modules~OnlyRemoteFeature, so a change to Modules~OnlyRemoteFeature can break Modules~Aphrodite, while a change to Modules~Aphrodite can't break Modules~OnlyRemoteFeature.
Position
Below the diagonal: Modules~Aphrodite uses a module listed above it, which is the healthy direction.
Modules~Aphrodite uses Modules~DesktopPet, so a change to Modules~DesktopPet can break Modules~Aphrodite, while a change to Modules~Aphrodite can't break Modules~DesktopPet.
Position
Below the diagonal: Modules~Aphrodite uses a module listed above it, which is the healthy direction.
Modules~Aphrodite uses Modules~Extensions, so a change to Modules~Extensions can break Modules~Aphrodite, while a change to Modules~Aphrodite can't break Modules~Extensions.
Position
Below the diagonal: Modules~Aphrodite uses a module listed above it, which is the healthy direction.
Modules~Aphrodite uses Modules~Design, so a change to Modules~Design can break Modules~Aphrodite, while a change to Modules~Aphrodite can't break Modules~Design.
Position
Below the diagonal: Modules~Aphrodite uses a module listed above it, which is the healthy direction.
Modules~Aphrodite uses Modules~AppUninstaller, so a change to Modules~AppUninstaller can break Modules~Aphrodite, while a change to Modules~Aphrodite can't break Modules~AppUninstaller.
Position
Below the diagonal: Modules~Aphrodite uses a module listed above it, which is the healthy direction.
Modules~Aphrodite uses Modules~RadioBrowser, so a change to Modules~RadioBrowser can break Modules~Aphrodite, while a change to Modules~Aphrodite can't break Modules~RadioBrowser.
Position
Below the diagonal: Modules~Aphrodite uses a module listed above it, which is the healthy direction.
Modules~Aphrodite uses Modules~Scheduler, so a change to Modules~Scheduler can break Modules~Aphrodite, while a change to Modules~Aphrodite can't break Modules~Scheduler.
Position
Below the diagonal: Modules~Aphrodite uses a module listed above it, which is the healthy direction.
Modules~Aphrodite uses Modules~Screenshots, so a change to Modules~Screenshots can break Modules~Aphrodite, while a change to Modules~Aphrodite can't break Modules~Screenshots.
Position
Below the diagonal: Modules~Aphrodite uses a module listed above it, which is the healthy direction.
Modules~Aphrodite uses Modules~SystemMonitor, so a change to Modules~SystemMonitor can break Modules~Aphrodite, while a change to Modules~Aphrodite can't break Modules~SystemMonitor.
Position
Below the diagonal: Modules~Aphrodite uses a module listed above it, which is the healthy direction.
Modules~Aphrodite uses Modules~Tailscale, so a change to Modules~Tailscale can break Modules~Aphrodite, while a change to Modules~Aphrodite can't break Modules~Tailscale.
Position
Below the diagonal: Modules~Aphrodite uses a module listed above it, which is the healthy direction.
Modules~Aphrodite uses Modules~SoundMixerEQ, so a change to Modules~SoundMixerEQ can break Modules~Aphrodite, while a change to Modules~Aphrodite can't break Modules~SoundMixerEQ.
Position
Below the diagonal: Modules~Aphrodite uses a module listed above it, which is the healthy direction.
Modules~Aphrodite uses Modules~AppFeature, so a change to Modules~AppFeature can break Modules~Aphrodite, while a change to Modules~Aphrodite can't break Modules~AppFeature.
Position
Below the diagonal: Modules~Aphrodite uses a module listed above it, which is the healthy direction.
Modules~Aphrodite uses Modules~WebBrowser, so a change to Modules~WebBrowser can break Modules~Aphrodite, while a change to Modules~Aphrodite can't break Modules~WebBrowser.
Position
Below the diagonal: Modules~Aphrodite uses a module listed above it, which is the healthy direction.
Modules~Aphrodite uses Modules~XcodeCleaner, so a change to Modules~XcodeCleaner can break Modules~Aphrodite, while a change to Modules~Aphrodite can't break Modules~XcodeCleaner.
Position
Below the diagonal: Modules~Aphrodite uses a module listed above it, which is the healthy direction.
Modules~OnlyControl uses Modules~RemoteTransport, so a change to Modules~RemoteTransport can break Modules~OnlyControl, while a change to Modules~OnlyControl can't break Modules~RemoteTransport.
Position
Below the diagonal: Modules~OnlyControl uses a module listed above it, which is the healthy direction.
Modules~OnlyControl uses Modules~Extensions, so a change to Modules~Extensions can break Modules~OnlyControl, while a change to Modules~OnlyControl can't break Modules~Extensions.
Position
Below the diagonal: Modules~OnlyControl uses a module listed above it, which is the healthy direction.
Modules~OnlyControl uses Modules~Design, so a change to Modules~Design can break Modules~OnlyControl, while a change to Modules~OnlyControl can't break Modules~Design.
Position
Below the diagonal: Modules~OnlyControl uses a module listed above it, which is the healthy direction.
Modules~OnlyControl uses Modules~Defines, so a change to Modules~Defines can break Modules~OnlyControl, while a change to Modules~OnlyControl can't break Modules~Defines.
Position
Below the diagonal: Modules~OnlyControl uses a module listed above it, which is the healthy direction.
Modules~OnlyControl uses Modules~Switches, so a change to Modules~Switches can break Modules~OnlyControl, while a change to Modules~OnlyControl can't break Modules~Switches.
Position
Below the diagonal: Modules~OnlyControl uses a module listed above it, which is the healthy direction.
Modules~OnlyControl uses Modules~Aphrodite, so a change to Modules~Aphrodite can break Modules~OnlyControl, while a change to Modules~OnlyControl can't break Modules~Aphrodite.
Position
Below the diagonal: Modules~OnlyControl uses a module listed above it, which is the healthy direction.
Modules~OnlyWidgetFeature uses Modules~Extensions, so a change to Modules~Extensions can break Modules~OnlyWidgetFeature, while a change to Modules~OnlyWidgetFeature can't break Modules~Extensions.
Position
Below the diagonal: Modules~OnlyWidgetFeature uses a module listed above it, which is the healthy direction.
Modules~OnlyWidgetFeature uses Modules~Design, so a change to Modules~Design can break Modules~OnlyWidgetFeature, while a change to Modules~OnlyWidgetFeature can't break Modules~Design.
Position
Below the diagonal: Modules~OnlyWidgetFeature uses a module listed above it, which is the healthy direction.
Modules~OnlyWidgetFeature uses Modules~Defines, so a change to Modules~Defines can break Modules~OnlyWidgetFeature, while a change to Modules~OnlyWidgetFeature can't break Modules~Defines.
Position
Below the diagonal: Modules~OnlyWidgetFeature uses a module listed above it, which is the healthy direction.
Modules~OnlyWidgetFeature uses Modules~Switches, so a change to Modules~Switches can break Modules~OnlyWidgetFeature, while a change to Modules~OnlyWidgetFeature can't break Modules~Switches.
Position
Below the diagonal: Modules~OnlyWidgetFeature uses a module listed above it, which is the healthy direction.
Modules~OnlyWidgetFeature uses Modules~XcodeCleaner, so a change to Modules~XcodeCleaner can break Modules~OnlyWidgetFeature, while a change to Modules~OnlyWidgetFeature can't break Modules~XcodeCleaner.
Position
Below the diagonal: Modules~OnlyWidgetFeature uses a module listed above it, which is the healthy direction.
Modules~OnlyWidgetFeature uses Modules~Aphrodite, so a change to Modules~Aphrodite can break Modules~OnlyWidgetFeature, while a change to Modules~OnlyWidgetFeature can't break Modules~Aphrodite.
Position
Below the diagonal: Modules~OnlyWidgetFeature uses a module listed above it, which is the healthy direction.
Modules~PureColorView uses Modules~Extensions, so a change to Modules~Extensions can break Modules~PureColorView, while a change to Modules~PureColorView can't break Modules~Extensions.
Position
Below the diagonal: Modules~PureColorView uses a module listed above it, which is the healthy direction.
Modules~PureColorView uses Modules~Aphrodite, so a change to Modules~Aphrodite can break Modules~PureColorView, while a change to Modules~PureColorView can't break Modules~Aphrodite.
Position
Below the diagonal: Modules~PureColorView uses a module listed above it, which is the healthy direction.
Modules~Reorderable uses Modules~Extensions, so a change to Modules~Extensions can break Modules~Reorderable, while a change to Modules~Reorderable can't break Modules~Extensions.
Position
Below the diagonal: Modules~Reorderable uses a module listed above it, which is the healthy direction.
Modules~Reorderable uses Modules~Aphrodite, so a change to Modules~Aphrodite can break Modules~Reorderable, while a change to Modules~Reorderable can't break Modules~Aphrodite.
Position
Below the diagonal: Modules~Reorderable uses a module listed above it, which is the healthy direction.
Modules~ScriptEditor uses Modules~Extensions, so a change to Modules~Extensions can break Modules~ScriptEditor, while a change to Modules~ScriptEditor can't break Modules~Extensions.
Position
Below the diagonal: Modules~ScriptEditor uses a module listed above it, which is the healthy direction.
Modules~ScriptEditor uses Modules~Design, so a change to Modules~Design can break Modules~ScriptEditor, while a change to Modules~ScriptEditor can't break Modules~Design.
Position
Below the diagonal: Modules~ScriptEditor uses a module listed above it, which is the healthy direction.
Modules~ScriptEditor uses Modules~Defines, so a change to Modules~Defines can break Modules~ScriptEditor, while a change to Modules~ScriptEditor can't break Modules~Defines.
Position
Below the diagonal: Modules~ScriptEditor uses a module listed above it, which is the healthy direction.
Modules~ScriptEditor uses Modules~Aphrodite, so a change to Modules~Aphrodite can break Modules~ScriptEditor, while a change to Modules~ScriptEditor can't break Modules~Aphrodite.
Position
Below the diagonal: Modules~ScriptEditor uses a module listed above it, which is the healthy direction.
Top priorities: Resolve the 1 Assertions commented out finding(s) in Test Quality — start with OnlySwitchTests.swift; Add a CI workflow that builds and runs the test suite on every push/PR; Resolve the 224 No assertions finding(s) in Test Quality — start with RemoteScreenshotsFeatureTests.swift (22), EverySwitchTests.swift (17), RemoteAppFeatureTests.swift (17).
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 Assertions commented out finding(s) in Test Quality — start with OnlySwitchTests.swift.
Resolve the 224 No assertions finding(s) in Test Quality — start with RemoteScreenshotsFeatureTests.swift (22), EverySwitchTests.swift (17), RemoteAppFeatureTests.swift (17).
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Swift: await instead of blocking — `try await Task.sleep(for:)` for Thread.sleep/sleep, a checked continuation instead of a DispatchSemaphore or DispatchGroup wait, the async Process and URLSession APIs; never park a thread waiting on a Task — the cooperative pool cannot guarantee it progress.
Test Quality: No assertions: changingMacDuringTheTransferHoldTearsDownImmediately
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 — 45
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 — 965
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 — 82
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 29
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 47 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, 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 — 47 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, 1042 of 1092 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.
D8 Code Coverage — 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. Coverage NOT MEASURED: the Swift half could not be measured — the Swift suite in Modules produced no coverage export. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
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 source is present (.swift) and this repository declares a SwiftPM test suite (Modules), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D16 Bus Factor — 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. Single-maintainer repository — bus factor is not applicable (33 contributor(s) across 1461 commit(s) sampled, automation and bot accounts excluded). One of them holds 90% of the history; the other 32 hold 0.3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D19 Documentation Quality — 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 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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
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.
D24 Comment Value — 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. 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.
D26 Project Cohesion — 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. `Modules` (93708 LoC, 1777 module-visible types across 134 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
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. `Modules/Sources/Aphrodite/AphroditeApp.swift`, `Modules/Sources/Aphrodite/AphroditeIconValidation.swift`, `Modules/Sources/Aphrodite/AphroditeReducer.swift`, `Modules/Sources/AppFeature/EverySwitch/ReverseScrollDirectionSwitch.swift`, `Modules/Sources/AppFeature/Features/DockPreview/DockPreviewClient.swift`, … (+70 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.
D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
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 reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is swift-dependencies, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AX6 Interface segregation — 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 7 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
C1 Data Protection — 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. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — 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. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — 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. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
DM2 Strongly-typed ids — 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. 204 further occurrence(s) are not listed individually; the score already reflects all 244.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Swift, c, objectivec is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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 reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Swift, c, objectivec is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
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.
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.
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.
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.
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.
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. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's C, Objective-C is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 35 further occurrence(s) are not listed individually; the score already reflects all 75.
X30 Support guard that admits what it rejects — 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.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's C, Objectivec, Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
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.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
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.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
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.
DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
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.
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.
147 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was AphroditeReducer.body at 102. A further 9 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 RemoteMessage.init at 54 — they are counted neither in the figure above nor in this dimension's score. 6 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: Modules/Sources/RemoteCore/RemoteMessage.swift (RemoteMessage.init at 54), Modules/Sources/AppFeature/EverySwitch/SwitchType++.swift (SwitchType.getNewSwitchInstance at 50), Modules/Sources/Switches/SwitchType+BarInfo.swift (SwitchType.barInfo at 50), Modules/Sources/Switches/SwitchType.swift (SwitchType.legacyIdentifier at 50), Modules/Sources/AppFeature/Features/RemoteAccess/Catalog/RemoteIconAdapter.swift (RemoteIconAdapter.symbolName at 39), and 1 more not listed here. 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.
+ 129 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 6 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with AphroditeReducer.body (cyclomatic 102), overrideInlineStyle (cyclomatic 86), RemoteScreenshotsFeature.body (cyclomatic 74). — 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 6 together lifts Cyclomatic Complexity from 6.0 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.
+ 181 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with overrideInlineStyle (cognitive 131). — Refactoring it lifts Cognitive Complexity from 4.8 to about 5.0/10.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.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 28 MethodTooLong finding(s) in God Classes — start with RemoteMessage.swift (2), SwitchType+BarInfo.swift, AphroditeReducer.swift. — One of this dimension's main actionable groups (28 warning-level).
Resolve the 10 TooManyMethods finding(s) in God Classes — start with RemoteConnectionRuntime.swift, RemoteReviewDemoClient.swift, RemotePeerSession.swift. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 2 FileTooLong finding(s) in God Classes — start with DarkReader.js, 2026-10-30.html. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
101 duplicated block group(s) detected. 6.5 % of the production lines (5,535 of 85,644) are in a reported copy. A further 158 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
+ 91 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 12 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with RemoteScreenshotCell.swift (2), ClaudeUsageModels.swift (2), OnlyControlView.swift. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 10 Edited copy of a member (4 corresponding lines) finding(s) in Code Duplication — start with AphroditeRemoteModels.swift, RemotePeerSession.swift, AppUninstallerView.swift. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 9 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with RemoteClaudeUsageView.swift, SoundMixerService.swift, CodexAppServerClient.swift. — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling7.9 / 10Strong✓ 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.
36 production modules (SwiftPM), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; 8 module(s) off the main sequence, with abstractness counted on 34 of the 36 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: Design · ×8
Unstable project OnlyControl
What to do
Resolve the 8 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 1 Unstable project OnlyControl finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 40 Low cohesion finding(s) in Cohesion (LCOM4) — start with RollingText.swift, RemoteConnectionRuntime.swift, BrowserWebViewDelegate.swift. — One of this dimension's main actionable groups (40 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality8.6 / 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.
8 skipped (8 with a documented reason), 225 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 2386 tests.
Resolve the 1 Assertions commented out finding(s) in Test Quality — start with OnlySwitchTests.swift. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 224 No assertions finding(s) in Test Quality — start with RemoteScreenshotsFeatureTests.swift (22), EverySwitchTests.swift (17), RemoteAppFeatureTests.swift (17). — One of this dimension's main actionable groups (224 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
40 outdated direct SwiftPM dependencies, 0 pinning defect(s). 54 of 58 direct dependencies had their releases listed (0 naming no readable repository, 4 pinned to a branch or a revision rather than a version). SwiftPM has no package registry: a dependency is a repository URL and its releases are that repository's semver tags, so currency is answered by listing tags rather than by querying an index. Only a newer tag on the SAME MAJOR is reported — a `from:` requirement admits everything below the next major and nothing above it, so a major crossing needs a Package.swift edit rather than an update, and naming the update as its remedy would be wrong. Whether any dependency is DEPRECATED or ABANDONED is not graded and cannot be: a repository publishes no such marker, and there is no registry that could carry one. Known CVEs in this dependency graph are D30's question.
Outdated: abseil-cpp-binary · ×36
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 42 SwiftPM package(s) use a banned license. SwiftPM has no package registry, so each package's licence is the one its repository declares: 40 of them read from the licence file the repository carries at the revision Package.resolved pins, and 2 — unpinned, or whose licence file could not be read or named — from api.deps.dev, which reports the licence the repository declares today. Graded: every package a committed Package.resolved pins, direct and transitive, and every declared dependency none pins. 2 of them declare no licence that matches a known SPDX licence; that is missing data, not a violation, and none of them is charged.
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 30 Hotspot finding(s) in Churn × Complexity Hotspots — start with RemoteAppFeature.swift, OnlySwitchListView.swift, SettingsView.swift. — One of this dimension's main actionable groups (30 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
0 deducted task-comment markers across 85644 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
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.
9 % of calls cross a namespace and 5 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
semgrep found no security issues. semgrep hit a parse error in 11 file(s) — `Modules/Sources/AppFeature/EverySwitch/ReverseScrollDirectionSwitch.swift` (line 179), `Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerVM.swift` (line 88, line 121, line 122), `Modules/Sources/AppFeature/Player/MusicAppPlayer/AppleMusic/iTunesBridge/ObjC/iTunes.h` (line 9, line 147, line 149, …), `Modules/Sources/AppFeature/StatusBar/StatusBarController.swift` (line 270), `Modules/Sources/WebBrowser/Resources/DarkReader.js`, … (+6 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.
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.
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.
9 of 461 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Modules/Sources/Authenticator/OtpAuthImport.swift. Counted over 461 of the 915 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 1 Change coupling finding(s) in Change Coupling — start with Preferences.swift. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with RemotePeerSession.swift. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether 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.
No dependency in any ecosystem this repository declares is published as malicious.
✓ On the Gold path — maintain.
Detailed fixes: d43_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives4.8 / 10Weak✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. — Modules/Sources/WebBrowser/Resources/DarkReader.js:3258
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
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.
Other · Domain Modelling — Whether domain identifiers are strongly typed (a typed-id struct) rather than raw primitives — consistency once an idiom exists.
Method: Roslyn (DDD-gated): strongly-typed id adoption on domain entities/events; raw Guid/int/string ids counted versus wrapped types. An id wrapper is recognised by VALUE SEMANTICS, not by being a struct — a record struct, a record class (`record ApartmentId(Guid Value)`) or a class declared by a typed-id base (`class MemberId : TypedIdValueBase`) all count, while a plain mutable class (reference equality) and a verb-phrase query record (`GetCustomerById`) do not. Deterministic, adoption percentage.
Coverage: Population: id-like members by *Id/*Key NAME suffix; strongly-typed-ID shape then checked semantically — non-suffixed identifiers are not seen.
`AphroditeApp.id` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/Aphrodite/AphroditeApp.swift:6
`AphroditeApp.conversationID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/Aphrodite/AphroditeApp.swift:10
`AphroditeConversationTurn.id` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/Aphrodite/AphroditeApp.swift:42
`AphroditeAppOrigin.appID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/Aphrodite/AphroditeAppOrigin.swift:6
`AphroditeGeneratedDocumentSchemeHandler.appID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/Aphrodite/AphroditeGeneratedDocumentSchemeHandler.swift:9
`AphroditeEditOperation.taskID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/Aphrodite/AphroditeReducer.swift:7
`AphroditeEditOperation.appID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/Aphrodite/AphroditeReducer.swift:8
`State.selectedAppID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/Aphrodite/AphroditeReducer.swift:26
`State.editingAppID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/Aphrodite/AphroditeReducer.swift:27
`State.activeGenerationID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/Aphrodite/AphroditeReducer.swift:30
`ScrollWheelEventTraits.tabletDeviceID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/EverySwitch/ReverseScrollDirectionSwitch.swift:13
`StickerWindow.stickerId` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/EverySwitch/TopStickerSwitch.swift:162
`AdsModel.id` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Model/AdsModel.swift:16
`ReleaseAssets.id` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Model/GitHubReleaseModel.swift:12
`GitHubRelease.id` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Model/GitHubReleaseModel.swift:44
`Metadata.bundleID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Features/CrashReports/CrashReportDiscovery.swift:10
`SecondaryInformationRequest.id` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Features/OnlyControl/OnlyControlReducer.swift:369
`OwnPlaybackSource.rowID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Features/SoundMixer/OwnPlaybackSource.swift:15
`ScriptableAudioApp.bundleID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerModel.swift:18
`ScriptableAudioApp.id` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerModel.swift:24
`Row.id` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerRemoteBridge.swift:15
`AppRow.id` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerVM.swift:35
`AudioApp.bundleID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer.swift:16
`Configuration.ownerBundleID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer.swift:38
`HostedAudioPlayer.playbackID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Player/CommonPlayer/HostedAudioPlayer.swift:20
`PlaybackHelperEngine.playbackID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Player/CommonPlayer/PlaybackHelperEngine.swift:16
`PlaybackHelperCommand.playbackID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Player/CommonPlayer/PlaybackHelperProtocol.swift:12
`PlaybackHelperEvent.playbackID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Player/CommonPlayer/PlaybackHelperProtocol.swift:21
`RadioPlayerItem.id` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Player/RadioPlayerItem/RadioPlayerItem.swift:41
`RemoteCatalogMonitor.activeRefreshID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteCatalogMonitor.swift:24
`PairedRemoteDevice.id` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteCredentialStore.swift:8
`RemoteProvisionalPairingContext.transactionID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteCredentialStore.swift:16
`RemoteCredentialStore.memoryInstallationID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteCredentialStore.swift:76
`PreparedReplacement.transactionID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteCredentialStore.swift:48
`RemotePairingSnapshot.deviceID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteHostLifecycle.swift:4
`RemotePeerSession.id` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession.swift:29
`RemotePeerSession.macID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession.swift:31
`PendingPairing.transactionID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession.swift:14
`Device.id` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Features/RemoteAccess/Settings/RemoteAccessSettingsFeature.swift:10
`State.selectedID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value. — Modules/Sources/AppFeature/Features/Settings/DesktopPet/DesktopPetSkinsFeature.swift:15
What to do
Adopt the repo's typed-id idiom consistently — wrap every entity identity in its own typed id.
Do you agree with this assessment?
DM4 · Rich vs anemic domain model7.7 / 10Strong✓ Tool-verified
Other · Domain Modelling — Whether domain entities own their behaviour — a data-only reference entity whose logic lives in a foreign service is anemic. Rich models enforce their own invariants.
Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.
Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.
`CGRect` is a data-only reference entity whose behaviour is DELEGATED to a foreign utility (static methods that take it as their first parameter and hold its logic) — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants rather than being driven from outside. — Modules/Sources/DesktopPet/DesktopPetLayout.swift:97
`Int` is a data-only reference entity whose behaviour is DELEGATED to a foreign utility (static methods that take it as their first parameter and hold its logic) — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants rather than being driven from outside. — Modules/Sources/Extensions/IntBool.swift:15
What to do
Move delegated behaviour onto the domain entity (or make it a value object); keep invariants inside the type.
Other · Domain Modelling — Whether a reference entity protects its own invariants — a class whose identity is a computed content hash but whose hashed fields are publicly mutable bypasses that invariant. Encapsulated state keeps identity-bearing fields immutable.
Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.
Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain entity fused to a persistence ORM on its own declaration (active-record), or reaching a web-framework transport type in its own method, couples the domain to infrastructure. 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 · Event-Driven — Whether state changes and message publishes are atomic (a transactional outbox) rather than a crash-unsafe dual write.
Method: Roslyn semantic scan (event-driven gated): event-handler methods scanned for DB-save plus bus-publish without a transactional outbox reference. Deterministic, semantic-resolved.
`RemoteKeychainClient.client` performs two independent DURABLE writes — `store` (a persistence store) via `save` and `provisional` (a persistence store) via `save` — in one command path with no shared transaction or outbox. A crash between the two leaves the stores diverged (one write committed, the other lost) or emits a phantom record. Wrap both in one transaction, or record the second write in the same store and dispatch it afterwards (a transactional outbox). — Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteKeychainClient.swift:140
What to do
Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Do you agree with this assessment?
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified
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.
No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
Add a CI workflow that builds and runs the test suite on every push/PR.
Do you agree with this assessment?
P10 · Library API & versioning6.0 / 10Adequate✓ 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.
No explicit version was found for the SwiftPM library declared by `Package.swift`. This check read nothing in Package.swift, which has no version field, and a CHANGELOG/CHANGES/HISTORY/NEWS/RELEASES file with a semver heading, or release tooling (changesets, release-please, semantic-release, goreleaser, cargo-release, bump2version, standard-version, git-cliff) in the library's directory or at the repository root, or a semver release tag (or a Drupal `8.x-1.2` release tag) in the repository. A version computed where none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes. — Modules/Package.swift
What to do
Declare the version where the ecosystem expects it, or keep a CHANGELOG with semver release headings, and follow semver for breaking changes.
Do you agree with this assessment?
P2 · Observability5.5 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
Run what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
`sleep` is async and calls sleep — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs. — Modules/Sources/Extensions/Task++.swift:11
`runShell` is async and calls .wait() — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs. — Modules/Sources/OnlyAgent/Conversation/AgentScriptRunner.swift:57
What to do
Swift: await instead of blocking — `try await Task.sleep(for:)` for Thread.sleep/sleep, a checked continuation instead of a DispatchSemaphore or DispatchGroup wait, the async Process and URLSession APIs; never park a thread waiting on a Task — the cooperative pool cannot guarantee it progress.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×10) — Modules/Sources/WebBrowser/Resources/DarkReader.js:2811, Modules/Sources/WebBrowser/Resources/DarkReader.js:2846, Modules/Sources/WebBrowser/Resources/DarkReader.js:2852, …
`catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×30) — Modules/Sources/Tailscale/TailscaleCoordinator.swift:126, Modules/Sources/Screenshots/ScreenshotFolderWatcher.swift:187, Modules/Sources/Screenshots/WindowFrameReader.swift:50, …
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 42 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 15 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X6 Hand-rolled structured-format parsing — 3 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 — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 69 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.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D11 Test Reliability — Test reliability not included — the .swift suite was found but not re-run
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D19 Documentation Quality — D19 withholds "Documentation: empty section": 2 candidate(s) were measured and not published.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Swift surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .swift source were not judged.
D25 ADR Conformance — no ADRs to check
D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 75 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
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.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — Swift suite
DM1 Aggregate boundaries — not scored for Swift: the sidecar flattens array/collection types (a child COLLECTION = legitimate membership vs a single embedded aggregate is indistinguishable), and aggregate-vs-value-object classification cannot be told apart in source (every struct-holding-struct reads alike) — reported as guidance rather than measured
DM3 Integration-event coupling — not scored for Swift: a cross-SwiftPM-target domain leak cannot be told apart in source from a legitimate shared-kernel/contracts module, and most repositories ship a single module — reported as guidance rather than measured
DM7 Repository granularity — not scored for Swift: 'a repository per CHILD entity' needs the aggregate-root structure, which is not source-resolvable — reported as guidance rather than measured
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down 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
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — no CI workflow found
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Swift source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `Benchmark("…")` in a file importing package-benchmark, or package-benchmark in Package.swift, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — X1 reached only 12% of this repository's production lines — swift (84,197 lines), c (964 lines), objectivec (443 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 12% of this repository's production lines — swift (84,197 lines), c (964 lines), objectivec (443 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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 12% of this repository's production lines — swift (84,197 lines), c (964 lines), objectivec (443 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — X2 reached only 12% of this repository's production lines — swift (84,197 lines), c (964 lines), objectivec (443 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X21 Side-effecting pattern guard — X21 reached only 12% of this repository's production lines — swift (84,197 lines), c (964 lines), objectivec (443 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — X24 reached only 12% of this repository's production lines — swift (84,197 lines), c (964 lines), objectivec (443 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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
X27 Collection changed while being enumerated — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X29 Per-element action decided by a fixed element — X29 reached only 12% of this repository's production lines — swift (84,197 lines), c (964 lines), objectivec (443 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 — X30 reached only 12% of this repository's production lines — swift (84,197 lines), c (964 lines), objectivec (443 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Critical — 45 finding(s)
DM2 · Strongly-typed ids· Raw-primitive id despite a typed-id idiom · ×40
Raw-primitive id despite a typed-id idiom: AphroditeApp.id Modules/Sources/Aphrodite/AphroditeApp.swift:6— `AphroditeApp.id` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value.
Raw-primitive id despite a typed-id idiom: AphroditeApp.conversationID Modules/Sources/Aphrodite/AphroditeApp.swift:10— `AphroditeApp.conversationID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value.
Raw-primitive id despite a typed-id idiom: AphroditeConversationTurn.id Modules/Sources/Aphrodite/AphroditeApp.swift:42— `AphroditeConversationTurn.id` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value.
Raw-primitive id despite a typed-id idiom: AphroditeAppOrigin.appID Modules/Sources/Aphrodite/AphroditeAppOrigin.swift:6— `AphroditeAppOrigin.appID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value.
Raw-primitive id despite a typed-id idiom: AphroditeGeneratedDocumentSchemeHandler.appID Modules/Sources/Aphrodite/AphroditeGeneratedDocumentSchemeHandler.swift:9— `AphroditeGeneratedDocumentSchemeHandler.appID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value.
Raw-primitive id despite a typed-id idiom: AphroditeEditOperation.taskID Modules/Sources/Aphrodite/AphroditeReducer.swift:7— `AphroditeEditOperation.taskID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value.
Raw-primitive id despite a typed-id idiom: AphroditeEditOperation.appID Modules/Sources/Aphrodite/AphroditeReducer.swift:8— `AphroditeEditOperation.appID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value.
Raw-primitive id despite a typed-id idiom: State.selectedAppID Modules/Sources/Aphrodite/AphroditeReducer.swift:26— `State.selectedAppID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value.
Raw-primitive id despite a typed-id idiom: State.editingAppID Modules/Sources/Aphrodite/AphroditeReducer.swift:27— `State.editingAppID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value.
Raw-primitive id despite a typed-id idiom: State.activeGenerationID Modules/Sources/Aphrodite/AphroditeReducer.swift:30— `State.activeGenerationID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value.
Raw-primitive id despite a typed-id idiom: ScrollWheelEventTraits.tabletDeviceID Modules/Sources/AppFeature/EverySwitch/ReverseScrollDirectionSwitch.swift:13— `ScrollWheelEventTraits.tabletDeviceID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value.
Raw-primitive id despite a typed-id idiom: StickerWindow.stickerId Modules/Sources/AppFeature/EverySwitch/TopStickerSwitch.swift:162— `StickerWindow.stickerId` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value.
Raw-primitive id despite a typed-id idiom: AdsModel.id Modules/Sources/AppFeature/Model/AdsModel.swift:16— `AdsModel.id` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value.
Raw-primitive id despite a typed-id idiom: ReleaseAssets.id Modules/Sources/AppFeature/Model/GitHubReleaseModel.swift:12— `ReleaseAssets.id` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value.
Raw-primitive id despite a typed-id idiom: GitHubRelease.id Modules/Sources/AppFeature/Model/GitHubReleaseModel.swift:44— `GitHubRelease.id` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value.
Raw-primitive id despite a typed-id idiom: Metadata.bundleID Modules/Sources/AppFeature/Features/CrashReports/CrashReportDiscovery.swift:10— `Metadata.bundleID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value.
Raw-primitive id despite a typed-id idiom: SecondaryInformationRequest.id Modules/Sources/AppFeature/Features/OnlyControl/OnlyControlReducer.swift:369— `SecondaryInformationRequest.id` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value.
Raw-primitive id despite a typed-id idiom: OwnPlaybackSource.rowID Modules/Sources/AppFeature/Features/SoundMixer/OwnPlaybackSource.swift:15— `OwnPlaybackSource.rowID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value.
Raw-primitive id despite a typed-id idiom: ScriptableAudioApp.bundleID Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerModel.swift:18— `ScriptableAudioApp.bundleID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value.
Raw-primitive id despite a typed-id idiom: ScriptableAudioApp.id Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerModel.swift:24— `ScriptableAudioApp.id` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value.
Raw-primitive id despite a typed-id idiom: Row.id Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerRemoteBridge.swift:15— `Row.id` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value.
Raw-primitive id despite a typed-id idiom: AppRow.id Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerVM.swift:35— `AppRow.id` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value.
Raw-primitive id despite a typed-id idiom: AudioApp.bundleID Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer.swift:16— `AudioApp.bundleID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value.
Raw-primitive id despite a typed-id idiom: Configuration.ownerBundleID Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer.swift:38— `Configuration.ownerBundleID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value.
Raw-primitive id despite a typed-id idiom: HostedAudioPlayer.playbackID Modules/Sources/AppFeature/Player/CommonPlayer/HostedAudioPlayer.swift:20— `HostedAudioPlayer.playbackID` is a raw primitive id while the repo already defines typed-id wrappers — an inconsistently-adopted typed-id idiom. Give this identity its own typed id so it can't be confused with another entity's id or a plain value.
+ 15 more in this group — see findings.md.
DM4 · Rich vs anemic domain model· Anemic domain model · ×2
Anemic domain model: CGRect Modules/Sources/DesktopPet/DesktopPetLayout.swift:97— `CGRect` is a data-only reference entity whose behaviour is DELEGATED to a foreign utility (static methods that take it as their first parameter and hold its logic) — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants rather than being driven from outside.
Anemic domain model: Int Modules/Sources/Extensions/IntBool.swift:15— `Int` is a data-only reference entity whose behaviour is DELEGATED to a foreign utility (static methods that take it as their first parameter and hold its logic) — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants rather than being driven from outside.
AC1 · Text alternatives· <img> without a text alternative · ×1
<img> without a text alternative Modules/Sources/WebBrowser/Resources/DarkReader.js:3258— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
Assertions commented out: testExample Modules/Tests/AppFeatureTests/OnlySwitchTests.swift:32— 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.
Dual write (no outbox): RemoteKeychainClient.client Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteKeychainClient.swift:140— `RemoteKeychainClient.client` performs two independent DURABLE writes — `store` (a persistence store) via `save` and `provisional` (a persistence store) via `save` — in one command path with no shared transaction or outbox. A crash between the two leaves the stores diverged (one write committed, the other lost) or emits a phantom record. Wrap both in one transaction, or record the second write in the same store and dispatch it afterwards (a transactional outbox).
No assertions: hidingSelectedUninstallerReturnsOnlyControlToControls Modules/Tests/AppFeatureTests/AppUninstallerSwitchTests.swift:80— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, 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: cancellingManualRefreshClearsKeychainHint Modules/Tests/AppFeatureTests/ClaudeUsageIntegrationTests.swift:368— 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: failedSignInIsShownWithoutTouchingUsage Modules/Tests/AppFeatureTests/ClaudeUsageIntegrationTests.swift:422— 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: testDarkModeSwitch Modules/Tests/AppFeatureTests/EverySwitchTests.swift:13— 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: testHiddenDesktopSwitch Modules/Tests/AppFeatureTests/EverySwitchTests.swift:18— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, 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: testTopNotchSwitch Modules/Tests/AppFeatureTests/EverySwitchTests.swift:23— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, 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: testMuteSwitch Modules/Tests/AppFeatureTests/EverySwitchTests.swift:28— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, 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: testScreenSaverSwitch Modules/Tests/AppFeatureTests/EverySwitchTests.swift:33— 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: testNightShiftSwitch Modules/Tests/AppFeatureTests/EverySwitchTests.swift:38— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testAutohideDockSwitch Modules/Tests/AppFeatureTests/EverySwitchTests.swift:43— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, 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: testAutohideMenuBarSwitch Modules/Tests/AppFeatureTests/EverySwitchTests.swift:59— 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: testHiddenFilesSwitch Modules/Tests/AppFeatureTests/EverySwitchTests.swift:64— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, 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: testKeepAwakeSwitch Modules/Tests/AppFeatureTests/EverySwitchTests.swift:69— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, 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: testShowUserLibrarySwitch Modules/Tests/AppFeatureTests/EverySwitchTests.swift:79— 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: testShowExtensionNameSwitch Modules/Tests/AppFeatureTests/EverySwitchTests.swift:84— 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: testSmallLaunchpadIconSwitch Modules/Tests/AppFeatureTests/EverySwitchTests.swift:89— 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: testLowPowerModeSwitch Modules/Tests/AppFeatureTests/EverySwitchTests.swift:94— 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: testMuteMicSwitch Modules/Tests/AppFeatureTests/EverySwitchTests.swift:99— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, 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: testShowFinderPathbarSwitch Modules/Tests/AppFeatureTests/EverySwitchTests.swift:104— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, 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: testDockRecentSwitch Modules/Tests/AppFeatureTests/EverySwitchTests.swift:109— 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: openOnlyAgentIsIgnoredWhenUnavailable Modules/Tests/AppFeatureTests/OnlyAgentEvolutionTests.swift: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: testPerformanceExample Modules/Tests/AppFeatureTests/OnlySwitchTests.swift:170— 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: subsequentCaptureCreatesNewRevealAfterPreviousSelectionWasConsumed Modules/Tests/AppFeatureTests/ScreenshotsSectionTests.swift:168— 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: hidingSelectedBrightnessReturnsOnlyControlToControls Modules/Tests/AppFeatureTests/TabVisibilitySettingsTests.swift:160— 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: hidingSelectedCleanerReturnsOnlyControlToControls Modules/Tests/AppFeatureTests/XcodeCleanerSwitchTests.swift:78— 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.
Low cohesion: String (LCOM4 10) Modules/Sources/Design/RollingText.swift:97— String's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: RemoteConnectionRuntime (LCOM4 8) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime.swift:5— RemoteConnectionRuntime's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: BrowserWebViewDelegate (LCOM4 7) Modules/Sources/WebBrowser/BrowserWebViewDelegate.swift:7— BrowserWebViewDelegate's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: KeepAwakeSwitch (LCOM4 6) Modules/Sources/AppFeature/EverySwitch/KeepAwakeSwitch.swift:15— KeepAwakeSwitch's methods fall into 6 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 6 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: BluetoothDevicesManager (LCOM4 5) Modules/Sources/AppFeature/Utilities/BluetoothDevicesManager.swift:22— BluetoothDevicesManager's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: JLASAudioPlayer (LCOM4 5) Modules/Sources/AppFeature/Player/CommonPlayer/JLASAudioPlayer.swift:19— JLASAudioPlayer's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AppleMusicSwitch (LCOM4 4) Modules/Sources/AppFeature/EverySwitch/AppleMusicSwitch.swift:12— AppleMusicSwitch'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: AutohideDockSwitch (LCOM4 4) Modules/Sources/AppFeature/EverySwitch/AutohideDockSwitch.swift:12— AutohideDockSwitch'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: AutohideMenuBarSwitch (LCOM4 4) Modules/Sources/AppFeature/EverySwitch/AutohideMenuBarSwitch.swift:12— AutohideMenuBarSwitch'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: ClaudeUsageSwitch (LCOM4 4) Modules/Sources/AppFeature/EverySwitch/ClaudeUsageSwitch.swift:12— ClaudeUsageSwitch'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: CodexUsageSwitch (LCOM4 4) Modules/Sources/AppFeature/EverySwitch/CodexUsageSwitch.swift:12— CodexUsageSwitch'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: DarkModeSwitch (LCOM4 4) Modules/Sources/AppFeature/EverySwitch/DarkModeSwitch.swift:12— DarkModeSwitch'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: DesktopPetSwitch (LCOM4 4) Modules/Sources/AppFeature/EverySwitch/DesktopPetSwitch.swift:4— DesktopPetSwitch'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: DockPreviewSwitch (LCOM4 4) Modules/Sources/AppFeature/EverySwitch/DockPreviewSwitch.swift:4— DockPreviewSwitch'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: DockRecentSwitch (LCOM4 4) Modules/Sources/AppFeature/EverySwitch/DockRecentSwitch.swift:12— DockRecentSwitch'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: EjectDiscsSWitch (LCOM4 4) Modules/Sources/AppFeature/EverySwitch/EjectDiscsSwitch.swift:11— EjectDiscsSWitch'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: EmptyPasteboardSwitch (LCOM4 4) Modules/Sources/AppFeature/EverySwitch/EmptyPasteboardSwitch.swift:12— EmptyPasteboardSwitch'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: EmptyTrashSwitch (LCOM4 4) Modules/Sources/AppFeature/EverySwitch/EmptyTrashSwitch.swift:12— EmptyTrashSwitch'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: FKeySwitch (LCOM4 4) Modules/Sources/AppFeature/EverySwitch/FKeySwitch.swift:11— FKeySwitch'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: HiddenDesktopSwitch (LCOM4 4) Modules/Sources/AppFeature/EverySwitch/HiddenDesktopSwitch.swift:14— HiddenDesktopSwitch'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: HiddenFilesSwitch (LCOM4 4) Modules/Sources/AppFeature/EverySwitch/HiddenFilesSwitch.swift:12— HiddenFilesSwitch'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: HideMenubarIconsSwitch (LCOM4 4) Modules/Sources/AppFeature/EverySwitch/HideMenubarIconsSwitch.swift:13— HideMenubarIconsSwitch'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: HideWindowsSwitch (LCOM4 4) Modules/Sources/AppFeature/EverySwitch/HideWindowsSwitch.swift:13— HideWindowsSwitch'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: KeyLightSwitch (LCOM4 4) Modules/Sources/AppFeature/EverySwitch/KeyLightSwitch.swift:12— KeyLightSwitch'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: MuteMicSwitch (LCOM4 4) Modules/Sources/AppFeature/EverySwitch/MuteMicSwitch.swift:12— MuteMicSwitch'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.
Hotspot: Modules/Sources/OnlyRemoteFeature/App/RemoteAppFeature.swift Modules/Sources/OnlyRemoteFeature/App/RemoteAppFeature.swift:178— Modules/Sources/OnlyRemoteFeature/App/RemoteAppFeature.swift changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 57 in RemoteAppFeature.core at line 178. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 22:36:50 +01:00' --until='2026-11-14 22:36:50 +01:00' --full-history --no-merges -- Modules/Sources/OnlyRemoteFeature/App/RemoteAppFeature.swift`: 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: Modules/Sources/AppFeature/Features/OnlySwitchList/OnlySwitchListView.swift Modules/Sources/AppFeature/Features/OnlySwitchList/OnlySwitchListView.swift:77— Modules/Sources/AppFeature/Features/OnlySwitchList/OnlySwitchListView.swift changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in OnlySwitchListView.body at line 77. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 22:36:50 +01:00' --until='2026-11-14 22:36:50 +01:00' --full-history --no-merges -- Modules/Sources/AppFeature/Features/OnlySwitchList/OnlySwitchListView.swift`: 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: Modules/Sources/AppFeature/Features/Settings/SettingsView/SettingsView.swift Modules/Sources/AppFeature/Features/Settings/SettingsView/SettingsView.swift:97— Modules/Sources/AppFeature/Features/Settings/SettingsView/SettingsView.swift changed 20 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in SettingsView.page at line 97. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 22:36:50 +01:00' --until='2026-11-14 22:36:50 +01:00' --full-history --no-merges -- Modules/Sources/AppFeature/Features/Settings/SettingsView/SettingsView.swift`: 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: Modules/Sources/OnlyRemoteFeature/Features/Dashboard/DashboardFeature.swift Modules/Sources/OnlyRemoteFeature/Features/Dashboard/DashboardFeature.swift:141— Modules/Sources/OnlyRemoteFeature/Features/Dashboard/DashboardFeature.swift changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 45 in DashboardFeature.body at line 141. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 22:36:50 +01:00' --until='2026-11-14 22:36:50 +01:00' --full-history --no-merges -- Modules/Sources/OnlyRemoteFeature/Features/Dashboard/DashboardFeature.swift`: 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: Modules/Sources/OnlyRemoteFeature/Features/Settings/SettingsFeature.swift Modules/Sources/OnlyRemoteFeature/Features/Settings/SettingsFeature.swift:96— Modules/Sources/OnlyRemoteFeature/Features/Settings/SettingsFeature.swift changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in SettingsFeature.body at line 96. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 22:36:50 +01:00' --until='2026-11-14 22:36:50 +01:00' --full-history --no-merges -- Modules/Sources/OnlyRemoteFeature/Features/Settings/SettingsFeature.swift`: 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: Modules/Sources/OnlyRemoteFeature/App/RemoteAppView.swift Modules/Sources/OnlyRemoteFeature/App/RemoteAppView.swift:8— Modules/Sources/OnlyRemoteFeature/App/RemoteAppView.swift changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in RemoteAppView.body at line 8. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 22:36:50 +01:00' --until='2026-11-14 22:36:50 +01:00' --full-history --no-merges -- Modules/Sources/OnlyRemoteFeature/App/RemoteAppView.swift`: 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: Modules/Sources/AppFeature/Features/SystemMonitor/MacSystemMonitorCollector.swift Modules/Sources/AppFeature/Features/SystemMonitor/MacSystemMonitorCollector.swift:191— Modules/Sources/AppFeature/Features/SystemMonitor/MacSystemMonitorCollector.swift changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in MacSystemMonitorCollector.sampleForStream at line 191. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 22:36:50 +01:00' --until='2026-11-14 22:36:50 +01:00' --full-history --no-merges -- Modules/Sources/AppFeature/Features/SystemMonitor/MacSystemMonitorCollector.swift`: 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: Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteReviewDemoClient.swift Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteReviewDemoClient.swift:170— Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteReviewDemoClient.swift changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in RemoteReviewDemoRuntime.sendSoundMixer at line 170. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 22:36:50 +01:00' --until='2026-11-14 22:36:50 +01:00' --full-history --no-merges -- Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteReviewDemoClient.swift`: 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: Modules/Sources/AppFeature/EverySwitch/SwitchManager.swift Modules/Sources/AppFeature/EverySwitch/SwitchManager.swift:112— Modules/Sources/AppFeature/EverySwitch/SwitchManager.swift changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in SwitchManager.visibleTypesIncludingNewDiscoveries at line 112. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 22:36:50 +01:00' --until='2026-11-14 22:36:50 +01:00' --full-history --no-merges -- Modules/Sources/AppFeature/EverySwitch/SwitchManager.swift`: 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: Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerVM.swift Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerVM.swift:222— Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerVM.swift changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in SoundMixerVM.refresh at line 222. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 22:36:50 +01:00' --until='2026-11-14 22:36:50 +01:00' --full-history --no-merges -- Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerVM.swift`: 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: Modules/Sources/Aphrodite/AphroditeReducer.swift Modules/Sources/Aphrodite/AphroditeReducer.swift:96— Modules/Sources/Aphrodite/AphroditeReducer.swift changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 102 in AphroditeReducer.body at line 96. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 22:36:50 +01:00' --until='2026-11-14 22:36:50 +01:00' --full-history --no-merges -- Modules/Sources/Aphrodite/AphroditeReducer.swift`: 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: Modules/Sources/OnlyRemoteFeature/Features/Settings/GlobalSettingsFeature.swift Modules/Sources/OnlyRemoteFeature/Features/Settings/GlobalSettingsFeature.swift:75— Modules/Sources/OnlyRemoteFeature/Features/Settings/GlobalSettingsFeature.swift changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in GlobalSettingsFeature.features at line 75. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 22:36:50 +01:00' --until='2026-11-14 22:36:50 +01:00' --full-history --no-merges -- Modules/Sources/OnlyRemoteFeature/Features/Settings/GlobalSettingsFeature.swift`: 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: Modules/Sources/AppFeature/Features/OnlyControl/OnlyControlReducer.swift Modules/Sources/AppFeature/Features/OnlyControl/OnlyControlReducer.swift:91— Modules/Sources/AppFeature/Features/OnlyControl/OnlyControlReducer.swift changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in OnlyControlReducer.body at line 91. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 22:36:50 +01:00' --until='2026-11-14 22:36:50 +01:00' --full-history --no-merges -- Modules/Sources/AppFeature/Features/OnlyControl/OnlyControlReducer.swift`: 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: Modules/Sources/AppFeature/Features/RemoteAccess/Catalog/RemoteCatalogProvider+Live.swift Modules/Sources/AppFeature/Features/RemoteAccess/Catalog/RemoteCatalogProvider+Live.swift:7— Modules/Sources/AppFeature/Features/RemoteAccess/Catalog/RemoteCatalogProvider+Live.swift changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in RemoteCatalogProvider.init at line 7. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 22:36:50 +01:00' --until='2026-11-14 22:36:50 +01:00' --full-history --no-merges -- Modules/Sources/AppFeature/Features/RemoteAccess/Catalog/RemoteCatalogProvider+Live.swift`: 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: Modules/Sources/Scheduler/SchedulesFeature.swift Modules/Sources/Scheduler/SchedulesFeature.swift:82— Modules/Sources/Scheduler/SchedulesFeature.swift changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in SchedulesFeature.body at line 82. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 22:36:50 +01:00' --until='2026-11-14 22:36:50 +01:00' --full-history --no-merges -- Modules/Sources/Scheduler/SchedulesFeature.swift`: 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: Modules/Sources/OnlyAgent/ModelProviderService.swift Modules/Sources/OnlyAgent/ModelProviderService.swift:69— Modules/Sources/OnlyAgent/ModelProviderService.swift changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in ModelProviderService.liveValue at line 69. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 22:36:50 +01:00' --until='2026-11-14 22:36:50 +01:00' --full-history --no-merges -- Modules/Sources/OnlyAgent/ModelProviderService.swift`: 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: Modules/Sources/Screenshots/ScreenshotsFeature.swift Modules/Sources/Screenshots/ScreenshotsFeature.swift:68— Modules/Sources/Screenshots/ScreenshotsFeature.swift changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 62 in ScreenshotsFeature.body at line 68. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 22:36:50 +01:00' --until='2026-11-14 22:36:50 +01:00' --full-history --no-merges -- Modules/Sources/Screenshots/ScreenshotsFeature.swift`: 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: Modules/Sources/AppFeature/Features/DockPreview/DockPreviewFeature.swift Modules/Sources/AppFeature/Features/DockPreview/DockPreviewFeature.swift:67— Modules/Sources/AppFeature/Features/DockPreview/DockPreviewFeature.swift changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 55 in DockPreviewFeature.body at line 67. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 22:36:50 +01:00' --until='2026-11-14 22:36:50 +01:00' --full-history --no-merges -- Modules/Sources/AppFeature/Features/DockPreview/DockPreviewFeature.swift`: 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: Modules/Sources/OnlySwitchPersistence/Persistence.swift Modules/Sources/OnlySwitchPersistence/Persistence.swift:23— Modules/Sources/OnlySwitchPersistence/Persistence.swift changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in PersistenceController.init at line 23. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 22:36:50 +01:00' --until='2026-11-14 22:36:50 +01:00' --full-history --no-merges -- Modules/Sources/OnlySwitchPersistence/Persistence.swift`: 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: Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer.swift Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer.swift:222— Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer.swift changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in SystemAudioMixer.setConfiguration at line 222. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 22:36:50 +01:00' --until='2026-11-14 22:36:50 +01:00' --full-history --no-merges -- Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer.swift`: 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: Modules/Sources/AppFeature/CoreData/EvolutionCommandEntityLive.swift Modules/Sources/AppFeature/CoreData/EvolutionCommandEntityLive.swift:58— Modules/Sources/AppFeature/CoreData/EvolutionCommandEntityLive.swift changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in EvolutionCommandEntity.addItem at line 58. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 22:36:50 +01:00' --until='2026-11-14 22:36:50 +01:00' --full-history --no-merges -- Modules/Sources/AppFeature/CoreData/EvolutionCommandEntityLive.swift`: 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: Modules/Sources/DisplayBrightness/DisplayBrightnessFeature.swift Modules/Sources/DisplayBrightness/DisplayBrightnessFeature.swift:54— Modules/Sources/DisplayBrightness/DisplayBrightnessFeature.swift changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in DisplayBrightnessFeature.body at line 54. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 22:36:50 +01:00' --until='2026-11-14 22:36:50 +01:00' --full-history --no-merges -- Modules/Sources/DisplayBrightness/DisplayBrightnessFeature.swift`: 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: Modules/Sources/AppFeature/Features/RemoteAccess/Campaign/OnlyRemoteCampaignFeature.swift Modules/Sources/AppFeature/Features/RemoteAccess/Campaign/OnlyRemoteCampaignFeature.swift:27— Modules/Sources/AppFeature/Features/RemoteAccess/Campaign/OnlyRemoteCampaignFeature.swift changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in OnlyRemoteCampaignFeature.body at line 27. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 22:36:50 +01:00' --until='2026-11-14 22:36:50 +01:00' --full-history --no-merges -- Modules/Sources/AppFeature/Features/RemoteAccess/Campaign/OnlyRemoteCampaignFeature.swift`: 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: Modules/Sources/DesktopPet/DesktopPetPlaybackFeature.swift Modules/Sources/DesktopPet/DesktopPetPlaybackFeature.swift:39— Modules/Sources/DesktopPet/DesktopPetPlaybackFeature.swift changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in DesktopPetPlaybackFeature.body at line 39. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 22:36:50 +01:00' --until='2026-11-14 22:36:50 +01:00' --full-history --no-merges -- Modules/Sources/DesktopPet/DesktopPetPlaybackFeature.swift`: 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: Modules/Sources/DesktopPet/MotionValues.swift Modules/Sources/DesktopPet/MotionValues.swift:57— Modules/Sources/DesktopPet/MotionValues.swift changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in DesktopPetMotion.values at line 57. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 22:36:50 +01:00' --until='2026-11-14 22:36:50 +01:00' --full-history --no-merges -- Modules/Sources/DesktopPet/MotionValues.swift`: 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.
Swallowed exception (caught, then discarded) Modules/Sources/Tailscale/TailscaleCoordinator.swift:126— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Modules/Sources/Screenshots/ScreenshotFolderWatcher.swift:187— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Modules/Sources/Screenshots/WindowFrameReader.swift:50— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Modules/Sources/RadioBrowser/RadioBrowserClient.swift:135— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Modules/Sources/OnlyWidgetFeature/Widgets/Evolution/Intents/EvolutionEntity.swift:31— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Background.swift:62— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Discovery.swift:113— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Messages.swift:77— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Messages.swift:86— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Pairing.swift:296— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteScreenshotResponses.swift:194— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Modules/Sources/OnlyAgent/Settings/OpenAISettings/OpenAIService.swift:119— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Modules/Sources/OnlyAgent/Settings/GeminiSettings/GeminiService.swift:109— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Modules/Sources/OnlyAgent/Settings/CodexSettings/CodexService.swift:137— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeService.swift:107— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Modules/Sources/OnlyAgent/CodexUsage/CodexUsageService.swift:62— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Modules/Sources/Extensions/LocalizedString++.swift:79— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Modules/Sources/Extensions/LocalizedString++.swift:88— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Modules/Sources/Extensions/String++.swift:93— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Modules/Sources/Extensions/String++.swift:155— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Modules/Sources/AppFeature/AppDelegate.swift:295— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Modules/Sources/AppFeature/Utilities/BluetoothDevicesManager.swift:68— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Modules/Sources/AppFeature/Utilities/WallpaperManager.swift:65— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Modules/Sources/AppFeature/StatusBar/StatusBarController+MenuBarIconHiding.swift:77— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) Modules/Sources/AppFeature/StatusBar/StatusBarController+MenuBarIconHiding.swift:88— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
MethodTooLong: SwitchType.barInfo Modules/Sources/Switches/SwitchType+BarInfo.swift:9— MethodTooLong — barInfo runs 279 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 179 over it, 2.79× 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: AphroditeReducer.body Modules/Sources/Aphrodite/AphroditeReducer.swift:96— MethodTooLong — body runs 238 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 138 over it, 2.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PairingFeature.body Modules/Sources/OnlyRemoteFeature/Features/Pairing/PairingFeature.swift:137— MethodTooLong — body runs 214 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 114 over it, 2.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RemoteAccessSettingsFeature.body Modules/Sources/AppFeature/Features/RemoteAccess/Settings/RemoteAccessSettingsFeature.swift:85— MethodTooLong — body runs 175 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 75 over it, 1.75× 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: DockPreviewFeature.body Modules/Sources/AppFeature/Features/DockPreview/DockPreviewFeature.swift:67— MethodTooLong — body runs 173 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 73 over it, 1.73× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RemoteMessage.encode Modules/Sources/RemoteCore/RemoteMessage.swift:238— MethodTooLong — encode runs 158 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RemoteAppFeature.core Modules/Sources/OnlyRemoteFeature/App/RemoteAppFeature.swift:178— MethodTooLong — core runs 149 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 49 over it, 1.49× 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: RemoteScreenshotsFeature.body Modules/Sources/OnlyRemoteFeature/Features/Screenshots/RemoteScreenshotsFeature.swift:123— MethodTooLong — body runs 149 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 49 over it, 1.49× 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: RemotePeerSession.handleAuthenticated Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession+Messages.swift:38— MethodTooLong — handleAuthenticated runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CodexUsageView.content Modules/Sources/OnlyAgent/CodexUsage/CodexUsageView.swift:22— MethodTooLong — content runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RemoteAppView.body Modules/Sources/OnlyRemoteFeature/App/RemoteAppView.swift:8— MethodTooLong — body runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ScreenshotsFeature.body Modules/Sources/Screenshots/ScreenshotsFeature.swift:68— MethodTooLong — body runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× 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: OnlyControlReducer.body Modules/Sources/AppFeature/Features/OnlyControl/OnlyControlReducer.swift:91— MethodTooLong — body 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.
MethodTooLong: OnlySwitchListView.body Modules/Sources/AppFeature/Features/OnlySwitchList/OnlySwitchListView.swift:77— MethodTooLong — body runs 126 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× 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: GeneralView.body Modules/Sources/AppFeature/Features/Settings/General/GeneralView.swift:20— MethodTooLong — body runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× 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: GlobalSettingsView.body Modules/Sources/OnlyRemoteFeature/Features/Settings/GlobalSettingsView.swift:7— MethodTooLong — body runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× 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: RemoteConnectionRuntime.preparePairing Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Pairing.swift:5— MethodTooLong — preparePairing 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.
MethodTooLong: AgentConversationReducer.reduceExecution Modules/Sources/OnlyAgent/Conversation/AgentConversationReducer+Execution.swift:10— MethodTooLong — reduceExecution runs 117 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PairingView.body Modules/Sources/OnlyRemoteFeature/Features/Pairing/PairingView.swift:7— MethodTooLong — body runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SettingsFeature.body Modules/Sources/OnlyRemoteFeature/Features/Settings/SettingsFeature.swift:96— MethodTooLong — body runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RemoteMessage.init Modules/Sources/RemoteCore/RemoteMessage.swift:123— MethodTooLong — init runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× 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: DisplayBrightnessFeature.body Modules/Sources/DisplayBrightness/DisplayBrightnessFeature.swift:54— MethodTooLong — body 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: ModelProviderService.liveValue Modules/Sources/OnlyAgent/ModelProviderService.swift:69— MethodTooLong — liveValue 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.
MethodTooLong: SchedulesFeature.body Modules/Sources/Scheduler/SchedulesFeature.swift:82— MethodTooLong — body 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.
MethodTooLong: AgentConversationReducer.body Modules/Sources/OnlyAgent/Conversation/AgentConversationReducer.swift:142— MethodTooLong — body runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (8 lines × 2) Modules/Sources/AppFeature/Features/OnlyControl/OnlyControlView.swift:157— Modules/Sources/AppFeature/Features/OnlyControl/OnlyControlView.swift:157-164 | Modules/Sources/AppFeature/Features/OnlySwitchList/OnlySwitchListView.swift:144-151 — 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 `Modules/Sources/AppFeature/Features/OnlyControl/OnlyControlView.swift:157` 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) Modules/Sources/AppFeature/Features/Settings/DesktopPet/DesktopPetSkinGeneratorSheet.swift:117— Modules/Sources/AppFeature/Features/Settings/DesktopPet/DesktopPetSkinGeneratorSheet.swift:117-124 | Modules/Sources/DesktopPet/DesktopPetNowPlayingLabel.swift:99-106 — 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 (8 lines × 2) Modules/Sources/AppFeature/Features/Settings/Evolution/EvolutionGallery/EvolutionGalleryView.swift:25— Modules/Sources/AppFeature/Features/Settings/Evolution/EvolutionGallery/EvolutionGalleryView.swift:25-32 | Modules/Sources/AppFeature/Features/Settings/Shortcuts/ShortcutsSettingsView.swift:64-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 `Modules/Sources/AppFeature/Features/Settings/Evolution/EvolutionGallery/EvolutionGalleryView.swift:25` 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) Modules/Sources/AppFeature/Features/SystemMonitor/SystemMonitorStatusItemController.swift:228— Modules/Sources/AppFeature/Features/SystemMonitor/SystemMonitorStatusItemController.swift:228-235 | Modules/Sources/SystemMonitor/SystemMonitorFormatters.swift:9-16 — 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 (8 lines × 2) Modules/Sources/AppFeature/Features/Update/UpdateView.swift:42— Modules/Sources/AppFeature/Features/Update/UpdateView.swift:42-49 | Modules/Sources/AppFeature/Features/Update/UpdateView.swift:58-65 — 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 `Modules/Sources/AppFeature/Features/Update/UpdateView.swift:42` 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) Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift:32— Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift:32-39 | Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageFeature.swift:33-40 — before extracting anything, compare `Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift` and `Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageFeature.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 52 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 `Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift:32` 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 lines × 2) Modules/Sources/OnlyRemoteFeature/Features/Screenshots/RemoteScreenshotCell.swift:107— Modules/Sources/OnlyRemoteFeature/Features/Screenshots/RemoteScreenshotCell.swift:107-114 | Modules/Sources/Screenshots/ScreenshotsView.swift:385-392 — 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 `Modules/Sources/OnlyRemoteFeature/Features/Screenshots/RemoteScreenshotCell.swift: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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Modules/Sources/OnlyRemoteFeature/Features/Screenshots/RemoteScreenshotCell.swift:105` calls `Image` and `Modules/Sources/Screenshots/ScreenshotsView.swift:383` 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 (8 lines × 2) Modules/Sources/RemoteCore/ClaudeUsageModels.swift:88— Modules/Sources/RemoteCore/ClaudeUsageModels.swift:88-95 | Modules/Sources/RemoteCore/CodexUsageModels.swift:90-97 — 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 (8 lines × 2) Modules/Sources/OnlyRemoteFeature/Features/Screenshots/RemoteScreenshotCell.swift:120— Modules/Sources/OnlyRemoteFeature/Features/Screenshots/RemoteScreenshotCell.swift:120-127 | Modules/Sources/OnlyRemoteFeature/Features/Screenshots/RemoteScreenshotDetailContent.swift:60-67 — 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 (8 lines × 2) Modules/Sources/XcodeCleaner/XcodeCleanerFileSystem.swift:97— Modules/Sources/XcodeCleaner/XcodeCleanerFileSystem.swift:97-104 | Modules/Sources/XcodeCleaner/XcodeCleanerSimulator.swift:165-172 — 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 `Modules/Sources/XcodeCleaner/XcodeCleanerFileSystem.swift:97` 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 (8 lines × 2) Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerService.swift:222— Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerService.swift:222-229 | Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer+Taps.swift:118-125 — 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. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (8 lines × 2) Modules/Sources/RemoteCore/ClaudeUsageModels.swift:77— Modules/Sources/RemoteCore/ClaudeUsageModels.swift:77-84 | Modules/Sources/RemoteCore/CodexUsageModels.swift:79-86 — 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 `Modules/Sources/RemoteCore/ClaudeUsageModels.swift:77` 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.
TooManyMethods: RemoteConnectionRuntime Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime.swift:5— TooManyMethods — 75 methods, declared across 8 files: Dependencies/RemoteConnectionRuntime+Commands.swift (14), Dependencies/RemoteConnectionRuntime+Policies.swift (14), Dependencies/RemoteConnectionRuntime.swift (13), Dependencies/RemoteConnectionRuntime+Messages.swift (9), +4 more file(s). The bar is 30 methods; this is 45 over it, 2.50× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. 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: RemoteReviewDemoRuntime Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteReviewDemoClient.swift:5— TooManyMethods — 59 methods, declared across 3 files: Dependencies/RemoteReviewDemoRuntime+Persistence.swift (28), Dependencies/RemoteReviewDemoClient.swift (24), Dependencies/RemoteReviewDemoRuntime+Fixtures.swift (7). The bar is 30 methods; this is 29 over it, 1.97× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. 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: RemotePeerSession Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession.swift:8— TooManyMethods — 50 methods, declared across 5 files: Host/RemotePeerSession+Streaming.swift (20), Host/RemotePeerSession.swift (10), Host/RemotePeerSession+Messages.swift (8), Host/RemotePeerSession+Handshake.swift (6), +1 more file(s). The bar is 30 methods; this is 20 over it, 1.67× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. 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: RemoteCredentialStore Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteCredentialStore.swift:22— TooManyMethods — 49 methods, declared across 3 files: Host/RemoteCredentialStore.swift (29), Host/RemoteCredentialStore+PreparedReplacements.swift (11), Host/RemoteCredentialStore+Keychain.swift (9). The bar is 30 methods; this is 19 over it, 1.63× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. 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: RemoteHost Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteHost.swift:7— TooManyMethods — 39 methods, declared across 3 files: Host/RemoteHost.swift (18), Host/RemoteHost+Sessions.swift (12), Host/RemoteHost+Testing.swift (9). The bar is 30 methods; this is 9 over it, 1.30× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. 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: RemoteFilePersistenceStore Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteFilePersistenceStore.swift:9— 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: RemoteAppFeature Modules/Sources/OnlyRemoteFeature/App/RemoteAppFeature.swift:15— TooManyMethods — 38 methods, declared across 4 files: App/RemoteAppFeature+Sync.swift (12), App/RemoteAppFeature+Navigation.swift (10), App/RemoteAppFeature+Selection.swift (9), App/RemoteAppFeature+Launch.swift (7). The bar is 30 methods; this is 8 over it, 1.27× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. 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: RemoteClientSession Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteClientSession.swift:7— TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SystemAudioMixer Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer.swift:10— TooManyMethods — 33 methods, declared across 3 files: SoundMixer/SystemAudioMixer.swift (16), SoundMixer/SystemAudioMixer+CoreAudio.swift (9), SoundMixer/SystemAudioMixer+Taps.swift (8). The bar is 30 methods; this is 3 over it, 1.10× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. 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: InMemoryRemotePersistenceStore Modules/Sources/OnlyRemoteFeature/Dependencies/InMemoryRemotePersistenceStore.swift:4— 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.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×10
Edited copy of a member (4 corresponding lines) Modules/Sources/RemoteCore/AphroditeRemoteModels.swift:216— Modules/Sources/RemoteCore/AphroditeRemoteModels.swift:216-219 | Modules/Sources/RemoteCore/RemoteScreenshots.swift:200-211 — 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) Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession.swift:287— Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession.swift:287-302 | Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteClientSession.swift:419-422 — 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) Modules/Sources/AppUninstaller/AppUninstallerView.swift:166— Modules/Sources/AppUninstaller/AppUninstallerView.swift:166-169 | Modules/Sources/Tailscale/TailscaleSettingsView.swift:197-200 — 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) Modules/Sources/OnlyAgent/Settings/OllamaSettings/OllamaSharedKey.swift:21— Modules/Sources/OnlyAgent/Settings/OllamaSettings/OllamaSharedKey.swift:21-24 | Modules/Sources/StickerView/StickerSharedKey.swift:19-22 — 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) Modules/Sources/AppFeature/Features/DisplayBrightness/DisplayBrightnessKeyTap.swift:28— Modules/Sources/AppFeature/Features/DisplayBrightness/DisplayBrightnessKeyTap.swift:28-31 | Modules/Sources/AppFeature/Features/DisplayBrightness/DisplayBrightnessKeyboardController.swift:20-24 — 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) Modules/Sources/Screenshots/ScreenCapturePreferences.swift:180— Modules/Sources/Screenshots/ScreenCapturePreferences.swift:180-183 | Modules/Sources/Screenshots/SimulatorScreenshotPreferences.swift:64-67 — 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) Modules/Sources/AppFeature/Features/RemoteAccess/Campaign/OnlyRemoteCampaignClient.swift:119— Modules/Sources/AppFeature/Features/RemoteAccess/Campaign/OnlyRemoteCampaignClient.swift:119-127 | Modules/Sources/OnlyAgent/ClaudeUsage/ClaudeUsageService.swift:97-100 — 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) Modules/Sources/Aphrodite/AphroditeEditorView.swift:132— Modules/Sources/Aphrodite/AphroditeEditorView.swift:132-135 | Modules/Sources/Aphrodite/AphroditeViews.swift:102-105 — 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) Modules/Sources/OnlyAgent/ClaudeUsage/ClaudeUsagePanelContainer.swift:8— Modules/Sources/OnlyAgent/ClaudeUsage/ClaudeUsagePanelContainer.swift:8-11 | Modules/Sources/OnlyAgent/CodexUsage/CodexUsagePanelContainer.swift:9-14 — 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) Modules/Sources/AppFeature/Features/Settings/DesktopPet/DesktopPetSettingsFeature.swift:26— Modules/Sources/AppFeature/Features/Settings/DesktopPet/DesktopPetSettingsFeature.swift:26-29 | Modules/Sources/Scheduler/ScheduleEditorFeature.swift:33-36 — 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.
Swallowed exception (empty catch) Modules/Sources/WebBrowser/Resources/DarkReader.js:2811— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Modules/Sources/WebBrowser/Resources/DarkReader.js:2846— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Modules/Sources/WebBrowser/Resources/DarkReader.js:2852— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Modules/Sources/WebBrowser/Resources/DarkReader.js:2858— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Modules/Sources/WebBrowser/Resources/DarkReader.js:9199— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Modules/Sources/OnlySwitchPersistence/RadioStations+Fetch.swift:54— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Modules/Sources/OnlySwitchPersistence/RadioStations+Fetch.swift:78— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Modules/Sources/OnlySwitchPersistence/RadioStations+Fetch.swift:102— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Modules/Sources/OnlyRemoteFeature/Features/Pairing/PairingFeature.swift:154— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Modules/Sources/OnlyAgent/ClaudeUsage/ClaudeOAuthCredentialClient.swift:61— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×9
Edited copy of a member (9 corresponding lines) Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageView.swift:46— Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageView.swift:46-54 | Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageView.swift:78-88 — 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) Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerService.swift:238— Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerService.swift:238-246 | Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerService.swift:261-274 — 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) Modules/Sources/OnlyAgent/CodexUsage/CodexAppServerClient.swift:106— Modules/Sources/OnlyAgent/CodexUsage/CodexAppServerClient.swift:106-114 | Modules/Sources/OnlyAgent/CodexUsage/CodexLocalUsageScanner.swift:63-72 — 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) Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer+CoreAudio.swift:112— Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer+CoreAudio.swift:112-121 | Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer+Taps.swift:166-174 — 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) Modules/Sources/RemoteCore/RemoteAction.swift:17— Modules/Sources/RemoteCore/RemoteAction.swift:17-25 | Modules/Sources/RemoteCore/RemoteControlDescriptor.swift:24-32 — 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) Modules/Sources/RadioBrowser/RadioStationArtwork.swift:55— Modules/Sources/RadioBrowser/RadioStationArtwork.swift:55-63 | Modules/Sources/Scheduler/ScheduleSurface.swift:7-15 — 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) Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteCredentialStore+PreparedReplacements.swift:13— Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteCredentialStore+PreparedReplacements.swift:13-24 | Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteCredentialStore.swift:410-418 — 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) Modules/Sources/Extensions/NSImage++.swift:23— Modules/Sources/Extensions/NSImage++.swift:23-31 | Modules/Sources/Extensions/NSImage++.swift:146-154 — 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) Modules/Sources/AppFeature/Player/MusicAppPlayer/AppleMusic/AppleMusicPlayer/AppleMusicPlayer.swift:33— Modules/Sources/AppFeature/Player/MusicAppPlayer/AppleMusic/AppleMusicPlayer/AppleMusicPlayer.swift:33-41 | Modules/Sources/AppFeature/Player/MusicAppPlayer/Spotify/SpotifyPlayer/SpotifyPlayer.swift:38-46 — 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.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×9
Edited copy of a member (7 corresponding lines) Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageView.swift:55— Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageView.swift:55-61 | Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageView.swift:89-104 — 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) Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageView.swift:62— Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageView.swift:62-68 | Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageView.swift:149-155 — 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) Modules/Sources/RemoteCore/RemoteSoundMixer.swift:38— Modules/Sources/RemoteCore/RemoteSoundMixer.swift:38-45 | Modules/Sources/RemoteCore/RemoteSoundMixer.swift:63-69 — 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) Modules/Sources/DesktopPet/DesktopPetAgentLogParser.swift:119— Modules/Sources/DesktopPet/DesktopPetAgentLogParser.swift:119-125 | Modules/Sources/OnlyAgent/ClaudeUsage/ClaudeUsageResponse.swift:43-50 — 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) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteFilePersistenceStore.swift:77— Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteFilePersistenceStore.swift:77-83 | Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteFilePersistenceStore.swift:85-92 — 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) Modules/Sources/RemoteCore/RemoteBrightness.swift:45— Modules/Sources/RemoteCore/RemoteBrightness.swift:45-51 | Modules/Sources/RemoteCore/RemoteScreenshots.swift:94-101 — 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) Modules/Sources/AppFeature/Features/SoundMixer/DisplayVolumeHUDView.swift:35— Modules/Sources/AppFeature/Features/SoundMixer/DisplayVolumeHUDView.swift:35-41 | Modules/Sources/DesktopPet/DesktopPetPlaybackButtonBackground.swift:4-10 — 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) Modules/Sources/AppFeature/Features/Settings/HideMenubarIcons/HideMenubarIconsSettingVM.swift:55— Modules/Sources/AppFeature/Features/Settings/HideMenubarIcons/HideMenubarIconsSettingVM.swift:55-63 | Modules/Sources/AppFeature/Features/Settings/BackNoises/BackNoisesSettingVM.swift:64-70 — 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) Modules/Sources/DisplayBrightness/DisplayBrightnessView.swift:109— Modules/Sources/DisplayBrightness/DisplayBrightnessView.swift:109-115 | Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessView.swift:104-110 — 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 (11 lines × 2) Modules/Sources/AppFeature/EverySwitch/ScrollDirectionEventTap.swift:57— Modules/Sources/AppFeature/EverySwitch/ScrollDirectionEventTap.swift:57-70 | Modules/Sources/AppFeature/Features/SoundMixer/DisplayVolumeKeyTap.swift:44-54 — 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 `Modules/Sources/AppFeature/EverySwitch/ScrollDirectionEventTap.swift:57` 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 (11 lines × 2) Modules/Sources/AppFeature/Features/DockPreview/DockPreviewClient.swift:355— Modules/Sources/AppFeature/Features/DockPreview/DockPreviewClient.swift:355-365 | Modules/Sources/AppFeature/StatusBar/MenuBarAccessibilityItemResolver.swift:380-390 — 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 `Modules/Sources/AppFeature/Features/DockPreview/DockPreviewClient.swift:355` 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 (11 lines × 2) Modules/Sources/AppFeature/Features/Settings/DimScreen/DimScreenSettingVM.swift:58— Modules/Sources/AppFeature/Features/Settings/DimScreen/DimScreenSettingVM.swift:58-68 | Modules/Sources/AppFeature/Features/Settings/KeepAwake/KeepAwakeSettingVM.swift:79-89 — 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 (11 lines × 2) Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerService.swift:249— Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerService.swift:249-259 | Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer+CoreAudio.swift:124-134 — 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 (11 lines × 2) Modules/Sources/AppFeature/Player/MusicAppPlayer/AppleMusic/AppleMusicPlayer/AppleMusicPlayer.swift:47— Modules/Sources/AppFeature/Player/MusicAppPlayer/AppleMusic/AppleMusicPlayer/AppleMusicPlayer.swift:47-57 | Modules/Sources/AppFeature/Player/MusicAppPlayer/Spotify/SpotifyPlayer/SpotifyPlayer.swift:48-58 — 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 `Modules/Sources/AppFeature/Player/MusicAppPlayer/AppleMusic/AppleMusicPlayer/AppleMusicPlayer.swift:47` 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, `Modules/Sources/AppFeature/Player/MusicAppPlayer/AppleMusic/AppleMusicPlayer/AppleMusicPlayer.swift:58` calls `debug` and `Modules/Sources/AppFeature/Player/MusicAppPlayer/Spotify/SpotifyPlayer/SpotifyPlayer.swift: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 (11 lines × 2) Modules/Sources/Networking/GitHub/GitHubRemoteDataSource.swift:15— Modules/Sources/Networking/GitHub/GitHubRemoteDataSource.swift:15-25 | Modules/Sources/Networking/GitHub/GitHubRemoteDataSource.swift:45-55 — 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 `Modules/Sources/Networking/GitHub/GitHubRemoteDataSource.swift:15` 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 (11 lines × 2) Modules/Sources/OnlyRemoteFeature/Features/Pairing/PairingView.swift:25— Modules/Sources/OnlyRemoteFeature/Features/Pairing/PairingView.swift:25-35 | Modules/Sources/OnlyRemoteFeature/Features/Pairing/PairingView.swift:56-66 — 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 (11 lines × 2) Modules/Sources/SoundMixerEQ/EqualizerFeature.swift:51— Modules/Sources/SoundMixerEQ/EqualizerFeature.swift:51-61 | Modules/Sources/SoundMixerEQ/OutputRoutingFeature.swift:37-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 both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Modules/Sources/SoundMixerEQ/EqualizerFeature.swift:51` 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 (11 lines × 2) Modules/Sources/AppFeature/EverySwitch/AppleMusicSwitch.swift:56— Modules/Sources/AppFeature/EverySwitch/AppleMusicSwitch.swift:56-66 | Modules/Sources/AppFeature/EverySwitch/SpotifySwitch.swift:57-67 — 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) Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerVM+Interaction.swift:83— Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerVM+Interaction.swift:83-91 | Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerVM+Interaction.swift:97-105 — 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) Modules/Sources/AppFeature/Features/SwitchItem/EvolutionItems/EvolutionBarView.swift:52— Modules/Sources/AppFeature/Features/SwitchItem/EvolutionItems/EvolutionBarView.swift:52-60 | Modules/Sources/AppFeature/Features/SwitchItem/ShortcutsItem/ShortcutsBarView.swift:45-53 — 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 `Modules/Sources/AppFeature/Features/SwitchItem/EvolutionItems/EvolutionBarView.swift:52` 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 × 2) Modules/Sources/AppFeature/Player/CommonPlayer/JLASAudioPlayer.swift:52— Modules/Sources/AppFeature/Player/CommonPlayer/JLASAudioPlayer.swift:52-60 | Modules/Sources/AppFeature/Player/CommonPlayer/JLAVAudioPlayer.swift:27-35 — 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 `Modules/Sources/AppFeature/Player/CommonPlayer/JLASAudioPlayer.swift:52` 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 × 2) Modules/Sources/AppUninstaller/AppUninstallerView.swift:16— Modules/Sources/AppUninstaller/AppUninstallerView.swift:16-24 | Modules/Sources/XcodeCleaner/XcodeCleanerView.swift:14-22 — 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 `Modules/Sources/AppUninstaller/AppUninstallerView.swift:16` 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 first that the copies are not typed on the same thing: the declarations holding them bind `store` to `StoreOf<AppUninstallerFeature>` in one and `StoreOf<XcodeCleanerFeature>` 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) Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:112— Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:112-120 | Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerFeature.swift:225-233 — before extracting anything, compare `Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift` and `Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerFeature.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 86 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 (9 lines × 2) Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift:73— Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift:73-81 | Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageFeature.swift:81-89 — before extracting anything, compare `Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift` and `Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageFeature.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 52 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 `Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift: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.
Duplicated block (9 lines × 2) Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift:107— Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift:107-115 | Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageFeature.swift:114-122 — before extracting anything, compare `Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift` and `Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageFeature.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 52 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) Modules/Sources/OnlyRemoteFeature/Features/Dashboard/ControlTileStatusBadge.swift:89— Modules/Sources/OnlyRemoteFeature/Features/Dashboard/ControlTileStatusBadge.swift:89-97 | Modules/Sources/OnlyRemoteFeature/Features/Dashboard/ControlTileView.swift:102-110 — 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 (9 lines × 2) Modules/Sources/AppFeature/Player/MusicAppPlayer/AppleMusic/AppleMusicPlayer/AppleMusicPlayer.swift:76— Modules/Sources/AppFeature/Player/MusicAppPlayer/AppleMusic/AppleMusicPlayer/AppleMusicPlayer.swift:76-84 | Modules/Sources/AppFeature/Player/MusicAppPlayer/Spotify/SpotifyPlayer/SpotifyPlayer.swift:71-79 — 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 (6 lines × 2) Modules/Sources/AppFeature/EverySwitch/KeepAwakeSwitch.swift:127— Modules/Sources/AppFeature/EverySwitch/KeepAwakeSwitch.swift:127-132 | Modules/Sources/AppFeature/EverySwitch/NightShiftSwitch.swift:91-96 — 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 (6 lines × 2) Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerService.swift:133— Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerService.swift:133-138 | Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerService.swift:149-154 — 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. 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 (6 lines × 2) Modules/Sources/Screenshots/ScreenshotsView.swift:135— Modules/Sources/Screenshots/ScreenshotsView.swift:135-140 | Modules/Sources/Screenshots/ScreenshotsView.swift:173-178 — 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 `Modules/Sources/Screenshots/ScreenshotsView.swift:135` 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, `Modules/Sources/Screenshots/ScreenshotsView.swift:180` calls `Text`, `localized`, `font` and `Modules/Sources/Screenshots/ScreenshotsView.swift:142` 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) Modules/Sources/SoundMixerEQ/EqualizerFeature.swift:117— Modules/Sources/SoundMixerEQ/EqualizerFeature.swift:117-122 | Modules/Sources/SoundMixerEQ/OutputRoutingFeature.swift:104-109 — 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 `Modules/Sources/SoundMixerEQ/EqualizerFeature.swift:117` 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 (6 lines × 2) Modules/Sources/XcodeCleaner/XcodeCleanerFileSystem.swift:62— Modules/Sources/XcodeCleaner/XcodeCleanerFileSystem.swift:62-67 | Modules/Sources/XcodeCleaner/XcodeCleanerSimulator.swift:151-156 — 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 `Modules/Sources/XcodeCleaner/XcodeCleanerFileSystem.swift:62` 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 (6 lines × 2) Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift:97— Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift:97-102 | Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageFeature.swift:104-109 — before extracting anything, compare `Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift` and `Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageFeature.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 52 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 (6 lines × 2) Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeService.swift:15— Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeService.swift:15-20 | Modules/Sources/OnlyAgent/Settings/GeminiSettings/GeminiService.swift:15-23 — before extracting anything, compare `Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeService.swift` and `Modules/Sources/OnlyAgent/Settings/GeminiSettings/GeminiService.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 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 before the matched lines, `Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeService.swift:12` calls `URL` and `Modules/Sources/OnlyAgent/Settings/GeminiSettings/GeminiService.swift:14` 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 (6 lines × 2) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteClientSessionResponses.swift:44— Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteClientSessionResponses.swift:44-49 | Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteClientSessionResponses.swift:78-83 — 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 `Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteClientSessionResponses.swift:44` 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 (6 lines × 2) Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageView.swift:63— Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageView.swift:63-68 | Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageView.swift:150-155 — 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) Modules/Sources/Aphrodite/AphroditeReducer.swift:204— Modules/Sources/Aphrodite/AphroditeReducer.swift:204-208 | Modules/Sources/Aphrodite/AphroditeReducer.swift:253-257 — 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 `Modules/Sources/Aphrodite/AphroditeReducer.swift:204` 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 (5 lines × 2) Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession+Handshake.swift:103— Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession+Handshake.swift:103-107 | Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession+Pairing.swift:101-109 — 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 `Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession+Handshake.swift:103` 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 (5 lines × 2) Modules/Sources/OnlyRemoteFeature/App/RemoteAppFeature.swift:332— Modules/Sources/OnlyRemoteFeature/App/RemoteAppFeature.swift:332-336 | Modules/Sources/OnlyRemoteFeature/App/RemoteAppFeature.swift:350-354 — 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. 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 (5 lines × 2) Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteEqualizerView.swift:81— Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteEqualizerView.swift:81-85 | Modules/Sources/SoundMixerEQ/EqualizerView.swift:133-137 — 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 `Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteEqualizerView.swift:81` 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 (5 lines × 2) Modules/Sources/AppFeature/EverySwitch/AppleMusicSwitch.swift:69— Modules/Sources/AppFeature/EverySwitch/AppleMusicSwitch.swift:69-73 | Modules/Sources/AppFeature/EverySwitch/SpotifySwitch.swift:70-74 — 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) Modules/Sources/AppFeature/EverySwitch/AppleMusicSwitch.swift:75— Modules/Sources/AppFeature/EverySwitch/AppleMusicSwitch.swift:75-79 | Modules/Sources/AppFeature/EverySwitch/SpotifySwitch.swift:76-80 — 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) Modules/Sources/AppFeature/Player/MusicAppPlayer/AppleMusic/AppleMusicPlayer/AppleMusicPlayer.swift:21— Modules/Sources/AppFeature/Player/MusicAppPlayer/AppleMusic/AppleMusicPlayer/AppleMusicPlayer.swift:21-25 | Modules/Sources/AppFeature/Player/MusicAppPlayer/Spotify/SpotifyPlayer/SpotifyPlayer.swift:22-26 — 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) Modules/Sources/Authenticator/AuthenticatorPanelView.swift:102— Modules/Sources/Authenticator/AuthenticatorPanelView.swift:102-106 | Modules/Sources/Authenticator/AuthenticatorSettingsView.swift:78-82 — 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 `Modules/Sources/Authenticator/AuthenticatorPanelView.swift: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.
Duplicated block (5 lines × 2) Modules/Sources/OnlyRemoteFeature/Dependencies/RemotePersistenceClient.swift:70— Modules/Sources/OnlyRemoteFeature/Dependencies/RemotePersistenceClient.swift:70-74 | Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteReviewDemoClients.swift:100-104 — 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 (8 corresponding lines) · ×8
Edited copy of a member (8 corresponding lines) Modules/Sources/OnlyAgent/ClaudeUsage/ClaudeUsageView.swift:124— Modules/Sources/OnlyAgent/ClaudeUsage/ClaudeUsageView.swift:124-131 | Modules/Sources/OnlyAgent/CodexUsage/CodexUsageView.swift:203-228 — 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) Modules/Sources/AppUninstaller/AdministratorTrash.swift:22— Modules/Sources/AppUninstaller/AdministratorTrash.swift:22-29 | Modules/Sources/Screenshots/DeviceHubScreenshotImporter.swift:39-50 — 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) Modules/Sources/AppFeature/Features/SystemMonitor/MacSystemMonitorCollector+Readers.swift:30— Modules/Sources/AppFeature/Features/SystemMonitor/MacSystemMonitorCollector+Readers.swift:30-38 | Modules/Sources/OnlyAgent/Conversation/AgentSystemInfo.swift:139-146 — 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) Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteHost.swift:148— Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteHost.swift:148-160 | Modules/Sources/OnlyAgent/ClaudeUsage/ClaudeCodeCLI.swift:305-312 — 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) Modules/Sources/DesktopPet/DesktopPetNeedsFeature.swift:99— Modules/Sources/DesktopPet/DesktopPetNeedsFeature.swift:99-107 | Modules/Sources/RadioBrowser/RadioStationsFeature.swift:114-121 — 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) Modules/Sources/XcodeCleaner/XcodeCleanerSimulator.swift:93— Modules/Sources/XcodeCleaner/XcodeCleanerSimulator.swift:93-100 | Modules/Sources/XcodeCleaner/XcodeCleanerFileSystem.swift:21-28 — 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) Modules/Sources/AppFeature/Features/SystemMonitor/SystemMonitorPanelView+Network.swift:127— Modules/Sources/AppFeature/Features/SystemMonitor/SystemMonitorPanelView+Network.swift:127-137 | Modules/Sources/OnlyRemoteFeature/Features/SystemMonitor/RemoteSystemMonitorView.swift:303-310 — 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) Modules/Sources/RemoteCore/AphroditeRemoteModels.swift:254— Modules/Sources/RemoteCore/AphroditeRemoteModels.swift:254-262 | Modules/Sources/RemoteCore/RemoteScreenshots.swift:219-226 — 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 (14 corresponding lines) · ×8
Edited copy of a member (14 corresponding lines) Modules/Sources/AppFeature/EverySwitch/AppUninstallerSwitch.swift:17— Modules/Sources/AppFeature/EverySwitch/AppUninstallerSwitch.swift:17-30 | Modules/Sources/AppFeature/EverySwitch/XcodeCleanerSwitch.swift:17-30 — 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) Modules/Sources/Scheduler/ScheduleHourlyControls.swift:8— Modules/Sources/Scheduler/ScheduleHourlyControls.swift:8-21 | Modules/Sources/Scheduler/ScheduleIntervalControls.swift:8-26 — 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) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteClientSession.swift:308— Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteClientSession.swift:308-321 | Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteClientSession.swift:323-336 — 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) Modules/Sources/DisplayBrightness/BrightnessKeyEvent.swift:10— Modules/Sources/DisplayBrightness/BrightnessKeyEvent.swift:10-23 | Modules/Sources/DisplayDDC/VolumeKeyEvent.swift:20-34 — 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) Modules/Sources/Reorderable/Reorderable.swift:24— Modules/Sources/Reorderable/Reorderable.swift:24-38 | Modules/Sources/Reorderable/Reorderable.swift:40-53 — 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) Modules/Sources/AppFeature/EverySwitch/ScrollDirectionEventTap.swift:52— Modules/Sources/AppFeature/EverySwitch/ScrollDirectionEventTap.swift:52-70 | Modules/Sources/AppFeature/Features/SoundMixer/DisplayVolumeKeyTap.swift:41-54 — 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) Modules/Sources/OnlyWidgetFeature/Widgets/BuiltIn/OnlyWidgetBuiltIn.swift:62— Modules/Sources/OnlyWidgetFeature/Widgets/BuiltIn/OnlyWidgetBuiltIn.swift:62-75 | Modules/Sources/OnlyWidgetFeature/Widgets/Evolution/OnlyWidgetEvolutionProvider.swift:53-66 — 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) Modules/Sources/AppFeature/EverySwitch/AppleMusicSwitch.swift:41— Modules/Sources/AppFeature/EverySwitch/AppleMusicSwitch.swift:41-54 | Modules/Sources/AppFeature/EverySwitch/SpotifySwitch.swift:41-55 — 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 (3 corresponding lines) · ×8
Edited copy of a member (3 corresponding lines) Modules/Sources/AppUninstaller/AppUninstallerClient.swift:12— Modules/Sources/AppUninstaller/AppUninstallerClient.swift:12-14 | Modules/Sources/Tailscale/TailscaleClient.swift:11-13 — 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) Modules/Sources/OnlyAgent/ClaudeUsage/ClaudeUsageModels.swift:34— Modules/Sources/OnlyAgent/ClaudeUsage/ClaudeUsageModels.swift:34-36 | Modules/Sources/RemoteCore/ClaudeUsageModels.swift:44-50 — 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) Modules/Sources/SoundMixerEQ/EqualizerView.swift:12— Modules/Sources/SoundMixerEQ/EqualizerView.swift:12-14 | Modules/Sources/SoundMixerEQ/OutputRoutingView.swift:12-15 — 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) Modules/Sources/AppUninstaller/AppUninstallerView.swift:13— Modules/Sources/AppUninstaller/AppUninstallerView.swift:13-15 | Modules/Sources/XcodeCleaner/XcodeCleanerView.swift:11-13 — 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) Modules/Sources/AppFeature/Features/SwitchItem/SwitchBar/AirPodsBatteryView.swift:17— Modules/Sources/AppFeature/Features/SwitchItem/SwitchBar/AirPodsBatteryView.swift:17-19 | Modules/Sources/OnlyRemoteFeature/Features/Dashboard/DashboardBackground.swift:43-47 — 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) Modules/Sources/AppFeature/Features/SwitchItem/SwitchBar/AirPodsBatteryView.swift:21— Modules/Sources/AppFeature/Features/SwitchItem/SwitchBar/AirPodsBatteryView.swift:21-23 | Modules/Sources/OnlyRemoteFeature/Features/Dashboard/DashboardBackground.swift:49-53 — 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) Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsagePresentation.swift:14— Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsagePresentation.swift:14-16 | Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsagePresentation.swift:15-17 — 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) Modules/Sources/Screenshots/ScreenCapturePreferences.swift:68— Modules/Sources/Screenshots/ScreenCapturePreferences.swift:68-70 | Modules/Sources/Screenshots/SimulatorScreenshotPreferences.swift:20-22 — 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 (5 corresponding lines) · ×8
Edited copy of a member (5 corresponding lines) Modules/Sources/Aphrodite/SecureAphroditeWebView.swift:163— Modules/Sources/Aphrodite/SecureAphroditeWebView.swift:163-167 | Modules/Sources/Aphrodite/SecureAphroditeWebView.swift:168-172 — 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) Modules/Sources/SoundMixerEQ/EqualizerClient.swift:9— Modules/Sources/SoundMixerEQ/EqualizerClient.swift:9-13 | Modules/Sources/SoundMixerEQ/OutputRoutingClient.swift:8-12 — 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) Modules/Sources/AppFeature/Features/OnlyControl/OnlyControlReducer.swift:267— Modules/Sources/AppFeature/Features/OnlyControl/OnlyControlReducer.swift:267-271 | Modules/Sources/AppFeature/Features/SwitchItem/SwitchBar/SwitchBarView.swift:166-170 — 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) Modules/Sources/OnlyRemoteFeature/Dependencies/InMemoryRemotePersistenceStore.swift:43— Modules/Sources/OnlyRemoteFeature/Dependencies/InMemoryRemotePersistenceStore.swift:43-47 | Modules/Sources/OnlyRemoteFeature/Dependencies/InMemoryRemotePersistenceStore.swift:48-53 — 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) Modules/Sources/SoundMixerEQ/EqualizerFeature.swift:106— Modules/Sources/SoundMixerEQ/EqualizerFeature.swift:106-110 | Modules/Sources/SoundMixerEQ/OutputRoutingFeature.swift:88-92 — 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) Modules/Sources/DisplayBrightness/DisplayBrightnessView.swift:12— Modules/Sources/DisplayBrightness/DisplayBrightnessView.swift:12-16 | Modules/Sources/Screenshots/ScreenshotsView.swift:18-22 — 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) Modules/Sources/AppFeature/EverySwitch/AuthenticatorSwitch.swift:34— Modules/Sources/AppFeature/EverySwitch/AuthenticatorSwitch.swift:34-38 | Modules/Sources/AppFeature/EverySwitch/SoundMixerSwitch.swift: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) Modules/Sources/AppFeature/Features/Settings/SettingsView/SettingsVM.swift:260— Modules/Sources/AppFeature/Features/Settings/SettingsView/SettingsVM.swift:260-264 | Modules/Sources/AppFeature/Model/Preferences.swift:130-134 — 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.
Off the main sequence: Design — Design: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: DesktopPetSkinKit — DesktopPetSkinKit: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: DisplayDDC — DisplayDDC: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: RemoteCore — RemoteCore: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: Reorderable — Reorderable: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: ScriptEditor — ScriptEditor: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: Extensions — Extensions: abstractness 0.00, instability 0.05, distance 0.95 — zone of pain — concrete and depended on by 19 project(s), so it's rigid to change.
Off the main sequence: PrivilegedHelperCore — PrivilegedHelperCore: abstractness 0.20, instability 0.00, distance 0.80 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×6
Edited copy of a member (11 corresponding lines) Modules/Sources/SoundMixerEQ/EqualizerFeature.swift:112— Modules/Sources/SoundMixerEQ/EqualizerFeature.swift:112-122 | Modules/Sources/SoundMixerEQ/OutputRoutingFeature.swift:93-109 — 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) Modules/Sources/Aphrodite/AphroditeApp.swift:28— Modules/Sources/Aphrodite/AphroditeApp.swift:28-38 | Modules/Sources/Authenticator/AuthenticatorModels.swift:62-73 — 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) Modules/Sources/OnlyRemoteFeature/Features/Dashboard/DashboardFeature.swift:274— Modules/Sources/OnlyRemoteFeature/Features/Dashboard/DashboardFeature.swift:274-290 | Modules/Sources/OnlyRemoteFeature/Features/Settings/SettingsFeature.swift:246-256 — 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) Modules/Sources/Networking/GitHub/GitHubPresenter.swift:52— Modules/Sources/Networking/GitHub/GitHubPresenter.swift:52-66 | Modules/Sources/Networking/GitHub/GitHubPresenter.swift:68-78 — 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) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Messages.swift:104— Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Messages.swift:104-123 | Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Messages.swift:125-135 — 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) Modules/Sources/AppFeature/EverySwitch/DesktopPetSwitch.swift:11— Modules/Sources/AppFeature/EverySwitch/DesktopPetSwitch.swift:11-21 | Modules/Sources/AppFeature/EverySwitch/DockPreviewSwitch.swift:11-21 — 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 (1 corresponding lines) · ×6
Edited copy of a member (1 corresponding lines) Modules/Sources/XcodeCleaner/CleanerBatchConfirmationView.swift:37— Modules/Sources/XcodeCleaner/CleanerBatchConfirmationView.swift:37-37 | Modules/Sources/XcodeCleaner/XcodeCleanerView.swift:200-202 — 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.
Edited copy of a member (1 corresponding lines) Modules/Sources/Aphrodite/SecureAphroditeWebView.swift:174— Modules/Sources/Aphrodite/SecureAphroditeWebView.swift:174-174 | Modules/Sources/WebBrowser/BrowserWebViewDelegate.swift:97-104 — 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.
Edited copy of a member (1 corresponding lines) Modules/Sources/Tailscale/TailscaleCommandRunner.swift:9— Modules/Sources/Tailscale/TailscaleCommandRunner.swift:9-9 | Modules/Sources/XcodeCleaner/XcodeCleanerSimulator.swift:15-15 — 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.
Edited copy of a member (1 corresponding lines) Modules/Sources/AppUninstaller/AppUninstallerFeature.swift:19— Modules/Sources/AppUninstaller/AppUninstallerFeature.swift:19-19 | Modules/Sources/XcodeCleaner/XcodeCleanerFeature.swift:31-31 — 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.
Edited copy of a member (1 corresponding lines) Modules/Sources/Aphrodite/AphroditeAppOrigin.swift:12— Modules/Sources/Aphrodite/AphroditeAppOrigin.swift:12-14 | Modules/Sources/RemoteCore/AphroditeRemoteModels.swift:274-274 — 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.
Edited copy of a member (1 corresponding lines) Modules/Sources/RemoteCore/RemoteSoundMixer.swift:35— Modules/Sources/RemoteCore/RemoteSoundMixer.swift:35-35 | Modules/Sources/SoundMixerEQ/EqualizerSettings.swift:19-21 — 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.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×5
Edited copy of a member (12 corresponding lines) Modules/Sources/XcodeCleaner/XcodeCleanerFeature+Operations.swift:35— Modules/Sources/XcodeCleaner/XcodeCleanerFeature+Operations.swift:35-48 | Modules/Sources/XcodeCleaner/XcodeCleanerFeature+Operations.swift:49-60 — 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) Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerVM+Interaction.swift:81— Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerVM+Interaction.swift:81-94 | Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerVM+Interaction.swift:96-107 — 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) Modules/Sources/Screenshots/ScreenshotEditorView.swift:244— Modules/Sources/Screenshots/ScreenshotEditorView.swift:244-255 | Modules/Sources/Screenshots/ScreenshotsView.swift:197-212 — 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) Modules/Sources/OnlyWidgetFeature/Widgets/Evolution/Intents/EvolutionEntity.swift:21— Modules/Sources/OnlyWidgetFeature/Widgets/Evolution/Intents/EvolutionEntity.swift:21-34 | Modules/Sources/OnlyWidgetFeature/Widgets/Evolution/Intents/EvolutionEntity.swift:45-56 — 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) Modules/Sources/OnlyRemoteFeature/Features/Dashboard/ControlTileStatusBadge.swift:74— Modules/Sources/OnlyRemoteFeature/Features/Dashboard/ControlTileStatusBadge.swift:74-87 | Modules/Sources/OnlyRemoteFeature/Features/Dashboard/ControlTileView.swift:112-123 — 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 (10 lines × 2) Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerPanelView.swift:34— Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerPanelView.swift:34-43 | Modules/Sources/Authenticator/AuthenticatorPanelView.swift:51-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. Read the line range as the matched WINDOW rather than a finished unit: at `Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerPanelView.swift: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 (10 lines × 2) Modules/Sources/DesktopPet/MotionValues.swift:120— Modules/Sources/DesktopPet/MotionValues.swift:120-129 | Modules/Sources/DesktopPet/MotionValues.swift:140-149 — 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 `Modules/Sources/DesktopPet/MotionValues.swift:120` 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) Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift:48— Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift:48-57 | Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageFeature.swift:56-65 — before extracting anything, compare `Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift` and `Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageFeature.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 52 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 `Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift: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 (10 lines × 2) Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteHost+Testing.swift:15— Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteHost+Testing.swift:15-24 | Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteHost.swift:55-64 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteHost+Testing.swift:25` calls `Sendable` and `Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteHost.swift:65` 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) Modules/Sources/AppFeature/EverySwitch/AutohideDockSwitch.swift:16— Modules/Sources/AppFeature/EverySwitch/AutohideDockSwitch.swift:16-25 | Modules/Sources/AppFeature/EverySwitch/AutohideMenuBarSwitch.swift:16-25 — 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 (22 corresponding lines) · ×4
Edited copy of a member (22 corresponding lines) Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteHost+Testing.swift:8— Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteHost+Testing.swift:8-91 | Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession.swift:82-168 — 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.
Edited copy of a member (22 corresponding lines) Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift:73— Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift:73-95 | Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageFeature.swift:81-102 — 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.
Edited copy of a member (22 corresponding lines) Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerPanelView.swift:34— Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerPanelView.swift:34-55 | Modules/Sources/Authenticator/AuthenticatorPanelView.swift:51-72 — 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.
Edited copy of a member (22 corresponding lines) Modules/Sources/OnlyRemoteFeature/Features/Dashboard/ControlTileView.swift:139— Modules/Sources/OnlyRemoteFeature/Features/Dashboard/ControlTileView.swift:139-160 | Modules/Sources/OnlyRemoteFeature/Features/Dashboard/MacPickerView.swift:73-96 — 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 copy of a member (16 corresponding lines) · ×4
Edited copy of a member (16 corresponding lines) Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerService.swift:221— Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerService.swift:221-236 | Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer+Taps.swift:74-97 — 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) Modules/Sources/Screenshots/ScreenCapturePreferences.swift:84— Modules/Sources/Screenshots/ScreenCapturePreferences.swift:84-99 | Modules/Sources/Screenshots/SimulatorScreenshotPreferences.swift:29-45 — 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) Modules/Sources/AppFeature/EverySwitch/MuteMicSwitch.swift:34— Modules/Sources/AppFeature/EverySwitch/MuteMicSwitch.swift:34-49 | Modules/Sources/AppFeature/EverySwitch/MuteSwitch.swift:149-164 — 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) Modules/Sources/AppFeature/Utilities/BluetoothDevicesManager.swift:83— Modules/Sources/AppFeature/Utilities/BluetoothDevicesManager.swift:83-99 | Modules/Sources/AppFeature/Utilities/BluetoothDevicesManager.swift:109-124 — 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 (17 corresponding lines) · ×4
Edited copy of a member (17 corresponding lines) Modules/Sources/XcodeCleaner/XcodeCleanerFileSystem.swift:151— Modules/Sources/XcodeCleaner/XcodeCleanerFileSystem.swift:151-167 | doc/research/xcode-cleaner-scan-benchmark.swift:5-22 — 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) Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteEqualizerView.swift:77— Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteEqualizerView.swift:77-93 | Modules/Sources/SoundMixerEQ/EqualizerView.swift:128-146 — 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) Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:191— Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:191-207 | Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerFeature.swift:319-339 — 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) Modules/Sources/AppFeature/Features/OnlyControl/OnlyControlView.swift:294— Modules/Sources/AppFeature/Features/OnlyControl/OnlyControlView.swift:294-310 | Modules/Sources/AppFeature/Features/OnlySwitchList/OnlySwitchListView.swift:289-305 — 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 (18 corresponding lines) · ×4
Edited copy of a member (18 corresponding lines) Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:172— Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:172-189 | Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerFeature.swift:300-317 — 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) Modules/Sources/AppFeature/Features/OnlyControl/OnlyControlSectionBar.swift:98— Modules/Sources/AppFeature/Features/OnlyControl/OnlyControlSectionBar.swift:98-115 | Modules/Sources/AppFeature/Features/SystemMonitor/SystemMonitorSectionBar.swift:248-267 — 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) Modules/Sources/RadioBrowser/RadioStationArtwork.swift:77— Modules/Sources/RadioBrowser/RadioStationArtwork.swift:77-94 | Modules/Sources/Scheduler/ScheduleSearchField.swift:8-25 — 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) Modules/Sources/AppFeature/AppDelegate.swift:341— Modules/Sources/AppFeature/AppDelegate.swift:341-358 | Modules/Sources/AppFeature/Features/Settings/General/GeneralVM.swift:193-210 — 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.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×4
Edited copy of a member (6 corresponding lines) Modules/Sources/AppUninstaller/AppUninstallerView.swift:157— Modules/Sources/AppUninstaller/AppUninstallerView.swift:157-162 | Modules/Sources/XcodeCleaner/XcodeCleanerView.swift:203-208 — 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) Modules/Sources/AppUninstaller/AppUninstallerView.swift:151— Modules/Sources/AppUninstaller/AppUninstallerView.swift:151-156 | Modules/Sources/Tailscale/TailscaleSettingsView.swift:187-193 — 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) Modules/Sources/AppFeature/Features/SystemMonitor/AppleSiliconMetricsReader.swift:68— Modules/Sources/AppFeature/Features/SystemMonitor/AppleSiliconMetricsReader.swift:68-73 | Modules/Sources/AppFeature/Features/SystemMonitor/AppleSiliconMetricsReader.swift:334-340 — 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) Modules/Sources/Aphrodite/AphroditeEditorView.swift:137— Modules/Sources/Aphrodite/AphroditeEditorView.swift:137-142 | Modules/Sources/Aphrodite/AphroditeViews.swift:123-128 — 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.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×4
Edited copy of a member (10 corresponding lines) Modules/Sources/AppFeature/Player/CommonPlayer/JLASAudioPlayer.swift:147— Modules/Sources/AppFeature/Player/CommonPlayer/JLASAudioPlayer.swift:147-157 | Modules/Sources/AppFeature/Player/CommonPlayer/JLAVAudioPlayer.swift:103-112 — 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) Modules/Sources/RemoteCore/RemoteAction.swift:27— Modules/Sources/RemoteCore/RemoteAction.swift:27-36 | Modules/Sources/RemoteCore/RemoteControlDescriptor.swift:34-44 — 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) Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteHost+Sessions.swift:106— Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteHost+Sessions.swift:106-115 | Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteHost+Sessions.swift:117-127 — 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) Modules/Sources/OnlyRemoteFeature/App/RemoteAppFeature+Selection.swift:101— Modules/Sources/OnlyRemoteFeature/App/RemoteAppFeature+Selection.swift:101-110 | Modules/Sources/OnlyRemoteFeature/Features/SystemMonitor/RemoteSystemMonitorConfigurationFeature.swift:68-78 — 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 copies of one member (3 members, 9+ corresponding lines) · ×4
Edited copies of one member (3 members, 9+ corresponding lines) Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerService.swift:238— Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerService.swift:238-246 | Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerService.swift:261-274 | Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer+CoreAudio.swift:95-109 — 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) Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteCredentialStore+PreparedReplacements.swift:53— Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteCredentialStore+PreparedReplacements.swift:53-66 | Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteCredentialStore+PreparedReplacements.swift:105-116 | Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteCredentialStore.swift:431-439 — 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) Modules/Sources/Scheduler/ScheduleSurface.swift:7— Modules/Sources/Scheduler/ScheduleSurface.swift:7-15 | Modules/Sources/Screenshots/ScreenshotsView.swift:219-227 | Modules/Sources/Screenshots/ScreenshotsView.swift:418-426 — 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) Modules/Sources/OnlyRemoteFeature/Features/SystemMonitor/RemoteSystemMonitorConfigurationView.swift:66— Modules/Sources/OnlyRemoteFeature/Features/SystemMonitor/RemoteSystemMonitorConfigurationView.swift:66-74 | Modules/Sources/OnlyRemoteFeature/Features/SystemMonitor/RemoteSystemMonitorView.swift:316-324 | Modules/Sources/RemoteCore/SystemMonitorModels.swift:22-30 — 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 (13 lines × 2) Modules/Sources/Extensions/KeychainManager.swift:76— Modules/Sources/Extensions/KeychainManager.swift:76-88 | Modules/Sources/Utilities/KeychainManager.swift:76-88 — `Modules/Sources/Extensions/KeychainManager.swift` and `Modules/Sources/Utilities/KeychainManager.swift` 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 74 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 (13 lines × 2) Modules/Sources/OnlyRemoteFeature/App/RemoteAppFeature+Launch.swift:10— Modules/Sources/OnlyRemoteFeature/App/RemoteAppFeature+Launch.swift:10-22 | Modules/Sources/OnlyRemoteFeature/App/RemoteAppFeature+Launch.swift:112-124 — 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 `Modules/Sources/OnlyRemoteFeature/App/RemoteAppFeature+Launch.swift:10` 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) Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:177— Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:177-189 | Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerFeature.swift:305-317 — before extracting anything, compare `Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift` and `Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerFeature.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 86 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 `Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:177` 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) Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessView.swift:45— Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessView.swift:45-57 | Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerView.swift:44-56 — before extracting anything, compare `Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessView.swift` and `Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerView.swift` as WHOLE FILES: this scan already matched 4 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. 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 `Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessView.swift:45` 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) Modules/Sources/AppFeature/Features/Settings/DimScreen/DimScreenSettingView.swift:14— Modules/Sources/AppFeature/Features/Settings/DimScreen/DimScreenSettingView.swift:14-25 | Modules/Sources/AppFeature/Features/Settings/NightShift/NightShiftSettingsView.swift:13-24 — 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 `Modules/Sources/AppFeature/Features/Settings/DimScreen/DimScreenSettingView.swift:14` 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) Modules/Sources/OnlyRemoteFeature/App/RemoteAppFeature+Navigation.swift:147— Modules/Sources/OnlyRemoteFeature/App/RemoteAppFeature+Navigation.swift:147-158 | Modules/Sources/OnlyRemoteFeature/App/RemoteAppFeature+Navigation.swift:161-172 — 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 (12 lines × 2) Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:139— Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:139-150 | Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerFeature.swift:267-278 — before extracting anything, compare `Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift` and `Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerFeature.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 86 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 (12 lines × 2) Modules/Sources/Extensions/KeychainManager.swift:90— Modules/Sources/Extensions/KeychainManager.swift:90-101 | Modules/Sources/Utilities/KeychainManager.swift:90-101 — `Modules/Sources/Extensions/KeychainManager.swift` and `Modules/Sources/Utilities/KeychainManager.swift` 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 74 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.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (4 members, 50+ identical tokens) Modules/Sources/AppFeature/Features/Settings/Radio/RadioSettingView.swift:76— Modules/Sources/AppFeature/Features/Settings/Radio/RadioSettingView.swift:76-84 | Modules/Sources/DisplayBrightness/DisplayBrightnessView.swift:119-126 | Modules/Sources/Screenshots/ScreenshotEditorView.swift:259-267 | Modules/Sources/XcodeCleaner/XcodeCleanerView.swift:221-224 — 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) Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeService.swift:22— Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeService.swift:22-37 | Modules/Sources/OnlyAgent/Settings/GeminiSettings/GeminiService.swift:25-42 | Modules/Sources/OnlyAgent/Settings/OllamaSettings/OllamaRequestService.swift:48-64 | Modules/Sources/OnlyAgent/Settings/OpenAISettings/OpenAIService.swift:30-47 — 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) Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift:117— Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift:117-126 | Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift:127-136 | Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageFeature.swift:124-133 | Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageFeature.swift:134-143 — 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 (15 corresponding lines) · ×3
Edited copy of a member (15 corresponding lines) Modules/Sources/OnlyRemoteFeature/Features/Screenshots/RemoteScreenshotCell.swift:99— Modules/Sources/OnlyRemoteFeature/Features/Screenshots/RemoteScreenshotCell.swift:99-114 | Modules/Sources/Screenshots/ScreenshotsView.swift:378-392 — 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) Modules/Sources/AppFeature/Features/RemoteAccess/Catalog/RemoteCatalogProvider+Live.swift:93— Modules/Sources/AppFeature/Features/RemoteAccess/Catalog/RemoteCatalogProvider+Live.swift:93-111 | Modules/Sources/AppFeature/Features/RemoteAccess/Catalog/RemoteCatalogProvider+Live.swift:132-146 — 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) Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession.swift:250— Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession.swift:250-264 | Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Policies.swift:163-177 — 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 copies of one member (3 members, 7+ corresponding lines) · ×3
Edited copies of one member (3 members, 7+ corresponding lines) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteClientSessionResponses.swift:8— Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteClientSessionResponses.swift:8-14 | Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteClientSessionResponses.swift:42-49 | Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteClientSessionResponses.swift:76-83 — 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) Modules/Sources/OnlyAgent/CodexUsage/CodexUsageService.swift:163— Modules/Sources/OnlyAgent/CodexUsage/CodexUsageService.swift:163-170 | Modules/Sources/OnlyAgent/CodexUsage/CodexUsageService.swift:172-178 | Modules/Sources/OnlyAgent/CodexUsage/CodexUsageService.swift:180-186 — 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) Modules/Sources/OnlyAgent/CodexUsage/CodexAppServerClient.swift:98— Modules/Sources/OnlyAgent/CodexUsage/CodexAppServerClient.swift:98-104 | Modules/Sources/OnlyAgent/CodexUsage/CodexAppServerClient.swift:116-122 | Modules/Sources/OnlyAgent/CodexUsage/CodexAppServerClient.swift:124-130 — 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.
Duplicated block (7 lines × 2) Modules/Sources/AppFeature/EverySwitch/TopNotchSwitch.swift:74— Modules/Sources/AppFeature/EverySwitch/TopNotchSwitch.swift:74-80 | Modules/Sources/AppFeature/Utilities/WallpaperManager.swift:18-24 — 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 (7 lines × 2) Modules/Sources/OnlyRemoteFeature/Dependencies/InMemoryRemotePersistenceStore.swift:147— Modules/Sources/OnlyRemoteFeature/Dependencies/InMemoryRemotePersistenceStore.swift:147-153 | Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteFilePersistenceStore.swift:219-225 — 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) Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer+CoreAudio.swift:34— Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer+CoreAudio.swift:34-40 | Modules/Sources/AppFeature/Features/SystemMonitor/SystemMonitorProcessActivation.swift:88-94 — 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 `Modules/Sources/AppFeature/Features/SystemMonitor/SystemMonitorProcessActivation.swift:88` 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.
FileTooLong: Resources/DarkReader.js Modules/Sources/WebBrowser/Resources/DarkReader.js— FileTooLong — 7415 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 1500 significant lines; this is 5915 over it, 4.94× 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: LaunchCampaign/2026-10-30.html LaunchCampaign/2026-10-30.html— FileTooLong — 522 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: translations (28-523). The bar is 500 significant lines; this is 22 over it, 1.04× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×2
Edited copy of a member (26 corresponding lines) Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:105— Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:105-130 | Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerFeature.swift:218-243 — 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) Modules/Sources/AppFeature/Features/Settings/DesktopPet/DesktopPetControlPicker.swift:12— Modules/Sources/AppFeature/Features/Settings/DesktopPet/DesktopPetControlPicker.swift:12-37 | Modules/Sources/Scheduler/ScheduleTargetPicker.swift:10-35 — 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 (19 corresponding lines) · ×2
Edited copy of a member (19 corresponding lines) Modules/Sources/AppFeature/EverySwitch/KeepAwakeSwitch.swift:125— Modules/Sources/AppFeature/EverySwitch/KeepAwakeSwitch.swift:125-145 | Modules/Sources/AppFeature/EverySwitch/NightShiftSwitch.swift:90-108 — 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) Modules/Sources/AppFeature/Player/MusicAppPlayer/AppleMusic/AppleMusicPlayer/AppleMusicPlayer.swift:47— Modules/Sources/AppFeature/Player/MusicAppPlayer/AppleMusic/AppleMusicPlayer/AppleMusicPlayer.swift:47-68 | Modules/Sources/AppFeature/Player/MusicAppPlayer/Spotify/SpotifyPlayer/SpotifyPlayer.swift:48-66 — 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, 15+ corresponding lines) · ×2
Edited copies of one member (3 members, 15+ corresponding lines) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Commands.swift:10— Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Commands.swift:10-24 | Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Commands.swift:26-44 | Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Commands.swift:46-64 — 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.
Edited copies of one member (3 members, 15+ corresponding lines) Modules/Sources/AppFeature/Features/Settings/DesktopPet/DesktopPetClickActionStorage.swift:10— Modules/Sources/AppFeature/Features/Settings/DesktopPet/DesktopPetClickActionStorage.swift:10-28 | Modules/Sources/Scheduler/ScheduleClients.swift:27-42 | Modules/Sources/WebBrowser/BrowserStorageClient.swift:45-59 — 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 copy of a member (13 corresponding lines) · ×2
Edited copy of a member (13 corresponding lines) Modules/Sources/Extensions/KeychainStorageKey.swift:27— Modules/Sources/Extensions/KeychainStorageKey.swift:27-39 | Modules/Sources/Extensions/KeychainStorageKey.swift:41-58 — 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) Modules/Sources/AppFeature/Features/DisplayBrightness/DisplayBrightnessService.swift:233— Modules/Sources/AppFeature/Features/DisplayBrightness/DisplayBrightnessService.swift:233-245 | Modules/Sources/AppFeature/Features/DisplayBrightness/DisplayBrightnessService.swift:247-260 — 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.
D4 · Code Duplication· Edited copies of one member (3 members, 6+ corresponding lines) · ×2
Edited copies of one member (3 members, 6+ corresponding lines) Modules/Sources/Aphrodite/AphroditeApp.swift:85— Modules/Sources/Aphrodite/AphroditeApp.swift:85-90 | Modules/Sources/Aphrodite/AphroditeIconValidation.swift:5-11 | Modules/Sources/DesktopPetSkinKit/DesktopPetSkinReplyParser.swift:35-40 — 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.
Edited copies of one member (3 members, 6+ corresponding lines) Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteCredentialStore+Keychain.swift:146— Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteCredentialStore+Keychain.swift:146-151 | Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession.swift:308-313 | Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteKeychainClient.swift:183-188 — 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, 10+ corresponding lines) · ×2
Edited copies of one member (3 members, 10+ corresponding lines) Modules/Sources/AppFeature/EverySwitch/TopNotchSwitch.swift:288— Modules/Sources/AppFeature/EverySwitch/TopNotchSwitch.swift:288-297 | Modules/Sources/AppFeature/EverySwitch/TopNotchSwitch.swift:314-323 | Modules/Sources/AppFeature/EverySwitch/TopNotchSwitch.swift:325-337 — 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) Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerService.swift:276— Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerService.swift:276-285 | Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer+CoreAudio.swift:73-82 | Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer+CoreAudio.swift:84-93 — 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, 4+ corresponding lines) · ×2
Edited copies of one member (3 members, 4+ corresponding lines) Modules/Sources/RemoteCore/RemoteScreenshots.swift:114— Modules/Sources/RemoteCore/RemoteScreenshots.swift:114-117 | Modules/Sources/RemoteCore/RemoteScreenshots.swift:151-158 | Modules/Sources/RemoteCore/RemoteScreenshots.swift:244-247 — 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) Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeSharedKey.swift:13— Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeSharedKey.swift:13-16 | Modules/Sources/OnlyAgent/Settings/GeminiSettings/GeminiSharedKey.swift:13-16 | Modules/Sources/OnlyAgent/Settings/OpenAISettings/OpenAISharedKey.swift:13-16 — 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.
Duplicated block (27 lines × 2) Modules/Sources/Extensions/KeychainManager.swift:48— Modules/Sources/Extensions/KeychainManager.swift:48-74 | Modules/Sources/Utilities/KeychainManager.swift:48-74 — `Modules/Sources/Extensions/KeychainManager.swift` and `Modules/Sources/Utilities/KeychainManager.swift` 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 74 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 (27 lines × 2) Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:51— Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:51-77 | Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerFeature.swift:82-108 — before extracting anything, compare `Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift` and `Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerFeature.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 86 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 `Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:51` 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 (15 lines × 2) Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteEqualizerPreset.swift:13— Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteEqualizerPreset.swift:13-27 | Modules/Sources/SoundMixerEQ/EqualizerPreset.swift:14-28 — 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 (15 lines × 2) Modules/Sources/OnlySwitchPersistence/RadioStations+Fetch.swift:61— Modules/Sources/OnlySwitchPersistence/RadioStations+Fetch.swift:61-75 | Modules/Sources/OnlySwitchPersistence/RadioStations+Fetch.swift:85-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. Read the line range as the matched WINDOW rather than a finished unit: at `Modules/Sources/OnlySwitchPersistence/RadioStations+Fetch.swift:61` 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 × 2) Modules/Sources/AppFeature/Features/OnlyControl/OnlyControlSectionBar.swift:122— Modules/Sources/AppFeature/Features/OnlyControl/OnlyControlSectionBar.swift:122-135 | Modules/Sources/AppFeature/Features/SystemMonitor/SystemMonitorSectionBar.swift:270-283 — 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 `Modules/Sources/AppFeature/Features/OnlyControl/OnlyControlSectionBar.swift:122` 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) Modules/Sources/OnlyAgent/Settings/OllamaSettings/OllamaRequestService.swift:91— Modules/Sources/OnlyAgent/Settings/OllamaSettings/OllamaRequestService.swift:91-104 | Modules/Sources/OnlyAgent/Settings/OpenAISettings/OpenAIService.swift:99-112 — 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 `Modules/Sources/OnlyAgent/Settings/OllamaSettings/OllamaRequestService.swift: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 (11 lines × 3) Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessView.swift:17— Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessView.swift:17-27 | Modules/Sources/OnlyRemoteFeature/Features/Screenshots/RemoteScreenshotsView.swift:17-27 | Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerView.swift:18-28 — before extracting anything, compare `Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessView.swift` and `Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerView.swift` as WHOLE FILES: this scan already matched 4 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. 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 `Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessView.swift:17` 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 × 3) Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessView.swift:10— Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessView.swift:10-21 | Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerView.swift:11-22 | Modules/Sources/OnlyRemoteFeature/Features/SystemMonitor/RemoteSystemMonitorView.swift:61-71 — before extracting anything, compare `Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessView.swift` and `Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerView.swift` as WHOLE FILES: this scan already matched 4 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. 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 `Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessView.swift:10` 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, `Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerView.swift:7` calls `Environment` and `Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessView.swift:6` 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.
Sync-over-async blocking Modules/Sources/Extensions/Task++.swift:11— `sleep` is async and calls sleep — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs.
Sync-over-async blocking Modules/Sources/OnlyAgent/Conversation/AgentScriptRunner.swift:57— `runShell` is async and calls .wait() — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs.
AphroditeReducer.body (cyclomatic 102) Modules/Sources/Aphrodite/AphroditeReducer.swift:96— AphroditeReducer.body has cyclomatic complexity 102 (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.
overrideInlineStyle (cyclomatic 86) Modules/Sources/WebBrowser/Resources/DarkReader.js:6261— overrideInlineStyle has cyclomatic complexity 86 (threshold 15). Of this number, 44 points are the body's own statements and 42 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.
RemoteScreenshotsFeature.body (cyclomatic 74) Modules/Sources/OnlyRemoteFeature/Features/Screenshots/RemoteScreenshotsFeature.swift:123— RemoteScreenshotsFeature.body has cyclomatic complexity 74 (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.
PairingFeature.body (cyclomatic 73) Modules/Sources/OnlyRemoteFeature/Features/Pairing/PairingFeature.swift:137— PairingFeature.body has cyclomatic complexity 73 (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.
XcodeCleanerFeature.body (cyclomatic 71) Modules/Sources/XcodeCleaner/XcodeCleanerFeature.swift:58— XcodeCleanerFeature.body has cyclomatic complexity 71 (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.
ScreenshotsFeature.body (cyclomatic 62) Modules/Sources/Screenshots/ScreenshotsFeature.swift:68— ScreenshotsFeature.body 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.
RemoteAppFeature.core (cyclomatic 57) Modules/Sources/OnlyRemoteFeature/App/RemoteAppFeature.swift:178— RemoteAppFeature.core has cyclomatic complexity 57 (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.
TailscaleFeature.body (cyclomatic 56) Modules/Sources/Tailscale/TailscaleFeature.swift:38— TailscaleFeature.body has cyclomatic complexity 56 (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.
DockPreviewFeature.body (cyclomatic 55) Modules/Sources/AppFeature/Features/DockPreview/DockPreviewFeature.swift:67— DockPreviewFeature.body has cyclomatic complexity 55 (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.
RemoteAccessSettingsFeature.body (cyclomatic 51) Modules/Sources/AppFeature/Features/RemoteAccess/Settings/RemoteAccessSettingsFeature.swift:85— RemoteAccessSettingsFeature.body 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.
AppUninstallerFeature.body (cyclomatic 50) Modules/Sources/AppUninstaller/AppUninstallerFeature.swift:33— AppUninstallerFeature.body has cyclomatic complexity 50 (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.
RemoteSoundMixerFeature.body (cyclomatic 50) Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerFeature.swift:82— RemoteSoundMixerFeature.body has cyclomatic complexity 50 (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.
DarkReader.injectProxy (cyclomatic 48) Modules/Sources/WebBrowser/Resources/DarkReader.js:7438— DarkReader.injectProxy has cyclomatic complexity 48 (threshold 15). Most of this is not in the body itself: 6 of the 48 points are its own statements and the rest belongs to 18 function items inside it that branch (reportSheetChangeAsync, a function literal at line 7719, isDRAdoptedSheetOverride, …). 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.
ModelProviderService.liveValue (cyclomatic 47) Modules/Sources/OnlyAgent/ModelProviderService.swift:69— ModelProviderService.liveValue has cyclomatic complexity 47 (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.
RemotePeerSession.handleAuthenticated (cyclomatic 45) Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession+Messages.swift:38— RemotePeerSession.handleAuthenticated has cyclomatic complexity 45 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AgentConversationReducer.reduceExecution (cyclomatic 45) Modules/Sources/OnlyAgent/Conversation/AgentConversationReducer+Execution.swift:10— AgentConversationReducer.reduceExecution has cyclomatic complexity 45 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DashboardFeature.body (cyclomatic 45) Modules/Sources/OnlyRemoteFeature/Features/Dashboard/DashboardFeature.swift:141— DashboardFeature.body has cyclomatic complexity 45 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DarkReader.createStyleSheetModifier.modifySheet (cyclomatic 45) Modules/Sources/WebBrowser/Resources/DarkReader.js:5221— DarkReader.createStyleSheetModifier.modifySheet has cyclomatic complexity 45 (threshold 15). Most of this is not in the body itself: 5 of the 45 points are its own statements and the rest belongs to 13 function items inside it that branch (setRule, a function literal at line 5240, buildStyleSheet::createTarget, …). 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.
createStyleSheetModifier.modifySheet (cyclomatic 45) Modules/Sources/WebBrowser/Resources/DarkReader.js:5221— createStyleSheetModifier.modifySheet has cyclomatic complexity 45 (threshold 15). Most of this is not in the body itself: 5 of the 45 points are its own statements and the rest belongs to 26 function items inside it that branch (setRule, a function literal at line 5240, buildStyleSheet::createTarget, …). 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.
OnlyControlReducer.body (cyclomatic 44) Modules/Sources/AppFeature/Features/OnlyControl/OnlyControlReducer.swift:91— OnlyControlReducer.body has cyclomatic complexity 44 (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.
DisplayBrightnessFeature.body (cyclomatic 44) Modules/Sources/DisplayBrightness/DisplayBrightnessFeature.swift:54— DisplayBrightnessFeature.body has cyclomatic complexity 44 (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.
SettingsFeature.body (cyclomatic 43) Modules/Sources/OnlyRemoteFeature/Features/Settings/SettingsFeature.swift:96— SettingsFeature.body has cyclomatic complexity 43 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
(anonymous) (cyclomatic 43) Modules/Sources/WebBrowser/Resources/DarkReader.js:16— (anonymous) has cyclomatic complexity 43 (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.
TailscaleCoordinator.perform (cyclomatic 38) Modules/Sources/Tailscale/TailscaleCoordinator.swift:43— TailscaleCoordinator.perform has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SchedulesFeature.body (cyclomatic 37) Modules/Sources/Scheduler/SchedulesFeature.swift:82— SchedulesFeature.body has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SystemAudioMixer.outputLayout (cyclomatic 35) Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer+Taps.swift:101— SystemAudioMixer.outputLayout has cyclomatic complexity 35 (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.
RemotePaywallFeature.body (cyclomatic 35) Modules/Sources/OnlyRemoteFeature/Features/Subscription/RemotePaywallFeature.swift:61— RemotePaywallFeature.body has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SoundMixerVM.refresh (cyclomatic 34) Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerVM.swift:222— SoundMixerVM.refresh 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.
RemoteSystemMonitorFeature.body (cyclomatic 34) Modules/Sources/OnlyRemoteFeature/Features/SystemMonitor/RemoteSystemMonitorFeature.swift:36— RemoteSystemMonitorFeature.body 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.
RadioFavoritesFeature.body (cyclomatic 34) Modules/Sources/RadioBrowser/RadioFavoritesFeature.swift:69— RadioFavoritesFeature.body has cyclomatic complexity 34 (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.
DarkReader.watchForStylePositions (cyclomatic 33) Modules/Sources/WebBrowser/Resources/DarkReader.js:8004— DarkReader.watchForStylePositions has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 1 of the 33 points is its own statement and the rest belongs to 18 function items inside it that branch (a function literal at line 8171, a function literal at line 8017, a function literal at line 8058, …). 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.
SystemAudioMixer.setConfiguration (cyclomatic 32) Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer.swift:222— SystemAudioMixer.setConfiguration has cyclomatic complexity 32 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SettingsView.page (cyclomatic 32) Modules/Sources/AppFeature/Features/Settings/SettingsView/SettingsView.swift:97— SettingsView.page has cyclomatic complexity 32 (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.
AgentConversationReducer.body (cyclomatic 32) Modules/Sources/OnlyAgent/Conversation/AgentConversationReducer.swift:142— AgentConversationReducer.body has cyclomatic complexity 32 (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.
RemoteConnectionRuntime.connectWithRetry (cyclomatic 32) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Reconnect.swift:5— RemoteConnectionRuntime.connectWithRetry has cyclomatic complexity 32 (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.
ScreenshotEditorFeature.body (cyclomatic 32) Modules/Sources/Screenshots/ScreenshotEditorFeature.swift:80— ScreenshotEditorFeature.body has cyclomatic complexity 32 (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.
OnlySwitchListView.body (cyclomatic 30) Modules/Sources/AppFeature/Features/OnlySwitchList/OnlySwitchListView.swift:77— OnlySwitchListView.body has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EvolutionReducer.body (cyclomatic 30) Modules/Sources/AppFeature/Features/Settings/Evolution/EvolutionReducer.swift:72— EvolutionReducer.body has cyclomatic complexity 30 (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.
RadioBrowseFeature.body (cyclomatic 29) Modules/Sources/RadioBrowser/RadioBrowseFeature.swift:65— RadioBrowseFeature.body has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
VariablesStore.getModifierForVarDependant (cyclomatic 29) Modules/Sources/WebBrowser/Resources/DarkReader.js:4452— VariablesStore.getModifierForVarDependant has cyclomatic complexity 29 (threshold 15). Of this number, 15 points are the body's own statements and 14 belong to 7 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.
DarkReader.getRGBValues (cyclomatic 29) Modules/Sources/WebBrowser/Resources/DarkReader.js:1178— DarkReader.getRGBValues has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RemoteConnectionRuntime.handle (cyclomatic 28) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Messages.swift:5— RemoteConnectionRuntime.handle 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.
RemoteConnectionRuntime.preparePairing (cyclomatic 28) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Pairing.swift:5— RemoteConnectionRuntime.preparePairing 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.
HostedAudioPlayer.startHelper (cyclomatic 27) Modules/Sources/AppFeature/Player/CommonPlayer/HostedAudioPlayer.swift:151— HostedAudioPlayer.startHelper has cyclomatic complexity 27 (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.
PlaybackHelperEngine.perform (cyclomatic 27) Modules/Sources/AppFeature/Player/CommonPlayer/PlaybackHelperEngine.swift:26— PlaybackHelperEngine.perform 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.
ShortcutsSettingsReducer.body (cyclomatic 27) Modules/Sources/AppFeature/Features/Settings/Shortcuts/ShortcutsSettingsReducer.swift:64— ShortcutsSettingsReducer.body 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.
DashboardFeature.handleConnectionEvent (cyclomatic 27) Modules/Sources/OnlyRemoteFeature/Features/Dashboard/DashboardFeature+ConnectionEvents.swift:6— DashboardFeature.handleConnectionEvent has cyclomatic complexity 27 (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.
BrowserFeature.body (cyclomatic 27) Modules/Sources/WebBrowser/BrowserFeature.swift:62— BrowserFeature.body 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.
RemoteScreenshotsProvider.service (cyclomatic 26) Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteScreenshotsProvider.swift:31— RemoteScreenshotsProvider.service 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.
GlobalSettingsFeature.features (cyclomatic 26) Modules/Sources/OnlyRemoteFeature/Features/Settings/GlobalSettingsFeature.swift:75— GlobalSettingsFeature.features 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.
AphroditeRemoteSVGValidationDelegate.validAttribute (cyclomatic 26) Modules/Sources/RemoteCore/AphroditeRemoteModels.swift:64— AphroditeRemoteSVGValidationDelegate.validAttribute has cyclomatic complexity 26 (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.
OnlyRemoteCampaignFeature.body (cyclomatic 25) Modules/Sources/AppFeature/Features/RemoteAccess/Campaign/OnlyRemoteCampaignFeature.swift:27— OnlyRemoteCampaignFeature.body 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.
RemoteCodexUsageFeature.body (cyclomatic 25) Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageFeature.swift:33— RemoteCodexUsageFeature.body 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.
DesktopPetAgentLogMonitor.discover (cyclomatic 24) Modules/Sources/DesktopPet/DesktopPetAgentLogMonitor.swift:175— DesktopPetAgentLogMonitor.discover has cyclomatic complexity 24 (threshold 15). Of this number, 14 points are the body's own statements and 10 belong to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
XcodeCleanerSimulator.inventory (cyclomatic 24) Modules/Sources/XcodeCleaner/XcodeCleanerSimulator.swift:102— XcodeCleanerSimulator.inventory 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.
DarkReader.getModifiableCSSDeclaration (cyclomatic 24) Modules/Sources/WebBrowser/Resources/DarkReader.js:3370— DarkReader.getModifiableCSSDeclaration has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DarkReader.getBgImageModifier::getBgImageValue (cyclomatic 24) Modules/Sources/WebBrowser/Resources/DarkReader.js:3961— DarkReader.getBgImageModifier::getBgImageValue has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
watchForNodePosition (cyclomatic 24) Modules/Sources/WebBrowser/Resources/DarkReader.js:1724— watchForNodePosition has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 4 of the 24 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 1743, 1814, 1758). 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.
DisplayBrightnessKeyTap.handle (cyclomatic 23) Modules/Sources/AppFeature/Features/DisplayBrightness/DisplayBrightnessKeyTap.swift:122— DisplayBrightnessKeyTap.handle 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.
SoundMixerVM.applyOutputRoute (cyclomatic 23) Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerVM.swift:365— SoundMixerVM.applyOutputRoute 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.
RemoteCatalogProvider.init (cyclomatic 23) Modules/Sources/AppFeature/Features/RemoteAccess/Catalog/RemoteCatalogProvider+Live.swift:7— RemoteCatalogProvider.init has cyclomatic complexity 23 (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.
DesktopPetPlaybackFeature.body (cyclomatic 23) Modules/Sources/DesktopPet/DesktopPetPlaybackFeature.swift:39— DesktopPetPlaybackFeature.body 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.
ClaudeUsageView.content (cyclomatic 23) Modules/Sources/OnlyAgent/ClaudeUsage/ClaudeUsageView.swift:17— ClaudeUsageView.content 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.
CodexUsageView.content (cyclomatic 23) Modules/Sources/OnlyAgent/CodexUsage/CodexUsageView.swift:22— CodexUsageView.content 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.
RemoteAppView.body (cyclomatic 23) Modules/Sources/OnlyRemoteFeature/App/RemoteAppView.swift:8— RemoteAppView.body 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.
RemoteReviewDemoRuntime.sendSoundMixer (cyclomatic 23) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteReviewDemoClient.swift:170— RemoteReviewDemoRuntime.sendSoundMixer has cyclomatic complexity 23 (threshold 15). Of this number, 22 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DarkReader.getInversionStyleValue (cyclomatic 23) Modules/Sources/WebBrowser/Resources/DarkReader.js:8384— DarkReader.getInversionStyleValue has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 2 of the 23 points are its own statements and the rest belongs to 6 function items inside it that branch (buildGroupRules, buildInversionRules, appendRule, …). 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.
MacSystemMonitorCollector.sampleForStream (cyclomatic 22) Modules/Sources/AppFeature/Features/SystemMonitor/MacSystemMonitorCollector.swift:191— MacSystemMonitorCollector.sampleForStream has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AppUninstallerFileSystem.scan (cyclomatic 22) Modules/Sources/AppUninstaller/AppUninstallerFileSystem.swift:30— AppUninstallerFileSystem.scan has cyclomatic complexity 22 (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.
AppUninstallerFileSystem.validate (cyclomatic 22) Modules/Sources/AppUninstaller/AppUninstallerFileSystem.swift:127— AppUninstallerFileSystem.validate has cyclomatic complexity 22 (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.
DesktopPetSkinsFeature.reduceGenerator (cyclomatic 21) Modules/Sources/AppFeature/Features/Settings/DesktopPet/DesktopPetSkinsFeature.swift:127— DesktopPetSkinsFeature.reduceGenerator has cyclomatic complexity 21 (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.
NSSound.setSystemVolume (cyclomatic 21) Modules/Sources/Extensions/NSSound_SystemVolumeExtension.swift:159— NSSound.setSystemVolume 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.
RemoteClaudeUsageFeature.body (cyclomatic 21) Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift:32— RemoteClaudeUsageFeature.body has cyclomatic complexity 21 (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.
RemoteScreenshotsFeature.handle (cyclomatic 21) Modules/Sources/OnlyRemoteFeature/Features/Screenshots/RemoteScreenshotsFeature+Effects.swift:8— RemoteScreenshotsFeature.handle 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.
EvolutionEditorReducer.reduceGeneration (cyclomatic 20) Modules/Sources/AppFeature/Features/Settings/Evolution/EvolutionEditor/EvolutionEditorReducer+Generation.swift:43— EvolutionEditorReducer.reduceGeneration has cyclomatic complexity 20 (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.
DesktopPetAgentLogMonitor.scan (cyclomatic 20) Modules/Sources/DesktopPet/DesktopPetAgentLogMonitor.swift:67— DesktopPetAgentLogMonitor.scan 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.
BrightnessCoordinator.apply (cyclomatic 20) Modules/Sources/DisplayBrightness/BrightnessCoordinator.swift:39— BrightnessCoordinator.apply 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.
ClaudeCodeCLI.signIn (cyclomatic 20) Modules/Sources/OnlyAgent/ClaudeUsage/ClaudeCodeCLI.swift:66— ClaudeCodeCLI.signIn has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PersistenceController.init (cyclomatic 20) Modules/Sources/OnlySwitchPersistence/Persistence.swift:23— PersistenceController.init 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.
ScriptTokenizer.tokens (cyclomatic 20) Modules/Sources/ScriptEditor/ScriptTokenizer.swift:41— ScriptTokenizer.tokens 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.
BrowserFeature.reduceBookmarks (cyclomatic 20) Modules/Sources/WebBrowser/BrowserFeature+Bookmarks.swift:18— BrowserFeature.reduceBookmarks has cyclomatic complexity 20 (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.
XcodeCleanerFileSystem.clean (cyclomatic 20) Modules/Sources/XcodeCleaner/XcodeCleanerFileSystem.swift:54— XcodeCleanerFileSystem.clean 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.
DarkReader.parse (cyclomatic 20) Modules/Sources/WebBrowser/Resources/DarkReader.js:1059— DarkReader.parse has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DarkReader.createOrUpdateDynamicThemeInternal (cyclomatic 20) Modules/Sources/WebBrowser/Resources/DarkReader.js:9042— DarkReader.createOrUpdateDynamicThemeInternal has cyclomatic complexity 20 (threshold 15). Of this number, 16 points are the body's own statements and 4 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.
SwitchManager.visibleTypesIncludingNewDiscoveries (cyclomatic 19) Modules/Sources/AppFeature/EverySwitch/SwitchManager.swift:112— SwitchManager.visibleTypesIncludingNewDiscoveries 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.
CrashReportDiscovery.latest (cyclomatic 19) Modules/Sources/AppFeature/Features/CrashReports/CrashReportDiscovery.swift:21— CrashReportDiscovery.latest has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DisplayBrightnessService.pollNative (cyclomatic 19) Modules/Sources/AppFeature/Features/DisplayBrightness/DisplayBrightnessService.swift:282— DisplayBrightnessService.pollNative 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.
SoundMixerVM.applyEqualizer (cyclomatic 19) Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerVM.swift:332— SoundMixerVM.applyEqualizer 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.
SystemAudioMixer.audioPlayingApps (cyclomatic 19) Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer.swift:175— SystemAudioMixer.audioPlayingApps 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.
EvolutionAdapter.toEvolutionItem (cyclomatic 19) Modules/Sources/AppFeature/Features/Settings/Evolution/EvolutionAdapter.swift:22— EvolutionAdapter.toEvolutionItem has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DesktopPetAgentLogParser.claude (cyclomatic 19) Modules/Sources/DesktopPet/DesktopPetAgentLogParser.swift:76— DesktopPetAgentLogParser.claude 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.
RemoteConnectionRuntime.updateDiscovery (cyclomatic 19) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Discovery.swift:6— RemoteConnectionRuntime.updateDiscovery has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
RemoteBrightnessFeature.body (cyclomatic 19) Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:51— RemoteBrightnessFeature.body has cyclomatic complexity 19 (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.
EvolutionCommandEntity.addItem (cyclomatic 19) Modules/Sources/AppFeature/CoreData/EvolutionCommandEntityLive.swift:58— EvolutionCommandEntity.addItem has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ScreenshotEditorFeature.commitDraft (cyclomatic 19) Modules/Sources/Screenshots/ScreenshotEditorFeature.swift:206— ScreenshotEditorFeature.commitDraft 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, 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.
DarkReader.getNumbersFromString (cyclomatic 19) Modules/Sources/WebBrowser/Resources/DarkReader.js:1125— DarkReader.getNumbersFromString has cyclomatic complexity 19 (threshold 15). Of this number, 15 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SystemAXMenuBarSource.systemItemKind (cyclomatic 18) Modules/Sources/AppFeature/StatusBar/MenuBarAccessibilityItemResolver.swift:352— SystemAXMenuBarSource.systemItemKind 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.
EvolutionEditorReducer.body (cyclomatic 18) Modules/Sources/AppFeature/Features/Settings/Evolution/EvolutionEditor/EvolutionEditorReducer.swift:91— EvolutionEditorReducer.body has cyclomatic complexity 18 (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.
DesktopPetAgentActivityFeature.apply (cyclomatic 18) Modules/Sources/DesktopPet/DesktopPetAgentActivityFeature.swift:87— DesktopPetAgentActivityFeature.apply 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.
ClaudeUsageReducer.body (cyclomatic 18) Modules/Sources/OnlyAgent/ClaudeUsage/ClaudeUsageReducer.swift:37— ClaudeUsageReducer.body has cyclomatic complexity 18 (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.
RemoteConnectionRuntime.recoverPreparedPairingIfNeeded (cyclomatic 18) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Reconnect.swift:117— RemoteConnectionRuntime.recoverPreparedPairingIfNeeded 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.
RadioStationsFeature.body (cyclomatic 18) Modules/Sources/RadioBrowser/RadioStationsFeature.swift:42— RadioStationsFeature.body has cyclomatic complexity 18 (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.
OutputRoutingFeature.body (cyclomatic 18) Modules/Sources/SoundMixerEQ/OutputRoutingFeature.swift:37— OutputRoutingFeature.body has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
CleanerCoordinator.clean (cyclomatic 18) Modules/Sources/XcodeCleaner/XcodeCleanerClient.swift:75— CleanerCoordinator.clean has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
DarkReader.manageStyle.getRulesAsync (cyclomatic 18) Modules/Sources/WebBrowser/Resources/DarkReader.js:7058— DarkReader.manageStyle.getRulesAsync 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.
manageStyle.getRulesAsync (cyclomatic 18) Modules/Sources/WebBrowser/Resources/DarkReader.js:7058— manageStyle.getRulesAsync 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.
OnlySwitchApp.body (cyclomatic 17) Modules/Sources/AppFeature/OnlySwitchApp.swift:30— OnlySwitchApp.body has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PlaybackHelperEngine.streamer (cyclomatic 17) Modules/Sources/AppFeature/Player/CommonPlayer/PlaybackHelperEngine.swift:156— PlaybackHelperEngine.streamer has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
RemotePeerSession.completePairing (cyclomatic 17) Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession+Pairing.swift:7— RemotePeerSession.completePairing has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
AgentSystemInfo.promptDescription (cyclomatic 17) Modules/Sources/OnlyAgent/Conversation/AgentSystemInfo.swift:59— AgentSystemInfo.promptDescription has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
RemoteConnectionRuntime.abortPairing (cyclomatic 17) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Pairing.swift:253— RemoteConnectionRuntime.abortPairing has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SettingsFeature.handleConnectionEvent (cyclomatic 17) Modules/Sources/OnlyRemoteFeature/Features/Settings/SettingsFeature.swift:258— SettingsFeature.handleConnectionEvent has cyclomatic complexity 17 (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.
RadioFavoriteRow.body (cyclomatic 17) Modules/Sources/RadioBrowser/RadioFavoritesView.swift:77— RadioFavoriteRow.body has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ScreenshotCell.body (cyclomatic 17) Modules/Sources/Screenshots/ScreenshotsView.swift:274— ScreenshotCell.body has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SystemMonitorReducer.body (cyclomatic 17) Modules/Sources/SystemMonitor/SystemMonitorReducer.swift:59— SystemMonitorReducer.body 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.
XcodeCleanerFileSystem.removeEntry (cyclomatic 17) Modules/Sources/XcodeCleaner/XcodeCleanerFileSystem.swift:114— XcodeCleanerFileSystem.removeEntry 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.
getImageDetails (cyclomatic 17) Modules/Sources/WebBrowser/Resources/DarkReader.js:2950— getImageDetails has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 2951, 3015, 2997, …). 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.
OnlySwitchListView.singleSwitchList (cyclomatic 16) Modules/Sources/AppFeature/Features/OnlySwitchList/OnlySwitchListView+Lists.swift:13— OnlySwitchListView.singleSwitchList 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.
SystemAudioMixer.makeAppTap (cyclomatic 16) Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer+Taps.swift:9— SystemAudioMixer.makeAppTap 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.
RemotePeerSession.handshake (cyclomatic 16) Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession+Handshake.swift:7— RemotePeerSession.handshake 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.
DesktopPetAgentLogMonitor.updateCodexInventory (cyclomatic 16) Modules/Sources/DesktopPet/DesktopPetAgentLogMonitor.swift:265— DesktopPetAgentLogMonitor.updateCodexInventory 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.
DesktopPetMotion.values (cyclomatic 16) Modules/Sources/DesktopPet/MotionValues.swift:57— DesktopPetMotion.values 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.
BrightnessKeyRoutingState.route (cyclomatic 16) Modules/Sources/DisplayBrightness/BrightnessKeyPolicy.swift:59— BrightnessKeyRoutingState.route 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.
AgentPromptBuilder.serialize (cyclomatic 16) Modules/Sources/OnlyAgent/Conversation/AgentPromptBuilder.swift:65— AgentPromptBuilder.serialize has cyclomatic complexity 16 (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.
ClaudeLive.chatStream (cyclomatic 16) Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeService.swift:39— ClaudeLive.chatStream has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
CodexRuntimePool.chatStream (cyclomatic 16) Modules/Sources/OnlyAgent/Settings/CodexSettings/CodexService.swift:142— CodexRuntimePool.chatStream 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.
DashboardReducer.body (cyclomatic 16) Modules/Sources/OnlyControl/DashboardReducer.swift:38— DashboardReducer.body 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.
RemoteAppFeature.reduceConnectionEvent (cyclomatic 16) Modules/Sources/OnlyRemoteFeature/App/RemoteAppFeature+Launch.swift:104— RemoteAppFeature.reduceConnectionEvent 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.
RemoteScreenshotResponses.consume (cyclomatic 16) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteScreenshotResponses.swift:97— RemoteScreenshotResponses.consume 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.
PairingView.body (cyclomatic 16) Modules/Sources/OnlyRemoteFeature/Features/Pairing/PairingView.swift:7— PairingView.body 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.
TailscaleConnection.validatedIPAddress (cyclomatic 16) Modules/Sources/Tailscale/TailscaleModels.swift:58— TailscaleConnection.validatedIPAddress 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.
DarkReader.watchForNodePosition.restore (cyclomatic 16) Modules/Sources/WebBrowser/Resources/DarkReader.js:1743— DarkReader.watchForNodePosition.restore 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.
DarkReader.iterateCSSRules (cyclomatic 16) Modules/Sources/WebBrowser/Resources/DarkReader.js:2025— DarkReader.iterateCSSRules has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 2031, 2060). 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.
DarkReader.isFallbackResolved (cyclomatic 16) Modules/Sources/WebBrowser/Resources/DarkReader.js:5023— DarkReader.isFallbackResolved 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.
overrideInlineStyle (cognitive 131) Modules/Sources/WebBrowser/Resources/DarkReader.js:6261— overrideInlineStyle has cognitive complexity 131 (threshold 15). Drivers by points: if/else 51 (89 pts), boolean chains 26, ternaries 6 (13 pts), other 3 (nesting depth added 45). Of this number, 64 points are the body's own statements and 67 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.
AphroditeReducer.body (cognitive 106) Modules/Sources/Aphrodite/AphroditeReducer.swift:96— AphroditeReducer.body has cognitive complexity 106 (threshold 15). Drivers by points: if/else 27 (56 pts), error handling 12 (24 pts), boolean chains 20, ternaries 2 (5 pts), match/switch 1 (nesting depth added 44). 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.
PairingFeature.body (cognitive 98) Modules/Sources/OnlyRemoteFeature/Features/Pairing/PairingFeature.swift:137— PairingFeature.body has cognitive complexity 98 (threshold 15). Drivers by points: if/else 24 (57 pts), boolean chains 18, error handling 5 (10 pts), match/switch 4 (7 pts), loops 1 (3 pts), ternaries 1 (3 pts) (nesting depth added 45). 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.
RemoteScreenshotsFeature.body (cognitive 82) Modules/Sources/OnlyRemoteFeature/Features/Screenshots/RemoteScreenshotsFeature.swift:123— RemoteScreenshotsFeature.body has cognitive complexity 82 (threshold 15). Drivers by points: if/else 27 (55 pts), boolean chains 14, error handling 3 (6 pts), match/switch 2 (3 pts), loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 34). 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.
DockPreviewFeature.body (cognitive 77) Modules/Sources/AppFeature/Features/DockPreview/DockPreviewFeature.swift:67— DockPreviewFeature.body has cognitive complexity 77 (threshold 15). Drivers by points: if/else 19 (42 pts), error handling 5 (14 pts), boolean chains 10, ternaries 2 (5 pts), loops 1 (3 pts), match/switch 2 (3 pts) (nesting depth added 38). 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.
XcodeCleanerFeature.body (cognitive 73) Modules/Sources/XcodeCleaner/XcodeCleanerFeature.swift:58— XcodeCleanerFeature.body has cognitive complexity 73 (threshold 15). Drivers by points: if/else 21 (42 pts), boolean chains 21, match/switch 4 (7 pts), ternaries 1 (3 pts) (nesting depth added 26). 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.
ScreenshotsFeature.body (cognitive 72) Modules/Sources/Screenshots/ScreenshotsFeature.swift:68— ScreenshotsFeature.body has cognitive complexity 72 (threshold 15). Drivers by points: if/else 25 (50 pts), ternaries 3 (7 pts), error handling 3 (6 pts), boolean chains 4, loops 2 (4 pts), match/switch 1 (nesting depth added 34). 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.
getRGBValues (cognitive 69) Modules/Sources/WebBrowser/Resources/DarkReader.js:1178— getRGBValues has cognitive complexity 69 (threshold 15). Drivers by points: if/else 22 (59 pts), boolean chains 6, ternaries 1 (3 pts), loops 1 (nesting depth added 39). 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.
RemoteConnectionRuntime.connectWithRetry (cognitive 68) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Reconnect.swift:5— RemoteConnectionRuntime.connectWithRetry has cognitive complexity 68 (threshold 15). Drivers by points: if/else 11 (36 pts), error handling 5 (15 pts), boolean chains 13, loops 2 (4 pts) (nesting depth added 37). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TailscaleFeature.body (cognitive 57) Modules/Sources/Tailscale/TailscaleFeature.swift:38— TailscaleFeature.body has cognitive complexity 57 (threshold 15). Drivers by points: if/else 18 (38 pts), boolean chains 14, match/switch 2 (3 pts), ternaries 1 (2 pts) (nesting depth added 22). 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.
DarkReader.injectProxy (cognitive 57) Modules/Sources/WebBrowser/Resources/DarkReader.js:7438— DarkReader.injectProxy has cognitive complexity 57 (threshold 15). Drivers by points: if/else 30 (40 pts), boolean chains 12, loops 3 (5 pts) (nesting depth added 12). Most of this is not in the body itself: 5 of the 57 points are its own statements and the rest belongs to 18 function items inside it that branch (reportSheetChangeAsync, a function literal at line 7719, isDRAdoptedSheetOverride, …). 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.
AppUninstallerFeature.body (cognitive 55) Modules/Sources/AppUninstaller/AppUninstallerFeature.swift:33— AppUninstallerFeature.body has cognitive complexity 55 (threshold 15). Drivers by points: if/else 16 (32 pts), boolean chains 12, error handling 3 (6 pts), match/switch 3 (5 pts) (nesting depth added 21). 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.
AgentConversationReducer.reduceExecution (cognitive 54) Modules/Sources/OnlyAgent/Conversation/AgentConversationReducer+Execution.swift:10— AgentConversationReducer.reduceExecution has cognitive complexity 54 (threshold 15). Drivers by points: if/else 17 (35 pts), boolean chains 7, loops 2 (4 pts), match/switch 2 (3 pts), ternaries 1 (3 pts), error handling 1 (2 pts) (nesting depth added 24). 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.
XcodeCleanerSimulator.inventory (cognitive 52) Modules/Sources/XcodeCleaner/XcodeCleanerSimulator.swift:102— XcodeCleanerSimulator.inventory has cognitive complexity 52 (threshold 15). Drivers by points: if/else 7 (24 pts), ternaries 3 (11 pts), loops 3 (7 pts), boolean chains 6, error handling 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.
RemotePeerSession.handleAuthenticated (cognitive 50) Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession+Messages.swift:38— RemotePeerSession.handleAuthenticated has cognitive complexity 50 (threshold 15). Drivers by points: if/else 26 (46 pts), boolean chains 3, match/switch 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
createStyleSheetModifier.modifySheet (cognitive 50) Modules/Sources/WebBrowser/Resources/DarkReader.js:5221— createStyleSheetModifier.modifySheet has cognitive complexity 50 (threshold 15). Drivers by points: if/else 32 (34 pts), boolean chains 10, ternaries 2 (5 pts), loops 1 (nesting depth added 5). Most of this is not in the body itself: 3 of the 50 points are its own statements and the rest belongs to 26 function items inside it that branch (setRule, a function literal at line 5240, a function literal at line 5474, …). 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.
DesktopPetAgentLogMonitor.scan (cognitive 49) Modules/Sources/DesktopPet/DesktopPetAgentLogMonitor.swift:67— DesktopPetAgentLogMonitor.scan has cognitive complexity 49 (threshold 15). Drivers by points: if/else 14 (40 pts), loops 3 (5 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DisplayBrightnessFeature.body (cognitive 48) Modules/Sources/DisplayBrightness/DisplayBrightnessFeature.swift:54— DisplayBrightnessFeature.body has cognitive complexity 48 (threshold 15). Drivers by points: if/else 15 (31 pts), error handling 4 (8 pts), boolean chains 6, loops 1 (2 pts), match/switch 1 (nesting depth added 21). 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.
SettingsFeature.body (cognitive 48) Modules/Sources/OnlyRemoteFeature/Features/Settings/SettingsFeature.swift:96— SettingsFeature.body has cognitive complexity 48 (threshold 15). Drivers by points: if/else 17 (35 pts), boolean chains 8, match/switch 2 (3 pts), ternaries 1 (2 pts) (nesting depth added 20). 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.
RemoteSoundMixerFeature.body (cognitive 48) Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerFeature.swift:82— RemoteSoundMixerFeature.body has cognitive complexity 48 (threshold 15). Drivers by points: if/else 15 (29 pts), boolean chains 18, match/switch 1 (nesting depth added 14). 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.
SoundMixerVM.refresh (cognitive 47) Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerVM.swift:222— SoundMixerVM.refresh has cognitive complexity 47 (threshold 15). Drivers by points: if/else 19 (27 pts), boolean chains 13, 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.
RemoteAccessSettingsFeature.body (cognitive 46) Modules/Sources/AppFeature/Features/RemoteAccess/Settings/RemoteAccessSettingsFeature.swift:85— RemoteAccessSettingsFeature.body has cognitive complexity 46 (threshold 15). Drivers by points: if/else 16 (33 pts), error handling 3 (6 pts), match/switch 2 (3 pts), loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 23). 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.
RemoteSystemMonitorFeature.body (cognitive 46) Modules/Sources/OnlyRemoteFeature/Features/SystemMonitor/RemoteSystemMonitorFeature.swift:36— RemoteSystemMonitorFeature.body has cognitive complexity 46 (threshold 15). Drivers by points: if/else 16 (38 pts), boolean chains 5, match/switch 2 (3 pts) (nesting depth added 23). 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.
DarkReader.createStyleSheetModifier.modifySheet (cognitive 46) Modules/Sources/WebBrowser/Resources/DarkReader.js:5221— DarkReader.createStyleSheetModifier.modifySheet has cognitive complexity 46 (threshold 15). Drivers by points: if/else 31 (33 pts), boolean chains 10, ternaries 1 (2 pts), loops 1 (nesting depth added 3). Most of this is not in the body itself: 3 of the 46 points are its own statements and the rest belongs to 13 function items inside it that branch (setRule, a function literal at line 5240, a function literal at line 5474, …). 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.
RemotePaywallFeature.body (cognitive 45) Modules/Sources/OnlyRemoteFeature/Features/Subscription/RemotePaywallFeature.swift:61— RemotePaywallFeature.body has cognitive complexity 45 (threshold 15). Drivers by points: if/else 10 (22 pts), error handling 7 (14 pts), ternaries 3 (6 pts), boolean chains 2, match/switch 1 (nesting depth added 22). 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.
getModifierForVarDependant (cognitive 44) Modules/Sources/WebBrowser/Resources/DarkReader.js:4452— getModifierForVarDependant has cognitive complexity 44 (threshold 15). Drivers by points: if/else 13 (22 pts), ternaries 6 (13 pts), boolean chains 6, loops 1 (3 pts) (nesting depth added 18). Most of this is not in the body itself: 12 of the 44 points are its own statements and the rest belongs to 16 function items inside it that branch (a function literal at line 4463, a function literal at line 4517, (anonymous)::modify, …). 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.
TailscaleCoordinator.perform (cognitive 43) Modules/Sources/Tailscale/TailscaleCoordinator.swift:43— TailscaleCoordinator.perform has cognitive complexity 43 (threshold 15). Drivers by points: if/else 20 (34 pts), boolean chains 3, ternaries 1 (3 pts), match/switch 2, loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XcodeCleanerFileSystem.clean (cognitive 43) Modules/Sources/XcodeCleaner/XcodeCleanerFileSystem.swift:54— XcodeCleanerFileSystem.clean has cognitive complexity 43 (threshold 15). Drivers by points: if/else 8 (22 pts), error handling 4 (12 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous) (cognitive 43) Modules/Sources/WebBrowser/Resources/DarkReader.js:16— (anonymous) has cognitive complexity 43 (threshold 15). Drivers by points: boolean chains 23, ternaries 12, if/else 8. 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.
OnlyControlReducer.body (cognitive 42) Modules/Sources/AppFeature/Features/OnlyControl/OnlyControlReducer.swift:91— OnlyControlReducer.body has cognitive complexity 42 (threshold 15). Drivers by points: if/else 12 (22 pts), boolean chains 9, loops 3 (6 pts), ternaries 2 (4 pts), match/switch 1 (nesting depth added 15). 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.
DashboardFeature.body (cognitive 42) Modules/Sources/OnlyRemoteFeature/Features/Dashboard/DashboardFeature.swift:141— DashboardFeature.body has cognitive complexity 42 (threshold 15). Drivers by points: if/else 15 (30 pts), boolean chains 11, match/switch 1 (nesting depth added 15). 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.
RemoteAppView.body (cognitive 41) Modules/Sources/OnlyRemoteFeature/App/RemoteAppView.swift:8— RemoteAppView.body has cognitive complexity 41 (threshold 15). Drivers by points: if/else 18 (31 pts), ternaries 2 (6 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CodexUsageView.content (cognitive 39) Modules/Sources/OnlyAgent/CodexUsage/CodexUsageView.swift:22— CodexUsageView.content has cognitive complexity 39 (threshold 15). Drivers by points: if/else 18 (33 pts), match/switch 2 (4 pts), boolean chains 2 (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.
SystemAudioMixer.outputLayout (cognitive 37) Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer+Taps.swift:101— SystemAudioMixer.outputLayout has cognitive complexity 37 (threshold 15). Drivers by points: boolean chains 22, if/else 9 (11 pts), loops 2, ternaries 1 (2 pts) (nesting depth added 3). 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.
PlaybackHelperEngine.perform (cognitive 37) Modules/Sources/AppFeature/Player/CommonPlayer/PlaybackHelperEngine.swift:26— PlaybackHelperEngine.perform has cognitive complexity 37 (threshold 15). Drivers by points: if/else 9 (24 pts), boolean chains 12, match/switch 1 (nesting depth added 15). 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.
DarkReader.watchForStylePositions (cognitive 37) Modules/Sources/WebBrowser/Resources/DarkReader.js:8004— DarkReader.watchForStylePositions has cognitive complexity 37 (threshold 15). Drivers by points: if/else 24 (28 pts), boolean chains 8, loops 1 (nesting depth added 4). None of this is in the body itself: all 37 points belong to 18 function items inside it that branch (a function literal at line 8058, a function literal at line 8171, a function literal at line 8017, …). 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.
SystemAudioMixer.setConfiguration (cognitive 36) Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer.swift:222— SystemAudioMixer.setConfiguration has cognitive complexity 36 (threshold 15). Drivers by points: if/else 18 (23 pts), boolean chains 10, ternaries 2, loops 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.
ModelProviderService.liveValue (cognitive 36) Modules/Sources/OnlyAgent/ModelProviderService.swift:69— ModelProviderService.liveValue has cognitive complexity 36 (threshold 15). Drivers by points: match/switch 8 (17 pts), if/else 5 (10 pts), loops 2 (4 pts), ternaries 1 (4 pts), boolean chains 1 (nesting depth added 19). 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.
SchedulesFeature.body (cognitive 36) Modules/Sources/Scheduler/SchedulesFeature.swift:82— SchedulesFeature.body has cognitive complexity 36 (threshold 15). Drivers by points: if/else 16 (29 pts), match/switch 2 (3 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 15). 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.
RemoteScreenshotsProvider.service (cognitive 34) Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteScreenshotsProvider.swift:31— RemoteScreenshotsProvider.service has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 12, loops 3 (5 pts), ternaries 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RadioBrowseFeature.body (cognitive 34) Modules/Sources/RadioBrowser/RadioBrowseFeature.swift:65— RadioBrowseFeature.body has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (25 pts), loops 1 (4 pts), match/switch 2 (3 pts), boolean chains 2 (nesting depth added 17). 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.
RadioFavoritesFeature.body (cognitive 34) Modules/Sources/RadioBrowser/RadioFavoritesFeature.swift:69— RadioFavoritesFeature.body has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (20 pts), error handling 5 (10 pts), ternaries 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 16). 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.
AppUninstallerFileSystem.scan (cognitive 33) Modules/Sources/AppUninstaller/AppUninstallerFileSystem.swift:30— AppUninstallerFileSystem.scan has cognitive complexity 33 (threshold 15). Drivers by points: error handling 10 (18 pts), if/else 4 (7 pts), loops 4 (5 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.
RemoteConnectionRuntime.preparePairing (cognitive 33) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Pairing.swift:5— RemoteConnectionRuntime.preparePairing has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 10, error handling 5 (6 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.
OnlyRemoteCampaignFeature.body (cognitive 32) Modules/Sources/AppFeature/Features/RemoteAccess/Campaign/OnlyRemoteCampaignFeature.swift:27— OnlyRemoteCampaignFeature.body has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 8, error handling 1 (2 pts), match/switch 1 (nesting depth added 13). 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.
createOrUpdateDynamicThemeInternal (cognitive 32) Modules/Sources/WebBrowser/Resources/DarkReader.js:9042— createOrUpdateDynamicThemeInternal has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (20 pts), ternaries 4 (7 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 10). Of this number, 26 points are the body's own statements and 6 belong to 9 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.
ScriptTokenizer.tokens (cognitive 31) Modules/Sources/ScriptEditor/ScriptTokenizer.swift:41— ScriptTokenizer.tokens has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 7, ternaries 3 (6 pts), loops 2 (4 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.
getImageDetails (cognitive 31) Modules/Sources/WebBrowser/Resources/DarkReader.js:2950— getImageDetails has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (24 pts), boolean chains 2, other 2, ternaries 2, error handling 1 (nesting depth added 15). None of this is in the body itself: all 31 points belong to 4 function literals inside it that branch (lines 2951, 3015, 2997, …). 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.
SoundMixerVM.applyOutputRoute (cognitive 30) Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerVM.swift:365— SoundMixerVM.applyOutputRoute has cognitive complexity 30 (threshold 15). Drivers by points: if/else 15 (22 pts), boolean chains 4, ternaries 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.
ClaudeUsageView.content (cognitive 30) Modules/Sources/OnlyAgent/ClaudeUsage/ClaudeUsageView.swift:17— ClaudeUsageView.content has cognitive complexity 30 (threshold 15). Drivers by points: if/else 17 (24 pts), boolean chains 6 (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.
DarkReader.analyzeImage (cognitive 30) Modules/Sources/WebBrowser/Resources/DarkReader.js:3086— DarkReader.analyzeImage has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (24 pts), loops 2 (3 pts), boolean chains 2, ternaries 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
manageStyle.getRulesAsync (cognitive 30) Modules/Sources/WebBrowser/Resources/DarkReader.js:7058— manageStyle.getRulesAsync has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (21 pts), error handling 2 (5 pts), boolean chains 4 (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.
NSSound.setSystemVolume (cognitive 29) Modules/Sources/Extensions/NSSound_SystemVolumeExtension.swift:159— NSSound.setSystemVolume has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (21 pts), boolean chains 6, ternaries 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RemoteCodexUsageFeature.body (cognitive 29) Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageFeature.swift:33— RemoteCodexUsageFeature.body has cognitive complexity 29 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 6, match/switch 3 (6 pts), ternaries 2 (4 pts) (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
DarkReader.manageStyle.getRulesAsync (cognitive 29) Modules/Sources/WebBrowser/Resources/DarkReader.js:7058— DarkReader.manageStyle.getRulesAsync has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (21 pts), error handling 2 (5 pts), boolean chains 3 (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.
DesktopPetAgentLogMonitor.discover (cognitive 28) Modules/Sources/DesktopPet/DesktopPetAgentLogMonitor.swift:175— DesktopPetAgentLogMonitor.discover has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 13, if/else 6 (10 pts), loops 4 (5 pts) (nesting depth added 5). Of this number, 17 points are the body's own statements and 11 belong to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ClaudeCodeCLI.signIn (cognitive 28) Modules/Sources/OnlyAgent/ClaudeUsage/ClaudeCodeCLI.swift:66— ClaudeCodeCLI.signIn has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 4, loops 2, error handling 1 (nesting depth added 9). Of this number, 23 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RemoteConnectionRuntime.recoverPreparedPairingIfNeeded (cognitive 28) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Reconnect.swift:117— RemoteConnectionRuntime.recoverPreparedPairingIfNeeded has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 6, error handling 1 (2 pts), 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.
PersistenceController.init (cognitive 28) Modules/Sources/OnlySwitchPersistence/Persistence.swift:23— PersistenceController.init has cognitive complexity 28 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 7, error handling 2 (5 pts), ternaries 3 (5 pts), loops 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DisplayBrightnessKeyTap.handle (cognitive 27) Modules/Sources/AppFeature/Features/DisplayBrightness/DisplayBrightnessKeyTap.swift:122— DisplayBrightnessKeyTap.handle has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 11, 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.
HostedAudioPlayer.startHelper (cognitive 27) Modules/Sources/AppFeature/Player/CommonPlayer/HostedAudioPlayer.swift:151— HostedAudioPlayer.startHelper has cognitive complexity 27 (threshold 15). Drivers by points: if/else 16 (17 pts), boolean chains 9, error handling 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PlaybackHelperCommandWriter.drain (cognitive 27) Modules/Sources/AppFeature/Player/CommonPlayer/PlaybackHelperCommandWriter.swift:65— PlaybackHelperCommandWriter.drain has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 4, 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.
DesktopPetPlaybackFeature.body (cognitive 27) Modules/Sources/DesktopPet/DesktopPetPlaybackFeature.swift:39— DesktopPetPlaybackFeature.body has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 6, ternaries 2 (4 pts), match/switch 1 (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
BrightnessCoordinator.apply (cognitive 27) Modules/Sources/DisplayBrightness/BrightnessCoordinator.swift:39— BrightnessCoordinator.apply has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 5, ternaries 3 (5 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.
XcodeCleanerFileSystem.removeEntry (cognitive 27) Modules/Sources/XcodeCleaner/XcodeCleanerFileSystem.swift:114— XcodeCleanerFileSystem.removeEntry has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (20 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.
SoundMixerService.outputFormatSignature (cognitive 26) Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerService.swift:182— SoundMixerService.outputFormatSignature has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 3 (8 pts), boolean chains 4 (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.
RemoteConnectionRuntime.handle (cognitive 26) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Messages.swift:5— RemoteConnectionRuntime.handle has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (18 pts), error handling 3 (6 pts), boolean chains 1, match/switch 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.
RemoteReviewDemoRuntime.sendSoundMixer (cognitive 26) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteReviewDemoClient.swift:170— RemoteReviewDemoRuntime.sendSoundMixer has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (17 pts), ternaries 3 (6 pts), boolean chains 2, match/switch 1 (nesting depth added 10). Of this number, 25 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScreenshotEditorFeature.commitDraft (cognitive 26) Modules/Sources/Screenshots/ScreenshotEditorFeature.swift:206— ScreenshotEditorFeature.commitDraft has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 7, match/switch 1 (2 pts) (nesting depth added 10). Of this number, 25 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TailscaleCommandRunner.drain (cognitive 26) Modules/Sources/Tailscale/TailscaleCommandRunner.swift:100— TailscaleCommandRunner.drain has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (21 pts), boolean chains 2, loops 1 (2 pts), error handling 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Benchmark.main (cognitive 26) doc/research/xcode-cleaner-scan-benchmark.swift:25— Benchmark.main has cognitive complexity 26 (threshold 15). Drivers by points: if/else 5 (12 pts), ternaries 3 (8 pts), loops 4 (6 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
watchForNodePosition (cognitive 26) Modules/Sources/WebBrowser/Resources/DarkReader.js:1724— watchForNodePosition has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 8, ternaries 1 (nesting depth added 4). Most of this is not in the body itself: 3 of the 26 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 1743, 1814, 1758). 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.
OnlySwitchListView.body (cognitive 25) Modules/Sources/AppFeature/Features/OnlySwitchList/OnlySwitchListView.swift:77— OnlySwitchListView.body has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 4, ternaries 2 (3 pts), match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SystemAudioMixer.audioPlayingApps (cognitive 25) Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer.swift:175— SystemAudioMixer.audioPlayingApps has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 9, loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RemoteCatalogProvider.init (cognitive 25) Modules/Sources/AppFeature/Features/RemoteAccess/Catalog/RemoteCatalogProvider+Live.swift:7— RemoteCatalogProvider.init has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 15, if/else 5 (9 pts), 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.
DesktopPetSkinsFeature.reduceGenerator (cognitive 25) Modules/Sources/AppFeature/Features/Settings/DesktopPet/DesktopPetSkinsFeature.swift:127— DesktopPetSkinsFeature.reduceGenerator has cognitive complexity 25 (threshold 15). Drivers by points: error handling 5 (10 pts), if/else 6 (10 pts), match/switch 2 (3 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.
CodexRuntimePool.chatStream (cognitive 25) Modules/Sources/OnlyAgent/Settings/CodexSettings/CodexService.swift:142— CodexRuntimePool.chatStream has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, match/switch 1 (3 pts), ternaries 2 (3 pts), loops 1 (2 pts), error handling 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.
RemoteAppFeature.core (cognitive 25) Modules/Sources/OnlyRemoteFeature/App/RemoteAppFeature.swift:178— RemoteAppFeature.core has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 2, match/switch 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ScreenshotEditorFeature.body (cognitive 25) Modules/Sources/Screenshots/ScreenshotEditorFeature.swift:80— ScreenshotEditorFeature.body has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 4, error handling 1 (2 pts), match/switch 1 (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
CleanerCoordinator.clean (cognitive 25) Modules/Sources/XcodeCleaner/XcodeCleanerClient.swift:75— CleanerCoordinator.clean has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 10, if/else 3 (5 pts), loops 2 (4 pts), ternaries 1 (4 pts), error handling 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.
DarkReader.evalMath (cognitive 25) Modules/Sources/WebBrowser/Resources/DarkReader.js:864— DarkReader.evalMath has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 3 (5 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DarkReader.parse (cognitive 25) Modules/Sources/WebBrowser/Resources/DarkReader.js:1059— DarkReader.parse has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 4, ternaries 1 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DarkReader.getModifiableCSSDeclaration (cognitive 25) Modules/Sources/WebBrowser/Resources/DarkReader.js:3370— DarkReader.getModifiableCSSDeclaration has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 7, ternaries 1 (2 pts) (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.
SoundMixerVM.applyEqualizer (cognitive 24) Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerVM.swift:332— SoundMixerVM.applyEqualizer has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 4, ternaries 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.
AppUninstallerFileSystem.remove (cognitive 24) Modules/Sources/AppUninstaller/AppUninstallerFileSystem.swift:79— AppUninstallerFileSystem.remove has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (12 pts), boolean chains 6, error handling 2 (5 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GeminiLive.chatStream (cognitive 24) Modules/Sources/OnlyAgent/Settings/GeminiSettings/GeminiService.swift:44— GeminiLive.chatStream has cognitive complexity 24 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 3 (9 pts), boolean chains 1, error handling 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RemoteScreenshotResponses.consume (cognitive 24) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteScreenshotResponses.swift:97— RemoteScreenshotResponses.consume has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (20 pts), error handling 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
RemoteClaudeUsageFeature.body (cognitive 24) Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift:32— RemoteClaudeUsageFeature.body has cognitive complexity 24 (threshold 15). Drivers by points: if/else 4 (9 pts), match/switch 3 (6 pts), boolean chains 5, ternaries 2 (4 pts) (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.
DashboardFeature.handleConnectionEvent (cognitive 24) Modules/Sources/OnlyRemoteFeature/Features/Dashboard/DashboardFeature+ConnectionEvents.swift:6— DashboardFeature.handleConnectionEvent has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 3, loops 1 (2 pts), match/switch 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.
BrowserFeature.body (cognitive 24) Modules/Sources/WebBrowser/BrowserFeature.swift:62— BrowserFeature.body has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 2, 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.
StatusBarController.togglePopover (cognitive 23) Modules/Sources/AppFeature/StatusBar/StatusBarController.swift:128— StatusBarController.togglePopover has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (19 pts), ternaries 2 (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.
ShortcutsSettingsReducer.body (cognitive 23) Modules/Sources/AppFeature/Features/Settings/Shortcuts/ShortcutsSettingsReducer.swift:64— ShortcutsSettingsReducer.body has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 4, match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ClaudeUsageService.fetchOnce (cognitive 23) Modules/Sources/OnlyAgent/ClaudeUsage/ClaudeUsageService.swift:28— ClaudeUsageService.fetchOnce has cognitive complexity 23 (threshold 15). Drivers by points: error handling 7 (13 pts), if/else 3 (8 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.
RemoteScreenshotsFeature.handle (cognitive 23) Modules/Sources/OnlyRemoteFeature/Features/Screenshots/RemoteScreenshotsFeature+Effects.swift:8— RemoteScreenshotsFeature.handle has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (16 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.
EvolutionCommandEntity.addItem (cognitive 23) Modules/Sources/AppFeature/CoreData/EvolutionCommandEntityLive.swift:58— EvolutionCommandEntity.addItem has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 12, if/else 7 (11 pts) (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.
DarkReader.getBgImageModifier::getBgImageValue (cognitive 23) Modules/Sources/WebBrowser/Resources/DarkReader.js:3961— DarkReader.getBgImageModifier::getBgImageValue has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 5, ternaries 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.
DarkReader.getInversionStyleValue (cognitive 23) Modules/Sources/WebBrowser/Resources/DarkReader.js:8384— DarkReader.getInversionStyleValue has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 8, ternaries 3 (nesting depth added 1). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 6 function items inside it that branch (buildGroupRules, buildInversionRules, a function literal at line 8503, …). 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.
CrashReportDiscovery.latest (cognitive 22) Modules/Sources/AppFeature/Features/CrashReports/CrashReportDiscovery.swift:21— CrashReportDiscovery.latest has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 13, if/else 4 (8 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.
DisplayBrightnessService.pollNative (cognitive 22) Modules/Sources/AppFeature/Features/DisplayBrightness/DisplayBrightnessService.swift:282— DisplayBrightnessService.pollNative has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 9, 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.
MacSystemMonitorCollector.sampleForStream (cognitive 22) Modules/Sources/AppFeature/Features/SystemMonitor/MacSystemMonitorCollector.swift:191— MacSystemMonitorCollector.sampleForStream has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 11, boolean chains 6, if/else 5. 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.
RadioPlayerItemViewModel.storeEditedData (cognitive 22) Modules/Sources/AppFeature/Player/RadioPlayerItem/RadioPlayerItemViewModel.swift:122— RadioPlayerItemViewModel.storeEditedData has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (21 pts), error handling 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.
AppUninstallerFileSystem.validate (cognitive 22) Modules/Sources/AppUninstaller/AppUninstallerFileSystem.swift:127— AppUninstallerFileSystem.validate has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 16, if/else 4 (5 pts), loops 1 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DesktopPetAgentLogMonitor.updateCodexInventory (cognitive 22) Modules/Sources/DesktopPet/DesktopPetAgentLogMonitor.swift:265— DesktopPetAgentLogMonitor.updateCodexInventory has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 6, 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.
DesktopPetAgentLogParser.claude (cognitive 22) Modules/Sources/DesktopPet/DesktopPetAgentLogParser.swift:76— DesktopPetAgentLogParser.claude has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 6 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentConversationReducer.body (cognitive 22) Modules/Sources/OnlyAgent/Conversation/AgentConversationReducer.swift:142— AgentConversationReducer.body has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (10 pts), match/switch 3 (5 pts), boolean chains 4, ternaries 1 (3 pts) (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
RemoteConnectionRuntime.updateDiscovery (cognitive 22) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Discovery.swift:6— RemoteConnectionRuntime.updateDiscovery has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 10, if/else 6 (9 pts), loops 3 (nesting depth added 3). 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.
XcodeCleanerSimulator.clean (cognitive 22) Modules/Sources/XcodeCleaner/XcodeCleanerSimulator.swift:145— XcodeCleanerSimulator.clean has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 6, error handling 2 (4 pts), 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.
AphroditeFileStore.load (cognitive 21) Modules/Sources/Aphrodite/AphroditePersistenceClient.swift:86— AphroditeFileStore.load has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (12 pts), error handling 5 (9 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.
OnlySwitchApp.body (cognitive 21) Modules/Sources/AppFeature/OnlySwitchApp.swift:30— OnlySwitchApp.body has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (14 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, 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.
StatusBarController.restoreMenuBarIconHidingState (cognitive 21) Modules/Sources/AppFeature/StatusBar/StatusBarController+MenuBarIconHiding.swift:67— StatusBarController.restoreMenuBarIconHidingState has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (10 pts), error handling 3 (7 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DockPreviewView.body (cognitive 21) Modules/Sources/AppFeature/Features/DockPreview/DockPreviewView.swift:12— DockPreviewView.body has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (17 pts), ternaries 1 (3 pts), boolean chains 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.
AgentSystemInfo.promptDescription (cognitive 21) Modules/Sources/OnlyAgent/Conversation/AgentSystemInfo.swift:59— AgentSystemInfo.promptDescription has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11, ternaries 5 (10 pts) (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.
ClaudeLive.chatStream (cognitive 21) Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeService.swift:39— ClaudeLive.chatStream has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 9, if/else 4 (9 pts), 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.
DarkReader.getOpenCloseRange (cognitive 21) Modules/Sources/WebBrowser/Resources/DarkReader.js:496— DarkReader.getOpenCloseRange has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
getModifierForVariable (cognitive 21) Modules/Sources/WebBrowser/Resources/DarkReader.js:4331— getModifierForVariable has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 3 (8 pts) (nesting depth added 9). None of this is in the body itself: all 21 points belong to 12 function items inside it that branch ((anonymous)::getDeclarations::addModifiedValue, (anonymous)::getDeclarations, (anonymous)::addListener, …). 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.
TopNotchSwitch.hideHeicDesktopNotch (cognitive 20) Modules/Sources/AppFeature/EverySwitch/TopNotchSwitch.swift:174— TopNotchSwitch.hideHeicDesktopNotch has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 1, loops 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.
PrivateAppleSiliconMetricsReader.discoverTemperatureSensors (cognitive 20) Modules/Sources/AppFeature/Features/SystemMonitor/AppleSiliconMetricsReader.swift:218— PrivateAppleSiliconMetricsReader.discoverTemperatureSensors has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 5, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DesktopPetAgentActivityFeature.apply (cognitive 20) Modules/Sources/DesktopPet/DesktopPetAgentActivityFeature.swift:87— DesktopPetAgentActivityFeature.apply has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 6, 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.
BrightnessKeyRoutingState.route (cognitive 20) Modules/Sources/DisplayBrightness/BrightnessKeyPolicy.swift:59— BrightnessKeyRoutingState.route has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 5, ternaries 1 (4 pts), 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.
CodexLocalUsageScanner.scan (cognitive 20) Modules/Sources/OnlyAgent/CodexUsage/CodexLocalUsageScanner.swift:17— CodexLocalUsageScanner.scan has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 5, 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.
GlobalSettingsFeature.features (cognitive 20) Modules/Sources/OnlyRemoteFeature/Features/Settings/GlobalSettingsFeature.swift:75— GlobalSettingsFeature.features has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3, ternaries 1 (2 pts), 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.
DarkReader.getNumbersFromString (cognitive 20) Modules/Sources/WebBrowser/Resources/DarkReader.js:1125— DarkReader.getNumbersFromString has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 3, loops 1, ternaries 1 (nesting depth added 6). Of this number, 15 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DarkReader.iterateCSSRules (cognitive 20) Modules/Sources/WebBrowser/Resources/DarkReader.js:2025— DarkReader.iterateCSSRules has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 5). None of this is in the body itself: all 20 points belong to 2 function literals inside it that branch (lines 2031, 2060). 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.
AXMenuBarVisibleItemResolver.itemsToKeepVisible (cognitive 19) Modules/Sources/AppFeature/StatusBar/MenuBarAccessibilityItemResolver.swift:126— AXMenuBarVisibleItemResolver.itemsToKeepVisible has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 6, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DisplayBrightnessService.handleBrightnessKey (cognitive 19) Modules/Sources/AppFeature/Features/DisplayBrightness/DisplayBrightnessService.swift:364— DisplayBrightnessService.handleBrightnessKey has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 6, error handling 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.
OnlyControlReducer.refreshDashboard (cognitive 19) Modules/Sources/AppFeature/Features/OnlyControl/OnlyControlReducer.swift:273— OnlyControlReducer.refreshDashboard has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 3 (6 pts), loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PlaybackHelperEngine.streamer (cognitive 19) Modules/Sources/AppFeature/Player/CommonPlayer/PlaybackHelperEngine.swift:156— PlaybackHelperEngine.streamer has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 9, if/else 6, loops 1 (2 pts), ternaries 1 (2 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.
RemoteStatusScheduler.deliver (cognitive 19) Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteStatusScheduler.swift:223— RemoteStatusScheduler.deliver has cognitive complexity 19 (threshold 15). Drivers by points: if/else 3 (7 pts), error handling 3 (6 pts), loops 3, match/switch 1 (2 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DesktopPetMotion.values (cognitive 19) Modules/Sources/DesktopPet/MotionValues.swift:57— DesktopPetMotion.values has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 4, boolean chains 2, match/switch 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.
RemoteConnectionRuntime.validateCatalog (cognitive 19) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Policies.swift:15— RemoteConnectionRuntime.validateCatalog has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 7, 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.
RemoteFrameCodec.append (cognitive 19) Modules/Sources/RemoteTransport/RemoteFrameCodec.swift:96— RemoteFrameCodec.append has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 1 (3 pts), error handling 1 (2 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.
OutputRoutingFeature.body (cognitive 19) Modules/Sources/SoundMixerEQ/OutputRoutingFeature.swift:37— OutputRoutingFeature.body has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 3 (6 pts), boolean chains 4, 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.
TailscaleSettingsView.accountDetails (cognitive 19) Modules/Sources/Tailscale/TailscaleSettingsView.swift:95— TailscaleSettingsView.accountDetails has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 2 (5 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.
DarkReader.watchForNodePosition.restore (cognitive 19) Modules/Sources/WebBrowser/Resources/DarkReader.js:1743— DarkReader.watchForNodePosition.restore has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 4, ternaries 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SwitchManager.visibleTypesIncludingNewDiscoveries (cognitive 18) Modules/Sources/AppFeature/EverySwitch/SwitchManager.swift:112— SwitchManager.visibleTypesIncludingNewDiscoveries has cognitive complexity 18 (threshold 15). Drivers by points: if/else 18. 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.
EvolutionAdapter.toEvolutionItem (cognitive 18) Modules/Sources/AppFeature/Features/Settings/Evolution/EvolutionAdapter.swift:22— EvolutionAdapter.toEvolutionItem has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 11, if/else 7. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
EvolutionEditorReducer.reduceGeneration (cognitive 18) Modules/Sources/AppFeature/Features/Settings/Evolution/EvolutionEditor/EvolutionEditorReducer+Generation.swift:43— EvolutionEditorReducer.reduceGeneration has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (8 pts), error handling 3 (6 pts), boolean chains 3, 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.
DesktopPetSkinGenerationClient.run (cognitive 18) Modules/Sources/OnlyAgent/DesktopPetSkinGeneration/DesktopPetSkinGenerationClient.swift:64— DesktopPetSkinGenerationClient.run has cognitive complexity 18 (threshold 15). Drivers by points: if/else 2 (7 pts), error handling 2 (4 pts), match/switch 1 (3 pts), ternaries 1 (3 pts), 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.
RemoteConnectionRuntime.abortPairing (cognitive 18) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Pairing.swift:253— RemoteConnectionRuntime.abortPairing has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (11 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.
PairingView.body (cognitive 18) Modules/Sources/OnlyRemoteFeature/Features/Pairing/PairingView.swift:7— PairingView.body has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 5 (8 pts), if/else 7, match/switch 1 (2 pts), boolean chains 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.
ScreenshotFileCompleteness.hasMovieBox (cognitive 18) Modules/Sources/Screenshots/ScreenshotFolderWatcher.swift:142— ScreenshotFileCompleteness.hasMovieBox has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 3, 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.
VariablesStore.inspectVarDependant (cognitive 18) Modules/Sources/WebBrowser/Resources/DarkReader.js:4748— VariablesStore.inspectVarDependant has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 4 (nesting depth added 4). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 4750, 4782, 4800). 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.
DarkReader.iterateCSSDeclarations (cognitive 18) Modules/Sources/WebBrowser/Resources/DarkReader.js:2134— DarkReader.iterateCSSDeclarations has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 5 (nesting depth added 5). Of this number, 9 points are the body's own statements and 9 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SystemAXMenuBarSource.systemItemKind (cognitive 17) Modules/Sources/AppFeature/StatusBar/MenuBarAccessibilityItemResolver.swift:352— SystemAXMenuBarSource.systemItemKind has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, boolean chains 8. 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.
DisplayBrightnessKeyboardController.update (cognitive 17) Modules/Sources/AppFeature/Features/DisplayBrightness/DisplayBrightnessKeyboardController.swift:26— DisplayBrightnessKeyboardController.update has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 4, error handling 1 (3 pts), loops 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.
DisplayBrightnessService.scan (cognitive 17) Modules/Sources/AppFeature/Features/DisplayBrightness/DisplayBrightnessService.swift:107— DisplayBrightnessService.scan has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 4, ternaries 1 (2 pts), 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.
JLASAudioPlayer.play (cognitive 17) Modules/Sources/AppFeature/Player/CommonPlayer/JLASAudioPlayer.swift:76— JLASAudioPlayer.play has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 1 (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.
RemoteHost.startListener (cognitive 17) Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteHost.swift:237— RemoteHost.startListener has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 1 (2 pts), ternaries 1 (2 pts), boolean chains 1, 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.
RemoteStatusScheduler.update (cognitive 17) Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteStatusScheduler.swift:75— RemoteStatusScheduler.update has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 2, 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.
EvolutionReducer.body (cognitive 17) Modules/Sources/AppFeature/Features/Settings/Evolution/EvolutionReducer.swift:72— EvolutionReducer.body has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 2, error handling 1 (2 pts), ternaries 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.
SwitchBarVM.doSwitch (cognitive 17) Modules/Sources/AppFeature/Features/SwitchItem/SwitchBar/SwitchBarVM.swift:155— SwitchBarVM.doSwitch has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 4, match/switch 1 (2 pts), error handling 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.
DesktopPetAgentActivityFeature.body (cognitive 17) Modules/Sources/DesktopPet/DesktopPetAgentActivityFeature.swift:47— DesktopPetAgentActivityFeature.body has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (6 pts), loops 2 (4 pts), ternaries 2 (4 pts), boolean chains 2, 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.
DesktopPetSkinValidator.decodeCSSEscapes (cognitive 17) Modules/Sources/DesktopPetSkinKit/DesktopPetSkinValidator.swift:133— DesktopPetSkinValidator.decodeCSSEscapes has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DDCDisplayController.framebufferIdentities (cognitive 17) Modules/Sources/DisplayDDC/DDCDisplayController.swift:214— DDCDisplayController.framebufferIdentities has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 5, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClaudeCodeCLI.authorizationURL (cognitive 17) Modules/Sources/OnlyAgent/ClaudeUsage/ClaudeCodeCLI.swift:138— ClaudeCodeCLI.authorizationURL has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 9, if/else 3 (5 pts), loops 2 (3 pts) (nesting depth added 3). 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.
OpenAILive.chatStream (cognitive 17) Modules/Sources/OnlyAgent/Settings/OpenAISettings/OpenAIService.swift:49— OpenAILive.chatStream has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 2 (5 pts), boolean chains 2, 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.
DashboardReducer.body (cognitive 17) Modules/Sources/OnlyControl/DashboardReducer.swift:38— DashboardReducer.body has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (6 pts), ternaries 2 (6 pts), boolean chains 4, 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.
ControlTilePresentation.init (cognitive 17) Modules/Sources/OnlyRemoteFeature/Features/Dashboard/ControlTilePresentation.swift:21— ControlTilePresentation.init has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, match/switch 2 (3 pts), ternaries 1 (3 pts), boolean chains 2 (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.
RemoteSoundMixerView.appCard (cognitive 17) Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerView.swift:104— RemoteSoundMixerView.appCard has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 4 (6 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.
ScreenshotCell.body (cognitive 17) Modules/Sources/Screenshots/ScreenshotsView.swift:274— ScreenshotCell.body has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8, ternaries 6 (7 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.
DarkReader.parseGradient (cognitive 17) Modules/Sources/WebBrowser/Resources/DarkReader.js:2734— DarkReader.parseGradient has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 1 (nesting depth added 10). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 2741). 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.
DarkReader.manageStyle.hasImports (cognitive 17) Modules/Sources/WebBrowser/Resources/DarkReader.js:6974— DarkReader.manageStyle.hasImports has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 1 (2 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.
DarkReader.replaceCSSImports (cognitive 17) Modules/Sources/WebBrowser/Resources/DarkReader.js:7375— DarkReader.replaceCSSImports has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (8 pts), error handling 1 (4 pts), boolean chains 2, 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.
manageStyle.hasImports (cognitive 17) Modules/Sources/WebBrowser/Resources/DarkReader.js:6974— manageStyle.hasImports has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 1 (2 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.
DisplayBrightnessKeyTap.run (cognitive 16) Modules/Sources/AppFeature/Features/DisplayBrightness/DisplayBrightnessKeyTap.swift:73— DisplayBrightnessKeyTap.run has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 3, ternaries 1 (2 pts) (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.
DisplayBrightnessService.start (cognitive 16) Modules/Sources/AppFeature/Features/DisplayBrightness/DisplayBrightnessService.swift:62— DisplayBrightnessService.start has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), error handling 1 (2 pts), loops 2, ternaries 1 (2 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OnlySwitchListView.singleSwitchList (cognitive 16) Modules/Sources/AppFeature/Features/OnlySwitchList/OnlySwitchListView+Lists.swift:13— OnlySwitchListView.singleSwitchList has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SettingsWindow.show (cognitive 16) Modules/Sources/AppFeature/Features/OnlySwitchList/SettingsWindow.swift:85— SettingsWindow.show has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (16 pts) (nesting depth added 9). 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.
PlaybackHelperCommandWriter.send (cognitive 16) Modules/Sources/AppFeature/Player/CommonPlayer/PlaybackHelperCommandWriter.swift:33— PlaybackHelperCommandWriter.send has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 7 (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.
RemotePeerSession.completePairing (cognitive 16) Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession+Pairing.swift:7— RemotePeerSession.completePairing has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 7, error handling 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.
EvolutionItem.doSwitch (cognitive 16) Modules/Sources/AppFeature/Features/Settings/Evolution/EvolutionModel.swift:67— EvolutionItem.doSwitch has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EvolutionEditorReducer.apply (cognitive 16) Modules/Sources/AppFeature/Features/Settings/Evolution/EvolutionEditor/EvolutionEditorReducer+Generation.swift:122— EvolutionEditorReducer.apply has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 3 (5 pts), boolean chains 2, loops 1, match/switch 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.
ClaudeUsageResponse.decode (cognitive 16) Modules/Sources/OnlyAgent/ClaudeUsage/ClaudeUsageResponse.swift:5— ClaudeUsageResponse.decode has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, if/else 4 (6 pts), loops 2, ternaries 1 (2 pts) (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RemoteAppFeature.syncScreenshotsContext (cognitive 16) Modules/Sources/OnlyRemoteFeature/App/RemoteAppFeature+Sync.swift:211— RemoteAppFeature.syncScreenshotsContext has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 3, match/switch 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.
RemoteClientSession.receiveLoop (cognitive 16) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteClientSession.swift:355— RemoteClientSession.receiveLoop has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (12 pts), error handling 2, loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RemoteConnectionRuntime.boundedCandidates (cognitive 16) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Policies.swift:55— RemoteConnectionRuntime.boundedCandidates has cognitive complexity 16 (threshold 15). Drivers by points: loops 5 (8 pts), if/else 3 (6 pts), boolean chains 2 (nesting depth added 6). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
RemoteBrightnessFeature.body (cognitive 16) Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:51— RemoteBrightnessFeature.body has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 6, 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.
RadioFavoriteRow.body (cognitive 16) Modules/Sources/RadioBrowser/RadioFavoritesView.swift:77— RadioFavoriteRow.body has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 12, if/else 3, boolean chains 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.
ScheduleDraft.issues (cognitive 16) Modules/Sources/Scheduler/ScheduleDraft.swift:75— ScheduleDraft.issues has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 2, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScreenshotWatcherSession.poll (cognitive 16) Modules/Sources/Screenshots/ScreenshotFolderWatcher.swift:107— ScreenshotWatcherSession.poll has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 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.
ScreenshotRenderer.render (cognitive 16) Modules/Sources/Screenshots/ScreenshotRenderer.swift:12— ScreenshotRenderer.render has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 4, loops 2 (3 pts), ternaries 1 (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TailscaleCoordinator.authorize (cognitive 16) Modules/Sources/Tailscale/TailscaleCoordinator.swift:145— TailscaleCoordinator.authorize has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 3 (5 pts), boolean chains 1, 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.
TailscaleConnection.validatedIPAddress (cognitive 16) Modules/Sources/Tailscale/TailscaleModels.swift:58— TailscaleConnection.validatedIPAddress has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 11, if/else 3 (4 pts), ternaries 1 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DarkReader.hslToRGB (cognitive 16) Modules/Sources/WebBrowser/Resources/DarkReader.js:960— DarkReader.hslToRGB has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (15 pts), if/else 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.
DarkReader.insertVarValues (cognitive 16) Modules/Sources/WebBrowser/Resources/DarkReader.js:5109— DarkReader.insertVarValues has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 1 (nesting depth added 4). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to one function item inside it that branches (matchReplacer). 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.
injectStyleAway (cognitive 16) Modules/Sources/WebBrowser/Resources/DarkReader.js:5818— injectStyleAway has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 1 (4 pts) (nesting depth added 9). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 5852, 5822, 5848, …). 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.
ClassTooLong: RemoteMessage Modules/Sources/RemoteCore/RemoteMessage.swift:3— ClassTooLong — 407 significant lines (blank, comment-only and punctuation-only lines excluded), 4 methods. The bar is 400 significant lines; this is 7 over it, 1.02× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Change coupling: Preferences.swift ↔ NotificationNames.swift Modules/Sources/AppFeature/Model/Preferences.swift:1— `Modules/Sources/AppFeature/Model/Preferences.swift` and `Modules/Sources/Defines/NotificationNames.swift` change together 60% of the time (12 of the 20 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `613b47b8` feat: add system monitor settings (at that commit the file was still `OnlySwitch/Model/Preferences.swift`); `3c891501` feat: add desktop pet setting (at that commit the file was still `OnlySwitch/Model/Preferences.swift`); `fe8b2a88` feat(DimScreen): sync external monitor brightness via DDC/CI (at that commit the file was still `OnlySwitch/Model/Preferences.swift`) — run `git show` on any of them.
Change coupling clique: RemotePeerSession.swift, RemoteConnectionClient+Live.swift, RemotePersistenceClient.swift Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession.swift— 3 files — `Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession.swift`, `Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionClient+Live.swift`, `Modules/Sources/OnlyRemoteFeature/Dependencies/RemotePersistenceClient.swift` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×1
Edited copy of a member (31 corresponding lines) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteReviewDemoClient.swift:38— Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteReviewDemoClient.swift:38-68 | Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteReviewDemoClient.swift:359-401 — 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 (38 corresponding lines) · ×1
Edited copy of a member (38 corresponding lines) Modules/Sources/OnlyRemoteFeature/Dependencies/RemotePersistenceClient.swift:61— Modules/Sources/OnlyRemoteFeature/Dependencies/RemotePersistenceClient.swift:61-101 | Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteReviewDemoClients.swift:94-131 — 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 (43 corresponding lines) · ×1
Edited copy of a member (43 corresponding lines) Modules/Sources/SoundMixerEQ/EqualizerFeature.swift:51— Modules/Sources/SoundMixerEQ/EqualizerFeature.swift:51-93 | Modules/Sources/SoundMixerEQ/OutputRoutingFeature.swift:37-87 — 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 (40 corresponding lines) · ×1
Edited copy of a member (40 corresponding lines) Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift:32— Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift:32-71 | Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageFeature.swift:33-79 — 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 (39 corresponding lines) · ×1
Edited copy of a member (39 corresponding lines) Modules/Sources/AppFeature/EverySwitch/ScrollDirectionEventTap.swift:76— Modules/Sources/AppFeature/EverySwitch/ScrollDirectionEventTap.swift:76-128 | Modules/Sources/AppFeature/Features/SoundMixer/DisplayVolumeKeyTap.swift:56-94 — 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.
D4 · Code Duplication· Edited copy of a member (48 corresponding lines) · ×1
Edited copy of a member (48 corresponding lines) Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessView.swift:8— Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessView.swift:8-57 | Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerView.swift:9-56 — 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 copies of one member (3 members, 55+ corresponding lines) · ×1
Edited copies of one member (3 members, 55+ corresponding lines) Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeSettingView.swift:20— Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeSettingView.swift:20-74 | Modules/Sources/OnlyAgent/Settings/GeminiSettings/GeminiSettingView.swift:20-74 | Modules/Sources/OnlyAgent/Settings/OpenAISettings/OpenAISettingView.swift:20-86 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 55 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, 54+ corresponding lines) · ×1
Edited copies of one member (3 members, 54+ corresponding lines) Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeSettingReducer.swift:38— Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeSettingReducer.swift:38-91 | Modules/Sources/OnlyAgent/Settings/GeminiSettings/GeminiSettingReducer.swift:38-91 | Modules/Sources/OnlyAgent/Settings/OpenAISettings/OpenAISettingReducer.swift:40-94 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 54 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 (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) Modules/Sources/AppFeature/StatusBar/StatusBarController.swift:200— Modules/Sources/AppFeature/StatusBar/StatusBarController.swift:200-222 | Modules/Sources/AppFeature/StatusBar/StatusBarController.swift:240-268 — 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 copy of a member (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) Modules/Sources/Extensions/NSSound_SystemVolumeExtension.swift:252— Modules/Sources/Extensions/NSSound_SystemVolumeExtension.swift:252-284 | Modules/Sources/Extensions/NSSound_SystemVolumeExtension.swift:316-347 — These two members are one piece of code written twice and then edited apart: 32 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, 23+ corresponding lines) · ×1
Edited copies of one member (3 members, 23+ corresponding lines) Modules/Sources/OnlyRemoteFeature/App/RemoteAppFeature+Sync.swift:76— Modules/Sources/OnlyRemoteFeature/App/RemoteAppFeature+Sync.swift:76-98 | Modules/Sources/OnlyRemoteFeature/App/RemoteAppFeature+Sync.swift:130-155 | Modules/Sources/OnlyRemoteFeature/App/RemoteAppFeature+Sync.swift:163-186 — 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 copies of one member (3 members, 11+ corresponding lines) · ×1
Edited copies of one member (3 members, 11+ corresponding lines) Modules/Sources/RemoteCore/ClaudeUsageModels.swift:77— Modules/Sources/RemoteCore/ClaudeUsageModels.swift:77-87 | Modules/Sources/RemoteCore/CodexUsageModels.swift:79-89 | Modules/Sources/RemoteCore/RemoteAction.swift:66-85 — 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 (25 corresponding lines) · ×1
Edited copy of a member (25 corresponding lines) Modules/Sources/OnlyRemoteFeature/Dependencies/InMemoryRemotePersistenceStore.swift:121— Modules/Sources/OnlyRemoteFeature/Dependencies/InMemoryRemotePersistenceStore.swift:121-145 | Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteFilePersistenceStore.swift:191-217 — 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, 14+ corresponding lines) · ×1
Edited copies of one member (4 members, 14+ corresponding lines) Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:152— Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:152-170 | Modules/Sources/OnlyRemoteFeature/Features/Screenshots/RemoteScreenshotsFeature+Effects.swift:124-137 | Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerFeature.swift:280-298 | Modules/Sources/OnlyRemoteFeature/Features/SystemMonitor/RemoteSystemMonitorFeature.swift:119-137 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 20+ corresponding lines) · ×1
Edited copies of one member (3 members, 20+ corresponding lines) Modules/Sources/Aphrodite/AphroditeGeneratedDocumentSchemeHandler.swift:22— Modules/Sources/Aphrodite/AphroditeGeneratedDocumentSchemeHandler.swift:22-42 | Modules/Sources/Aphrodite/AphroditeWebStorageCleanup.swift:77-96 | Modules/Sources/OnlyRemoteFeature/Features/Aphrodite/RemoteAphroditeView.swift:90-110 — 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 copies of one member (3 members, 14+ corresponding lines) · ×1
Edited copies of one member (3 members, 14+ corresponding lines) Modules/Sources/Networking/GitHub/GitHubRemoteDataSource.swift:12— Modules/Sources/Networking/GitHub/GitHubRemoteDataSource.swift:12-25 | Modules/Sources/Networking/GitHub/GitHubRemoteDataSource.swift:27-40 | Modules/Sources/Networking/GitHub/GitHubRemoteDataSource.swift:42-55 — 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 (5 members, 7+ corresponding lines) · ×1
Edited copies of one member (5 members, 7+ corresponding lines) Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeTool.swift:14— Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeTool.swift:14-20 | Modules/Sources/OnlyAgent/Settings/CodexSettings/CodexTool.swift:14-21 | Modules/Sources/OnlyAgent/Settings/GeminiSettings/GeminiTool.swift:14-21 | Modules/Sources/OnlyAgent/Settings/OllamaSettings/OllamaTool.swift:14-21 | Modules/Sources/OnlyAgent/Settings/OpenAISettings/OpenAITool.swift:14-21 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 8+ corresponding lines) · ×1
Edited copies of one member (4 members, 8+ corresponding lines) Modules/Sources/AppFeature/EverySwitch/AphroditeSwitch.swift:16— Modules/Sources/AppFeature/EverySwitch/AphroditeSwitch.swift:16-23 | Modules/Sources/AppFeature/EverySwitch/ClaudeUsageSwitch.swift:19-30 | Modules/Sources/AppFeature/EverySwitch/CodexUsageSwitch.swift:19-30 | Modules/Sources/AppFeature/EverySwitch/SystemMonitorSwitch.swift:19-30 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×1
Edited copies of one member (3 members, 16+ corresponding lines) Modules/Sources/OnlySwitchPersistence/EvolutionCommandEntity+Fetch.swift:30— Modules/Sources/OnlySwitchPersistence/EvolutionCommandEntity+Fetch.swift:30-45 | Modules/Sources/OnlySwitchPersistence/RadioStations+Fetch.swift:60-82 | Modules/Sources/OnlySwitchPersistence/RadioStations+Fetch.swift:84-106 — 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 (5 members, 4+ corresponding lines) · ×1
Edited copies of one member (5 members, 4+ corresponding lines) Modules/Sources/Aphrodite/AphroditeShareDocument.swift:68— Modules/Sources/Aphrodite/AphroditeShareDocument.swift:68-76 | Modules/Sources/RemoteCore/AphroditeRemoteModels.swift:242-245 | Modules/Sources/RemoteCore/AphroditeRemoteModels.swift:264-267 | Modules/Sources/RemoteCore/RemoteScreenshots.swift:134-137 | Modules/Sources/RemoteCore/RemoteScreenshots.swift:228-231 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 5+ corresponding lines) · ×1
Edited copies of one member (3 members, 5+ corresponding lines) Modules/Sources/Tailscale/TailscaleCoordinator.swift:130— Modules/Sources/Tailscale/TailscaleCoordinator.swift:130-134 | Modules/Sources/Tailscale/TailscaleCoordinator.swift:135-139 | Modules/Sources/Tailscale/TailscaleCoordinator.swift:140-144 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 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) · ×1
Edited copies of one member (3 members, 12+ corresponding lines) Modules/Sources/AppFeature/EverySwitch/MuteMicSwitch.swift:16— Modules/Sources/AppFeature/EverySwitch/MuteMicSwitch.swift:16-27 | Modules/Sources/AppFeature/EverySwitch/MuteSwitch.swift:133-147 | Modules/Sources/AppFeature/EverySwitch/ScreenSaverSwitch.swift:35-47 — 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, 16+ corresponding lines) · ×1
Edited copies of one member (4 members, 16+ corresponding lines) Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession+Streaming.swift:6— Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession+Streaming.swift:6-21 | Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession+Streaming.swift:66-81 | Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession+Streaming.swift:88-103 | Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession+Streaming.swift:126-141 — 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, 3+ corresponding lines) · ×1
Edited copies of one member (3 members, 3+ corresponding lines) Modules/Sources/AppFeature/Features/Settings/Evolution/EvolutionEditor/EvolutionShellQuoting.swift:13— Modules/Sources/AppFeature/Features/Settings/Evolution/EvolutionEditor/EvolutionShellQuoting.swift:13-17 | Modules/Sources/AppUninstaller/AdministratorTrash.swift:31-33 | Modules/Sources/OnlyAgent/Conversation/EvolutionScriptComposer.swift:50-55 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 1+ corresponding lines) · ×1
Edited copies of one member (3 members, 1+ corresponding lines) Modules/Sources/AppFeature/EverySwitch/ScrollDirectionEventTap.swift:246— Modules/Sources/AppFeature/EverySwitch/ScrollDirectionEventTap.swift:246-250 | Modules/Sources/AppFeature/Features/DisplayBrightness/DisplayBrightnessKeyTap.swift:173-173 | Modules/Sources/AppFeature/Features/SoundMixer/DisplayVolumeKeyTap.swift:127-130 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 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, 3+ corresponding lines) · ×1
Edited copies of one member (4 members, 3+ corresponding lines) Modules/Sources/OnlyAgent/ClaudeUsage/ClaudeUsageModels.swift:12— Modules/Sources/OnlyAgent/ClaudeUsage/ClaudeUsageModels.swift:12-14 | Modules/Sources/OnlyAgent/CodexUsage/CodexUsageModels.swift:17-20 | Modules/Sources/RemoteCore/ClaudeUsageModels.swift:21-24 | Modules/Sources/RemoteCore/CodexUsageModels.swift:21-24 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 4+ corresponding lines) · ×1
Edited copies of one member (4 members, 4+ corresponding lines) Modules/Sources/AppFeature/EverySwitch/AphroditeSwitch.swift:27— Modules/Sources/AppFeature/EverySwitch/AphroditeSwitch.swift:27-30 | Modules/Sources/AppFeature/EverySwitch/ClaudeUsageSwitch.swift:42-46 | Modules/Sources/AppFeature/EverySwitch/CodexUsageSwitch.swift:42-46 | Modules/Sources/AppFeature/EverySwitch/SystemMonitorSwitch.swift:42-46 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
Duplicated block (34 lines × 3) Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeSettingView.swift:20— Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeSettingView.swift:20-53 | Modules/Sources/OnlyAgent/Settings/GeminiSettings/GeminiSettingView.swift:20-53 | Modules/Sources/OnlyAgent/Settings/OpenAISettings/OpenAISettingView.swift:20-53 — 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 `Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeSettingView.swift:20` 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 first that the copies are not typed on the same thing: the declarations holding them bind `store` to `StoreOf<ClaudeSettingReducer>` in one and `StoreOf<GeminiSettingReducer>` 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 (26–33 lines × 2) Modules/Sources/AppFeature/EverySwitch/ScrollDirectionEventTap.swift:96— Modules/Sources/AppFeature/EverySwitch/ScrollDirectionEventTap.swift:96-128 | Modules/Sources/AppFeature/Features/SoundMixer/DisplayVolumeKeyTap.swift:69-94 — 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 `Modules/Sources/AppFeature/EverySwitch/ScrollDirectionEventTap.swift: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 (23–24 lines × 3) Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeSettingView.swift:51— Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeSettingView.swift:51-74 | Modules/Sources/OnlyAgent/Settings/GeminiSettings/GeminiSettingView.swift:51-74 | Modules/Sources/OnlyAgent/Settings/OpenAISettings/OpenAISettingView.swift:64-86 — 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 `Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeSettingView.swift:51` 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 (23 lines × 2) Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessView.swift:8— Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessView.swift:8-30 | Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerView.swift:9-31 — before extracting anything, compare `Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessView.swift` and `Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerView.swift` as WHOLE FILES: this scan already matched 4 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. 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 `Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessView.swift:8` 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, `Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerView.swift:7` calls `Environment` and `Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessView.swift:6` 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 (22 lines × 2) Modules/Sources/Extensions/KeychainManager.swift:25— Modules/Sources/Extensions/KeychainManager.swift:25-46 | Modules/Sources/Utilities/KeychainManager.swift:25-46 — `Modules/Sources/Extensions/KeychainManager.swift` and `Modules/Sources/Utilities/KeychainManager.swift` 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 74 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 (19 lines × 2) Modules/Sources/AppFeature/Features/Settings/KeepAwake/KeepAwakeSettingView.swift:41— Modules/Sources/AppFeature/Features/Settings/KeepAwake/KeepAwakeSettingView.swift:41-59 | Modules/Sources/AppFeature/Features/Settings/NightShift/NightShiftSettingsView.swift:33-51 — 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 `Modules/Sources/AppFeature/Features/Settings/KeepAwake/KeepAwakeSettingView.swift:41` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Modules/Sources/AppFeature/Features/Settings/NightShift/NightShiftSettingsView.swift:31` calls `Toggle`, `localized` and `Modules/Sources/AppFeature/Features/Settings/KeepAwake/KeepAwakeSettingView.swift:39` 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 (18 lines × 2) Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteHost+Testing.swift:29— Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteHost+Testing.swift:29-46 | Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession.swift:104-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.
Duplicated block (15–17 lines × 4) Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeService.swift:23— Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeService.swift:23-37 | Modules/Sources/OnlyAgent/Settings/GeminiSettings/GeminiService.swift:26-42 | Modules/Sources/OnlyAgent/Settings/OllamaSettings/OllamaRequestService.swift:48-64 | Modules/Sources/OnlyAgent/Settings/OpenAISettings/OpenAIService.swift:31-47 — before extracting anything, compare `Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeService.swift` and `Modules/Sources/OnlyAgent/Settings/GeminiSettings/GeminiService.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 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 (16–17 lines × 2) Modules/Sources/AppFeature/Player/CommonPlayer/JLASAudioPlayer.swift:83— Modules/Sources/AppFeature/Player/CommonPlayer/JLASAudioPlayer.swift:83-99 | Modules/Sources/AppFeature/Player/CommonPlayer/JLAVAudioPlayer.swift:58-73 — 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 `Modules/Sources/AppFeature/Player/CommonPlayer/JLASAudioPlayer.swift:83` 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, `Modules/Sources/AppFeature/Player/CommonPlayer/JLAVAudioPlayer.swift:75` calls `stop`, `AVAsset`, `AVPlayerItem` and `Modules/Sources/AppFeature/Player/CommonPlayer/JLASAudioPlayer.swift:101` 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–15 lines × 4) Modules/Sources/AppFeature/Features/OnlySwitchList/OnlySwitchListView+Lists.swift:131— Modules/Sources/AppFeature/Features/OnlySwitchList/OnlySwitchListView+Lists.swift:131-141 | Modules/Sources/AppFeature/Features/OnlySwitchList/OnlySwitchListView+Lists.swift:152-164 | Modules/Sources/AppFeature/Features/OnlySwitchList/OnlySwitchListView+Lists.swift:177-190 | Modules/Sources/AppFeature/Features/OnlySwitchList/OnlySwitchListView+Lists.swift:203-217 — 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 `Modules/Sources/AppFeature/Features/OnlySwitchList/OnlySwitchListView+Lists.swift:131` 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 (15 lines × 3) Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:156— Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:156-170 | Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerFeature.swift:284-298 | Modules/Sources/OnlyRemoteFeature/Features/SystemMonitor/RemoteSystemMonitorFeature.swift:123-137 — before extracting anything, compare `Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift` and `Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerFeature.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 86 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 `Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:156` 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 (11–14 lines × 2) Modules/Sources/OnlyAgent/DesktopPetSkinGeneration/DesktopPetSkinGenerationClient.swift:138— Modules/Sources/OnlyAgent/DesktopPetSkinGeneration/DesktopPetSkinGenerationClient.swift:138-148 | Modules/Sources/OnlyAgent/EvolutionGeneration/EvolutionScriptGenerationClient.swift:46-59 — 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 `Modules/Sources/OnlyAgent/DesktopPetSkinGeneration/DesktopPetSkinGenerationClient.swift:138` 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 (9–13 lines × 3) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Pairing.swift:33— Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Pairing.swift:33-41 | Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Reconnect.swift:45-57 | Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Reconnect.swift:155-163 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Pairing.swift:33` 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, `Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Pairing.swift:30` calls `uppercased` and `Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteConnectionRuntime+Reconnect.swift:154` 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–13 lines × 2) Modules/Sources/OnlyAgent/ClaudeUsage/ClaudeUsageView.swift:29— Modules/Sources/OnlyAgent/ClaudeUsage/ClaudeUsageView.swift:29-35 | Modules/Sources/OnlyAgent/CodexUsage/CodexUsageView.swift:35-47 — 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 `Modules/Sources/OnlyAgent/ClaudeUsage/ClaudeUsageView.swift:29` 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 × 4) Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift:117— Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift:117-126 | Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift:127-136 | Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageFeature.swift:124-133 | Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageFeature.swift:134-143 — before extracting anything, compare `Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift` and `Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageFeature.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 52 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 (4–10 lines × 3) Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerService.swift:240— Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerService.swift:240-243 | Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerService.swift:265-274 | Modules/Sources/AppFeature/Features/SoundMixer/SystemAudioMixer+CoreAudio.swift:100-109 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Modules/Sources/AppFeature/Features/SoundMixer/SoundMixerService.swift:240` 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.
Duplicated block (9–10 lines × 2) Modules/Sources/AppFeature/StatusBar/StatusBarController.swift:211— Modules/Sources/AppFeature/StatusBar/StatusBarController.swift:211-220 | Modules/Sources/AppFeature/StatusBar/StatusBarController.swift:229-237 — 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 `Modules/Sources/AppFeature/StatusBar/StatusBarController.swift:211` 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 (6–10 lines × 2) Modules/Sources/OnlyRemoteFeature/Features/Dashboard/DashboardFeature+ConnectionEvents.swift:6— Modules/Sources/OnlyRemoteFeature/Features/Dashboard/DashboardFeature+ConnectionEvents.swift:6-15 | Modules/Sources/OnlyRemoteFeature/Features/Settings/SettingsFeature.swift:259-264 — 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 `Modules/Sources/OnlyRemoteFeature/Features/Dashboard/DashboardFeature+ConnectionEvents.swift:6` 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) Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteReviewDemoClient.swift:55— Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteReviewDemoClient.swift:55-63 | Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteReviewDemoClient.swift:375-382 — 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 `Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteReviewDemoClient.swift:55` 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 × 3) Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:117— Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:117-126 | Modules/Sources/OnlyRemoteFeature/Features/Screenshots/RemoteScreenshotsFeature+Effects.swift:27-36 | Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerFeature.swift:230-239 — before extracting anything, compare `Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift` and `Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerFeature.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 86 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 `Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:117` 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 (2–8 lines × 4) Modules/Sources/AppFeature/Features/Settings/Radio/RadioSettingView.swift:77— Modules/Sources/AppFeature/Features/Settings/Radio/RadioSettingView.swift:77-84 | Modules/Sources/DisplayBrightness/DisplayBrightnessView.swift:119-123 | Modules/Sources/Screenshots/ScreenshotEditorView.swift:260-267 | Modules/Sources/XcodeCleaner/XcodeCleanerView.swift:221-222 — 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 `Modules/Sources/AppFeature/Features/Settings/Radio/RadioSettingView.swift:77` 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 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 after the matched lines, `Modules/Sources/DisplayBrightness/DisplayBrightnessView.swift:123` calls `background`, `rect`, `overlay` and `Modules/Sources/AppFeature/Features/Settings/Radio/RadioSettingView.swift:84` 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–8 lines × 2) Modules/Sources/OnlyWidgetFeature/Widgets/Evolution/Intents/EvolutionEntity.swift:24— Modules/Sources/OnlyWidgetFeature/Widgets/Evolution/Intents/EvolutionEntity.swift:24-30 | Modules/Sources/OnlyWidgetFeature/Widgets/Evolution/Intents/EvolutionEntity.swift:49-56 — 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 `Modules/Sources/OnlyWidgetFeature/Widgets/Evolution/Intents/EvolutionEntity.swift:24` 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 (6–7 lines × 2) Modules/Sources/AppFeature/Player/CommonPlayer/AudioSpectrum/SpectrumView.swift:35— Modules/Sources/AppFeature/Player/CommonPlayer/AudioSpectrum/SpectrumView.swift:35-41 | Modules/Sources/AppFeature/Player/CommonPlayer/AudioSpectrum/SpectrumView.swift:54-59 — 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 `Modules/Sources/AppFeature/Player/CommonPlayer/AudioSpectrum/SpectrumView.swift:35` 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 (5–7 lines × 2) Modules/Sources/OnlyAgent/CodexUsage/CodexUsageView.swift:150— Modules/Sources/OnlyAgent/CodexUsage/CodexUsageView.swift:150-156 | Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageView.swift:130-134 — 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 `Modules/Sources/OnlyAgent/CodexUsage/CodexUsageView.swift:150` 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) Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteCredentialStore+Keychain.swift:147— Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteCredentialStore+Keychain.swift:147-151 | Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemotePeerSession.swift:309-313 | Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteKeychainClient.swift:184-188 — 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.
Duplicated block (9 lines × 3) Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeService.swift:102— Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeService.swift:102-110 | Modules/Sources/OnlyAgent/Settings/GeminiSettings/GeminiService.swift:104-112 | Modules/Sources/OnlyAgent/Settings/OpenAISettings/OpenAIService.swift:114-122 — before extracting anything, compare `Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeService.swift` and `Modules/Sources/OnlyAgent/Settings/GeminiSettings/GeminiService.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 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 (12 lines × 3) Modules/Sources/AppFeature/EverySwitch/AutohideDockSwitch.swift:36— Modules/Sources/AppFeature/EverySwitch/AutohideDockSwitch.swift:36-47 | Modules/Sources/AppFeature/EverySwitch/AutohideMenuBarSwitch.swift:36-48 | Modules/Sources/AppFeature/EverySwitch/DarkModeSwitch.swift:26-37 — 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.
Duplicated block (9 lines × 4) Modules/Sources/AppFeature/EverySwitch/DockRecentSwitch.swift:16— Modules/Sources/AppFeature/EverySwitch/DockRecentSwitch.swift:16-25 | Modules/Sources/AppFeature/EverySwitch/HiddenFilesSwitch.swift:21-30 | Modules/Sources/AppFeature/EverySwitch/ShowExtensionNameSwitch.swift:16-25 | Modules/Sources/AppFeature/EverySwitch/ShowFinderPathbarSwitch.swift:16-24 — 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 4 call sites, so a change lands once.
Duplicated block (12 lines × 6) Modules/Sources/AppFeature/EverySwitch/DockRecentSwitch.swift:32— Modules/Sources/AppFeature/EverySwitch/DockRecentSwitch.swift:32-44 | Modules/Sources/AppFeature/EverySwitch/HiddenDesktopSwitch.swift:34-45 | Modules/Sources/AppFeature/EverySwitch/HiddenFilesSwitch.swift:36-48 | Modules/Sources/AppFeature/EverySwitch/ShowExtensionNameSwitch.swift:32-43 | Modules/Sources/AppFeature/EverySwitch/ShowFinderPathbarSwitch.swift:31-42 | Modules/Sources/AppFeature/EverySwitch/SmallLaunchpadIconSwitch.swift:36-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 6 call sites, so a change lands once.
Duplicated predicate Modules/Sources/AppFeature/EverySwitch/KeepAwakeSwitch.swift:134— `endTimeToday >= nowTimeInterval - 1 && endTimeToday <= nowTimeInterval + 1` appears character-identically in 2 files — Modules/Sources/AppFeature/EverySwitch/KeepAwakeSwitch.swift, Modules/Sources/AppFeature/EverySwitch/NightShiftSwitch.swift. 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 Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:69— `error.code == .upgradeRequired || error.code == .actionNotSupported` appears character-identically in 2 files — Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift, Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerFeature.swift. 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 Modules/Sources/AppFeature/Features/DisplayBrightness/DisplayBrightnessKeyTap.swift:150— `event.flags.contains(.maskShift) && event.flags.contains(.maskAlternate)` appears character-identically in 2 files — Modules/Sources/AppFeature/Features/DisplayBrightness/DisplayBrightnessKeyTap.swift, Modules/Sources/AppFeature/Features/SoundMixer/DisplayVolumeKeyTap.swift. 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 Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsagePresentation.swift:7— `horizontalSizeClass == .regular && availableWidth >= 700` appears character-identically in 2 files — Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsagePresentation.swift, Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsagePresentation.swift. 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 Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift:25— `isVisible && isEntitled && selectedMacID != nil && connectionState == .authenticated` appears character-identically in 3 files — Modules/Sources/OnlyRemoteFeature/Features/Brightness/RemoteBrightnessFeature.swift, Modules/Sources/OnlyRemoteFeature/Features/Screenshots/RemoteScreenshotsFeature.swift, Modules/Sources/OnlyRemoteFeature/Features/SoundMixer/RemoteSoundMixerFeature.swift. 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 Modules/Sources/XcodeCleaner/CleanerBatchConfirmationView.swift:18— `item.category == .simulatorDevice || item.category == .simulatorRuntime` appears character-identically in 2 files — Modules/Sources/XcodeCleaner/CleanerBatchConfirmationView.swift, Modules/Sources/XcodeCleaner/XcodeCleanerView.swift. 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 Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift:116— `self == .unavailable || self == .invalidResponse || self == .serverFailure` appears character-identically in 2 files — Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift, Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageFeature.swift. 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 Modules/Sources/OnlyAgent/ClaudeUsage/ClaudeUsageView.swift:72— `snapshot.session == nil && snapshot.weekly == nil && snapshot.models.isEmpty` appears character-identically in 2 files — Modules/Sources/OnlyAgent/ClaudeUsage/ClaudeUsageView.swift, Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageView.swift. 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 Modules/Sources/AppFeature/EverySwitch/KeepAwakeSwitch.swift:139— `startTimeToday >= nowTimeInterval - 1 && startTimeToday <= nowTimeInterval + 1` appears character-identically in 2 files — Modules/Sources/AppFeature/EverySwitch/KeepAwakeSwitch.swift, Modules/Sources/AppFeature/EverySwitch/NightShiftSwitch.swift. 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 Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift:98— `state.activeRequestID != nil || state.isLoading` appears character-identically in 2 files — Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift, Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageFeature.swift. 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 Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift:39— `state.selectedMacID != macID || state.authenticatedSessionID != sessionID` appears character-identically in 2 files — Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageFeature.swift, Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageFeature.swift. 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 Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteCredentialStore+PreparedReplacements.swift:62— `status == errSecSuccess || status == errSecItemNotFound` appears character-identically in 5 files — Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteCredentialStore+PreparedReplacements.swift, Modules/Sources/AppFeature/Features/RemoteAccess/Host/RemoteCredentialStore.swift, Modules/Sources/Extensions/KeychainManager.swift, Modules/Sources/OnlyRemoteFeature/Dependencies/RemoteKeychainClient.swift. 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 Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageView.swift:18— `store.isLoading || store.selectedMacID == nil || store.authenticatedSessionID == nil` appears character-identically in 2 files — Modules/Sources/OnlyRemoteFeature/Features/ClaudeUsage/RemoteClaudeUsageView.swift, Modules/Sources/OnlyRemoteFeature/Features/CodexUsage/RemoteCodexUsageView.swift. 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 Modules/Sources/AppFeature/Features/RemoteAccess/Catalog/RemoteCatalogProvider+Live.swift:31— `type != .xcodeCleaner && type != .appUninstaller && type != .tailscale` appears character-identically in 3 files — Modules/Sources/AppFeature/Features/RemoteAccess/Catalog/RemoteCatalogProvider+Live.swift, Modules/Sources/AppFeature/Features/RemoteAccess/Commands/RemoteCommandRouter+Live.swift, Modules/Sources/AppFeature/Features/RemoteAccess/Commands/RemoteCommandRouter.swift. 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 Modules/Sources/AppFeature/EverySwitch/ScrollDirectionEventTap.swift:153— `type == .tapDisabledByTimeout || type == .tapDisabledByUserInput` appears character-identically in 3 files — Modules/Sources/AppFeature/EverySwitch/ScrollDirectionEventTap.swift, Modules/Sources/AppFeature/Features/DisplayBrightness/DisplayBrightnessKeyTap.swift, Modules/Sources/AppFeature/Features/SoundMixer/DisplayVolumeKeyTap.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Orphaned file Modules/Sources/Authenticator/OtpAuthImport.swift: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 Modules/Sources/Extensions/KeychainStorageKey.swift: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 Modules/Sources/OnlyAgent/Settings/OpenAISettings/OpenAISettingReducer.swift: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 Modules/Sources/OnlyAgent/Settings/OpenAISettings/OpenAISettingView.swift: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 Modules/Sources/Utilities/KeychainManager.swift: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 Modules/Sources/Extensions/KeychainManager.swift: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 Modules/Sources/OnlyAgent/Settings/GeminiSettings/GeminiSettingReducer.swift: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 Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeSettingReducer.swift: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 Modules/Sources/OnlyAgent/Settings/GeminiSettings/GeminiSettingView.swift: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.
Silent fallback default in catch Modules/Sources/AppFeature/EverySwitch/XcodeCacheSwitch.swift:54— `currentInfo` turns every thrown error into `""` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). 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 at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch Modules/Sources/AppFeature/Utilities/BluetoothDevicesManager.swift:68— `getAirPodsBattery` turns every thrown error into `""` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). 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 at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch Modules/Sources/Extensions/String++.swift:93— `groups` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). 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 at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch Modules/Sources/Extensions/LocalizedString++.swift:79— `regulayExpression` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). 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 at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch Modules/Sources/OnlyWidgetFeature/Widgets/Evolution/Intents/EvolutionEntity.swift:31— `allEvolutions` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). 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 at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Hand-rolled JSON/XML parsing via regex Modules/Sources/RemoteCore/AphroditeRemoteModels.swift:11— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This Swift code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex Modules/Sources/Aphrodite/AphroditeIconValidation.swift:7— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This Swift code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex Modules/Sources/Aphrodite/AphroditeReducer.swift:401— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This Swift code already uses a real parser in the same package; use it here too.
D21 · Naming Consistency· `stickerId` spells `Id` where 471 names in the project spell it `ID` · ×1
`stickerId` spells `Id` where 471 names in the project spell it `ID` Modules/Sources/AppFeature/EverySwitch/TopStickerSwitch.swift:162— 471 of 472 names in project Modules~Aphrodite spell the token `ID` (471 of 472; unit: names in project Modules~Aphrodite containing `ID`). Peers: AphroditeApp.conversationID (Modules/Sources/Aphrodite/AphroditeApp.swift:10); AphroditeApp.init(conversationID) (Modules/Sources/Aphrodite/AphroditeApp.swift:15); AphroditeAppOrigin.appID (Modules/Sources/Aphrodite/AphroditeAppOrigin.swift:6); AphroditeAppOrigin.init(appID) (Modules/Sources/Aphrodite/AphroditeAppOrigin.swift:8); AphroditeGeneratedDocumentSchemeHandler.appID (Modules/Sources/Aphrodite/AphroditeGeneratedDocumentSchemeHandler.swift:9). Rename to `stickerID`. [rule N6]
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 9 of 461 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; 461 of the 915 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: Modules/Sources/Authenticator/OtpAuthImport.swift, Modules/Sources/Extensions/KeychainStorageKey.swift, Modules/Sources/OnlyAgent/Settings/OpenAISettings/OpenAISettingReducer.swift, Modules/Sources/OnlyAgent/Settings/OpenAISettings/OpenAISettingView.swift, Modules/Sources/Extensions/KeychainManager.swift, Modules/Sources/Utilities/KeychainManager.swift, Modules/Sources/OnlyAgent/Settings/GeminiSettings/GeminiSettingReducer.swift, Modules/Sources/OnlyAgent/Settings/ClaudeSettings/ClaudeSettingReducer.swift (and 1 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P10 · Library API & versioning· No explicit versioning · ×1
No explicit versioning Modules/Package.swift— No explicit version was found for the SwiftPM library declared by `Package.swift`. This check read nothing in Package.swift, which has no version field, and a CHANGELOG/CHANGES/HISTORY/NEWS/RELEASES file with a semver heading, or release tooling (changesets, release-please, semantic-release, goreleaser, cargo-release, bump2version, standard-version, git-cliff) in the library's directory or at the repository root, or a semver release tag (or a Drupal `8.x-1.2` release tag) in the repository. A version computed where none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes.
Logging is not universal — Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`.
No SAST — No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
Outdated: abseil-cpp-binary — `abseil-cpp-binary` is resolved at 1.2024072200.0, but 1.2025051202.0 is the newest release tagged on https://github.com/google/abseil-cpp-binary.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update abseil-cpp-binary` reaches this one with no change to Package.swift.
Outdated: aiproxyswift — `aiproxyswift` is resolved at 0.146.0, but 0.157.0 is the newest release tagged on https://github.com/lzell/AIProxySwift within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update aiproxyswift` reaches this one with no change to Package.swift.
Outdated: alamofire — `alamofire` is resolved at 5.5.0, but 5.12.2 is the newest release tagged on https://github.com/Alamofire/Alamofire within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update alamofire` reaches this one with no change to Package.swift.
Outdated: alamofire — `alamofire` is resolved at 5.5.0, but 5.12.2 is the newest release tagged on https://github.com/Alamofire/Alamofire.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update alamofire` reaches this one with no change to Package.swift.
Outdated: app-check — `app-check` is resolved at 11.2.0, but 11.3.2 is the newest release tagged on https://github.com/google/app-check.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update app-check` reaches this one with no change to Package.swift.
Outdated: combine-schedulers — `combine-schedulers` is resolved at 1.0.2, but 1.2.2 is the newest release tagged on https://github.com/pointfreeco/combine-schedulers within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update combine-schedulers` reaches this one with no change to Package.swift.
Outdated: firebase-ios-sdk — `firebase-ios-sdk` is resolved at 12.6.0, but 12.19.3 is the newest release tagged on https://github.com/firebase/firebase-ios-sdk within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update firebase-ios-sdk` reaches this one with no change to Package.swift.
Outdated: firebase-ios-sdk — `firebase-ios-sdk` is resolved at 12.6.0, but 12.19.3 is the newest release tagged on https://github.com/firebase/firebase-ios-sdk.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update firebase-ios-sdk` reaches this one with no change to Package.swift.
Outdated: google-ads-on-device-conversion-ios-sdk — `google-ads-on-device-conversion-ios-sdk` is resolved at 3.2.0, but 3.8.0 is the newest release tagged on https://github.com/googleads/google-ads-on-device-conversion-ios-sdk within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update google-ads-on-device-conversion-ios-sdk` reaches this one with no change to Package.swift.
Outdated: googleappmeasurement — `googleappmeasurement` is resolved at 12.5.0, but 12.19.2 is the newest release tagged on https://github.com/google/GoogleAppMeasurement.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update googleappmeasurement` reaches this one with no change to Package.swift.
Outdated: googledatatransport — `googledatatransport` is resolved at 10.1.0, but 10.1.1 is the newest release tagged on https://github.com/google/GoogleDataTransport.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update googledatatransport` reaches this one with no change to Package.swift.
Outdated: googleutilities — `googleutilities` is resolved at 8.1.0, but 8.1.5 is the newest release tagged on https://github.com/google/GoogleUtilities.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update googleutilities` reaches this one with no change to Package.swift.
Outdated: grdb.swift — `grdb.swift` is resolved at 7.10.0, but 7.12.0 is the newest release tagged on https://github.com/groue/GRDB.swift.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update grdb.swift` reaches this one with no change to Package.swift.
Outdated: grpc-binary — `grpc-binary` is resolved at 1.69.1, but 1.83.1 is the newest release tagged on https://github.com/google/grpc-binary.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update grpc-binary` reaches this one with no change to Package.swift.
Outdated: gtm-session-fetcher — `gtm-session-fetcher` is resolved at 5.0.0, but 5.3.1 is the newest release tagged on https://github.com/google/gtm-session-fetcher.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update gtm-session-fetcher` reaches this one with no change to Package.swift.
Outdated: nanopb — `nanopb` is resolved at 2.30910.0, but 2.30910.1 is the newest release tagged on https://github.com/firebase/nanopb.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update nanopb` reaches this one with no change to Package.swift.
Outdated: networkimage — `networkimage` is resolved at 6.0.0, but 6.0.1 is the newest release tagged on https://github.com/gonzalezreal/NetworkImage within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update networkimage` reaches this one with no change to Package.swift.
Outdated: promises — `promises` is resolved at 2.4.0, but 2.4.1 is the newest release tagged on https://github.com/google/promises.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update promises` reaches this one with no change to Package.swift.
Outdated: sparkle — `sparkle` is resolved at 2.10.0, but 2.10.1 is the newest release tagged on https://github.com/sparkle-project/Sparkle within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update sparkle` reaches this one with no change to Package.swift.
Outdated: swift-case-paths — `swift-case-paths` is resolved at 1.7.0, but 1.10.0 is the newest release tagged on https://github.com/pointfreeco/swift-case-paths within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-case-paths` reaches this one with no change to Package.swift.
Outdated: swift-clocks — `swift-clocks` is resolved at 1.0.5, but 1.1.1 is the newest release tagged on https://github.com/pointfreeco/swift-clocks within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-clocks` reaches this one with no change to Package.swift.
Outdated: swift-collections — `swift-collections` is resolved at 1.1.1, but 1.7.6 is the newest release tagged on https://github.com/apple/swift-collections within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-collections` reaches this one with no change to Package.swift.
Outdated: swift-concurrency-extras — `swift-concurrency-extras` is resolved at 1.3.2, but 1.4.3 is the newest release tagged on https://github.com/pointfreeco/swift-concurrency-extras within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-concurrency-extras` reaches this one with no change to Package.swift.
Outdated: swift-custom-dump — `swift-custom-dump` is resolved at 1.5.0, but 1.7.3 is the newest release tagged on https://github.com/pointfreeco/swift-custom-dump within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-custom-dump` reaches this one with no change to Package.swift.
Outdated: swift-custom-dump — `swift-custom-dump` is resolved at 1.3.3, but 1.7.3 is the newest release tagged on https://github.com/pointfreeco/swift-custom-dump within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-custom-dump` reaches this one with no change to Package.swift.
Skipped (documented): sidebarTitlesRefreshAfterLanguageChange Modules/Tests/AppFeatureTests/OnlySwitchTests.swift:589— Skipped with a documented reason — a deferral, not lazy debt: Requires the app host after package migration: hosts SettingsView in an NSWindow and pumps the main run loop
Skipped (documented): splitViewDetailRendersRestoredSelection Modules/Tests/AppFeatureTests/OnlySwitchTests.swift:636— Skipped with a documented reason — a deferral, not lazy debt: Requires the app host after package migration: hosts SettingsView in an NSWindow and pumps the main run loop
Skipped (documented): helperProcessesShortCommandsBeforeItsInputPipeCloses Modules/Tests/AppFeatureTests/OwnPlaybackSourceTests.swift:93— Skipped with a documented reason — a deferral, not lazy debt: Requires the app host after package migration: launches the OnlySwitch executable as the playback helper
Skipped (documented): everySavedToolAppearsInManifestRegardlessOfLegacySharingKey Modules/Tests/ModulesTests/AphroditeRemoteSnapshotEncoderTests.swift:12— Skipped with a documented reason — a deferral, not lazy debt: disabled by a .disabled(…) trait
Skipped (documented): obsoleteSharingBooleanDoesNotChangeDecodedApp Modules/Tests/ModulesTests/AphroditeTests.swift:1332— Skipped with a documented reason — a deferral, not lazy debt: disabled by a .disabled(…) trait
Skipped (documented): mapsStatusToRecoveryPresentation Modules/Tests/AppFeatureTests/PrivilegedOperations/PrivilegedAccessViewModelTests.swift:11— Skipped with a documented reason — a deferral, not lazy debt: Privileged access disabled
Skipped (documented): liveStoreMigratesLegacyKeychainDevices Modules/Tests/AppFeatureTests/RemoteAccess/RemoteCredentialStoreTests.swift:49— Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
Skipped (documented): legacyMigrationKeepsExistingDataProtectionItem Modules/Tests/AppFeatureTests/RemoteAccess/RemoteCredentialStoreTests.swift:82— Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 75 file(s) — `Modules/Sources/Aphrodite/AphroditeApp.swift`, `Modules/Sources/Aphrodite/AphroditeIconValidation.swift`, `Modules/Sources/Aphrodite/AphroditeReducer.swift`, `Modules/Sources/AppFeature/EverySwitch/ReverseScrollDirectionSwitch.swift`, `Modules/Sources/AppFeature/Features/DockPreview/DockPreviewClient.swift`, … (+70 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
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 01a1dc02-86c8-7ea2-8729-e48a77cda4ac · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 45 · Warnings: 965 · Recommendations: 38 · Info: 44 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 21:41 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.