Public report of muxy-app/muxy, published 15 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, 15 November 2026, 01:22 UTC · Survey ID cd_bb053d9e60444e0fb4501b07d12d113d
muxy-app/muxy
Measured 15 November 2026, 01:21 UTC, at code version 08bbdd0
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
Down 10 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 237,231 lines of product code in 11 projects, tests not counted · Estimated rebuild effort: about 1.8 person-years · Weakest lens: Code Health, 38
Findings by how serious they are
69 critical778 serious53 minor
12 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
15 November 2026, 01:21 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 ▸
59of 59 dimensions measured by tools.
873of 900 findings point to an exact file and line, so you can open each one in the code. The other 27 concern the repository as a whole, such as missing documentation.
59dimensions across 8 lenses, read from 237,231 lines of product code in 11 projects.
muxy-app/muxy falls short of our standard for production, held back most by its Code Health lens, the quality of the code itself. It scores 50 out of 100 and is rated Weak, and 68 of its 69 critical findings are security problems.
Code Health, at 38, is the weakest lens and counts most in the score. The best first steps are adding type checking and splitting the oversized files, each worth about 6 points. Raising Code Health to 70 would lift the score to about 59.
Fifty-five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Nine passwords or keys are open to anyone who can read the repository, and three secrets can leak from the build pipeline. Pinning each tool to an exact version, replacing each exposed password or key and limiting each secret to its own step would close these risks. Fixing the weaknesses the scanner points to would fix the security weakness in the code. Making recorded events unchangeable would take care of the recorded event that can be changed afterwards.
The product code is 237,231 lines, about €260,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Code Health rose from 38 to 70, the lowest score rated Strong, the score would rise from 50 to about 59.
Code composition: what the lines of code are
Product code 86%Tests 14%
New since the last survey: 383 findings
These 383 critical or serious findings weren't in the previous survey, on 29 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
God Classes · FileTooLong: webviews/panels.rs crates/muxy-app/src/model/webviews/panels.rs
God Classes · FileTooLong: workspace/commands.rs crates/muxy-app/src/views/workspace/commands.rs
God Classes · FileTooLong: views/move_drag.rs crates/muxy-app/src/views/move_drag.rs
God Classes · TooManyFunctions: muxy_app::views::workspace::commands::available crates/muxy-app/src/views/workspace/commands/available.rs
God Classes · TooManyMethods: Connection crates/muxy-server/src/connection/peer.rs
God Classes · FileTooLong: onboarding/steps.rs crates/muxy-app/src/views/onboarding/steps.rs
God Classes · FileTooLong: extensions/publish.rs crates/muxy-app/src/extensions/publish.rs
God Classes · FileTooLong: extensions/detail.rs crates/muxy-app/src/views/settings/extensions/detail.rs
God Classes · FileTooLong: views/servers_page.rs crates/muxy-app/src/views/servers_page.rs
God Classes · ClassTooLong: SettingsTab crates/muxy-app/src/views/settings/tab.rs
God Classes · TooManyMethods: NativeBrowser crates/muxy-ui/src/browser/unsupported.rs
God Classes · MethodTooLong: ExtensionsView.render crates/muxy-app/src/views/settings/extensions.rs
God Classes · MethodTooLong: Requests.route crates/muxy-server/src/connection/reader.rs
God Classes · FileTooLong: src/graphics.rs crates/muxy-terminal/src/graphics.rs
God Classes · MethodTooLong: ExtensionsView.gallery crates/muxy-app/src/views/settings/extensions/detail.rs
God Classes · FileTooLong: model/tab_windows.rs crates/muxy-app/src/model/tab_windows.rs
God Classes · TooManyFields: TextInput crates/muxy-ui/src/text_input.rs
God Classes · FileTooLong: extensions/cards.rs crates/muxy-app/src/views/settings/extensions/cards.rs
God Classes · FileTooLong: connection/reader.rs crates/muxy-server/src/connection/reader.rs
God Classes · FileTooLong: src/tab_windows.rs crates/muxy-app-core/src/tab_windows.rs
God Classes · FileTooLong: extensions/authoring.rs crates/muxy-app/src/model/extensions/authoring.rs
God Classes · ClassTooLong: ProjectPicker crates/muxy-app/src/views/project_picker.rs
God Classes · FileTooLong: extensions/consent.rs crates/muxy-app/src/model/extensions/consent.rs
God Classes · ClassTooLong: Webview crates/muxy-app/src/views/webview/mod.rs
God Classes · FileTooLong: views/splits.rs crates/muxy-app/src/views/splits.rs
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: 141 findings
These 141 critical or serious findings were in the previous survey, on 29 October 2026, and are gone from this one. The first 100 are listed here.
€85,000 to €430,000, for 1,422 to 4,512 hours of work, about 1.8 person-years for 1 to 4 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.7 at a score of 50. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 237,231 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
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Raises the score by about 6 points · Medium effort · Type Safety
2
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Raises the score by about 6 points · Medium effort · Large Files
3
Resolve the 9 REDACTED finding(s) in Secrets (history) — start with REDACTED (9).
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 €260,000 to build again, about 1.8 person-years of work. Its weakest lens is Code Health, at 38 (Weak). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up. Of all the actions in this report, it raises the score most for the work it takes: about 6 points for medium effort. 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 7.4 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 521,390 lines over the last 90 days, which is about 2,114,526 lines a year. At that pace, the extra work comes to an estimated 105.7 to 704.8 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.
858 modules, with 3587 dependencies between them. 24 loops run through 187 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 818 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
13 pairs of types, where a type in gpui.element uses a type in gpui.window.
The types involved
gpui.element.AnyElement → gpui.window.ElementId
gpui.element.AnyElement → gpui.window.FocusHandle
gpui.element.AnyElement → gpui.window.Window
gpui.element.Component → gpui.window.ElementId
gpui.element.Component → gpui.window.Window
gpui.element.Drawable → gpui.window.Window
gpui.element.Element → gpui.window.ElementId
gpui.element.Element → gpui.window.Window
gpui.element.ElementObject → gpui.window.Window
gpui.element.Empty → gpui.window.ElementId
gpui.element.Empty → gpui.window.Window
gpui.element.Render → gpui.window.Window
gpui.element.RenderOnce → gpui.window.Window
Direction
gpui.element uses gpui.window, so a change to gpui.window can break gpui.element, while a change to gpui.element can't break gpui.window.
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→28 gpui.element uses gpui.app.contextpart of a loop✕
Connections
2 pairs of types, where a type in gpui.element uses a type in gpui.app.context.
The types involved
gpui.element.Empty → gpui.app.context.Context
gpui.element.Render → gpui.app.context.Context
Direction
gpui.element uses gpui.app.context, so a change to gpui.app.context can break gpui.element, while a change to gpui.element can't break gpui.app.context.
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 pairs of types, where a type in gpui.element uses a type in gpui.app.
The types involved
gpui.element.AnyElement → gpui.app.App
gpui.element.Component → gpui.app.App
gpui.element.Drawable → gpui.app.App
gpui.element.Element → gpui.app.App
gpui.element.ElementObject → gpui.app.App
gpui.element.Empty → gpui.app.App
gpui.element.RenderOnce → gpui.app.App
Direction
gpui.element uses gpui.app, so a change to gpui.app can break gpui.element, while a change to gpui.element can't break gpui.app.
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→28 gpui.executor uses gpui.app.contextpart of a loop✕
Connections
1 pair of types, where a type in gpui.executor uses a type in gpui.app.context.
The types involved
gpui.executor.Task → gpui.app.context.Context
Direction
gpui.executor uses gpui.app.context, so a change to gpui.app.context can break gpui.executor, while a change to gpui.executor can't break gpui.app.context.
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.
gpui.platform.keystroke uses gpui.style, so a change to gpui.style can break gpui.platform.keystroke, while a change to gpui.platform.keystroke can't break gpui.style.
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.
muxy_protocol.control uses muxy_protocol.path, so a change to muxy_protocol.path can break muxy_protocol.control, while a change to muxy_protocol.control can't break muxy_protocol.path.
Position
Below the diagonal: muxy_protocol.control uses a module listed above it, which is the healthy direction.
muxy_protocol.control uses muxy_protocol.screen, so a change to muxy_protocol.screen can break muxy_protocol.control, while a change to muxy_protocol.control can't break muxy_protocol.screen.
Position
Below the diagonal: muxy_protocol.control uses a module listed above it, which is the healthy direction.
muxy_protocol.session uses muxy_protocol.ids, so a change to muxy_protocol.ids can break muxy_protocol.session, while a change to muxy_protocol.session can't break muxy_protocol.ids.
Position
Below the diagonal: muxy_protocol.session uses a module listed above it, which is the healthy direction.
muxy_protocol.session uses muxy_protocol.path, so a change to muxy_protocol.path can break muxy_protocol.session, while a change to muxy_protocol.session can't break muxy_protocol.path.
Position
Below the diagonal: muxy_protocol.session uses a module listed above it, which is the healthy direction.
muxy_protocol.session uses muxy_protocol.screen, so a change to muxy_protocol.screen can break muxy_protocol.session, while a change to muxy_protocol.session can't break muxy_protocol.screen.
Position
Below the diagonal: muxy_protocol.session uses a module listed above it, which is the healthy direction.
11→15 muxy_protocol.session uses muxy_protocol.projectpart of a loop✕
Connections
2 pairs of types, where a type in muxy_protocol.session uses a type in muxy_protocol.project.
muxy_protocol.session uses muxy_protocol.project, so a change to muxy_protocol.project can break muxy_protocol.session, while a change to muxy_protocol.session can't break muxy_protocol.project.
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.
gpui.interactive uses gpui.element, so a change to gpui.element can break gpui.interactive, while a change to gpui.interactive can't break gpui.element.
Position
Below the diagonal: gpui.interactive uses a module listed above it, which is the healthy direction.
gpui.interactive uses gpui.platform.keystroke, so a change to gpui.platform.keystroke can break gpui.interactive, while a change to gpui.interactive can't break gpui.platform.keystroke.
Position
Below the diagonal: gpui.interactive uses a module listed above it, which is the healthy direction.
12→22 gpui.interactive uses gpui.geometrypart of a loop✕
Connections
10 pairs of types, where a type in gpui.interactive uses a type in gpui.geometry.
gpui.interactive uses gpui.geometry, so a change to gpui.geometry can break gpui.interactive, while a change to gpui.interactive can't break gpui.geometry.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→26 gpui.interactive uses gpui.windowpart of a loop✕
Connections
1 pair of types, where a type in gpui.interactive uses a type in gpui.window.
gpui.interactive uses gpui.app.context, so a change to gpui.app.context can break gpui.interactive, while a change to gpui.interactive can't break gpui.app.context.
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.
gpui.shared_string uses gpui.element, so a change to gpui.element can break gpui.shared_string, while a change to gpui.shared_string can't break gpui.element.
Position
Below the diagonal: gpui.shared_string uses a module listed above it, which is the healthy direction.
13→22 gpui.shared_string uses gpui.geometrypart of a loop✕
Connections
1 pair of types, where a type in gpui.shared_string uses a type in gpui.geometry.
gpui.shared_string uses gpui.geometry, so a change to gpui.geometry can break gpui.shared_string, while a change to gpui.shared_string can't break gpui.geometry.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→24 gpui.shared_string uses gpui.stylepart of a loop✕
Connections
1 pair of types, where a type in gpui.shared_string uses a type in gpui.style.
gpui.shared_string uses gpui.style, so a change to gpui.style can break gpui.shared_string, while a change to gpui.shared_string can't break gpui.style.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→26 gpui.shared_string uses gpui.windowpart of a loop✕
Connections
2 pairs of types, where a type in gpui.shared_string uses a type in gpui.window.
gpui.shared_string uses gpui.window, so a change to gpui.window can break gpui.shared_string, while a change to gpui.shared_string can't break gpui.window.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→31 gpui.shared_string uses gpui.apppart of a loop✕
Connections
1 pair of types, where a type in gpui.shared_string uses a type in gpui.app.
The types involved
gpui.shared_string.SharedString → gpui.app.App
Direction
gpui.shared_string uses gpui.app, so a change to gpui.app can break gpui.shared_string, while a change to gpui.shared_string can't break gpui.app.
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.
muxy_app.extensions.pictures uses gpui.scene, so a change to gpui.scene can break muxy_app.extensions.pictures, while a change to muxy_app.extensions.pictures can't break gpui.scene.
Position
Below the diagonal: muxy_app.extensions.pictures uses a module listed above it, which is the healthy direction.
muxy_protocol.project uses muxy_protocol.ids, so a change to muxy_protocol.ids can break muxy_protocol.project, while a change to muxy_protocol.project can't break muxy_protocol.ids.
Position
Below the diagonal: muxy_protocol.project uses a module listed above it, which is the healthy direction.
muxy_protocol.project uses muxy_protocol.path, so a change to muxy_protocol.path can break muxy_protocol.project, while a change to muxy_protocol.project can't break muxy_protocol.path.
Position
Below the diagonal: muxy_protocol.project uses a module listed above it, which is the healthy direction.
muxy_protocol.project uses muxy_protocol.session, so a change to muxy_protocol.session can break muxy_protocol.project, while a change to muxy_protocol.project can't break muxy_protocol.session.
Position
Below the diagonal: muxy_protocol.project uses a module listed above it, which is the healthy direction.
gpui.elements.div uses gpui.element, so a change to gpui.element can break gpui.elements.div, while a change to gpui.elements.div can't break gpui.element.
Position
Below the diagonal: gpui.elements.div uses a module listed above it, which is the healthy direction.
gpui.elements.div uses gpui.interactive, so a change to gpui.interactive can break gpui.elements.div, while a change to gpui.elements.div can't break gpui.interactive.
Position
Below the diagonal: gpui.elements.div uses a module listed above it, which is the healthy direction.
gpui.elements.div uses gpui.shared_string, so a change to gpui.shared_string can break gpui.elements.div, while a change to gpui.elements.div can't break gpui.shared_string.
Position
Below the diagonal: gpui.elements.div uses a module listed above it, which is the healthy direction.
16→22 gpui.elements.div uses gpui.geometrypart of a loop✕
Connections
17 pairs of types, where a type in gpui.elements.div uses a type in gpui.geometry.
gpui.elements.div uses gpui.geometry, so a change to gpui.geometry can break gpui.elements.div, while a change to gpui.elements.div can't break gpui.geometry.
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.
16→24 gpui.elements.div uses gpui.stylepart of a loop✕
Connections
1 pair of types, where a type in gpui.elements.div uses a type in gpui.style.
gpui.elements.div uses gpui.window, so a change to gpui.window can break gpui.elements.div, while a change to gpui.elements.div can't break gpui.window.
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.
16→31 gpui.elements.div uses gpui.apppart of a loop✕
Connections
7 pairs of types, where a type in gpui.elements.div uses a type in gpui.app.
The types involved
gpui.elements.div.Div → gpui.app.App
gpui.elements.div.DragMoveEvent → gpui.app.App
gpui.elements.div.GroupHitboxes → gpui.app.App
gpui.elements.div.Interactivity → gpui.app.App
gpui.elements.div.ScrollAnchor → gpui.app.App
gpui.elements.div.Stateful → gpui.app.App
gpui.elements.div.div$module → gpui.app.App
Direction
gpui.elements.div uses gpui.app, so a change to gpui.app can break gpui.elements.div, while a change to gpui.elements.div can't break gpui.app.
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.
gpui.platform uses gpui.platform.keystroke, so a change to gpui.platform.keystroke can break gpui.platform, while a change to gpui.platform can't break gpui.platform.keystroke.
Position
Below the diagonal: gpui.platform uses a module listed above it, which is the healthy direction.
gpui.platform uses gpui.shared_string, so a change to gpui.shared_string can break gpui.platform, while a change to gpui.platform can't break gpui.shared_string.
Position
Below the diagonal: gpui.platform uses a module listed above it, which is the healthy direction.
17→22 gpui.platform uses gpui.geometrypart of a loop✕
Connections
22 pairs of types, where a type in gpui.platform uses a type in gpui.geometry.
muxy_app_core.ids uses muxy_protocol.project, so a change to muxy_protocol.project can break muxy_app_core.ids, while a change to muxy_app_core.ids can't break muxy_protocol.project.
Position
Below the diagonal: muxy_app_core.ids uses a module listed above it, which is the healthy direction.
muxy_client.client uses muxy_protocol.ids, so a change to muxy_protocol.ids can break muxy_client.client, while a change to muxy_client.client can't break muxy_protocol.ids.
Position
Below the diagonal: muxy_client.client uses a module listed above it, which is the healthy direction.
muxy_client.client uses muxy_protocol.path, so a change to muxy_protocol.path can break muxy_client.client, while a change to muxy_client.client can't break muxy_protocol.path.
Position
Below the diagonal: muxy_client.client uses a module listed above it, which is the healthy direction.
muxy_client.client uses muxy_protocol.screen, so a change to muxy_protocol.screen can break muxy_client.client, while a change to muxy_client.client can't break muxy_protocol.screen.
Position
Below the diagonal: muxy_client.client uses a module listed above it, which is the healthy direction.
muxy_client.client uses muxy_protocol.control, so a change to muxy_protocol.control can break muxy_client.client, while a change to muxy_client.client can't break muxy_protocol.control.
Position
Below the diagonal: muxy_client.client uses a module listed above it, which is the healthy direction.
muxy_client.client uses muxy_protocol.session, so a change to muxy_protocol.session can break muxy_client.client, while a change to muxy_client.client can't break muxy_protocol.session.
Position
Below the diagonal: muxy_client.client uses a module listed above it, which is the healthy direction.
muxy_client.client uses muxy_protocol.project, so a change to muxy_protocol.project can break muxy_client.client, while a change to muxy_client.client can't break muxy_protocol.project.
Position
Below the diagonal: muxy_client.client uses a module listed above it, which is the healthy direction.
muxy_protocol.activity uses muxy_protocol.ids, so a change to muxy_protocol.ids can break muxy_protocol.activity, while a change to muxy_protocol.activity can't break muxy_protocol.ids.
Position
Below the diagonal: muxy_protocol.activity uses a module listed above it, which is the healthy direction.
muxy_protocol.activity uses muxy_protocol.project, so a change to muxy_protocol.project can break muxy_protocol.activity, while a change to muxy_protocol.activity can't break muxy_protocol.project.
Position
Below the diagonal: muxy_protocol.activity uses a module listed above it, which is the healthy direction.
muxy_server.registry uses muxy_protocol.ids, so a change to muxy_protocol.ids can break muxy_server.registry, while a change to muxy_server.registry can't break muxy_protocol.ids.
Position
Below the diagonal: muxy_server.registry uses a module listed above it, which is the healthy direction.
muxy_server.registry uses muxy_protocol.path, so a change to muxy_protocol.path can break muxy_server.registry, while a change to muxy_server.registry can't break muxy_protocol.path.
Position
Below the diagonal: muxy_server.registry uses a module listed above it, which is the healthy direction.
muxy_server.registry uses muxy_protocol.screen, so a change to muxy_protocol.screen can break muxy_server.registry, while a change to muxy_server.registry can't break muxy_protocol.screen.
Position
Below the diagonal: muxy_server.registry uses a module listed above it, which is the healthy direction.
muxy_server.registry uses muxy_protocol.control, so a change to muxy_protocol.control can break muxy_server.registry, while a change to muxy_server.registry can't break muxy_protocol.control.
Position
Below the diagonal: muxy_server.registry uses a module listed above it, which is the healthy direction.
muxy_server.registry uses muxy_protocol.session, so a change to muxy_protocol.session can break muxy_server.registry, while a change to muxy_server.registry can't break muxy_protocol.session.
Position
Below the diagonal: muxy_server.registry uses a module listed above it, which is the healthy direction.
muxy_server.registry uses muxy_protocol.project, so a change to muxy_protocol.project can break muxy_server.registry, while a change to muxy_server.registry can't break muxy_protocol.project.
Position
Below the diagonal: muxy_server.registry uses a module listed above it, which is the healthy direction.
gpui.geometry uses gpui.elements.div, so a change to gpui.elements.div can break gpui.geometry, while a change to gpui.geometry can't break gpui.elements.div.
Position
Below the diagonal: gpui.geometry uses a module listed above it, which is the healthy direction.
muxy_app.boot uses muxy_protocol.ids, so a change to muxy_protocol.ids can break muxy_app.boot, while a change to muxy_app.boot can't break muxy_protocol.ids.
Position
Below the diagonal: muxy_app.boot uses a module listed above it, which is the healthy direction.
muxy_app.boot uses muxy_protocol.control, so a change to muxy_protocol.control can break muxy_app.boot, while a change to muxy_app.boot can't break muxy_protocol.control.
Position
Below the diagonal: muxy_app.boot uses a module listed above it, which is the healthy direction.
muxy_app.boot uses muxy_protocol.session, so a change to muxy_protocol.session can break muxy_app.boot, while a change to muxy_app.boot can't break muxy_protocol.session.
Position
Below the diagonal: muxy_app.boot uses a module listed above it, which is the healthy direction.
muxy_app.boot uses muxy_app.extensions.pictures, so a change to muxy_app.extensions.pictures can break muxy_app.boot, while a change to muxy_app.boot can't break muxy_app.extensions.pictures.
Position
Below the diagonal: muxy_app.boot uses a module listed above it, which is the healthy direction.
muxy_app.boot uses muxy_protocol.project, so a change to muxy_protocol.project can break muxy_app.boot, while a change to muxy_app.boot can't break muxy_protocol.project.
Position
Below the diagonal: muxy_app.boot uses a module listed above it, which is the healthy direction.
muxy_app.boot uses muxy_app_core.ids, so a change to muxy_app_core.ids can break muxy_app.boot, while a change to muxy_app.boot can't break muxy_app_core.ids.
Position
Below the diagonal: muxy_app.boot uses a module listed above it, which is the healthy direction.
gpui.style uses gpui.shared_string, so a change to gpui.shared_string can break gpui.style, while a change to gpui.style can't break gpui.shared_string.
Position
Below the diagonal: gpui.style uses a module listed above it, which is the healthy direction.
gpui.window uses gpui.subscription, so a change to gpui.subscription can break gpui.window, while a change to gpui.window can't break gpui.subscription.
Position
Below the diagonal: gpui.window uses a module listed above it, which is the healthy direction.
gpui.window uses gpui.platform.keystroke, so a change to gpui.platform.keystroke can break gpui.window, while a change to gpui.window can't break gpui.platform.keystroke.
Position
Below the diagonal: gpui.window uses a module listed above it, which is the healthy direction.
gpui.window uses gpui.shared_string, so a change to gpui.shared_string can break gpui.window, while a change to gpui.window can't break gpui.shared_string.
Position
Below the diagonal: gpui.window uses a module listed above it, which is the healthy direction.
gpui.window uses gpui.app.entity_map, so a change to gpui.app.entity_map can break gpui.window, while a change to gpui.window can't break gpui.app.entity_map.
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.
muxy_ui.theme.colors uses gpui.color, so a change to gpui.color can break muxy_ui.theme.colors, while a change to muxy_ui.theme.colors can't break gpui.color.
Position
Below the diagonal: muxy_ui.theme.colors uses a module listed above it, which is the healthy direction.
gpui.app.context uses gpui.subscription, so a change to gpui.subscription can break gpui.app.context, while a change to gpui.app.context can't break gpui.subscription.
Position
Below the diagonal: gpui.app.context uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in gpui.app.context uses a type in gpui.executor.
The types involved
gpui.app.context.Context → gpui.executor.Task
Direction
gpui.app.context uses gpui.executor, so a change to gpui.executor can break gpui.app.context, while a change to gpui.app.context can't break gpui.executor.
Position
Below the diagonal: gpui.app.context uses a module listed above it, which is the healthy direction.
gpui.app.context uses gpui.app.entity_map, so a change to gpui.app.entity_map can break gpui.app.context, while a change to gpui.app.context can't break gpui.app.entity_map.
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.
28→31 gpui.app.context uses gpui.apppart of a loop✕
Connections
1 pair of types, where a type in gpui.app.context uses a type in gpui.app.
The types involved
gpui.app.context.Context → gpui.app.App
Direction
gpui.app.context uses gpui.app, so a change to gpui.app can break gpui.app.context, while a change to gpui.app.context can't break gpui.app.
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.
muxy_ui.theme.metrics uses gpui.geometry, so a change to gpui.geometry can break muxy_ui.theme.metrics, while a change to muxy_ui.theme.metrics can't break gpui.geometry.
Position
Below the diagonal: muxy_ui.theme.metrics uses a module listed above it, which is the healthy direction.
muxy_ui.theme.metrics uses gpui.window, so a change to gpui.window can break muxy_ui.theme.metrics, while a change to muxy_ui.theme.metrics can't break gpui.window.
Position
Below the diagonal: muxy_ui.theme.metrics uses a module listed above it, which is the healthy direction.
gpui.app.entity_map uses gpui.element, so a change to gpui.element can break gpui.app.entity_map, while a change to gpui.app.entity_map can't break gpui.element.
Position
Below the diagonal: gpui.app.entity_map uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in gpui.app.entity_map uses a type in gpui.geometry.
The types involved
gpui.app.entity_map.Entity → gpui.geometry.Bounds
gpui.app.entity_map.Entity → gpui.geometry.Pixels
gpui.app.entity_map.Entity → gpui.geometry.Point
Direction
gpui.app.entity_map uses gpui.geometry, so a change to gpui.geometry can break gpui.app.entity_map, while a change to gpui.app.entity_map can't break gpui.geometry.
Position
Below the diagonal: gpui.app.entity_map uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in gpui.app.entity_map uses a type in gpui.style.
The types involved
gpui.app.entity_map.EntityId → gpui.style.Display
Direction
gpui.app.entity_map uses gpui.style, so a change to gpui.style can break gpui.app.entity_map, while a change to gpui.app.entity_map can't break gpui.style.
Position
Below the diagonal: gpui.app.entity_map uses a module listed above it, which is the healthy direction.
gpui.app.entity_map uses gpui.window, so a change to gpui.window can break gpui.app.entity_map, while a change to gpui.app.entity_map can't break gpui.window.
Position
Below the diagonal: gpui.app.entity_map uses a module listed above it, which is the healthy direction.
gpui.app.entity_map uses gpui.app.context, so a change to gpui.app.context can break gpui.app.entity_map, while a change to gpui.app.entity_map can't break gpui.app.context.
Position
Below the diagonal: gpui.app.entity_map uses a module listed above it, which is the healthy direction.
30→31 gpui.app.entity_map uses gpui.apppart of a loop✕
Connections
1 pair of types, where a type in gpui.app.entity_map uses a type in gpui.app.
The types involved
gpui.app.entity_map.Entity → gpui.app.App
Direction
gpui.app.entity_map uses gpui.app, so a change to gpui.app can break gpui.app.entity_map, while a change to gpui.app.entity_map can't break gpui.app.
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.
gpui.app uses gpui.platform.keystroke, so a change to gpui.platform.keystroke can break gpui.app, while a change to gpui.app can't break gpui.platform.keystroke.
Position
Below the diagonal: gpui.app uses a module listed above it, which is the healthy direction.
muxy_app.model.agents_panel uses muxy_protocol.ids, so a change to muxy_protocol.ids can break muxy_app.model.agents_panel, while a change to muxy_app.model.agents_panel can't break muxy_protocol.ids.
Position
Below the diagonal: muxy_app.model.agents_panel uses a module listed above it, which is the healthy direction.
muxy_app.model.agents_panel uses gpui.executor, so a change to gpui.executor can break muxy_app.model.agents_panel, while a change to muxy_app.model.agents_panel can't break gpui.executor.
Position
Below the diagonal: muxy_app.model.agents_panel uses a module listed above it, which is the healthy direction.
muxy_app.model.agents_panel uses muxy_protocol.project, so a change to muxy_protocol.project can break muxy_app.model.agents_panel, while a change to muxy_app.model.agents_panel can't break muxy_protocol.project.
Position
Below the diagonal: muxy_app.model.agents_panel uses a module listed above it, which is the healthy direction.
muxy_app.model.agents_panel uses gpui.elements.div, so a change to gpui.elements.div can break muxy_app.model.agents_panel, while a change to muxy_app.model.agents_panel can't break gpui.elements.div.
Position
Below the diagonal: muxy_app.model.agents_panel uses a module listed above it, which is the healthy direction.
muxy_app.model.agents_panel uses muxy_app_core.ids, so a change to muxy_app_core.ids can break muxy_app.model.agents_panel, while a change to muxy_app.model.agents_panel can't break muxy_app_core.ids.
Position
Below the diagonal: muxy_app.model.agents_panel uses a module listed above it, which is the healthy direction.
muxy_app.model.agents_panel uses muxy_protocol.activity, so a change to muxy_protocol.activity can break muxy_app.model.agents_panel, while a change to muxy_app.model.agents_panel can't break muxy_protocol.activity.
Position
Below the diagonal: muxy_app.model.agents_panel uses a module listed above it, which is the healthy direction.
muxy_app.model.agents_panel uses gpui.geometry, so a change to gpui.geometry can break muxy_app.model.agents_panel, while a change to muxy_app.model.agents_panel can't break gpui.geometry.
Position
Below the diagonal: muxy_app.model.agents_panel uses a module listed above it, which is the healthy direction.
muxy_app.model.agents_panel uses gpui.style, so a change to gpui.style can break muxy_app.model.agents_panel, while a change to muxy_app.model.agents_panel can't break gpui.style.
Position
Below the diagonal: muxy_app.model.agents_panel uses a module listed above it, which is the healthy direction.
muxy_app.model.agents_panel uses gpui.window, so a change to gpui.window can break muxy_app.model.agents_panel, while a change to muxy_app.model.agents_panel can't break gpui.window.
Position
Below the diagonal: muxy_app.model.agents_panel uses a module listed above it, which is the healthy direction.
muxy_app.model.agents_panel uses gpui.app.context, so a change to gpui.app.context can break muxy_app.model.agents_panel, while a change to muxy_app.model.agents_panel can't break gpui.app.context.
Position
Below the diagonal: muxy_app.model.agents_panel uses a module listed above it, which is the healthy direction.
muxy_app.model.agents_panel uses gpui.app.entity_map, so a change to gpui.app.entity_map can break muxy_app.model.agents_panel, while a change to muxy_app.model.agents_panel can't break gpui.app.entity_map.
Position
Below the diagonal: muxy_app.model.agents_panel uses a module listed above it, which is the healthy direction.
muxy_app.views.browser uses gpui.subscription, so a change to gpui.subscription can break muxy_app.views.browser, while a change to muxy_app.views.browser can't break gpui.subscription.
Position
Below the diagonal: muxy_app.views.browser uses a module listed above it, which is the healthy direction.
muxy_app.views.browser uses muxy_app_core.localization.plist, so a change to muxy_app_core.localization.plist can break muxy_app.views.browser, while a change to muxy_app.views.browser can't break muxy_app_core.localization.plist.
Position
Below the diagonal: muxy_app.views.browser uses a module listed above it, which is the healthy direction.
muxy_app.views.browser uses gpui.element, so a change to gpui.element can break muxy_app.views.browser, while a change to muxy_app.views.browser can't break gpui.element.
Position
Below the diagonal: muxy_app.views.browser uses a module listed above it, which is the healthy direction.
muxy_app.views.browser uses gpui.executor, so a change to gpui.executor can break muxy_app.views.browser, while a change to muxy_app.views.browser can't break gpui.executor.
Position
Below the diagonal: muxy_app.views.browser uses a module listed above it, which is the healthy direction.
muxy_app.views.browser uses gpui.platform, so a change to gpui.platform can break muxy_app.views.browser, while a change to muxy_app.views.browser can't break gpui.platform.
Position
Below the diagonal: muxy_app.views.browser uses a module listed above it, which is the healthy direction.
muxy_app.views.browser uses gpui.geometry, so a change to gpui.geometry can break muxy_app.views.browser, while a change to muxy_app.views.browser can't break gpui.geometry.
Position
Below the diagonal: muxy_app.views.browser uses a module listed above it, which is the healthy direction.
muxy_app.views.browser uses gpui.color, so a change to gpui.color can break muxy_app.views.browser, while a change to muxy_app.views.browser can't break gpui.color.
Position
Below the diagonal: muxy_app.views.browser uses a module listed above it, which is the healthy direction.
muxy_app.views.browser uses gpui.window, so a change to gpui.window can break muxy_app.views.browser, while a change to muxy_app.views.browser can't break gpui.window.
Position
Below the diagonal: muxy_app.views.browser uses a module listed above it, which is the healthy direction.
muxy_app.views.browser uses muxy_ui.theme.colors, so a change to muxy_ui.theme.colors can break muxy_app.views.browser, while a change to muxy_app.views.browser can't break muxy_ui.theme.colors.
Position
Below the diagonal: muxy_app.views.browser uses a module listed above it, which is the healthy direction.
muxy_app.views.browser uses gpui.app.context, so a change to gpui.app.context can break muxy_app.views.browser, while a change to muxy_app.views.browser can't break gpui.app.context.
Position
Below the diagonal: muxy_app.views.browser uses a module listed above it, which is the healthy direction.
muxy_app.views.browser uses muxy_ui.theme.metrics, so a change to muxy_ui.theme.metrics can break muxy_app.views.browser, while a change to muxy_app.views.browser can't break muxy_ui.theme.metrics.
Position
Below the diagonal: muxy_app.views.browser uses a module listed above it, which is the healthy direction.
muxy_app.views.browser uses gpui.app.entity_map, so a change to gpui.app.entity_map can break muxy_app.views.browser, while a change to muxy_app.views.browser can't break gpui.app.entity_map.
Position
Below the diagonal: muxy_app.views.browser uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in muxy_app.views.browser uses a type in gpui.app.
The types involved
muxy_app.views.browser.BrowserView → gpui.app.App
Direction
muxy_app.views.browser uses gpui.app, so a change to gpui.app can break muxy_app.views.browser, while a change to muxy_app.views.browser can't break gpui.app.
Position
Below the diagonal: muxy_app.views.browser uses a module listed above it, which is the healthy direction.
muxy_app.views.move_drag uses gpui.element, so a change to gpui.element can break muxy_app.views.move_drag, while a change to muxy_app.views.move_drag can't break gpui.element.
Position
Below the diagonal: muxy_app.views.move_drag uses a module listed above it, which is the healthy direction.
muxy_app.views.move_drag uses gpui.shared_string, so a change to gpui.shared_string can break muxy_app.views.move_drag, while a change to muxy_app.views.move_drag can't break gpui.shared_string.
Position
Below the diagonal: muxy_app.views.move_drag uses a module listed above it, which is the healthy direction.
muxy_app.views.move_drag uses muxy_app.extensions.pictures, so a change to muxy_app.extensions.pictures can break muxy_app.views.move_drag, while a change to muxy_app.views.move_drag can't break muxy_app.extensions.pictures.
Position
Below the diagonal: muxy_app.views.move_drag uses a module listed above it, which is the healthy direction.
muxy_app.views.move_drag uses muxy_protocol.project, so a change to muxy_protocol.project can break muxy_app.views.move_drag, while a change to muxy_app.views.move_drag can't break muxy_protocol.project.
Position
Below the diagonal: muxy_app.views.move_drag uses a module listed above it, which is the healthy direction.
muxy_app.views.move_drag uses muxy_app_core.ids, so a change to muxy_app_core.ids can break muxy_app.views.move_drag, while a change to muxy_app.views.move_drag can't break muxy_app_core.ids.
Position
Below the diagonal: muxy_app.views.move_drag uses a module listed above it, which is the healthy direction.
muxy_app.views.move_drag uses gpui.geometry, so a change to gpui.geometry can break muxy_app.views.move_drag, while a change to muxy_app.views.move_drag can't break gpui.geometry.
Position
Below the diagonal: muxy_app.views.move_drag uses a module listed above it, which is the healthy direction.
muxy_app.views.move_drag uses muxy_app.boot, so a change to muxy_app.boot can break muxy_app.views.move_drag, while a change to muxy_app.views.move_drag can't break muxy_app.boot.
Position
Below the diagonal: muxy_app.views.move_drag uses a module listed above it, which is the healthy direction.
muxy_app.views.move_drag uses gpui.color, so a change to gpui.color can break muxy_app.views.move_drag, while a change to muxy_app.views.move_drag can't break gpui.color.
Position
Below the diagonal: muxy_app.views.move_drag uses a module listed above it, which is the healthy direction.
muxy_app.views.move_drag uses gpui.window, so a change to gpui.window can break muxy_app.views.move_drag, while a change to muxy_app.views.move_drag can't break gpui.window.
Position
Below the diagonal: muxy_app.views.move_drag uses a module listed above it, which is the healthy direction.
muxy_app.views.move_drag uses gpui.app.context, so a change to gpui.app.context can break muxy_app.views.move_drag, while a change to muxy_app.views.move_drag can't break gpui.app.context.
Position
Below the diagonal: muxy_app.views.move_drag uses a module listed above it, which is the healthy direction.
muxy_app.views.move_drag uses muxy_app.model.agents_panel, so a change to muxy_app.model.agents_panel can break muxy_app.views.move_drag, while a change to muxy_app.views.move_drag can't break muxy_app.model.agents_panel.
Position
Below the diagonal: muxy_app.views.move_drag uses a module listed above it, which is the healthy direction.
34→40 muxy_app.views.move_drag uses muxy_app.modelpart of a loop✕
Connections
1 pair of types, where a type in muxy_app.views.move_drag uses a type in muxy_app.model.
muxy_app.views.move_drag uses muxy_app.model, so a change to muxy_app.model can break muxy_app.views.move_drag, while a change to muxy_app.views.move_drag can't break muxy_app.model.
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.
muxy_app.views.settings.extensions uses gpui.subscription, so a change to gpui.subscription can break muxy_app.views.settings.extensions, while a change to muxy_app.views.settings.extensions can't break gpui.subscription.
Position
Below the diagonal: muxy_app.views.settings.extensions uses a module listed above it, which is the healthy direction.
muxy_app.views.settings.extensions uses muxy_app_core.localization.plist, so a change to muxy_app_core.localization.plist can break muxy_app.views.settings.extensions, while a change to muxy_app.views.settings.extensions can't break muxy_app_core.localization.plist.
Position
Below the diagonal: muxy_app.views.settings.extensions uses a module listed above it, which is the healthy direction.
muxy_app.views.settings.extensions uses gpui.element, so a change to gpui.element can break muxy_app.views.settings.extensions, while a change to muxy_app.views.settings.extensions can't break gpui.element.
Position
Below the diagonal: muxy_app.views.settings.extensions uses a module listed above it, which is the healthy direction.
muxy_app.views.settings.extensions uses gpui.shared_string, so a change to gpui.shared_string can break muxy_app.views.settings.extensions, while a change to muxy_app.views.settings.extensions can't break gpui.shared_string.
Position
Below the diagonal: muxy_app.views.settings.extensions uses a module listed above it, which is the healthy direction.
muxy_app.views.settings.extensions uses muxy_app.extensions.pictures, so a change to muxy_app.extensions.pictures can break muxy_app.views.settings.extensions, while a change to muxy_app.views.settings.extensions can't break muxy_app.extensions.pictures.
Position
Below the diagonal: muxy_app.views.settings.extensions uses a module listed above it, which is the healthy direction.
muxy_app.views.settings.extensions uses gpui.elements.div, so a change to gpui.elements.div can break muxy_app.views.settings.extensions, while a change to muxy_app.views.settings.extensions can't break gpui.elements.div.
Position
Below the diagonal: muxy_app.views.settings.extensions uses a module listed above it, which is the healthy direction.
muxy_app.views.settings.extensions uses gpui.geometry, so a change to gpui.geometry can break muxy_app.views.settings.extensions, while a change to muxy_app.views.settings.extensions can't break gpui.geometry.
Position
Below the diagonal: muxy_app.views.settings.extensions uses a module listed above it, which is the healthy direction.
muxy_app.views.settings.extensions uses gpui.window, so a change to gpui.window can break muxy_app.views.settings.extensions, while a change to muxy_app.views.settings.extensions can't break gpui.window.
Position
Below the diagonal: muxy_app.views.settings.extensions uses a module listed above it, which is the healthy direction.
muxy_app.views.settings.extensions uses muxy_ui.theme.colors, so a change to muxy_ui.theme.colors can break muxy_app.views.settings.extensions, while a change to muxy_app.views.settings.extensions can't break muxy_ui.theme.colors.
Position
Below the diagonal: muxy_app.views.settings.extensions uses a module listed above it, which is the healthy direction.
muxy_app.views.settings.extensions uses gpui.app.context, so a change to gpui.app.context can break muxy_app.views.settings.extensions, while a change to muxy_app.views.settings.extensions can't break gpui.app.context.
Position
Below the diagonal: muxy_app.views.settings.extensions uses a module listed above it, which is the healthy direction.
muxy_app.views.settings.extensions uses muxy_ui.theme.metrics, so a change to muxy_ui.theme.metrics can break muxy_app.views.settings.extensions, while a change to muxy_app.views.settings.extensions can't break muxy_ui.theme.metrics.
Position
Below the diagonal: muxy_app.views.settings.extensions uses a module listed above it, which is the healthy direction.
muxy_app.views.settings.extensions uses gpui.app.entity_map, so a change to gpui.app.entity_map can break muxy_app.views.settings.extensions, while a change to muxy_app.views.settings.extensions can't break gpui.app.entity_map.
Position
Below the diagonal: muxy_app.views.settings.extensions uses a module listed above it, which is the healthy direction.
muxy_app.views.settings.extensions uses gpui.app, so a change to gpui.app can break muxy_app.views.settings.extensions, while a change to muxy_app.views.settings.extensions can't break gpui.app.
Position
Below the diagonal: muxy_app.views.settings.extensions uses a module listed above it, which is the healthy direction.
35→40 muxy_app.views.settings.extensions uses muxy_app.modelpart of a loop✕
Connections
1 pair of types, where a type in muxy_app.views.settings.extensions uses a type in muxy_app.model.
muxy_app.views.settings.extensions uses muxy_app.model, so a change to muxy_app.model can break muxy_app.views.settings.extensions, while a change to muxy_app.views.settings.extensions can't break muxy_app.model.
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.
muxy_app.views.overlays uses gpui.element, so a change to gpui.element can break muxy_app.views.overlays, while a change to muxy_app.views.overlays can't break gpui.element.
Position
Below the diagonal: muxy_app.views.overlays uses a module listed above it, which is the healthy direction.
muxy_app.views.overlays uses gpui.window, so a change to gpui.window can break muxy_app.views.overlays, while a change to muxy_app.views.overlays can't break gpui.window.
Position
Below the diagonal: muxy_app.views.overlays uses a module listed above it, which is the healthy direction.
muxy_app.views.overlays uses gpui.app.context, so a change to gpui.app.context can break muxy_app.views.overlays, while a change to muxy_app.views.overlays can't break gpui.app.context.
Position
Below the diagonal: muxy_app.views.overlays uses a module listed above it, which is the healthy direction.
muxy_app.views.overlays uses gpui.app.entity_map, so a change to gpui.app.entity_map can break muxy_app.views.overlays, while a change to muxy_app.views.overlays can't break gpui.app.entity_map.
Position
Below the diagonal: muxy_app.views.overlays uses a module listed above it, which is the healthy direction.
muxy_app.views.overlays uses gpui.app, so a change to gpui.app can break muxy_app.views.overlays, while a change to muxy_app.views.overlays can't break gpui.app.
Position
Below the diagonal: muxy_app.views.overlays uses a module listed above it, which is the healthy direction.
muxy_app.views.overlays uses muxy_app.model.agents_panel, so a change to muxy_app.model.agents_panel can break muxy_app.views.overlays, while a change to muxy_app.views.overlays can't break muxy_app.model.agents_panel.
Position
Below the diagonal: muxy_app.views.overlays uses a module listed above it, which is the healthy direction.
muxy_app.views.overlays uses muxy_app.views.move_drag, so a change to muxy_app.views.move_drag can break muxy_app.views.overlays, while a change to muxy_app.views.overlays can't break muxy_app.views.move_drag.
Position
Below the diagonal: muxy_app.views.overlays uses a module listed above it, which is the healthy direction.
36→40 muxy_app.views.overlays uses muxy_app.modelpart of a loop✕
Connections
4 pairs of types, where a type in muxy_app.views.overlays uses a type in muxy_app.model.
muxy_app.views.overlays uses muxy_app.model, so a change to muxy_app.model can break muxy_app.views.overlays, while a change to muxy_app.views.overlays can't break muxy_app.model.
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.
muxy_app.views.tab_activity uses gpui.element, so a change to gpui.element can break muxy_app.views.tab_activity, while a change to muxy_app.views.tab_activity can't break gpui.element.
Position
Below the diagonal: muxy_app.views.tab_activity uses a module listed above it, which is the healthy direction.
muxy_app.views.tab_activity uses gpui.scene, so a change to gpui.scene can break muxy_app.views.tab_activity, while a change to muxy_app.views.tab_activity can't break gpui.scene.
Position
Below the diagonal: muxy_app.views.tab_activity uses a module listed above it, which is the healthy direction.
muxy_app.views.tab_activity uses muxy_protocol.session, so a change to muxy_protocol.session can break muxy_app.views.tab_activity, while a change to muxy_app.views.tab_activity can't break muxy_protocol.session.
Position
Below the diagonal: muxy_app.views.tab_activity uses a module listed above it, which is the healthy direction.
muxy_app.views.tab_activity uses muxy_protocol.project, so a change to muxy_protocol.project can break muxy_app.views.tab_activity, while a change to muxy_app.views.tab_activity can't break muxy_protocol.project.
Position
Below the diagonal: muxy_app.views.tab_activity uses a module listed above it, which is the healthy direction.
muxy_app.views.tab_activity uses muxy_app_core.ids, so a change to muxy_app_core.ids can break muxy_app.views.tab_activity, while a change to muxy_app.views.tab_activity can't break muxy_app_core.ids.
Position
Below the diagonal: muxy_app.views.tab_activity uses a module listed above it, which is the healthy direction.
muxy_app.views.tab_activity uses muxy_protocol.activity, so a change to muxy_protocol.activity can break muxy_app.views.tab_activity, while a change to muxy_app.views.tab_activity can't break muxy_protocol.activity.
Position
Below the diagonal: muxy_app.views.tab_activity uses a module listed above it, which is the healthy direction.
muxy_app.views.tab_activity uses gpui.geometry, so a change to gpui.geometry can break muxy_app.views.tab_activity, while a change to muxy_app.views.tab_activity can't break gpui.geometry.
Position
Below the diagonal: muxy_app.views.tab_activity uses a module listed above it, which is the healthy direction.
muxy_app.views.tab_activity uses gpui.color, so a change to gpui.color can break muxy_app.views.tab_activity, while a change to muxy_app.views.tab_activity can't break gpui.color.
Position
Below the diagonal: muxy_app.views.tab_activity uses a module listed above it, which is the healthy direction.
muxy_app.views.tab_activity uses gpui.window, so a change to gpui.window can break muxy_app.views.tab_activity, while a change to muxy_app.views.tab_activity can't break gpui.window.
Position
Below the diagonal: muxy_app.views.tab_activity uses a module listed above it, which is the healthy direction.
muxy_app.views.tab_activity uses gpui.app.entity_map, so a change to gpui.app.entity_map can break muxy_app.views.tab_activity, while a change to muxy_app.views.tab_activity can't break gpui.app.entity_map.
Position
Below the diagonal: muxy_app.views.tab_activity uses a module listed above it, which is the healthy direction.
muxy_app.views.tab_activity uses muxy_app.model.agents_panel, so a change to muxy_app.model.agents_panel can break muxy_app.views.tab_activity, while a change to muxy_app.views.tab_activity can't break muxy_app.model.agents_panel.
Position
Below the diagonal: muxy_app.views.tab_activity uses a module listed above it, which is the healthy direction.
muxy_app.views.tab_activity uses muxy_app.views.settings.extensions, so a change to muxy_app.views.settings.extensions can break muxy_app.views.tab_activity, while a change to muxy_app.views.tab_activity can't break muxy_app.views.settings.extensions.
Position
Below the diagonal: muxy_app.views.tab_activity uses a module listed above it, which is the healthy direction.
37→40 muxy_app.views.tab_activity uses muxy_app.modelpart of a loop✕
Connections
1 pair of types, where a type in muxy_app.views.tab_activity uses a type in muxy_app.model.
muxy_app.views.tab_activity uses muxy_app.model, so a change to muxy_app.model can break muxy_app.views.tab_activity, while a change to muxy_app.views.tab_activity can't break muxy_app.model.
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.
muxy_app.views.settings uses gpui.subscription, so a change to gpui.subscription can break muxy_app.views.settings, while a change to muxy_app.views.settings can't break gpui.subscription.
Position
Below the diagonal: muxy_app.views.settings uses a module listed above it, which is the healthy direction.
muxy_app.views.settings uses gpui.element, so a change to gpui.element can break muxy_app.views.settings, while a change to muxy_app.views.settings can't break gpui.element.
Position
Below the diagonal: muxy_app.views.settings uses a module listed above it, which is the healthy direction.
muxy_app.views.settings uses gpui.platform.keystroke, so a change to gpui.platform.keystroke can break muxy_app.views.settings, while a change to muxy_app.views.settings can't break gpui.platform.keystroke.
Position
Below the diagonal: muxy_app.views.settings uses a module listed above it, which is the healthy direction.
muxy_app.views.settings uses muxy_protocol.control, so a change to muxy_protocol.control can break muxy_app.views.settings, while a change to muxy_app.views.settings can't break muxy_protocol.control.
Position
Below the diagonal: muxy_app.views.settings uses a module listed above it, which is the healthy direction.
muxy_app.views.settings uses gpui.shared_string, so a change to gpui.shared_string can break muxy_app.views.settings, while a change to muxy_app.views.settings can't break gpui.shared_string.
Position
Below the diagonal: muxy_app.views.settings uses a module listed above it, which is the healthy direction.
muxy_app.views.settings uses muxy_app.extensions.pictures, so a change to muxy_app.extensions.pictures can break muxy_app.views.settings, while a change to muxy_app.views.settings can't break muxy_app.extensions.pictures.
Position
Below the diagonal: muxy_app.views.settings uses a module listed above it, which is the healthy direction.
muxy_app.views.settings uses gpui.elements.div, so a change to gpui.elements.div can break muxy_app.views.settings, while a change to muxy_app.views.settings can't break gpui.elements.div.
Position
Below the diagonal: muxy_app.views.settings uses a module listed above it, which is the healthy direction.
muxy_app.views.settings uses gpui.geometry, so a change to gpui.geometry can break muxy_app.views.settings, while a change to muxy_app.views.settings can't break gpui.geometry.
Position
Below the diagonal: muxy_app.views.settings uses a module listed above it, which is the healthy direction.
muxy_app.views.settings uses gpui.window, so a change to gpui.window can break muxy_app.views.settings, while a change to muxy_app.views.settings can't break gpui.window.
Position
Below the diagonal: muxy_app.views.settings uses a module listed above it, which is the healthy direction.
muxy_app.views.settings uses muxy_ui.theme.colors, so a change to muxy_ui.theme.colors can break muxy_app.views.settings, while a change to muxy_app.views.settings can't break muxy_ui.theme.colors.
Position
Below the diagonal: muxy_app.views.settings uses a module listed above it, which is the healthy direction.
muxy_app.views.settings uses gpui.app.context, so a change to gpui.app.context can break muxy_app.views.settings, while a change to muxy_app.views.settings can't break gpui.app.context.
Position
Below the diagonal: muxy_app.views.settings uses a module listed above it, which is the healthy direction.
muxy_app.views.settings uses muxy_ui.theme.metrics, so a change to muxy_ui.theme.metrics can break muxy_app.views.settings, while a change to muxy_app.views.settings can't break muxy_ui.theme.metrics.
Position
Below the diagonal: muxy_app.views.settings uses a module listed above it, which is the healthy direction.
muxy_app.views.settings uses gpui.app.entity_map, so a change to gpui.app.entity_map can break muxy_app.views.settings, while a change to muxy_app.views.settings can't break gpui.app.entity_map.
Position
Below the diagonal: muxy_app.views.settings uses a module listed above it, which is the healthy direction.
muxy_app.views.settings uses gpui.app, so a change to gpui.app can break muxy_app.views.settings, while a change to muxy_app.views.settings can't break gpui.app.
Position
Below the diagonal: muxy_app.views.settings uses a module listed above it, which is the healthy direction.
muxy_app.views.settings uses muxy_app.model.agents_panel, so a change to muxy_app.model.agents_panel can break muxy_app.views.settings, while a change to muxy_app.views.settings can't break muxy_app.model.agents_panel.
Position
Below the diagonal: muxy_app.views.settings uses a module listed above it, which is the healthy direction.
muxy_app.views.settings uses muxy_app.views.tab_activity, so a change to muxy_app.views.tab_activity can break muxy_app.views.settings, while a change to muxy_app.views.settings can't break muxy_app.views.tab_activity.
Position
Below the diagonal: muxy_app.views.settings uses a module listed above it, which is the healthy direction.
38→40 muxy_app.views.settings uses muxy_app.modelpart of a loop✕
Connections
1 pair of types, where a type in muxy_app.views.settings uses a type in muxy_app.model.
muxy_app.views.settings uses muxy_app.model, so a change to muxy_app.model can break muxy_app.views.settings, while a change to muxy_app.views.settings can't break muxy_app.model.
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.
muxy_app.views.terminal.pane uses gpui.subscription, so a change to gpui.subscription can break muxy_app.views.terminal.pane, while a change to muxy_app.views.terminal.pane can't break gpui.subscription.
Position
Below the diagonal: muxy_app.views.terminal.pane uses a module listed above it, which is the healthy direction.
muxy_app.views.terminal.pane uses muxy_protocol.ids, so a change to muxy_protocol.ids can break muxy_app.views.terminal.pane, while a change to muxy_app.views.terminal.pane can't break muxy_protocol.ids.
Position
Below the diagonal: muxy_app.views.terminal.pane uses a module listed above it, which is the healthy direction.
muxy_app.views.terminal.pane uses muxy_protocol.path, so a change to muxy_protocol.path can break muxy_app.views.terminal.pane, while a change to muxy_app.views.terminal.pane can't break muxy_protocol.path.
Position
Below the diagonal: muxy_app.views.terminal.pane uses a module listed above it, which is the healthy direction.
muxy_app.views.terminal.pane uses muxy_protocol.screen, so a change to muxy_protocol.screen can break muxy_app.views.terminal.pane, while a change to muxy_app.views.terminal.pane can't break muxy_protocol.screen.
Position
Below the diagonal: muxy_app.views.terminal.pane uses a module listed above it, which is the healthy direction.
muxy_app.views.terminal.pane uses gpui.element, so a change to gpui.element can break muxy_app.views.terminal.pane, while a change to muxy_app.views.terminal.pane can't break gpui.element.
Position
Below the diagonal: muxy_app.views.terminal.pane uses a module listed above it, which is the healthy direction.
muxy_app.views.terminal.pane uses gpui.executor, so a change to gpui.executor can break muxy_app.views.terminal.pane, while a change to muxy_app.views.terminal.pane can't break gpui.executor.
Position
Below the diagonal: muxy_app.views.terminal.pane uses a module listed above it, which is the healthy direction.
muxy_app.views.terminal.pane uses gpui.platform.keystroke, so a change to gpui.platform.keystroke can break muxy_app.views.terminal.pane, while a change to muxy_app.views.terminal.pane can't break gpui.platform.keystroke.
Position
Below the diagonal: muxy_app.views.terminal.pane uses a module listed above it, which is the healthy direction.
muxy_app.views.terminal.pane uses gpui.scene, so a change to gpui.scene can break muxy_app.views.terminal.pane, while a change to muxy_app.views.terminal.pane can't break gpui.scene.
Position
Below the diagonal: muxy_app.views.terminal.pane uses a module listed above it, which is the healthy direction.
muxy_app.views.terminal.pane uses muxy_protocol.session, so a change to muxy_protocol.session can break muxy_app.views.terminal.pane, while a change to muxy_app.views.terminal.pane can't break muxy_protocol.session.
Position
Below the diagonal: muxy_app.views.terminal.pane uses a module listed above it, which is the healthy direction.
muxy_app.views.terminal.pane uses gpui.interactive, so a change to gpui.interactive can break muxy_app.views.terminal.pane, while a change to muxy_app.views.terminal.pane can't break gpui.interactive.
Position
Below the diagonal: muxy_app.views.terminal.pane uses a module listed above it, which is the healthy direction.
muxy_app.views.terminal.pane uses muxy_app.extensions.pictures, so a change to muxy_app.extensions.pictures can break muxy_app.views.terminal.pane, while a change to muxy_app.views.terminal.pane can't break muxy_app.extensions.pictures.
Position
Below the diagonal: muxy_app.views.terminal.pane uses a module listed above it, which is the healthy direction.
muxy_app.views.terminal.pane uses gpui.platform, so a change to gpui.platform can break muxy_app.views.terminal.pane, while a change to muxy_app.views.terminal.pane can't break gpui.platform.
Position
Below the diagonal: muxy_app.views.terminal.pane uses a module listed above it, which is the healthy direction.
muxy_app.views.terminal.pane uses muxy_app_core.ids, so a change to muxy_app_core.ids can break muxy_app.views.terminal.pane, while a change to muxy_app.views.terminal.pane can't break muxy_app_core.ids.
Position
Below the diagonal: muxy_app.views.terminal.pane uses a module listed above it, which is the healthy direction.
muxy_app.views.terminal.pane uses gpui.geometry, so a change to gpui.geometry can break muxy_app.views.terminal.pane, while a change to muxy_app.views.terminal.pane can't break gpui.geometry.
Position
Below the diagonal: muxy_app.views.terminal.pane uses a module listed above it, which is the healthy direction.
muxy_app.views.terminal.pane uses gpui.window, so a change to gpui.window can break muxy_app.views.terminal.pane, while a change to muxy_app.views.terminal.pane can't break gpui.window.
Position
Below the diagonal: muxy_app.views.terminal.pane uses a module listed above it, which is the healthy direction.
muxy_app.views.terminal.pane uses muxy_ui.theme.colors, so a change to muxy_ui.theme.colors can break muxy_app.views.terminal.pane, while a change to muxy_app.views.terminal.pane can't break muxy_ui.theme.colors.
Position
Below the diagonal: muxy_app.views.terminal.pane uses a module listed above it, which is the healthy direction.
muxy_app.views.terminal.pane uses gpui.app.context, so a change to gpui.app.context can break muxy_app.views.terminal.pane, while a change to muxy_app.views.terminal.pane can't break gpui.app.context.
Position
Below the diagonal: muxy_app.views.terminal.pane uses a module listed above it, which is the healthy direction.
muxy_app.views.terminal.pane uses muxy_ui.theme.metrics, so a change to muxy_ui.theme.metrics can break muxy_app.views.terminal.pane, while a change to muxy_app.views.terminal.pane can't break muxy_ui.theme.metrics.
Position
Below the diagonal: muxy_app.views.terminal.pane uses a module listed above it, which is the healthy direction.
muxy_app.views.terminal.pane uses muxy_app.views.tab_activity, so a change to muxy_app.views.tab_activity can break muxy_app.views.terminal.pane, while a change to muxy_app.views.terminal.pane can't break muxy_app.views.tab_activity.
Position
Below the diagonal: muxy_app.views.terminal.pane uses a module listed above it, which is the healthy direction.
muxy_app.model uses gpui.subscription, so a change to gpui.subscription can break muxy_app.model, while a change to muxy_app.model can't break gpui.subscription.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses muxy_app_core.localization.plist, so a change to muxy_app_core.localization.plist can break muxy_app.model, while a change to muxy_app.model can't break muxy_app_core.localization.plist.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses muxy_protocol.ids, so a change to muxy_protocol.ids can break muxy_app.model, while a change to muxy_app.model can't break muxy_protocol.ids.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses muxy_protocol.path, so a change to muxy_protocol.path can break muxy_app.model, while a change to muxy_app.model can't break muxy_protocol.path.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses gpui.platform.keystroke, so a change to gpui.platform.keystroke can break muxy_app.model, while a change to muxy_app.model can't break gpui.platform.keystroke.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses muxy_protocol.control, so a change to muxy_protocol.control can break muxy_app.model, while a change to muxy_app.model can't break muxy_protocol.control.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses muxy_protocol.session, so a change to muxy_protocol.session can break muxy_app.model, while a change to muxy_app.model can't break muxy_protocol.session.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses gpui.interactive, so a change to gpui.interactive can break muxy_app.model, while a change to muxy_app.model can't break gpui.interactive.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses gpui.shared_string, so a change to gpui.shared_string can break muxy_app.model, while a change to muxy_app.model can't break gpui.shared_string.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses muxy_app.extensions.pictures, so a change to muxy_app.extensions.pictures can break muxy_app.model, while a change to muxy_app.model can't break muxy_app.extensions.pictures.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses muxy_protocol.project, so a change to muxy_protocol.project can break muxy_app.model, while a change to muxy_app.model can't break muxy_protocol.project.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses muxy_app_core.ids, so a change to muxy_app_core.ids can break muxy_app.model, while a change to muxy_app.model can't break muxy_app_core.ids.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses muxy_protocol.activity, so a change to muxy_protocol.activity can break muxy_app.model, while a change to muxy_app.model can't break muxy_protocol.activity.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses muxy_ui.theme.colors, so a change to muxy_ui.theme.colors can break muxy_app.model, while a change to muxy_app.model can't break muxy_ui.theme.colors.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses gpui.app.context, so a change to gpui.app.context can break muxy_app.model, while a change to muxy_app.model can't break gpui.app.context.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses muxy_ui.theme.metrics, so a change to muxy_ui.theme.metrics can break muxy_app.model, while a change to muxy_app.model can't break muxy_ui.theme.metrics.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses gpui.app.entity_map, so a change to gpui.app.entity_map can break muxy_app.model, while a change to muxy_app.model can't break gpui.app.entity_map.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses muxy_app.model.agents_panel, so a change to muxy_app.model.agents_panel can break muxy_app.model, while a change to muxy_app.model can't break muxy_app.model.agents_panel.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses muxy_app.views.browser, so a change to muxy_app.views.browser can break muxy_app.model, while a change to muxy_app.model can't break muxy_app.views.browser.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses muxy_app.views.move_drag, so a change to muxy_app.views.move_drag can break muxy_app.model, while a change to muxy_app.model can't break muxy_app.views.move_drag.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses muxy_app.views.settings.extensions, so a change to muxy_app.views.settings.extensions can break muxy_app.model, while a change to muxy_app.model can't break muxy_app.views.settings.extensions.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses muxy_app.views.overlays, so a change to muxy_app.views.overlays can break muxy_app.model, while a change to muxy_app.model can't break muxy_app.views.overlays.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses muxy_app.views.tab_activity, so a change to muxy_app.views.tab_activity can break muxy_app.model, while a change to muxy_app.model can't break muxy_app.views.tab_activity.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses muxy_app.views.settings, so a change to muxy_app.views.settings can break muxy_app.model, while a change to muxy_app.model can't break muxy_app.views.settings.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses muxy_app.views.terminal.pane, so a change to muxy_app.views.terminal.pane can break muxy_app.model, while a change to muxy_app.model can't break muxy_app.views.terminal.pane.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 38% · Weak · gated by R1, R10, R3 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
59
High / Critical
A03:2025 — Software Supply Chain Failures
28
Medium
A07:2025 — Authentication Failures
10
High / Critical
Roadmap
Top priorities: Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up; Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package; Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
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 — 69
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 — 778
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 — 53
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 12
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 59 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 59 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, 873 of 900 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 Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 22 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 152 test source file(s) (.rs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs, .cjs) and this repository declares a Cargo test suite (repository root, 373 test files), but it was not re-run: no test result was produced. 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 (62 contributor(s) across 1358 commit(s) sampled, automation and bot accounts excluded). One of them holds 86% of the history; the other 61 hold 0.2% 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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
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.
D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
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.
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 Rust 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 Rust 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.
P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
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.
X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
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 Rust 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: 2 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
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 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
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.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
112 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was (anonymous) at 177. A further 34 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 Icon::path at 88 — they are counted neither in the figure above nor in this dimension's score. 19 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: crates/muxy-ui/src/icon/mod.rs (Icon::path at 88), crates/muxy-terminal/src/input.rs (muxy_terminal::input::key_code at 80), crates/muxy-core/src/quick_terminal/keys.rs (muxy_core::quick_terminal::keys::legacy_key_for_virtual_key_code at 57), crates/muxy-app-core/src/extensions/api.rs (muxy_app_core::extensions::api::git_action at 40), crates/muxy-app-core/src/extensions/permissions.rs (muxy_app_core::extensions::permissions::required_permission at 40), and 14 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.
+ 40 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 Cyclomatic Complexity — start with (anonymous) (cyclomatic 177). — Refactoring it lifts Cyclomatic Complexity from 5.4 to about 5.8/10.
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.
+ 55 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 (anonymous) (cognitive 217). — Refactoring it lifts Cognitive Complexity from 5.2 to about 5.8/10.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.0 / 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.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 74 FileTooLong finding(s) in God Classes — start with mod.rs (5), remote_servers.rs (2), state.rs (2). — One of this dimension's main actionable groups (74 warning-level).
Resolve the 21 MethodTooLong finding(s) in God Classes — start with picker.rs (2), git.rs (2), preferences.rs. — One of this dimension's main actionable groups (21 warning-level).
Resolve the 19 FunctionTooLong finding(s) in God Classes — start with element.rs (3), boot.rs (2), args.rs. — One of this dimension's main actionable groups (19 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.
99 duplicated block group(s) detected. 2.5 % of the production lines (5,947 of 237,231) are in a reported copy. A further 125 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
+ 69 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 13 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with tab.rs, panel.rs, shell.rs. — One of this dimension's main actionable groups (13 warning-level).
Resolve the 12 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with mod.rs (3), automation.rs (2), model.rs. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 11 Edited copy of a member (14 corresponding lines) finding(s) in Code Duplication — start with files.rs (2), text_input.rs, worker.rs. — One of this dimension's main actionable groups (11 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.4 / 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.
10 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence.
Off the main sequence: muxy-core · ×2
What to do
Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 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 4 Low cohesion finding(s) in Cohesion (LCOM4) — start with storage.rs, commands.rs, config.rs. — One of this dimension's main actionable groups (4 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 Quality10.0 / 10Exemplary✓ 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.
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 22 tests. Measured on the JavaScript/TypeScript suite only — at least 152 test source file(s) (.rs) went unread, so its test quality is unmeasured and is not in these counts.
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.
14 outdated, 0 yanked direct Cargo dependencies. 56 of 59 direct crates were graded against crates.io (0 not published there, 3 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
Outdated: icu_locale_core · ×14
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 1019 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 4 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: crates/muxy-app/src/model.rs (134×54=7236); crates/muxy-app/src/model/preferences.rs (72×70=5040); crates/muxy-app/src/views/menu.rs (46×64=2944) Repeated repair below the complexity floor: crates/muxy-ui/src/native_scroll.rs (3 of 5 changes were fixes); crates/muxy-app/src/views/settings/extensions/configuration.rs (3 of 5 changes were fixes); crates/muxy-app-core/src/settings/ghostty/bindings.rs (3 of 5 changes were fixes)
Resolve the 62 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs (8), git.rs (3), args.rs (2). — One of this dimension's main actionable groups (62 warning-level).
Resolve the 4 Repeated repair finding(s) in Churn × Complexity Hotspots — start with native_scroll.rs, configuration.rs, bindings.rs. — One of this dimension's main actionable groups (4 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 237231 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 the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 46 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.
Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.
Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.
5 of 11 build units (Cargo) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
9 finding(s): 0 critical, 9 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 9 REDACTED finding(s) in Secrets (history) — start with REDACTED (9). — One of this dimension's main actionable groups (9 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
59 finding(s): 0 critical, 59 high, 0 medium, 0 low. 55 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 40 file(s) — `crates/muxy-app/src/cli_install.rs` (line 23, line 29), `crates/muxy-app/src/model.rs` (line 540, line 1942), `crates/muxy-app/src/model/banners.rs` (line 110, line 185), `crates/muxy-app/src/model/browsers/mod.rs` (line 274, line 350, line 538, …), `crates/muxy-app/src/model/composer.rs` (line 253, line 328, line 400, …), … (+35 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 55 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (55 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 16 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (16). — One of this dimension's main actionable groups (16 warning-level).
Resolve the 4 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
Resolve the 2 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 641 of the 764 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 2 Change coupling finding(s) in Change Coupling — start with keymap.rs (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with rust-toolchain.toml. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether 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 an aggregate references another aggregate by identity rather than embedding it by object reference.
Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.
Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.
Other · Domain Modelling — Whether domain identifiers are strongly typed (a newtype wrapper) 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.
Do you agree with this assessment?
DM4 · Rich vs anemic domain model10.0 / 10Exemplary✓ Tool-verified
Other · Domain Modelling — Whether domain entities own their behaviour (invariant-enforcing commands) rather than being data-only structs driven by a foreign service.
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.
Other · Domain Modelling — Whether a domain type's identity-bearing field stays immutable — a `pub` mutable field under a hand-rolled Hash/PartialEq breaks the value-identity invariant.
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 · Event Sourcing — Whether the recovery-replay fold is deterministic — state derived purely from each event's own fields, no clock/random/IO on the replay path.
Method: Roslyn syntax scan (event-sourcing gated): Apply/When folds checked for forbidden tokens (DateTime.Now, Guid.NewGuid, Random, IO), stripped of comments/strings. Deterministic, hard fact per fold.
Other · Event Sourcing — Whether domain events stay immutable (private fields, set once) rather than carrying mutable state.
Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.
`ClientEvent` conforms to a domain-event contract but carries a freely-mutable `pub` field. Events are immutable facts — model them with private fields (set once in the constructor) so a recorded event can never be rewritten. — crates/muxy-client/src/events.rs:21
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Do you agree with this assessment?
P1 · CI/CD gates8.5 / 10Strong✓ 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.
What to do
Run the test suite in CI via an explicit runner step (`cargo test` for the toolchain this pipeline already uses) and gate merges on it.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability4.6 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 1/5 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `crates/muxy-app`, `crates/muxy-cli`, `crates/muxy-mobile`, `crates/muxy-protocol`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Do you agree with this assessment?
P5 · DR & Backup4.0 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
R1 · Type Safety0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
0 typed · 5 plain JS — the untyped files are crates/muxy-app-core/src/browser/element_picker.js, crates/muxy-app/src/extensions/bridge.js, crates/muxy-app/src/extensions/script.js, crates/muxy-app/src/views/webview/bridge.js, crates/muxy-app/src/views/webview/bridge.test.cjs.
What to do
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Do you agree with this assessment?
R10 · Code Duplication3.7 / 10Weak✓ Tool-verified
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
crates/muxy-app/src/extensions/bridge.js:320 · crates/muxy-app/src/views/webview/bridge.js:140 — the two spans are one implementation copied and then locally edited — 393 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — crates/muxy-app/src/extensions/bridge.js:320
crates/muxy-app/src/extensions/script.js:6 · crates/muxy-app/src/views/webview/bridge.js:260 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — crates/muxy-app/src/extensions/script.js:6
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
restore has cyclomatic complexity 14 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — crates/muxy-app-core/src/browser/element_picker.js:5
open has cyclomatic complexity 14 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — crates/muxy-app/src/views/webview/bridge.js:166
(anonymous) has cyclomatic complexity 12 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — crates/muxy-app/src/extensions/bridge.js:1
execPayload has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — crates/muxy-app/src/extensions/bridge.js:13
__muxyTick has cyclomatic complexity 11 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — crates/muxy-app/src/extensions/script.js:36
Do you agree with this assessment?
R3 · Large Files0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
crates/muxy-app/src/extensions/bridge.js has 451 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — crates/muxy-app/src/extensions/bridge.js:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R7 · Dead Code10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · 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.
This function unwraps IPv4-MAPPED IPv6 (`to_ipv4_mapped`, line 100) and then rejects `10.0.0.0/8` on its IPv4 path — but the IPv6 decision at line 93 classifies the address as written, and IPv4 reaches IPv6 through three MORE embeddings this function never mentions: IPv4-compatible (`::a.b.c.d`), 6to4 (`2002::/16`) and NAT64 (`64:ff9b::/96`). So `::10.0.0.1`, `2002:0a00:0001::` and `64:ff9b::10.0.0.0` all name a host inside `10.0.0.0/8` — the range this same function declares non-public — and all reach the IPv6 decision un-unwrapped, taking the opposite verdict. Unwrap every embedding to its IPv4 form before classifying, or reject any IPv6 address carrying an embedded IPv4 outright. — crates/muxy-app/src/extensions/http.rs:93
What to do
Each finding names the IPv4 branch that rejects the host and the IPv6 branch that accepts the same host in another notation. Confirm from the two, then unwrap every IPv4-in-IPv6 embedding before classifying, or reject non-native IPv6 outright.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 27 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 73 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
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. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. 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
AX8 Test isolation — no test/production split to check
AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source 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 field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source 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 .rs 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.
D21 Naming Consistency — Naming consistency does not read html yet; not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .rs source were not judged.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. 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) — 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.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — Rust suite
DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM6 Domain ↔ infrastructure boundary — this Rust crate maps no type to a persistence framework (diesel/sea-orm/sqlx), so DM6's domain↔infrastructure fusion read has no population to be taken over
DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
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 — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Rust 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 `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, 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.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R4 Test Coverage — 1 test file(s) reach none of 4 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
S1 Web-Security Posture — No web surface: 727 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
X12 Unreachable branch — X12 reached only 0% of this repository's production lines — rust (237,231 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 0% of this repository's production lines — rust (237,231 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 — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X3 Exception handling — X3 reached only 0% of this repository's production lines — rust (237,231 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 — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
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
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Mutable domain event: ClientEvent crates/muxy-client/src/events.rs:21— `ClientEvent` conforms to a domain-event contract but carries a freely-mutable `pub` field. Events are immutable facts — model them with private fields (set once in the constructor) so a recorded event can never be rewritten.
FileTooLong: src/model.rs crates/muxy-app/src/model.rs— FileTooLong — 2424 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 1924 over it, 4.85× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/text_input.rs crates/muxy-ui/src/text_input.rs— FileTooLong — 1619 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 1119 over it, 3.24× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/picker.rs crates/muxy-ui/src/picker.rs— FileTooLong — 1527 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 64% of them inside a single declaration: Picker (5 blocks, 740-2020). The bar is 500 significant lines; this is 1027 over it, 3.05× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/shortcuts.rs crates/muxy-core/src/shortcuts.rs— FileTooLong — 1483 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 983 over it, 2.97× 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: terminal/pane.rs crates/muxy-app/src/views/terminal/pane.rs— FileTooLong — 1377 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 877 over it, 2.75× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: linux/page.rs crates/muxy-ui/src/webview/linux/page.rs— FileTooLong — 1311 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 48 free functions. The bar is 500 significant lines; this is 811 over it, 2.62× 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: views/remote_servers.rs crates/muxy-app/src/views/remote_servers.rs— FileTooLong — 1274 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 774 over it, 2.55× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: views/sidebar.rs crates/muxy-app/src/views/sidebar.rs— FileTooLong — 1273 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 35 free functions. The bar is 500 significant lines; this is 773 over it, 2.55× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: model/webviews.rs crates/muxy-app/src/model/webviews.rs— FileTooLong — 1166 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 90% of them inside a single declaration: AppModel (5 blocks, 112-1534). The bar is 500 significant lines; this is 666 over it, 2.33× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/boot.rs crates/muxy-app/src/boot.rs— FileTooLong — 1151 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 651 over it, 2.30× 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: model/preferences.rs crates/muxy-app/src/model/preferences.rs— FileTooLong — 1129 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 81% of them inside a single declaration: AppModel (163-1407). The bar is 500 significant lines; this is 629 over it, 2.26× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: settings/extensions.rs crates/muxy-app/src/views/settings/extensions.rs— FileTooLong — 1112 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 91% of them inside a single declaration: ExtensionsView (4 blocks, 119-1482). The bar is 500 significant lines; this is 612 over it, 2.22× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: views/project_picker.rs crates/muxy-app/src/views/project_picker.rs— FileTooLong — 1029 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 529 over it, 2.06× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/state.rs crates/muxy-app-core/src/state.rs— FileTooLong — 987 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 95% of them inside a single declaration: AppState (3 blocks, 22-1314). The bar is 500 significant lines; this is 487 over it, 1.97× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: webviews/panels.rs crates/muxy-app/src/model/webviews/panels.rs— FileTooLong — 979 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 83% of them inside a single declaration: AppModel (243-1320). The bar is 500 significant lines; this is 479 over it, 1.96× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: views/agents_panel.rs crates/muxy-app/src/views/agents_panel.rs— FileTooLong — 937 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 437 over it, 1.87× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/samples.rs crates/muxy-protocol/src/samples.rs— FileTooLong — 890 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 390 over it, 1.78× 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: workspace/commands.rs crates/muxy-app/src/views/workspace/commands.rs— FileTooLong — 871 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 371 over it, 1.74× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: views/tab_sidebar.rs crates/muxy-app/src/views/tab_sidebar.rs— FileTooLong — 825 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 325 over it, 1.65× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/ghostty.rs crates/muxy-terminal/src/ghostty.rs— FileTooLong — 822 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 81% of them inside a single declaration: Terminal (2 blocks, 96-966). The bar is 500 significant lines; this is 322 over it, 1.64× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: terminal/element.rs crates/muxy-app/src/views/terminal/element.rs— FileTooLong — 818 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 318 over it, 1.64× 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: model/composer.rs crates/muxy-app/src/model/composer.rs— FileTooLong — 802 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 78% of them inside a single declaration: AppModel (3 blocks, 70-1059). The bar is 500 significant lines; this is 302 over it, 1.60× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: browser/mod.rs crates/muxy-app/src/views/browser/mod.rs— FileTooLong — 799 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 77% of them inside a single declaration: BrowserView (4 blocks, 106-1027). The bar is 500 significant lines; this is 299 over it, 1.60× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: settings/catalog.rs crates/muxy-app/src/views/settings/catalog.rs— FileTooLong — 798 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 298 over it, 1.60× 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: extensions/mod.rs crates/muxy-app/src/model/extensions/mod.rs— FileTooLong — 779 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 81% of them inside a single declaration: AppModel (205-1075). The bar is 500 significant lines; this is 279 over it, 1.56× 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.
Hotspot: crates/muxy-app/src/model.rs crates/muxy-app/src/model.rs:2594— crates/muxy-app/src/model.rs changed 134 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 54 in AppModel::receive at line 2594. 11 of those changes were fix/bug commits, and the other 123 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-app/src/model.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/muxy-app/src/model/preferences.rs crates/muxy-app/src/model/preferences.rs:524— crates/muxy-app/src/model/preferences.rs changed 72 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 70 in AppModel::apply_preference at line 524. 2 of those changes were fix/bug commits, and the other 70 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-app/src/model/preferences.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/muxy-app/src/views/menu.rs crates/muxy-app/src/views/menu.rs:590— crates/muxy-app/src/views/menu.rs changed 46 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 64 in AppModel::perform_menu at line 590. 3 of those changes were fix/bug commits, and the other 43 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-app/src/views/menu.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/muxy-app/src/views/settings/appearance.rs crates/muxy-app/src/views/settings/appearance.rs:18— crates/muxy-app/src/views/settings/appearance.rs changed 30 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 58 in muxy_app::views::settings::appearance::rows at line 18. 1 of those changes was a fix/bug commit, and the other 29 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-app/src/views/settings/appearance.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/muxy-app/src/boot.rs crates/muxy-app/src/boot.rs:658— crates/muxy-app/src/boot.rs changed 45 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in muxy_app::boot::worker at line 658. 3 of those changes were fix/bug commits, and the other 42 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-app/src/boot.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/muxy-server/src/connection/reader.rs crates/muxy-server/src/connection/reader.rs:336— crates/muxy-server/src/connection/reader.rs changed 31 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 46 in muxy_server::connection::reader::ordered_request at line 336. 1 of those changes was a fix/bug commit, and the other 30 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-server/src/connection/reader.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/muxy-app/src/views/workspace.rs crates/muxy-app/src/views/workspace.rs:375— crates/muxy-app/src/views/workspace.rs changed 71 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in AppModel::prepare_workspace at line 375. 4 of those changes were fix/bug commits, and the other 67 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-app/src/views/workspace.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/muxy-app-core/src/state.rs crates/muxy-app-core/src/state.rs:1211— crates/muxy-app-core/src/state.rs changed 41 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in AppState::validate at line 1211. 3 of those changes were fix/bug commits, and the other 38 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-app-core/src/state.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/muxy-protocol/src/validate.rs crates/muxy-protocol/src/validate.rs:325— crates/muxy-protocol/src/validate.rs changed 31 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in muxy_protocol::validate::validate_reply at line 325. 3 of those changes were fix/bug commits, and the other 28 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-protocol/src/validate.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/muxy-app/src/views/terminal/pane.rs crates/muxy-app/src/views/terminal/pane.rs:913— crates/muxy-app/src/views/terminal/pane.rs changed 44 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in TerminalPane::metadata at line 913. 10 of those changes were fix/bug commits, and the other 34 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-app/src/views/terminal/pane.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/muxy-app/src/model/git.rs crates/muxy-app/src/model/git.rs:341— crates/muxy-app/src/model/git.rs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 76 in AppModel::receive_git at line 341. 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 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-app/src/model/git.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/muxy-server/src/session/owner.rs crates/muxy-server/src/session/owner.rs:283— crates/muxy-server/src/session/owner.rs changed 31 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in Owner::serve at line 283. 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 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-server/src/session/owner.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/muxy-app/src/views/settings/mod.rs crates/muxy-app/src/views/settings/mod.rs:325— crates/muxy-app/src/views/settings/mod.rs changed 60 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in SettingsView::create_fields at line 325. 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 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-app/src/views/settings/mod.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/muxy-ui/src/picker.rs crates/muxy-ui/src/picker.rs:1094— crates/muxy-ui/src/picker.rs changed 24 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in Picker::render_item at line 1094. 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 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-ui/src/picker.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/muxy-app/src/model/extensions/calls.rs crates/muxy-app/src/model/extensions/calls.rs:16— crates/muxy-app/src/model/extensions/calls.rs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 54 in AppModel::dispatch_extension at line 16. 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 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-app/src/model/extensions/calls.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/muxy-app/src/model/webviews.rs crates/muxy-app/src/model/webviews.rs:579— crates/muxy-app/src/model/webviews.rs changed 34 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in AppModel::dispatch_webview at line 579. 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 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-app/src/model/webviews.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/muxy-app/src/model/catalog.rs crates/muxy-app/src/model/catalog.rs:129— crates/muxy-app/src/model/catalog.rs changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in AppModel::receive_catalog at line 129. 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 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-app/src/model/catalog.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/muxy-app/src/views/settings/terminal.rs crates/muxy-app/src/views/settings/terminal.rs:427— crates/muxy-app/src/views/settings/terminal.rs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in muxy_app::views::settings::terminal::rows at line 427. 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 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-app/src/views/settings/terminal.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/muxy-app/src/views/git.rs crates/muxy-app/src/views/git.rs:188— crates/muxy-app/src/views/git.rs changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in AppModel::update_git_picker at line 188. 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 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-app/src/views/git.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/muxy-app/src/views/project_picker.rs crates/muxy-app/src/views/project_picker.rs:365— crates/muxy-app/src/views/project_picker.rs changed 29 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in ProjectPicker::sync_picker at line 365. 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 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-app/src/views/project_picker.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/muxy-app/src/views/settings/results.rs crates/muxy-app/src/views/settings/results.rs:162— crates/muxy-app/src/views/settings/results.rs changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in SettingsView::refresh_results at line 162. 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 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-app/src/views/settings/results.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/muxy-app/src/views/settings/tab.rs crates/muxy-app/src/views/settings/tab.rs:165— crates/muxy-app/src/views/settings/tab.rs changed 33 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in SettingsTab::open_picker at line 165. 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 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-app/src/views/settings/tab.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/muxy-cli/src/args.rs crates/muxy-cli/src/args.rs:106— crates/muxy-cli/src/args.rs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in muxy_cli::args::command at line 106. 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 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-cli/src/args.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/muxy-app/src/model/extensions/mod.rs crates/muxy-app/src/model/extensions/mod.rs:208— crates/muxy-app/src/model/extensions/mod.rs changed 27 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in AppModel::extension_client at line 208. 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 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-app/src/model/extensions/mod.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/muxy-app-core/src/settings/keymap.rs crates/muxy-app-core/src/settings/keymap.rs:228— crates/muxy-app-core/src/settings/keymap.rs changed 27 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in Keymap::from_overrides at line 228. 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 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-app-core/src/settings/keymap.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
AppModel::receive_git (cognitive 106) crates/muxy-app/src/model/git.rs:341— AppModel::receive_git has cognitive complexity 106 (threshold 15). Drivers by points: if/else 34 (72 pts), boolean chains 18, match/switch 7 (16 pts) (nesting depth added 47). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AppModel::apply_preference (cognitive 49) crates/muxy-app/src/model/preferences.rs:524— AppModel::apply_preference has cognitive complexity 49 (threshold 15). Drivers by points: if/else 21 (40 pts), match/switch 3 (5 pts), boolean chains 4 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppModel::update_git_picker (cognitive 46) crates/muxy-app/src/views/git.rs:188— AppModel::update_git_picker has cognitive complexity 46 (threshold 15). Drivers by points: if/else 20 (31 pts), boolean chains 6, loops 2 (6 pts), match/switch 2 (3 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppModel::submit_composer (cognitive 39) crates/muxy-app/src/model/composer.rs:957— AppModel::submit_composer has cognitive complexity 39 (threshold 15). Drivers by points: if/else 15 (26 pts), match/switch 4 (7 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppModel::sync_extension_events (cognitive 33) crates/muxy-app/src/model/extensions/events.rs:353— AppModel::sync_extension_events has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (20 pts), loops 9 (12 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppModel::receive (cognitive 32) crates/muxy-app/src/model.rs:2594— AppModel::receive has cognitive complexity 32 (threshold 15). Drivers by points: if/else 16 (31 pts), match/switch 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.
AppModel::running_agents (cognitive 27) crates/muxy-app/src/model/agents_panel.rs:144— AppModel::running_agents has cognitive complexity 27 (threshold 15). Drivers by points: if/else 5 (16 pts), loops 3 (6 pts), match/switch 1 (4 pts), boolean chains 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppModel::receive_catalog (cognitive 26) crates/muxy-app/src/model/catalog.rs:129— AppModel::receive_catalog has cognitive complexity 26 (threshold 15). Drivers by points: if/else 15 (19 pts), boolean chains 4, loops 1 (2 pts), match/switch 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.
AppModel::update_details (cognitive 26) crates/muxy-app/src/model/updates/status.rs:50— AppModel::update_details has cognitive complexity 26 (threshold 15). Drivers by points: if/else 19 (24 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AppModel::panel_operation (cognitive 25) crates/muxy-app/src/model/webviews/panels.rs:362— AppModel::panel_operation has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 3, match/switch 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.
AppModel::extension_client (cognitive 23) crates/muxy-app/src/model/extensions/mod.rs:208— AppModel::extension_client has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 4, match/switch 2 (3 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.
AppModel::worktrees_synced (cognitive 23) crates/muxy-app/src/model/worktrees.rs:480— AppModel::worktrees_synced has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 4, loops 1 (3 pts), match/switch 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.
AppModel::receive_event (cognitive 23) crates/muxy-app/src/model.rs:3128— AppModel::receive_event has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (19 pts), match/switch 2 (3 pts), boolean chains 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.
AppModel::await_consent (cognitive 22) crates/muxy-app/src/model/extensions/consent.rs:473— AppModel::await_consent has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 6, match/switch 2 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppModel::close_confirmed (cognitive 22) crates/muxy-app/src/model.rs:1674— AppModel::close_confirmed has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 5, match/switch 1 (2 pts), loops 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.
AppModel::receive_attach_failed (cognitive 22) crates/muxy-app/src/model.rs:2863— AppModel::receive_attach_failed has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 5 (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.
AppModel::browser_event (cognitive 21) crates/muxy-app/src/model/browsers/mod.rs:251— AppModel::browser_event has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 3, match/switch 2 (3 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.
AppModel::discard_pending (cognitive 20) crates/muxy-app/src/model.rs:1821— AppModel::discard_pending has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 4, loops 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppModel::perform_menu (cognitive 20) crates/muxy-app/src/views/menu.rs:590— AppModel::perform_menu has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (14 pts), match/switch 3 (4 pts), boolean chains 2 (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.
AppModel::sync_extension_file_watches (cognitive 19) crates/muxy-app/src/model/extensions/events.rs:613— AppModel::sync_extension_file_watches has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 3 (4 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppModel::request_git_context (cognitive 19) crates/muxy-app/src/model/git.rs:177— AppModel::request_git_context has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 4 (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.
AppModel::rehome_pages (cognitive 19) crates/muxy-app/src/model/webviews.rs:223— AppModel::rehome_pages has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (15 pts), match/switch 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.
AppModel::sync_visible (cognitive 19) crates/muxy-app/src/model.rs:2045— AppModel::sync_visible has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 3, 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.
AppModel::receive_attached (cognitive 19) crates/muxy-app/src/model.rs:2790— AppModel::receive_attached has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 5 (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.
AppModel::extension_server_call (cognitive 18) crates/muxy-app/src/model/extensions/calls.rs:526— AppModel::extension_server_call has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (13 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
muxy_app::views::settings::appearance::rows (cognitive 71) crates/muxy-app/src/views/settings/appearance.rs:18— muxy_app::views::settings::appearance::rows has cognitive complexity 71 (threshold 15). Drivers by points: if/else 29 (39 pts), boolean chains 22, loops 6, match/switch 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.
muxy_app::views::terminal::element::glyph::strokes (cognitive 58) crates/muxy-app/src/views/terminal/element/glyph.rs:131— muxy_app::views::terminal::element::glyph::strokes has cognitive complexity 58 (threshold 15). Drivers by points: if/else 20 (44 pts), loops 3 (6 pts), match/switch 2 (6 pts), boolean chains 2 (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_app::boot::worker (cognitive 46) crates/muxy-app/src/boot.rs:658— muxy_app::boot::worker has cognitive complexity 46 (threshold 15). Drivers by points: if/else 13 (33 pts), match/switch 3 (8 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_app::views::terminal::element::paint (cognitive 37) crates/muxy-app/src/views/terminal/element.rs:886— muxy_app::views::terminal::element::paint has cognitive complexity 37 (threshold 15). Drivers by points: loops 12 (21 pts), if/else 8 (14 pts), match/switch 1 (2 pts) (nesting depth added 16). 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.
muxy_app::views::terminal::links::widen (cognitive 37) crates/muxy-app/src/views/terminal/links.rs:155— muxy_app::views::terminal::links::widen has cognitive complexity 37 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 7 (9 pts), boolean chains 8, match/switch 3 (6 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_app::backup::archive::read (cognitive 36) crates/muxy-app/src/backup/archive.rs:147— muxy_app::backup::archive::read has cognitive complexity 36 (threshold 15). Drivers by points: if/else 18 (27 pts), boolean chains 6, loops 2, match/switch 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_app::model::composer::prepare (cognitive 30) crates/muxy-app/src/model/composer.rs:720— muxy_app::model::composer::prepare has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (24 pts), match/switch 3 (5 pts), 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.
muxy_app::picker::search::scan (cognitive 30) crates/muxy-app/src/picker/search.rs:244— muxy_app::picker::search::scan has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (24 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_app::views::settings::terminal::rows (cognitive 30) crates/muxy-app/src/views/settings/terminal.rs:427— muxy_app::views::settings::terminal::rows has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (18 pts), match/switch 3 (9 pts), boolean chains 2, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_app::views::terminal::element::prepare (cognitive 30) crates/muxy-app/src/views/terminal/element.rs:315— muxy_app::views::terminal::element::prepare has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (21 pts), loops 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.
muxy_app::views::git::form::render (cognitive 27) crates/muxy-app/src/views/git/form.rs:13— muxy_app::views::git::form::render has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15 (17 pts), boolean chains 8, loops 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.
muxy_app::views::settings::quick_terminal::rows (cognitive 23) crates/muxy-app/src/views/settings/quick_terminal.rs:91— muxy_app::views::settings::quick_terminal::rows has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14 (21 pts), loops 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_app::views::splits::header::actions (cognitive 23) crates/muxy-app/src/views/splits/header.rs:303— muxy_app::views::splits::header::actions has cognitive complexity 23 (threshold 15). Drivers by points: if/else 16 (21 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
muxy_app::views::terminal::element::selected_runs (cognitive 22) crates/muxy-app/src/views/terminal/element.rs:461— muxy_app::views::terminal::element::selected_runs has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 2 (5 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_app::model::extensions::consent::dialog_options (cognitive 21) crates/muxy-app/src/model/extensions/consent.rs:701— muxy_app::model::extensions::consent::dialog_options has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 3, match/switch 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.
muxy_app::views::tab_activity::status_glyph_in (cognitive 21) crates/muxy-app/src/views/tab_activity.rs:558— muxy_app::views::tab_activity::status_glyph_in has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (17 pts), match/switch 2 (3 pts), boolean chains 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.
muxy_app::views::terminal::element::background::uncovered (cognitive 21) crates/muxy-app/src/views/terminal/element/background.rs:5— muxy_app::views::terminal::element::background::uncovered has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 3 (5 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.
muxy_app::model::remote_servers::join_destination (cognitive 20) crates/muxy-app/src/model/remote_servers.rs:201— muxy_app::model::remote_servers::join_destination has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 4 (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.
muxy_app::views::tab_strip::drag::move_pointer (cognitive 20) crates/muxy-app/src/views/tab_strip/drag.rs:292— muxy_app::views::tab_strip::drag::move_pointer has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 5, match/switch 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
muxy_app::views::terminal::links::detect (cognitive 20) crates/muxy-app/src/views/terminal/links.rs:51— muxy_app::views::terminal::links::detect has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 2, 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.
muxy_app::backup::transaction::restore (cognitive 19) crates/muxy-app/src/backup/transaction.rs:64— muxy_app::backup::transaction::restore has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 2, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
muxy_app::project_icon::icns::jpeg2000_header (cognitive 19) crates/muxy-app/src/project_icon/icns.rs:174— muxy_app::project_icon::icns::jpeg2000_header has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (11 pts), match/switch 3 (7 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.
muxy_app::repository_actions::parse_metadata (cognitive 19) crates/muxy-app/src/repository_actions.rs:520— muxy_app::repository_actions::parse_metadata has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_app::views::terminal::element::terminal (cognitive 19) crates/muxy-app/src/views/terminal/element.rs:70— muxy_app::views::terminal::element::terminal has cognitive complexity 19 (threshold 15). Drivers by points: loops 5 (10 pts), if/else 7 (8 pts), boolean chains 1 (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.
muxy_app::views::terminal::input::encode_with_bindings (cognitive 19) crates/muxy-app/src/views/terminal/input.rs:149— muxy_app::views::terminal::input::encode_with_bindings has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 4, match/switch 3 (4 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.
AppModel::receive_git (cyclomatic 76) crates/muxy-app/src/model/git.rs:341— AppModel::receive_git has cyclomatic complexity 76 (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.
AppModel::apply_preference (cyclomatic 70) crates/muxy-app/src/model/preferences.rs:524— AppModel::apply_preference has cyclomatic complexity 70 (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.
AppModel::perform_menu (cyclomatic 64) crates/muxy-app/src/views/menu.rs:590— AppModel::perform_menu has cyclomatic complexity 64 (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.
AppModel::dispatch_extension (cyclomatic 54) crates/muxy-app/src/model/extensions/calls.rs:16— AppModel::dispatch_extension has cyclomatic complexity 54 (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.
AppModel::receive (cyclomatic 54) crates/muxy-app/src/model.rs:2594— AppModel::receive has cyclomatic complexity 54 (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.
AppModel::submit_composer (cyclomatic 29) crates/muxy-app/src/model/composer.rs:957— AppModel::submit_composer 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.
AppModel::receive_event (cyclomatic 27) crates/muxy-app/src/model.rs:3128— AppModel::receive_event 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.
AppModel::update_git_picker (cyclomatic 27) crates/muxy-app/src/views/git.rs:188— AppModel::update_git_picker 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.
AppModel::create_terminal_view (cyclomatic 25) crates/muxy-app/src/model.rs:2114— AppModel::create_terminal_view has cyclomatic complexity 25 (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.
AppModel::perform_server_menu (cyclomatic 25) crates/muxy-app/src/views/server_menu.rs:389— AppModel::perform_server_menu has cyclomatic complexity 25 (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.
AppModel::receive_catalog (cyclomatic 23) crates/muxy-app/src/model/catalog.rs:129— AppModel::receive_catalog has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AppModel::browser_event (cyclomatic 21) crates/muxy-app/src/model/browsers/mod.rs:251— AppModel::browser_event 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.
AppModel::sync_extension_events (cyclomatic 21) crates/muxy-app/src/model/extensions/events.rs:353— AppModel::sync_extension_events 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.
AppModel::dispatch_webview (cyclomatic 21) crates/muxy-app/src/model/webviews.rs:579— AppModel::dispatch_webview has cyclomatic complexity 21 (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.
AppModel::close_confirmed (cyclomatic 21) crates/muxy-app/src/model.rs:1674— AppModel::close_confirmed has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AppModel::request_pull_request_action (cyclomatic 21) crates/muxy-app/src/views/git/pr.rs:123— AppModel::request_pull_request_action 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.
AppModel::ui_call (cyclomatic 20) crates/muxy-app/src/model/extensions/app.rs:108— AppModel::ui_call 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.
AppModel::extension_client (cyclomatic 19) crates/muxy-app/src/model/extensions/mod.rs:208— AppModel::extension_client 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.
AppModel::panel_operation (cyclomatic 19) crates/muxy-app/src/model/webviews/panels.rs:362— AppModel::panel_operation 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.
AppModel::continue_onboarding_pairing (cyclomatic 18) crates/muxy-app/src/model/onboarding.rs:651— AppModel::continue_onboarding_pairing 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.
AppModel::update_details (cyclomatic 18) crates/muxy-app/src/model/updates/status.rs:50— AppModel::update_details 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.
AppModel::prepare_workspace (cyclomatic 18) crates/muxy-app/src/views/workspace.rs:375— AppModel::prepare_workspace 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.
AppModel::await_consent (cyclomatic 17) crates/muxy-app/src/model/extensions/consent.rs:473— AppModel::await_consent 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.
AppModel::terminal_menu (cyclomatic 17) crates/muxy-app/src/model/links.rs:296— AppModel::terminal_menu 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.
AppModel::pane_control (cyclomatic 16) crates/muxy-app/src/model/extensions/controls.rs:264— AppModel::pane_control 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.
MethodTooLong: Picker.render_item crates/muxy-ui/src/picker.rs:1094— MethodTooLong — render_item runs 302 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 202 over it, 3.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AppModel.apply_preference crates/muxy-app/src/model/preferences.rs:524— MethodTooLong — apply_preference runs 259 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 159 over it, 2.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AppModel.receive_git crates/muxy-app/src/model/git.rs:341— MethodTooLong — receive_git runs 231 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 131 over it, 2.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: QuickTerminalView.render crates/muxy-app/src/views/quick_terminal.rs:213— MethodTooLong — render runs 192 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 92 over it, 1.92× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TextElement.prepaint crates/muxy-ui/src/text_input.rs:1849— MethodTooLong — prepaint runs 189 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× 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: Picker.render crates/muxy-ui/src/picker.rs:1815— MethodTooLong — render runs 151 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 51 over it, 1.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AppModel.dispatch_extension crates/muxy-app/src/model/extensions/calls.rs:16— MethodTooLong — dispatch_extension runs 140 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 40 over it, 1.40× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AppModel.perform_menu crates/muxy-app/src/views/menu.rs:590— MethodTooLong — perform_menu runs 139 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Dialog.render crates/muxy-ui/src/dialog/view.rs:155— MethodTooLong — render runs 133 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× 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: ExtensionsView.render crates/muxy-app/src/views/settings/extensions.rs:847— MethodTooLong — render runs 130 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 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: Requests.route crates/muxy-server/src/connection/reader.rs:167— MethodTooLong — route runs 129 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 29 over it, 1.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ExtensionsView.gallery crates/muxy-app/src/views/settings/extensions/detail.rs:522— MethodTooLong — gallery runs 127 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AppState.restore_configuration crates/muxy-app-core/src/backup/projects.rs:110— MethodTooLong — restore_configuration runs 115 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 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: PromptTarget.new crates/muxy-ui/src/dialog/prompt.rs:210— MethodTooLong — new runs 114 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 14 over it, 1.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: AppModel.open_ssh_form crates/muxy-app/src/views/remote_servers.rs:752— MethodTooLong — open_ssh_form runs 111 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 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: AppModel.render_workspace crates/muxy-app/src/views/workspace.rs:436— MethodTooLong — render_workspace runs 111 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 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: AppModel.request_pull_request_action crates/muxy-app/src/views/git/pr.rs:123— MethodTooLong — request_pull_request_action runs 108 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× 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: SettingsTab.backup_action crates/muxy-app/src/views/settings/backup.rs:119— MethodTooLong — backup_action runs 107 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Item.render crates/muxy-app/src/views/menu/render.rs:224— MethodTooLong — render runs 104 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TerminalSettings.read_source crates/muxy-app-core/src/settings/ghostty.rs:255— MethodTooLong — read_source runs 103 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AppModel.open_git_form crates/muxy-app/src/views/git.rs:463— MethodTooLong — open_git_form runs 101 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: muxy_cli::browser::args::invocation crates/muxy-cli/src/browser/args.rs:142— FunctionTooLong — muxy_cli::browser::args::invocation runs 240 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 140 over it, 2.40× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: muxy_app::views::settings::appearance::rows crates/muxy-app/src/views/settings/appearance.rs:18— FunctionTooLong — muxy_app::views::settings::appearance::rows runs 216 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 116 over it, 2.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: muxy_server::connection::reader::ordered_request crates/muxy-server/src/connection/reader.rs:336— FunctionTooLong — muxy_server::connection::reader::ordered_request runs 203 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 103 over it, 2.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: muxy_app::boot::perform crates/muxy-app/src/boot.rs:1143— FunctionTooLong — muxy_app::boot::perform runs 198 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 98 over it, 1.98× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: muxy_app::views::settings::terminal::rows crates/muxy-app/src/views/settings/terminal.rs:427— FunctionTooLong — muxy_app::views::settings::terminal::rows runs 189 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: muxy_app::views::settings::quick_terminal::rows crates/muxy-app/src/views/settings/quick_terminal.rs:91— FunctionTooLong — muxy_app::views::settings::quick_terminal::rows runs 167 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 67 over it, 1.67× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: muxy_app::views::sidebar::project_row crates/muxy-app/src/views/sidebar.rs:1311— FunctionTooLong — muxy_app::views::sidebar::project_row runs 160 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 60 over it, 1.60× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: muxy_app::views::tab_strip::tab_cell crates/muxy-app/src/views/tab_strip.rs:400— FunctionTooLong — muxy_app::views::tab_strip::tab_cell runs 160 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 60 over it, 1.60× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: muxy_app::views::tab_sidebar::tab_row crates/muxy-app/src/views/tab_sidebar.rs:648— FunctionTooLong — muxy_app::views::tab_sidebar::tab_row runs 145 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: muxy_app::views::git::ai_provider::render_provider_menu crates/muxy-app/src/views/git/ai_provider.rs:271— FunctionTooLong — muxy_app::views::git::ai_provider::render_provider_menu runs 139 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: muxy_app::views::git::form::render crates/muxy-app/src/views/git/form.rs:13— FunctionTooLong — muxy_app::views::git::form::render runs 136 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: muxy_app::views::terminal::element::terminal crates/muxy-app/src/views/terminal/element.rs:70— FunctionTooLong — muxy_app::views::terminal::element::terminal runs 135 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: muxy_app::boot::worker crates/muxy-app/src/boot.rs:658— FunctionTooLong — muxy_app::boot::worker runs 131 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 31 over it, 1.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: muxy_app::menus crates/muxy-app/src/main.rs:326— FunctionTooLong — muxy_app::menus runs 122 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: muxy_app::views::terminal::element::prepare crates/muxy-app/src/views/terminal/element.rs:315— FunctionTooLong — muxy_app::views::terminal::element::prepare runs 119 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: muxy_protocol::validate::validate_reply crates/muxy-protocol/src/validate.rs:325— FunctionTooLong — muxy_protocol::validate::validate_reply runs 111 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 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.
FunctionTooLong: muxy_app::views::status_bar::ai_action_chip crates/muxy-app/src/views/status_bar.rs:360— FunctionTooLong — muxy_app::views::status_bar::ai_action_chip runs 108 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: muxy_app::views::terminal::element::paint crates/muxy-app/src/views/terminal/element.rs:886— FunctionTooLong — muxy_app::views::terminal::element::paint runs 105 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: muxy_app::views::sidebar::worktrees::row crates/muxy-app/src/views/sidebar/worktrees.rs:181— FunctionTooLong — muxy_app::views::sidebar::worktrees::row runs 104 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 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.
TooManyMethods: AppModel crates/muxy-app/src/model.rs:136— TooManyMethods — 1361 methods, declared across 109 files: src/model.rs (109), model/webviews.rs (47), model/preferences.rs (40), extensions/mod.rs (37), +105 more file(s). The bar is 30 methods; this is 1331 over it, 45.37× 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: Client crates/muxy-client/src/client.rs:41— TooManyMethods — 220 methods, declared across 8 files: src/git.rs (98), src/client.rs (56), src/files.rs (28), src/catalog.rs (16), +4 more file(s). The bar is 30 methods; this is 190 over it, 7.33× 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: AppState crates/muxy-app-core/src/state.rs:22— TooManyMethods — 205 methods, declared across 15 files: src/state.rs (72), src/tab_windows.rs (34), src/servers.rs (20), src/catalog.rs (19), +11 more file(s). The bar is 30 methods; this is 175 over it, 6.83× 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: TerminalPane crates/muxy-app/src/views/terminal/pane.rs:132— TooManyMethods — 114 methods, declared across 6 files: terminal/pane.rs (86), terminal/find.rs (10), terminal/scrollbar.rs (8), terminal/cursor.rs (4), +2 more file(s). The bar is 30 methods; this is 84 over it, 3.80× 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: TextInput crates/muxy-ui/src/text_input.rs:523— TooManyMethods — 97 methods. The bar is 30 methods; this is 67 over it, 3.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Registry crates/muxy-server/src/registry.rs:46— TooManyMethods — 91 methods, declared across 6 files: src/registry.rs (65), git/worktree.rs (13), push/mod.rs (7), git/mod.rs (4), +2 more file(s). The bar is 30 methods; this is 61 over it, 3.03× 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: ExtensionsView crates/muxy-app/src/views/settings/extensions.rs:119— TooManyMethods — 86 methods, declared across 5 files: settings/extensions.rs (48), extensions/cards.rs (18), extensions/detail.rs (13), extensions/configuration.rs (4), +1 more file(s). The bar is 30 methods; this is 56 over it, 2.87× 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: SettingsView crates/muxy-app/src/views/settings/mod.rs:156— TooManyMethods — 84 methods, declared across 14 files: settings/mod.rs (29), settings/layout.rs (11), settings/slider.rs (9), settings/results.rs (8), +10 more file(s). The bar is 30 methods; this is 54 over it, 2.80× 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: GitRepository crates/muxy-mobile/src/git/repository.rs:14— TooManyMethods — 48 methods, declared across 3 files: git/repository.rs (31), git/pull_requests.rs (9), git/worktrees.rs (8). The bar is 30 methods; this is 18 over it, 1.60× 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: Picker crates/muxy-ui/src/picker.rs:740— TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Connection crates/muxy-server/src/connection/peer.rs:43— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Terminal crates/muxy-terminal/src/ghostty.rs:96— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: NativeBrowser crates/muxy-ui/src/webview/linux/browser.rs:19— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Page crates/muxy-ui/src/webview/linux/page.rs:652— TooManyMethods — 41 methods, declared across 4 files: linux/page.rs (20), page/browser.rs (13), browser/cookies.rs (5), page/input.rs (3). The bar is 30 methods; this is 11 over it, 1.37× 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: Catalog crates/muxy-server/src/catalog/mod.rs:74— TooManyMethods — 40 methods, declared across 6 files: catalog/sessions.rs (15), catalog/mod.rs (11), catalog/git.rs (7), catalog/mutations.rs (4), +2 more file(s). The bar is 30 methods; this is 10 over it, 1.33× 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: NativeBrowser crates/muxy-ui/src/browser/unsupported.rs:16— 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: BrowserView crates/muxy-app/src/views/browser/mod.rs:106— 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: RemoteAccess crates/muxy-server/src/remote/mod.rs:37— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
muxy_cli::tui::events (cognitive 38) crates/muxy-cli/src/tui/mod.rs:66— muxy_cli::tui::events has cognitive complexity 38 (threshold 15). Drivers by points: if/else 15 (30 pts), match/switch 2 (5 pts), boolean chains 2, loops 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_cli::completion::candidates (cognitive 29) crates/muxy-cli/src/completion.rs:72— muxy_cli::completion::candidates has cognitive complexity 29 (threshold 15). Drivers by points: if/else 17 (26 pts), boolean chains 2, 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.
muxy_cli::ui::sidebar::project_list (cognitive 24) crates/muxy-cli/src/ui/sidebar.rs:73— muxy_cli::ui::sidebar::project_list has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_cli::extension::dev::fingerprint (cognitive 23) crates/muxy-cli/src/extension/dev.rs:303— muxy_cli::extension::dev::fingerprint has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (16 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_cli::manage::execute (cognitive 23) crates/muxy-cli/src/manage/mod.rs:82— muxy_cli::manage::execute has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (19 pts), match/switch 2 (3 pts), boolean chains 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.
muxy_cli::config::run (cognitive 21) crates/muxy-cli/src/config.rs:75— muxy_cli::config::run has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (17 pts), loops 1 (3 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.
muxy_cli::extension::text (cognitive 19) crates/muxy-cli/src/extension.rs:390— muxy_cli::extension::text has cognitive complexity 19 (threshold 15). Drivers by points: loops 7 (14 pts), match/switch 2 (3 pts), if/else 1 (2 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.
muxy_cli::worker::io::reader (cognitive 18) crates/muxy-cli/src/worker/io.rs:216— muxy_cli::worker::io::reader has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (15 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_cli::args::command (cognitive 17) crates/muxy-cli/src/args.rs:106— muxy_cli::args::command has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, if/else 3 (4 pts), match/switch 2 (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.
muxy_cli::browser::print (cognitive 17) crates/muxy-cli/src/browser/mod.rs:89— muxy_cli::browser::print has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), match/switch 3 (5 pts), loops 1 (3 pts) (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.
muxy_cli::tui::keys::overlay (cognitive 17) crates/muxy-cli/src/tui/keys.rs:216— muxy_cli::tui::keys::overlay has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 7 (13 pts), if/else 2 (4 pts) (nesting depth added 8). 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.
muxy_cli::ui::panes::scroll_position (cognitive 17) crates/muxy-cli/src/ui/panes.rs:163— muxy_cli::ui::panes::scroll_position has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (15 pts), loops 1, match/switch 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
muxy_cli::ui::tabs::strip (cognitive 17) crates/muxy-cli/src/ui/tabs.rs:145— muxy_cli::ui::tabs::strip has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (12 pts), loops 3, boolean chains 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
muxy_cli::manage::args::parse (cognitive 16) crates/muxy-cli/src/manage/args.rs:175— muxy_cli::manage::args::parse has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, if/else 4 (5 pts), match/switch 3 (5 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.
muxy_cli::tui::mouse::wheel (cognitive 16) crates/muxy-cli/src/tui/mouse.rs:412— muxy_cli::tui::mouse::wheel has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (15 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.
muxy_cli::worker::apply (cognitive 16) crates/muxy-cli/src/worker.rs:902— muxy_cli::worker::apply 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.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×16
muxy_cli::args::command (cyclomatic 37) crates/muxy-cli/src/args.rs:106— muxy_cli::args::command has cyclomatic complexity 37 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
muxy_cli::browser::args::invocation (cyclomatic 34) crates/muxy-cli/src/browser/args.rs:142— muxy_cli::browser::args::invocation has cyclomatic complexity 34 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This is NOT this file's highest cyclomatic complexity: muxy_cli::browser::args::verb (cyclomatic 37) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
muxy_cli::tui::keys::overlay (cyclomatic 33) crates/muxy-cli/src/tui/keys.rs:216— muxy_cli::tui::keys::overlay has cyclomatic complexity 33 (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.
muxy_cli::extension::parse (cyclomatic 31) crates/muxy-cli/src/extension.rs:37— muxy_cli::extension::parse has cyclomatic complexity 31 (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.
muxy_cli::tui::keys::prefix (cyclomatic 27) crates/muxy-cli/src/tui/keys.rs:48— muxy_cli::tui::keys::prefix has cyclomatic complexity 27 (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.
muxy_cli::input::encode (cyclomatic 26) crates/muxy-cli/src/input.rs:29— muxy_cli::input::encode 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.
muxy_cli::tui::events (cyclomatic 25) crates/muxy-cli/src/tui/mod.rs:66— muxy_cli::tui::events 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.
muxy_cli::worker::apply (cyclomatic 24) crates/muxy-cli/src/worker.rs:902— muxy_cli::worker::apply has cyclomatic complexity 24 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
muxy_cli::manage::execute (cyclomatic 22) crates/muxy-cli/src/manage/mod.rs:82— muxy_cli::manage::execute has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
muxy_cli::manage::args::parse (cyclomatic 22) crates/muxy-cli/src/manage/args.rs:175— muxy_cli::manage::args::parse has cyclomatic complexity 22 (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.
muxy_cli::extension::text (cyclomatic 19) crates/muxy-cli/src/extension.rs:390— muxy_cli::extension::text has cyclomatic complexity 19 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
muxy_cli::completion::candidates (cyclomatic 18) crates/muxy-cli/src/completion.rs:72— muxy_cli::completion::candidates 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.
muxy_cli::worker::io::reader (cyclomatic 17) crates/muxy-cli/src/worker/io.rs:216— muxy_cli::worker::io::reader 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.
ClassTooLong: ExtensionsView crates/muxy-app/src/views/settings/extensions.rs:119— ClassTooLong — 1017 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 86 methods, 4 blocks, lines 119-1482. The bar is 400 significant lines; this is 617 over it, 2.54× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Picker crates/muxy-ui/src/picker.rs:740— ClassTooLong — 971 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 45 methods, 5 blocks, lines 740-2020. The bar is 400 significant lines; this is 571 over it, 2.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AppState crates/muxy-app-core/src/state.rs:22— ClassTooLong — 939 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 205 methods, 3 blocks, lines 22-1314. The bar is 400 significant lines; this is 539 over it, 2.35× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TextInput crates/muxy-ui/src/text_input.rs:523— ClassTooLong — 910 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 97 methods, 6 blocks, lines 523-2207. The bar is 400 significant lines; this is 510 over it, 2.28× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Terminal crates/muxy-terminal/src/ghostty.rs:96— ClassTooLong — 666 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 42 methods, 2 blocks, lines 96-966. The bar is 400 significant lines; this is 266 over it, 1.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: BrowserView crates/muxy-app/src/views/browser/mod.rs:106— ClassTooLong — 619 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 34 methods, 4 blocks, lines 106-1027. The bar is 400 significant lines; this is 219 over it, 1.55× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Registry crates/muxy-server/src/registry.rs:46— ClassTooLong — 612 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 91 methods, 2 blocks, lines 46-893. The bar is 400 significant lines; this is 212 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Owner crates/muxy-server/src/session/owner.rs:83— ClassTooLong — 585 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 20 methods, 2 blocks, lines 83-977. The bar is 400 significant lines; this is 185 over it, 1.46× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SettingsTab crates/muxy-app/src/views/settings/tab.rs:46— ClassTooLong — 536 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 19 methods, 3 blocks, lines 46-775. The bar is 400 significant lines; this is 136 over it, 1.34× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Core crates/muxy-cli/src/worker.rs:210— ClassTooLong — 514 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 22 methods, 2 blocks, lines 210-898. The bar is 400 significant lines; this is 114 over it, 1.29× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ProjectPicker crates/muxy-app/src/views/project_picker.rs:72— ClassTooLong — 469 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 21 methods, 5 blocks, lines 72-701. The bar is 400 significant lines; this is 69 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Webview crates/muxy-app/src/views/webview/mod.rs:104— ClassTooLong — 462 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 25 methods, 4 blocks, lines 104-755. The bar is 400 significant lines; this is 62 over it, 1.16× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Client crates/muxy-client/src/client.rs:41— ClassTooLong — 437 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 220 methods, 3 blocks, lines 41-690. The bar is 400 significant lines; this is 37 over it, 1.09× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (5 lines × 2) crates/muxy-app/src/views/settings/tab.rs:321— crates/muxy-app/src/views/settings/tab.rs:321-325 | crates/muxy-app/src/views/settings/tab.rs:461-465 — 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 `crates/muxy-app/src/views/settings/tab.rs:321` 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) crates/muxy-app/src/views/webview/panel.rs:165— crates/muxy-app/src/views/webview/panel.rs:165-169 | crates/muxy-app/src/views/webview/panel.rs:276-280 — 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 (5 lines × 2) crates/muxy-server/src/shell.rs:124— crates/muxy-server/src/shell.rs:124-128 | crates/muxy-server/src/uploads.rs:94-98 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/muxy-server/src/shell.rs:124` 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) crates/muxy-ui/src/dialog/message.rs:125— crates/muxy-ui/src/dialog/message.rs:125-129 | crates/muxy-ui/src/dialog/prompt.rs:710-714 — 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) crates/muxy-app/src/views/browser/mod.rs:847— crates/muxy-app/src/views/browser/mod.rs:847-851 | crates/muxy-app/src/views/webview/mod.rs:393-397 — `crates/muxy-app/src/views/browser/mod.rs` and `crates/muxy-app/src/views/webview/mod.rs` 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 5 separate duplicated blocks between them, totalling at least 50 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 (5 lines × 2) crates/muxy-ui/src/picker.rs:52— crates/muxy-ui/src/picker.rs:52-56 | crates/muxy-ui/src/text_input.rs:119-123 — 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) crates/muxy-server/src/git/details.rs:112— crates/muxy-server/src/git/details.rs:112-116 | crates/muxy-server/src/git/read.rs:121-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.
Duplicated block (5 lines × 2) crates/muxy-app-core/src/opener.rs:181— crates/muxy-app-core/src/opener.rs:181-185 | crates/muxy-server/src/session/metadata.rs:233-237 — 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 `crates/muxy-app-core/src/opener.rs:181` 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 (5 lines × 2) crates/muxy-app-core/src/servers.rs:238— crates/muxy-app-core/src/servers.rs:238-242 | crates/muxy-app-core/src/set_aside.rs: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. Note first that the copies are not typed on the same thing: the declarations holding them bind `self` to `crate) fn remove_remote_projects(&mut` in one and `&mut` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 2) crates/muxy-app/src/model/webviews.rs:1116— crates/muxy-app/src/model/webviews.rs:1116-1120 | crates/muxy-app/src/model/webviews.rs:1123-1127 — 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 `crates/muxy-app/src/model/webviews.rs:1116` 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) crates/muxy-app/src/views/onboarding.rs:133— crates/muxy-app/src/views/onboarding.rs:133-137 | crates/muxy-app/src/views/proxy.rs:173-177 — 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 `crates/muxy-app/src/views/onboarding.rs:133` 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 (5 lines × 2) crates/muxy-app/src/views/tab_sidebar.rs:882— crates/muxy-app/src/views/tab_sidebar.rs:882-886 | crates/muxy-app/src/views/tab_strip.rs:373-377 — 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 `crates/muxy-app/src/views/tab_sidebar.rs:882` 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) crates/muxy-protocol/src/graphics.rs:140— crates/muxy-protocol/src/graphics.rs:140-144 | crates/muxy-protocol/src/graphics.rs:244-248 — 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.
muxy_app::views::settings::appearance::rows (cyclomatic 58) crates/muxy-app/src/views/settings/appearance.rs:18— muxy_app::views::settings::appearance::rows has cyclomatic complexity 58 (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.
muxy_app::views::terminal::input::encode_with_bindings (cyclomatic 52) crates/muxy-app/src/views/terminal/input.rs:149— muxy_app::views::terminal::input::encode_with_bindings has cyclomatic complexity 52 (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.
muxy_app::views::settings::terminal::rows (cyclomatic 42) crates/muxy-app/src/views/settings/terminal.rs:427— muxy_app::views::settings::terminal::rows has cyclomatic complexity 42 (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.
muxy_app::boot::worker (cyclomatic 33) crates/muxy-app/src/boot.rs:658— muxy_app::boot::worker has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: Work::name (cyclomatic 56) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
muxy_app::backup::archive::read (cyclomatic 27) crates/muxy-app/src/backup/archive.rs:147— muxy_app::backup::archive::read 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.
muxy_app::views::terminal::links::widen (cyclomatic 27) crates/muxy-app/src/views/terminal/links.rs:155— muxy_app::views::terminal::links::widen 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.
muxy_app::views::terminal::element::paint (cyclomatic 22) crates/muxy-app/src/views/terminal/element.rs:886— muxy_app::views::terminal::element::paint has cyclomatic complexity 22 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
muxy_app::views::terminal::element::glyph::strokes (cyclomatic 22) crates/muxy-app/src/views/terminal/element/glyph.rs:131— muxy_app::views::terminal::element::glyph::strokes has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
muxy_app::views::git::form::render (cyclomatic 21) crates/muxy-app/src/views/git/form.rs:13— muxy_app::views::git::form::render has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
muxy_app::repository_actions::prepare (cyclomatic 17) crates/muxy-app/src/repository_actions.rs:350— muxy_app::repository_actions::prepare 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.
muxy_app::views::tab_strip::drag::move_pointer (cyclomatic 17) crates/muxy-app/src/views/tab_strip/drag.rs:292— muxy_app::views::tab_strip::drag::move_pointer 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.
muxy_app::views::terminal::element::prepare (cyclomatic 16) crates/muxy-app/src/views/terminal/element.rs:315— muxy_app::views::terminal::element::prepare 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.
Duplicated block (10 lines × 2) crates/muxy-app/src/model.rs:2474— crates/muxy-app/src/model.rs:2474-2483 | crates/muxy-app/src/model.rs:2505-2514 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) crates/muxy-app/src/model/browsers/automation.rs:245— crates/muxy-app/src/model/browsers/automation.rs:245-254 | crates/muxy-app/src/model/extensions/pages.rs:368-377 — 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 `crates/muxy-app/src/model/browsers/automation.rs:245` 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) crates/muxy-app/src/model/browsers/automation.rs:256— crates/muxy-app/src/model/browsers/automation.rs:256-265 | crates/muxy-app/src/model/extensions/pages.rs:379-388 — 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 `crates/muxy-app/src/model/browsers/automation.rs:256` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/muxy-app/src/model/extensions/mod.rs:857— crates/muxy-app/src/model/extensions/mod.rs:857-866 | crates/muxy-app/src/model/webviews.rs:1519-1528 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) crates/muxy-app/src/model/git.rs:494— crates/muxy-app/src/model/git.rs:494-503 | crates/muxy-app/src/model/git.rs:625-634 — 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 `crates/muxy-app/src/model/git.rs:494` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/muxy-app/src/views/status_bar.rs:576— crates/muxy-app/src/views/status_bar.rs:576-585 | crates/muxy-app/src/views/status_bar.rs:681-690 — 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 `crates/muxy-app/src/views/status_bar.rs:576` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/muxy-protocol/src/samples.rs:139— crates/muxy-protocol/src/samples.rs:139-148 | crates/muxy-protocol/src/samples.rs:159-168 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/muxy-protocol/src/samples.rs:139` 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) crates/muxy-ui/src/text_input.rs:737— crates/muxy-ui/src/text_input.rs:737-746 | crates/muxy-ui/src/text_input.rs:1958-1967 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) crates/muxy-app/src/views/browser/mod.rs:180— crates/muxy-app/src/views/browser/mod.rs:180-189 | crates/muxy-app/src/views/webview/mod.rs:172-181 — `crates/muxy-app/src/views/browser/mod.rs` and `crates/muxy-app/src/views/webview/mod.rs` 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 5 separate duplicated blocks between them, totalling at least 50 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `crates/muxy-app/src/views/browser/mod.rs:180` 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) crates/muxy-app-core/src/backup/mod.rs:65— crates/muxy-app-core/src/backup/mod.rs:65-74 | crates/muxy-server/src/settings.rs:25-34 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) crates/muxy-app/src/model/extensions/events.rs:111— crates/muxy-app/src/model/extensions/events.rs:111-120 | crates/muxy-app/src/views/tab_activity.rs:723-732 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) crates/muxy-app-core/src/composer/draft.rs:552— crates/muxy-app-core/src/composer/draft.rs:552-561 | crates/muxy-app-core/src/composer/draft.rs:569-578 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/muxy-app-core/src/composer/draft.rs:552` 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.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×11
Edited copy of a member (14 corresponding lines) crates/muxy-ui/src/text_input.rs:1341— crates/muxy-ui/src/text_input.rs:1341-1354 | crates/muxy-ui/src/text_input.rs:1356-1372 — 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) crates/muxy-cli/src/worker.rs:535— crates/muxy-cli/src/worker.rs:535-548 | crates/muxy-cli/src/worker.rs:550-568 — 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) crates/muxy-app/src/favicon.rs:20— crates/muxy-app/src/favicon.rs:20-33 | crates/muxy-app/src/opener.rs:54-67 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/muxy-app/src/views/menu.rs:523— crates/muxy-app/src/views/menu.rs:523-536 | crates/muxy-app/src/views/menu.rs:572-587 — 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) crates/muxy-client/src/catalog.rs:162— crates/muxy-client/src/catalog.rs:162-175 | crates/muxy-client/src/catalog.rs:256-276 — 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) crates/muxy-app/src/model/ai.rs:182— crates/muxy-app/src/model/ai.rs:182-197 | crates/muxy-app/src/model/extensions/authoring.rs:355-368 — 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) crates/muxy-app/src/picker/path_service.rs:198— crates/muxy-app/src/picker/path_service.rs:198-212 | crates/muxy-app/src/picker/search.rs:616-629 — 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) crates/muxy-ui/src/command_palette.rs:48— crates/muxy-ui/src/command_palette.rs:48-61 | crates/muxy-ui/src/command_palette.rs:67-80 — 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) crates/muxy-app/src/views/project_picker/targets.rs:48— crates/muxy-app/src/views/project_picker/targets.rs:48-61 | crates/muxy-app/src/views/sidebar.rs:653-667 — 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) crates/muxy-mobile/src/files.rs:138— crates/muxy-mobile/src/files.rs:138-151 | crates/muxy-mobile/src/git/records.rs:468-481 — 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) crates/muxy-mobile/src/files.rs:155— crates/muxy-mobile/src/files.rs:155-168 | crates/muxy-mobile/src/git/records.rs:451-464 — 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.
Duplicated block (8 lines × 2) crates/muxy-app-core/src/extensions/audit.rs:60— crates/muxy-app-core/src/extensions/audit.rs:60-67 | crates/muxy-app/src/model/extensions/logs.rs:173-180 — 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 `crates/muxy-app-core/src/extensions/audit.rs:60` 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 (8 lines × 2) crates/muxy-app-core/src/state.rs:806— crates/muxy-app-core/src/state.rs:806-813 | crates/muxy-app-core/src/tab_windows.rs:585-592 — 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) crates/muxy-app/src/model.rs:282— crates/muxy-app/src/model.rs:282-289 | crates/muxy-app/src/model/preferences.rs:1139-1146 — 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 `crates/muxy-app/src/model.rs:282` 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 `self` to `crate) fn refresh_theme(&mut` in one and `&mut` 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 (8 lines × 2) crates/muxy-app/src/model/extensions/authoring.rs:822— crates/muxy-app/src/model/extensions/authoring.rs:822-829 | crates/muxy-app/src/model/extensions/updates.rs:28-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 `crates/muxy-app/src/model/extensions/authoring.rs:822` 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) crates/muxy-app/src/views/settings/extensions.rs:661— crates/muxy-app/src/views/settings/extensions.rs:661-668 | crates/muxy-app/src/views/settings/extensions.rs:707-714 — 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 `crates/muxy-app/src/views/settings/extensions.rs:661` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) crates/muxy-cli/src/input.rs:106— crates/muxy-cli/src/input.rs:106-113 | crates/muxy-mobile/src/keys.rs:109-116 — 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 `crates/muxy-cli/src/input.rs:106` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) crates/muxy-server/src/git/mod.rs:76— crates/muxy-server/src/git/mod.rs:76-83 | crates/muxy-server/src/git/operations.rs:28-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 `crates/muxy-server/src/git/mod.rs:76` 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 (8 lines × 2) crates/muxy-ui/src/text_input.rs:785— crates/muxy-ui/src/text_input.rs:785-792 | crates/muxy-ui/src/text_input.rs:1937-1944 — 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 `crates/muxy-ui/src/text_input.rs:785` 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) crates/muxy-client/src/events.rs:101— crates/muxy-client/src/events.rs:101-108 | crates/muxy-protocol/src/message.rs:123-130 — 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 `crates/muxy-client/src/events.rs:101` 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) crates/muxy-ui/src/notifications/linux.rs:158— crates/muxy-ui/src/notifications/linux.rs:158-165 | crates/muxy-ui/src/notifications/windows.rs:243-250 — 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) crates/muxy-app/src/views/floating_tab.rs:94— crates/muxy-app/src/views/floating_tab.rs:94-101 | crates/muxy-app/src/views/tab_window.rs:116-124 — 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 `crates/muxy-app/src/views/floating_tab.rs:94` 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 (7 lines × 2) crates/muxy-app/src/cli_install.rs:29— crates/muxy-app/src/cli_install.rs:29-36 | crates/muxy-app/src/model/updates.rs:475-481 — 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 `crates/muxy-app/src/cli_install.rs:29` 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.
Duplicated block (7 lines × 2) crates/muxy-app/src/model/extensions/authoring.rs:150— crates/muxy-app/src/model/extensions/authoring.rs:150-156 | crates/muxy-app/src/model/extensions/authoring.rs:419-425 — 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 `crates/muxy-app/src/model/extensions/authoring.rs:150` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) crates/muxy-app/src/views/tab_strip/drag.rs:385— crates/muxy-app/src/views/tab_strip/drag.rs:385-391 | crates/muxy-ui/src/panel.rs:788-794 — 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 `crates/muxy-app/src/views/tab_strip/drag.rs:385` 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 (7 lines × 2) crates/muxy-cli/src/mobile.rs:97— crates/muxy-cli/src/mobile.rs:97-103 | crates/muxy-cli/src/mobile.rs:188-194 — 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 `crates/muxy-cli/src/mobile.rs:97` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) crates/muxy-server/src/connection/reader.rs:268— crates/muxy-server/src/connection/reader.rs:268-274 | crates/muxy-server/src/connection/reader.rs:290-296 — 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 `crates/muxy-server/src/connection/reader.rs:268` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) crates/muxy-protocol/src/git.rs:583— crates/muxy-protocol/src/git.rs:583-589 | crates/muxy-server/src/git/hooks.rs:83-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. Read the line range as the matched WINDOW rather than a finished unit: at `crates/muxy-protocol/src/git.rs:583` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) crates/muxy-app-core/src/tab_windows.rs:76— crates/muxy-app-core/src/tab_windows.rs:76-82 | crates/muxy-app-core/src/window.rs:50-56 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) crates/muxy-core/src/files/windows.rs:254— crates/muxy-core/src/files/windows.rs:254-260 | crates/muxy-server/src/files/native/windows.rs:305-311 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) crates/muxy-ui/src/notifications/linux.rs:241— crates/muxy-ui/src/notifications/linux.rs:241-247 | crates/muxy-ui/src/notifications/windows.rs:309-315 — 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) crates/muxy-cli/src/mobile.rs:111— crates/muxy-cli/src/mobile.rs:111-121 | crates/muxy-cli/src/mobile.rs:197-203 — 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 `crates/muxy-cli/src/mobile.rs:111` 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 (7 lines × 2) crates/muxy-app/src/model.rs:1926— crates/muxy-app/src/model.rs:1926-1932 | crates/muxy-app/src/model/tab_windows.rs:436-442 — 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.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×10
Edited copy of a member (7 corresponding lines) crates/muxy-app-core/src/extensions/storage.rs:74— crates/muxy-app-core/src/extensions/storage.rs:74-80 | crates/muxy-app-core/src/settings/appearance.rs:462-468 — 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) crates/muxy-app-core/src/composer/storage/windows.rs:83— crates/muxy-app-core/src/composer/storage/windows.rs:83-89 | crates/muxy-server/src/remote/store.rs:216-222 — 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) crates/muxy-app/src/backup/transaction.rs:36— crates/muxy-app/src/backup/transaction.rs:36-43 | crates/muxy-server/src/archive.rs:672-678 — 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) crates/muxy-server/src/detection/regions.rs:105— crates/muxy-server/src/detection/regions.rs:105-111 | crates/muxy-server/src/detection/regions.rs:144-151 — 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) crates/muxy-client/src/catalog.rs:58— crates/muxy-client/src/catalog.rs:58-64 | crates/muxy-client/src/remote.rs:145-151 — 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) crates/muxy-server/src/push/mod.rs:327— crates/muxy-server/src/push/mod.rs:327-333 | crates/muxy-server/src/remote/mod.rs:644-650 — 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) crates/muxy-app-core/src/extensions/panels.rs:163— crates/muxy-app-core/src/extensions/panels.rs:163-169 | crates/muxy-app-core/src/settings/commands.rs:58-64 — 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) crates/muxy-app/src/model/agents_panel.rs:584— crates/muxy-app/src/model/agents_panel.rs:584-590 | crates/muxy-app/src/model/floating.rs:47-54 — 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) crates/muxy-app/src/picker/path_service.rs:36— crates/muxy-app/src/picker/path_service.rs:36-42 | crates/muxy-core/src/paths.rs:59-65 — 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) crates/muxy-app-core/src/opener.rs:218— crates/muxy-app-core/src/opener.rs:218-224 | crates/muxy-ui/src/command_palette.rs:38-44 — 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.
muxy_server::connection::reader::run (cognitive 48) crates/muxy-server/src/connection/reader.rs:31— muxy_server::connection::reader::run has cognitive complexity 48 (threshold 15). Drivers by points: if/else 10 (32 pts), match/switch 4 (10 pts), boolean chains 5, loops 1 (nesting depth added 28). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_server::session::metadata::windows::split_command_line (cognitive 37) crates/muxy-server/src/session/metadata/windows.rs:118— muxy_server::session::metadata::windows::split_command_line has cognitive complexity 37 (threshold 15). Drivers by points: if/else 9 (21 pts), loops 5 (10 pts), boolean chains 3, match/switch 1 (3 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_server::git::processes::stop (cognitive 32) crates/muxy-server/src/git/processes.rs:15— muxy_server::git::processes::stop has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 7, loops 3 (6 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_server::git::mutate_files (cognitive 29) crates/muxy-server/src/git/mod.rs:416— muxy_server::git::mutate_files has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (20 pts), match/switch 2 (4 pts), boolean chains 3, loops 2 (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.
muxy_server::search::row_matches (cognitive 23) crates/muxy-server/src/search.rs:108— muxy_server::search::row_matches has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 4 (7 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_server::files::native::windows::names (cognitive 21) crates/muxy-server/src/files/native/windows.rs:394— muxy_server::files::native::windows::names has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (17 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_server::files::watch::watch (cognitive 21) crates/muxy-server/src/files/watch.rs:57— muxy_server::files::watch::watch has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 2, loops 1 (2 pts), match/switch 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.
muxy_server::git::diff::read (cognitive 19) crates/muxy-server/src/git/diff.rs:6— muxy_server::git::diff::read has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 3 (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.
muxy_server::git::details::log (cognitive 17) crates/muxy-server/src/git/details.rs:65— muxy_server::git::details::log has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 1, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Duplicated block (6 lines × 2) crates/muxy-app/src/model/extensions/consent.rs:260— crates/muxy-app/src/model/extensions/consent.rs:260-265 | crates/muxy-app/src/model/extensions/consent.rs:361-366 — 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 `crates/muxy-app/src/model/extensions/consent.rs:260` 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 `cx` to `&mut gpui::App` in one and `&mut Context<Self>` 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 (6 lines × 2) crates/muxy-app/src/model/project_apps.rs:229— crates/muxy-app/src/model/project_apps.rs:229-234 | crates/muxy-app/src/views/sidebar.rs:487-492 — 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 `crates/muxy-app/src/model/project_apps.rs:229` 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 `self` to `crate) fn open_project_apps_menu(&mut` in one and `crate) fn open_extensions_menu(&mut` 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 (6 lines × 2) crates/muxy-app/src/updater/macos.rs:184— crates/muxy-app/src/updater/macos.rs:184-189 | crates/muxy-app/src/updater/macos.rs:297-302 — 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 `crates/muxy-app/src/updater/macos.rs:184` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) crates/muxy-ui/src/dialog.rs:74— crates/muxy-ui/src/dialog.rs:74-79 | crates/muxy-ui/src/dialog.rs:193-198 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) crates/muxy-app/src/views/browser/mod.rs:773— crates/muxy-app/src/views/browser/mod.rs:773-778 | crates/muxy-app/src/views/webview/mod.rs:560-565 — `crates/muxy-app/src/views/browser/mod.rs` and `crates/muxy-app/src/views/webview/mod.rs` 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 5 separate duplicated blocks between them, totalling at least 50 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (6 lines × 2) crates/muxy-protocol/src/transport/tls.rs:59— crates/muxy-protocol/src/transport/tls.rs:59-64 | crates/muxy-server/src/remote/mod.rs:652-657 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) crates/muxy-client/src/catalog.rs:73— crates/muxy-client/src/catalog.rs:73-78 | crates/muxy-client/src/client.rs:164-169 — 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) crates/muxy-app/src/views/remote_servers.rs:370— crates/muxy-app/src/views/remote_servers.rs:370-375 | crates/muxy-app/src/views/servers_page.rs:664-669 — 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 `crates/muxy-app/src/views/remote_servers.rs:370` 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 `cx` to `&mut Context<AppModel>` in one and `&Context<AppModel>` 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 (6 lines × 2) crates/muxy-app/src/model/extensions/items.rs:133— crates/muxy-app/src/model/extensions/items.rs:133-138 | crates/muxy-app/src/model/extensions/items.rs:168-173 — 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 `crates/muxy-app/src/model/extensions/items.rs:133` 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.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×8
Edited copy of a member (10 corresponding lines) crates/muxy-app-core/src/settings/config.rs:218— crates/muxy-app-core/src/settings/config.rs:218-231 | crates/muxy-app-core/src/settings/config.rs:247-256 — 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) crates/muxy-app/src/views/onboarding/art/remote.rs:111— crates/muxy-app/src/views/onboarding/art/remote.rs:111-120 | crates/muxy-app/src/views/onboarding/art/server.rs:166-180 — 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) crates/muxy-app/src/views/sidebar/worktrees.rs:90— crates/muxy-app/src/views/sidebar/worktrees.rs:90-100 | crates/muxy-app/src/views/worktree_picker.rs:39-48 — 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) crates/muxy-app-core/src/browser/api.rs:39— crates/muxy-app-core/src/browser/api.rs:39-49 | crates/muxy-app-core/src/extensions/storage.rs:11-20 — 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) crates/muxy-app-core/src/state.rs:891— crates/muxy-app-core/src/state.rs:891-900 | crates/muxy-app-core/src/state.rs:908-917 — 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) crates/muxy-app-core/src/layout.rs:115— crates/muxy-app-core/src/layout.rs:115-124 | crates/muxy-app-core/src/layout.rs:126-136 — 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) crates/muxy-app/src/updater/macos.rs:478— crates/muxy-app/src/updater/macos.rs:478-490 | crates/muxy-app/src/updater/linux.rs:208-217 — 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) crates/muxy-app-core/src/project.rs:25— crates/muxy-app-core/src/project.rs:25-36 | crates/muxy-protocol/src/project.rs:251-260 — 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.
Duplicated block (12 lines × 2) crates/muxy-app/src/extensions/authoring.rs:268— crates/muxy-app/src/extensions/authoring.rs:268-279 | crates/muxy-app/src/extensions/authoring.rs:312-323 — 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 `crates/muxy-app/src/extensions/authoring.rs:268` 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) crates/muxy-app/src/extensions/io.rs:28— crates/muxy-app/src/extensions/io.rs:28-39 | crates/muxy-app/src/model/extensions/local.rs:88-99 — 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 `crates/muxy-app/src/extensions/io.rs:28` 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) crates/muxy-app/src/model/extensions/calls.rs:195— crates/muxy-app/src/model/extensions/calls.rs:195-206 | crates/muxy-app/src/model/extensions/calls.rs:268-279 — 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 `crates/muxy-app/src/model/extensions/calls.rs:195` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) crates/muxy-app/src/model/extensions/calls.rs:377— crates/muxy-app/src/model/extensions/calls.rs:377-388 | crates/muxy-app/src/model/extensions/calls.rs:500-511 — 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 `crates/muxy-app/src/model/extensions/calls.rs:377` 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 (12 lines × 2) crates/muxy-app/src/model/proxy.rs:94— crates/muxy-app/src/model/proxy.rs:94-105 | crates/muxy-app/src/model/remote_servers.rs:375-386 — 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 `crates/muxy-app/src/model/proxy.rs:94` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `self` to `super) fn sync_ssh_proxy(&mut` in one and `super) fn sync_servers(&mut` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/muxy-app/src/model/remote_servers.rs:374` calls `restart` and `crates/muxy-app/src/model/proxy.rs:93` 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 (12 lines × 2) crates/muxy-app/src/views/tab_sidebar.rs:734— crates/muxy-app/src/views/tab_sidebar.rs:734-745 | crates/muxy-app/src/views/tab_strip.rs:482-493 — 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 `crates/muxy-app/src/views/tab_sidebar.rs:734` 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) crates/muxy-app/src/views/terminal/scroll.rs:263— crates/muxy-app/src/views/terminal/scroll.rs:263-274 | crates/muxy-cli/src/scroll.rs:142-153 — 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 `crates/muxy-app/src/views/terminal/scroll.rs:263` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `self` to `&mut` in one and `crate) fn bottom(&mut` 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 (12 lines × 2) crates/muxy-app/src/views/pair_form.rs:69— crates/muxy-app/src/views/pair_form.rs:69-80 | crates/muxy-app/src/views/remote_servers.rs:776-787 — 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 `crates/muxy-app/src/views/pair_form.rs:69` 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 first that the copies are not typed on the same thing: the declarations holding them bind `self` to `crate) fn open_pair_form(&mut` in one and `crate) fn open_server_form(&mut` 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.
TooManyFields: AppModel crates/muxy-app/src/model.rs:136— TooManyFields — 109 stored fields beside 1361 methods. The bar is 30 stored fields; this is 79 over it, 3.63× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: TerminalPane crates/muxy-app/src/views/terminal/pane.rs:132— TooManyFields — 57 stored fields beside 114 methods. The bar is 30 stored fields; this is 27 over it, 1.90× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: Appearance crates/muxy-app-core/src/settings/appearance.rs:119— TooManyFields — 52 stored fields beside 6 methods. The bar is 30 stored fields; this is 22 over it, 1.73× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: TextInput crates/muxy-ui/src/text_input.rs:523— TooManyFields — 37 stored fields beside 97 methods. The bar is 30 stored fields; this is 7 over it, 1.23× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: SettingsView crates/muxy-app/src/views/settings/mod.rs:156— TooManyFields — 37 stored fields beside 84 methods. The bar is 30 stored fields; this is 7 over it, 1.23× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: Owner crates/muxy-server/src/session/owner.rs:83— TooManyFields — 36 stored fields beside 20 methods. The bar is 30 stored fields; this is 6 over it, 1.20× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: ExtensionsView crates/muxy-app/src/views/settings/extensions.rs:119— TooManyFields — 31 stored fields beside 86 methods. The bar is 30 stored fields; this is 1 over it, 1.03× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
Duplicated block (11 lines × 2) crates/muxy-app/src/model/client_access.rs:216— crates/muxy-app/src/model/client_access.rs:216-226 | crates/muxy-app/src/model/client_access.rs:387-397 — 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 `crates/muxy-app/src/model/client_access.rs:216` 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 `self` to `crate) fn switch_push_notifications(&mut` in one and `super) fn withdraw_pairing(&mut` 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 (11 lines × 2) crates/muxy-app/src/model/extensions/items.rs:390— crates/muxy-app/src/model/extensions/items.rs:390-400 | crates/muxy-app/src/model/extensions/items.rs:441-451 — 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 `crates/muxy-app/src/model/extensions/items.rs:390` 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 (11 lines × 2) crates/muxy-app/src/model/webviews.rs:1076— crates/muxy-app/src/model/webviews.rs:1076-1086 | crates/muxy-app/src/model/webviews.rs:1098-1108 — 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 `crates/muxy-app/src/model/webviews.rs:1076` 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, `crates/muxy-app/src/model/webviews.rs:1075` calls `clone` and `crates/muxy-app/src/model/webviews.rs:1097` 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) crates/muxy-app/src/views/remote_servers.rs:186— crates/muxy-app/src/views/remote_servers.rs:186-196 | crates/muxy-app/src/views/sidebar.rs:326-336 — 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 `crates/muxy-app/src/views/remote_servers.rs:186` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) crates/muxy-ui/src/dialog.rs:97— crates/muxy-ui/src/dialog.rs:97-107 | crates/muxy-ui/src/dialog.rs:209-219 — 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 `crates/muxy-ui/src/dialog.rs: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.
Duplicated block (11 lines × 2) crates/muxy-app/src/extensions/authoring.rs:288— crates/muxy-app/src/extensions/authoring.rs:288-298 | crates/muxy-app/src/extensions/authoring.rs:332-345 — 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 `crates/muxy-app/src/extensions/authoring.rs:288` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) crates/muxy-app/src/views/git/form.rs:123— crates/muxy-app/src/views/git/form.rs:123-133 | crates/muxy-app/src/views/git/form.rs:136-147 — 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 `crates/muxy-app/src/views/git/form.rs:136` 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.
AppState::validate (cognitive 42) crates/muxy-app-core/src/state.rs:1211— AppState::validate has cognitive complexity 42 (threshold 15). Drivers by points: if/else 15 (29 pts), boolean chains 8, loops 4 (5 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppState::restore_configuration (cognitive 37) crates/muxy-app-core/src/backup/projects.rs:110— AppState::restore_configuration has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (25 pts), loops 8 (11 pts), boolean chains 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.
AppState::merge_configuration (cognitive 22) crates/muxy-app-core/src/backup/projects.rs:258— AppState::merge_configuration has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (13 pts), match/switch 2 (5 pts), boolean chains 2, loops 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppState::merge_catalog (cognitive 17) crates/muxy-app-core/src/catalog.rs:276— AppState::merge_catalog has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (7 pts), boolean chains 5, loops 3, match/switch 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.
AppState::show_settings_tab (cognitive 17) crates/muxy-app-core/src/settings_tab.rs:55— AppState::show_settings_tab has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 2 (4 pts), boolean chains 3 (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.
AppState::move_pane_to (cognitive 17) crates/muxy-app-core/src/tab_windows.rs:522— AppState::move_pane_to has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), match/switch 3 (4 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.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×6
Edited copy of a member (12 corresponding lines) crates/muxy-app-core/src/extensions/audit.rs:56— crates/muxy-app-core/src/extensions/audit.rs:56-67 | crates/muxy-app/src/model/extensions/logs.rs:169-180 — 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) crates/muxy-app/src/updater/linux.rs:166— crates/muxy-app/src/updater/linux.rs:166-180 | crates/muxy-app/src/updater/macos.rs:505-516 — 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) crates/muxy-app/src/views/proxy.rs:372— crates/muxy-app/src/views/proxy.rs:372-384 | crates/muxy-app/src/views/remote_servers.rs:678-689 — 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) crates/muxy-ui/src/text_input.rs:352— crates/muxy-ui/src/text_input.rs:352-363 | crates/muxy-ui/src/text_input.rs:365-376 — 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) crates/muxy-app/src/views/settings/mod.rs:827— crates/muxy-app/src/views/settings/mod.rs:827-838 | crates/muxy-app/src/views/settings/terminal.rs:153-166 — 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) crates/muxy-client/src/client.rs:263— crates/muxy-client/src/client.rs:263-276 | crates/muxy-client/src/client.rs:474-485 — 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.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×6
Edited copy of a member (15 corresponding lines) crates/muxy-app/src/views/terminal/pane.rs:537— crates/muxy-app/src/views/terminal/pane.rs:537-556 | crates/muxy-app/src/views/terminal/pane.rs:559-573 — 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) crates/muxy-app/src/model/extensions/calls.rs:192— crates/muxy-app/src/model/extensions/calls.rs:192-206 | crates/muxy-app/src/model/extensions/calls.rs:257-279 — 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) crates/muxy-server/src/detection/regions.rs:73— crates/muxy-server/src/detection/regions.rs:73-87 | crates/muxy-server/src/detection/regions.rs:89-103 — 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) crates/muxy-app-core/src/browser/mod.rs:240— crates/muxy-app-core/src/browser/mod.rs:240-259 | crates/muxy-app-core/src/state.rs:770-784 — 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) crates/muxy-app/src/views/splits/drag.rs:147— crates/muxy-app/src/views/splits/drag.rs:147-161 | crates/muxy-app/src/views/splits/drag/target.rs:115-134 — 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) crates/muxy-app/src/model/extensions/mod.rs:464— crates/muxy-app/src/model/extensions/mod.rs:464-479 | crates/muxy-app/src/model/extensions/mod.rs:741-755 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×6
Edited copy of a member (13 corresponding lines) crates/muxy-app/src/views/workspace.rs:193— crates/muxy-app/src/views/workspace.rs:193-206 | crates/muxy-app/src/views/workspace.rs:208-220 — 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) crates/muxy-cli/src/input.rs:105— crates/muxy-cli/src/input.rs:105-117 | crates/muxy-mobile/src/keys.rs:108-122 — 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) crates/muxy-app-core/src/state.rs:998— crates/muxy-app-core/src/state.rs:998-1010 | crates/muxy-app-core/src/state.rs:1012-1024 — 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) crates/muxy-server/src/catalog/storage.rs:376— crates/muxy-server/src/catalog/storage.rs:376-388 | crates/muxy-server/src/catalog/storage.rs:392-404 — 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) crates/muxy-app-core/src/catalog.rs:408— crates/muxy-app-core/src/catalog.rs:408-421 | crates/muxy-protocol/src/path.rs:23-35 — 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) crates/muxy-mobile/src/git/worktrees.rs:33— crates/muxy-mobile/src/git/worktrees.rs:33-45 | crates/muxy-mobile/src/git/worktrees.rs:65-79 — 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 copy of a member (9 corresponding lines) · ×6
Edited copy of a member (9 corresponding lines) crates/muxy-app/src/views/browser/toolbar.rs:325— crates/muxy-app/src/views/browser/toolbar.rs:325-336 | crates/muxy-ui/src/components.rs:380-388 — 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) crates/muxy-app-core/src/layout/docking.rs:33— crates/muxy-app-core/src/layout/docking.rs:33-44 | crates/muxy-app-core/src/layout/docking.rs:55-63 — 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) crates/muxy-app-core/src/layout/docking.rs:339— crates/muxy-app-core/src/layout/docking.rs:339-347 | crates/muxy-app-core/src/layout/docking.rs:349-357 — 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) crates/muxy-core/src/process.rs:414— crates/muxy-core/src/process.rs:414-424 | crates/muxy-core/src/process.rs:466-474 — 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) crates/muxy-app/src/views/command_palette.rs:77— crates/muxy-app/src/views/command_palette.rs:77-88 | crates/muxy-app/src/views/command_palette.rs:101-109 — 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) crates/muxy-app-core/src/composer/storage/unix.rs:36— crates/muxy-app-core/src/composer/storage/unix.rs:36-44 | crates/muxy-server/src/files/native/unix.rs:58-66 — 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 (6 corresponding lines) · ×6
Edited copy of a member (6 corresponding lines) crates/muxy-app/src/model/activity.rs:517— crates/muxy-app/src/model/activity.rs:517-522 | crates/muxy-app/src/model/tab_windows.rs:517-523 — 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) crates/muxy-app-core/src/settings/proxy.rs:74— crates/muxy-app-core/src/settings/proxy.rs:74-81 | crates/muxy-app/src/backup/extensions.rs:193-198 — 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) crates/muxy-core/src/release.rs:104— crates/muxy-core/src/release.rs:104-109 | crates/muxy-protocol/src/remote.rs:374-379 — 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) crates/muxy-app-core/src/catalog.rs:85— crates/muxy-app-core/src/catalog.rs:85-91 | crates/muxy-app-core/src/servers.rs:197-202 — 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) crates/muxy-app/src/views/settings/ai.rs:21— crates/muxy-app/src/views/settings/ai.rs:21-26 | crates/muxy-cli/src/ui/mod.rs:167-173 — 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) crates/muxy-ui/src/javascript/jsc.rs:44— crates/muxy-ui/src/javascript/jsc.rs:44-49 | crates/muxy-ui/src/webview/linux.rs:27-32 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (9 lines × 2) crates/muxy-app-core/src/backup/projects.rs:429— crates/muxy-app-core/src/backup/projects.rs:429-437 | crates/muxy-app-core/src/backup/projects.rs:693-701 — 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 `crates/muxy-app-core/src/backup/projects.rs:429` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/muxy-app/src/model/project_layouts.rs:130— crates/muxy-app/src/model/project_layouts.rs:130-138 | crates/muxy-app/src/views/session_picker.rs:54-62 — 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 `crates/muxy-app/src/model/project_layouts.rs:130` 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 lines × 2) crates/muxy-app/src/views/settings/terminal_lists.rs:223— crates/muxy-app/src/views/settings/terminal_lists.rs:223-231 | crates/muxy-app/src/views/settings/terminal_lists.rs:314-322 — 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 `crates/muxy-app/src/views/settings/terminal_lists.rs:223` 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) crates/muxy-app/src/views/font_picker.rs:92— crates/muxy-app/src/views/font_picker.rs:92-100 | crates/muxy-ui/src/command_palette.rs:376-384 — 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 `crates/muxy-app/src/views/font_picker.rs:92` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/muxy-app/src/views/settings/terminal_lists.rs:235— crates/muxy-app/src/views/settings/terminal_lists.rs:235-243 | crates/muxy-app/src/views/settings/terminal_lists.rs:326-334 — 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 `crates/muxy-app/src/views/settings/terminal_lists.rs:235` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/muxy-app/src/views/proxy.rs:516— crates/muxy-app/src/views/proxy.rs:516-524 | crates/muxy-app/src/views/proxy.rs:531-539 — 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 `crates/muxy-app/src/views/proxy.rs:516` 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.
muxy_server::connection::reader::ordered_request (cyclomatic 46) crates/muxy-server/src/connection/reader.rs:336— muxy_server::connection::reader::ordered_request has cyclomatic complexity 46 (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.
muxy_server::connection::reader::run (cyclomatic 30) crates/muxy-server/src/connection/reader.rs:31— muxy_server::connection::reader::run 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.
muxy_server::git::mutate_files (cyclomatic 20) crates/muxy-server/src/git/mod.rs:416— muxy_server::git::mutate_files 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. This is NOT this file's highest cyclomatic complexity: Registry::dispatch_git (cyclomatic 21) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
muxy_server::git::processes::stop (cyclomatic 19) crates/muxy-server/src/git/processes.rs:15— muxy_server::git::processes::stop 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.
muxy_server::session::metadata::windows::split_command_line (cyclomatic 18) crates/muxy-server/src/session/metadata/windows.rs:118— muxy_server::session::metadata::windows::split_command_line 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.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×5
Edited copy of a member (11 corresponding lines) crates/muxy-app-core/src/state.rs:662— crates/muxy-app-core/src/state.rs:662-672 | crates/muxy-app-core/src/state.rs:689-706 — 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) crates/muxy-ui/src/components.rs:111— crates/muxy-ui/src/components.rs:111-121 | crates/muxy-ui/src/components.rs:594-606 — 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) crates/muxy-protocol/src/path.rs:39— crates/muxy-protocol/src/path.rs:39-51 | crates/muxy-protocol/src/path.rs:74-84 — 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) crates/muxy-app/src/model/extensions/checks.rs:59— crates/muxy-app/src/model/extensions/checks.rs:59-69 | crates/muxy-app/src/model/updates.rs:220-230 — 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) crates/muxy-cli/src/browser/mod.rs:64— crates/muxy-cli/src/browser/mod.rs:64-74 | crates/muxy-server/src/git/processes.rs:359-369 — 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.
Repeated repair: crates/muxy-ui/src/native_scroll.rs crates/muxy-ui/src/native_scroll.rs:184— crates/muxy-ui/src/native_scroll.rs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is NativeScrollView::sync at line 184), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Unify desktop UI helpers and fix menu sizing (#1338)”; “Fix github actions (#1143)”; “Fix terminal block rendering and edge padding”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-ui/src/native_scroll.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: crates/muxy-app/src/views/settings/extensions/configuration.rs crates/muxy-app/src/views/settings/extensions/configuration.rs:42— crates/muxy-app/src/views/settings/extensions/configuration.rs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is ExtensionsView::sync_setting_inputs at line 42), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Unify desktop UI helpers and fix menu sizing (#1338)”; “Fix github actions (#1143)”; “Extension follow-up: API parity fixes, extension settings, per-project panels (#1130)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-app/src/views/settings/extensions/configuration.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: crates/muxy-app-core/src/settings/ghostty/bindings.rs crates/muxy-app-core/src/settings/ghostty/bindings.rs:151— crates/muxy-app-core/src/settings/ghostty/bindings.rs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 15 (its worst body is TerminalAction::fmt at line 151), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(terminal): restore shortcuts and server-owned input”; “Expand terminal context menu and fix maximized pane frame”; “fix terminal issues”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-app-core/src/settings/ghostty/bindings.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: crates/muxy-ui/src/vibrancy.rs crates/muxy-ui/src/vibrancy.rs:49— crates/muxy-ui/src/vibrancy.rs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 2 (its worst body is SidebarVibrancy::set_width at line 49), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Unify desktop UI helpers and fix menu sizing (#1338)”; “Fix github actions (#1143)”; “Fix border consistency and theme-aware sidebar vibrancy”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 21:53:20 +01:00' --until='2026-11-14 21:53:20 +01:00' --full-history --no-merges -- crates/muxy-ui/src/vibrancy.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Registry::apply_worktree (cognitive 46) crates/muxy-server/src/git/worktree.rs:344— Registry::apply_worktree has cognitive complexity 46 (threshold 15). Drivers by points: if/else 18 (41 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Registry::reload (cognitive 17) crates/muxy-app-core/src/extensions/mod.rs:92— Registry::reload has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 2 (3 pts), match/switch 2 (3 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Registry::prepare_worktree_receipt (cognitive 17) crates/muxy-server/src/git/worktree.rs:135— Registry::prepare_worktree_receipt has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 1, match/switch 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.
Registry::git (cognitive 16) crates/muxy-server/src/git/mod.rs:109— Registry::git has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
TerminalPane::metadata (cognitive 26) crates/muxy-app/src/views/terminal/pane.rs:913— TerminalPane::metadata has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 4, 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.
TerminalPane::focus_changed (cognitive 21) crates/muxy-app/src/views/terminal/pane.rs:1117— TerminalPane::focus_changed has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (13 pts), loops 2 (6 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
TerminalPane::receive_history (cognitive 20) crates/muxy-app/src/views/terminal/pane.rs:758— TerminalPane::receive_history has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 7 (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.
TerminalPane::mouse_wheel (cognitive 16) crates/muxy-app/src/views/terminal/pane.rs:1237— TerminalPane::mouse_wheel has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 2, loops 1 (2 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.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×4
REDACTED
REDACTED
REDACTED
REDACTED
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×4
Edited copy of a member (17 corresponding lines) crates/muxy-cli/src/mobile.rs:96— crates/muxy-cli/src/mobile.rs:96-121 | crates/muxy-cli/src/mobile.rs:187-203 — 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) crates/muxy-protocol/src/validate.rs:469— crates/muxy-protocol/src/validate.rs:469-485 | crates/muxy-protocol/src/validate.rs:501-517 — 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) crates/muxy-mobile/src/channel.rs:134— crates/muxy-mobile/src/channel.rs:134-150 | crates/muxy-protocol/src/transport/stdio.rs:258-276 — 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) crates/muxy-core/src/files/windows.rs:186— crates/muxy-core/src/files/windows.rs:186-202 | crates/muxy-server/src/files/native/windows.rs:209-226 — 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.
Low cohesion: Settings (LCOM4 10) crates/muxy-app-core/src/extensions/storage.rs:147— Settings'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: CommandDef (LCOM4 4) crates/muxy-app/src/views/workspace/commands.rs:76— CommandDef'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: Settings (LCOM4 4) crates/muxy-app-core/src/settings/config.rs:12— Settings'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: TextInput (LCOM4 4) crates/muxy-ui/src/text_input.rs:523— TextInput'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.
TerminalPane::metadata (cyclomatic 23) crates/muxy-app/src/views/terminal/pane.rs:913— TerminalPane::metadata 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.
TerminalPane::receive_history (cyclomatic 18) crates/muxy-app/src/views/terminal/pane.rs:758— TerminalPane::receive_history 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.
TerminalPane::perform (cyclomatic 16) crates/muxy-app/src/views/terminal/pane.rs:1886— TerminalPane::perform 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.
BrowserView::handle (cyclomatic 20) crates/muxy-app/src/views/browser/mod.rs:242— BrowserView::handle 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.
BrowserView::present (cyclomatic 19) crates/muxy-app/src/views/browser/mod.rs:729— BrowserView::present 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.
BrowserView::page_event (cyclomatic 18) crates/muxy-app/src/views/browser/mod.rs:306— BrowserView::page_event 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.
SettingsView::refresh_results (cognitive 34) crates/muxy-app/src/views/settings/results.rs:162— SettingsView::refresh_results has cognitive complexity 34 (threshold 15). Drivers by points: if/else 16 (25 pts), boolean chains 4, loops 2 (4 pts), 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.
SettingsView::create_fields (cognitive 20) crates/muxy-app/src/views/settings/mod.rs:325— SettingsView::create_fields has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 4 (7 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SettingsView::categories (cognitive 19) crates/muxy-app/src/views/settings/layout.rs:102— SettingsView::categories has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Core::connected (cognitive 31) crates/muxy-cli/src/worker.rs:346— Core::connected has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (16 pts), match/switch 4 (9 pts), boolean chains 4, loops 2 (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.
Core::synchronize_pane (cognitive 21) crates/muxy-cli/src/worker.rs:721— Core::synchronize_pane has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (17 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Core::synchronize (cognitive 18) crates/muxy-cli/src/worker.rs:616— Core::synchronize has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (10 pts), match/switch 2 (5 pts), loops 3 (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.
muxy_app_core::backup::projects::import_worktrees (cognitive 24) crates/muxy-app-core/src/backup/projects.rs:672— muxy_app_core::backup::projects::import_worktrees has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 2 (3 pts), match/switch 1 (3 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.
muxy_app_core::backup::projects::import_projects (cognitive 22) crates/muxy-app-core/src/backup/projects.rs:416— muxy_app_core::backup::projects::import_projects has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 3, match/switch 1 (2 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_app_core::agent_sessions::parse::read (cognitive 17) crates/muxy-app-core/src/agent_sessions/parse.rs:27— muxy_app_core::agent_sessions::parse::read has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×3
Edited copy of a member (22 corresponding lines) crates/muxy-app/src/model/browsers/automation.rs:244— crates/muxy-app/src/model/browsers/automation.rs:244-265 | crates/muxy-app/src/model/extensions/pages.rs:367-388 — 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) crates/muxy-app/src/views/settings/extensions.rs:655— crates/muxy-app/src/views/settings/extensions.rs:655-676 | crates/muxy-app/src/views/settings/extensions.rs:700-725 — 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) crates/muxy-mobile/src/git/records.rs:256— crates/muxy-mobile/src/git/records.rs:256-281 | crates/muxy-server/src/archive/layout.rs:190-211 — 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) · ×3
Edited copy of a member (16 corresponding lines) crates/muxy-server/src/catalog/storage.rs:554— crates/muxy-server/src/catalog/storage.rs:554-573 | crates/muxy-server/src/catalog/storage.rs:577-592 — 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) crates/muxy-app/src/views/confirm.rs:60— crates/muxy-app/src/views/confirm.rs:60-75 | crates/muxy-app/src/views/project_menu.rs:316-331 — 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) crates/muxy-app/src/views/settings/appearance.rs:367— crates/muxy-app/src/views/settings/appearance.rs:367-385 | crates/muxy-app/src/views/settings/appearance.rs:411-426 — 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 (8 corresponding lines) · ×3
Edited copy of a member (8 corresponding lines) crates/muxy-ui/src/webview/linux/browser.rs:343— crates/muxy-ui/src/webview/linux/browser.rs:343-350 | crates/muxy-ui/src/webview/linux/browser.rs:357-364 — 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) crates/muxy-cli/src/state.rs:393— crates/muxy-cli/src/state.rs:393-402 | crates/muxy-cli/src/state.rs:407-414 — 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) crates/muxy-app-core/src/agent_sessions.rs:78— crates/muxy-app-core/src/agent_sessions.rs:78-85 | crates/muxy-app-core/src/extensions/manifest.rs:582-589 — 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 (5 corresponding lines) · ×3
Edited copy of a member (5 corresponding lines) crates/muxy-app/src/model/agent_sessions.rs:73— crates/muxy-app/src/model/agent_sessions.rs:73-82 | crates/muxy-app/src/model/project_apps.rs:96-100 — 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) crates/muxy-app-core/src/backup/legacy.rs:417— crates/muxy-app-core/src/backup/legacy.rs:417-422 | crates/muxy-app/src/opener.rs:470-474 — 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) crates/muxy-cli/src/manage/help/discovery.rs:15— crates/muxy-cli/src/manage/help/discovery.rs:15-19 | crates/muxy-ui/src/notifications/linux.rs:45-49 — 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.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×3
Edited copy of a member (4 corresponding lines) crates/muxy-app/src/views/browser/mod.rs:919— crates/muxy-app/src/views/browser/mod.rs:919-922 | crates/muxy-app/src/views/webview/mod.rs:637-642 — 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) crates/muxy-ui/src/webview/macos.rs:388— crates/muxy-ui/src/webview/macos.rs:388-391 | crates/muxy-ui/src/webview/mod.rs:207-210 — 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) crates/muxy-app-core/src/project_layouts.rs:247— crates/muxy-app-core/src/project_layouts.rs:247-250 | crates/muxy-ui/src/font.rs:65-68 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (14 lines × 2) crates/muxy-app/src/ai.rs:515— crates/muxy-app/src/ai.rs:515-528 | crates/muxy-app/src/extensions/io.rs:21-34 — 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 `crates/muxy-app/src/ai.rs:515` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) crates/muxy-app/src/model/webviews.rs:804— crates/muxy-app/src/model/webviews.rs:804-817 | crates/muxy-app/src/model/webviews.rs:1481-1494 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) crates/muxy-app/src/views/agent_sessions.rs:100— crates/muxy-app/src/views/agent_sessions.rs:100-113 | crates/muxy-app/src/views/webview/panel.rs:70-83 — 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 `crates/muxy-app/src/views/agent_sessions.rs:100` 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.
Metadata::visit (cyclomatic 35) crates/muxy-app-core/src/agent_sessions/parse.rs:110— Metadata::visit 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.
Metadata::update (cyclomatic 17) crates/muxy-server/src/session/metadata.rs:106— Metadata::update 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.
muxy_protocol::validate::validate_reply (cyclomatic 33) crates/muxy-protocol/src/validate.rs:325— muxy_protocol::validate::validate_reply has cyclomatic complexity 33 (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.
muxy_protocol::validate::validate_request (cyclomatic 32) crates/muxy-protocol/src/validate.rs:197— muxy_protocol::validate::validate_request 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.
AppState::validate (cyclomatic 28) crates/muxy-app-core/src/state.rs:1211— AppState::validate has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AppState::restore_configuration (cyclomatic 20) crates/muxy-app-core/src/backup/projects.rs:110— AppState::restore_configuration 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.
SettingsView::refresh_results (cyclomatic 26) crates/muxy-app/src/views/settings/results.rs:162— SettingsView::refresh_results 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.
SettingsView::create_fields (cyclomatic 16) crates/muxy-app/src/views/settings/mod.rs:325— SettingsView::create_fields 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.
Running::wait (cyclomatic 26) crates/muxy-core/src/process/windows.rs:101— Running::wait has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
Running::wait (cyclomatic 23) crates/muxy-core/src/process.rs:187— Running::wait 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.
muxy_mobile::keys::encode (cyclomatic 25) crates/muxy-mobile/src/keys.rs:41— muxy_mobile::keys::encode has cyclomatic complexity 25 (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.
muxy_mobile::connection::deliver (cyclomatic 21) crates/muxy-mobile/src/connection.rs:404— muxy_mobile::connection::deliver has cyclomatic complexity 21 (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.
TextElement::prepaint (cyclomatic 25) crates/muxy-ui/src/text_input.rs:1849— TextElement::prepaint 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.
TextElement::paint (cyclomatic 16) crates/muxy-ui/src/text_input.rs:2092— TextElement::paint 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.
muxy_ui::webview::linux::page::keyval (cyclomatic 24) crates/muxy-ui/src/webview/linux/page.rs:1422— muxy_ui::webview::linux::page::keyval has cyclomatic complexity 24 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
muxy_ui::webview::host::monitor (cyclomatic 18) crates/muxy-ui/src/webview/host.rs:781— muxy_ui::webview::host::monitor 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.
Webview::present (cyclomatic 17) crates/muxy-app/src/views/webview/mod.rs:463— Webview::present 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.
Webview::handle (cyclomatic 16) crates/muxy-app/src/views/webview/mod.rs:276— Webview::handle 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.
TextElement::prepaint (cognitive 47) crates/muxy-ui/src/text_input.rs:1849— TextElement::prepaint has cognitive complexity 47 (threshold 15). Drivers by points: if/else 27 (41 pts), boolean chains 3, loops 1 (2 pts), match/switch 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.
TextElement::paint (cognitive 18) crates/muxy-ui/src/text_input.rs:2092— TextElement::paint has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 5, loops 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Metadata::visit (cognitive 43) crates/muxy-app-core/src/agent_sessions/parse.rs:110— Metadata::visit has cognitive complexity 43 (threshold 15). Drivers by points: if/else 17 (28 pts), boolean chains 11, loops 1 (3 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.
Metadata::update (cognitive 25) crates/muxy-server/src/session/metadata.rs:106— Metadata::update has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Running::wait (cognitive 35) crates/muxy-core/src/process/windows.rs:101— Running::wait has cognitive complexity 35 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 11, match/switch 4 (10 pts), loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Running::wait (cognitive 32) crates/muxy-core/src/process.rs:187— Running::wait has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 10, 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.
Catalog::scan (cognitive 30) crates/muxy-app-core/src/agent_sessions/files.rs:78— Catalog::scan has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (20 pts), match/switch 1 (4 pts), boolean chains 3, loops 2 (3 pts) (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.
Catalog::begin_mutation (cognitive 25) crates/muxy-server/src/catalog/mutations.rs:5— Catalog::begin_mutation has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 2, match/switch 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.
Terminal::history_with_metadata (cognitive 27) crates/muxy-terminal/src/ghostty.rs:854— Terminal::history_with_metadata has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (21 pts), loops 5 (6 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Terminal::encode_mouse (cognitive 18) crates/muxy-terminal/src/ghostty.rs:551— Terminal::encode_mouse has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), match/switch 4 (7 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.
ExtensionsView::render (cognitive 22) crates/muxy-app/src/views/settings/extensions.rs:847— ExtensionsView::render has cognitive complexity 22 (threshold 15). Drivers by points: if/else 17 (20 pts), loops 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.
ExtensionsView::change_extension (cognitive 18) crates/muxy-app/src/views/settings/extensions.rs:526— ExtensionsView::change_extension has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), match/switch 4 (6 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_protocol::validate::validate_reply (cognitive 22) crates/muxy-protocol/src/validate.rs:325— muxy_protocol::validate::validate_reply has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 5, loops 1 (2 pts), match/switch 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
muxy_protocol::validate::validate_request (cognitive 21) crates/muxy-protocol/src/validate.rs:197— muxy_protocol::validate::validate_request has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 1, 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.
muxy_ui::webview::host::monitor (cognitive 20) crates/muxy-ui/src/webview/host.rs:781— muxy_ui::webview::host::monitor has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 4 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
muxy_ui::quick_terminal::platform::linux::shortcut::registrations (cognitive 16) crates/muxy-ui/src/quick_terminal/platform/linux/shortcut.rs:263— muxy_ui::quick_terminal::platform::linux::shortcut::registrations has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 3 (4 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous)::restore (cognitive 19) crates/muxy-app-core/src/browser/element_picker.js:5— (anonymous)::restore has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous)::open (cognitive 17) crates/muxy-app/src/views/webview/bridge.js:166— (anonymous)::open has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 3, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
TooManyFunctions: muxy_app::views::workspace::commands::available crates/muxy-app/src/views/workspace/commands/available.rs:8— TooManyFunctions — 42 free functions. The bar is 30 free functions; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyFunctions: muxy_server::files::native::windows crates/muxy-server/src/files/native/windows.rs:58— TooManyFunctions — 32 free functions. The bar is 30 free functions; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×2
Change coupling: keymap.rs ↔ model.rs crates/muxy-app-core/src/settings/keymap.rs:1— `crates/muxy-app-core/src/settings/keymap.rs` and `crates/muxy-app/src/model.rs` change together 69% of the time (9 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `6b2b3421` Preserve ended session output and fix Linux worktree shortcuts (#1259); `06befaa6` Add folder search and path completion to New Tab in Project (#1248); `596301a5` Add project-scoped agent session browsing and resume support (#1225) — run `git show` on any of them.
Change coupling: keymap.rs ↔ main.rs crates/muxy-app-core/src/settings/keymap.rs:1— `crates/muxy-app-core/src/settings/keymap.rs` and `crates/muxy-app/src/main.rs` change together 62% of the time (8 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `06befaa6` Add folder search and path completion to New Tab in Project (#1248); `596301a5` Add project-scoped agent session browsing and resume support (#1225); `98d56b54` feat(agents): Add agents panel and vibrancy for project panel (#1209) — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (49 corresponding lines) · ×2
Edited copy of a member (49 corresponding lines) crates/muxy-app/src/views/browser/mod.rs:784— crates/muxy-app/src/views/browser/mod.rs:784-832 | crates/muxy-app/src/views/webview/mod.rs:567-615 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (49 corresponding lines) crates/muxy-app/src/views/settings/extensions/cards.rs:294— crates/muxy-app/src/views/settings/extensions/cards.rs:294-354 | crates/muxy-app/src/views/settings/extensions/detail.rs:288-336 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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) · ×2
Edited copy of a member (39 corresponding lines) crates/muxy-ui/src/dialog.rs:73— crates/muxy-ui/src/dialog.rs:73-118 | crates/muxy-ui/src/dialog.rs:192-230 — 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.
Edited copy of a member (39 corresponding lines) crates/muxy-server/src/catalog/storage.rs:292— crates/muxy-server/src/catalog/storage.rs:292-330 | crates/muxy-server/src/catalog/storage.rs:334-372 — 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 (31 corresponding lines) · ×2
Edited copy of a member (31 corresponding lines) crates/muxy-server/src/shell.rs:105— crates/muxy-server/src/shell.rs:105-135 | crates/muxy-server/src/uploads.rs:68-103 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (31 corresponding lines) crates/muxy-app/src/views/composer/layout.rs:624— crates/muxy-app/src/views/composer/layout.rs:624-654 | crates/muxy-app/src/views/move_drag.rs:1006-1040 — 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 (29 corresponding lines) · ×2
Edited copy of a member (29 corresponding lines) crates/muxy-app/src/views/clients.rs:207— crates/muxy-app/src/views/clients.rs:207-237 | crates/muxy-app/src/views/clients.rs:246-274 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (29 corresponding lines) crates/muxy-app/src/views/browser/mod.rs:1036— crates/muxy-app/src/views/browser/mod.rs:1036-1069 | crates/muxy-app/src/views/webview/mod.rs:806-834 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×2
Edited copy of a member (21 corresponding lines) crates/muxy-app-core/src/settings/keys.rs:73— crates/muxy-app-core/src/settings/keys.rs:73-93 | crates/muxy-app-core/src/settings/keys.rs:96-122 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (21 corresponding lines) crates/muxy-app/src/extensions/authoring.rs:175— crates/muxy-app/src/extensions/authoring.rs:175-198 | crates/muxy-app/src/extensions/authoring.rs:233-253 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (20 corresponding lines) · ×2
Edited copy of a member (20 corresponding lines) crates/muxy-app/src/model/browsers/mod.rs:534— crates/muxy-app/src/model/browsers/mod.rs:534-554 | crates/muxy-app/src/views/settings/extensions.rs:679-698 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) crates/muxy-app/src/model/catalog.rs:319— crates/muxy-app/src/model/catalog.rs:319-338 | crates/muxy-app/src/model/catalog.rs:345-369 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×2
Edited copy of a member (19 corresponding lines) crates/muxy-app/src/views/settings/appearance.rs:336— crates/muxy-app/src/views/settings/appearance.rs:336-364 | crates/muxy-app/src/views/settings/appearance.rs:389-407 — 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) crates/muxy-server/src/catalog/storage.rs:596— crates/muxy-server/src/catalog/storage.rs:596-617 | crates/muxy-server/src/catalog/storage.rs:621-639 — 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, 11+ corresponding lines) · ×2
Edited copies of one member (3 members, 11+ corresponding lines) crates/muxy-server/src/connection/reader.rs:651— crates/muxy-server/src/connection/reader.rs:651-669 | crates/muxy-server/src/connection/reader.rs:676-686 | crates/muxy-server/src/connection/reader.rs:695-714 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 11+ corresponding lines) crates/muxy-ui/src/panel.rs:401— crates/muxy-ui/src/panel.rs:401-411 | crates/muxy-ui/src/panel.rs:419-429 | crates/muxy-ui/src/panel.rs:455-465 — 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 copies of one member (3 members, 13+ corresponding lines) · ×2
Edited copies of one member (3 members, 13+ corresponding lines) crates/muxy-app/src/model/webviews.rs:1034— crates/muxy-app/src/model/webviews.rs:1034-1046 | crates/muxy-app/src/model/webviews.rs:1050-1064 | crates/muxy-app/src/model/webviews.rs:1095-1108 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 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, 13+ corresponding lines) crates/muxy-app/src/model/server_status.rs:89— crates/muxy-app/src/model/server_status.rs:89-101 | crates/muxy-app/src/model/updates/status.rs:180-192 | crates/muxy-app/src/views/remote_servers.rs:706-718 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 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 (8–9 lines × 2) crates/muxy-app/src/views/remote_servers.rs:1418— crates/muxy-app/src/views/remote_servers.rs:1418-1426 | crates/muxy-app/src/views/remote_servers.rs:1464-1471 — 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 `crates/muxy-app/src/views/remote_servers.rs:1418` 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–9 lines × 2) crates/muxy-app/src/updater/linux.rs:92— crates/muxy-app/src/updater/linux.rs:92-99 | crates/muxy-app/src/updater/macos.rs:133-141 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 4) crates/muxy-app/src/views/agents_panel.rs:1104— crates/muxy-app/src/views/agents_panel.rs:1104-1109 | crates/muxy-app/src/views/floating.rs:86-91 | crates/muxy-app/src/views/move_drag.rs:1027-1032 | crates/muxy-app/src/views/splits/drag.rs:488-493 — 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 `crates/muxy-app/src/views/agents_panel.rs:1104` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `cx` to `&mut Context<AppModel>` in one and `&Context<AppModel>` 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 (6 lines × 4) crates/muxy-app/src/views/agents_panel.rs:1105— crates/muxy-app/src/views/agents_panel.rs:1105-1110 | crates/muxy-app/src/views/floating.rs:87-92 | crates/muxy-app/src/views/splits/drag.rs:489-494 | crates/muxy-app/src/views/tab_strip/drag.rs:387-392 — 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 `crates/muxy-app/src/views/agents_panel.rs:1105` 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 `cx` to `&mut Context<AppModel>` in one and `&Context<AppModel>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/muxy-app/src/views/tab_strip/drag.rs:386` calls `clone` and `crates/muxy-app/src/views/agents_panel.rs:1104` 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.
Off the main sequence: muxy-core — muxy-core: abstractness 0.02, instability 0.00, distance 0.98 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
Off the main sequence: muxy-protocol — muxy-protocol: abstractness 0.03, instability 0.13, distance 0.84 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
(anonymous) (cyclomatic 177) crates/muxy-app/src/extensions/bridge.js:1— (anonymous) has cyclomatic complexity 177 (threshold 15). Most of this is not in the body itself: 12 of the 177 points are its own statements and the rest belongs to 211 function items inside it that branch (execPayload, open, openWebview, …). 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.
(anonymous) (cyclomatic 116) crates/muxy-app/src/views/webview/bridge.js:1— (anonymous) has cyclomatic complexity 116 (threshold 15). Most of this is not in the body itself: 9 of the 116 points are its own statements and the rest belongs to 83 function items inside it that branch (open, trackHitElements::elements, format, …). 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.
TerminalOptions::read (cyclomatic 45) crates/muxy-app-core/src/settings/ghostty/options.rs:280— TerminalOptions::read has cyclomatic complexity 45 (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.
Picker::render_item (cyclomatic 35) crates/muxy-ui/src/picker.rs:1094— Picker::render_item 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.
(anonymous) (cyclomatic 32) crates/muxy-app-core/src/browser/element_picker.js:1— (anonymous) has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 3 of the 32 points are its own statements and the rest belongs to 16 function items inside it that branch (restore, finish, a function literal at line 61, …). 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.
Owner::serve (cyclomatic 31) crates/muxy-server/src/session/owner.rs:283— Owner::serve has cyclomatic complexity 31 (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.
TerminalSettings::read_source (cyclomatic 27) crates/muxy-app-core/src/settings/ghostty.rs:255— TerminalSettings::read_source 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.
GitRequest::validate (cyclomatic 26) crates/muxy-protocol/src/git.rs:460— GitRequest::validate has cyclomatic complexity 26 (threshold 15). Of this number, 23 points are the body's own statements and 3 belong to 2 function items inside it that branch. 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.
FontOptions::read (cyclomatic 24) crates/muxy-app-core/src/settings/ghostty/fonts.rs:81— FontOptions::read 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.
Requests::route (cyclomatic 24) crates/muxy-server/src/connection/reader.rs:167— Requests::route 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.
muxy_client::bridge::explain (cyclomatic 23) crates/muxy-client/src/bridge.rs:289— muxy_client::bridge::explain has cyclomatic complexity 23 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
Registry::apply_worktree (cyclomatic 23) crates/muxy-server/src/git/worktree.rs:344— Registry::apply_worktree 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.
(anonymous) (cyclomatic 23) crates/muxy-app/src/extensions/script.js:1— (anonymous) 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 11 function items inside it that branch (__muxyTick, format, schedule, …). 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.
Frame::extend_row (cyclomatic 22) crates/muxy-app/src/views/terminal/element/padding.rs:76— Frame::extend_row has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
State::validate (cyclomatic 22) crates/muxy-cli/src/state.rs:416— State::validate has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Message::validate (cyclomatic 22) crates/muxy-protocol/src/validate.rs:103— Message::validate has cyclomatic complexity 22 (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.
Router::next (cyclomatic 21) crates/muxy-client/src/events.rs:168— Router::next has cyclomatic complexity 21 (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.
Pointer::press (cyclomatic 20) crates/muxy-cli/src/tui/mouse.rs:117— Pointer::press 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.
ProjectPicker::sync_picker (cyclomatic 19) crates/muxy-app/src/views/project_picker.rs:365— ProjectPicker::sync_picker 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.
Core::connected (cyclomatic 19) crates/muxy-cli/src/worker.rs:346— Core::connected 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.
Binary::value (cyclomatic 17) crates/muxy-app-core/src/localization/plist/binary.rs:76— Binary::value 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.
Keymap::from_overrides (cyclomatic 17) crates/muxy-app-core/src/settings/keymap.rs:228— Keymap::from_overrides 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.
Keys::report (cyclomatic 17) crates/muxy-cli/src/status.rs:79— Keys::report 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.
Catalog::begin_mutation (cyclomatic 17) crates/muxy-server/src/catalog/mutations.rs:5— Catalog::begin_mutation 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.
Github::lookup_current (cyclomatic 17) crates/muxy-server/src/git/github/pull_requests.rs:297— Github::lookup_current 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.
ExtensionsView::render (cyclomatic 16) crates/muxy-app/src/views/settings/extensions.rs:847— ExtensionsView::render 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.
SettingsTab::open_picker (cyclomatic 16) crates/muxy-app/src/views/settings/tab.rs:165— SettingsTab::open_picker 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.
KeyChord::from_str (cyclomatic 16) crates/muxy-app-core/src/settings/chord.rs:24— KeyChord::from_str 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.
muxy_core::l10n::format::write_argument (cyclomatic 16) crates/muxy-core/src/l10n/format.rs:226— muxy_core::l10n::format::write_argument 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.
Terminal::encode_mouse (cyclomatic 16) crates/muxy-terminal/src/ghostty.rs:551— Terminal::encode_mouse 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.
(anonymous) (cognitive 217) crates/muxy-app/src/extensions/bridge.js:1— (anonymous) has cognitive complexity 217 (threshold 15). Drivers by points: boolean chains 75, if/else 51 (68 pts), ternaries 35 (46 pts), error handling 8 (17 pts), loops 6 (9 pts), other 2 (nesting depth added 40). Of this number, 16 points are the body's own statements and 201 belong to 211 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Picker::render_item (cognitive 82) crates/muxy-ui/src/picker.rs:1094— Picker::render_item has cognitive complexity 82 (threshold 15). Drivers by points: if/else 34 (68 pts), boolean chains 7, loops 2 (6 pts), match/switch 1 (nesting depth added 38). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Frame::extend_row (cognitive 45) crates/muxy-app/src/views/terminal/element/padding.rs:76— Frame::extend_row has cognitive complexity 45 (threshold 15). Drivers by points: if/else 15 (32 pts), boolean chains 9, loops 2 (4 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Requests::route (cognitive 38) crates/muxy-server/src/connection/reader.rs:167— Requests::route has cognitive complexity 38 (threshold 15). Drivers by points: if/else 14 (24 pts), match/switch 7 (14 pts) (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.
FontOptions::read (cognitive 34) crates/muxy-app-core/src/settings/ghostty/fonts.rs:81— FontOptions::read has cognitive complexity 34 (threshold 15). Drivers by points: if/else 15 (26 pts), loops 2 (4 pts), boolean chains 2, match/switch 2 (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.
State::validate (cognitive 34) crates/muxy-cli/src/state.rs:416— State::validate has cognitive complexity 34 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 9, loops 4 (7 pts), match/switch 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TerminalSettings::read_source (cognitive 32) crates/muxy-app-core/src/settings/ghostty.rs:255— TerminalSettings::read_source has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 6, match/switch 2 (4 pts), loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Root::resolve (cognitive 27) crates/muxy-server/src/files/root.rs:38— Root::resolve has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (24 pts), boolean chains 2, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProjectPicker::sync_picker (cognitive 25) crates/muxy-app/src/views/project_picker.rs:365— ProjectPicker::sync_picker has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (19 pts), match/switch 3 (4 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous) (cognitive 25) crates/muxy-app/src/extensions/script.js:1— (anonymous) has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 7, error handling 2 (3 pts), loops 2, ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 11 function items inside it that branch (__muxyTick, format, schedule, …). 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.
OldStyle::skip (cognitive 24) crates/muxy-app-core/src/localization/plist.rs:192— OldStyle::skip has cognitive complexity 24 (threshold 15). Drivers by points: match/switch 3 (10 pts), loops 3 (9 pts), if/else 1 (5 pts) (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.
Keys::report (cognitive 24) crates/muxy-cli/src/status.rs:79— Keys::report has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (21 pts), boolean chains 2, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CachedRow::refresh (cognitive 24) crates/muxy-terminal/src/links.rs:36— CachedRow::refresh has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 3, match/switch 1 (3 pts), loops 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Dialog::render (cognitive 24) crates/muxy-ui/src/dialog/view.rs:155— Dialog::render has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 3 (4 pts), boolean chains 1, match/switch 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Keymap::from_overrides (cognitive 23) crates/muxy-app-core/src/settings/keymap.rs:228— Keymap::from_overrides has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 7, loops 4 (5 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.
SessionList::rebuild (cognitive 22) crates/muxy-app/src/model/agent_sessions/list.rs:60— SessionList::rebuild has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (16 pts), match/switch 1 (3 pts), boolean chains 2, 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.
Owner::update_metadata (cognitive 22) crates/muxy-server/src/session/owner.rs:733— Owner::update_metadata has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (17 pts), match/switch 1 (3 pts), loops 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.
BrowserView::present (cognitive 21) crates/muxy-app/src/views/browser/mod.rs:729— BrowserView::present has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 10 (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.
Textures::prepare (cognitive 21) crates/muxy-app/src/views/terminal/element/images.rs:303— Textures::prepare has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 3 (6 pts), boolean chains 3 (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.
Player::advance (cognitive 21) crates/muxy-app/src/views/terminal/element/images.rs:400— Player::advance has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 3, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Target::file (cognitive 21) crates/muxy-app-core/src/opener.rs:64— Target::file has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Appearance::save_changes (cognitive 21) crates/muxy-app-core/src/settings/appearance.rs:287— Appearance::save_changes has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 7 (8 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.
muxy_client::bridge::explain (cognitive 21) crates/muxy-client/src/bridge.rs:289— muxy_client::bridge::explain has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10, boolean chains 8, match/switch 2 (3 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Webview::present (cognitive 20) crates/muxy-app/src/views/webview/mod.rs:463— Webview::present has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 7 (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.
TerminalOptions::read (cognitive 20) crates/muxy-app-core/src/settings/ghostty/options.rs:280— TerminalOptions::read has cognitive complexity 20 (threshold 15). Drivers by points: match/switch 5 (10 pts), if/else 4 (6 pts), loops 2 (4 pts) (nesting depth added 9). 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.
Display::help (cognitive 20) crates/muxy-cli/src/output.rs:49— Display::help has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (12 pts), boolean chains 4, loops 2 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_terminal::graphics::sixel::paint (cognitive 20) crates/muxy-terminal/src/graphics/sixel.rs:163— muxy_terminal::graphics::sixel::paint has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (7 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Paths::paint (cognitive 19) crates/muxy-app/src/views/terminal/element/layers.rs:47— Paths::paint has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 3 (7 pts), match/switch 1 (2 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.
Scroll::receive (cognitive 19) crates/muxy-app/src/views/terminal/scroll.rs:228— Scroll::receive has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 2, match/switch 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.
muxy_mobile::connection::deliver (cognitive 19) crates/muxy-mobile/src/connection.rs:404— muxy_mobile::connection::deliver has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 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.
QuickTerminalView::render (cognitive 18) crates/muxy-app/src/views/quick_terminal.rs:213— QuickTerminalView::render has cognitive complexity 18 (threshold 15). Drivers by points: if/else 17, 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.
SettingsTab::open_picker (cognitive 18) crates/muxy-app/src/views/settings/tab.rs:165— SettingsTab::open_picker has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RowRenderer::row (cognitive 18) crates/muxy-app/src/views/terminal/element.rs:516— RowRenderer::row has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Github::lookup_current (cognitive 18) crates/muxy-server/src/git/github/pull_requests.rs:297— Github::lookup_current has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (10 pts), match/switch 5 (7 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.
Editor::command (cognitive 17) crates/muxy-app/src/opener.rs:418— Editor::command has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (16 pts), match/switch 1 (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.
ComposerStore::attach_prepared_image (cognitive 17) crates/muxy-app-core/src/composer/draft.rs:329— ComposerStore::attach_prepared_image has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), match/switch 2 (4 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Node::dock (cognitive 17) crates/muxy-app-core/src/layout/docking.rs:174— Node::dock has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), match/switch 3 (4 pts), boolean chains 2, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Project::sync_groups (cognitive 17) crates/muxy-app-core/src/groups.rs:207— Project::sync_groups has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 4, loops 4 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GitRequest::validate (cognitive 17) crates/muxy-protocol/src/git.rs:460— GitRequest::validate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 3, match/switch 2 (3 pts) (nesting depth added 5). Of this number, 13 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Page::pointer_target (cognitive 17) crates/muxy-ui/src/webview/linux/page/input.rs:33— Page::pointer_target has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 2, match/switch 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Options::parse (cognitive 16) crates/muxy-cli/src/manage/args.rs:607— Options::parse has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 2, 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.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) crates/muxy-app/src/views/settings/tab.rs:264— crates/muxy-app/src/views/settings/tab.rs:264-304 | crates/muxy-app/src/views/settings/tab.rs:313-362 | crates/muxy-app/src/views/settings/tab.rs:369-444 | crates/muxy-app/src/views/settings/tab.rs:453-502 | crates/muxy-app/src/views/settings/tab.rs:510-553 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Edited copy of a member (93 corresponding lines) · ×1
Edited copy of a member (93 corresponding lines) crates/muxy-ui/src/icon/mod.rs:108— crates/muxy-ui/src/icon/mod.rs:108-201 | crates/muxy-ui/src/icon/mod.rs:296-388 — These two members are one piece of code written twice and then edited apart: 93 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (66 corresponding lines) · ×1
Edited copy of a member (66 corresponding lines) crates/muxy-cli/src/input.rs:29— crates/muxy-cli/src/input.rs:29-103 | crates/muxy-mobile/src/keys.rs:41-106 — These two members are one piece of code written twice and then edited apart: 66 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (77 corresponding lines) · ×1
Edited copy of a member (77 corresponding lines) crates/muxy-app/src/views/browser/toolbar.rs:433— crates/muxy-app/src/views/browser/toolbar.rs:433-511 | crates/muxy-app/src/views/terminal/find.rs:421-497 — These two members are one piece of code written twice and then edited apart: 77 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (56 corresponding lines) · ×1
Edited copy of a member (56 corresponding lines) crates/muxy-app/src/views/settings/terminal_lists.rs:211— crates/muxy-app/src/views/settings/terminal_lists.rs:211-266 | crates/muxy-app/src/views/settings/terminal_lists.rs:298-364 — These two members are one piece of code written twice and then edited apart: 56 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (52 corresponding lines) · ×1
Edited copy of a member (52 corresponding lines) crates/muxy-app/src/views/server_status.rs:58— crates/muxy-app/src/views/server_status.rs:58-109 | crates/muxy-app/src/views/status_bar.rs:86-149 — These two members are one piece of code written twice and then edited apart: 52 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (35 corresponding lines) · ×1
Edited copy of a member (35 corresponding lines) crates/muxy-app/src/model/client_access.rs:215— crates/muxy-app/src/model/client_access.rs:215-251 | crates/muxy-app/src/model/client_access.rs:386-420 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 41+ corresponding lines) · ×1
Edited copies of one member (3 members, 41+ corresponding lines) crates/muxy-app/src/views/agents_panel.rs:1083— crates/muxy-app/src/views/agents_panel.rs:1083-1123 | crates/muxy-app/src/views/floating.rs:65-105 | crates/muxy-app/src/views/splits/drag.rs:457-506 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 41 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (34 corresponding lines) · ×1
Edited copy of a member (34 corresponding lines) crates/muxy-app/src/extensions/authoring.rs:265— crates/muxy-app/src/extensions/authoring.rs:265-298 | crates/muxy-app/src/extensions/authoring.rs:309-345 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (43 corresponding lines) · ×1
Edited copy of a member (43 corresponding lines) crates/muxy-app/src/views/settings/commands.rs:56— crates/muxy-app/src/views/settings/commands.rs:56-98 | crates/muxy-app/src/views/settings/files.rs:90-136 — 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 (51 corresponding lines) · ×1
Edited copy of a member (51 corresponding lines) crates/muxy-app/src/views/onboarding/steps.rs:245— crates/muxy-app/src/views/onboarding/steps.rs:245-300 | crates/muxy-app/src/views/onboarding/steps.rs:567-617 — These two members are one piece of code written twice and then edited apart: 51 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) crates/muxy-ui/src/icon/raster.rs:75— crates/muxy-ui/src/icon/raster.rs:75-118 | crates/muxy-ui/src/icon/raster.rs:128-163 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 20+ corresponding lines) · ×1
Edited copies of one member (3 members, 20+ corresponding lines) crates/muxy-app/src/model/webviews.rs:884— crates/muxy-app/src/model/webviews.rs:884-903 | crates/muxy-app/src/model/webviews/panels.rs:1164-1194 | crates/muxy-app/src/model/webviews/popover.rs:124-153 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (33 corresponding lines) · ×1
Edited copy of a member (33 corresponding lines) crates/muxy-app/src/views/sidebar/worktrees.rs:107— crates/muxy-app/src/views/sidebar/worktrees.rs:107-141 | crates/muxy-app/src/views/tab_sidebar.rs:579-611 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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, 29+ corresponding lines) · ×1
Edited copies of one member (4 members, 29+ corresponding lines) crates/muxy-app/src/views/settings/appearance.rs:428— crates/muxy-app/src/views/settings/appearance.rs:428-456 | crates/muxy-app/src/views/settings/appearance.rs:458-486 | crates/muxy-app/src/views/settings/appearance.rs:488-516 | crates/muxy-app/src/views/settings/appearance.rs:552-580 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 29 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×1
Edited copy of a member (26 corresponding lines) crates/muxy-app/src/model/extensions/mod.rs:856— crates/muxy-app/src/model/extensions/mod.rs:856-881 | crates/muxy-app/src/model/webviews.rs:394-421 — 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 copies of one member (3 members, 24+ corresponding lines) · ×1
Edited copies of one member (3 members, 24+ corresponding lines) crates/muxy-app/src/ai.rs:510— crates/muxy-app/src/ai.rs:510-533 | crates/muxy-app/src/extensions/io.rs:16-39 | crates/muxy-app/src/model/extensions/local.rs:76-99 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×1
Edited copy of a member (24 corresponding lines) crates/muxy-app/src/model.rs:1125— crates/muxy-app/src/model.rs:1125-1148 | crates/muxy-app/src/model.rs:1474-1498 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×1
Edited copy of a member (27 corresponding lines) crates/muxy-app/src/views/onboarding/steps.rs:728— crates/muxy-app/src/views/onboarding/steps.rs:728-756 | crates/muxy-app/src/views/tips.rs:64-90 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×1
Edited copy of a member (25 corresponding lines) crates/muxy-app/src/model.rs:2473— crates/muxy-app/src/model.rs:2473-2497 | crates/muxy-app/src/model.rs:2504-2529 — 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 copy of a member (1 corresponding lines) · ×1
Edited copy of a member (1 corresponding lines) crates/muxy-protocol/src/activity.rs:8— crates/muxy-protocol/src/activity.rs:8-8 | crates/muxy-protocol/src/control.rs:413-413 — 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 copies of one member (3 members, 7+ corresponding lines) · ×1
Edited copies of one member (3 members, 7+ corresponding lines) crates/muxy-server/src/files/mod.rs:55— crates/muxy-server/src/files/mod.rs:55-61 | crates/muxy-server/src/git/mod.rs:74-83 | crates/muxy-server/src/git/operations.rs:26-35 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×1
Edited copies of one member (3 members, 8+ corresponding lines) crates/muxy-ui/src/notifications.rs:90— crates/muxy-ui/src/notifications.rs:90-97 | crates/muxy-ui/src/notifications.rs:100-107 | crates/muxy-ui/src/notifications.rs:109-116 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 8+ corresponding lines) · ×1
Edited copies of one member (5 members, 8+ corresponding lines) crates/muxy-app/src/views/settings/about.rs:10— crates/muxy-app/src/views/settings/about.rs:10-20 | crates/muxy-app/src/views/settings/keyboard.rs:153-163 | crates/muxy-app/src/views/settings/mod.rs:561-568 | crates/muxy-app/src/views/settings/mod.rs:578-586 | crates/muxy-app/src/views/settings/quick_terminal.rs:309-317 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
Duplicated block (22 lines × 2) crates/muxy-app/src/views/settings/tab.rs:327— crates/muxy-app/src/views/settings/tab.rs:327-348 | crates/muxy-app/src/views/settings/tab.rs:467-488 — 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 `crates/muxy-app/src/views/settings/tab.rs:327` 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 (20 lines × 2) crates/muxy-ui/src/quick_terminal/platform/linux/panel.rs:345— crates/muxy-ui/src/quick_terminal/platform/linux/panel.rs:345-364 | crates/muxy-ui/src/quick_terminal/platform/linux/shortcut.rs:125-144 — 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 (18–19 lines × 2) crates/muxy-app/src/views/terminal/colors.rs:98— crates/muxy-app/src/views/terminal/colors.rs:98-115 | crates/muxy-app/src/views/terminal/colors.rs:117-135 — 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 `crates/muxy-app/src/views/terminal/colors.rs: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.
Duplicated block (15–16 lines × 2) crates/muxy-app/src/views/browser/mod.rs:968— crates/muxy-app/src/views/browser/mod.rs:968-983 | crates/muxy-app/src/views/webview/mod.rs:732-746 — `crates/muxy-app/src/views/browser/mod.rs` and `crates/muxy-app/src/views/webview/mod.rs` 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 5 separate duplicated blocks between them, totalling at least 50 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `crates/muxy-app/src/views/browser/mod.rs:968` 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–12 lines × 2) crates/muxy-server/src/git/github/pull_requests.rs:329— crates/muxy-server/src/git/github/pull_requests.rs:329-339 | crates/muxy-server/src/git/github/pull_requests.rs:352-363 — 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 `crates/muxy-server/src/git/github/pull_requests.rs:329` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) crates/muxy-app/src/views/browser/mod.rs:803— crates/muxy-app/src/views/browser/mod.rs:803-815 | crates/muxy-app/src/views/webview/mod.rs:586-598 — `crates/muxy-app/src/views/browser/mod.rs` and `crates/muxy-app/src/views/webview/mod.rs` 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 5 separate duplicated blocks between them, totalling at least 50 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `crates/muxy-app/src/views/browser/mod.rs:803` 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 × 5) crates/muxy-app/src/views/settings/tab.rs:295— crates/muxy-app/src/views/settings/tab.rs:295-304 | crates/muxy-app/src/views/settings/tab.rs:353-362 | crates/muxy-app/src/views/settings/tab.rs:435-444 | crates/muxy-app/src/views/settings/tab.rs:493-502 | crates/muxy-app/src/views/settings/tab.rs:544-553 — all 5 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 `crates/muxy-app/src/views/settings/tab.rs:295` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) crates/muxy-app/src/views/agents_panel.rs:1084— crates/muxy-app/src/views/agents_panel.rs:1084-1093 | crates/muxy-app/src/views/floating.rs:66-75 | crates/muxy-app/src/views/move_drag.rs:1007-1016 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/muxy-app/src/views/agents_panel.rs:1084` 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 `cx` to `&mut Context<AppModel>` in one and `&Context<AppModel>` 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–10 lines × 2) crates/muxy-app/src/views/tab_sidebar.rs:367— crates/muxy-app/src/views/tab_sidebar.rs:367-376 | crates/muxy-app/src/views/tab_strip/drag.rs:281-289 — 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 `crates/muxy-app/src/views/tab_sidebar.rs:367` 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 (7–9 lines × 3) crates/muxy-app/src/views/settings/tab.rs:341— crates/muxy-app/src/views/settings/tab.rs:341-347 | crates/muxy-app/src/views/settings/tab.rs:481-487 | crates/muxy-app/src/views/settings/tab.rs:532-540 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/muxy-app/src/views/settings/tab.rs:341` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (7 lines × 5) crates/muxy-server/src/connection/reader.rs:212— crates/muxy-server/src/connection/reader.rs:212-218 | crates/muxy-server/src/connection/reader.rs:260-266 | crates/muxy-server/src/connection/reader.rs:282-288 | crates/muxy-server/src/connection/reader.rs:299-305 | crates/muxy-server/src/connection/reader.rs:321-327 — all 5 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 `crates/muxy-server/src/connection/reader.rs:212` 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 (7 lines × 4) crates/muxy-app/src/views/settings/tab.rs:283— crates/muxy-app/src/views/settings/tab.rs:283-289 | crates/muxy-app/src/views/settings/tab.rs:340-346 | crates/muxy-app/src/views/settings/tab.rs:480-486 | crates/muxy-app/src/views/settings/tab.rs:531-537 — 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 `crates/muxy-app/src/views/settings/tab.rs:283` 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) crates/muxy-server/src/session/metadata/linux.rs:15— crates/muxy-server/src/session/metadata/linux.rs:15-20 | crates/muxy-server/src/session/metadata/linux.rs:48-54 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 5) crates/muxy-app/src/views/agents_panel.rs:1105— crates/muxy-app/src/views/agents_panel.rs:1105-1109 | crates/muxy-app/src/views/floating.rs:87-91 | crates/muxy-app/src/views/move_drag.rs:1028-1032 | crates/muxy-app/src/views/splits/drag.rs:489-493 | crates/muxy-app/src/views/tab_strip/drag.rs:387-391 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `crates/muxy-app/src/views/agents_panel.rs:1105` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `cx` to `&mut Context<AppModel>` in one and `&Context<AppModel>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/muxy-app/src/views/tab_strip/drag.rs:386` calls `clone` and `crates/muxy-app/src/views/agents_panel.rs:1104` 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 (5 lines × 3) crates/muxy-server/src/connection/reader.rs:105— crates/muxy-server/src/connection/reader.rs:105-109 | crates/muxy-server/src/connection/reader.rs:116-120 | crates/muxy-server/src/connection/reader.rs:127-131 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/muxy-server/src/connection/reader.rs:105` 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.
End-of-life runtime: Rust 1.92 rust-toolchain.toml:1— rust-toolchain.toml declares Rust 1.92 as this project's toolchain file, and Rust 1.92, superseded by 1.93 on 2026-01-22 (the Rust project patches only the current stable). An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2026-01-22 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
Type Safety — 0 typed · 5 plain JS — the untyped files are crates/muxy-app-core/src/browser/element_picker.js, crates/muxy-app/src/extensions/bridge.js, crates/muxy-app/src/extensions/script.js, crates/muxy-app/src/views/webview/bridge.js, crates/muxy-app/src/views/webview/bridge.test.cjs.
R10 · Code Duplication· Duplicated block with local edits (43 matched lines × 2 locations) · ×1
Duplicated block with local edits (43 matched lines × 2 locations) crates/muxy-app/src/extensions/bridge.js:320— crates/muxy-app/src/extensions/bridge.js:320 · crates/muxy-app/src/views/webview/bridge.js:140 — the two spans are one implementation copied and then locally edited — 393 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (8 lines × 2 locations) crates/muxy-app/src/extensions/script.js:6— crates/muxy-app/src/extensions/script.js:6 · crates/muxy-app/src/views/webview/bridge.js:260 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Complex function restore (cyclomatic 14, cognitive 19) crates/muxy-app-core/src/browser/element_picker.js:5— restore has cyclomatic complexity 14 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity· Complex function open (cyclomatic 14, cognitive 17) · ×1
Complex function open (cyclomatic 14, cognitive 17) crates/muxy-app/src/views/webview/bridge.js:166— open has cyclomatic complexity 14 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 12, cognitive 16) crates/muxy-app/src/extensions/bridge.js:1— (anonymous) has cyclomatic complexity 12 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function execPayload (cyclomatic 12, cognitive 13) crates/muxy-app/src/extensions/bridge.js:13— execPayload has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function __muxyTick (cyclomatic 11, cognitive 13) crates/muxy-app/src/extensions/script.js:36— __muxyTick has cyclomatic complexity 11 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· crates/muxy-app/src/extensions/bridge.js · ×1
crates/muxy-app/src/extensions/bridge.js: 451 lines of code crates/muxy-app/src/extensions/bridge.js:1— crates/muxy-app/src/extensions/bridge.js has 451 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
X14 · Bypassable address classification· IP classification is bypassable through an IPv4-in-IPv6 embedding · ×1
IP classification is bypassable through an IPv4-in-IPv6 embedding crates/muxy-app/src/extensions/http.rs:93— This function unwraps IPv4-MAPPED IPv6 (`to_ipv4_mapped`, line 100) and then rejects `10.0.0.0/8` on its IPv4 path — but the IPv6 decision at line 93 classifies the address as written, and IPv4 reaches IPv6 through three MORE embeddings this function never mentions: IPv4-compatible (`::a.b.c.d`), 6to4 (`2002::/16`) and NAT64 (`64:ff9b::/96`). So `::10.0.0.1`, `2002:0a00:0001::` and `64:ff9b::10.0.0.0` all name a host inside `10.0.0.0/8` — the range this same function declares non-public — and all reach the IPv6 decision un-unwrapped, taking the opposite verdict. Unwrap every embedding to its IPv4 form before classifying, or reject any IPv6 address carrying an embedded IPv4 outright.
Duplicated predicate crates/muxy-app/src/extensions/bridge.js:437— `!key.startsWith('extension.') || key.length <= 'extension.'.length` appears character-identically in 2 files — crates/muxy-app/src/extensions/bridge.js, crates/muxy-app/src/views/webview/bridge.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate crates/muxy-app/src/extensions/bridge.js:330— `typeof o.onQuery === 'function' || typeof o.onQueryChange === 'function'` appears character-identically in 2 files — crates/muxy-app/src/extensions/bridge.js, crates/muxy-app/src/views/webview/bridge.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate scripts/install-desktop-linux.py:314— `path.is_file() and not path.is_symlink()` appears character-identically in 4 files — scripts/install-desktop-linux.py, scripts/linux_packages.py, scripts/verify-desktop-formats.py, scripts/verify-desktop-linux.py. 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 scripts/verify-desktop-linux.py:60— `server.poll() is None and socket.stat().st_ino == inode` appears character-identically in 2 files — scripts/verify-desktop-linux.py, scripts/verify-release-package.py. 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 scripts/smoke-headless.py:30— `server.poll() is not None or time.monotonic() >= deadline` appears character-identically in 2 files — scripts/smoke-headless.py, scripts/verify-desktop-linux.py. 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 crates/muxy-server/src/git/worktree.rs:52— `!metadata.is_dir() || metadata.file_type().is_symlink()` appears character-identically in 3 files — crates/muxy-server/src/git/worktree.rs, crates/muxy-server/src/shell.rs, crates/muxy-server/src/uploads.rs. 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 crates/muxy-app/src/opener.rs:544— `!output.status.success() || output.timed_out || output.stdout.truncated` appears character-identically in 2 files — crates/muxy-app/src/opener.rs, crates/muxy-app/src/profiler/capture.rs. 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 crates/muxy-app/src/model/commands.rs:60— `!self.can_run_custom_command() || self.overlay.is_some()` appears character-identically in 2 files — crates/muxy-app/src/model/commands.rs, crates/muxy-app/src/model/extensions/app.rs. 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 crates/muxy-app/src/model.rs:1822— `!self.ready(server) || !self.confirmed(server)` appears character-identically in 2 files — crates/muxy-app/src/model.rs, crates/muxy-app/src/model/remote_files.rs. 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 crates/muxy-app/src/views/menu/shortcuts.rs:117— `bindings.bindings.contains_key(chord) || !application_handles(chord, cx)` appears character-identically in 2 files — crates/muxy-app/src/views/menu/shortcuts.rs, crates/muxy-app/src/views/workspace/commands.rs. 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 crates/muxy-app/src/views/terminal/scroll.rs:270— `error.code == ErrorCode::StaleHistoryCursor && request.before.0 != 0 && !self.restarted` appears character-identically in 2 files — crates/muxy-app/src/views/terminal/scroll.rs, crates/muxy-cli/src/scroll.rs. 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 crates/muxy-core/src/process.rs:200— `exited.is_none() || !limits.kill_leftovers` appears character-identically in 2 files — crates/muxy-core/src/process.rs, crates/muxy-core/src/process/windows.rs. 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 crates/muxy-app-core/src/backup/legacy.rs:429— `extension.eq_ignore_ascii_case("exe") || extension.eq_ignore_ascii_case("com")` appears character-identically in 2 files — crates/muxy-app-core/src/backup/legacy.rs, crates/muxy-server/src/settings.rs. 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 crates/muxy-app/src/ai.rs:494— `output.stdout.truncated || output.stderr.truncated` appears character-identically in 3 files — crates/muxy-app/src/ai.rs, REDACTED, crates/muxy-server/src/git/hooks.rs. 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 crates/muxy-app/src/views/agents_panel.rs:1107— `phase != DispatchPhase::Capture || event.button != MouseButton::Left` appears character-identically in 7 files — crates/muxy-app/src/views/agents_panel.rs, crates/muxy-app/src/views/floating.rs, crates/muxy-app/src/views/move_drag.rs, crates/muxy-app/src/views/sidebar/resize.rs. 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 crates/muxy-app-core/src/settings_tab.rs:89— `project.server_id.is_local() && project.status() == ProjectStatus::Available` appears character-identically in 2 files — crates/muxy-app-core/src/settings_tab.rs, crates/muxy-app/src/model/project_apps.rs. 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 crates/muxy-app/src/views/terminal/element/block.rs:58— `quad.size.width > px(0.0) && quad.size.height > px(0.0)` appears character-identically in 2 files — crates/muxy-app/src/views/terminal/element/block.rs, crates/muxy-app/src/views/terminal/element/glyph.rs. 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 crates/muxy-app/src/views/terminal/element.rs:488— `run.text.is_ascii() && run.text.len() == usize::from(run.width)` appears character-identically in 3 files — crates/muxy-app/src/views/terminal/element.rs, crates/muxy-app/src/views/terminal/selection.rs, crates/muxy-server/src/search.rs. 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 crates/muxy-core/src/process.rs:452— `self.captured.truncated && matches!(self.cap, Cap::StopAt(_))` appears character-identically in 2 files — crates/muxy-core/src/process.rs, crates/muxy-core/src/process/windows.rs. 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 crates/muxy-app/src/model/active.rs:220— `self.overlay.is_some() || self.dialogs.is_open()` appears character-identically in 2 files — crates/muxy-app/src/model/active.rs, crates/muxy-app/src/views/workspace.rs. 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 crates/muxy-app/src/views/browser/mod.rs:748— `self.presentation.visible != visible || self.presentation.blocked != blocked` appears character-identically in 2 files — crates/muxy-app/src/views/browser/mod.rs, crates/muxy-app/src/views/webview/mod.rs. 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 crates/muxy-app/src/model.rs:867— `self.quitting != Quitting::Idle || self.close_request.is_some()` appears character-identically in 3 files — crates/muxy-app/src/model.rs, crates/muxy-app/src/model/project_layouts.rs, crates/muxy-app/src/model/tab_windows.rs. 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 crates/muxy-app/src/views/remote_servers.rs:640— `server.incompatible && crate::model::released_version().is_some()` appears character-identically in 2 files — crates/muxy-app/src/views/remote_servers.rs, crates/muxy-app/src/views/server_menu.rs. 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 crates/muxy-app/src/views/remote_servers.rs:628— `server.missing && crate::model::released_version().is_some()` appears character-identically in 2 files — crates/muxy-app/src/views/remote_servers.rs, crates/muxy-app/src/views/server_menu.rs. 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 crates/muxy-app/src/project_icon/icns.rs:53— `width == 0 || height == 0 || width > MAX_SIDE || height > MAX_SIDE` appears character-identically in 2 files — crates/muxy-app/src/project_icon/icns.rs, crates/muxy-terminal/src/graphics/sixel.rs. 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.
Silent fallback default on Err crates/muxy-app/src/ai.rs:255— `discover` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err crates/muxy-core/src/l10n/format.rs:293— `number` turns every `Err` into `0.0` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err crates/muxy-server/src/git/command.rs:149— `system_path` turns every `Err` into `r"C:\Windows\System32".into()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err crates/muxy-ui/src/webview/linux/page.rs:403— `web_context` turns every `Err` into `CString::default()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
No ADRs found crates/muxy-server/src/main.rs:1— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `crates/muxy-server/src/main.rs` makes this repository a deployable product (line 1).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 5 of 11 project(s) overshoot their size bounds, lowering Project Cohesion to 1.3/10. The most over is `crates/muxy-app` (115620 LoC, 345 module-visible types across 39 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
Logging is not universal — Only 1/5 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `crates/muxy-app`, `crates/muxy-cli`, `crates/muxy-mobile`, `crates/muxy-protocol`.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
Outdated: icu_locale_core — `icu_locale_core` is locked at 2.3.0 but 2.4.0 is the current stable release on crates.io, and it already satisfies the `"2.3"` requirement declared in crates/muxy-app-core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p icu_locale_core` and commit the updated REDACTED.
Outdated: icu_plurals — `icu_plurals` is locked at 2.3.0 but 2.4.0 is the current stable release on crates.io, and it already satisfies the `"2.3"` requirement declared in crates/muxy-app-core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p icu_plurals` and commit the updated REDACTED.
Outdated: icu_provider — `icu_provider` is locked at 2.3.1 but 2.4.0 is the current stable release on crates.io, and it already satisfies the `"2.3"` requirement declared in crates/muxy-app-core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p icu_provider` and commit the updated REDACTED.
Outdated: libc — `libc` is locked at 0.2.189 but 0.2.191 is the current stable release on crates.io, and it already satisfies the `"0.2"` requirement declared in crates/muxy-client/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p libc` and commit the updated REDACTED.
Outdated: log — `log` is locked at 0.4.34 but 0.4.35 is the current stable release on crates.io, and it already satisfies the `"0.4"` requirement declared in crates/muxy-server/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p log` and commit the updated REDACTED.
Outdated: minicbor — `minicbor` is locked at 2.3.0 but 2.3.1 is the current stable release on crates.io, and it already satisfies the `"2.3"` requirement declared in crates/muxy-protocol/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p minicbor` and commit the updated REDACTED.
Outdated: notify — `notify` is locked at 8.2.0 but 8.2.2 is the current stable release on crates.io, and it already satisfies the `"8"` requirement declared in crates/muxy-server/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p notify` and commit the updated REDACTED.
Outdated: objc2 — `objc2` is locked at 0.6.4 but 0.6.5 is the current stable release on crates.io, and it already satisfies the `"0.6"` requirement declared in crates/muxy-ui/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p objc2` and commit the updated REDACTED.
Outdated: rustix — `rustix` is locked at 1.1.4 but 1.1.6 is the current stable release on crates.io, and it already satisfies the `"1.1.4"` requirement declared in crates/muxy-app-core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rustix` and commit the updated REDACTED.
Outdated: serde_json — `serde_json` is locked at 1.0.151 but 1.0.154 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in crates/muxy-app-core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde_json` and commit the updated REDACTED.
Outdated: signal-hook — `signal-hook` is locked at 0.4.4 but 0.4.6 is the current stable release on crates.io, and it already satisfies the `"0.4"` requirement declared in crates/muxy-cli/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p signal-hook` and commit the updated REDACTED.
Outdated: toml — `toml` is locked at 1.1.5+spec-1.1.0 but 1.2.1+spec-1.1.0 is the current stable release on crates.io, and it already satisfies the `"1.1"` requirement declared in crates/muxy-app-core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p toml` and commit the updated REDACTED.
Outdated: ureq — `ureq` is locked at 3.4.2 but 3.5.2 is the current stable release on crates.io, and it already satisfies the `"3.4.2"` requirement declared in crates/muxy-server/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p ureq` and commit the updated REDACTED.
Outdated: uuid — `uuid` is locked at 1.26.0 but 1.29.2 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/muxy-app-core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p uuid` and commit the updated REDACTED.
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.
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 01a1dccb-b337-7963-b1ea-e1370ef23bd5 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 69 · Warnings: 778 · Recommendations: 39 · Info: 14 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 15-11-2026 @ 01:21 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.