Public report of muxy-app/muxy, published 29 October 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.10.5). Watchdog 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, 29 October 2026, 09:51 UTC · Survey ID cd_f209eb6e62ed4034bb96eedc1b0c7b55
muxy-app/muxy
Measured 29 October 2026, 09:48 UTC, at code version c4e332b
Regression: 1 dimension fell since the last survey
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
CAI scoreAt riskDown 4 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: 168,278 lines of product code in 11 projects, tests not counted · Estimated rebuild effort: about 1.4 person-years · Weakest lens: Production Readiness, 55
Findings by how serious they are
52 critical565 serious49 minor
10 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks 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
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
29 October 2026, 09:48 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 Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. Watchdog works 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 ▸
73of 73 dimensions measured by tools.
639of 666 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.
73dimensions across 8 lenses, read from 168,278 lines of product code in 11 projects.
muxy-app/muxy is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 60 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 55, is the weakest lens, level with Security and Compliance, and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 2 points. Adding type checking comes next, worth about 3 points.
Thirty-eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Ten 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. Updating the vulnerable packages would fix the package with a known security hole.
The product code is 168,278 lines, about €200,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.
Watchdog compares 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: 10 findings
These 10 critical or serious findings were in the previous survey, on 15 October 2026, and are gone from this one.
€67,000 to €340,000, for 1,117 to 3,545 hours of work, about 1.4 person-years for 1 to 3 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.8 at a score of 60. 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: 168,278 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: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Raises the score by about 2 points · Low effort · ADR Quality
2
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 3 points · Medium effort · Type Safety
3
Resolve the 10 REDACTED finding(s) in Secrets (history) — start with REDACTED (9), REDACTED.
Raises the score by about 2 points · Medium effort · Secrets (history)
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €200,000 to build again, about 1.4 person-years of work. Its weakest lens is Production Readiness, at 55 (Adequate). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 2 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
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.
587 modules, with 2193 dependencies between them. 4 loops run through 234 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 547 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.
muxy_app.views.terminal.selection uses libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break muxy_app.views.terminal.selection, while a change to muxy_app.views.terminal.selection can't break libghostty_vt_sys.bindings.
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→15 muxy_app_core.ids uses muxy_protocol.projectpart of a loop✕
Connections
1 pair of types, where a type in muxy_app_core.ids uses a type in muxy_protocol.project.
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
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→20 muxy_app_core.ids uses libghostty_vt.fmtpart of a loop✕
Connections
5 pairs of types, where a type in muxy_app_core.ids uses a type in libghostty_vt.fmt.
muxy_app_core.ids uses libghostty_vt.fmt, so a change to libghostty_vt.fmt can break muxy_app_core.ids, while a change to muxy_app_core.ids can't break libghostty_vt.fmt.
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_core.project_layouts uses muxy_app_core.localization.plist, so a change to muxy_app_core.localization.plist can break muxy_app_core.project_layouts, while a change to muxy_app_core.project_layouts can't break muxy_app_core.localization.plist.
Position
Below the diagonal: muxy_app_core.project_layouts uses a module listed above it, which is the healthy direction.
muxy_app_core.project_layouts uses muxy_protocol.path, so a change to muxy_protocol.path can break muxy_app_core.project_layouts, while a change to muxy_app_core.project_layouts can't break muxy_protocol.path.
Position
Below the diagonal: muxy_app_core.project_layouts uses a module listed above it, which is the healthy direction.
8→19 muxy_app_core.project_layouts uses libghostty_vt_sys.bindingspart of a loop✕
Connections
3 pairs of types, where a type in muxy_app_core.project_layouts uses a type in libghostty_vt_sys.bindings.
muxy_app_core.project_layouts uses libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break muxy_app_core.project_layouts, while a change to muxy_app_core.project_layouts can't break libghostty_vt_sys.bindings.
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.wire.stream uses muxy_protocol.ids, so a change to muxy_protocol.ids can break muxy_protocol.wire.stream, while a change to muxy_protocol.wire.stream can't break muxy_protocol.ids.
Position
Below the diagonal: muxy_protocol.wire.stream uses a module listed above it, which is the healthy direction.
muxy_app_core.project uses muxy_app_core.ids, so a change to muxy_app_core.ids can break muxy_app_core.project, while a change to muxy_app_core.project can't break muxy_app_core.ids.
Position
Below the diagonal: muxy_app_core.project uses a module listed above it, which is the healthy direction.
10→15 muxy_app_core.project uses muxy_protocol.projectpart of a loop✕
Connections
3 pairs of types, where a type in muxy_app_core.project uses a type in muxy_protocol.project.
muxy_app_core.project uses muxy_protocol.project, so a change to muxy_protocol.project can break muxy_app_core.project, while a change to muxy_app_core.project 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.
10→19 muxy_app_core.project uses libghostty_vt_sys.bindingspart of a loop✕
Connections
2 pairs of types, where a type in muxy_app_core.project uses a type in libghostty_vt_sys.bindings.
muxy_app_core.project uses libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break muxy_app_core.project, while a change to muxy_app_core.project can't break libghostty_vt_sys.bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→20 muxy_app_core.project uses libghostty_vt.fmtpart of a loop✕
Connections
1 pair of types, where a type in muxy_app_core.project uses a type in libghostty_vt.fmt.
muxy_app_core.project uses libghostty_vt.fmt, so a change to libghostty_vt.fmt can break muxy_app_core.project, while a change to muxy_app_core.project can't break libghostty_vt.fmt.
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_core.quick_terminal.geometry uses muxy_app.views.terminal.selection, so a change to muxy_app.views.terminal.selection can break muxy_core.quick_terminal.geometry, while a change to muxy_core.quick_terminal.geometry can't break muxy_app.views.terminal.selection.
Position
Below the diagonal: muxy_core.quick_terminal.geometry 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.wire.stream, so a change to muxy_protocol.wire.stream can break muxy_protocol.activity, while a change to muxy_protocol.activity can't break muxy_protocol.wire.stream.
Position
Below the diagonal: muxy_protocol.activity uses a module listed above it, which is the healthy direction.
12→14 muxy_protocol.activity uses muxy_mobile.recordspart of a loop✕
Connections
3 pairs of types, where a type in muxy_protocol.activity uses a type in muxy_mobile.records.
muxy_protocol.activity uses muxy_mobile.records, so a change to muxy_mobile.records can break muxy_protocol.activity, while a change to muxy_protocol.activity can't break muxy_mobile.records.
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→15 muxy_protocol.activity uses muxy_protocol.projectpart of a loop✕
Connections
2 pairs of types, where a type in muxy_protocol.activity uses a type in muxy_protocol.project.
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
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.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.wire.stream, so a change to muxy_protocol.wire.stream can break muxy_protocol.session, while a change to muxy_protocol.session can't break muxy_protocol.wire.stream.
Position
Below the diagonal: muxy_protocol.session uses a module listed above it, which is the healthy direction.
muxy_protocol.session uses muxy_core.quick_terminal.geometry, so a change to muxy_core.quick_terminal.geometry can break muxy_protocol.session, while a change to muxy_protocol.session can't break muxy_core.quick_terminal.geometry.
Position
Below the diagonal: muxy_protocol.session uses a module listed above it, which is the healthy direction.
13→14 muxy_protocol.session uses muxy_mobile.recordspart of a loop✕
Connections
4 pairs of types, where a type in muxy_protocol.session uses a type in muxy_mobile.records.
muxy_protocol.session uses muxy_mobile.records, so a change to muxy_mobile.records can break muxy_protocol.session, while a change to muxy_protocol.session can't break muxy_mobile.records.
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→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.
13→19 muxy_protocol.session uses libghostty_vt_sys.bindingspart of a loop✕
Connections
4 pairs of types, where a type in muxy_protocol.session uses a type in libghostty_vt_sys.bindings.
muxy_protocol.session uses libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break muxy_protocol.session, while a change to muxy_protocol.session can't break libghostty_vt_sys.bindings.
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→20 muxy_protocol.session uses libghostty_vt.fmtpart of a loop✕
Connections
2 pairs of types, where a type in muxy_protocol.session uses a type in libghostty_vt.fmt.
muxy_protocol.session uses libghostty_vt.fmt, so a change to libghostty_vt.fmt can break muxy_protocol.session, while a change to muxy_protocol.session can't break libghostty_vt.fmt.
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_mobile.records uses muxy_protocol.path, so a change to muxy_protocol.path can break muxy_mobile.records, while a change to muxy_mobile.records can't break muxy_protocol.path.
Position
Below the diagonal: muxy_mobile.records uses a module listed above it, which is the healthy direction.
muxy_mobile.records uses muxy_app_core.project, so a change to muxy_app_core.project can break muxy_mobile.records, while a change to muxy_mobile.records can't break muxy_app_core.project.
Position
Below the diagonal: muxy_mobile.records uses a module listed above it, which is the healthy direction.
muxy_mobile.records uses muxy_protocol.activity, so a change to muxy_protocol.activity can break muxy_mobile.records, while a change to muxy_mobile.records can't break muxy_protocol.activity.
Position
Below the diagonal: muxy_mobile.records uses a module listed above it, which is the healthy direction.
muxy_mobile.records uses muxy_protocol.session, so a change to muxy_protocol.session can break muxy_mobile.records, while a change to muxy_mobile.records can't break muxy_protocol.session.
Position
Below the diagonal: muxy_mobile.records uses a module listed above it, which is the healthy direction.
14→15 muxy_mobile.records uses muxy_protocol.projectpart of a loop✕
Connections
2 pairs of types, where a type in muxy_mobile.records uses a type in muxy_protocol.project.
muxy_mobile.records uses muxy_protocol.project, so a change to muxy_protocol.project can break muxy_mobile.records, while a change to muxy_mobile.records 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.
14→19 muxy_mobile.records uses libghostty_vt_sys.bindingspart of a loop✕
Connections
9 pairs of types, where a type in muxy_mobile.records uses a type in libghostty_vt_sys.bindings.
muxy_mobile.records uses libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break muxy_mobile.records, while a change to muxy_mobile.records can't break libghostty_vt_sys.bindings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→20 muxy_mobile.records uses libghostty_vt.fmtpart of a loop✕
Connections
1 pair of types, where a type in muxy_mobile.records uses a type in libghostty_vt.fmt.
muxy_mobile.records uses libghostty_vt.fmt, so a change to libghostty_vt.fmt can break muxy_mobile.records, while a change to muxy_mobile.records can't break libghostty_vt.fmt.
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.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.wire.stream, so a change to muxy_protocol.wire.stream can break muxy_protocol.project, while a change to muxy_protocol.project can't break muxy_protocol.wire.stream.
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.
muxy_protocol.project uses muxy_mobile.records, so a change to muxy_mobile.records can break muxy_protocol.project, while a change to muxy_protocol.project can't break muxy_mobile.records.
Position
Below the diagonal: muxy_protocol.project uses a module listed above it, which is the healthy direction.
15→19 muxy_protocol.project uses libghostty_vt_sys.bindingspart of a loop✕
Connections
1 pair of types, where a type in muxy_protocol.project uses a type in libghostty_vt_sys.bindings.
muxy_protocol.project uses libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break muxy_protocol.project, while a change to muxy_protocol.project can't break libghostty_vt_sys.bindings.
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.
15→20 muxy_protocol.project uses libghostty_vt.fmtpart of a loop✕
Connections
5 pairs of types, where a type in muxy_protocol.project uses a type in libghostty_vt.fmt.
muxy_protocol.project uses libghostty_vt.fmt, so a change to libghostty_vt.fmt can break muxy_protocol.project, while a change to muxy_protocol.project can't break libghostty_vt.fmt.
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.git uses muxy_protocol.path, so a change to muxy_protocol.path can break muxy_protocol.git, while a change to muxy_protocol.git can't break muxy_protocol.path.
Position
Below the diagonal: muxy_protocol.git uses a module listed above it, which is the healthy direction.
muxy_protocol.git uses muxy_protocol.project, so a change to muxy_protocol.project can break muxy_protocol.git, while a change to muxy_protocol.git can't break muxy_protocol.project.
Position
Below the diagonal: muxy_protocol.git uses a module listed above it, which is the healthy direction.
16→19 muxy_protocol.git uses libghostty_vt_sys.bindingspart of a loop✕
Connections
8 pairs of types, where a type in muxy_protocol.git uses a type in libghostty_vt_sys.bindings.
muxy_protocol.git uses libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break muxy_protocol.git, while a change to muxy_protocol.git can't break libghostty_vt_sys.bindings.
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.repository_actions uses muxy_app_core.localization.plist, so a change to muxy_app_core.localization.plist can break muxy_app.repository_actions, while a change to muxy_app.repository_actions can't break muxy_app_core.localization.plist.
Position
Below the diagonal: muxy_app.repository_actions uses a module listed above it, which is the healthy direction.
muxy_app.repository_actions uses muxy_protocol.project, so a change to muxy_protocol.project can break muxy_app.repository_actions, while a change to muxy_app.repository_actions can't break muxy_protocol.project.
Position
Below the diagonal: muxy_app.repository_actions uses a module listed above it, which is the healthy direction.
muxy_app.repository_actions uses muxy_protocol.git, so a change to muxy_protocol.git can break muxy_app.repository_actions, while a change to muxy_app.repository_actions can't break muxy_protocol.git.
Position
Below the diagonal: muxy_app.repository_actions uses a module listed above it, which is the healthy direction.
17→19 muxy_app.repository_actions uses libghostty_vt_sys.bindingspart of a loop✕
Connections
4 pairs of types, where a type in muxy_app.repository_actions uses a type in libghostty_vt_sys.bindings.
muxy_app.repository_actions uses libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break muxy_app.repository_actions, while a change to muxy_app.repository_actions can't break libghostty_vt_sys.bindings.
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.
libghostty_vt.terminal uses muxy_app.views.terminal.selection, so a change to muxy_app.views.terminal.selection can break libghostty_vt.terminal, while a change to libghostty_vt.terminal can't break muxy_app.views.terminal.selection.
Position
Below the diagonal: libghostty_vt.terminal uses a module listed above it, which is the healthy direction.
libghostty_vt.terminal uses muxy_app_core.project_layouts, so a change to muxy_app_core.project_layouts can break libghostty_vt.terminal, while a change to libghostty_vt.terminal can't break muxy_app_core.project_layouts.
Position
Below the diagonal: libghostty_vt.terminal uses a module listed above it, which is the healthy direction.
libghostty_vt.terminal uses muxy_app.repository_actions, so a change to muxy_app.repository_actions can break libghostty_vt.terminal, while a change to libghostty_vt.terminal can't break muxy_app.repository_actions.
Position
Below the diagonal: libghostty_vt.terminal uses a module listed above it, which is the healthy direction.
18→19 libghostty_vt.terminal uses libghostty_vt_sys.bindingspart of a loop✕
Connections
4 pairs of types, where a type in libghostty_vt.terminal uses a type in libghostty_vt_sys.bindings.
libghostty_vt.terminal uses libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break libghostty_vt.terminal, while a change to libghostty_vt.terminal can't break libghostty_vt_sys.bindings.
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.
libghostty_vt_sys.bindings uses muxy_app_core.project, so a change to muxy_app_core.project can break libghostty_vt_sys.bindings, while a change to libghostty_vt_sys.bindings can't break muxy_app_core.project.
Position
Below the diagonal: libghostty_vt_sys.bindings uses a module listed above it, which is the healthy direction.
libghostty_vt_sys.bindings uses muxy_app.repository_actions, so a change to muxy_app.repository_actions can break libghostty_vt_sys.bindings, while a change to libghostty_vt_sys.bindings can't break muxy_app.repository_actions.
Position
Below the diagonal: libghostty_vt_sys.bindings uses a module listed above it, which is the healthy direction.
libghostty_vt_sys.bindings uses libghostty_vt.terminal, so a change to libghostty_vt.terminal can break libghostty_vt_sys.bindings, while a change to libghostty_vt_sys.bindings can't break libghostty_vt.terminal.
Position
Below the diagonal: libghostty_vt_sys.bindings uses a module listed above it, which is the healthy direction.
libghostty_vt.fmt uses muxy_app.views.terminal.selection, so a change to muxy_app.views.terminal.selection can break libghostty_vt.fmt, while a change to libghostty_vt.fmt can't break muxy_app.views.terminal.selection.
Position
Below the diagonal: libghostty_vt.fmt uses a module listed above it, which is the healthy direction.
libghostty_vt.fmt uses muxy_app_core.project_layouts, so a change to muxy_app_core.project_layouts can break libghostty_vt.fmt, while a change to libghostty_vt.fmt can't break muxy_app_core.project_layouts.
Position
Below the diagonal: libghostty_vt.fmt uses a module listed above it, which is the healthy direction.
libghostty_vt.fmt uses libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break libghostty_vt.fmt, while a change to libghostty_vt.fmt can't break libghostty_vt_sys.bindings.
Position
Below the diagonal: libghostty_vt.fmt uses a module listed above it, which is the healthy direction.
muxy_app.model.ai uses muxy_protocol.project, so a change to muxy_protocol.project can break muxy_app.model.ai, while a change to muxy_app.model.ai can't break muxy_protocol.project.
Position
Below the diagonal: muxy_app.model.ai uses a module listed above it, which is the healthy direction.
muxy_app.model.ai uses muxy_app.repository_actions, so a change to muxy_app.repository_actions can break muxy_app.model.ai, while a change to muxy_app.model.ai can't break muxy_app.repository_actions.
Position
Below the diagonal: muxy_app.model.ai uses a module listed above it, which is the healthy direction.
muxy_app.model.ai uses libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break muxy_app.model.ai, while a change to muxy_app.model.ai can't break libghostty_vt_sys.bindings.
Position
Below the diagonal: muxy_app.model.ai uses a module listed above it, which is the healthy direction.
muxy_app_core.extensions.manifest uses muxy_app_core.localization.plist, so a change to muxy_app_core.localization.plist can break muxy_app_core.extensions.manifest, while a change to muxy_app_core.extensions.manifest can't break muxy_app_core.localization.plist.
Position
Below the diagonal: muxy_app_core.extensions.manifest uses a module listed above it, which is the healthy direction.
muxy_app_core.extensions.manifest uses muxy_app.repository_actions, so a change to muxy_app.repository_actions can break muxy_app_core.extensions.manifest, while a change to muxy_app_core.extensions.manifest can't break muxy_app.repository_actions.
Position
Below the diagonal: muxy_app_core.extensions.manifest uses a module listed above it, which is the healthy direction.
muxy_app_core.extensions.manifest uses libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break muxy_app_core.extensions.manifest, while a change to muxy_app_core.extensions.manifest can't break libghostty_vt_sys.bindings.
Position
Below the diagonal: muxy_app_core.extensions.manifest uses a module listed above it, which is the healthy direction.
muxy_app_core.state uses muxy_app_core.localization.plist, so a change to muxy_app_core.localization.plist can break muxy_app_core.state, while a change to muxy_app_core.state can't break muxy_app_core.localization.plist.
Position
Below the diagonal: muxy_app_core.state uses a module listed above it, which is the healthy direction.
muxy_app_core.state uses muxy_protocol.ids, so a change to muxy_protocol.ids can break muxy_app_core.state, while a change to muxy_app_core.state can't break muxy_protocol.ids.
Position
Below the diagonal: muxy_app_core.state uses a module listed above it, which is the healthy direction.
muxy_app_core.state uses muxy_protocol.path, so a change to muxy_protocol.path can break muxy_app_core.state, while a change to muxy_app_core.state can't break muxy_protocol.path.
Position
Below the diagonal: muxy_app_core.state uses a module listed above it, which is the healthy direction.
muxy_app_core.state uses muxy_app_core.ids, so a change to muxy_app_core.ids can break muxy_app_core.state, while a change to muxy_app_core.state can't break muxy_app_core.ids.
Position
Below the diagonal: muxy_app_core.state uses a module listed above it, which is the healthy direction.
muxy_app_core.state uses muxy_app_core.project_layouts, so a change to muxy_app_core.project_layouts can break muxy_app_core.state, while a change to muxy_app_core.state can't break muxy_app_core.project_layouts.
Position
Below the diagonal: muxy_app_core.state uses a module listed above it, which is the healthy direction.
muxy_app_core.state uses muxy_app_core.project, so a change to muxy_app_core.project can break muxy_app_core.state, while a change to muxy_app_core.state can't break muxy_app_core.project.
Position
Below the diagonal: muxy_app_core.state uses a module listed above it, which is the healthy direction.
muxy_app_core.state uses muxy_protocol.project, so a change to muxy_protocol.project can break muxy_app_core.state, while a change to muxy_app_core.state can't break muxy_protocol.project.
Position
Below the diagonal: muxy_app_core.state uses a module listed above it, which is the healthy direction.
muxy_app_core.state uses libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break muxy_app_core.state, while a change to muxy_app_core.state can't break libghostty_vt_sys.bindings.
Position
Below the diagonal: muxy_app_core.state uses a module listed above it, which is the healthy direction.
muxy_cli.worker.io uses muxy_protocol.ids, so a change to muxy_protocol.ids can break muxy_cli.worker.io, while a change to muxy_cli.worker.io can't break muxy_protocol.ids.
Position
Below the diagonal: muxy_cli.worker.io uses a module listed above it, which is the healthy direction.
muxy_cli.worker.io uses muxy_app_core.ids, so a change to muxy_app_core.ids can break muxy_cli.worker.io, while a change to muxy_cli.worker.io can't break muxy_app_core.ids.
Position
Below the diagonal: muxy_cli.worker.io uses a module listed above it, which is the healthy direction.
muxy_cli.worker.io uses muxy_core.quick_terminal.geometry, so a change to muxy_core.quick_terminal.geometry can break muxy_cli.worker.io, while a change to muxy_cli.worker.io can't break muxy_core.quick_terminal.geometry.
Position
Below the diagonal: muxy_cli.worker.io uses a module listed above it, which is the healthy direction.
muxy_cli.worker.io uses muxy_protocol.activity, so a change to muxy_protocol.activity can break muxy_cli.worker.io, while a change to muxy_cli.worker.io can't break muxy_protocol.activity.
Position
Below the diagonal: muxy_cli.worker.io uses a module listed above it, which is the healthy direction.
muxy_cli.worker.io uses muxy_protocol.session, so a change to muxy_protocol.session can break muxy_cli.worker.io, while a change to muxy_cli.worker.io can't break muxy_protocol.session.
Position
Below the diagonal: muxy_cli.worker.io uses a module listed above it, which is the healthy direction.
muxy_cli.worker.io uses muxy_protocol.project, so a change to muxy_protocol.project can break muxy_cli.worker.io, while a change to muxy_cli.worker.io can't break muxy_protocol.project.
Position
Below the diagonal: muxy_cli.worker.io uses a module listed above it, which is the healthy direction.
muxy_cli.worker.io uses libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break muxy_cli.worker.io, while a change to muxy_cli.worker.io can't break libghostty_vt_sys.bindings.
Position
Below the diagonal: muxy_cli.worker.io uses a module listed above it, which is the healthy direction.
24→30 muxy_cli.worker.io uses muxy_client.clientpart of a loop✕
Connections
5 pairs of types, where a type in muxy_cli.worker.io uses a type in muxy_client.client.
muxy_cli.worker.io uses muxy_client.client, so a change to muxy_client.client can break muxy_cli.worker.io, while a change to muxy_cli.worker.io can't break muxy_client.client.
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.
24→37 muxy_cli.worker.io uses muxy_app.model.extensions.localpart of a loop✕
Connections
1 pair of types, where a type in muxy_cli.worker.io uses a type in muxy_app.model.extensions.local.
muxy_cli.worker.io uses muxy_app.model.extensions.local, so a change to muxy_app.model.extensions.local can break muxy_cli.worker.io, while a change to muxy_cli.worker.io can't break muxy_app.model.extensions.local.
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.wire.stream, so a change to muxy_protocol.wire.stream can break muxy_protocol.control, while a change to muxy_protocol.control can't break muxy_protocol.wire.stream.
Position
Below the diagonal: muxy_protocol.control uses a module listed above it, which is the healthy direction.
muxy_protocol.control uses muxy_mobile.records, so a change to muxy_mobile.records can break muxy_protocol.control, while a change to muxy_protocol.control can't break muxy_mobile.records.
Position
Below the diagonal: muxy_protocol.control uses a module listed above it, which is the healthy direction.
muxy_protocol.control uses libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break muxy_protocol.control, while a change to muxy_protocol.control can't break libghostty_vt_sys.bindings.
Position
Below the diagonal: muxy_protocol.control uses a module listed above it, which is the healthy direction.
muxy_ui.javascript.jsc uses libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break muxy_ui.javascript.jsc, while a change to muxy_ui.javascript.jsc can't break libghostty_vt_sys.bindings.
Position
Below the diagonal: muxy_ui.javascript.jsc 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 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 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 muxy_app.views.terminal.selection, so a change to muxy_app.views.terminal.selection can break muxy_app.views.browser, while a change to muxy_app.views.browser can't break muxy_app.views.terminal.selection.
Position
Below the diagonal: muxy_app.views.browser uses a module listed above it, which is the healthy direction.
muxy_app.views.browser uses libghostty_vt.terminal, so a change to libghostty_vt.terminal can break muxy_app.views.browser, while a change to muxy_app.views.browser can't break libghostty_vt.terminal.
Position
Below the diagonal: muxy_app.views.browser uses a module listed above it, which is the healthy direction.
muxy_app.views.browser uses libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break muxy_app.views.browser, while a change to muxy_app.views.browser can't break libghostty_vt_sys.bindings.
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.javascript.jsc, so a change to muxy_ui.javascript.jsc can break muxy_app.views.browser, while a change to muxy_app.views.browser can't break muxy_ui.javascript.jsc.
Position
Below the diagonal: muxy_app.views.browser uses a module listed above it, which is the healthy direction.
27→37 muxy_app.views.browser uses muxy_app.model.extensions.localpart of a loop✕
Connections
1 pair of types, where a type in muxy_app.views.browser uses a type in muxy_app.model.extensions.local.
muxy_app.views.browser uses muxy_app.model.extensions.local, so a change to muxy_app.model.extensions.local can break muxy_app.views.browser, while a change to muxy_app.views.browser can't break muxy_app.model.extensions.local.
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 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 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 muxy_app.views.terminal.selection, so a change to muxy_app.views.terminal.selection can break muxy_app.views.settings, while a change to muxy_app.views.settings can't break muxy_app.views.terminal.selection.
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_core.quick_terminal.geometry, so a change to muxy_core.quick_terminal.geometry can break muxy_app.views.settings, while a change to muxy_app.views.settings can't break muxy_core.quick_terminal.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 muxy_mobile.records, so a change to muxy_mobile.records can break muxy_app.views.settings, while a change to muxy_app.views.settings can't break muxy_mobile.records.
Position
Below the diagonal: muxy_app.views.settings uses a module listed above it, which is the healthy direction.
muxy_app.views.settings uses libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break muxy_app.views.settings, while a change to muxy_app.views.settings can't break libghostty_vt_sys.bindings.
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 muxy_ui.javascript.jsc, so a change to muxy_ui.javascript.jsc can break muxy_app.views.settings, while a change to muxy_app.views.settings can't break muxy_ui.javascript.jsc.
Position
Below the diagonal: muxy_app.views.settings uses a module listed above it, which is the healthy direction.
28→35 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.
28→36 muxy_app.views.settings uses muxy_app.views.tab_activitypart of a loop✕
Connections
1 pair of types, where a type in muxy_app.views.settings uses a type in muxy_app.views.tab_activity.
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
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→37 muxy_app.views.settings uses muxy_app.model.extensions.localpart of a loop✕
Connections
1 pair of types, where a type in muxy_app.views.settings uses a type in muxy_app.model.extensions.local.
muxy_app.views.settings uses muxy_app.model.extensions.local, so a change to muxy_app.model.extensions.local can break muxy_app.views.settings, while a change to muxy_app.views.settings can't break muxy_app.model.extensions.local.
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_core.settings.error uses libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break muxy_app_core.settings.error, while a change to muxy_app_core.settings.error can't break libghostty_vt_sys.bindings.
Position
Below the diagonal: muxy_app_core.settings.error uses a module listed above it, which is the healthy direction.
muxy_app_core.settings.error uses libghostty_vt.fmt, so a change to libghostty_vt.fmt can break muxy_app_core.settings.error, while a change to muxy_app_core.settings.error can't break libghostty_vt.fmt.
Position
Below the diagonal: muxy_app_core.settings.error 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.wire.stream, so a change to muxy_protocol.wire.stream can break muxy_client.client, while a change to muxy_client.client can't break muxy_protocol.wire.stream.
Position
Below the diagonal: muxy_client.client uses a module listed above it, which is the healthy direction.
muxy_client.client uses muxy_core.quick_terminal.geometry, so a change to muxy_core.quick_terminal.geometry can break muxy_client.client, while a change to muxy_client.client can't break muxy_core.quick_terminal.geometry.
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_mobile.records, so a change to muxy_mobile.records can break muxy_client.client, while a change to muxy_client.client can't break muxy_mobile.records.
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_client.client uses muxy_protocol.git, so a change to muxy_protocol.git can break muxy_client.client, while a change to muxy_client.client can't break muxy_protocol.git.
Position
Below the diagonal: muxy_client.client uses a module listed above it, which is the healthy direction.
muxy_client.client uses muxy_app.repository_actions, so a change to muxy_app.repository_actions can break muxy_client.client, while a change to muxy_client.client can't break muxy_app.repository_actions.
Position
Below the diagonal: muxy_client.client uses a module listed above it, which is the healthy direction.
muxy_client.client uses libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break muxy_client.client, while a change to muxy_client.client can't break libghostty_vt_sys.bindings.
Position
Below the diagonal: muxy_client.client uses a module listed above it, which is the healthy direction.
muxy_client.client uses libghostty_vt.fmt, so a change to libghostty_vt.fmt can break muxy_client.client, while a change to muxy_client.client can't break libghostty_vt.fmt.
Position
Below the diagonal: muxy_client.client uses a module listed above it, which is the healthy direction.
muxy_client.client uses muxy_cli.worker.io, so a change to muxy_cli.worker.io can break muxy_client.client, while a change to muxy_client.client can't break muxy_cli.worker.io.
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_terminal.ghostty uses muxy_protocol.wire.stream, so a change to muxy_protocol.wire.stream can break muxy_terminal.ghostty, while a change to muxy_terminal.ghostty can't break muxy_protocol.wire.stream.
Position
Below the diagonal: muxy_terminal.ghostty uses a module listed above it, which is the healthy direction.
muxy_terminal.ghostty uses muxy_app_core.project, so a change to muxy_app_core.project can break muxy_terminal.ghostty, while a change to muxy_terminal.ghostty can't break muxy_app_core.project.
Position
Below the diagonal: muxy_terminal.ghostty uses a module listed above it, which is the healthy direction.
muxy_terminal.ghostty uses muxy_core.quick_terminal.geometry, so a change to muxy_core.quick_terminal.geometry can break muxy_terminal.ghostty, while a change to muxy_terminal.ghostty can't break muxy_core.quick_terminal.geometry.
Position
Below the diagonal: muxy_terminal.ghostty uses a module listed above it, which is the healthy direction.
muxy_terminal.ghostty uses muxy_protocol.session, so a change to muxy_protocol.session can break muxy_terminal.ghostty, while a change to muxy_terminal.ghostty can't break muxy_protocol.session.
Position
Below the diagonal: muxy_terminal.ghostty uses a module listed above it, which is the healthy direction.
muxy_terminal.ghostty uses muxy_mobile.records, so a change to muxy_mobile.records can break muxy_terminal.ghostty, while a change to muxy_terminal.ghostty can't break muxy_mobile.records.
Position
Below the diagonal: muxy_terminal.ghostty uses a module listed above it, which is the healthy direction.
muxy_terminal.ghostty uses libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break muxy_terminal.ghostty, while a change to muxy_terminal.ghostty can't break libghostty_vt_sys.bindings.
Position
Below the diagonal: muxy_terminal.ghostty uses a module listed above it, which is the healthy direction.
muxy_terminal.ghostty uses muxy_app.model.ai, so a change to muxy_app.model.ai can break muxy_terminal.ghostty, while a change to muxy_terminal.ghostty can't break muxy_app.model.ai.
Position
Below the diagonal: muxy_terminal.ghostty uses a module listed above it, which is the healthy direction.
muxy_terminal.ghostty uses muxy_protocol.control, so a change to muxy_protocol.control can break muxy_terminal.ghostty, while a change to muxy_terminal.ghostty can't break muxy_protocol.control.
Position
Below the diagonal: muxy_terminal.ghostty uses a module listed above it, which is the healthy direction.
muxy_app.model.extensions uses muxy_app_core.localization.plist, so a change to muxy_app_core.localization.plist can break muxy_app.model.extensions, while a change to muxy_app.model.extensions can't break muxy_app_core.localization.plist.
Position
Below the diagonal: muxy_app.model.extensions uses a module listed above it, which is the healthy direction.
muxy_app.model.extensions uses muxy_app_core.ids, so a change to muxy_app_core.ids can break muxy_app.model.extensions, while a change to muxy_app.model.extensions can't break muxy_app_core.ids.
Position
Below the diagonal: muxy_app.model.extensions uses a module listed above it, which is the healthy direction.
muxy_app.model.extensions uses muxy_protocol.project, so a change to muxy_protocol.project can break muxy_app.model.extensions, while a change to muxy_app.model.extensions can't break muxy_protocol.project.
Position
Below the diagonal: muxy_app.model.extensions uses a module listed above it, which is the healthy direction.
muxy_app.model.extensions uses libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break muxy_app.model.extensions, while a change to muxy_app.model.extensions can't break libghostty_vt_sys.bindings.
Position
Below the diagonal: muxy_app.model.extensions uses a module listed above it, which is the healthy direction.
muxy_app.model.extensions uses muxy_client.client, so a change to muxy_client.client can break muxy_app.model.extensions, while a change to muxy_app.model.extensions can't break muxy_client.client.
Position
Below the diagonal: muxy_app.model.extensions uses a module listed above it, which is the healthy direction.
32→36 muxy_app.model.extensions uses muxy_app.views.tab_activitypart of a loop✕
Connections
1 pair of types, where a type in muxy_app.model.extensions uses a type in muxy_app.views.tab_activity.
muxy_app.model.extensions uses muxy_app.views.tab_activity, so a change to muxy_app.views.tab_activity can break muxy_app.model.extensions, while a change to muxy_app.model.extensions can't break muxy_app.views.tab_activity.
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.
32→37 muxy_app.model.extensions uses muxy_app.model.extensions.localpart of a loop✕
Connections
1 pair of types, where a type in muxy_app.model.extensions uses a type in muxy_app.model.extensions.local.
muxy_app.model.extensions uses muxy_app.model.extensions.local, so a change to muxy_app.model.extensions.local can break muxy_app.model.extensions, while a change to muxy_app.model.extensions can't break muxy_app.model.extensions.local.
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 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_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 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.terminal.selection, so a change to muxy_app.views.terminal.selection can break muxy_app.views.terminal.pane, while a change to muxy_app.views.terminal.pane can't break muxy_app.views.terminal.selection.
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 muxy_core.quick_terminal.geometry, so a change to muxy_core.quick_terminal.geometry can break muxy_app.views.terminal.pane, while a change to muxy_app.views.terminal.pane can't break muxy_core.quick_terminal.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 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 libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break muxy_app.views.terminal.pane, while a change to muxy_app.views.terminal.pane can't break libghostty_vt_sys.bindings.
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.javascript.jsc, so a change to muxy_ui.javascript.jsc can break muxy_app.views.terminal.pane, while a change to muxy_app.views.terminal.pane can't break muxy_ui.javascript.jsc.
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_client.client, so a change to muxy_client.client can break muxy_app.views.terminal.pane, while a change to muxy_app.views.terminal.pane can't break muxy_client.client.
Position
Below the diagonal: muxy_app.views.terminal.pane uses a module listed above it, which is the healthy direction.
33→36 muxy_app.views.terminal.pane uses muxy_app.views.tab_activitypart of a loop✕
Connections
1 pair of types, where a type in muxy_app.views.terminal.pane uses a type in muxy_app.views.tab_activity.
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
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.
33→39 muxy_app.views.terminal.pane uses muxy_app.bootpart of a loop✕
Connections
1 pair of types, where a type in muxy_app.views.terminal.pane uses a type in muxy_app.boot.
muxy_app.views.terminal.pane uses muxy_app.boot, so a change to muxy_app.boot can break muxy_app.views.terminal.pane, while a change to muxy_app.views.terminal.pane can't break muxy_app.boot.
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_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_core.quick_terminal.geometry, so a change to muxy_core.quick_terminal.geometry can break muxy_server.registry, while a change to muxy_server.registry can't break muxy_core.quick_terminal.geometry.
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_mobile.records, so a change to muxy_mobile.records can break muxy_server.registry, while a change to muxy_server.registry can't break muxy_mobile.records.
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.
muxy_server.registry uses muxy_protocol.git, so a change to muxy_protocol.git can break muxy_server.registry, while a change to muxy_server.registry can't break muxy_protocol.git.
Position
Below the diagonal: muxy_server.registry uses a module listed above it, which is the healthy direction.
muxy_server.registry uses muxy_app.repository_actions, so a change to muxy_app.repository_actions can break muxy_server.registry, while a change to muxy_server.registry can't break muxy_app.repository_actions.
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_app_core.settings.error, so a change to muxy_app_core.settings.error can break muxy_server.registry, while a change to muxy_server.registry can't break muxy_app_core.settings.error.
Position
Below the diagonal: muxy_server.registry 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 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 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 muxy_app.views.terminal.selection, so a change to muxy_app.views.terminal.selection can break muxy_app.model, while a change to muxy_app.model can't break muxy_app.views.terminal.selection.
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_app_core.project_layouts, so a change to muxy_app_core.project_layouts can break muxy_app.model, while a change to muxy_app.model can't break muxy_app_core.project_layouts.
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.project, so a change to muxy_app_core.project can break muxy_app.model, while a change to muxy_app.model can't break muxy_app_core.project.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses muxy_core.quick_terminal.geometry, so a change to muxy_core.quick_terminal.geometry can break muxy_app.model, while a change to muxy_app.model can't break muxy_core.quick_terminal.geometry.
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_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 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_protocol.git, so a change to muxy_protocol.git can break muxy_app.model, while a change to muxy_app.model can't break muxy_protocol.git.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses muxy_app.repository_actions, so a change to muxy_app.repository_actions can break muxy_app.model, while a change to muxy_app.model can't break muxy_app.repository_actions.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses libghostty_vt.terminal, so a change to libghostty_vt.terminal can break muxy_app.model, while a change to muxy_app.model can't break libghostty_vt.terminal.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break muxy_app.model, while a change to muxy_app.model can't break libghostty_vt_sys.bindings.
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.ai, so a change to muxy_app.model.ai can break muxy_app.model, while a change to muxy_app.model can't break muxy_app.model.ai.
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.extensions.manifest, so a change to muxy_app_core.extensions.manifest can break muxy_app.model, while a change to muxy_app.model can't break muxy_app_core.extensions.manifest.
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.state, so a change to muxy_app_core.state can break muxy_app.model, while a change to muxy_app.model can't break muxy_app_core.state.
Position
Below the diagonal: muxy_app.model uses a module listed above it, which is the healthy direction.
muxy_app.model uses muxy_ui.javascript.jsc, so a change to muxy_ui.javascript.jsc can break muxy_app.model, while a change to muxy_app.model can't break muxy_ui.javascript.jsc.
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.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_client.client, so a change to muxy_client.client can break muxy_app.model, while a change to muxy_app.model can't break muxy_client.client.
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.extensions, so a change to muxy_app.model.extensions can break muxy_app.model, while a change to muxy_app.model can't break muxy_app.model.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.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.
35→36 muxy_app.model uses muxy_app.views.tab_activitypart of a loop✕
Connections
2 pairs of types, where a type in muxy_app.model uses a type in muxy_app.views.tab_activity.
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
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.
35→37 muxy_app.model uses muxy_app.model.extensions.localpart of a loop✕
Connections
1 pair of types, where a type in muxy_app.model uses a type in muxy_app.model.extensions.local.
muxy_app.model uses muxy_app.model.extensions.local, so a change to muxy_app.model.extensions.local can break muxy_app.model, while a change to muxy_app.model can't break muxy_app.model.extensions.local.
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.
35→39 muxy_app.model uses muxy_app.bootpart of a loop✕
Connections
3 pairs of types, where a type in muxy_app.model uses a type in muxy_app.boot.
The types involved
muxy_app.model.AppModel → muxy_app.boot.Boot
muxy_app.model.AppModel → muxy_app.boot.Target
muxy_app.model.AppModel → muxy_app.boot.Work
Direction
muxy_app.model uses muxy_app.boot, so a change to muxy_app.boot can break muxy_app.model, while a change to muxy_app.model can't break muxy_app.boot.
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 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 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 libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break muxy_app.views.tab_activity, while a change to muxy_app.views.tab_activity can't break libghostty_vt_sys.bindings.
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, 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
Below the diagonal: muxy_app.views.tab_activity uses a module listed above it, which is the healthy direction.
muxy_app.model.extensions.local uses muxy_app.views.tab_activity, so a change to muxy_app.views.tab_activity can break muxy_app.model.extensions.local, while a change to muxy_app.model.extensions.local can't break muxy_app.views.tab_activity.
Position
Below the diagonal: muxy_app.model.extensions.local uses a module listed above it, which is the healthy direction.
muxy_cli.worker uses muxy_protocol.ids, so a change to muxy_protocol.ids can break muxy_cli.worker, while a change to muxy_cli.worker can't break muxy_protocol.ids.
Position
Below the diagonal: muxy_cli.worker uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in muxy_cli.worker uses a type in muxy_app_core.ids.
The types involved
muxy_cli.worker.Core → muxy_app_core.ids.PaneId
Direction
muxy_cli.worker uses muxy_app_core.ids, so a change to muxy_app_core.ids can break muxy_cli.worker, while a change to muxy_cli.worker can't break muxy_app_core.ids.
Position
Below the diagonal: muxy_cli.worker uses a module listed above it, which is the healthy direction.
muxy_cli.worker uses muxy_core.quick_terminal.geometry, so a change to muxy_core.quick_terminal.geometry can break muxy_cli.worker, while a change to muxy_cli.worker can't break muxy_core.quick_terminal.geometry.
Position
Below the diagonal: muxy_cli.worker uses a module listed above it, which is the healthy direction.
muxy_cli.worker uses muxy_protocol.session, so a change to muxy_protocol.session can break muxy_cli.worker, while a change to muxy_cli.worker can't break muxy_protocol.session.
Position
Below the diagonal: muxy_cli.worker uses a module listed above it, which is the healthy direction.
muxy_cli.worker uses muxy_protocol.project, so a change to muxy_protocol.project can break muxy_cli.worker, while a change to muxy_cli.worker can't break muxy_protocol.project.
Position
Below the diagonal: muxy_cli.worker uses a module listed above it, which is the healthy direction.
muxy_cli.worker uses muxy_app.repository_actions, so a change to muxy_app.repository_actions can break muxy_cli.worker, while a change to muxy_cli.worker can't break muxy_app.repository_actions.
Position
Below the diagonal: muxy_cli.worker uses a module listed above it, which is the healthy direction.
muxy_cli.worker uses libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break muxy_cli.worker, while a change to muxy_cli.worker can't break libghostty_vt_sys.bindings.
Position
Below the diagonal: muxy_cli.worker uses a module listed above it, which is the healthy direction.
muxy_cli.worker uses muxy_cli.worker.io, so a change to muxy_cli.worker.io can break muxy_cli.worker, while a change to muxy_cli.worker can't break muxy_cli.worker.io.
Position
Below the diagonal: muxy_cli.worker uses a module listed above it, which is the healthy direction.
muxy_cli.worker uses muxy_client.client, so a change to muxy_client.client can break muxy_cli.worker, while a change to muxy_cli.worker can't break muxy_client.client.
Position
Below the diagonal: muxy_cli.worker uses a module listed above it, which is the healthy direction.
muxy_cli.worker uses muxy_app.model.extensions.local, so a change to muxy_app.model.extensions.local can break muxy_cli.worker, while a change to muxy_cli.worker can't break muxy_app.model.extensions.local.
Position
Below the diagonal: muxy_cli.worker uses a module listed above it, which is the healthy direction.
38→39 muxy_cli.worker uses muxy_app.bootpart of a loop✕
Connections
2 pairs of types, where a type in muxy_cli.worker uses a type in muxy_app.boot.
The types involved
muxy_cli.worker.Core → muxy_app.boot.Target
muxy_cli.worker.Worker → muxy_app.boot.Target
Direction
muxy_cli.worker uses muxy_app.boot, so a change to muxy_app.boot can break muxy_cli.worker, while a change to muxy_cli.worker can't break muxy_app.boot.
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.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_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.
muxy_app.boot uses muxy_core.quick_terminal.geometry, so a change to muxy_core.quick_terminal.geometry can break muxy_app.boot, while a change to muxy_app.boot can't break muxy_core.quick_terminal.geometry.
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_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_protocol.git, so a change to muxy_protocol.git can break muxy_app.boot, while a change to muxy_app.boot can't break muxy_protocol.git.
Position
Below the diagonal: muxy_app.boot uses a module listed above it, which is the healthy direction.
muxy_app.boot uses libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break muxy_app.boot, while a change to muxy_app.boot can't break libghostty_vt_sys.bindings.
Position
Below the diagonal: muxy_app.boot uses a module listed above it, which is the healthy direction.
muxy_app.boot uses libghostty_vt.fmt, so a change to libghostty_vt.fmt can break muxy_app.boot, while a change to muxy_app.boot can't break libghostty_vt.fmt.
Position
Below the diagonal: muxy_app.boot uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in muxy_app.boot uses a type in muxy_app.model.ai.
The types involved
muxy_app.boot.Workers → muxy_app.model.ai.Run
Direction
muxy_app.boot uses muxy_app.model.ai, so a change to muxy_app.model.ai can break muxy_app.boot, while a change to muxy_app.boot can't break muxy_app.model.ai.
Position
Below the diagonal: muxy_app.boot uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in muxy_app.boot uses a type in muxy_app_core.state.
The types involved
muxy_app.boot.Boot → muxy_app_core.state.AppState
Direction
muxy_app.boot uses muxy_app_core.state, so a change to muxy_app_core.state can break muxy_app.boot, while a change to muxy_app.boot can't break muxy_app_core.state.
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_client.client, so a change to muxy_client.client can break muxy_app.boot, while a change to muxy_app.boot can't break muxy_client.client.
Position
Below the diagonal: muxy_app.boot uses a module listed above it, which is the healthy direction.
muxy_app.boot uses muxy_cli.worker, so a change to muxy_cli.worker can break muxy_app.boot, while a change to muxy_app.boot can't break muxy_cli.worker.
Position
Below the diagonal: muxy_app.boot uses a module listed above it, which is the healthy direction.
muxy_cli.ui uses muxy_protocol.ids, so a change to muxy_protocol.ids can break muxy_cli.ui, while a change to muxy_cli.ui can't break muxy_protocol.ids.
Position
Below the diagonal: muxy_cli.ui uses a module listed above it, which is the healthy direction.
muxy_cli.ui uses muxy_app.views.terminal.selection, so a change to muxy_app.views.terminal.selection can break muxy_cli.ui, while a change to muxy_cli.ui can't break muxy_app.views.terminal.selection.
Position
Below the diagonal: muxy_cli.ui uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in muxy_cli.ui uses a type in muxy_app_core.ids.
The types involved
muxy_cli.ui.ui$module → muxy_app_core.ids.PaneId
Direction
muxy_cli.ui uses muxy_app_core.ids, so a change to muxy_app_core.ids can break muxy_cli.ui, while a change to muxy_cli.ui can't break muxy_app_core.ids.
Position
Below the diagonal: muxy_cli.ui uses a module listed above it, which is the healthy direction.
muxy_cli.ui uses muxy_core.quick_terminal.geometry, so a change to muxy_core.quick_terminal.geometry can break muxy_cli.ui, while a change to muxy_cli.ui can't break muxy_core.quick_terminal.geometry.
Position
Below the diagonal: muxy_cli.ui uses a module listed above it, which is the healthy direction.
muxy_cli.ui uses muxy_protocol.project, so a change to muxy_protocol.project can break muxy_cli.ui, while a change to muxy_cli.ui can't break muxy_protocol.project.
Position
Below the diagonal: muxy_cli.ui uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in muxy_cli.ui uses a type in muxy_app.repository_actions.
The types involved
muxy_cli.ui.Ui → muxy_app.repository_actions.Mode
Direction
muxy_cli.ui uses muxy_app.repository_actions, so a change to muxy_app.repository_actions can break muxy_cli.ui, while a change to muxy_cli.ui can't break muxy_app.repository_actions.
Position
Below the diagonal: muxy_cli.ui uses a module listed above it, which is the healthy direction.
muxy_cli.ui uses libghostty_vt_sys.bindings, so a change to libghostty_vt_sys.bindings can break muxy_cli.ui, while a change to muxy_cli.ui can't break libghostty_vt_sys.bindings.
Position
Below the diagonal: muxy_cli.ui uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in muxy_cli.ui uses a type in muxy_cli.worker.io.
The types involved
muxy_cli.ui.Ui → muxy_cli.worker.io.Shared
muxy_cli.ui.ui$module → muxy_cli.worker.io.Shared
Direction
muxy_cli.ui uses muxy_cli.worker.io, so a change to muxy_cli.worker.io can break muxy_cli.ui, while a change to muxy_cli.ui can't break muxy_cli.worker.io.
Position
Below the diagonal: muxy_cli.ui uses a module listed above it, which is the healthy direction.
muxy_cli.ui uses muxy_app.model.extensions.local, so a change to muxy_app.model.extensions.local can break muxy_cli.ui, while a change to muxy_cli.ui can't break muxy_app.model.extensions.local.
Position
Below the diagonal: muxy_cli.ui uses a module listed above it, which is the healthy direction.
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
41
High / Critical
A03:2025 — Software Supply Chain Failures
30
High / Critical
A07:2025 — Authentication Failures
11
High / Critical
Roadmap
Begin by establishing type safety in the frontend by integrating a typecheck step and prioritizing the conversion of high-traffic modules. Simultaneously, address the ten security findings related to secrets history, starting with REDACTED and REDACTED, while also resolving the missing architectural decision records. Finally, eliminate swallowed exceptions across the codebase and enable automated dependency review tools to strengthen security and performance monitoring.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No ADRs found finding(s) in ADR Quality.
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.
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 — 52
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 — 565
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 — 49
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 10
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 73 of 73 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 73 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, 639 of 666 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rs, .cjs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`, or lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`, or lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
D10 Test Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 15 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 107 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs, .cjs) and this repository declares a Cargo test suite (repository root, 210 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.
D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A hotspot's complexity is meant to be the worst body its churn actually touched. For crates/muxy-protocol/src/control.rs that could not be established — the complexity reader for the file reports no body extents, or the history carries no per-line attribution — so the row quotes the file's worst body, which the counted changes may never have touched. The churn count is unaffected.
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 (58 contributor(s) across 1200 commit(s) sampled, automation and bot accounts excluded). One of them holds 85% of the history; the other 57 hold 0.3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22'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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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.
R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The filesystem refused the listing or the read of: CLAUDE.md. Every other path was read.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This 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
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
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.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
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 is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
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.
104 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was (anonymous) at 152. A further 30 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 84 — they are counted neither in the figure above nor in this dimension's score. 17 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 84), 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/settings/ghostty/native.rs (TerminalSettings::set_preference at 39), and 12 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.
+ 39 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with (anonymous) (cyclomatic 152), (anonymous) (cyclomatic 93), AppModel::receive_git (cyclomatic 75). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 5.6 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 51 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 186). — Refactoring it lifts Cognitive Complexity from 5.3 to about 5.8/10.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.8 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 55 FileTooLong finding(s) in God Classes — start with mod.rs (5), remote_servers.rs (2), workspace.rs (2). — One of this dimension's main actionable groups (55 warning-level).
Resolve the 18 FunctionTooLong finding(s) in God Classes — start with element.rs (3), boot.rs (2), args.rs. — One of this dimension's main actionable groups (18 warning-level).
Resolve the 17 TooManyMethods finding(s) in God Classes — start with mod.rs (3), model.rs, state.rs. — One of this dimension's main actionable groups (17 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
66 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
+ 19 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 10 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with opener.rs, macos.rs, window.rs. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 9 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with ghostty.rs, consent.rs, dialog.rs. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 6 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with proxy.rs, overlays.rs, extensions.rs. — One of this dimension's main actionable groups (6 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
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-protocol · ×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).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · 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 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with storage.rs, text_input.rs. — One of this dimension's main actionable groups (2 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
767 test methods: 569 unit, 198 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 15 `it`/`test` case(s) across 1 test file(s) declaring at least one; its tier split is read from package names and paths only. The Rust suite contributes 718 `#[test]` function(s) across 210 file(s) declaring at least one; its unit/integration split is Cargo's own — 47 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test. The Python suite contributes 34 test function(s) across 8 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.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 15 tests. Measured on the JavaScript/TypeScript suite only — at least 107 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, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
13 outdated, 0 yanked direct Cargo dependencies. 52 of 54 direct crates were graded against crates.io (0 not published there, 2 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 · ×13
✓ On the Gold path — maintain.
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 991 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 5 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 MIT, 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.
Resolve the 61 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs (5), git.rs (3), catalog.rs (2). — One of this dimension's main actionable groups (61 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 168278 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. 47 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: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
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.
10 finding(s): 0 critical, 10 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 10 REDACTED finding(s) in Secrets (history) — start with REDACTED (9), REDACTED. — One of this dimension's main actionable groups (10 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).
41 finding(s): 0 critical, 41 high, 0 medium, 0 low. 38 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 28 file(s) — `crates/muxy-app/src/cli_install.rs` (line 21), `crates/muxy-app/src/model.rs` (line 444, line 1609), `crates/muxy-app/src/model/banners.rs` (line 110, line 185), `crates/muxy-app/src/model/browsers/mod.rs` (line 250, line 326, line 494, …), `crates/muxy-app/src/model/extensions/calls.rs` (line 164, line 237, line 362, …), … (+23 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
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).
No action in Static Analysis (SAST) — all 38 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 (38 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.
Resolve the 15 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (15). — One of this dimension's main actionable groups (15 warning-level).
Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 4 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 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 482 of the 599 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.
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. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
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.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
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.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
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.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 9 of 10 project(s) that lack one — worth up to 1.8 pts.
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 README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Do you agree with this assessment?
P1 · CI/CD 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 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.
Consider OpenTelemetry tracing/metrics (opentelemetry with tracing-opentelemetry) and a health-check endpoint (a /health route on your axum/actix router) for operability.
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 the language 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.
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.
crates/muxy-app/src/extensions/bridge.js:216 · crates/muxy-app/src/views/webview/bridge.js:80 — 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:216
crates/muxy-app/src/extensions/script.js:6 · crates/muxy-app/src/views/webview/bridge.js:197 — 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:106
(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 Files10.0 / 10Exemplary✓ 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.
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 · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
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.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
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.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. 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.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×5) — crates/muxy-app/src/views/webview/bridge.js:17, crates/muxy-app/src/views/webview/bridge.js:48, crates/muxy-app/src/views/webview/bridge.js:60, …
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×5) — crates/muxy-app/src/views/webview/bridge.js:37, crates/muxy-app/src/views/webview/bridge.js:39, crates/muxy-app/src/views/webview/bridge.js:70, …
What to do
Swallowed exception (empty catch)
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 — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 62 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.
AC7 A11y enforcement — 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 is measured on C# only; JavaScript, Python, Rust, html 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# and Visual Basic comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
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.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
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 included — suite not readable by the collector
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 — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not 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 applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
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: 575 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.
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.
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.
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.
Hotspot: crates/muxy-app/src/model.rs crates/muxy-app/src/model.rs:2157— crates/muxy-app/src/model.rs changed 83 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 50 in AppModel::receive at line 2157. 9 of those changes were fix/bug commits, and the other 74 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 18:42:09 +01:00' --until='2026-10-28 18:42:09 +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:315— crates/muxy-app/src/model/preferences.rs changed 44 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 60 in AppModel::apply_preference at line 315. 2 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 18:42:09 +01:00' --until='2026-10-28 18:42:09 +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:532— crates/muxy-app/src/views/menu.rs changed 33 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 59 in AppModel::perform_menu at line 532. 3 of those changes were fix/bug commits, 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 18:42:09 +01:00' --until='2026-10-28 18:42:09 +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/boot.rs crates/muxy-app/src/boot.rs:387— crates/muxy-app/src/boot.rs changed 29 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 49 in Work::name at line 387. 2 of those changes were fix/bug commits, and the other 27 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 18:42:09 +01:00' --until='2026-10-28 18:42:09 +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-app/src/views/overlays.rs crates/muxy-app/src/views/overlays.rs:164— crates/muxy-app/src/views/overlays.rs changed 31 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in muxy_app::views::overlays::layer at line 164. 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 18:42:09 +01:00' --until='2026-10-28 18:42:09 +01:00' --full-history --no-merges -- crates/muxy-app/src/views/overlays.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:380— crates/muxy-app/src/model/git.rs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 75 in AppModel::receive_git at line 380. 1 of those changes was a fix/bug commit, and the other 10 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 18:42:09 +01:00' --until='2026-10-28 18:42:09 +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/connection/reader.rs crates/muxy-server/src/connection/reader.rs:289— crates/muxy-server/src/connection/reader.rs changed 20 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in muxy_server::connection::reader::ordered_request at line 289. 1 of those changes was a fix/bug commit, and the other 19 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 18:42:09 +01:00' --until='2026-10-28 18:42:09 +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/settings/appearance.rs crates/muxy-app/src/views/settings/appearance.rs:15— crates/muxy-app/src/views/settings/appearance.rs changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in muxy_app::views::settings::appearance::rows at line 15. 1 of those changes was a fix/bug commit, and the other 16 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 18:42:09 +01:00' --until='2026-10-28 18:42:09 +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/views/workspace.rs crates/muxy-app/src/views/workspace.rs:861— crates/muxy-app/src/views/workspace.rs changed 44 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in AppModel::sync_pane_focus at line 861. 3 of those changes were fix/bug commits, and the other 41 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 18:42:09 +01:00' --until='2026-10-28 18:42:09 +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-server/src/session/owner.rs crates/muxy-server/src/session/owner.rs:276— crates/muxy-server/src/session/owner.rs changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in Owner::serve at line 276. 4 of those changes were fix/bug commits, and the other 19 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 18:42:09 +01:00' --until='2026-10-28 18:42:09 +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/terminal/pane.rs crates/muxy-app/src/views/terminal/pane.rs:1487— crates/muxy-app/src/views/terminal/pane.rs changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in TerminalPane::key_binding at line 1487. 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 18:42:09 +01:00' --until='2026-10-28 18:42:09 +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-protocol/src/validate.rs crates/muxy-protocol/src/validate.rs:259— crates/muxy-protocol/src/validate.rs changed 20 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in muxy_protocol::validate::validate_reply at line 259. 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 18:42:09 +01:00' --until='2026-10-28 18:42:09 +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-ui/src/picker.rs crates/muxy-ui/src/picker.rs:1182— crates/muxy-ui/src/picker.rs changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in Picker::render_item at line 1182. 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 18:42:09 +01:00' --until='2026-10-28 18:42:09 +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-core/src/state.rs crates/muxy-app-core/src/state.rs:1014— crates/muxy-app-core/src/state.rs changed 22 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in AppState::validate at line 1014. 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 18:42:09 +01:00' --until='2026-10-28 18:42:09 +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-app/src/model/webviews.rs crates/muxy-app/src/model/webviews.rs:93— crates/muxy-app/src/model/webviews.rs changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in AppModel::sync_webviews at line 93. 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 18:42:09 +01:00' --until='2026-10-28 18:42:09 +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/views/git.rs crates/muxy-app/src/views/git.rs:133— crates/muxy-app/src/views/git.rs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in AppModel::update_git_picker at line 133. 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 18:42:09 +01:00' --until='2026-10-28 18:42:09 +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-server/src/connection/outbox.rs crates/muxy-server/src/connection/outbox.rs:245— crates/muxy-server/src/connection/outbox.rs changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in Outbox::push_control at line 245. 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 18:42:09 +01:00' --until='2026-10-28 18:42:09 +01:00' --full-history --no-merges -- crates/muxy-server/src/connection/outbox.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:172— crates/muxy-app-core/src/settings/keymap.rs changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in Keymap::from_overrides at line 172. 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 18:42:09 +01:00' --until='2026-10-28 18:42:09 +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.
Hotspot: crates/muxy-app/src/views/project_picker.rs crates/muxy-app/src/views/project_picker.rs:302— crates/muxy-app/src/views/project_picker.rs changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in ProjectPicker::sync_picker at line 302. 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 18:42:09 +01:00' --until='2026-10-28 18:42:09 +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/model/catalog.rs crates/muxy-app/src/model/catalog.rs:118— crates/muxy-app/src/model/catalog.rs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in AppModel::receive_catalog at line 118. 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 18:42:09 +01:00' --until='2026-10-28 18:42:09 +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/model/extensions/calls.rs crates/muxy-app/src/model/extensions/calls.rs:16— crates/muxy-app/src/model/extensions/calls.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 18:42:09 +01:00' --until='2026-10-28 18:42:09 +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/views/terminal/element.rs crates/muxy-app/src/views/terminal/element.rs:870— crates/muxy-app/src/views/terminal/element.rs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in muxy_app::views::terminal::element::paint at line 870. 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 18:42:09 +01:00' --until='2026-10-28 18:42:09 +01:00' --full-history --no-merges -- crates/muxy-app/src/views/terminal/element.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/window.rs crates/muxy-app/src/views/settings/window.rs:155— crates/muxy-app/src/views/settings/window.rs changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in SettingsWindow::open_picker at line 155. 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 18:42:09 +01:00' --until='2026-10-28 18:42:09 +01:00' --full-history --no-merges -- crates/muxy-app/src/views/settings/window.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:192— crates/muxy-app/src/model/extensions/mod.rs changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in AppModel::extension_client at line 192. 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 18:42:09 +01:00' --until='2026-10-28 18:42:09 +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/src/views/settings/terminal.rs crates/muxy-app/src/views/settings/terminal.rs:483— crates/muxy-app/src/views/settings/terminal.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in muxy_app::views::settings::terminal::rows at line 483. 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 18:42:09 +01:00' --until='2026-10-28 18:42:09 +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.
FileTooLong: src/model.rs crates/muxy-app/src/model.rs— FileTooLong — 2106 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 96% of them inside a single declaration: AppModel (3 blocks, 111-2799). The bar is 500 significant lines; this is 1606 over it, 4.21× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/picker.rs crates/muxy-ui/src/picker.rs— FileTooLong — 1669 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 65% of them inside a single declaration: Picker (5 blocks, 776-2180). The bar is 500 significant lines; this is 1169 over it, 3.34× 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/text_input.rs crates/muxy-ui/src/text_input.rs— FileTooLong — 1443 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 943 over it, 2.89× 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 — 1309 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 809 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: settings/extensions.rs crates/muxy-app/src/views/settings/extensions.rs— FileTooLong — 1239 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 94% of them inside a single declaration: ExtensionsView (4 blocks, 83-1582). The bar is 500 significant lines; this is 739 over it, 2.48× 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 — 1190 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 690 over it, 2.38× 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 — 1182 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 682 over it, 2.36× 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 — 1171 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 671 over it, 2.34× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: model/webviews.rs crates/muxy-app/src/model/webviews.rs— FileTooLong — 1034 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, 92-1345). The bar is 500 significant lines; this is 534 over it, 2.07× 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 — 961 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 461 over it, 1.92× 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/workspace.rs crates/muxy-app/src/views/workspace.rs— FileTooLong — 884 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 384 over it, 1.77× 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 — 844 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, 20-1098). The bar is 500 significant lines; this is 344 over it, 1.69× 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 — 841 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 341 over it, 1.68× 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 — 829 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 329 over it, 1.66× 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/element.rs crates/muxy-app/src/views/terminal/element.rs— FileTooLong — 807 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 307 over it, 1.61× 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/project_picker.rs crates/muxy-app/src/views/project_picker.rs— FileTooLong — 782 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 282 over it, 1.56× 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 — 777 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 88% of them inside a single declaration: AppModel (42-954). The bar is 500 significant lines; this is 277 over it, 1.55× 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: platform/macos.rs crates/muxy-ui/src/quick_terminal/platform/macos.rs— FileTooLong — 777 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 277 over it, 1.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: src/worker.rs crates/muxy-cli/src/worker.rs— FileTooLong — 769 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 66% of them inside a single declaration: Core (2 blocks, 213-889). The bar is 500 significant lines; this is 269 over it, 1.54× 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 — 767 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: BrowserView (4 blocks, 104-1021). The bar is 500 significant lines; this is 267 over it, 1.53× 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 — 732 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 232 over it, 1.46× 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 — 715 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 (3 blocks, 67-930). The bar is 500 significant lines; this is 215 over it, 1.43× 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: session/owner.rs crates/muxy-server/src/session/owner.rs— FileTooLong — 704 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 75% of them inside a single declaration: Owner (2 blocks, 79-899). The bar is 500 significant lines; this is 204 over it, 1.41× 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: composer/layout.rs crates/muxy-app/src/views/composer/layout.rs— FileTooLong — 693 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 96% of them inside a single declaration: Composer (37-852). The bar is 500 significant lines; this is 193 over it, 1.39× 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/ghostty.rs crates/muxy-terminal/src/ghostty.rs— FileTooLong — 693 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 79% of them inside a single declaration: Terminal (2 blocks, 82-786). The bar is 500 significant lines; this is 193 over it, 1.39× 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.
AppModel::receive_git (cognitive 105) crates/muxy-app/src/model/git.rs:380— AppModel::receive_git has cognitive complexity 105 (threshold 15). Drivers by points: if/else 34 (72 pts), boolean chains 17, 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::update_git_picker (cognitive 46) crates/muxy-app/src/views/git.rs:133— 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::apply_preference (cognitive 45) crates/muxy-app/src/model/preferences.rs:315— AppModel::apply_preference has cognitive complexity 45 (threshold 15). Drivers by points: if/else 20 (35 pts), match/switch 3 (5 pts), boolean chains 4, loops 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::submit_composer (cognitive 39) crates/muxy-app/src/model/composer.rs:828— 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::receive (cognitive 34) crates/muxy-app/src/model.rs:2157— AppModel::receive has cognitive complexity 34 (threshold 15). Drivers by points: if/else 17 (32 pts), boolean chains 1, 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::sync_extension_events (cognitive 33) crates/muxy-app/src/model/extensions/events.rs:270— 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::sync_visible (cognitive 32) crates/muxy-app/src/model.rs:1641— AppModel::sync_visible has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (27 pts), loops 3, boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
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::running_agents (cognitive 25) crates/muxy-app/src/model/agents_panel.rs:140— AppModel::running_agents has cognitive complexity 25 (threshold 15). Drivers by points: if/else 4 (14 pts), loops 3 (6 pts), match/switch 1 (4 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.
AppModel::receive_catalog (cognitive 25) crates/muxy-app/src/model/catalog.rs:118— AppModel::receive_catalog has cognitive complexity 25 (threshold 15). Drivers by points: if/else 15 (19 pts), boolean chains 3, 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::extension_client (cognitive 23) crates/muxy-app/src/model/extensions/mod.rs:192— 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:499— 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::perform_menu (cognitive 23) crates/muxy-app/src/views/menu.rs:532— AppModel::perform_menu has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 4, match/switch 3 (4 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.
AppModel::sync_webviews (cognitive 22) crates/muxy-app/src/model/webviews.rs:93— AppModel::sync_webviews has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 13, if/else 6 (8 pts), loops 1 (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
AppModel::close_confirmed (cognitive 22) crates/muxy-app/src/model.rs:1347— 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::browser_event (cognitive 21) crates/muxy-app/src/model/browsers/mod.rs:229— 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::check_next_close (cognitive 21) crates/muxy-app/src/model.rs:1198— AppModel::check_next_close has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 4, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppModel::sync_pane_focus (cognitive 21) crates/muxy-app/src/views/workspace.rs:861— AppModel::sync_pane_focus has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 7, 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.
AppModel::discard_pending (cognitive 20) crates/muxy-app/src/model.rs:1521— 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::request_git_context (cognitive 19) crates/muxy-app/src/model/git.rs:207— 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::receive_attached (cognitive 19) crates/muxy-app/src/model.rs:2335— AppModel::receive_attached has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 5 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppModel::receive_attach_failed (cognitive 19) crates/muxy-app/src/model.rs:2407— AppModel::receive_attach_failed has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 4 (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::request_pull_request_action (cognitive 19) crates/muxy-app/src/views/git/pr.rs:118— AppModel::request_pull_request_action has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9, boolean chains 7, match/switch 3. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AppModel::extension_server_call (cognitive 18) crates/muxy-app/src/model/extensions/calls.rs:500— 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.
AppModel::receive_event (cognitive 18) crates/muxy-app/src/model.rs:2611— AppModel::receive_event has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (16 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_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::views::settings::appearance::rows (cognitive 56) crates/muxy-app/src/views/settings/appearance.rs:15— muxy_app::views::settings::appearance::rows has cognitive complexity 56 (threshold 15). Drivers by points: if/else 23 (32 pts), boolean chains 17, loops 5, match/switch 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_app::boot::worker (cognitive 46) crates/muxy-app/src/boot.rs:542— muxy_app::boot::worker has cognitive complexity 46 (threshold 15). Drivers by points: if/else 13 (31 pts), match/switch 4 (12 pts), boolean chains 2, loops 1 (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:870— 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::backup::archive::read (cognitive 36) crates/muxy-app/src/backup/archive.rs:144— muxy_app::backup::archive::read has cognitive complexity 36 (threshold 15). Drivers by points: if/else 17 (26 pts), boolean chains 7, 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::ai::capture (cognitive 34) crates/muxy-app/src/ai.rs:384— muxy_app::ai::capture has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (19 pts), match/switch 4 (10 pts), loops 3 (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.
muxy_app::picker::search::scan (cognitive 30) crates/muxy-app/src/picker/search.rs:198— 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::terminal::element::prepare (cognitive 30) crates/muxy-app/src/views/terminal/element.rs:299— 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 28) crates/muxy-app/src/views/git/form.rs:13— muxy_app::views::git::form::render has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (17 pts), boolean chains 9, 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::terminal::rows (cognitive 25) crates/muxy-app/src/views/settings/terminal.rs:483— muxy_app::views::settings::terminal::rows has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 3 (9 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.
muxy_app::views::settings::server::rows (cognitive 24) crates/muxy-app/src/views/settings/server.rs:7— muxy_app::views::settings::server::rows has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (20 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_app::views::terminal::element::selected_runs (cognitive 22) crates/muxy-app/src/views/terminal/element.rs:445— 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:562— 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::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_activity::status_glyph (cognitive 20) crates/muxy-app/src/views/tab_activity.rs:482— muxy_app::views::tab_activity::status_glyph has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (17 pts), match/switch 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_app::views::terminal::links::detect (cognitive 20) crates/muxy-app/src/views/terminal/links.rs:26— 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::repository_actions::parse_metadata (cognitive 19) crates/muxy-app/src/repository_actions.rs:419— 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::settings::quick_terminal::rows (cognitive 19) crates/muxy-app/src/views/settings/quick_terminal.rs:62— muxy_app::views::settings::quick_terminal::rows has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (18 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
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.
muxy_app::views::agents_panel::header_buttons (cognitive 18) crates/muxy-app/src/views/agents_panel.rs:358— muxy_app::views::agents_panel::header_buttons has cognitive complexity 18 (threshold 15). Drivers by points: if/else 16 (18 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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::tab_strip::drag::move_pointer (cognitive 18) crates/muxy-app/src/views/tab_strip/drag.rs:279— muxy_app::views::tab_strip::drag::move_pointer has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 5, match/switch 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_app::repository_actions::prepare (cognitive 17) crates/muxy-app/src/repository_actions.rs:217— muxy_app::repository_actions::prepare has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11, boolean chains 3, 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.
muxy_app::views::terminal::element::terminal (cognitive 17) crates/muxy-app/src/views/terminal/element.rs:70— muxy_app::views::terminal::element::terminal has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (9 pts), loops 4 (7 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AppModel::receive_git (cyclomatic 75) crates/muxy-app/src/model/git.rs:380— AppModel::receive_git has cyclomatic complexity 75 (threshold 15). To reduce it, separate the cases: extract each independent 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 60) crates/muxy-app/src/model/preferences.rs:315— AppModel::apply_preference has cyclomatic complexity 60 (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 59) crates/muxy-app/src/views/menu.rs:532— AppModel::perform_menu has cyclomatic complexity 59 (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 50) crates/muxy-app/src/model.rs:2157— AppModel::receive has cyclomatic complexity 50 (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 42) crates/muxy-app/src/model/extensions/calls.rs:16— AppModel::dispatch_extension 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.
AppModel::submit_composer (cyclomatic 29) crates/muxy-app/src/model/composer.rs:828— 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::update_git_picker (cyclomatic 27) crates/muxy-app/src/views/git.rs:133— 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::receive_event (cyclomatic 25) crates/muxy-app/src/model.rs:2611— AppModel::receive_event 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.
AppModel::create_terminal_view (cyclomatic 23) crates/muxy-app/src/model.rs:1734— AppModel::create_terminal_view has cyclomatic complexity 23 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
AppModel::perform_server_menu (cyclomatic 23) crates/muxy-app/src/views/server_menu.rs:325— AppModel::perform_server_menu has cyclomatic complexity 23 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
AppModel::request_pull_request_action (cyclomatic 22) crates/muxy-app/src/views/git/pr.rs:118— AppModel::request_pull_request_action has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
AppModel::receive_catalog (cyclomatic 21) crates/muxy-app/src/model/catalog.rs:118— AppModel::receive_catalog 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::sync_extension_events (cyclomatic 21) crates/muxy-app/src/model/extensions/events.rs:270— 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::sync_webviews (cyclomatic 21) crates/muxy-app/src/model/webviews.rs:93— AppModel::sync_webviews has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
AppModel::close_confirmed (cyclomatic 21) crates/muxy-app/src/model.rs:1347— 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::browser_event (cyclomatic 20) crates/muxy-app/src/model/browsers/mod.rs:229— AppModel::browser_event 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.
AppModel::dispatch_webview (cyclomatic 20) crates/muxy-app/src/model/webviews.rs:493— AppModel::dispatch_webview 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:192— 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::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::sync_visible (cyclomatic 17) crates/muxy-app/src/model.rs:1641— AppModel::sync_visible 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 16) crates/muxy-app/src/model/links.rs:143— AppModel::terminal_menu 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.
AppModel::sync_pane_focus (cyclomatic 16) crates/muxy-app/src/views/workspace.rs:861— AppModel::sync_pane_focus 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.
FunctionTooLong: muxy_cli::browser::args::invocation crates/muxy-cli/src/browser/args.rs:138— FunctionTooLong — muxy_cli::browser::args::invocation runs 236 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 136 over it, 2.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::settings::terminal::rows crates/muxy-app/src/views/settings/terminal.rs:483— FunctionTooLong — muxy_app::views::settings::terminal::rows runs 174 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 74 over it, 1.74× 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:15— FunctionTooLong — muxy_app::views::settings::appearance::rows runs 163 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 63 over it, 1.63× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: muxy_server::connection::reader::ordered_request crates/muxy-server/src/connection/reader.rs:289— FunctionTooLong — muxy_server::connection::reader::ordered_request runs 157 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 57 over it, 1.57× 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::overlays::layer crates/muxy-app/src/views/overlays.rs:164— FunctionTooLong — muxy_app::views::overlays::layer runs 152 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 52 over it, 1.52× 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:716— FunctionTooLong — muxy_app::views::sidebar::project_row runs 152 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 52 over it, 1.52× 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:976— FunctionTooLong — muxy_app::boot::perform 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.
FunctionTooLong: muxy_app::views::git::form::render crates/muxy-app/src/views/git/form.rs:13— FunctionTooLong — muxy_app::views::git::form::render runs 134 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 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: muxy_app::boot::worker crates/muxy-app/src/boot.rs:542— 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::views::workspace::action_handlers crates/muxy-app/src/views/workspace.rs:312— FunctionTooLong — muxy_app::views::workspace::action_handlers 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::views::settings::quick_terminal::rows crates/muxy-app/src/views/settings/quick_terminal.rs:62— FunctionTooLong — muxy_app::views::settings::quick_terminal::rows 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.
FunctionTooLong: muxy_app::views::git::ai_provider::render_provider_menu crates/muxy-app/src/views/git/ai_provider.rs:229— FunctionTooLong — muxy_app::views::git::ai_provider::render_provider_menu runs 128 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: muxy_app::views::terminal::element::terminal crates/muxy-app/src/views/terminal/element.rs:70— FunctionTooLong — muxy_app::views::terminal::element::terminal 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:299— 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_app::views::tab_strip::tab_cell crates/muxy-app/src/views/tab_strip.rs:329— FunctionTooLong — muxy_app::views::tab_strip::tab_cell runs 116 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 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: muxy_app::menus crates/muxy-app/src/main.rs:276— FunctionTooLong — muxy_app::menus 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.
FunctionTooLong: muxy_app::views::tab_sidebar::tab_row crates/muxy-app/src/views/tab_sidebar.rs:521— FunctionTooLong — muxy_app::views::tab_sidebar::tab_row 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.
FunctionTooLong: muxy_app::views::terminal::element::paint crates/muxy-app/src/views/terminal/element.rs:870— 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.
TooManyMethods: AppModel crates/muxy-app/src/model.rs:111— TooManyMethods — 912 methods, declared across 83 files: src/model.rs (90), model/webviews.rs (37), extensions/mod.rs (33), model/servers.rs (32), +79 more file(s). The bar is 30 methods; this is 882 over it, 30.40× 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:20— TooManyMethods — 137 methods, declared across 10 files: src/state.rs (57), src/servers.rs (18), src/catalog.rs (16), src/workspace.rs (15), +6 more file(s). The bar is 30 methods; this is 107 over it, 4.57× 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:72— TooManyMethods — 95 methods, declared across 6 files: terminal/pane.rs (68), terminal/find.rs (10), terminal/scrollbar.rs (8), terminal/cursor.rs (4), +2 more file(s). The bar is 30 methods; this is 65 over it, 3.17× 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:513— TooManyMethods — 90 methods. The bar is 30 methods; this is 60 over it, 3.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Client crates/muxy-client/src/client.rs:52— TooManyMethods — 83 methods, declared across 6 files: src/client.rs (48), src/catalog.rs (17), src/asynchronous.rs (8), src/remote.rs (8), +2 more file(s). The bar is 30 methods; this is 53 over it, 2.77× 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: Registry crates/muxy-server/src/registry.rs:46— TooManyMethods — 73 methods, declared across 5 files: src/registry.rs (58), git/worktree.rs (11), git/mod.rs (2), files/mod.rs (1), +1 more file(s). The bar is 30 methods; this is 43 over it, 2.43× 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:194— TooManyMethods — 65 methods, declared across 11 files: settings/mod.rs (24), settings/layout.rs (9), settings/terminal_lists.rs (8), settings/results.rs (7), +7 more file(s). The bar is 30 methods; this is 35 over it, 2.17× 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:16— TooManyMethods — 51 methods, declared across 3 files: git/repository.rs (34), git/pull_requests.rs (9), git/worktrees.rs (8). The bar is 30 methods; this is 21 over it, 1.70× 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:776— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ExtensionsView crates/muxy-app/src/views/settings/extensions.rs:83— TooManyMethods — 45 methods, declared across 3 files: settings/extensions.rs (37), extensions/configuration.rs (4), extensions/updates.rs (4). The bar is 30 methods; this is 15 over it, 1.50× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: NativeBrowser crates/muxy-ui/src/webview/linux/browser.rs:18— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Page crates/muxy-ui/src/webview/linux/page.rs:646— 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: Outbox crates/muxy-server/src/connection/outbox.rs:78— TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Catalog crates/muxy-server/src/catalog/mod.rs:73— TooManyMethods — 36 methods, declared across 6 files: catalog/sessions.rs (12), catalog/mod.rs (10), catalog/git.rs (7), catalog/mutations.rs (4), +2 more file(s). The bar is 30 methods; this is 6 over it, 1.20× 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: Terminal crates/muxy-terminal/src/ghostty.rs:82— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BrowserView crates/muxy-app/src/views/browser/mod.rs:104— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Composer crates/muxy-app/src/views/composer.rs:38— TooManyMethods — 32 methods, declared across 3 files: composer/layout.rs (16), views/composer.rs (14), composer/menu.rs (2). The bar is 30 methods; this is 2 over it, 1.07× 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.
MethodTooLong: Picker.render_item crates/muxy-ui/src/picker.rs:1182— MethodTooLong — render_item runs 281 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 181 over it, 2.81× 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:380— MethodTooLong — receive_git runs 235 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 135 over it, 2.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AppModel.apply_preference crates/muxy-app/src/model/preferences.rs:315— MethodTooLong — apply_preference runs 202 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 102 over it, 2.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: Picker.render crates/muxy-ui/src/picker.rs:1924— MethodTooLong — render runs 190 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 90 over it, 1.90× 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.new crates/muxy-app/src/model.rs:443— MethodTooLong — new runs 185 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 85 over it, 1.85× 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:1627— MethodTooLong — prepaint runs 185 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 85 over it, 1.85× 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:204— MethodTooLong — render runs 172 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 72 over it, 1.72× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AppModel.receive crates/muxy-app/src/model.rs:2157— MethodTooLong — receive 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:532— MethodTooLong — perform_menu 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: AppModel.request_pull_request_action crates/muxy-app/src/views/git/pr.rs:118— MethodTooLong — request_pull_request_action runs 117 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 17 over it, 1.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: 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.dispatch_extension crates/muxy-app/src/model/extensions/calls.rs:16— MethodTooLong — dispatch_extension 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: AppState.restore_configuration crates/muxy-app-core/src/backup/projects.rs:98— MethodTooLong — restore_configuration 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: TerminalSettings.read_source crates/muxy-app-core/src/settings/ghostty.rs:281— MethodTooLong — read_source 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: SettingsWindow.backup_action crates/muxy-app/src/views/settings/backup.rs:113— 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: TerminalSettings.save crates/muxy-app-core/src/settings/ghostty.rs:417— MethodTooLong — save runs 106 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 6 over it, 1.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Dialog.render crates/muxy-ui/src/dialog/view.rs:135— MethodTooLong — render runs 102 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 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×15
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::appearance::rows (cyclomatic 44) crates/muxy-app/src/views/settings/appearance.rs:15— muxy_app::views::settings::appearance::rows has cyclomatic complexity 44 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
muxy_app::views::settings::terminal::rows (cyclomatic 40) crates/muxy-app/src/views/settings/terminal.rs:483— muxy_app::views::settings::terminal::rows has cyclomatic complexity 40 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
muxy_app::boot::worker (cyclomatic 33) crates/muxy-app/src/boot.rs:542— 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 49) 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::views::overlays::layer (cyclomatic 31) crates/muxy-app/src/views/overlays.rs:164— muxy_app::views::overlays::layer 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_app::backup::archive::read (cyclomatic 27) crates/muxy-app/src/backup/archive.rs:144— 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::ai::capture (cyclomatic 22) crates/muxy-app/src/ai.rs:384— muxy_app::ai::capture 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 22) crates/muxy-app/src/views/git/form.rs:13— muxy_app::views::git::form::render has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
muxy_app::views::terminal::element::paint (cyclomatic 22) crates/muxy-app/src/views/terminal/element.rs:870— 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::repository_actions::prepare (cyclomatic 20) crates/muxy-app/src/repository_actions.rs:217— muxy_app::repository_actions::prepare has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
muxy_app::views::settings::terminal::choices (cyclomatic 17) crates/muxy-app/src/views/settings/terminal.rs:281— muxy_app::views::settings::terminal::choices 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.
muxy_app::views::tab_strip::drag::move_pointer (cyclomatic 16) crates/muxy-app/src/views/tab_strip/drag.rs:279— muxy_app::views::tab_strip::drag::move_pointer 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.
muxy_app::views::terminal::element::prepare (cyclomatic 16) crates/muxy-app/src/views/terminal/element.rs:299— 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.
ClassTooLong: AppModel crates/muxy-app/src/model.rs:111— ClassTooLong — 2016 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 912 methods, 3 blocks, lines 111-2799. The bar is 400 significant lines; this is 1616 over it, 5.04× 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: ExtensionsView crates/muxy-app/src/views/settings/extensions.rs:83— ClassTooLong — 1165 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, 4 blocks, lines 83-1582. The bar is 400 significant lines; this is 765 over it, 2.91× 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:776— ClassTooLong — 1085 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 46 methods, 5 blocks, lines 776-2180. The bar is 400 significant lines; this is 685 over it, 2.71× 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:20— ClassTooLong — 805 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 137 methods, 3 blocks, lines 20-1098. The bar is 400 significant lines; this is 405 over it, 2.01× 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:513— ClassTooLong — 752 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 90 methods, 6 blocks, lines 513-1978. The bar is 400 significant lines; this is 352 over it, 1.88× 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:104— 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), 33 methods, 4 blocks, lines 104-1021. 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 — 598 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 73 methods, 2 blocks, lines 46-845. The bar is 400 significant lines; this is 198 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SettingsWindow crates/muxy-app/src/views/settings/window.rs:53— ClassTooLong — 563 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 18 methods, 3 blocks, lines 53-814. The bar is 400 significant lines; this is 163 over it, 1.41× 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:82— ClassTooLong — 546 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 35 methods, 2 blocks, lines 82-786. The bar is 400 significant lines; this is 146 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Owner crates/muxy-server/src/session/owner.rs:79— ClassTooLong — 529 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 18 methods, 2 blocks, lines 79-899. The bar is 400 significant lines; this is 129 over it, 1.32× 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:213— ClassTooLong — 509 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 213-889. The bar is 400 significant lines; this is 109 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Github crates/muxy-server/src/git/github.rs:14— ClassTooLong — 493 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 14 methods, 2 blocks, lines 14-621. The bar is 400 significant lines; this is 93 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (5 lines × 2) crates/muxy-app-core/src/opener.rs:127— crates/muxy-app-core/src/opener.rs:127-131 | crates/muxy-server/src/session/metadata.rs:115-119 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) crates/muxy-app/src/updater/macos.rs:185— crates/muxy-app/src/updater/macos.rs:185-189 | crates/muxy-app/src/updater/macos.rs:298-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.
Duplicated block (5 lines × 2) crates/muxy-app/src/views/settings/window.rs:356— crates/muxy-app/src/views/settings/window.rs:356-360 | crates/muxy-app/src/views/settings/window.rs:412-416 — 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-ui/src/dialog.rs:66— crates/muxy-ui/src/dialog.rs:66-70 | crates/muxy-ui/src/dialog.rs:188-192 — 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-ui/src/voice/linux.rs:129— crates/muxy-ui/src/voice/linux.rs:129-133 | crates/muxy-ui/src/voice/linux.rs:149-158 — 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-app/src/views/browser/mod.rs:841— crates/muxy-app/src/views/browser/mod.rs:841-845 | crates/muxy-app/src/views/webview/mod.rs:295-299 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) crates/muxy-ui/src/picker.rs:51— crates/muxy-ui/src/picker.rs:51-55 | crates/muxy-ui/src/text_input.rs:118-122 — 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:115— crates/muxy-server/src/git/details.rs:115-119 | 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-server/src/files/watch.rs:110— crates/muxy-server/src/files/watch.rs:110-114 | crates/muxy-server/src/git/watch.rs:117-121 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) crates/muxy-app/src/views/project_menu.rs:18— crates/muxy-app/src/views/project_menu.rs:18-22 | crates/muxy-app/src/views/project_menu.rs:143-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.
Swallowed exception (empty catch) crates/muxy-app/src/views/webview/bridge.js:17— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) crates/muxy-app/src/views/webview/bridge.js:37— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) crates/muxy-app/src/views/webview/bridge.js:39— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) crates/muxy-app/src/views/webview/bridge.js:48— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) crates/muxy-app/src/views/webview/bridge.js:60— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) crates/muxy-app/src/views/webview/bridge.js:70— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) crates/muxy-app/src/views/webview/bridge.js:209— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) crates/muxy-app/src/views/webview/bridge.js:220— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) crates/muxy-app/src/views/webview/bridge.js:226— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) crates/muxy-app/src/extensions/bridge.js:259— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
muxy_cli::browser::args::invocation (cyclomatic 34) crates/muxy-cli/src/browser/args.rs:138— 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::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:893— 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 21) crates/muxy-cli/src/manage/mod.rs:76— muxy_cli::manage::execute 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.
muxy_cli::manage::args::parse (cyclomatic 19) crates/muxy-cli/src/manage/args.rs:163— muxy_cli::manage::args::parse has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
muxy_cli::worker::io::reader (cyclomatic 18) crates/muxy-cli/src/worker/io.rs:194— muxy_cli::worker::io::reader 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_server::connection::reader::run (cognitive 48) crates/muxy-server/src/connection/reader.rs:34— 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::git::command::capture_process (cognitive 35) crates/muxy-server/src/git/command.rs:163— muxy_server::git::command::capture_process has cognitive complexity 35 (threshold 15). Drivers by points: if/else 13 (28 pts), boolean chains 3, loops 2, match/switch 1 (2 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_server::git::mutate_files (cognitive 29) crates/muxy-server/src/git/mod.rs:344— 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::git::processes::stop (cognitive 25) crates/muxy-server/src/git/processes.rs:6— muxy_server::git::processes::stop has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 3 (6 pts), boolean chains 4 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_server::exec::supervise (cognitive 23) crates/muxy-server/src/exec.rs:299— muxy_server::exec::supervise has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 7, match/switch 1 (3 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_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::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::connection::forward_events (cognitive 17) crates/muxy-server/src/connection/mod.rs:164— muxy_server::connection::forward_events has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 4, loops 2 (3 pts), match/switch 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
muxy_server::git::details::log (cognitive 17) crates/muxy-server/src/git/details.rs:68— 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.
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::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::manage::execute (cognitive 20) crates/muxy-cli/src/manage/mod.rs:76— muxy_cli::manage::execute has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (16 pts), match/switch 2 (3 pts), boolean chains 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_cli::worker::io::reader (cognitive 20) crates/muxy-cli/src/worker/io.rs:194— muxy_cli::worker::io::reader has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
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:162— 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::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:893— 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.
Duplicated block (6 lines × 2) crates/muxy-app-core/src/settings/ghostty.rs:424— crates/muxy-app-core/src/settings/ghostty.rs:424-429 | crates/muxy-app-core/src/settings/ghostty/native.rs:150-155 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) crates/muxy-app/src/model/extensions/consent.rs:202— crates/muxy-app/src/model/extensions/consent.rs:202-207 | crates/muxy-app/src/model/extensions/consent.rs:295-300 — 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-ui/src/dialog.rs:114— crates/muxy-ui/src/dialog.rs:114-119 | crates/muxy-ui/src/dialog.rs:369-374 — 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:775— crates/muxy-app/src/views/browser/mod.rs:775-780 | crates/muxy-app/src/views/webview/mod.rs:453-458 — 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-protocol/src/remote.rs:334— crates/muxy-protocol/src/remote.rs:334-339 | crates/muxy-server/src/remote/store.rs:145-150 — 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-protocol/src/transport/tls.rs:57— crates/muxy-protocol/src/transport/tls.rs:57-62 | crates/muxy-server/src/remote/mod.rs:430-435 — 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:40— crates/muxy-client/src/catalog.rs:40-45 | crates/muxy-client/src/client.rs:175-180 — 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-mobile/src/files.rs:50— crates/muxy-mobile/src/files.rs:50-55 | crates/muxy-mobile/src/git/repository.rs:40-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) crates/muxy-app/src/views/new_tab.rs:20— crates/muxy-app/src/views/new_tab.rs:20-25 | crates/muxy-app/src/views/theme_picker.rs:17-22 — 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/proxy.rs:316— crates/muxy-app/src/proxy.rs:316-323 | crates/muxy-cli/src/clipboard.rs:65-72 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) crates/muxy-app/src/views/overlays.rs:172— crates/muxy-app/src/views/overlays.rs:172-179 | crates/muxy-app/src/views/overlays.rs:195-202 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) crates/muxy-app/src/views/settings/extensions.rs:507— crates/muxy-app/src/views/settings/extensions.rs:507-514 | crates/muxy-app/src/views/settings/extensions.rs:552-559 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) crates/muxy-cli/src/input.rs:106— crates/muxy-cli/src/input.rs:106-113 | crates/muxy-mobile/src/keys.rs:107-114 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) crates/muxy-server/src/git/mod.rs:63— crates/muxy-server/src/git/mod.rs:63-70 | 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.
Duplicated block (8 lines × 2) crates/muxy-app/src/ai.rs:375— crates/muxy-app/src/ai.rs:375-382 | crates/muxy-server/src/git/command.rs:266-273 — 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.
TerminalPane::metadata (cognitive 26) crates/muxy-app/src/views/terminal/pane.rs:614— 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::key_binding (cognitive 26) crates/muxy-app/src/views/terminal/pane.rs:1487— TerminalPane::key_binding has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 3, 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.
TerminalPane::receive_history (cognitive 20) crates/muxy-app/src/views/terminal/pane.rs:468— 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::focus_changed (cognitive 20) crates/muxy-app/src/views/terminal/pane.rs:797— TerminalPane::focus_changed has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (12 pts), loops 2 (6 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TerminalPane::mouse_wheel (cognitive 16) crates/muxy-app/src/views/terminal/pane.rs:915— 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.
TooManyFields: AppModel crates/muxy-app/src/model.rs:111— TooManyFields — 105 stored fields beside 912 methods. The bar is 30 stored fields; this is 75 over it, 3.50× 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:72— TooManyFields — 52 stored fields beside 95 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: Appearance crates/muxy-app-core/src/settings/appearance.rs:76— TooManyFields — 37 stored fields beside 3 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:194— TooManyFields — 35 stored fields beside 65 methods. The bar is 30 stored fields; this is 5 over it, 1.17× 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:79— TooManyFields — 33 stored fields beside 18 methods. The bar is 30 stored fields; this is 3 over it, 1.10× 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/extensions/items.rs:53— crates/muxy-app/src/model/extensions/items.rs:53-63 | crates/muxy-app/src/model/extensions/items.rs:88-98 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) crates/muxy-app/src/model/webviews.rs:232— crates/muxy-app/src/model/webviews.rs:232-242 | crates/muxy-app/src/model/webviews/panels.rs:509-519 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) crates/muxy-protocol/src/transport/tls.rs:108— crates/muxy-protocol/src/transport/tls.rs:108-118 | crates/muxy-protocol/src/transport/unix.rs:56-66 — 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 (11 lines × 2) crates/muxy-protocol/src/transport/tls.rs:121— crates/muxy-protocol/src/transport/tls.rs:121-131 | crates/muxy-protocol/src/transport/unix.rs:69-79 — 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 (11 lines × 2) crates/muxy-ui/src/dialog.rs:86— crates/muxy-ui/src/dialog.rs:86-96 | crates/muxy-ui/src/dialog.rs:204-214 — 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-core/src/backup/mod.rs:66— crates/muxy-app-core/src/backup/mod.rs:66-75 | crates/muxy-server/src/settings.rs:24-33 — 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:538— crates/muxy-app/src/model/git.rs:538-547 | crates/muxy-app/src/model/git.rs:669-678 — 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:801— crates/muxy-app/src/views/browser/mod.rs:801-810 | crates/muxy-app/src/views/webview/mod.rs:475-484 — 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:59— crates/muxy-app/src/model/extensions/events.rs:59-68 | crates/muxy-app/src/views/tab_activity.rs:652-661 — 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.
Duplicated block (7 lines × 2) crates/muxy-app-core/src/extensions/audit.rs:65— crates/muxy-app-core/src/extensions/audit.rs:65-71 | crates/muxy-app/src/model/extensions/logs.rs:173-179 — 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-client/src/requests.rs:31— crates/muxy-client/src/requests.rs:31-37 | crates/muxy-client/src/requests.rs:91-97 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/muxy-ui/src/spinner.rs:123— crates/muxy-ui/src/spinner.rs:123-129 | crates/muxy-ui/src/webview/host.rs:326-332 — 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-server/src/files/watch.rs:145— crates/muxy-server/src/files/watch.rs:145-151 | crates/muxy-server/src/git/watch.rs:151-157 — 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-app/src/model/extensions/events.rs:299— crates/muxy-app/src/model/extensions/events.rs:299-305 | crates/muxy-app/src/model/extensions/events.rs:310-316 — 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_server::connection::reader::run (cyclomatic 30) crates/muxy-server/src/connection/reader.rs:34— 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. This is NOT this file's highest cyclomatic complexity: muxy_server::connection::reader::ordered_request (cyclomatic 38) 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::mutate_files (cyclomatic 20) crates/muxy-server/src/git/mod.rs:344— 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.
muxy_server::git::command::capture_process (cyclomatic 18) crates/muxy-server/src/git/command.rs:163— muxy_server::git::command::capture_process 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_server::exec::supervise (cyclomatic 17) crates/muxy-server/src/exec.rs:299— muxy_server::exec::supervise 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.
AppState::restore_configuration (cognitive 34) crates/muxy-app-core/src/backup/projects.rs:98— AppState::restore_configuration has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 8 (11 pts), boolean chains 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.
AppState::validate (cognitive 30) crates/muxy-app-core/src/state.rs:1014— AppState::validate has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 6, loops 4 (5 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.
AppState::merge_configuration (cognitive 19) crates/muxy-app-core/src/backup/projects.rs:235— AppState::merge_configuration has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (10 pts), match/switch 2 (5 pts), boolean chains 2, 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.
AppState::merge_catalog (cognitive 17) crates/muxy-app-core/src/catalog.rs:230— 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.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×4
TerminalPane::key_binding (cyclomatic 28) crates/muxy-app/src/views/terminal/pane.rs:1487— TerminalPane::key_binding 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.
TerminalPane::metadata (cyclomatic 23) crates/muxy-app/src/views/terminal/pane.rs:614— 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:468— 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.
BrowserView::handle (cyclomatic 20) crates/muxy-app/src/views/browser/mod.rs:233— 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:731— 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:297— 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.
Registry::apply_worktree (cognitive 43) crates/muxy-server/src/git/worktree.rs:338— Registry::apply_worktree has cognitive complexity 43 (threshold 15). Drivers by points: if/else 17 (38 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 22). To reduce it, split the body into named stages: move each independent 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:70— 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:132— 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.
Core::connected (cognitive 30) crates/muxy-cli/src/worker.rs:349— Core::connected has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (16 pts), match/switch 3 (8 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 19) crates/muxy-cli/src/worker.rs:716— Core::synchronize_pane has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (17 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.
Core::synchronize (cognitive 18) crates/muxy-cli/src/worker.rs:611— 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:591— 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:384— 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.
muxy_ui::webview::host::monitor (cognitive 19) crates/muxy-ui/src/webview/host.rs:670— muxy_ui::webview::host::monitor has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (15 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.
muxy_ui::voice::linux::collect (cognitive 16) crates/muxy-ui/src/voice/linux.rs:341— muxy_ui::voice::linux::collect has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), match/switch 1 (3 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×3
Duplicated block (14 lines × 2) crates/muxy-app/src/ai.rs:491— crates/muxy-app/src/ai.rs:491-504 | crates/muxy-app/src/extensions/io.rs:19-32 — 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 (14 lines × 2) crates/muxy-app/src/model/webviews.rs:702— crates/muxy-app/src/model/webviews.rs:702-715 | crates/muxy-app/src/model/webviews.rs:1292-1305 — 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:95— crates/muxy-app/src/views/agent_sessions.rs:95-108 | crates/muxy-app/src/views/webview/panel.rs:68-81 — 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 (12 lines × 2) crates/muxy-app/src/extensions/io.rs:26— crates/muxy-app/src/extensions/io.rs:26-37 | 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.
Duplicated block (12 lines × 2) crates/muxy-app/src/model/extensions/calls.rs:351— crates/muxy-app/src/model/extensions/calls.rs:351-362 | crates/muxy-app/src/model/extensions/calls.rs:474-485 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) 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.
Duplicated block (9 lines × 2) crates/muxy-app-core/src/backup/projects.rs:396— crates/muxy-app-core/src/backup/projects.rs:396-404 | crates/muxy-app-core/src/backup/projects.rs:612-620 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) crates/muxy-app/src/model/project_layouts.rs:120— crates/muxy-app/src/model/project_layouts.rs:120-128 | crates/muxy-app/src/views/session_picker.rs:42-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) crates/muxy-app/src/views/proxy.rs:430— crates/muxy-app/src/views/proxy.rs:430-438 | crates/muxy-app/src/views/proxy.rs:445-453 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 3) crates/muxy-app/src/model/extensions/workspace.rs:37— crates/muxy-app/src/model/extensions/workspace.rs:37-43 | crates/muxy-app/src/proxy.rs:314-320 | crates/muxy-cli/src/clipboard.rs:63-69 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (7 lines × 3) crates/muxy-app/src/views/overlays.rs:173— crates/muxy-app/src/views/overlays.rs:173-179 | crates/muxy-app/src/views/overlays.rs:196-202 | crates/muxy-app/src/views/overlays.rs:207-213 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 3) crates/muxy-server/src/connection/reader.rs:209— crates/muxy-server/src/connection/reader.rs:209-215 | crates/muxy-server/src/connection/reader.rs:252-258 | crates/muxy-server/src/connection/reader.rs:274-280 — 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.
Picker::render_item (cyclomatic 37) crates/muxy-ui/src/picker.rs:1182— Picker::render_item has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Picker::render (cyclomatic 22) crates/muxy-ui/src/picker.rs:1924— Picker::render has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
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 16) crates/muxy-server/src/session/metadata.rs:37— Metadata::update 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.
TerminalSettings::save (cyclomatic 33) crates/muxy-app-core/src/settings/ghostty.rs:417— TerminalSettings::save has cyclomatic complexity 33 (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.
TerminalSettings::read_source (cyclomatic 28) crates/muxy-app-core/src/settings/ghostty.rs:281— TerminalSettings::read_source 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.
Owner::serve (cyclomatic 30) crates/muxy-server/src/session/owner.rs:276— Owner::serve has cyclomatic complexity 30 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Owner::update_metadata (cyclomatic 16) crates/muxy-server/src/session/owner.rs:678— Owner::update_metadata 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.
muxy_protocol::validate::validate_reply (cyclomatic 29) crates/muxy-protocol/src/validate.rs:259— muxy_protocol::validate::validate_reply has cyclomatic complexity 29 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
muxy_protocol::validate::validate_request (cyclomatic 26) crates/muxy-protocol/src/validate.rs:159— muxy_protocol::validate::validate_request 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.
Registry::dispatch_git (cyclomatic 25) crates/muxy-server/src/git/mod.rs:154— Registry::dispatch_git 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.
Registry::apply_worktree (cyclomatic 22) crates/muxy-server/src/git/worktree.rs:338— Registry::apply_worktree 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.
TextElement::prepaint (cyclomatic 25) crates/muxy-ui/src/text_input.rs:1627— 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:1866— 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:1420— 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 17) crates/muxy-ui/src/webview/host.rs:670— muxy_ui::webview::host::monitor 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. This is NOT this file's highest cyclomatic complexity: muxy_ui::webview::host::native_keystroke (cyclomatic 20) 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_client::bridge::explain (cyclomatic 23) crates/muxy-client/src/bridge.rs:277— 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.
muxy_client::events::next_event (cyclomatic 20) crates/muxy-client/src/events.rs:92— muxy_client::events::next_event 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.
Webview::handle (cyclomatic 22) crates/muxy-app/src/views/webview/mod.rs:200— Webview::handle 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.
Webview::present (cyclomatic 17) crates/muxy-app/src/views/webview/mod.rs:357— 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.
AppState::validate (cyclomatic 22) crates/muxy-app-core/src/state.rs:1014— AppState::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.
AppState::restore_configuration (cyclomatic 19) crates/muxy-app-core/src/backup/projects.rs:98— AppState::restore_configuration 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.
Picker::render_item (cognitive 84) crates/muxy-ui/src/picker.rs:1182— Picker::render_item has cognitive complexity 84 (threshold 15). Drivers by points: if/else 36 (69 pts), boolean chains 8, loops 2 (6 pts), match/switch 1 (nesting depth added 37). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Picker::render (cognitive 23) crates/muxy-ui/src/picker.rs:1924— Picker::render has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 6, match/switch 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TextElement::prepaint (cognitive 47) crates/muxy-ui/src/text_input.rs:1627— 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:1866— 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 19) crates/muxy-server/src/session/metadata.rs:37— Metadata::update has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TerminalSettings::read_source (cognitive 34) crates/muxy-app-core/src/settings/ghostty.rs:281— TerminalSettings::read_source has cognitive complexity 34 (threshold 15). Drivers by points: if/else 11 (23 pts), boolean chains 6, match/switch 2 (4 pts), loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TerminalSettings::save (cognitive 33) crates/muxy-app-core/src/settings/ghostty.rs:417— TerminalSettings::save has cognitive complexity 33 (threshold 15). Drivers by points: if/else 14 (17 pts), loops 6 (9 pts), boolean chains 4, match/switch 2 (3 pts) (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
State::validate (cognitive 34) crates/muxy-cli/src/state.rs:452— 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.
State::close_sessions (cognitive 17) crates/muxy-cli/src/state.rs:340— State::close_sessions has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (11 pts), loops 3 (6 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.
SettingsView::refresh_results (cognitive 32) crates/muxy-app/src/views/settings/results.rs:142— SettingsView::refresh_results has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (23 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::categories (cognitive 16) crates/muxy-app/src/views/settings/layout.rs:105— SettingsView::categories has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 4, loops 2 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
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:8— 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.
ExtensionsView::install (cognitive 22) crates/muxy-app/src/views/settings/extensions.rs:304— ExtensionsView::install has cognitive complexity 22 (threshold 15). Drivers by points: match/switch 4 (11 pts), if/else 9 (10 pts), boolean chains 1 (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.
ExtensionsView::change_extension (cognitive 19) crates/muxy-app/src/views/settings/extensions.rs:411— ExtensionsView::change_extension has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (11 pts), match/switch 4 (6 pts), boolean chains 1, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Webview::present (cognitive 20) crates/muxy-app/src/views/webview/mod.rs:357— 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.
Webview::handle (cognitive 18) crates/muxy-app/src/views/webview/mod.rs:200— Webview::handle has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (12 pts), boolean chains 3, match/switch 2 (3 pts) (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.
(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:106— (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.
muxy_protocol::validate::validate_reply (cognitive 18) crates/muxy-protocol/src/validate.rs:259— muxy_protocol::validate::validate_reply has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 5, loops 1 (2 pts), match/switch 1 (nesting depth added 5). 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 16) crates/muxy-protocol/src/validate.rs:159— muxy_protocol::validate::validate_request has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), match/switch 1 (nesting depth added 6). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Duplicated block (9 lines × 3) crates/muxy-app/src/views/confirm.rs:71— crates/muxy-app/src/views/confirm.rs:71-79 | crates/muxy-app/src/views/confirm.rs:297-305 | crates/muxy-app/src/views/project_menu.rs:306-314 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (9 lines × 3) crates/muxy-app/src/views/font_picker.rs:92— crates/muxy-app/src/views/font_picker.rs:92-100 | crates/muxy-app/src/views/settings/languages.rs:117-125 | crates/muxy-ui/src/command_palette.rs:364-372 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Off the main sequence: muxy-protocol — muxy-protocol: abstractness 0.03, instability 0.00, distance 0.97 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
Off the main sequence: muxy-core — muxy-core: abstractness 0.04, instability 0.00, distance 0.96 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Low cohesion: Settings (LCOM4 10) crates/muxy-app-core/src/extensions/storage.rs:123— 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: TextInput (LCOM4 5) crates/muxy-ui/src/text_input.rs:513— TextInput's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
(anonymous) (cyclomatic 152) crates/muxy-app/src/extensions/bridge.js:1— (anonymous) has cyclomatic complexity 152 (threshold 15). Most of this is not in the body itself: 12 of the 152 points are its own statements and the rest belongs to 142 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 93) crates/muxy-app/src/views/webview/bridge.js:1— (anonymous) has cyclomatic complexity 93 (threshold 15). Most of this is not in the body itself: 6 of the 93 points are its own statements and the rest belongs to 62 function items inside it that branch (open, format, fetch, …). 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 44) crates/muxy-app-core/src/settings/ghostty/options.rs:273— TerminalOptions::read has cyclomatic complexity 44 (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) (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.
GitRequest::validate (cyclomatic 27) crates/muxy-protocol/src/git.rs:451— GitRequest::validate has cyclomatic complexity 27 (threshold 15). Of this number, 23 points are the body's own statements and 4 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.
muxy_mobile::keys::encode (cyclomatic 25) crates/muxy-mobile/src/keys.rs:39— 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.
SettingsView::refresh_results (cyclomatic 24) crates/muxy-app/src/views/settings/results.rs:142— SettingsView::refresh_results 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.
FontOptions::read (cyclomatic 24) crates/muxy-app-core/src/settings/ghostty/fonts.rs:92— 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.
(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:452— 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.
Delivery::event (cyclomatic 21) crates/muxy-app/src/boot/delivery.rs:23— Delivery::event 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.
Message::validate (cyclomatic 21) crates/muxy-protocol/src/validate.rs:75— Message::validate 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.
ProjectPicker::sync_picker (cyclomatic 20) crates/muxy-app/src/views/project_picker.rs:302— ProjectPicker::sync_picker 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.
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.
Core::connected (cyclomatic 18) crates/muxy-cli/src/worker.rs:349— Core::connected 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.
Requests::route (cyclomatic 18) crates/muxy-server/src/connection/reader.rs:168— Requests::route has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: muxy_server::connection::reader::ordered_request (cyclomatic 38) 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.
Github::lookup_current (cyclomatic 18) crates/muxy-server/src/git/github.rs:411— Github::lookup_current 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.
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:172— 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.
Catalog::begin_mutation (cyclomatic 17) crates/muxy-server/src/catalog/mutations.rs:8— 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.
Outbox::push_control (cyclomatic 17) crates/muxy-server/src/connection/outbox.rs:245— Outbox::push_control 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.
FileWatch::new (cyclomatic 17) crates/muxy-server/src/files/watch.rs:56— FileWatch::new 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_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.
Detector::update (cyclomatic 16) crates/muxy-server/src/detection/mod.rs:193— Detector::update 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.
Terminal::encode_mouse (cyclomatic 16) crates/muxy-terminal/src/ghostty.rs:471— 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.
Cache::snapshot (cyclomatic 16) crates/muxy-terminal/src/graphics.rs:72— Cache::snapshot 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.
(anonymous) (cognitive 186) crates/muxy-app/src/extensions/bridge.js:1— (anonymous) has cognitive complexity 186 (threshold 15). Drivers by points: boolean chains 64, if/else 48 (62 pts), ternaries 27 (35 pts), error handling 8 (17 pts), loops 5 (8 pts) (nesting depth added 34). Of this number, 16 points are the body's own statements and 170 belong to 142 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.
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.
FontOptions::read (cognitive 34) crates/muxy-app-core/src/settings/ghostty/fonts.rs:92— 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.
Cache::snapshot (cognitive 30) crates/muxy-terminal/src/graphics.rs:72— Cache::snapshot has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (24 pts), match/switch 1 (4 pts), boolean chains 1, 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.
FileWatch::new (cognitive 29) crates/muxy-server/src/files/watch.rs:56— FileWatch::new has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 3 (5 pts), boolean chains 3, match/switch 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 28) crates/muxy-app/src/views/project_picker.rs:302— ProjectPicker::sync_picker has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (20 pts), match/switch 4 (6 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.
Outbox::push_control (cognitive 28) crates/muxy-server/src/connection/outbox.rs:245— Outbox::push_control has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (22 pts), boolean chains 6 (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.
Requests::route (cognitive 27) crates/muxy-server/src/connection/reader.rs:168— Requests::route has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (21 pts), match/switch 4 (6 pts) (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Owner::update_metadata (cognitive 26) crates/muxy-server/src/session/owner.rs:678— Owner::update_metadata has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (20 pts), match/switch 1 (3 pts), loops 2, 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.
Root::resolve (cognitive 25) crates/muxy-server/src/files/root.rs:53— Root::resolve has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (22 pts), boolean chains 2, loops 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.
(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.
CachedRow::refresh (cognitive 24) crates/muxy-terminal/src/links.rs:12— 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.
Keymap::from_overrides (cognitive 23) crates/muxy-app-core/src/settings/keymap.rs:172— 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:54— 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.
BrowserView::present (cognitive 21) crates/muxy-app/src/views/browser/mod.rs:731— 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.
muxy_client::bridge::explain (cognitive 21) crates/muxy-client/src/bridge.rs:277— 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.
Delivery::event (cognitive 20) crates/muxy-app/src/boot/delivery.rs:23— Delivery::event has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11, boolean chains 8, match/switch 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.
TerminalOptions::read (cognitive 20) crates/muxy-app-core/src/settings/ghostty/options.rs:273— 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.
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.
GitRequest::validate (cognitive 19) crates/muxy-protocol/src/git.rs:451— GitRequest::validate has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, match/switch 2 (3 pts) (nesting depth added 5). Of this number, 13 points are the body's own statements and 6 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.
Detector::update (cognitive 19) crates/muxy-server/src/detection/mod.rs:193— Detector::update 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.
Github::lookup_current (cognitive 19) crates/muxy-server/src/git/github.rs:411— Github::lookup_current has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 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.
RepositoryWatch::new (cognitive 19) crates/muxy-server/src/git/watch.rs:89— RepositoryWatch::new has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 3, loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RowRenderer::row (cognitive 18) crates/muxy-app/src/views/terminal/element.rs:500— 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.
Target::file (cognitive 18) crates/muxy-app-core/src/opener.rs:56— Target::file has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (17 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.
Terminal::encode_mouse (cognitive 18) crates/muxy-terminal/src/ghostty.rs:471— 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.
Editor::command (cognitive 17) crates/muxy-app/src/opener.rs:307— 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.
Project::sync_groups (cognitive 17) crates/muxy-app-core/src/groups.rs:213— 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.
Dialog::render (cognitive 17) crates/muxy-ui/src/dialog/view.rs:135— Dialog::render has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (4 pts), boolean chains 1, match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
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.
Node::dock (cognitive 16) crates/muxy-app-core/src/layout/docking.rs:152— Node::dock has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 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.
Options::parse (cognitive 16) crates/muxy-cli/src/manage/args.rs:545— 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· Near-duplicate member family (5 members, 17 shared lines) · ×1
Near-duplicate member family (5 members, 17 shared lines) crates/muxy-app/src/views/settings/window.rs:248— crates/muxy-app/src/views/settings/window.rs:248-288 | crates/muxy-app/src/views/settings/window.rs:296-336 | crates/muxy-app/src/views/settings/window.rs:345-395 | crates/muxy-app/src/views/settings/window.rs:404-453 | crates/muxy-app/src/views/settings/window.rs:492-535 — These 5 members are variants of one another: a block of 17 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them 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.
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.
Duplicated block (13 lines × 2) crates/muxy-app/src/model.rs:2042— crates/muxy-app/src/model.rs:2042-2054 | crates/muxy-app/src/model.rs:2076-2088 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11–13 lines × 2) crates/muxy-server/src/git/command.rs:117— crates/muxy-server/src/git/command.rs:117-129 | crates/muxy-server/src/git/github.rs:36-46 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11–12 lines × 2) crates/muxy-server/src/git/github.rs:445— crates/muxy-server/src/git/github.rs:445-455 | crates/muxy-server/src/git/github.rs:468-479 — 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 × 5) crates/muxy-app/src/views/settings/window.rs:279— crates/muxy-app/src/views/settings/window.rs:279-288 | crates/muxy-app/src/views/settings/window.rs:327-336 | crates/muxy-app/src/views/settings/window.rs:386-395 | crates/muxy-app/src/views/settings/window.rs:444-453 | crates/muxy-app/src/views/settings/window.rs:526-535 — 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.
Duplicated block (8–10 lines × 2) crates/muxy-server/src/catalog/storage.rs:15— crates/muxy-server/src/catalog/storage.rs:15-24 | crates/muxy-server/src/remote/store.rs:128-135 — 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–9 lines × 4) crates/muxy-app/src/views/settings/window.rs:315— crates/muxy-app/src/views/settings/window.rs:315-321 | crates/muxy-app/src/views/settings/window.rs:374-380 | crates/muxy-app/src/views/settings/window.rs:432-438 | crates/muxy-app/src/views/settings/window.rs:514-522 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8–9 lines × 2) crates/muxy-app/src/views/remote_servers.rs:1306— crates/muxy-app/src/views/remote_servers.rs:1306-1314 | crates/muxy-app/src/views/remote_servers.rs:1351-1358 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7–8 lines × 5) crates/muxy-app/src/views/settings/window.rs:267— crates/muxy-app/src/views/settings/window.rs:267-273 | crates/muxy-app/src/views/settings/window.rs:313-320 | crates/muxy-app/src/views/settings/window.rs:373-379 | crates/muxy-app/src/views/settings/window.rs:431-437 | crates/muxy-app/src/views/settings/window.rs:513-519 — 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.
Duplicated block (6–7 lines × 2) crates/muxy-server/src/session/metadata/linux.rs:16— crates/muxy-server/src/session/metadata/linux.rs:16-21 | crates/muxy-server/src/session/metadata/linux.rs:50-56 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5–6 lines × 2) crates/muxy-app/src/updater/linux.rs:95— crates/muxy-app/src/updater/linux.rs:95-99 | crates/muxy-app/src/updater/macos.rs:136-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.
Duplicated block (5 lines × 3) crates/muxy-server/src/connection/reader.rs:109— crates/muxy-server/src/connection/reader.rs:109-113 | crates/muxy-server/src/connection/reader.rs:120-124 | crates/muxy-server/src/connection/reader.rs:131-135 — 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.
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:216— crates/muxy-app/src/extensions/bridge.js:216 · crates/muxy-app/src/views/webview/bridge.js:80 — 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:197 — 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:106— 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.
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:333— `!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:226— `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-app/src/model.rs:1522— `!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/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-client/src/local.rs:145— `error.kind() == io::ErrorKind::WouldBlock && Instant::now() < deadline` appears character-identically in 3 files — crates/muxy-client/src/local.rs, crates/muxy-core/src/bundle.rs, crates/muxy-server/src/archive.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/proxy.rs:136— `event.keystroke.key == "tab" && !modifiers.control && !modifiers.alt && !modifiers.platform && !modifiers.function` appears character-identically in 2 files — crates/muxy-app/src/views/proxy.rs, crates/muxy-app/src/views/remote_servers.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/sidebar/resize.rs:57— `model.overlay.is_some() || model.close_prompt.is_some()` appears character-identically in 3 files — crates/muxy-app/src/views/sidebar/resize.rs, crates/muxy-app/src/views/tab_strip/drag.rs, crates/muxy-app/src/views/titlebar.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/quick_terminal.rs:211— `pane.native_visible && pane.grid.is_some()` appears character-identically in 2 files — crates/muxy-app/src/views/quick_terminal.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-server/src/catalog/mod.rs:140— `parent.home || parent.parent_id.is_some() || parent.kind.is_some()` appears character-identically in 2 files — crates/muxy-server/src/catalog/mod.rs, crates/muxy-server/src/git/worktree.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:952— `phase != DispatchPhase::Capture || event.button != MouseButton::Left` appears character-identically in 5 files — crates/muxy-app/src/views/agents_panel.rs, crates/muxy-app/src/views/sidebar/resize.rs, crates/muxy-app/src/views/splits/drag.rs, crates/muxy-app/src/views/tab_strip/drag.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/model/extensions/consent.rs:554— `rest.is_empty() || rest.starts_with('/')` appears character-identically in 2 files — crates/muxy-app/src/model/extensions/consent.rs, crates/muxy-app/src/model/extensions/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/terminal/element.rs:472— `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-app/src/model.rs:1964— `self.is_quick_terminal(pane) && project.id == self.state.home().id` appears character-identically in 2 files — crates/muxy-app/src/model.rs, crates/muxy-app/src/model/links.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/commands.rs:36— `self.name.trim().is_empty() || self.name.len() > 256 || self.name.chars().any(char::is_control)` appears character-identically in 2 files — crates/muxy-app-core/src/settings/commands.rs, crates/muxy-app-core/src/settings/servers.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:750— `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/preferences.rs:56— `self.quitting != Quitting::Idle || self.close_prompt.is_some()` appears character-identically in 2 files — crates/muxy-app/src/model/preferences.rs, crates/muxy-app/src/model/updates.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:681— `self.quitting != Quitting::Idle || self.close_request.is_some()` appears character-identically in 2 files — crates/muxy-app/src/model.rs, crates/muxy-app/src/model/project_layouts.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/remote_servers.rs:972— `self.quitting == Quitting::Idle && self.close_prompt.is_none()` appears character-identically in 2 files — crates/muxy-app/src/model/remote_servers.rs, crates/muxy-app/src/model/server_status.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/composer/layout.rs:450— `self.recording() && self.voice_snapshot.phase != muxy_ui::voice::Phase::Starting` appears character-identically in 2 files — crates/muxy-app/src/views/composer/layout.rs, crates/muxy-app/src/views/composer/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:572— `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:560— `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.
Silent fallback default on Err crates/muxy-app/src/ai.rs:217— `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-ui/src/webview/linux/page.rs:397— `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 — 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/`.
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.4/10. The most over is `crates/muxy-app` (81557 LoC, 166 module-visible types across 31 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: 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.1 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: rustls — `rustls` is locked at 0.23.43 but 0.23.46 is the current stable release on crates.io, and it already satisfies the `"0.23.43"` requirement declared in crates/muxy-protocol/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rustls` 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.5 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.1.8+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: uuid — `uuid` is locked at 1.26.0 but 1.29.0 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 01a1870f-6210-7a49-8394-51bcc179a8d8 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 52 · Warnings: 565 · Recommendations: 36 · Info: 13 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 29-10-2026 @ 09:48 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.