Public report of lapce/floem, published 14 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 14 November 2026, 20:49 UTC · Survey ID cd_db08aff76e6446158ecb8bb53ae2f47f
lapce/floem
Measured 14 November 2026, 20:48 UTC, at code version 1351ffb
Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.
CAI scoreAt riskUp 2 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 82,284 lines of product code in 10 projects, tests not counted · Estimated rebuild effort: about 0.9 person-years · Weakest lens: Event Sourcing, 49
Findings by how serious they are
15 critical641 serious118 minor
21 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 20: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 the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
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. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
40of 40 dimensions measured by tools.
737of 774 findings point to an exact file and line, so you can open each one in the code. The other 37 concern the repository as a whole, such as missing documentation.
40dimensions across 8 lenses, read from 82,284 lines of product code in 10 projects.
lapce/floem is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 61 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Event Sourcing, at 49, is the weakest lens and counts most in the score. The best first step is making event replay repeatable, worth about 11 points. Recording design decisions comes next, worth about 4 points. Raising Event Sourcing to 65 would lift the score to about 68.
Ten pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version and updating the vulnerable packages would close both risks. The two sets of files in separate parts that keep changing together need that dependency made explicit.
The product code is 82,284 lines, about €130,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Event Sourcing rose from 49 to 65, the lowest score rated Strong, the score would rise from 61 to about 68.
Code composition: what the lines of code are
Product code 69%Tests 31%
New since the last survey: 147 findings
These 147 critical or serious findings weren't in the previous survey, on 28 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Code Duplication · Near-duplicate member pair (50 shared lines) src/view/mod.rs
Code Duplication · Near-duplicate member pair (38 shared lines) src/style/values.rs
Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) src/receiver_signal/common/executors.rs
Code Duplication · Edited copy of a member (99 corresponding lines) vello/src/lib.rs
Code Duplication · Edited copy of a member (108 corresponding lines) src/views/editor/keypress/mod.rs
Code Duplication · Edited copy of a member (42 corresponding lines) src/animate/easing.rs
Code Duplication · Edited copy of a member (37 corresponding lines) src/views/dyn_stack.rs
Code Duplication · Edited copy of a member (34 corresponding lines) src/view/id.rs
Code Duplication · Edited copy of a member (52 corresponding lines) src/window/handle.rs
Code Duplication · Edited copy of a member (29 corresponding lines) src/views/editor/text.rs
Code Duplication · Edited copy of a member (39 corresponding lines) src/receiver_signal/resource/builder.rs
Code Duplication · Edited copy of a member (26 corresponding lines) renderer/src/text/attrs.rs
Code Duplication · Edited copy of a member (39 corresponding lines) src/views/slider.rs
Code Duplication · Edited copy of a member (29 corresponding lines) editor-core/src/editor.rs
Code Duplication · Edited copy of a member (37 corresponding lines) src/views/editor/visual_line.rs
Code Duplication · Edited copy of a member (25 corresponding lines) editor-core/src/paragraph.rs
Code Duplication · Edited copy of a member (38 corresponding lines) src/views/editor/visual_line.rs
Code Duplication · Edited copy of a member (30 corresponding lines) src/style/cx.rs
Code Duplication · Edited copy of a member (20 corresponding lines) src/views/label.rs
Code Duplication · Edited copy of a member (12 corresponding lines) src/inspector/mod.rs
Code Duplication · Edited copy of a member (10 corresponding lines) src/style/values.rs
Code Duplication · Edited copy of a member (23 corresponding lines) src/views/editor/mod.rs
Code Duplication · Edited copy of a member (31 corresponding lines) src/views/resizable.rs
Code Duplication · Edited copy of a member (17 corresponding lines) src/views/text_editor.rs
Code Duplication · Edited copy of a member (31 corresponding lines) src/layout/screen.rs
Code Duplication · Edited copies of one member (3 members, 25+ corresponding lines) reactive/src/signal.rs
Code Duplication · Edited copy of a member (16 corresponding lines) src/text/layout.rs
Code Duplication · Edited copy of a member (16 corresponding lines) src/views/container.rs
Code Duplication · Edited copy of a member (17 corresponding lines) src/text/layout.rs
Code Duplication · Edited copy of a member (19 corresponding lines) src/views/radio_button.rs
Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) editor-core/src/word.rs
Code Duplication · Edited copy of a member (18 corresponding lines) src/headless.rs
Code Duplication · Edited copies of one member (3 members, 19+ corresponding lines) src/style/cx.rs
Code Duplication · Edited copy of a member (15 corresponding lines) editor-core/src/buffer/rope_text.rs
Code Duplication · Edited copy of a member (13 corresponding lines) src/view/id.rs
Code Duplication · Edited copy of a member (15 corresponding lines) src/style/theme.rs
Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) src/views/editor/mod.rs
Code Duplication · Edited copies of one member (4 members, 16+ corresponding lines) src/style/mod.rs
Code Duplication · Edited copy of a member (20 corresponding lines) reactive/src/scope.rs
Code Duplication · Edited copy of a member (13 corresponding lines) src/style/mod.rs
Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) src/views/editor/mod.rs
Code Duplication · Edited copy of a member (15 corresponding lines) src/text/layout_state.rs
Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) src/style/custom.rs
Code Duplication · Edited copy of a member (22 corresponding lines) src/action.rs
Code Duplication · Edited copies of one member (4 members, 19+ corresponding lines) src/headless.rs
Code Duplication · Edited copy of a member (17 corresponding lines) editor-core/src/buffer/rope_text.rs
Code Duplication · Edited copy of a member (10 corresponding lines) src/style/unit.rs
Code Duplication · Edited copy of a member (15 corresponding lines) reactive/src/effect.rs
Code Duplication · Edited copy of a member (7 corresponding lines) src/style/values.rs
Code Duplication · Edited copy of a member (9 corresponding lines) src/style/mod.rs
Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) reactive/src/derived.rs
Code Duplication · Edited copy of a member (15 corresponding lines) src/style/mod.rs
Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) reactive/src/effect.rs
Code Duplication · Edited copy of a member (9 corresponding lines) editor-core/src/selection.rs
Code Duplication · Edited copy of a member (15 corresponding lines) editor-core/src/word.rs
Code Duplication · Edited copy of a member (9 corresponding lines) src/style/values.rs
Code Duplication · Edited copies of one member (5 members, 15+ corresponding lines) src/receiver_signal/channel_signal/builder.rs
Code Duplication · Edited copies of one member (5 members, 1+ corresponding lines) src/style/theme.rs
Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) src/views/rich_text.rs
Code Duplication · Edited copy of a member (13 corresponding lines) tiny_skia/src/lib.rs
Code Duplication · Edited copy of a member (12 corresponding lines) src/views/rich_text.rs
Code Duplication · Edited copies of one member (6 members, 9+ corresponding lines) src/style/values.rs
Code Duplication · Edited copy of a member (13 corresponding lines) editor-core/src/buffer/mod.rs
Code Duplication · Edited copy of a member (11 corresponding lines) reactive/src/signal.rs
Code Duplication · Edited copy of a member (19 corresponding lines) src/views/editor/movement.rs
Code Duplication · Edited copy of a member (12 corresponding lines) src/views/img.rs
Code Duplication · Edited copy of a member (10 corresponding lines) reactive/src/read.rs
Code Duplication · Edited copy of a member (13 corresponding lines) src/views/editor/visual_line.rs
Code Duplication · Edited copy of a member (11 corresponding lines) reactive/src/derived.rs
Code Duplication · Edited copy of a member (9 corresponding lines) reactive/src/derived.rs
Code Duplication · Edited copy of a member (13 corresponding lines) src/views/decorator.rs
Code Duplication · Edited copy of a member (12 corresponding lines) src/window/state.rs
Code Duplication · Edited copies of one member (7 members, 12+ corresponding lines) src/style/mod.rs
Code Duplication · Edited copy of a member (13 corresponding lines) src/views/stack.rs
Code Duplication · Edited copy of a member (14 corresponding lines) editor-core/src/buffer/rope_text.rs
Code Duplication · Edited copy of a member (8 corresponding lines) editor-core/src/selection.rs
Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) src/view/id.rs
Code Duplication · Edited copies of one member (6 members, 15+ corresponding lines) src/view/id.rs
Code Duplication · Edited copy of a member (9 corresponding lines) reactive/src/write.rs
Code Duplication · Edited copy of a member (9 corresponding lines) reactive/src/effect.rs
Code Duplication · Edited copy of a member (11 corresponding lines) src/window/tracking.rs
Code Duplication · Edited copy of a member (8 corresponding lines) src/style/mod.rs
Code Duplication · Edited copy of a member (8 corresponding lines) src/views/label.rs
Code Duplication · Edited copy of a member (11 corresponding lines) src/views/virtual_list.rs
Code Duplication · Edited copy of a member (7 corresponding lines) src/animate/mod.rs
Code Duplication · Edited copy of a member (9 corresponding lines) vello/src/lib.rs
Code Duplication · Edited copy of a member (11 corresponding lines) src/views/virtual_list.rs
Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) skia/src/lib.rs
Code Duplication · Edited copies of one member (4 members, 8+ corresponding lines) src/views/dropdown.rs
Code Duplication · Edited copy of a member (12 corresponding lines) src/views/resizable.rs
Code Duplication · Edited copy of a member (6 corresponding lines) src/style/recalc.rs
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 45 findings
These 45 critical or serious findings were in the previous survey, on 28 October 2026, and are gone from this one.
Code Duplication · Near-duplicate member family (4 members, 21 shared lines) src/receiver_signal/common/executors.rs
Code Duplication · Near-duplicate member pair (33 shared lines) src/receiver_signal/common/executors.rs
Code Duplication · Edited copy of a member (33 corresponding lines) src/platform/context_menu.rs
Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) src/style/mod.rs
€43,000 to €220,000, for 720 to 2,285 hours of work, about 0.9 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.8 at a score of 61. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 82,284 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Stamp clock/random values into the event in the command; the recovery fold must be a pure function of the event.
Raises the score by about 11 points · Medium effort · Fold determinism
2
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.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €130,000 to build again, about 0.9 person-years of work. Its weakest lens is Event Sourcing, at 49 (Weak). Event Sourcing is about whether the stored history the system is built on can be trusted. Because the weakest lens counts most in the score, work on Event Sourcing also moves the score most.
Based on: the rebuild estimate · the Event Sourcing grade · how much each lens counts
What to do: Start with the Event Sourcing actions in Top priorities.
If you do one thing first · First action
Stamp clock/random values into the event in the command; the recovery fold must be a pure function of the event. Of all the actions in this report, it raises the score most for the work it takes: about 11 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.9 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 3% to 6% on every change. The history of the code shows how much it changes: about 179 lines over the last 90 days, which is about 726 lines a year. At that pace, the extra work comes to an estimated 0.1 to 0.3 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
165 modules, with 611 dependencies between them. 9 loops run through 73 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 125 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.
floem.style.props uses floem.style, so a change to floem.style can break floem.style.props, while a change to floem.style.props can't break floem.style.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
floem_editor_core.cursor uses floem_editor_core.mode, so a change to floem_editor_core.mode can break floem_editor_core.cursor, while a change to floem_editor_core.cursor can't break floem_editor_core.mode.
Position
Below the diagonal: floem_editor_core.cursor uses a module listed above it, which is the healthy direction.
5→8 floem_reactive.read uses floem_reactive.signalpart of a loop✕
Connections
2 pairs of types, where a type in floem_reactive.read uses a type in floem_reactive.signal.
floem_reactive.read uses floem_reactive.signal, so a change to floem_reactive.signal can break floem_reactive.read, while a change to floem_reactive.read can't break floem_reactive.signal.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→10 floem_reactive.read uses floem_reactive.idpart of a loop✕
Connections
4 pairs of types, where a type in floem_reactive.read uses a type in floem_reactive.id.
floem_reactive.read uses floem_reactive.id, so a change to floem_reactive.id can break floem_reactive.read, while a change to floem_reactive.read can't break floem_reactive.id.
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.
floem.style.values uses floem.style.props, so a change to floem.style.props can break floem.style.values, while a change to floem.style.values can't break floem.style.props.
Position
Below the diagonal: floem.style.values uses a module listed above it, which is the healthy direction.
6→29 floem.style.values uses floem.stylepart of a loop✕
Connections
2 pairs of types, where a type in floem.style.values uses a type in floem.style.
floem.style.values uses floem.style, so a change to floem.style can break floem.style.values, while a change to floem.style.values can't break floem.style.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
floem.text.layout uses floem_editor_core.cursor, so a change to floem_editor_core.cursor can break floem.text.layout, while a change to floem.text.layout can't break floem_editor_core.cursor.
Position
Below the diagonal: floem.text.layout uses a module listed above it, which is the healthy direction.
floem_reactive.signal uses floem_reactive.read, so a change to floem_reactive.read can break floem_reactive.signal, while a change to floem_reactive.signal can't break floem_reactive.read.
Position
Below the diagonal: floem_reactive.signal uses a module listed above it, which is the healthy direction.
8→10 floem_reactive.signal uses floem_reactive.idpart of a loop✕
Connections
4 pairs of types, where a type in floem_reactive.signal uses a type in floem_reactive.id.
floem_reactive.signal uses floem_reactive.id, so a change to floem_reactive.id can break floem_reactive.signal, while a change to floem_reactive.signal can't break floem_reactive.id.
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.
floem.style.unit uses floem.style.values, so a change to floem.style.values can break floem.style.unit, while a change to floem.style.unit can't break floem.style.values.
Position
Below the diagonal: floem.style.unit uses a module listed above it, which is the healthy direction.
floem_reactive.id uses floem_reactive.signal, so a change to floem_reactive.signal can break floem_reactive.id, while a change to floem_reactive.id can't break floem_reactive.signal.
Position
Below the diagonal: floem_reactive.id uses a module listed above it, which is the healthy direction.
floem.paint uses floem.window.state, so a change to floem.window.state can break floem.paint, while a change to floem.paint can't break floem.window.state.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→36 floem.paint uses floem.view.idpart of a loop✕
Connections
3 pairs of types, where a type in floem.paint uses a type in floem.view.id.
floem_reactive.scope uses floem_reactive.signal, so a change to floem_reactive.signal can break floem_reactive.scope, while a change to floem_reactive.scope can't break floem_reactive.signal.
Position
Below the diagonal: floem_reactive.scope uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in floem_reactive.scope uses a type in floem_reactive.id.
The types involved
floem_reactive.scope.Scope → floem_reactive.id.Id
Direction
floem_reactive.scope uses floem_reactive.id, so a change to floem_reactive.id can break floem_reactive.scope, while a change to floem_reactive.scope can't break floem_reactive.id.
Position
Below the diagonal: floem_reactive.scope uses a module listed above it, which is the healthy direction.
floem.style.cx uses floem_reactive.scope, so a change to floem_reactive.scope can break floem.style.cx, while a change to floem.style.cx can't break floem_reactive.scope.
Position
Below the diagonal: floem.style.cx uses a module listed above it, which is the healthy direction.
13→29 floem.style.cx uses floem.stylepart of a loop✕
Connections
1 pair of types, where a type in floem.style.cx uses a type in floem.style.
The types involved
floem.style.cx.StyleCx → floem.style.Style
Direction
floem.style.cx uses floem.style, so a change to floem.style can break floem.style.cx, while a change to floem.style.cx can't break floem.style.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→32 floem.style.cx uses floem.window.statepart of a loop✕
Connections
1 pair of types, where a type in floem.style.cx uses a type in floem.window.state.
floem.style.cx uses floem.window.state, so a change to floem.window.state can break floem.style.cx, while a change to floem.style.cx can't break floem.window.state.
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→36 floem.style.cx uses floem.view.idpart of a loop✕
Connections
2 pairs of types, where a type in floem.style.cx uses a type in floem.view.id.
The types involved
floem.style.cx.StyleCx → floem.view.id.ViewId
floem.style.cx.cx$module → floem.view.id.ViewId
Direction
floem.style.cx uses floem.view.id, so a change to floem.view.id can break floem.style.cx, while a change to floem.style.cx can't break floem.view.id.
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.
floem.view uses floem_reactive.scope, so a change to floem_reactive.scope can break floem.view, while a change to floem.view can't break floem_reactive.scope.
Position
Below the diagonal: floem.view uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in floem.view uses a type in floem.style.
The types involved
floem.view.View → floem.style.Style
Direction
floem.view uses floem.style, so a change to floem.style can break floem.view, while a change to floem.view can't break floem.style.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→33 floem.view uses floem.messagepart of a loop✕
Connections
1 pair of types, where a type in floem.view uses a type in floem.message.
The types involved
floem.view.View → floem.message.UpdateCx
Direction
floem.view uses floem.message, so a change to floem.message can break floem.view, while a change to floem.view can't break floem.message.
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→35 floem.view uses floem.event.dispatchpart of a loop✕
Connections
1 pair of types, where a type in floem.view uses a type in floem.event.dispatch.
The types involved
floem.view.View → floem.event.dispatch.EventCx
Direction
floem.view uses floem.event.dispatch, so a change to floem.event.dispatch can break floem.view, while a change to floem.view can't break floem.event.dispatch.
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→36 floem.view uses floem.view.idpart of a loop✕
Connections
4 pairs of types, where a type in floem.view uses a type in floem.view.id.
The types involved
floem.view.HasViewId → floem.view.id.ViewId
floem.view.LazyView → floem.view.id.ViewId
floem.view.View → floem.view.id.ViewId
floem.view.view$module → floem.view.id.ViewId
Direction
floem.view uses floem.view.id, so a change to floem.view.id can break floem.view, while a change to floem.view can't break floem.view.id.
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.
floem.style.custom uses floem.view, so a change to floem.view can break floem.style.custom, while a change to floem.style.custom can't break floem.view.
Position
Below the diagonal: floem.style.custom uses a module listed above it, which is the healthy direction.
floem.views.editor.view uses floem.event, so a change to floem.event can break floem.views.editor.view, while a change to floem.views.editor.view can't break floem.event.
Position
Below the diagonal: floem.views.editor.view uses a module listed above it, which is the healthy direction.
floem.views.editor.view uses floem.style.props, so a change to floem.style.props can break floem.views.editor.view, while a change to floem.views.editor.view can't break floem.style.props.
Position
Below the diagonal: floem.views.editor.view uses a module listed above it, which is the healthy direction.
floem.views.editor.view uses floem_editor_core.cursor, so a change to floem_editor_core.cursor can break floem.views.editor.view, while a change to floem.views.editor.view can't break floem_editor_core.cursor.
Position
Below the diagonal: floem.views.editor.view uses a module listed above it, which is the healthy direction.
floem.views.editor.view uses floem_reactive.signal, so a change to floem_reactive.signal can break floem.views.editor.view, while a change to floem.views.editor.view can't break floem_reactive.signal.
Position
Below the diagonal: floem.views.editor.view uses a module listed above it, which is the healthy direction.
floem.views.editor.view uses floem.paint, so a change to floem.paint can break floem.views.editor.view, while a change to floem.views.editor.view can't break floem.paint.
Position
Below the diagonal: floem.views.editor.view uses a module listed above it, which is the healthy direction.
floem.views.editor.view uses floem_reactive.scope, so a change to floem_reactive.scope can break floem.views.editor.view, while a change to floem.views.editor.view can't break floem_reactive.scope.
Position
Below the diagonal: floem.views.editor.view uses a module listed above it, which is the healthy direction.
floem.views.editor.view uses floem.style.cx, so a change to floem.style.cx can break floem.views.editor.view, while a change to floem.views.editor.view can't break floem.style.cx.
Position
Below the diagonal: floem.views.editor.view uses a module listed above it, which is the healthy direction.
floem.views.editor.view uses floem.view, so a change to floem.view can break floem.views.editor.view, while a change to floem.views.editor.view can't break floem.view.
Position
Below the diagonal: floem.views.editor.view uses a module listed above it, which is the healthy direction.
16→18 floem.views.editor.view uses floem.views.editorpart of a loop✕
Connections
3 pairs of types, where a type in floem.views.editor.view uses a type in floem.views.editor.
floem.views.editor.view uses floem.views.editor, so a change to floem.views.editor can break floem.views.editor.view, while a change to floem.views.editor.view can't break floem.views.editor.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→33 floem.views.editor.view uses floem.messagepart of a loop✕
Connections
1 pair of types, where a type in floem.views.editor.view uses a type in floem.message.
floem.views.editor.view uses floem.message, so a change to floem.message can break floem.views.editor.view, while a change to floem.views.editor.view can't break floem.message.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→35 floem.views.editor.view uses floem.event.dispatchpart of a loop✕
Connections
1 pair of types, where a type in floem.views.editor.view uses a type in floem.event.dispatch.
floem.views.editor.view uses floem.event.dispatch, so a change to floem.event.dispatch can break floem.views.editor.view, while a change to floem.views.editor.view can't break floem.event.dispatch.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→36 floem.views.editor.view uses floem.view.idpart of a loop✕
Connections
1 pair of types, where a type in floem.views.editor.view uses a type in floem.view.id.
floem.views.editor.view uses floem.view.id, so a change to floem.view.id can break floem.views.editor.view, while a change to floem.views.editor.view can't break floem.view.id.
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.
floem.views.dropdown uses floem.event, so a change to floem.event can break floem.views.dropdown, while a change to floem.views.dropdown can't break floem.event.
Position
Below the diagonal: floem.views.dropdown uses a module listed above it, which is the healthy direction.
floem.views.dropdown uses floem.style.props, so a change to floem.style.props can break floem.views.dropdown, while a change to floem.views.dropdown can't break floem.style.props.
Position
Below the diagonal: floem.views.dropdown uses a module listed above it, which is the healthy direction.
floem.views.dropdown uses floem_reactive.signal, so a change to floem_reactive.signal can break floem.views.dropdown, while a change to floem.views.dropdown can't break floem_reactive.signal.
Position
Below the diagonal: floem.views.dropdown uses a module listed above it, which is the healthy direction.
floem.views.dropdown uses floem_reactive.scope, so a change to floem_reactive.scope can break floem.views.dropdown, while a change to floem.views.dropdown can't break floem_reactive.scope.
Position
Below the diagonal: floem.views.dropdown uses a module listed above it, which is the healthy direction.
floem.views.dropdown uses floem.style.cx, so a change to floem.style.cx can break floem.views.dropdown, while a change to floem.views.dropdown can't break floem.style.cx.
Position
Below the diagonal: floem.views.dropdown uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in floem.views.dropdown uses a type in floem.view.
The types involved
floem.views.dropdown.Dropdown → floem.view.View
Direction
floem.views.dropdown uses floem.view, so a change to floem.view can break floem.views.dropdown, while a change to floem.views.dropdown can't break floem.view.
Position
Below the diagonal: floem.views.dropdown uses a module listed above it, which is the healthy direction.
floem.views.dropdown uses floem.style.custom, so a change to floem.style.custom can break floem.views.dropdown, while a change to floem.views.dropdown can't break floem.style.custom.
Position
Below the diagonal: floem.views.dropdown uses a module listed above it, which is the healthy direction.
17→29 floem.views.dropdown uses floem.stylepart of a loop✕
Connections
1 pair of types, where a type in floem.views.dropdown uses a type in floem.style.
floem.views.dropdown uses floem.style, so a change to floem.style can break floem.views.dropdown, while a change to floem.views.dropdown can't break floem.style.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→33 floem.views.dropdown uses floem.messagepart of a loop✕
Connections
1 pair of types, where a type in floem.views.dropdown uses a type in floem.message.
floem.views.dropdown uses floem.message, so a change to floem.message can break floem.views.dropdown, while a change to floem.views.dropdown can't break floem.message.
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.
17→35 floem.views.dropdown uses floem.event.dispatchpart of a loop✕
Connections
1 pair of types, where a type in floem.views.dropdown uses a type in floem.event.dispatch.
floem.views.dropdown uses floem.event.dispatch, so a change to floem.event.dispatch can break floem.views.dropdown, while a change to floem.views.dropdown can't break floem.event.dispatch.
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.
17→36 floem.views.dropdown uses floem.view.idpart of a loop✕
Connections
1 pair of types, where a type in floem.views.dropdown uses a type in floem.view.id.
floem.views.dropdown uses floem.view.id, so a change to floem.view.id can break floem.views.dropdown, while a change to floem.views.dropdown can't break floem.view.id.
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.
floem.views.editor uses floem_editor_core.mode, so a change to floem_editor_core.mode can break floem.views.editor, while a change to floem.views.editor can't break floem_editor_core.mode.
Position
Below the diagonal: floem.views.editor uses a module listed above it, which is the healthy direction.
floem.views.editor uses floem_editor_core.cursor, so a change to floem_editor_core.cursor can break floem.views.editor, while a change to floem.views.editor can't break floem_editor_core.cursor.
Position
Below the diagonal: floem.views.editor uses a module listed above it, which is the healthy direction.
floem.views.editor uses floem.text.layout, so a change to floem.text.layout can break floem.views.editor, while a change to floem.views.editor can't break floem.text.layout.
Position
Below the diagonal: floem.views.editor uses a module listed above it, which is the healthy direction.
floem.views.editor uses floem_reactive.signal, so a change to floem_reactive.signal can break floem.views.editor, while a change to floem.views.editor can't break floem_reactive.signal.
Position
Below the diagonal: floem.views.editor uses a module listed above it, which is the healthy direction.
floem.views.editor uses floem_reactive.scope, so a change to floem_reactive.scope can break floem.views.editor, while a change to floem.views.editor can't break floem_reactive.scope.
Position
Below the diagonal: floem.views.editor uses a module listed above it, which is the healthy direction.
floem.views.editor uses floem.views.editor.view, so a change to floem.views.editor.view can break floem.views.editor, while a change to floem.views.editor can't break floem.views.editor.view.
Position
Below the diagonal: floem.views.editor uses a module listed above it, which is the healthy direction.
18→25 floem.views.editor uses floem.views.editor.textpart of a loop✕
Connections
2 pairs of types, where a type in floem.views.editor uses a type in floem.views.editor.text.
floem.views.editor uses floem.views.editor.text, so a change to floem.views.editor.text can break floem.views.editor, while a change to floem.views.editor can't break floem.views.editor.text.
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.
floem.views.resizable uses floem.event, so a change to floem.event can break floem.views.resizable, while a change to floem.views.resizable can't break floem.event.
Position
Below the diagonal: floem.views.resizable uses a module listed above it, which is the healthy direction.
floem.views.resizable uses floem.style.props, so a change to floem.style.props can break floem.views.resizable, while a change to floem.views.resizable can't break floem.style.props.
Position
Below the diagonal: floem.views.resizable uses a module listed above it, which is the healthy direction.
floem.views.resizable uses floem.style.values, so a change to floem.style.values can break floem.views.resizable, while a change to floem.views.resizable can't break floem.style.values.
Position
Below the diagonal: floem.views.resizable uses a module listed above it, which is the healthy direction.
floem.views.resizable uses floem.style.unit, so a change to floem.style.unit can break floem.views.resizable, while a change to floem.views.resizable can't break floem.style.unit.
Position
Below the diagonal: floem.views.resizable uses a module listed above it, which is the healthy direction.
floem.views.resizable uses floem.paint, so a change to floem.paint can break floem.views.resizable, while a change to floem.views.resizable can't break floem.paint.
Position
Below the diagonal: floem.views.resizable uses a module listed above it, which is the healthy direction.
floem.views.resizable uses floem.style.cx, so a change to floem.style.cx can break floem.views.resizable, while a change to floem.views.resizable can't break floem.style.cx.
Position
Below the diagonal: floem.views.resizable uses a module listed above it, which is the healthy direction.
floem.views.resizable uses floem.view, so a change to floem.view can break floem.views.resizable, while a change to floem.views.resizable can't break floem.view.
Position
Below the diagonal: floem.views.resizable uses a module listed above it, which is the healthy direction.
floem.views.resizable uses floem.style.custom, so a change to floem.style.custom can break floem.views.resizable, while a change to floem.views.resizable can't break floem.style.custom.
Position
Below the diagonal: floem.views.resizable uses a module listed above it, which is the healthy direction.
19→29 floem.views.resizable uses floem.stylepart of a loop✕
Connections
3 pairs of types, where a type in floem.views.resizable uses a type in floem.style.
floem.views.resizable uses floem.style, so a change to floem.style can break floem.views.resizable, while a change to floem.views.resizable can't break floem.style.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→33 floem.views.resizable uses floem.messagepart of a loop✕
Connections
2 pairs of types, where a type in floem.views.resizable uses a type in floem.message.
floem.views.resizable uses floem.message, so a change to floem.message can break floem.views.resizable, while a change to floem.views.resizable can't break floem.message.
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.
19→35 floem.views.resizable uses floem.event.dispatchpart of a loop✕
Connections
2 pairs of types, where a type in floem.views.resizable uses a type in floem.event.dispatch.
floem.views.resizable uses floem.event.dispatch, so a change to floem.event.dispatch can break floem.views.resizable, while a change to floem.views.resizable can't break floem.event.dispatch.
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.
19→36 floem.views.resizable uses floem.view.idpart of a loop✕
Connections
3 pairs of types, where a type in floem.views.resizable uses a type in floem.view.id.
floem.views.resizable uses floem.view.id, so a change to floem.view.id can break floem.views.resizable, while a change to floem.views.resizable can't break floem.view.id.
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.
19→37 floem.views.resizable uses floem.box_treepart of a loop✕
Connections
2 pairs of types, where a type in floem.views.resizable uses a type in floem.box_tree.
floem.views.resizable uses floem.box_tree, so a change to floem.box_tree can break floem.views.resizable, while a change to floem.views.resizable can't break floem.box_tree.
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.
floem.views.scroll uses floem.event, so a change to floem.event can break floem.views.scroll, while a change to floem.views.scroll can't break floem.event.
Position
Below the diagonal: floem.views.scroll uses a module listed above it, which is the healthy direction.
floem.views.scroll uses floem.style.props, so a change to floem.style.props can break floem.views.scroll, while a change to floem.views.scroll can't break floem.style.props.
Position
Below the diagonal: floem.views.scroll uses a module listed above it, which is the healthy direction.
floem.views.scroll uses floem.paint, so a change to floem.paint can break floem.views.scroll, while a change to floem.views.scroll can't break floem.paint.
Position
Below the diagonal: floem.views.scroll uses a module listed above it, which is the healthy direction.
floem.views.scroll uses floem.style.cx, so a change to floem.style.cx can break floem.views.scroll, while a change to floem.views.scroll can't break floem.style.cx.
Position
Below the diagonal: floem.views.scroll uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in floem.views.scroll uses a type in floem.view.
The types involved
floem.views.scroll.Scroll → floem.view.View
Direction
floem.views.scroll uses floem.view, so a change to floem.view can break floem.views.scroll, while a change to floem.views.scroll can't break floem.view.
Position
Below the diagonal: floem.views.scroll uses a module listed above it, which is the healthy direction.
floem.views.scroll uses floem.style.custom, so a change to floem.style.custom can break floem.views.scroll, while a change to floem.views.scroll can't break floem.style.custom.
Position
Below the diagonal: floem.views.scroll uses a module listed above it, which is the healthy direction.
20→29 floem.views.scroll uses floem.stylepart of a loop✕
Connections
2 pairs of types, where a type in floem.views.scroll uses a type in floem.style.
floem.views.scroll uses floem.style, so a change to floem.style can break floem.views.scroll, while a change to floem.views.scroll can't break floem.style.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→33 floem.views.scroll uses floem.messagepart of a loop✕
Connections
1 pair of types, where a type in floem.views.scroll uses a type in floem.message.
floem.views.scroll uses floem.message, so a change to floem.message can break floem.views.scroll, while a change to floem.views.scroll can't break floem.message.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→35 floem.views.scroll uses floem.event.dispatchpart of a loop✕
Connections
3 pairs of types, where a type in floem.views.scroll uses a type in floem.event.dispatch.
floem.views.scroll uses floem.event.dispatch, so a change to floem.event.dispatch can break floem.views.scroll, while a change to floem.views.scroll can't break floem.event.dispatch.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→36 floem.views.scroll uses floem.view.idpart of a loop✕
Connections
3 pairs of types, where a type in floem.views.scroll uses a type in floem.view.id.
floem.views.scroll uses floem.view.id, so a change to floem.view.id can break floem.views.scroll, while a change to floem.views.scroll can't break floem.view.id.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→37 floem.views.scroll uses floem.box_treepart of a loop✕
Connections
4 pairs of types, where a type in floem.views.scroll uses a type in floem.box_tree.
floem.views.scroll uses floem.box_tree, so a change to floem.box_tree can break floem.views.scroll, while a change to floem.views.scroll can't break floem.box_tree.
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.
floem.views.slider uses floem.event, so a change to floem.event can break floem.views.slider, while a change to floem.views.slider can't break floem.event.
Position
Below the diagonal: floem.views.slider uses a module listed above it, which is the healthy direction.
floem.views.slider uses floem.style.props, so a change to floem.style.props can break floem.views.slider, while a change to floem.views.slider can't break floem.style.props.
Position
Below the diagonal: floem.views.slider uses a module listed above it, which is the healthy direction.
floem.views.slider uses floem.style.values, so a change to floem.style.values can break floem.views.slider, while a change to floem.views.slider can't break floem.style.values.
Position
Below the diagonal: floem.views.slider uses a module listed above it, which is the healthy direction.
floem.views.slider uses floem.style.unit, so a change to floem.style.unit can break floem.views.slider, while a change to floem.views.slider can't break floem.style.unit.
Position
Below the diagonal: floem.views.slider uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in floem.views.slider uses a type in floem.paint.
The types involved
floem.views.slider.Slider → floem.paint.PaintCx
Direction
floem.views.slider uses floem.paint, so a change to floem.paint can break floem.views.slider, while a change to floem.views.slider can't break floem.paint.
Position
Below the diagonal: floem.views.slider uses a module listed above it, which is the healthy direction.
floem.views.slider uses floem.style.cx, so a change to floem.style.cx can break floem.views.slider, while a change to floem.views.slider can't break floem.style.cx.
Position
Below the diagonal: floem.views.slider uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in floem.views.slider uses a type in floem.view.
The types involved
floem.views.slider.Slider → floem.view.View
Direction
floem.views.slider uses floem.view, so a change to floem.view can break floem.views.slider, while a change to floem.views.slider can't break floem.view.
Position
Below the diagonal: floem.views.slider uses a module listed above it, which is the healthy direction.
floem.views.slider uses floem.style.custom, so a change to floem.style.custom can break floem.views.slider, while a change to floem.views.slider can't break floem.style.custom.
Position
Below the diagonal: floem.views.slider uses a module listed above it, which is the healthy direction.
21→29 floem.views.slider uses floem.stylepart of a loop✕
Connections
2 pairs of types, where a type in floem.views.slider uses a type in floem.style.
floem.views.slider uses floem.style, so a change to floem.style can break floem.views.slider, while a change to floem.views.slider can't break floem.style.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→33 floem.views.slider uses floem.messagepart of a loop✕
Connections
1 pair of types, where a type in floem.views.slider uses a type in floem.message.
floem.views.slider uses floem.message, so a change to floem.message can break floem.views.slider, while a change to floem.views.slider can't break floem.message.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→35 floem.views.slider uses floem.event.dispatchpart of a loop✕
Connections
1 pair of types, where a type in floem.views.slider uses a type in floem.event.dispatch.
floem.views.slider uses floem.event.dispatch, so a change to floem.event.dispatch can break floem.views.slider, while a change to floem.views.slider can't break floem.event.dispatch.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→36 floem.views.slider uses floem.view.idpart of a loop✕
Connections
1 pair of types, where a type in floem.views.slider uses a type in floem.view.id.
The types involved
floem.views.slider.Slider → floem.view.id.ViewId
Direction
floem.views.slider uses floem.view.id, so a change to floem.view.id can break floem.views.slider, while a change to floem.views.slider can't break floem.view.id.
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.
floem.views.editor.text_document uses floem_editor_core.mode, so a change to floem_editor_core.mode can break floem.views.editor.text_document, while a change to floem.views.editor.text_document can't break floem_editor_core.mode.
Position
Below the diagonal: floem.views.editor.text_document uses a module listed above it, which is the healthy direction.
floem.views.editor.text_document uses floem_editor_core.cursor, so a change to floem_editor_core.cursor can break floem.views.editor.text_document, while a change to floem.views.editor.text_document can't break floem_editor_core.cursor.
Position
Below the diagonal: floem.views.editor.text_document uses a module listed above it, which is the healthy direction.
floem.views.editor.text_document uses floem_reactive.signal, so a change to floem_reactive.signal can break floem.views.editor.text_document, while a change to floem.views.editor.text_document can't break floem_reactive.signal.
Position
Below the diagonal: floem.views.editor.text_document uses a module listed above it, which is the healthy direction.
floem.views.editor.text_document uses floem_reactive.scope, so a change to floem_reactive.scope can break floem.views.editor.text_document, while a change to floem.views.editor.text_document can't break floem_reactive.scope.
Position
Below the diagonal: floem.views.editor.text_document uses a module listed above it, which is the healthy direction.
floem.views.editor.text_document uses floem.views.editor, so a change to floem.views.editor can break floem.views.editor.text_document, while a change to floem.views.editor.text_document can't break floem.views.editor.
Position
Below the diagonal: floem.views.editor.text_document uses a module listed above it, which is the healthy direction.
22→25 floem.views.editor.text_document uses floem.views.editor.textpart of a loop✕
Connections
3 pairs of types, where a type in floem.views.editor.text_document uses a type in floem.views.editor.text.
floem.views.editor.text_document uses floem.views.editor.text, so a change to floem.views.editor.text can break floem.views.editor.text_document, while a change to floem.views.editor.text_document can't break floem.views.editor.text.
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.
floem.views.toggle_button uses floem.event, so a change to floem.event can break floem.views.toggle_button, while a change to floem.views.toggle_button can't break floem.event.
Position
Below the diagonal: floem.views.toggle_button uses a module listed above it, which is the healthy direction.
floem.views.toggle_button uses floem.style.props, so a change to floem.style.props can break floem.views.toggle_button, while a change to floem.views.toggle_button can't break floem.style.props.
Position
Below the diagonal: floem.views.toggle_button uses a module listed above it, which is the healthy direction.
floem.views.toggle_button uses floem.style.unit, so a change to floem.style.unit can break floem.views.toggle_button, while a change to floem.views.toggle_button can't break floem.style.unit.
Position
Below the diagonal: floem.views.toggle_button uses a module listed above it, which is the healthy direction.
floem.views.toggle_button uses floem.paint, so a change to floem.paint can break floem.views.toggle_button, while a change to floem.views.toggle_button can't break floem.paint.
Position
Below the diagonal: floem.views.toggle_button uses a module listed above it, which is the healthy direction.
floem.views.toggle_button uses floem.style.cx, so a change to floem.style.cx can break floem.views.toggle_button, while a change to floem.views.toggle_button can't break floem.style.cx.
Position
Below the diagonal: floem.views.toggle_button uses a module listed above it, which is the healthy direction.
floem.views.toggle_button uses floem.view, so a change to floem.view can break floem.views.toggle_button, while a change to floem.views.toggle_button can't break floem.view.
Position
Below the diagonal: floem.views.toggle_button uses a module listed above it, which is the healthy direction.
floem.views.toggle_button uses floem.views.resizable, so a change to floem.views.resizable can break floem.views.toggle_button, while a change to floem.views.toggle_button can't break floem.views.resizable.
Position
Below the diagonal: floem.views.toggle_button uses a module listed above it, which is the healthy direction.
23→29 floem.views.toggle_button uses floem.stylepart of a loop✕
Connections
2 pairs of types, where a type in floem.views.toggle_button uses a type in floem.style.
floem.views.toggle_button uses floem.style, so a change to floem.style can break floem.views.toggle_button, while a change to floem.views.toggle_button can't break floem.style.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→33 floem.views.toggle_button uses floem.messagepart of a loop✕
Connections
1 pair of types, where a type in floem.views.toggle_button uses a type in floem.message.
floem.views.toggle_button uses floem.message, so a change to floem.message can break floem.views.toggle_button, while a change to floem.views.toggle_button can't break floem.message.
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.
23→35 floem.views.toggle_button uses floem.event.dispatchpart of a loop✕
Connections
2 pairs of types, where a type in floem.views.toggle_button uses a type in floem.event.dispatch.
floem.views.toggle_button uses floem.event.dispatch, so a change to floem.event.dispatch can break floem.views.toggle_button, while a change to floem.views.toggle_button can't break floem.event.dispatch.
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.
23→36 floem.views.toggle_button uses floem.view.idpart of a loop✕
Connections
2 pairs of types, where a type in floem.views.toggle_button uses a type in floem.view.id.
floem.views.toggle_button uses floem.view.id, so a change to floem.view.id can break floem.views.toggle_button, while a change to floem.views.toggle_button can't break floem.view.id.
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.
23→37 floem.views.toggle_button uses floem.box_treepart of a loop✕
Connections
2 pairs of types, where a type in floem.views.toggle_button uses a type in floem.box_tree.
floem.views.toggle_button uses floem.box_tree, so a change to floem.box_tree can break floem.views.toggle_button, while a change to floem.views.toggle_button can't break floem.box_tree.
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.
floem.views.text_editor uses floem.paint, so a change to floem.paint can break floem.views.text_editor, while a change to floem.views.text_editor can't break floem.paint.
Position
Below the diagonal: floem.views.text_editor uses a module listed above it, which is the healthy direction.
floem.views.text_editor uses floem_reactive.scope, so a change to floem_reactive.scope can break floem.views.text_editor, while a change to floem.views.text_editor can't break floem_reactive.scope.
Position
Below the diagonal: floem.views.text_editor uses a module listed above it, which is the healthy direction.
floem.views.text_editor uses floem.view, so a change to floem.view can break floem.views.text_editor, while a change to floem.views.text_editor can't break floem.view.
Position
Below the diagonal: floem.views.text_editor uses a module listed above it, which is the healthy direction.
floem.views.text_editor uses floem.views.editor, so a change to floem.views.editor can break floem.views.text_editor, while a change to floem.views.text_editor can't break floem.views.editor.
Position
Below the diagonal: floem.views.text_editor uses a module listed above it, which is the healthy direction.
floem.views.text_editor uses floem.views.editor.text_document, so a change to floem.views.editor.text_document can break floem.views.text_editor, while a change to floem.views.text_editor can't break floem.views.editor.text_document.
Position
Below the diagonal: floem.views.text_editor uses a module listed above it, which is the healthy direction.
24→25 floem.views.text_editor uses floem.views.editor.textpart of a loop✕
Connections
2 pairs of types, where a type in floem.views.text_editor uses a type in floem.views.editor.text.
floem.views.text_editor uses floem.views.editor.text, so a change to floem.views.editor.text can break floem.views.text_editor, while a change to floem.views.text_editor can't break floem.views.editor.text.
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→29 floem.views.text_editor uses floem.stylepart of a loop✕
Connections
2 pairs of types, where a type in floem.views.text_editor uses a type in floem.style.
floem.views.text_editor uses floem.style, so a change to floem.style can break floem.views.text_editor, while a change to floem.views.text_editor can't break floem.style.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→36 floem.views.text_editor uses floem.view.idpart of a loop✕
Connections
1 pair of types, where a type in floem.views.text_editor uses a type in floem.view.id.
floem.views.text_editor uses floem.view.id, so a change to floem.view.id can break floem.views.text_editor, while a change to floem.views.text_editor can't break floem.view.id.
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.
floem.views.editor.text uses floem_editor_core.mode, so a change to floem_editor_core.mode can break floem.views.editor.text, while a change to floem.views.editor.text can't break floem_editor_core.mode.
Position
Below the diagonal: floem.views.editor.text uses a module listed above it, which is the healthy direction.
floem.views.editor.text uses floem_editor_core.cursor, so a change to floem_editor_core.cursor can break floem.views.editor.text, while a change to floem.views.editor.text can't break floem_editor_core.cursor.
Position
Below the diagonal: floem.views.editor.text uses a module listed above it, which is the healthy direction.
floem.views.editor.text uses floem.style.values, so a change to floem.style.values can break floem.views.editor.text, while a change to floem.views.editor.text can't break floem.style.values.
Position
Below the diagonal: floem.views.editor.text uses a module listed above it, which is the healthy direction.
floem.views.editor.text uses floem_reactive.signal, so a change to floem_reactive.signal can break floem.views.editor.text, while a change to floem.views.editor.text can't break floem_reactive.signal.
Position
Below the diagonal: floem.views.editor.text uses a module listed above it, which is the healthy direction.
floem.views.editor.text uses floem_reactive.scope, so a change to floem_reactive.scope can break floem.views.editor.text, while a change to floem.views.editor.text can't break floem_reactive.scope.
Position
Below the diagonal: floem.views.editor.text uses a module listed above it, which is the healthy direction.
floem.views.editor.text uses floem.views.editor.view, so a change to floem.views.editor.view can break floem.views.editor.text, while a change to floem.views.editor.text can't break floem.views.editor.view.
Position
Below the diagonal: floem.views.editor.text uses a module listed above it, which is the healthy direction.
floem.views.editor.text uses floem.views.editor, so a change to floem.views.editor can break floem.views.editor.text, while a change to floem.views.editor.text can't break floem.views.editor.
Position
Below the diagonal: floem.views.editor.text uses a module listed above it, which is the healthy direction.
floem.views.editor.text uses floem.views.text_editor, so a change to floem.views.text_editor can break floem.views.editor.text, while a change to floem.views.editor.text can't break floem.views.text_editor.
Position
Below the diagonal: floem.views.editor.text uses a module listed above it, which is the healthy direction.
floem.views.text_input uses floem.event, so a change to floem.event can break floem.views.text_input, while a change to floem.views.text_input can't break floem.event.
Position
Below the diagonal: floem.views.text_input uses a module listed above it, which is the healthy direction.
floem.views.text_input uses floem.style.props, so a change to floem.style.props can break floem.views.text_input, while a change to floem.views.text_input can't break floem.style.props.
Position
Below the diagonal: floem.views.text_input uses a module listed above it, which is the healthy direction.
floem.views.text_input uses floem_editor_core.cursor, so a change to floem_editor_core.cursor can break floem.views.text_input, while a change to floem.views.text_input can't break floem_editor_core.cursor.
Position
Below the diagonal: floem.views.text_input uses a module listed above it, which is the healthy direction.
floem.views.text_input uses floem.text.layout, so a change to floem.text.layout can break floem.views.text_input, while a change to floem.views.text_input can't break floem.text.layout.
Position
Below the diagonal: floem.views.text_input uses a module listed above it, which is the healthy direction.
floem.views.text_input uses floem_reactive.signal, so a change to floem_reactive.signal can break floem.views.text_input, while a change to floem.views.text_input can't break floem_reactive.signal.
Position
Below the diagonal: floem.views.text_input uses a module listed above it, which is the healthy direction.
floem.views.text_input uses floem.paint, so a change to floem.paint can break floem.views.text_input, while a change to floem.views.text_input can't break floem.paint.
Position
Below the diagonal: floem.views.text_input uses a module listed above it, which is the healthy direction.
floem.views.text_input uses floem.style.cx, so a change to floem.style.cx can break floem.views.text_input, while a change to floem.views.text_input can't break floem.style.cx.
Position
Below the diagonal: floem.views.text_input uses a module listed above it, which is the healthy direction.
floem.views.text_input uses floem.view, so a change to floem.view can break floem.views.text_input, while a change to floem.views.text_input can't break floem.view.
Position
Below the diagonal: floem.views.text_input uses a module listed above it, which is the healthy direction.
floem.views.text_input uses floem.views.editor.text, so a change to floem.views.editor.text can break floem.views.text_input, while a change to floem.views.text_input can't break floem.views.editor.text.
Position
Below the diagonal: floem.views.text_input uses a module listed above it, which is the healthy direction.
26→32 floem.views.text_input uses floem.window.statepart of a loop✕
Connections
1 pair of types, where a type in floem.views.text_input uses a type in floem.window.state.
floem.views.text_input uses floem.window.state, so a change to floem.window.state can break floem.views.text_input, while a change to floem.views.text_input can't break floem.window.state.
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.
26→33 floem.views.text_input uses floem.messagepart of a loop✕
Connections
1 pair of types, where a type in floem.views.text_input uses a type in floem.message.
floem.views.text_input uses floem.message, so a change to floem.message can break floem.views.text_input, while a change to floem.views.text_input can't break floem.message.
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.
26→35 floem.views.text_input uses floem.event.dispatchpart of a loop✕
Connections
1 pair of types, where a type in floem.views.text_input uses a type in floem.event.dispatch.
floem.views.text_input uses floem.event.dispatch, so a change to floem.event.dispatch can break floem.views.text_input, while a change to floem.views.text_input can't break floem.event.dispatch.
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.
26→36 floem.views.text_input uses floem.view.idpart of a loop✕
Connections
1 pair of types, where a type in floem.views.text_input uses a type in floem.view.id.
floem.views.text_input uses floem.view.id, so a change to floem.view.id can break floem.views.text_input, while a change to floem.views.text_input can't break floem.view.id.
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.
floem.views.editor.movement uses floem_editor_core.mode, so a change to floem_editor_core.mode can break floem.views.editor.movement, while a change to floem.views.editor.movement can't break floem_editor_core.mode.
Position
Below the diagonal: floem.views.editor.movement uses a module listed above it, which is the healthy direction.
floem.views.editor.movement uses floem_editor_core.cursor, so a change to floem_editor_core.cursor can break floem.views.editor.movement, while a change to floem.views.editor.movement can't break floem_editor_core.cursor.
Position
Below the diagonal: floem.views.editor.movement uses a module listed above it, which is the healthy direction.
floem.views.editor.movement uses floem.views.editor, so a change to floem.views.editor can break floem.views.editor.movement, while a change to floem.views.editor.movement can't break floem.views.editor.
Position
Below the diagonal: floem.views.editor.movement uses a module listed above it, which is the healthy direction.
floem.views.editor.movement uses floem.views.text_input, so a change to floem.views.text_input can break floem.views.editor.movement, while a change to floem.views.editor.movement can't break floem.views.text_input.
Position
Below the diagonal: floem.views.editor.movement uses a module listed above it, which is the healthy direction.
floem.views.label uses floem.event, so a change to floem.event can break floem.views.label, while a change to floem.views.label can't break floem.event.
Position
Below the diagonal: floem.views.label uses a module listed above it, which is the healthy direction.
floem.views.label uses floem.style.props, so a change to floem.style.props can break floem.views.label, while a change to floem.views.label can't break floem.style.props.
Position
Below the diagonal: floem.views.label uses a module listed above it, which is the healthy direction.
floem.views.label uses floem_editor_core.cursor, so a change to floem_editor_core.cursor can break floem.views.label, while a change to floem.views.label can't break floem_editor_core.cursor.
Position
Below the diagonal: floem.views.label uses a module listed above it, which is the healthy direction.
floem.views.label uses floem.style.values, so a change to floem.style.values can break floem.views.label, while a change to floem.views.label can't break floem.style.values.
Position
Below the diagonal: floem.views.label uses a module listed above it, which is the healthy direction.
floem.views.label uses floem.text.layout, so a change to floem.text.layout can break floem.views.label, while a change to floem.views.label can't break floem.text.layout.
Position
Below the diagonal: floem.views.label uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in floem.views.label uses a type in floem.paint.
The types involved
floem.views.label.Label → floem.paint.PaintCx
Direction
floem.views.label uses floem.paint, so a change to floem.paint can break floem.views.label, while a change to floem.views.label can't break floem.paint.
Position
Below the diagonal: floem.views.label uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in floem.views.label uses a type in floem.style.cx.
The types involved
floem.views.label.Label → floem.style.cx.StyleCx
Direction
floem.views.label uses floem.style.cx, so a change to floem.style.cx can break floem.views.label, while a change to floem.views.label can't break floem.style.cx.
Position
Below the diagonal: floem.views.label uses a module listed above it, which is the healthy direction.
floem.views.label uses floem.style.custom, so a change to floem.style.custom can break floem.views.label, while a change to floem.views.label can't break floem.style.custom.
Position
Below the diagonal: floem.views.label uses a module listed above it, which is the healthy direction.
floem.views.label uses floem.views.text_input, so a change to floem.views.text_input can break floem.views.label, while a change to floem.views.label can't break floem.views.text_input.
Position
Below the diagonal: floem.views.label uses a module listed above it, which is the healthy direction.
28→29 floem.views.label uses floem.stylepart of a loop✕
Connections
3 pairs of types, where a type in floem.views.label uses a type in floem.style.
floem.views.label uses floem.style, so a change to floem.style can break floem.views.label, while a change to floem.views.label can't break floem.style.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→33 floem.views.label uses floem.messagepart of a loop✕
Connections
1 pair of types, where a type in floem.views.label uses a type in floem.message.
The types involved
floem.views.label.Label → floem.message.UpdateCx
Direction
floem.views.label uses floem.message, so a change to floem.message can break floem.views.label, while a change to floem.views.label can't break floem.message.
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→35 floem.views.label uses floem.event.dispatchpart of a loop✕
Connections
1 pair of types, where a type in floem.views.label uses a type in floem.event.dispatch.
floem.views.label uses floem.event.dispatch, so a change to floem.event.dispatch can break floem.views.label, while a change to floem.views.label can't break floem.event.dispatch.
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 floem.views.label uses floem.view.idpart of a loop✕
Connections
1 pair of types, where a type in floem.views.label uses a type in floem.view.id.
The types involved
floem.views.label.Label → floem.view.id.ViewId
Direction
floem.views.label uses floem.view.id, so a change to floem.view.id can break floem.views.label, while a change to floem.views.label can't break floem.view.id.
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.
floem.style uses floem.style.props, so a change to floem.style.props can break floem.style, while a change to floem.style can't break floem.style.props.
Position
Below the diagonal: floem.style uses a module listed above it, which is the healthy direction.
floem.style uses floem.style.values, so a change to floem.style.values can break floem.style, while a change to floem.style can't break floem.style.values.
Position
Below the diagonal: floem.style uses a module listed above it, which is the healthy direction.
floem.style uses floem.views.dropdown, so a change to floem.views.dropdown can break floem.style, while a change to floem.style can't break floem.views.dropdown.
Position
Below the diagonal: floem.style uses a module listed above it, which is the healthy direction.
floem.style uses floem.views.resizable, so a change to floem.views.resizable can break floem.style, while a change to floem.style can't break floem.views.resizable.
Position
Below the diagonal: floem.style uses a module listed above it, which is the healthy direction.
floem.style uses floem.views.scroll, so a change to floem.views.scroll can break floem.style, while a change to floem.style can't break floem.views.scroll.
Position
Below the diagonal: floem.style uses a module listed above it, which is the healthy direction.
floem.style uses floem.views.slider, so a change to floem.views.slider can break floem.style, while a change to floem.style can't break floem.views.slider.
Position
Below the diagonal: floem.style uses a module listed above it, which is the healthy direction.
floem.style uses floem.views.toggle_button, so a change to floem.views.toggle_button can break floem.style, while a change to floem.style can't break floem.views.toggle_button.
Position
Below the diagonal: floem.style uses a module listed above it, which is the healthy direction.
floem.style uses floem.views.label, so a change to floem.views.label can break floem.style, while a change to floem.style can't break floem.views.label.
Position
Below the diagonal: floem.style uses a module listed above it, which is the healthy direction.
floem.inspector uses floem.style.values, so a change to floem.style.values can break floem.inspector, while a change to floem.inspector can't break floem.style.values.
Position
Below the diagonal: floem.inspector uses a module listed above it, which is the healthy direction.
floem.inspector uses floem_reactive.signal, so a change to floem_reactive.signal can break floem.inspector, while a change to floem.inspector can't break floem_reactive.signal.
Position
Below the diagonal: floem.inspector uses a module listed above it, which is the healthy direction.
floem.inspector uses floem.style.unit, so a change to floem.style.unit can break floem.inspector, while a change to floem.inspector can't break floem.style.unit.
Position
Below the diagonal: floem.inspector uses a module listed above it, which is the healthy direction.
floem.inspector uses floem.style.cx, so a change to floem.style.cx can break floem.inspector, while a change to floem.inspector can't break floem.style.cx.
Position
Below the diagonal: floem.inspector uses a module listed above it, which is the healthy direction.
floem.inspector uses floem.views.label, so a change to floem.views.label can break floem.inspector, while a change to floem.inspector can't break floem.views.label.
Position
Below the diagonal: floem.inspector uses a module listed above it, which is the healthy direction.
floem.inspector uses floem.window.state, so a change to floem.window.state can break floem.inspector, while a change to floem.inspector can't break floem.window.state.
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.
30→36 floem.inspector uses floem.view.idpart of a loop✕
Connections
4 pairs of types, where a type in floem.inspector uses a type in floem.view.id.
floem.inspector uses floem.view.id, so a change to floem.view.id can break floem.inspector, while a change to floem.inspector can't break floem.view.id.
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.
30→37 floem.inspector uses floem.box_treepart of a loop✕
Connections
1 pair of types, where a type in floem.inspector uses a type in floem.box_tree.
floem.inspector uses floem.box_tree, so a change to floem.box_tree can break floem.inspector, while a change to floem.inspector can't break floem.box_tree.
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.
floem.view.state uses floem.style.props, so a change to floem.style.props can break floem.view.state, while a change to floem.view.state can't break floem.style.props.
Position
Below the diagonal: floem.view.state uses a module listed above it, which is the healthy direction.
floem.view.state uses floem_reactive.scope, so a change to floem_reactive.scope can break floem.view.state, while a change to floem.view.state can't break floem_reactive.scope.
Position
Below the diagonal: floem.view.state uses a module listed above it, which is the healthy direction.
floem.view.state uses floem.style.cx, so a change to floem.style.cx can break floem.view.state, while a change to floem.view.state can't break floem.style.cx.
Position
Below the diagonal: floem.view.state uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in floem.view.state uses a type in floem.style.
The types involved
floem.view.state.StyleStack → floem.style.Style
floem.view.state.ViewState → floem.style.Style
Direction
floem.view.state uses floem.style, so a change to floem.style can break floem.view.state, while a change to floem.view.state can't break floem.style.
Position
Below the diagonal: floem.view.state uses a module listed above it, which is the healthy direction.
31→36 floem.view.state uses floem.view.idpart of a loop✕
Connections
1 pair of types, where a type in floem.view.state uses a type in floem.view.id.
The types involved
floem.view.state.ViewState → floem.view.id.ViewId
Direction
floem.view.state uses floem.view.id, so a change to floem.view.id can break floem.view.state, while a change to floem.view.state can't break floem.view.id.
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.
31→37 floem.view.state uses floem.box_treepart of a loop✕
Connections
2 pairs of types, where a type in floem.view.state uses a type in floem.box_tree.
floem.view.state uses floem.box_tree, so a change to floem.box_tree can break floem.view.state, while a change to floem.view.state can't break floem.box_tree.
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.
floem.window.state uses floem.style, so a change to floem.style can break floem.window.state, while a change to floem.window.state can't break floem.style.
Position
Below the diagonal: floem.window.state uses a module listed above it, which is the healthy direction.
floem.window.state uses floem.inspector, so a change to floem.inspector can break floem.window.state, while a change to floem.window.state can't break floem.inspector.
Position
Below the diagonal: floem.window.state uses a module listed above it, which is the healthy direction.
32→36 floem.window.state uses floem.view.idpart of a loop✕
Connections
2 pairs of types, where a type in floem.window.state uses a type in floem.view.id.
floem.window.state uses floem.view.id, so a change to floem.view.id can break floem.window.state, while a change to floem.window.state can't break floem.view.id.
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 floem.window.state uses floem.box_treepart of a loop✕
Connections
5 pairs of types, where a type in floem.window.state uses a type in floem.box_tree.
floem.window.state uses floem.box_tree, so a change to floem.box_tree can break floem.window.state, while a change to floem.window.state can't break floem.box_tree.
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.
floem.message uses floem_reactive.scope, so a change to floem_reactive.scope can break floem.message, while a change to floem.message can't break floem_reactive.scope.
Position
Below the diagonal: floem.message uses a module listed above it, which is the healthy direction.
floem.message uses floem.window.state, so a change to floem.window.state can break floem.message, while a change to floem.message can't break floem.window.state.
Position
Below the diagonal: floem.message uses a module listed above it, which is the healthy direction.
33→36 floem.message uses floem.view.idpart of a loop✕
Connections
1 pair of types, where a type in floem.message uses a type in floem.view.id.
floem.views.list uses floem.style.props, so a change to floem.style.props can break floem.views.list, while a change to floem.views.list can't break floem.style.props.
Position
Below the diagonal: floem.views.list uses a module listed above it, which is the healthy direction.
floem.views.list uses floem_reactive.signal, so a change to floem_reactive.signal can break floem.views.list, while a change to floem.views.list can't break floem_reactive.signal.
Position
Below the diagonal: floem.views.list uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in floem.views.list uses a type in floem.style.cx.
The types involved
floem.views.list.Item → floem.style.cx.StyleCx
Direction
floem.views.list uses floem.style.cx, so a change to floem.style.cx can break floem.views.list, while a change to floem.views.list can't break floem.style.cx.
Position
Below the diagonal: floem.views.list uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in floem.views.list uses a type in floem.message.
The types involved
floem.views.list.List → floem.message.UpdateCx
Direction
floem.views.list uses floem.message, so a change to floem.message can break floem.views.list, while a change to floem.views.list can't break floem.message.
Position
Below the diagonal: floem.views.list uses a module listed above it, which is the healthy direction.
34→36 floem.views.list uses floem.view.idpart of a loop✕
Connections
2 pairs of types, where a type in floem.views.list uses a type in floem.view.id.
The types involved
floem.views.list.Item → floem.view.id.ViewId
floem.views.list.List → floem.view.id.ViewId
Direction
floem.views.list uses floem.view.id, so a change to floem.view.id can break floem.views.list, while a change to floem.views.list can't break floem.view.id.
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.
floem.event.dispatch uses floem.event, so a change to floem.event can break floem.event.dispatch, while a change to floem.event.dispatch can't break floem.event.
Position
Below the diagonal: floem.event.dispatch uses a module listed above it, which is the healthy direction.
floem.event.dispatch uses floem.window.state, so a change to floem.window.state can break floem.event.dispatch, while a change to floem.event.dispatch can't break floem.window.state.
Position
Below the diagonal: floem.event.dispatch uses a module listed above it, which is the healthy direction.
floem.event.dispatch uses floem.views.list, so a change to floem.views.list can break floem.event.dispatch, while a change to floem.event.dispatch can't break floem.views.list.
Position
Below the diagonal: floem.event.dispatch uses a module listed above it, which is the healthy direction.
35→36 floem.event.dispatch uses floem.view.idpart of a loop✕
Connections
2 pairs of types, where a type in floem.event.dispatch uses a type in floem.view.id.
floem.event.dispatch uses floem.view.id, so a change to floem.view.id can break floem.event.dispatch, while a change to floem.event.dispatch can't break floem.view.id.
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 floem.event.dispatch uses floem.box_treepart of a loop✕
Connections
10 pairs of types, where a type in floem.event.dispatch uses a type in floem.box_tree.
floem.event.dispatch uses floem.box_tree, so a change to floem.box_tree can break floem.event.dispatch, while a change to floem.event.dispatch can't break floem.box_tree.
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.
floem.view.id uses floem.style.props, so a change to floem.style.props can break floem.view.id, while a change to floem.view.id can't break floem.style.props.
Position
Below the diagonal: floem.view.id uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in floem.view.id uses a type in floem_reactive.scope.
The types involved
floem.view.id.ViewId → floem_reactive.scope.Scope
Direction
floem.view.id uses floem_reactive.scope, so a change to floem_reactive.scope can break floem.view.id, while a change to floem.view.id can't break floem_reactive.scope.
Position
Below the diagonal: floem.view.id uses a module listed above it, which is the healthy direction.
floem.view.id uses floem.view.state, so a change to floem.view.state can break floem.view.id, while a change to floem.view.id can't break floem.view.state.
Position
Below the diagonal: floem.view.id uses a module listed above it, which is the healthy direction.
floem.view.id uses floem.event.dispatch, so a change to floem.event.dispatch can break floem.view.id, while a change to floem.view.id can't break floem.event.dispatch.
Position
Below the diagonal: floem.view.id uses a module listed above it, which is the healthy direction.
36→37 floem.view.id uses floem.box_treepart of a loop✕
Connections
4 pairs of types, where a type in floem.view.id uses a type in floem.box_tree.
floem.views.virtual_stack uses floem.event, so a change to floem.event can break floem.views.virtual_stack, while a change to floem.views.virtual_stack can't break floem.event.
Position
Below the diagonal: floem.views.virtual_stack uses a module listed above it, which is the healthy direction.
floem.views.virtual_stack uses floem_reactive.signal, so a change to floem_reactive.signal can break floem.views.virtual_stack, while a change to floem.views.virtual_stack can't break floem_reactive.signal.
Position
Below the diagonal: floem.views.virtual_stack uses a module listed above it, which is the healthy direction.
floem.views.virtual_stack uses floem.style.cx, so a change to floem.style.cx can break floem.views.virtual_stack, while a change to floem.views.virtual_stack can't break floem.style.cx.
Position
Below the diagonal: floem.views.virtual_stack uses a module listed above it, which is the healthy direction.
floem.views.virtual_stack uses floem.view, so a change to floem.view can break floem.views.virtual_stack, while a change to floem.views.virtual_stack can't break floem.view.
Position
Below the diagonal: floem.views.virtual_stack uses a module listed above it, which is the healthy direction.
floem.views.virtual_stack uses floem.message, so a change to floem.message can break floem.views.virtual_stack, while a change to floem.views.virtual_stack can't break floem.message.
Position
Below the diagonal: floem.views.virtual_stack uses a module listed above it, which is the healthy direction.
floem.views.virtual_stack uses floem.event.dispatch, so a change to floem.event.dispatch can break floem.views.virtual_stack, while a change to floem.views.virtual_stack can't break floem.event.dispatch.
Position
Below the diagonal: floem.views.virtual_stack uses a module listed above it, which is the healthy direction.
floem.views.virtual_stack uses floem.view.id, so a change to floem.view.id can break floem.views.virtual_stack, while a change to floem.views.virtual_stack can't break floem.view.id.
Position
Below the diagonal: floem.views.virtual_stack uses a module listed above it, which is the healthy direction.
floem.window.handle uses floem.event, so a change to floem.event can break floem.window.handle, while a change to floem.window.handle can't break floem.event.
Position
Below the diagonal: floem.window.handle uses a module listed above it, which is the healthy direction.
floem.window.handle uses floem_reactive.signal, so a change to floem_reactive.signal can break floem.window.handle, while a change to floem.window.handle can't break floem_reactive.signal.
Position
Below the diagonal: floem.window.handle uses a module listed above it, which is the healthy direction.
floem.window.handle uses floem.paint, so a change to floem.paint can break floem.window.handle, while a change to floem.window.handle can't break floem.paint.
Position
Below the diagonal: floem.window.handle uses a module listed above it, which is the healthy direction.
floem.window.handle uses floem_reactive.scope, so a change to floem_reactive.scope can break floem.window.handle, while a change to floem.window.handle can't break floem_reactive.scope.
Position
Below the diagonal: floem.window.handle uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in floem.window.handle uses a type in floem.view.
The types involved
floem.window.handle.WindowView → floem.view.View
Direction
floem.window.handle uses floem.view, so a change to floem.view can break floem.window.handle, while a change to floem.window.handle can't break floem.view.
Position
Below the diagonal: floem.window.handle uses a module listed above it, which is the healthy direction.
floem.window.handle uses floem.style, so a change to floem.style can break floem.window.handle, while a change to floem.window.handle can't break floem.style.
Position
Below the diagonal: floem.window.handle uses a module listed above it, which is the healthy direction.
floem.window.handle uses floem.inspector, so a change to floem.inspector can break floem.window.handle, while a change to floem.window.handle can't break floem.inspector.
Position
Below the diagonal: floem.window.handle uses a module listed above it, which is the healthy direction.
floem.window.handle uses floem.window.state, so a change to floem.window.state can break floem.window.handle, while a change to floem.window.handle can't break floem.window.state.
Position
Below the diagonal: floem.window.handle uses a module listed above it, which is the healthy direction.
floem.window.handle uses floem.view.id, so a change to floem.view.id can break floem.window.handle, while a change to floem.window.handle can't break floem.view.id.
Position
Below the diagonal: floem.window.handle uses a module listed above it, which is the healthy direction.
floem.inspector.view uses floem.event, so a change to floem.event can break floem.inspector.view, while a change to floem.inspector.view can't break floem.event.
Position
Below the diagonal: floem.inspector.view uses a module listed above it, which is the healthy direction.
floem.inspector.view uses floem_reactive.signal, so a change to floem_reactive.signal can break floem.inspector.view, while a change to floem.inspector.view can't break floem_reactive.signal.
Position
Below the diagonal: floem.inspector.view uses a module listed above it, which is the healthy direction.
floem.inspector.view uses floem.paint, so a change to floem.paint can break floem.inspector.view, while a change to floem.inspector.view can't break floem.paint.
Position
Below the diagonal: floem.inspector.view uses a module listed above it, which is the healthy direction.
floem.inspector.view uses floem.style.cx, so a change to floem.style.cx can break floem.inspector.view, while a change to floem.inspector.view can't break floem.style.cx.
Position
Below the diagonal: floem.inspector.view uses a module listed above it, which is the healthy direction.
floem.inspector.view uses floem.view, so a change to floem.view can break floem.inspector.view, while a change to floem.inspector.view can't break floem.view.
Position
Below the diagonal: floem.inspector.view uses a module listed above it, which is the healthy direction.
floem.inspector.view uses floem.inspector, so a change to floem.inspector can break floem.inspector.view, while a change to floem.inspector.view can't break floem.inspector.
Position
Below the diagonal: floem.inspector.view uses a module listed above it, which is the healthy direction.
floem.inspector.view uses floem.event.dispatch, so a change to floem.event.dispatch can break floem.inspector.view, while a change to floem.inspector.view can't break floem.event.dispatch.
Position
Below the diagonal: floem.inspector.view uses a module listed above it, which is the healthy direction.
floem.inspector.view uses floem.view.id, so a change to floem.view.id can break floem.inspector.view, while a change to floem.inspector.view can't break floem.view.id.
Position
Below the diagonal: floem.inspector.view uses a module listed above it, which is the healthy direction.
floem.inspector.view uses floem.box_tree, so a change to floem.box_tree can break floem.inspector.view, while a change to floem.inspector.view can't break floem.box_tree.
Position
Below the diagonal: floem.inspector.view 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
A03:2025 — Software Supply Chain Failures
31
High / Critical
A05:2025 — Injection
10
High / Critical
Roadmap
Top priorities: Stamp clock/random values into the event in the command; the recovery fold must be a pure function of the event; 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; Resolve the 80 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (7), builder.rs (4), movement.rs (2).
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Stamp clock/random values into the event in the command; the recovery fold must be a pure function of the event.
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.
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
Code Duplication: Edited copy of a member (16 corresponding lines)
editor-core/src/editor.rs
6.0
Mixed
Explicit Debt: TodoComment
src/style/cx.rs
6.0
Mixed
Explicit Debt: TodoComment
src/style/mod.rs
6.0
Mixed
Explicit Debt: TodoComment
src/views/text_input.rs
6.0
Mixed
Explicit Debt: TodoComment
src/animate/mod.rs
6.0
Mixed
Explicit Debt: TodoComment
src/views/editor/movement.rs
6.0
Mixed
Explicit Debt: TodoComment
editor-core/src/cursor.rs
6.0
Mixed
Explicit Debt: TodoComment
editor-core/src/buffer/mod.rs
6.0
Mixed
Explicit Debt: TodoComment
src/window/state.rs
6.0
Mixed
Explicit Debt: TodoComment
src/views/editor/gutter.rs
6.0
Mixed
Explicit Debt: TodoComment
src/views/editor/view.rs
6.0
Mixed
Explicit Debt: TodoComment
src/inspector/mod.rs
6.0
Mixed
Explicit Debt: TodoComment
tiny_skia/src/lib.rs
6.0
Mixed
Explicit Debt: FixmeComment
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 15
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 — 641
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 — 118
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 21
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 40 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 40 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, 737 of 774 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 120 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.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala 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.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala 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.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, 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.
X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
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.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
34 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was Action::do_edit at 124. A further 6 function(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 Event::listener_keys at 65 — they are counted neither in the figure above nor in this dimension's score. 5 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: src/event/mod.rs (Event::listener_keys at 65), editor-core/src/command.rs (MoveCommand::to_movement at 23), src/style/values.rs (ObjectPosition::debug_view at 19), src/views/img.rs (Img::object_fit_dest_rect_with at 18), tiny_skia/src/lib.rs (floem_tiny_skia_renderer::mix_to_tiny_blend_mode at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 13 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with Action::do_edit (cyclomatic 124), ApplicationHandle::handle_window_event (cyclomatic 64). — 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 2 together lifts Cyclomatic Complexity from 5.8 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: 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.
+ 27 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 Action::do_edit (cognitive 237). — Refactoring it lifts Cognitive Complexity from 5.1 to about 5.8/10.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.6 / 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 28 FileTooLong finding(s) in God Classes — start with mod.rs (7), lib.rs (2), handle.rs (2). — One of this dimension's main actionable groups (28 warning-level).
Resolve the 16 ClassTooLong finding(s) in God Classes — start with mod.rs (4), lib.rs (4), handle.rs (2). — One of this dimension's main actionable groups (16 warning-level).
Resolve the 14 TooManyMethods finding(s) in God Classes — start with mod.rs (5), id.rs, state.rs. — One of this dimension's main actionable groups (14 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
139 duplicated block group(s) detected. 7.4 % of the production lines (6,063 of 82,284) are in a reported copy. A further 99 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
+ 110 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 9 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with cursor.rs, editor.rs, context.rs. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 9 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with editor.rs, view.rs, context_menu.rs. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 9 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with editor.rs (2), values.rs (2), word.rs. — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling6.6 / 10Adequate✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
10 production modules (Cargo), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; 3 module(s) off the main sequence, with abstractness counted on 8 of the 10 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: floem-editor-core · ×3
Unstable project floem
What to do
Resolve the 3 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 Unstable project floem finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 5 Low cohesion finding(s) in Cohesion (LCOM4) — start with mod.rs (2), id.rs (2), state.rs. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
27 outdated, 1 yanked direct Cargo dependencies. 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.
Yanked release: clipboard-win
Outdated: anyhow · ×27
What to do
Resolve the 1 Yanked release finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
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 702 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 20 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.
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/text/layout_state.rs. Counted over 147 of the 176 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
174 deducted task-comment markers across 82284 LoC (0.2/KLoC) → score 9.6. 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.
TodoComment · ×164vello/src/lib.rs:37
FixmeComment · ×7tiny_skia/src/lib.rs:817
XxxComment · ×2src/window/id.rs:332
HackCommentsrc/views/editor/view.rs:158
What to do
Resolve the 164 TodoComment finding(s) in Explicit Debt — start with mod.rs (48), visual_line.rs (32), view.rs (22). — One of this dimension's main actionable groups (164 warning-level).
Resolve the 7 FixmeComment finding(s) in Explicit Debt — start with lib.rs (3), rope_text.rs (2), profiler.rs. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 2 XxxComment finding(s) in Explicit Debt — start with id.rs (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 9 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: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
10 finding(s): 0 critical, 10 high, 0 medium, 0 low. 10 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 1 file(s) — `src/inspector/view.rs` (line 478, line 524, lines 595–596, …) — 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.
REDACTED
What to do
No action in Static Analysis (SAST) — all 10 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 (10 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 13 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (13). — One of this dimension's main actionable groups (13 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 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-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.
83 of 147 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is editor-core/src/editor.rs. Counted over 147 of the 176 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Orphaned file · ×80src/event/drag_state.rs:1
Most significant orphaned file · ×3editor-core/src/editor.rs:1
Concentrated knowledge decay
What to do
Resolve the 80 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (7), builder.rs (4), movement.rs (2). — One of this dimension's main actionable groups (80 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with editor.rs, listener.rs, char_buffer.rs. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 2 Boundary-crossing change coupling finding(s) in Change Coupling — start with tuple.rs, lib.rs. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 3 Change coupling finding(s) in Change Coupling — start with container.rs, mod.rs, label.rs. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with scroll.rs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
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.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 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.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Other · Event-Driven — Whether persisted/published domain events are named in the past tense (facts that happened) rather than imperatively.
Method: Roslyn scan (event-driven gated): domain and integration events checked for past-tense naming (-ed/-en suffix or irregular set). Naming nudge, low-weight advisory.
`UpdatePhase` is an imperative name inside a domain-event set whose siblings are past-tense facts — it reads as an intent, not something that happened. Name new events for the fact that occurred (e.g. `ItemAdded`). Do not rename this one if it is already stored or published: its type name is written with every event recorded under it, so a rename can break replay of the stored stream and every subscriber that reads it, and a clearer name does not pay for that. If it has never been written or sent, renaming it now is safe. — src/event/mod.rs:701
What to do
Name new events in the past tense: they record facts that already happened. Do not rename an event that is already stored or published: its type name is written with every event recorded under it, so a rename can break replay of the stored stream and every subscriber that reads it.
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.
`WindowEventReducer.reduce` folds a domain event but reads a clock/random source (`Instant::now`/`Utc::now`/`rand`/`Uuid::new_v4`) on the replay path — a replay must derive state PURELY from the event's own fields, or two replays of the same log diverge. Stamp the timestamp/id into the event in the COMMAND, then read it from the event in the fold. — ui-events-winit/src/lib.rs:98
What to do
Stamp clock/random values into the event in the command; the recovery fold must be a pure function of the event.
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 repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
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.
What to do
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
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 a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
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.
D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 75 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: 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 — Not applicable: 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.
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.
D10 Test Quality — ~36339 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
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.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D21 Naming Consistency — D21 withholds its sibling role token rows: 3 candidate(s) found and not reported.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (ui-events-winit), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — 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.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — Rust suite
DM1 Domain Modelling — applicable but not scored (3 signals for this style, 3 needed — the count is met but a required primary signal is absent): 4 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 34 value object(s); 6 domain event(s); its domain events are published by services or handlers — no domain entity raises one; no aggregate is declared and no domain structure surrounds the state-guarding types: not claimed as DDD
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'.
P2 Observability — This repository's Rust source (9 module(s), 179 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
S1 Web-Security Posture — No web surface: 177 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
X12 Unreachable branch — 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
X13 Undrained process stream — 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
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — 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
X17 Uncapped recursion over a caller-supplied document — 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
X18 Disposal-pattern correctness — 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
X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not 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
X23 Unguarded diagnostic materialisation — 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
X24 Document value interpolated into markup unescaped — 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
X25 Inert configuration knob — 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
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. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X3 Exception handling — 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
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — 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.
X7 Silent fallback defaults — 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.
Boundary-crossing change coupling: tuple.rs ↔ label.rs src/view/tuple.rs:1— `src/view/tuple.rs` (context view) and `src/views/label.rs` (context views) sit in DIFFERENT parts of the tree yet change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `7111c39e` Add lazy view construction with Intermediate type on IntoView (#995) (at that commit the file was still `src/view_tuple.rs`); `38dac12b` bump cosmic-text (at that commit the file was still `src/view_tuple.rs`); `0d6f3707` label text change (at that commit the file was still `src/view_tuple.rs`) — run `git show` on any of them.
Boundary-crossing change coupling: lib.rs ↔ lib.rs vello/src/lib.rs:1— `vello/src/lib.rs` (context vello) and `vger/src/lib.rs` (context vger) sit in DIFFERENT parts of the tree yet change together 58% of the time (11 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `bcafaaad` recover from lost/outdated wgpu surface on Wayland (#1074); `998102e6` Fix scale (#1036); `c9546920` Update to Vello 0.6 (#903) — run `git show` on any of them.
Non-deterministic recovery fold: WindowEventReducer.reduce ui-events-winit/src/lib.rs:98— `WindowEventReducer.reduce` folds a domain event but reads a clock/random source (`Instant::now`/`Utc::now`/`rand`/`Uuid::new_v4`) on the replay path — a replay must derive state PURELY from the event's own fields, or two replays of the same log diverge. Stamp the timestamp/id into the event in the COMMAND, then read it from the event in the fold.
TodoComment vello/src/lib.rs:37— // TODO: Apply once vello's DrawGlyphs gains embolden support. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment vello/src/lib.rs:308— // TODO: Vello 0.7's DrawGlyphs API has no embolden support. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/tests/position_consistency.rs:1— //! TODO: should we delete these tests? probably yes. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/action.rs:134— // TODO: what is this for? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/lib.rs:122— // TODO: Add links on these — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/window/mod.rs:468— // TODO: need to patch winit first — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/window/state.rs:148— // TODO: Track hover state per pointer — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/views/dropdown.rs:317— // TODO: this should be more customizable — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/views/navigation_stack.rs:87— // TODO: Tighten naming and lift NavigationPath into a reusable collection-source — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/views/text_editor.rs:405— // TODO(minor): should this be named `text`? Ideally most users should use the rope text version — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/views/text_input.rs:75— //TODO: pub font_size: FontSize, — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/views/text_input.rs:146— // TODO: make this configurable — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/views/text_input.rs:738— //TODO: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/views/text_input.rs:1261— // TODO: find a better way to handle this — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/views/editor/actions.rs:55— // TODO: Should we instead pass the editor so that it can grab — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/views/editor/actions.rs:77— // TODO: should we track jump locations? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/views/editor/actions.rs:117— // TODO: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/views/editor/mod.rs:1435— // TODO: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/views/editor/actions.rs:164— // TODO: should this use Rope's Interval instead of Range? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/views/editor/actions.rs:175— // TODO: should we have a more general cursor state structure? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/views/editor/gutter.rs:99— // TODO: don't assume font family is constant for each line — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/views/editor/gutter.rs:119— // TODO: check if shis should be 0 or 1 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/views/editor/view.rs:650— // TODO: check if shis should be 0 or 1 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/views/editor/gutter.rs:128— // TODO: unsure if this is correct for wrapping lines — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/views/editor/view.rs:660— // TODO: unsure if this is correct for wrapping lines — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FileTooLong: style/mod.rs src/style/mod.rs— FileTooLong — 1852 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 1352 over it, 3.70× 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: style/values.rs src/style/values.rs— FileTooLong — 1632 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 1132 over it, 3.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: event/dispatch.rs src/event/dispatch.rs— FileTooLong — 1463 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 70% of them inside a single declaration: RouteCx (11 blocks, 501-2287). The bar is 500 significant lines; this is 963 over it, 2.93× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/lib.rs tiny_skia/src/lib.rs— FileTooLong — 1447 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 35 free functions. The bar is 500 significant lines; this is 947 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: src/editor.rs editor-core/src/editor.rs— FileTooLong — 1167 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 667 over it, 2.33× 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: window/handle.rs src/window/handle.rs— FileTooLong — 1132 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: WindowHandle (3 blocks, 74-1676). The bar is 500 significant lines; this is 632 over it, 2.26× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: editor/visual_line.rs src/views/editor/visual_line.rs— FileTooLong — 1046 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 546 over it, 2.09× 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: editor/mod.rs src/views/editor/mod.rs— FileTooLong — 1032 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 76% of them inside a single declaration: Editor (5 blocks, 151-1488). The bar is 500 significant lines; this is 532 over it, 2.06× 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/text_input.rs src/views/text_input.rs— FileTooLong — 968 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 85% of them inside a single declaration: TextInput (4 blocks, 127-1579). The bar is 500 significant lines; this is 468 over it, 1.94× 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: editor/view.rs src/views/editor/view.rs— FileTooLong — 958 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 458 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: window/state.rs src/window/state.rs— FileTooLong — 877 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 84% of them inside a single declaration: WindowState (3 blocks, 100-1398). The bar is 500 significant lines; this is 377 over it, 1.75× 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: view/id.rs src/view/id.rs— FileTooLong — 845 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: ViewId (5 blocks, 62-1700). The bar is 500 significant lines; this is 345 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: inspector/mod.rs src/inspector/mod.rs— FileTooLong — 787 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 287 over it, 1.57× 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/scroll.rs src/views/scroll.rs— FileTooLong — 740 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 240 over it, 1.48× 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: animate/mod.rs src/animate/mod.rs— FileTooLong — 717 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: Animation (4 blocks, 359-1239). The bar is 500 significant lines; this is 217 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: event/mod.rs src/event/mod.rs— FileTooLong — 713 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 213 over it, 1.43× 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: style/theme.rs src/style/theme.rs— FileTooLong — 663 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 163 over it, 1.33× 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: app/handle.rs src/app/handle.rs— FileTooLong — 659 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 82% of them inside a single declaration: ApplicationHandle (2 blocks, 45-832). The bar is 500 significant lines; this is 159 over it, 1.32× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/signal.rs reactive/src/signal.rs— FileTooLong — 652 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 152 over it, 1.30× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: view/mod.rs src/view/mod.rs— FileTooLong — 630 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 130 over it, 1.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: inspector/view.rs src/inspector/view.rs— FileTooLong — 617 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 117 over it, 1.23× 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: style/components.rs src/style/components.rs— FileTooLong — 605 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 105 over it, 1.21× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs vger/src/lib.rs— FileTooLong — 561 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: VgerRenderer (4 blocks, 31-766). The bar is 500 significant lines; this is 61 over it, 1.12× 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: style/cx.rs src/style/cx.rs— FileTooLong — 522 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 82% of them inside a single declaration: StyleCx (2 blocks, 86-808). The bar is 500 significant lines; this is 22 over it, 1.04× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: event/listener.rs src/event/listener.rs— FileTooLong — 521 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 21 over it, 1.04× 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.
ClassTooLong: WindowHandle src/window/handle.rs:74— ClassTooLong — 1061 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 52 methods, 3 blocks, lines 74-1676. The bar is 400 significant lines; this is 661 over it, 2.65× 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: RouteCx src/event/dispatch.rs:501— ClassTooLong — 1028 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 37 methods, 11 blocks, lines 501-2287. The bar is 400 significant lines; this is 628 over it, 2.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Style src/style/mod.rs:862— ClassTooLong — 987 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 190 methods, 7 blocks, lines 249-3707. The bar is 400 significant lines; this is 587 over it, 2.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TextInput src/views/text_input.rs:127— ClassTooLong — 818 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 30 methods, 4 blocks, lines 127-1579. The bar is 400 significant lines; this is 418 over it, 2.05× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Editor src/views/editor/mod.rs:151— ClassTooLong — 780 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 87 methods, 5 blocks, lines 151-1488. The bar is 400 significant lines; this is 380 over it, 1.95× 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: ViewId src/view/id.rs:58— ClassTooLong — 762 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 117 methods, 5 blocks, lines 62-1700. The bar is 400 significant lines; this is 362 over it, 1.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: WindowState src/window/state.rs:100— ClassTooLong — 740 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 63 methods, 3 blocks, lines 100-1398. The bar is 400 significant lines; this is 340 over it, 1.85× 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: ApplicationHandle src/app/handle.rs:45— ClassTooLong — 543 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 45-832. The bar is 400 significant lines; this is 143 over it, 1.36× 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: Animation src/animate/mod.rs:359— ClassTooLong — 538 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 56 methods, 4 blocks, lines 359-1239. The bar is 400 significant lines; this is 138 over it, 1.35× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: VgerRenderer vger/src/lib.rs:31— ClassTooLong — 532 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 10 methods, 4 blocks, lines 31-766. The bar is 400 significant lines; this is 132 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: EditorView src/views/editor/view.rs:347— ClassTooLong — 480 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 12 methods, 3 blocks, lines 347-1075. The bar is 400 significant lines; this is 80 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TinySkiaRenderer tiny_skia/src/lib.rs:870— ClassTooLong — 435 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 10 methods, 3 blocks, lines 870-1624. The bar is 400 significant lines; this is 35 over it, 1.09× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: StyleCx src/style/cx.rs:86— ClassTooLong — 430 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 13 methods, 2 blocks, lines 86-808. The bar is 400 significant lines; this is 30 over it, 1.08× 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: Layer tiny_skia/src/lib.rs:252— ClassTooLong — 429 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 23 methods, 3 blocks, lines 252-868. The bar is 400 significant lines; this is 29 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Buffer editor-core/src/buffer/mod.rs:75— ClassTooLong — 408 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 34 methods, 4 blocks, lines 75-680. The bar is 400 significant lines; this is 8 over it, 1.02× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: VelloRenderer vello/src/lib.rs:25— ClassTooLong — 406 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 6 methods, 4 blocks, lines 25-591. The bar is 400 significant lines; this is 6 over it, 1.02× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
floem::style::resolve_selectors (cognitive 68) src/style/mod.rs:704— floem::style::resolve_selectors has cognitive complexity 68 (threshold 15). Drivers by points: if/else 22 (50 pts), boolean chains 11, loops 3 (7 pts) (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
floem::view::paint_border (cognitive 43) src/view/mod.rs:1291— floem::view::paint_border has cognitive complexity 43 (threshold 15). Drivers by points: if/else 15 (33 pts), boolean chains 7, match/switch 1 (2 pts), loops 1 (nesting depth added 19). 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.
floem::views::virtual_stack::virtual_stack (cognitive 37) src/views/virtual_stack.rs:263— floem::views::virtual_stack::virtual_stack has cognitive complexity 37 (threshold 15). Drivers by points: match/switch 8 (15 pts), loops 5 (11 pts), if/else 6 (9 pts), boolean chains 2 (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.
floem::views::editor::movement::do_multi_selection (cognitive 36) src/views/editor/movement.rs:663— floem::views::editor::movement::do_multi_selection has cognitive complexity 36 (threshold 15). Drivers by points: if/else 10 (25 pts), loops 3 (10 pts), match/switch 1 (nesting depth added 22). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
floem::inspector::view::capture_view (cognitive 25) src/inspector/view.rs:180— floem::inspector::view::capture_view has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 2, match/switch 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.
floem::views::list::list (cognitive 23) src/views/list.rs:83— floem::views::list::list has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (18 pts), match/switch 3 (5 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
floem::platform::context_menu::context_menu_view::view_fn (cognitive 20) src/platform/context_menu.rs:120— floem::platform::context_menu::context_menu_view::view_fn has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 1, match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
floem::inspector::add_event (cognitive 18) src/inspector/mod.rs:595— floem::inspector::add_event has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (17 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.
floem::views::dyn_stack::diff (cognitive 18) src/views/dyn_stack.rs:194— floem::views::dyn_stack::diff has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 5, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
floem::views::editor::view::editor_view (cognitive 18) src/views/editor/view.rs:1082— floem::views::editor::view::editor_view has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 3 (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.
floem::views::svg::brush_to_css_string (cognitive 18) src/views/svg.rs:350— floem::views::svg::brush_to_css_string has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 1 (3 pts), 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.
floem::inspector::view::capture (cognitive 17) src/inspector/view.rs:41— floem::inspector::view::capture has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 7, if/else 4 (6 pts), match/switch 2 (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.
floem::paint::collect_visual_order (cognitive 17) src/paint/mod.rs:146— floem::paint::collect_visual_order has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (4 pts), 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.
floem::view::apply_keyed_diff (cognitive 17) src/view/mod.rs:620— floem::view::apply_keyed_diff has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 5 (6 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
floem::window::state::build_focus_space_for_scope (cognitive 17) src/window/state.rs:46— floem::window::state::build_focus_space_for_scope has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (13 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.
TooManyMethods: Style src/style/mod.rs:862— TooManyMethods — 190 methods, declared across 3 files: style/mod.rs (187), style/cache.rs (2), style/values.rs (1). The bar is 30 methods; this is 160 over it, 6.33× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ViewId src/view/id.rs:58— TooManyMethods — 117 methods. The bar is 30 methods; this is 87 over it, 3.90× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Editor src/views/editor/mod.rs:151— TooManyMethods — 87 methods. The bar is 30 methods; this is 57 over it, 2.90× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WindowState src/window/state.rs:100— TooManyMethods — 63 methods. The bar is 30 methods; this is 33 over it, 2.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Animation src/animate/mod.rs:359— TooManyMethods — 56 methods. The bar is 30 methods; this is 26 over it, 1.87× 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: HeadlessHarness src/headless.rs:101— TooManyMethods — 52 methods. The bar is 30 methods; this is 22 over it, 1.73× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WindowHandle src/window/handle.rs:74— TooManyMethods — 52 methods. The bar is 30 methods; this is 22 over it, 1.73× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ExprStyle src/style/mod.rs:239— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: StyleReason src/style/recalc.rs:82— TooManyMethods — 38 methods. The bar is 30 methods; this is 8 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.
TooManyMethods: RouteCx src/event/dispatch.rs:501— 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: TextLayout src/text/layout.rs:154— 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: Buffer editor-core/src/buffer/mod.rs:75— TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Lines src/views/editor/visual_line.rs:295— TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Selection editor-core/src/selection.rs:38— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×13
FunctionTooLong: floem::style::theme::default_theme src/style/theme.rs:550— FunctionTooLong — floem::style::theme::default_theme runs 285 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 185 over it, 2.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.
FunctionTooLong: floem::inspector::view::capture_view src/inspector/view.rs:180— FunctionTooLong — floem::inspector::view::capture_view runs 188 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 88 over it, 1.88× 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: floem::platform::context_menu::context_menu_view src/platform/context_menu.rs:102— FunctionTooLong — floem::platform::context_menu::context_menu_view runs 168 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 68 over it, 1.68× 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: floem::views::virtual_stack::virtual_stack src/views/virtual_stack.rs:263— FunctionTooLong — floem::views::virtual_stack::virtual_stack runs 161 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 61 over it, 1.61× 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: floem::inspector::profiler::profile_view src/inspector/profiler.rs:74— FunctionTooLong — floem::inspector::profiler::profile_view runs 138 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 38 over it, 1.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: floem::inspector::selected_view src/inspector/mod.rs:725— FunctionTooLong — floem::inspector::selected_view runs 126 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 26 over it, 1.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: floem_editor_core::buffer::diff::rope_diff editor-core/src/buffer/diff.rs:77— FunctionTooLong — floem_editor_core::buffer::diff::rope_diff runs 120 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 20 over it, 1.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: floem::inspector::box_model_view src/inspector/mod.rs:352— FunctionTooLong — floem::inspector::box_model_view runs 118 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 18 over it, 1.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: floem::views::editor::view::editor_content src/views/editor/view.rs:1364— FunctionTooLong — floem::views::editor::view::editor_content 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: floem::view::paint_border src/view/mod.rs:1291— FunctionTooLong — floem::view::paint_border runs 104 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: StyleCx.style_view src/style/cx.rs:241— MethodTooLong — style_view runs 252 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 152 over it, 2.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.
MethodTooLong: WindowHandle.process_update_messages src/window/handle.rs:1102— MethodTooLong — process_update_messages runs 200 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 100 over it, 2.00× 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: SkiaRenderer.replay skia/src/lib.rs:151— MethodTooLong — replay runs 130 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TextInput.handle_key_down src/views/text_input.rs:890— MethodTooLong — handle_key_down runs 128 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TextInput.event src/views/text_input.rs:1254— MethodTooLong — event runs 127 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ApplicationHandle.handle_window_event src/app/handle.rs:246— MethodTooLong — handle_window_event runs 126 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 26 over it, 1.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ObjectPosition.debug_view src/style/values.rs:469— MethodTooLong — debug_view runs 104 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BorderPathIter.next src/paint/border_path_iter.rs:95— MethodTooLong — next 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.
MethodTooLong: Event.listener_keys src/event/mod.rs:2023— MethodTooLong — listener_keys runs 101 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (12 lines × 2) editor-core/src/cursor.rs:325— editor-core/src/cursor.rs:325-336 | editor-core/src/cursor.rs:444-455 — 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) editor-core/src/editor.rs:1268— editor-core/src/editor.rs:1268-1279 | editor-core/src/editor.rs:1293-1304 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor-core/src/editor.rs:1268` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) reactive/src/context.rs:46— reactive/src/context.rs:46-57 | reactive/src/context.rs:185-196 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) src/event/drag_state.rs:600— src/event/drag_state.rs:600-611 | src/event/drag_state.rs:736-748 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/event/drag_state.rs:600` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/headless.rs:743— src/headless.rs:743-754 | src/headless.rs:766-777 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/headless.rs:743` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/text/layout_state.rs:155— src/text/layout_state.rs:155-166 | src/text/layout_state.rs:179-190 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/text/layout_state.rs:155` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/views/scroll.rs:239— src/views/scroll.rs:239-250 | src/views/scroll.rs:426-437 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/views/scroll.rs:239` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/inspector/profiler.rs:228— src/inspector/profiler.rs:228-239 | src/inspector/profiler.rs:294-305 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/inspector/profiler.rs:228` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) vger/src/lib.rs:606— vger/src/lib.rs:606-617 | vger/src/lib.rs:638-649 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) editor-core/src/editor.rs:1199— editor-core/src/editor.rs:1199-1207 | editor-core/src/editor.rs:1230-1238 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor-core/src/editor.rs:1199` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (9 lines × 2) src/inspector/view.rs:763— src/inspector/view.rs:763-771 | src/inspector/view.rs:779-787 — 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) src/platform/context_menu.rs:165— src/platform/context_menu.rs:165-173 | src/platform/context_menu.rs:270-278 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/platform/context_menu.rs:165` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/style/values.rs:1971— src/style/values.rs:1971-1979 | src/style/values.rs:2239-2247 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/style/values.rs:1971` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/text/layout.rs:746— src/text/layout.rs:746-754 | src/text/layout.rs:765-773 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/text/layout.rs:746` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/views/editor/mod.rs:377— src/views/editor/mod.rs:377-385 | src/views/editor/mod.rs:401-409 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/views/editor/mod.rs:377` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/views/editor/mod.rs:374` calls `Some`, `set` and `src/views/editor/mod.rs:399` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) src/views/editor/movement.rs:680— src/views/editor/movement.rs:680-688 | src/views/editor/movement.rs:702-710 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/views/editor/movement.rs:680` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/views/text_editor.rs:79— src/views/text_editor.rs:79-87 | src/views/text_editor.rs:103-111 — 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) src/views/text_input.rs:1014— src/views/text_input.rs:1014-1022 | src/views/text_input.rs:1037-1045 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/views/text_input.rs:1014` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) editor-core/src/editor.rs:234— editor-core/src/editor.rs:234-238 | editor-core/src/editor.rs:763-767 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor-core/src/editor.rs:234` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) editor-core/src/word.rs:206— editor-core/src/word.rs:206-210 | editor-core/src/word.rs:236-240 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor-core/src/word.rs:206` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) src/event/dispatch.rs:1609— src/event/dispatch.rs:1609-1613 | src/event/dispatch.rs:1769-1773 — 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) src/inspector/mod.rs:710— src/inspector/mod.rs:710-715 | src/inspector/mod.rs:842-846 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/inspector/mod.rs:710` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) src/paint/renderer.rs:96— src/paint/renderer.rs:96-100 | src/paint/renderer.rs:175-179 — 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) src/inspector/view.rs:50— src/inspector/view.rs:50-54 | src/style/values.rs:2437-2443 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/style/values.rs:2437` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) editor-core/src/editor.rs:400— editor-core/src/editor.rs:400-404 | editor-core/src/editor.rs:410-414 — 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) src/style/values.rs:916— src/style/values.rs:916-920 | src/style/values.rs:973-977 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/style/values.rs:916` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) src/style/values.rs:941— src/style/values.rs:941-945 | src/style/values.rs:996-1000 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/style/values.rs:941` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×8
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×8
Edited copy of a member (13 corresponding lines) vger/src/lib.rs:605— vger/src/lib.rs:605-630 | vger/src/lib.rs:637-676 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) src/view/id.rs:204— src/view/id.rs:204-218 | src/view/id.rs:222-234 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) src/style/mod.rs:1234— src/style/mod.rs:1234-1246 | src/style/mod.rs:1248-1261 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) tiny_skia/src/lib.rs:266— tiny_skia/src/lib.rs:266-278 | tiny_skia/src/lib.rs:286-300 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) editor-core/src/buffer/mod.rs:629— editor-core/src/buffer/mod.rs:629-641 | editor-core/src/buffer/mod.rs:643-655 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) src/views/editor/visual_line.rs:722— src/views/editor/visual_line.rs:722-739 | src/views/editor/visual_line.rs:811-823 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) src/views/decorator.rs:162— src/views/decorator.rs:162-174 | src/views/decorator.rs:198-210 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) src/views/stack.rs:301— src/views/stack.rs:301-313 | src/views/stack.rs:325-337 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (11 lines × 2) src/event/drag_state.rs:615— src/event/drag_state.rs:615-625 | src/event/drag_state.rs:750-760 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/event/drag_state.rs:615` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/event/drag_state.rs:612` calls `current_path`, `last`, `copied` and `src/event/drag_state.rs:748` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 2) src/headless.rs:568— src/headless.rs:568-578 | src/headless.rs:594-604 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/headless.rs:568` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/headless.rs:615— src/headless.rs:615-625 | src/headless.rs:636-646 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/headless.rs:615` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/headless.rs:688— src/headless.rs:688-698 | src/headless.rs:709-719 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/headless.rs:688` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/style/cx.rs:817— src/style/cx.rs:817-827 | src/views/dyn_container.rs:199-209 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/style/cx.rs:817` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/text/layout_state.rs:236— src/text/layout_state.rs:236-246 | src/text/layout_state.rs:294-304 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/text/layout_state.rs:236` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/views/container.rs:106— src/views/container.rs:106-116 | src/views/dyn_view.rs:42-52 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `cx` to `&mut UpdateCx` in one and `&mut crate::context::UpdateCx` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (11 lines × 2) src/views/slider.rs:443— src/views/slider.rs:443-453 | src/views/slider.rs:534-544 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/views/slider.rs:443` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/style/mod.rs:973— src/style/mod.rs:973-979 | src/style/mod.rs:993-999 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/style/mod.rs:973` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/view/id.rs:378— src/view/id.rs:378-384 | src/view/id.rs:426-432 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/view/id.rs:377` calls `into_view` and `src/view/id.rs:425` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) src/inspector/view.rs:743— src/inspector/view.rs:743-749 | src/inspector/view.rs:752-758 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/inspector/view.rs:743` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) editor-core/src/cursor.rs:316— editor-core/src/cursor.rs:316-322 | editor-core/src/cursor.rs:435-441 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor-core/src/cursor.rs:316` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/views/list.rs:59— src/views/list.rs:59-65 | src/views/virtual_list.rs:135-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 (7 lines × 2) src/animate/easing.rs:273— src/animate/easing.rs:273-279 | src/animate/easing.rs:331-337 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/animate/easing.rs:273` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/views/editor/mod.rs:1311— src/views/editor/mod.rs:1311-1317 | src/views/editor/mod.rs:1318-1324 — 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) src/views/editor/text.rs:378— src/views/editor/text.rs:378-384 | src/views/editor/text.rs:408-414 — 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.
floem::style::resolve_selectors (cyclomatic 35) src/style/mod.rs:704— floem::style::resolve_selectors 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.
floem::view::paint_border (cyclomatic 23) src/view/mod.rs:1291— floem::view::paint_border 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.
floem::views::virtual_stack::virtual_stack (cyclomatic 21) src/views/virtual_stack.rs:263— floem::views::virtual_stack::virtual_stack has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
floem::views::editor::movement::do_multi_selection (cyclomatic 19) src/views/editor/movement.rs:663— floem::views::editor::movement::do_multi_selection 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.
floem::platform::context_menu::context_menu_view (cyclomatic 18) src/platform/context_menu.rs:102— floem::platform::context_menu::context_menu_view has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to one function item inside it that branches (view_fn). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
floem::inspector::view::capture (cyclomatic 17) src/inspector/view.rs:41— floem::inspector::view::capture has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
floem::inspector::view::capture_view (cyclomatic 17) src/inspector/view.rs:180— floem::inspector::view::capture_view 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.
FixmeComment tiny_skia/src/lib.rs:817— // FIXME: Handle _blur_radius — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment tiny_skia/src/lib.rs:1484— // FIXME: Remove this method? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment tiny_skia/src/lib.rs:1669— // FIXME: Doesn't use `start_radius` — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/inspector/profiler.rs:308— // FIXME: This needs an extra `container` or the `Stack::vertical` ends up horizontal. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment editor-core/src/buffer/rope_text.rs:306— // FIXME: wait for if-let-chain — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment editor-core/src/buffer/rope_text.rs:339— // FIXME: wait for if-let-chain — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment editor-core/src/buffer/test.rs:79— // FIXME: see #501 for possible issues in WordCursor::next_boundary()
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×7
Edited copy of a member (9 corresponding lines) src/style/mod.rs:1069— src/style/mod.rs:1069-1077 | src/style/mod.rs:1082-1091 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) editor-core/src/selection.rs:616— editor-core/src/selection.rs:616-624 | editor-core/src/selection.rs:626-637 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) src/style/values.rs:894— src/style/values.rs:894-903 | src/style/values.rs:952-960 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) reactive/src/derived.rs:169— reactive/src/derived.rs:169-177 | reactive/src/derived.rs:412-420 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) reactive/src/write.rs:29— reactive/src/write.rs:29-37 | reactive/src/write.rs:52-65 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) reactive/src/effect.rs:198— reactive/src/effect.rs:198-206 | reactive/src/scope.rs:268-284 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) vello/src/lib.rs:477— vello/src/lib.rs:477-485 | vger/src/lib.rs:757-765 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (13 lines × 2) editor-core/src/editor.rs:1127— editor-core/src/editor.rs:1127-1139 | editor-core/src/editor.rs:1207-1219 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor-core/src/editor.rs:1127` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `editor-core/src/editor.rs:1140` calls `indent_unit` and `editor-core/src/editor.rs:1220` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) src/animate/mod.rs:1004— src/animate/mod.rs:1004-1016 | src/animate/mod.rs:1034-1046 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/animate/mod.rs:1004` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/event/dispatch.rs:1400— src/event/dispatch.rs:1400-1412 | src/event/dispatch.rs:1456-1468 — 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) src/receiver_signal/common/executors.rs:423— src/receiver_signal/common/executors.rs:423-435 | src/receiver_signal/common/executors.rs:503-515 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/receiver_signal/common/executors.rs:423` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/receiver_signal/common/executors.rs:439— src/receiver_signal/common/executors.rs:439-451 | src/receiver_signal/common/executors.rs:519-531 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/receiver_signal/common/executors.rs:439` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/view/mod.rs:335— src/view/mod.rs:335-347 | src/view/mod.rs:549-561 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/view/mod.rs:335` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/views/virtual_stack.rs:353— src/views/virtual_stack.rs:353-365 | src/views/virtual_stack.rs:377-389 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/views/virtual_stack.rs:353` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) editor-core/src/buffer/rope_text.rs:128— editor-core/src/buffer/rope_text.rs:128-135 | src/views/editor/visual_line.rs:1583-1590 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `editor-core/src/buffer/rope_text.rs:128` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) src/event/drag_state.rs:537— src/event/drag_state.rs:537-544 | src/event/drag_state.rs:566-573 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/event/drag_state.rs:537` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) src/receiver_signal/future_signal/builder.rs:140— src/receiver_signal/future_signal/builder.rs:140-147 | src/receiver_signal/stream_signal/builder.rs:215-222 — 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) src/style/values.rs:2478— src/style/values.rs:2478-2485 | src/style/values.rs:2488-2495 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/style/values.rs:2478` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) src/view/state.rs:541— src/view/state.rs:541-548 | src/view/state.rs:588-595 — 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) src/receiver_signal/channel_signal/builder.rs:96— src/receiver_signal/channel_signal/builder.rs:96-103 | src/receiver_signal/stream_signal/builder.rs:84-91 — 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) src/receiver_signal/channel_signal/builder.rs:109— src/receiver_signal/channel_signal/builder.rs:109-116 | src/receiver_signal/stream_signal/builder.rs:97-104 — 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.
RouteCx::element_tab_navigation (cognitive 47) src/event/dispatch.rs:1717— RouteCx::element_tab_navigation has cognitive complexity 47 (threshold 15). Drivers by points: if/else 24 (45 pts), boolean chains 2 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RouteCx::handle_default_behaviors (cognitive 30) src/event/dispatch.rs:1094— RouteCx::handle_default_behaviors has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (15 pts), loops 3 (7 pts), match/switch 5, boolean chains 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RouteCx::dispatch_directed (cognitive 26) src/event/dispatch.rs:679— RouteCx::dispatch_directed has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 5 (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.
RouteCx::handle_pointer_state_updates (cognitive 22) src/event/dispatch.rs:2059— RouteCx::handle_pointer_state_updates has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 3 (8 pts), match/switch 2 (4 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.
RouteCx::push_hover_events (cognitive 18) src/event/dispatch.rs:2001— RouteCx::push_hover_events has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (15 pts), 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.
RouteCx::element_arrow_navigation (cognitive 17) src/event/dispatch.rs:1851— RouteCx::element_arrow_navigation has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (14 pts), match/switch 2, boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×6
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×6
Edited copy of a member (12 corresponding lines) src/views/img.rs:157— src/views/img.rs:157-172 | src/views/img.rs:192-206 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) src/inspector/mod.rs:70— src/inspector/mod.rs:70-81 | src/inspector/mod.rs:83-95 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) src/views/rich_text.rs:318— src/views/rich_text.rs:318-329 | src/views/rich_text.rs:334-345 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) src/views/img.rs:237— src/views/img.rs:237-253 | src/views/svg.rs:236-247 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) src/window/state.rs:530— src/window/state.rs:530-543 | src/window/state.rs:598-609 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) src/views/resizable.rs:169— src/views/resizable.rs:169-181 | src/views/scroll.rs:316-327 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×6
Edited copy of a member (15 corresponding lines) editor-core/src/buffer/rope_text.rs:125— editor-core/src/buffer/rope_text.rs:125-139 | src/views/editor/visual_line.rs:1577-1594 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) src/style/theme.rs:128— src/style/theme.rs:128-142 | src/style/theme.rs:145-159 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) src/text/layout_state.rs:152— src/text/layout_state.rs:152-166 | src/text/layout_state.rs:175-190 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) reactive/src/effect.rs:80— reactive/src/effect.rs:80-94 | reactive/src/effect.rs:145-161 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) src/style/mod.rs:3331— src/style/mod.rs:3331-3345 | src/style/mod.rs:3349-3363 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) editor-core/src/word.rs:341— editor-core/src/word.rs:341-355 | editor-core/src/word.rs:370-384 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
RouteCx::handle_default_behaviors (cyclomatic 24) src/event/dispatch.rs:1094— RouteCx::handle_default_behaviors has cyclomatic complexity 24 (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.
RouteCx::element_arrow_navigation (cyclomatic 18) src/event/dispatch.rs:1851— RouteCx::element_arrow_navigation 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.
RouteCx::handle_pointer_state_updates (cyclomatic 18) src/event/dispatch.rs:2059— RouteCx::handle_pointer_state_updates has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
RouteCx::element_tab_navigation (cyclomatic 17) src/event/dispatch.rs:1717— RouteCx::element_tab_navigation 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.
RouteCx::dispatch_directed (cyclomatic 16) src/event/dispatch.rs:679— RouteCx::dispatch_directed has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Action::do_edit (cognitive 237) editor-core/src/editor.rs:775— Action::do_edit has cognitive complexity 237 (threshold 15). Drivers by points: if/else 57 (148 pts), loops 16 (50 pts), match/switch 15 (34 pts), boolean chains 5 (nesting depth added 144). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident. This file is where this pass's cognitive complexity CONCENTRATES: editor-core/src/editor.rs holds 5 of the 72 functions over the threshold — including the worst — and 321 of the 1205 points over it (27%), 2.3× the next-largest file (src/event/dispatch.rs at 137). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
Action::insert (cognitive 95) editor-core/src/editor.rs:89— Action::insert has cognitive complexity 95 (threshold 15). Drivers by points: if/else 18 (69 pts), match/switch 3 (12 pts), boolean chains 8, loops 2 (6 pts) (nesting depth added 64). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: editor-core/src/editor.rs holds 5 of the 72 functions over the threshold — including the worst — and 321 of the 1205 points over it (27%), 2.3× the next-largest file (src/event/dispatch.rs at 137). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
Action::do_paste (cognitive 28) editor-core/src/editor.rs:567— Action::do_paste has cognitive complexity 28 (threshold 15). Drivers by points: match/switch 6 (13 pts), if/else 5 (11 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident. This file is where this pass's cognitive complexity CONCENTRATES: editor-core/src/editor.rs holds 5 of the 72 functions over the threshold — including the worst — and 321 of the 1205 points over it (27%), 2.3× the next-largest file (src/event/dispatch.rs at 137). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
Action::do_outdent (cognitive 20) editor-core/src/editor.rs:697— Action::do_outdent has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (16 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: editor-core/src/editor.rs holds 5 of the 72 functions over the threshold — including the worst — and 321 of the 1205 points over it (27%), 2.3× the next-largest file (src/event/dispatch.rs at 137). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
Action::do_indent (cognitive 16) editor-core/src/editor.rs:667— Action::do_indent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: editor-core/src/editor.rs holds 5 of the 72 functions over the threshold — including the worst — and 321 of the 1205 points over it (27%), 2.3× the next-largest file (src/event/dispatch.rs at 137). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×5
Edited copy of a member (11 corresponding lines) reactive/src/signal.rs:74— reactive/src/signal.rs:74-85 | reactive/src/signal.rs:88-98 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) reactive/src/derived.rs:220— reactive/src/derived.rs:220-230 | reactive/src/derived.rs:463-473 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) src/window/tracking.rs:209— src/window/tracking.rs:209-219 | src/window/tracking.rs:221-237 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) src/views/virtual_list.rs:44— src/views/virtual_list.rs:44-54 | src/views/virtual_stack.rs:134-144 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) src/views/virtual_list.rs:25— src/views/virtual_list.rs:25-35 | src/views/virtual_stack.rs:116-126 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (18 lines × 2) reactive/src/scope.rs:297— reactive/src/scope.rs:297-314 | reactive/src/scope.rs:365-382 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `reactive/src/scope.rs:297` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/app/handle.rs:918— src/app/handle.rs:918-935 | src/app/handle.rs:944-961 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/app/handle.rs:918` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/event/mod.rs:1960— src/event/mod.rs:1960-1977 | src/event/mod.rs:1980-1997 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (18 lines × 2) src/receiver_signal/common/executors.rs:477— src/receiver_signal/common/executors.rs:477-494 | src/receiver_signal/common/executors.rs:557-574 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/receiver_signal/common/executors.rs:477` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/receiver_signal/resource/builder.rs:582— src/receiver_signal/resource/builder.rs:582-599 | src/receiver_signal/resource/builder.rs:622-639 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/receiver_signal/resource/builder.rs:582` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/layout/screen.rs:21— src/layout/screen.rs:21-34 | src/layout/screen.rs:58-71 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/layout/screen.rs:21` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/receiver_signal/common/executors.rs:460— src/receiver_signal/common/executors.rs:460-473 | src/receiver_signal/common/executors.rs:540-553 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/receiver_signal/common/executors.rs:460` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/style/values.rs:2301— src/style/values.rs:2301-2314 | src/style/values.rs:2353-2366 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/style/values.rs:2301` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 2) src/view/mod.rs:356— src/view/mod.rs:356-369 | src/view/mod.rs:571-584 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/view/mod.rs:356` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/view/mod.rs:372` calls `child_fn_for_effect` and `src/view/mod.rs:587` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 2) src/paint/border_path_iter.rs:147— src/paint/border_path_iter.rs:147-161 | src/paint/border_path_iter.rs:179-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/paint/border_path_iter.rs:147` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Low cohesion: Style (LCOM4 13) src/style/mod.rs:862— Style's methods fall into 13 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 13 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: ViewId (LCOM4 7) src/view/id.rs:58— ViewId's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Id (LCOM4 4) reactive/src/id.rs:12— Id's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Animation (LCOM4 4) src/animate/mod.rs:359— Animation's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: WindowState (LCOM4 4) src/window/state.rs:100— WindowState's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
floem_editor_core::buffer::diff::rope_diff (cognitive 67) editor-core/src/buffer/diff.rs:77— floem_editor_core::buffer::diff::rope_diff has cognitive complexity 67 (threshold 15). Drivers by points: if/else 19 (42 pts), match/switch 4 (11 pts), boolean chains 7, loops 5 (7 pts) (nesting depth added 32). 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.
floem_editor_core::buffer::diff::expand_diff_lines (cognitive 30) editor-core/src/buffer/diff.rs:39— floem_editor_core::buffer::diff::expand_diff_lines has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (22 pts), boolean chains 4, match/switch 1 (3 pts), 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.
floem_editor_core::indent::auto_detect_indent_style (cognitive 30) editor-core/src/indent.rs:101— floem_editor_core::indent::auto_detect_indent_style has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (15 pts), match/switch 3 (7 pts), boolean chains 5, loops 2 (3 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.
floem_editor_core::util::has_unmatched_pair (cognitive 17) editor-core/src/util.rs:85— floem_editor_core::util::has_unmatched_pair has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ApplicationHandle::handle_update_event (cognitive 45) src/app/handle.rs:131— ApplicationHandle::handle_update_event has cognitive complexity 45 (threshold 15). Drivers by points: if/else 12 (30 pts), loops 4 (10 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ApplicationHandle::new_window (cognitive 33) src/app/handle.rs:429— ApplicationHandle::new_window has cognitive complexity 33 (threshold 15). Drivers by points: if/else 28 (32 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ApplicationHandle::handle_window_event (cognitive 18) src/app/handle.rs:246— ApplicationHandle::handle_window_event has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), match/switch 4, boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ApplicationHandle::handle_updates_for_all_windows_budgeted (cognitive 16) src/app/handle.rs:672— ApplicationHandle::handle_updates_for_all_windows_budgeted has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Cursor::yank (cognitive 34) editor-core/src/cursor.rs:384— Cursor::yank has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (21 pts), match/switch 3 (8 pts), loops 2 (5 pts) (nesting depth added 20). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Cursor::set_offset (cognitive 33) editor-core/src/cursor.rs:509— Cursor::set_offset has cognitive complexity 33 (threshold 15). Drivers by points: if/else 14 (28 pts), boolean chains 4, match/switch 1 (nesting depth added 14). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Cursor::edit_selection (cognitive 20) editor-core/src/cursor.rs:293— Cursor::edit_selection has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (10 pts), match/switch 3 (7 pts), loops 1 (3 pts) (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.
Cursor::add_region (cognitive 17) editor-core/src/cursor.rs:609— Cursor::add_region has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (16 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.
Duplicated block (10 lines × 2) src/event/dispatch.rs:727— src/event/dispatch.rs:727-736 | src/event/dispatch.rs:769-778 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `self` to `crate) fn dispatch_directed( &mut` in one and `&mut` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (10 lines × 2) src/headless.rs:608— src/headless.rs:608-617 | src/headless.rs:681-690 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/headless.rs:608` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) src/headless.rs:629— src/headless.rs:629-638 | src/headless.rs:702-711 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/headless.rs:629` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) src/views/container.rs:62— src/views/container.rs:62-71 | src/views/dyn_view.rs:23-32 — 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.
ApplicationHandle::handle_window_event (cyclomatic 64) src/app/handle.rs:246— ApplicationHandle::handle_window_event has cyclomatic complexity 64 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
ApplicationHandle::handle_update_event (cyclomatic 29) src/app/handle.rs:131— ApplicationHandle::handle_update_event 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.
ApplicationHandle::new_window (cyclomatic 29) src/app/handle.rs:429— ApplicationHandle::new_window has cyclomatic complexity 29 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TextInput::handle_key_down (cognitive 46) src/views/text_input.rs:890— TextInput::handle_key_down has cognitive complexity 46 (threshold 15). Drivers by points: if/else 20 (36 pts), match/switch 6 (10 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TextInput::event (cognitive 45) src/views/text_input.rs:1254— TextInput::event has cognitive complexity 45 (threshold 15). Drivers by points: if/else 21 (38 pts), boolean chains 4, match/switch 2 (3 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TextInput::move_cursor (cognitive 20) src/views/text_input.rs:396— TextInput::move_cursor has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (11 pts), match/switch 3 (5 pts), loops 2 (4 pts) (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Change coupling: container.rs ↔ stack.rs src/views/container.rs:1— `src/views/container.rs` and `src/views/stack.rs` change together 73% of the time (11 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `7111c39e` Add lazy view construction with Intermediate type on IntoView (#995); `236b8e2a` view extension trait updates (#578); `c4cd0d16` Box up views in containers (#146) — run `git show` on any of them.
Change coupling: mod.rs ↔ context.rs src/app/mod.rs:1— `src/app/mod.rs` and `src/context.rs` change together 53% of the time (39 of the 73 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 39 shared commits counted here, the most recent 3 are `1669a703` support window menus (#877) (at that commit the file was still `src/app.rs`); `05f6012e` allow access to gpu resources in the paint ctx (#838) (at that commit the file was still `src/app.rs`); `7e5e78ae` Default to std::sync::mpsc, introduce `crossbeam` feature (#775) (at that commit the file was still `src/app.rs`) — run `git show` on any of them.
Change coupling: label.rs ↔ stack.rs src/views/label.rs:1— `src/views/label.rs` and `src/views/stack.rs` change together 50% of the time (13 of the 26 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `7111c39e` Add lazy view construction with Intermediate type on IntoView (#995); `d10a3c22` Add a style pass (#142); `1d62633d` layout change (at that commit the file was still `src/stack.rs`) — run `git show` on any of them.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (4 members, 50+ identical tokens) src/receiver_signal/common/executors.rs:422— src/receiver_signal/common/executors.rs:422-451 | src/receiver_signal/common/executors.rs:459-494 | src/receiver_signal/common/executors.rs:502-531 | src/receiver_signal/common/executors.rs:539-574 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) src/style/components.rs:225— src/style/components.rs:225-233 | src/style/components.rs:332-340 | src/style/components.rs:577-585 | src/style/components.rs:683-691 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) src/style/components.rs:262— src/style/components.rs:262-269 | src/style/components.rs:368-375 | src/style/components.rs:613-620 | src/style/components.rs:719-726 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×3
Edited copy of a member (10 corresponding lines) src/style/values.rs:904— src/style/values.rs:904-914 | src/style/values.rs:962-971 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) src/style/unit.rs:508— src/style/unit.rs:508-517 | src/style/unit.rs:519-528 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) reactive/src/read.rs:177— reactive/src/read.rs:177-186 | reactive/src/read.rs:191-200 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×3
Edited copy of a member (17 corresponding lines) src/views/text_editor.rs:78— src/views/text_editor.rs:78-94 | src/views/text_editor.rs:102-124 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) src/text/layout.rs:745— src/text/layout.rs:745-761 | src/text/layout.rs:764-780 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) editor-core/src/buffer/rope_text.rs:150— editor-core/src/buffer/rope_text.rs:150-166 | editor-core/src/buffer/rope_text.rs:168-188 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×3
Edited copy of a member (8 corresponding lines) editor-core/src/selection.rs:391— editor-core/src/selection.rs:391-398 | editor-core/src/selection.rs:418-425 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) src/style/mod.rs:1219— src/style/mod.rs:1219-1228 | src/window/state.rs:311-318 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) src/views/label.rs:260— src/views/label.rs:260-267 | src/views/rich_text.rs:130-146 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (23 lines × 2) src/receiver_signal/common/executors.rs:133— src/receiver_signal/common/executors.rs:133-155 | src/receiver_signal/common/executors.rs:188-210 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/receiver_signal/common/executors.rs:133` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) src/receiver_signal/common/executors.rs:684— src/receiver_signal/common/executors.rs:684-706 | src/receiver_signal/common/executors.rs:730-752 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/receiver_signal/common/executors.rs:684` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) vello/src/lib.rs:60— vello/src/lib.rs:60-82 | vger/src/lib.rs:56-78 — before extracting anything, compare `vello/src/lib.rs` and `vger/src/lib.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12–13 lines × 2) editor-core/src/editor.rs:1352— editor-core/src/editor.rs:1352-1363 | editor-core/src/editor.rs:1418-1430 — 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–13 lines × 2) src/event/dispatch.rs:393— src/event/dispatch.rs:393-404 | src/event/dispatch.rs:438-450 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/event/dispatch.rs:393` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–13 lines × 2) vello/src/lib.rs:112— vello/src/lib.rs:112-124 | vello/src/lib.rs:170-181 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `vello/src/lib.rs:112` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 3) editor-core/src/editor.rs:1268— editor-core/src/editor.rs:1268-1275 | editor-core/src/editor.rs:1293-1300 | editor-core/src/editor.rs:1344-1351 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor-core/src/editor.rs:1268` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 3) src/views/editor/view.rs:438— src/views/editor/view.rs:438-446 | src/views/label.rs:356-363 | src/views/rich_text.rs:64-71 — before extracting anything, compare `src/views/label.rs` and `src/views/rich_text.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 3) reactive/src/effect.rs:45— reactive/src/effect.rs:45-52 | reactive/src/effect.rs:108-115 | reactive/src/memo.rs:266-273 — 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 (6 lines × 2) src/views/label.rs:230— src/views/label.rs:230-235 | src/views/text_input.rs:790-795 — before extracting anything, compare `src/views/label.rs` and `src/views/text_input.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/views/label.rs:230` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (6 lines × 2) src/views/virtual_stack.rs:204— src/views/virtual_stack.rs:204-209 | src/views/virtual_stack.rs:220-225 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/views/virtual_stack.rs:204` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) src/animate/mod.rs:1109— src/animate/mod.rs:1109-1114 | src/animate/mod.rs:1141-1146 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/animate/mod.rs:1109` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Off the main sequence: floem-editor-core — floem-editor-core: abstractness 0.11, instability 0.00, distance 0.89 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: floem_renderer — floem_renderer: abstractness 0.18, instability 0.00, distance 0.82 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: floem_reactive — floem_reactive: abstractness 0.21, instability 0.00, distance 0.79 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Action::do_edit (cyclomatic 124) editor-core/src/editor.rs:775— Action::do_edit has cyclomatic complexity 124 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Action::insert (cyclomatic 33) editor-core/src/editor.rs:89— Action::insert 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.
WindowHandle::process_update_messages (cyclomatic 49) src/window/handle.rs:1102— WindowHandle::process_update_messages has cyclomatic complexity 49 (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.
WindowHandle::set_cursor (cyclomatic 28) src/window/handle.rs:1424— WindowHandle::set_cursor has cyclomatic complexity 28 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
floem_editor_core::buffer::diff::rope_diff (cyclomatic 34) editor-core/src/buffer/diff.rs:77— floem_editor_core::buffer::diff::rope_diff has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
floem_editor_core::indent::auto_detect_indent_style (cyclomatic 21) editor-core/src/indent.rs:101— floem_editor_core::indent::auto_detect_indent_style has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
TextInput::event (cyclomatic 31) src/views/text_input.rs:1254— TextInput::event has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TextInput::handle_key_down (cyclomatic 29) src/views/text_input.rs:890— TextInput::handle_key_down 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.
XxxComment src/window/id.rs:332— // XXX log any returned error? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment src/window/id.rs:341— // XXX log any returned error? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Style::apply_iter (cognitive 44) src/style/mod.rs:1301— Style::apply_iter has cognitive complexity 44 (threshold 15). Drivers by points: if/else 14 (34 pts), loops 3 (7 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Style::inherited_equal (cognitive 16) src/style/cache.rs:569— Style::inherited_equal has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), boolean chains 2, 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.
Scroll::event (cognitive 38) src/views/scroll.rs:959— Scroll::event has cognitive complexity 38 (threshold 15). Drivers by points: if/else 17 (32 pts), boolean chains 6 (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.
Scroll::paint (cognitive 17) src/views/scroll.rs:1046— Scroll::paint has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 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.
WindowHandle::process_update_messages (cognitive 38) src/window/handle.rs:1102— WindowHandle::process_update_messages has cognitive complexity 38 (threshold 15). Drivers by points: if/else 8 (28 pts), loops 3 (7 pts), match/switch 1 (3 pts) (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.
WindowHandle::process_update_budgeted (cognitive 21) src/window/handle.rs:943— WindowHandle::process_update_budgeted has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Animation::advance (cognitive 32) src/animate/mod.rs:816— Animation::advance has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (27 pts), match/switch 2 (3 pts), boolean chains 2 (nesting depth added 14). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Animation::animate_into (cognitive 20) src/animate/mod.rs:1075— Animation::animate_into has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 6 (8 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EditorView::paint_normal_selection (cognitive 21) src/views/editor/view.rs:467— EditorView::paint_normal_selection has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EditorView::paint_text (cognitive 19) src/views/editor/view.rs:871— EditorView::paint_text has cognitive complexity 19 (threshold 15). Drivers by points: loops 4 (9 pts), if/else 4 (5 pts), match/switch 1 (4 pts), boolean chains 1 (nesting depth added 9). 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.
DragTracker::on_pointer_move (cognitive 19) src/event/drag_state.rs:474— DragTracker::on_pointer_move has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (12 pts), match/switch 2 (4 pts), loops 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.
DragTracker::on_pointer_up (cognitive 18) src/event/drag_state.rs:596— DragTracker::on_pointer_up has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 1 (2 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.
TooManyFields: WindowState src/window/state.rs:100— TooManyFields — 45 stored fields beside 63 methods. The bar is 30 stored fields; this is 15 over it, 1.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: ViewState src/view/state.rs:321— TooManyFields — 39 stored fields beside 9 methods. The bar is 30 stored fields; this is 9 over it, 1.30× 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.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (5 members, 50+ identical tokens) src/style/components.rs:234— src/style/components.rs:234-260 | src/style/components.rs:341-366 | src/style/components.rs:480-505 | src/style/components.rs:586-611 | src/style/components.rs:692-717 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) src/views/editor/gutter.rs:187— src/views/editor/gutter.rs:187-262 | src/views/editor/view.rs:437-464 | src/views/label.rs:355-380 | src/views/rich_text.rs:63-88 | src/views/text_input.rs:350-385 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Edited copy of a member (37 corresponding lines) · ×2
Edited copy of a member (37 corresponding lines) src/views/dyn_stack.rs:90— src/views/dyn_stack.rs:90-126 | src/views/tab.rs:187-235 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (37 corresponding lines) src/views/editor/visual_line.rs:596— src/views/editor/visual_line.rs:596-636 | src/views/editor/visual_line.rs:672-708 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×2
Edited copy of a member (29 corresponding lines) src/views/editor/text.rs:376— src/views/editor/text.rs:376-404 | src/views/editor/text.rs:406-434 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (29 corresponding lines) editor-core/src/editor.rs:667— editor-core/src/editor.rs:667-695 | editor-core/src/editor.rs:697-726 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (39 corresponding lines) · ×2
Edited copy of a member (39 corresponding lines) src/receiver_signal/resource/builder.rs:467— src/receiver_signal/resource/builder.rs:467-505 | src/receiver_signal/resource/builder.rs:524-562 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (39 corresponding lines) src/views/slider.rs:424— src/views/slider.rs:424-463 | src/views/slider.rs:516-554 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×2
Edited copy of a member (20 corresponding lines) src/views/label.rs:221— src/views/label.rs:221-246 | src/views/text_input.rs:781-800 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) reactive/src/scope.rs:294— reactive/src/scope.rs:294-314 | reactive/src/scope.rs:363-382 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×2
Edited copy of a member (31 corresponding lines) src/views/resizable.rs:183— src/views/resizable.rs:183-220 | src/views/resizable.rs:336-366 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (31 corresponding lines) src/layout/screen.rs:19— src/layout/screen.rs:19-52 | src/layout/screen.rs:57-87 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×2
Edited copy of a member (16 corresponding lines) src/text/layout.rs:564— src/text/layout.rs:564-583 | src/text/layout.rs:594-609 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) src/views/container.rs:58— src/views/container.rs:58-73 | src/views/dyn_view.rs:19-34 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×2
Edited copy of a member (19 corresponding lines) src/views/radio_button.rs:115— src/views/radio_button.rs:115-137 | src/views/radio_button.rs:175-193 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) src/views/editor/movement.rs:237— src/views/editor/movement.rs:237-255 | src/views/editor/movement.rs:265-283 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 17+ corresponding lines) · ×2
Edited copies of one member (3 members, 17+ corresponding lines) editor-core/src/word.rs:79— editor-core/src/word.rs:79-104 | editor-core/src/word.rs:205-221 | editor-core/src/word.rs:234-251 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 17+ corresponding lines) src/views/editor/mod.rs:575— src/views/editor/mod.rs:575-595 | src/views/editor/mod.rs:597-613 | src/views/editor/mod.rs:615-633 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 12+ corresponding lines) · ×2
Edited copies of one member (3 members, 12+ corresponding lines) src/style/custom.rs:397— src/style/custom.rs:397-408 | src/views/decorator.rs:80-95 | src/views/decorator.rs:522-541 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 12+ corresponding lines) src/views/rich_text.rs:248— src/views/rich_text.rs:248-259 | src/views/rich_text.rs:264-277 | src/views/rich_text.rs:282-295 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×2
Edited copy of a member (7 corresponding lines) src/style/values.rs:932— src/style/values.rs:932-939 | src/style/values.rs:988-994 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) src/animate/mod.rs:210— src/animate/mod.rs:210-222 | src/animate/mod.rs:224-230 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (28 lines × 2) src/views/editor/mod.rs:1045— src/views/editor/mod.rs:1045-1072 | src/views/editor/mod.rs:1092-1119 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `point` to `Point) -> (usize` in one and `Point` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (28 lines × 2) vello/src/lib.rs:541— vello/src/lib.rs:541-568 | vger/src/lib.rs:244-271 — before extracting anything, compare `vello/src/lib.rs` and `vger/src/lib.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vello/src/lib.rs:541` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (23–24 lines × 2) src/views/editor/visual_line.rs:613— src/views/editor/visual_line.rs:613-636 | src/views/editor/visual_line.rs:686-708 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/views/editor/visual_line.rs:613` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23–24 lines × 2) vello/src/lib.rs:84— vello/src/lib.rs:84-107 | vger/src/lib.rs:83-105 — before extracting anything, compare `vello/src/lib.rs` and `vger/src/lib.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 2) editor-core/src/editor.rs:668— editor-core/src/editor.rs:668-687 | editor-core/src/editor.rs:698-717 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor-core/src/editor.rs:668` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) reactive/src/context.rs:83— reactive/src/context.rs:83-102 | reactive/src/context.rs:133-152 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 2) editor-core/src/editor.rs:800— editor-core/src/editor.rs:800-816 | editor-core/src/editor.rs:835-851 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) src/animate/easing.rs:254— src/animate/easing.rs:254-270 | src/animate/easing.rs:309-325 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/animate/easing.rs:254` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–12 lines × 2) src/style/theme.rs:274— src/style/theme.rs:274-284 | src/style/values.rs:2136-2147 — 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) src/view/mod.rs:373— src/view/mod.rs:373-383 | src/view/mod.rs:587-598 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/view/mod.rs:373` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/view/mod.rs:372` calls `child_fn_for_effect` and `src/view/mod.rs:584` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10–11 lines × 2) src/style/mod.rs:932— src/style/mod.rs:932-941 | src/style/mod.rs:959-969 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/style/mod.rs:932` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10–11 lines × 2) src/views/img.rs:159— src/views/img.rs:159-169 | src/views/img.rs:194-203 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/views/img.rs:194` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: the declarations holding them bind `image` to `impl Fn() -> Vec<u8> + 'static` in one and `impl Fn() -> PathBuf + 'static` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (8–9 lines × 2) src/inspector/mod.rs:237— src/inspector/mod.rs:237-244 | src/inspector/mod.rs:373-381 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/inspector/mod.rs:373` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8–9 lines × 2) src/views/editor/gutter.rs:126— src/views/editor/gutter.rs:126-134 | src/views/editor/view.rs:658-665 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/views/editor/gutter.rs:126` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/views/editor/view.rs:656` calls `Some` and `src/views/editor/gutter.rs:123` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 4) src/receiver_signal/common/executors.rs:426— src/receiver_signal/common/executors.rs:426-433 | src/receiver_signal/common/executors.rs:464-471 | src/receiver_signal/common/executors.rs:506-513 | src/receiver_signal/common/executors.rs:544-551 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/receiver_signal/common/executors.rs:426` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 4) src/style/components.rs:226— src/style/components.rs:226-233 | src/style/components.rs:333-340 | src/style/components.rs:578-585 | src/style/components.rs:684-691 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
StyleCx::style_view (cyclomatic 51) src/style/cx.rs:241— StyleCx::style_view has cyclomatic complexity 51 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GlobalEventCx::route_window_event (cyclomatic 24) src/event/dispatch.rs:358— GlobalEventCx::route_window_event 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.
Scroll::event (cyclomatic 22) src/views/scroll.rs:959— Scroll::event 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.
Animation::advance (cyclomatic 20) src/animate/mod.rs:816— Animation::advance 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.
BorderPathIter::next (cyclomatic 20) src/paint/border_path_iter.rs:95— BorderPathIter::next 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.
Style::apply_iter (cyclomatic 20) src/style/mod.rs:1301— Style::apply_iter 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.
Label::event (cyclomatic 19) src/views/label.rs:396— Label::event 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.
StylePropInfo::new (cyclomatic 17) src/style/props.rs:205— StylePropInfo::new 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.
Cursor::set_offset (cyclomatic 16) editor-core/src/cursor.rs:509— Cursor::set_offset 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.
ParseList::next (cyclomatic 16) renderer/src/text/attrs.rs:655— ParseList::next has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
SvgLayoutData::create_taffy_layout_fn (cyclomatic 16) src/views/svg.rs:60— SvgLayoutData::create_taffy_layout_fn 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.
Yanked release: clipboard-win — `clipboard-win` resolves to 5.4.1 in the committed REDACTED, and crates.io reports that release as YANKED. A yanked release is one the publisher has withdrawn and asked you to stop using; it keeps resolving only so existing locks do not break. The current stable release is 5.4.3. Run `cargo update -p clipboard-win` and commit the updated lock.
HackComment src/views/editor/view.rs:158— // Hacky method to get an empty iterator of the same type — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
StyleCx::style_view (cognitive 88) src/style/cx.rs:241— StyleCx::style_view has cognitive complexity 88 (threshold 15). Drivers by points: if/else 42 (71 pts), boolean chains 12, loops 2 (5 pts) (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GlobalEventCx::route_window_event (cognitive 62) src/event/dispatch.rs:358— GlobalEventCx::route_window_event has cognitive complexity 62 (threshold 15). Drivers by points: if/else 13 (39 pts), loops 6 (22 pts), match/switch 1 (nesting depth added 42). 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.
BorderPathIter::next (cognitive 45) src/paint/border_path_iter.rs:95— BorderPathIter::next has cognitive complexity 45 (threshold 15). Drivers by points: if/else 19 (40 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (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.
EventCx::dispatch_one (cognitive 35) src/event/dispatch.rs:940— EventCx::dispatch_one has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (27 pts), loops 2 (6 pts), boolean chains 1, match/switch 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Buffer::compute_undo (cognitive 27) editor-core/src/buffer/mod.rs:509— Buffer::compute_undo has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (24 pts), loops 2, 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.
TextLayout::selection_geometry_with_line_metrics (cognitive 27) src/text/layout.rs:663— TextLayout::selection_geometry_with_line_metrics has cognitive complexity 27 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 3 (10 pts), boolean chains 2 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Resizable::update (cognitive 27) src/views/resizable.rs:405— Resizable::update has cognitive complexity 27 (threshold 15). Drivers by points: if/else 5 (16 pts), loops 3 (9 pts), match/switch 1 (2 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WindowState::build_style_traversal (cognitive 27) src/window/state.rs:423— WindowState::build_style_traversal has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 5 (11 pts), boolean chains 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.
EditorGutterView::paint (cognitive 26) src/views/editor/gutter.rs:87— EditorGutterView::paint has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 2 (4 pts), match/switch 1 (2 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.
Label::event (cognitive 25) src/views/label.rs:396— Label::event has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (17 pts), match/switch 3 (6 pts), boolean chains 2 (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.
SvgLayoutData::create_taffy_layout_fn (cognitive 24) src/views/svg.rs:60— SvgLayoutData::create_taffy_layout_fn has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 4, 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.
InspectorImageView::event (cognitive 22) src/inspector/view.rs:722— InspectorImageView::event has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (19 pts), match/switch 2 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StylePropInfo::new (cognitive 20) src/style/props.rs:205— StylePropInfo::new has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (13 pts), match/switch 5 (7 pts) (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TextLayoutState::finalize_for_width (cognitive 19) src/text/layout_state.rs:263— TextLayoutState::finalize_for_width has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VgerRenderer::fill (cognitive 19) vger/src/lib.rs:423— VgerRenderer::fill has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (14 pts), match/switch 2 (3 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ToggleButton::event (cognitive 18) src/views/toggle_button.rs:325— ToggleButton::event has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (16 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.
TinySkiaRenderer::finish (cognitive 18) tiny_skia/src/lib.rs:1497— TinySkiaRenderer::finish has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (8 pts), loops 2 (7 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CapturedData::get_children (cognitive 17) src/inspector/data.rs:167— CapturedData::get_children has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 1 (3 pts), boolean chains 1, match/switch 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Dropdown::update (cognitive 17) src/views/dropdown.rs:235— Dropdown::update has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (14 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.
Change-coupling hub: scroll.rs → clip.rs, container.rs, tab.rs, virtual_list.rs src/views/scroll.rs— `src/views/scroll.rs` changes together with 4 other files — `src/views/clip.rs`, `src/views/container.rs`, `src/views/tab.rs`, `src/views/virtual_list.rs` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
D4 · Code Duplication· Near-duplicate member family (6 members, 25 shared lines) · ×1
Near-duplicate member family (6 members, 25 shared lines) src/receiver_signal/common/executors.rs:21— src/receiver_signal/common/executors.rs:21-58 | src/receiver_signal/common/executors.rs:67-104 | src/receiver_signal/common/executors.rs:113-159 | src/receiver_signal/common/executors.rs:168-214 | src/receiver_signal/common/executors.rs:223-271 | src/receiver_signal/common/executors.rs:280-328 — These 6 members are variants of one another: a block of 25 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 6 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 6 times.
Near-duplicate member pair (50 shared lines) src/view/mod.rs:334— src/view/mod.rs:334-399 | src/view/mod.rs:548-614 — These two members are variants of one another: 50 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (38 shared lines) src/style/values.rs:321— src/style/values.rs:321-462 | src/style/values.rs:469-605 — These two members are variants of one another: 38 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) src/receiver_signal/common/executors.rs:336— src/receiver_signal/common/executors.rs:336-370 | src/receiver_signal/common/executors.rs:378-412 | src/receiver_signal/common/executors.rs:582-617 | src/receiver_signal/common/executors.rs:625-660 | src/receiver_signal/common/executors.rs:668-706 | src/receiver_signal/common/executors.rs:714-752 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 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 6 times.
D4 · Code Duplication· Edited copy of a member (99 corresponding lines) · ×1
Edited copy of a member (99 corresponding lines) vello/src/lib.rs:489— vello/src/lib.rs:489-590 | vger/src/lib.rs:205-303 — These two members are one piece of code written twice and then edited apart: 99 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (108 corresponding lines) · ×1
Edited copy of a member (108 corresponding lines) src/views/editor/keypress/mod.rs:213— src/views/editor/keypress/mod.rs:213-335 | src/views/editor/keypress/mod.rs:341-448 — These two members are one piece of code written twice and then edited apart: 108 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (42 corresponding lines) · ×1
Edited copy of a member (42 corresponding lines) src/animate/easing.rs:249— src/animate/easing.rs:249-290 | src/animate/easing.rs:304-348 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (34 corresponding lines) · ×1
Edited copy of a member (34 corresponding lines) src/view/id.rs:370— src/view/id.rs:370-405 | src/view/id.rs:419-452 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (52 corresponding lines) · ×1
Edited copy of a member (52 corresponding lines) src/window/handle.rs:943— src/window/handle.rs:943-1009 | src/window/handle.rs:1012-1063 — These two members are one piece of code written twice and then edited apart: 52 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×1
Edited copy of a member (26 corresponding lines) renderer/src/text/attrs.rs:353— renderer/src/text/attrs.rs:353-378 | renderer/src/text/attrs.rs:391-421 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×1
Edited copy of a member (25 corresponding lines) editor-core/src/paragraph.rs:56— editor-core/src/paragraph.rs:56-81 | editor-core/src/paragraph.rs:83-107 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (38 corresponding lines) · ×1
Edited copy of a member (38 corresponding lines) src/views/editor/visual_line.rs:1016— src/views/editor/visual_line.rs:1016-1053 | src/views/editor/visual_line.rs:1060-1102 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) src/style/cx.rs:812— src/style/cx.rs:812-841 | src/views/dyn_container.rs:195-226 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) src/views/editor/mod.rs:362— src/views/editor/mod.rs:362-385 | src/views/editor/mod.rs:387-409 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 25+ corresponding lines) · ×1
Edited copies of one member (3 members, 25+ corresponding lines) reactive/src/signal.rs:503— reactive/src/signal.rs:503-527 | reactive/src/signal.rs:530-554 | reactive/src/signal.rs:563-587 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×1
Edited copy of a member (18 corresponding lines) src/headless.rs:649— src/headless.rs:649-666 | src/headless.rs:722-739 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 19+ corresponding lines) · ×1
Edited copies of one member (3 members, 19+ corresponding lines) src/style/cx.rs:843— src/style/cx.rs:843-865 | src/style/cx.rs:867-885 | src/views/dyn_container.rs:227-247 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 13+ corresponding lines) · ×1
Edited copies of one member (3 members, 13+ corresponding lines) src/views/editor/mod.rs:682— src/views/editor/mod.rs:682-698 | src/views/editor/mod.rs:700-712 | src/views/editor/mod.rs:714-726 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 16+ corresponding lines) · ×1
Edited copies of one member (4 members, 16+ corresponding lines) src/style/mod.rs:3116— src/style/mod.rs:3116-3131 | src/style/mod.rs:3133-3148 | src/style/mod.rs:3160-3175 | src/style/mod.rs:3177-3192 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×1
Edited copy of a member (22 corresponding lines) src/action.rs:165— src/action.rs:165-186 | src/action.rs:192-217 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 19+ corresponding lines) · ×1
Edited copies of one member (4 members, 19+ corresponding lines) src/headless.rs:560— src/headless.rs:560-578 | src/headless.rs:586-604 | src/headless.rs:742-762 | src/headless.rs:765-785 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 12+ corresponding lines) · ×1
Edited copies of one member (4 members, 12+ corresponding lines) reactive/src/derived.rs:182— reactive/src/derived.rs:182-193 | reactive/src/derived.rs:198-210 | reactive/src/derived.rs:425-436 | reactive/src/derived.rs:441-453 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 15+ corresponding lines) · ×1
Edited copies of one member (3 members, 15+ corresponding lines) reactive/src/effect.rs:248— reactive/src/effect.rs:248-262 | reactive/src/effect.rs:264-281 | reactive/src/effect.rs:289-306 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 15+ corresponding lines) · ×1
Edited copies of one member (5 members, 15+ corresponding lines) src/receiver_signal/channel_signal/builder.rs:297— src/receiver_signal/channel_signal/builder.rs:297-311 | src/receiver_signal/channel_signal/builder.rs:324-338 | src/receiver_signal/future_signal/builder.rs:139-153 | src/receiver_signal/stream_signal/builder.rs:188-202 | src/receiver_signal/stream_signal/builder.rs:214-228 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 1+ corresponding lines) · ×1
Edited copies of one member (5 members, 1+ corresponding lines) src/style/theme.rs:78— src/style/theme.rs:78-78 | src/style/theme.rs:84-84 | src/style/theme.rs:90-90 | src/style/theme.rs:96-96 | src/style/theme.rs:102-102 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 9+ corresponding lines) · ×1
Edited copies of one member (6 members, 9+ corresponding lines) src/style/values.rs:739— src/style/values.rs:739-748 | src/style/values.rs:915-924 | src/style/values.rs:940-949 | src/style/values.rs:972-980 | src/style/values.rs:995-1003 | src/style/values.rs:1432-1440 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (7 members, 12+ corresponding lines) · ×1
Edited copies of one member (7 members, 12+ corresponding lines) src/style/mod.rs:3251— src/style/mod.rs:3251-3262 | src/style/mod.rs:3265-3276 | src/style/mod.rs:3280-3291 | src/style/mod.rs:3366-3377 | src/style/mod.rs:3380-3391 | src/style/mod.rs:3394-3405 | src/style/mod.rs:3408-3419 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×1
Edited copy of a member (14 corresponding lines) editor-core/src/buffer/rope_text.rs:302— editor-core/src/buffer/rope_text.rs:302-315 | editor-core/src/buffer/rope_text.rs:335-348 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 14+ corresponding lines) · ×1
Edited copies of one member (3 members, 14+ corresponding lines) src/view/id.rs:1314— src/view/id.rs:1314-1327 | src/view/id.rs:1332-1345 | src/view/id.rs:1354-1367 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 15+ corresponding lines) · ×1
Edited copies of one member (6 members, 15+ corresponding lines) src/view/id.rs:1584— src/view/id.rs:1584-1598 | src/view/id.rs:1603-1617 | src/view/id.rs:1622-1636 | src/view/id.rs:1641-1655 | src/view/id.rs:1661-1677 | src/view/id.rs:1682-1699 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 6+ corresponding lines) · ×1
Edited copies of one member (3 members, 6+ corresponding lines) skia/src/lib.rs:144— skia/src/lib.rs:144-149 | tiny_skia/src/lib.rs:1097-1103 | vger/src/lib.rs:148-154 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 8+ corresponding lines) · ×1
Edited copies of one member (4 members, 8+ corresponding lines) src/views/dropdown.rs:500— src/views/dropdown.rs:500-507 | src/views/resizable.rs:510-517 | src/views/scroll.rs:631-639 | src/views/svg.rs:197-204 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×1
Edited copy of a member (6 corresponding lines) src/style/recalc.rs:266— src/style/recalc.rs:266-271 | src/window/state.rs:629-634 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (42 lines × 2) src/receiver_signal/common/executors.rs:226— src/receiver_signal/common/executors.rs:226-267 | src/receiver_signal/common/executors.rs:283-324 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/receiver_signal/common/executors.rs:226` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (37–38 lines × 2) src/window/handle.rs:947— src/window/handle.rs:947-983 | src/window/handle.rs:1013-1050 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/window/handle.rs:947` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `self` to `crate) fn process_update_budgeted(&mut` in one and `crate) fn process_update_no_paint(&mut` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (35 lines × 2) src/receiver_signal/resource/builder.rs:471— src/receiver_signal/resource/builder.rs:471-505 | src/receiver_signal/resource/builder.rs:528-562 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/receiver_signal/resource/builder.rs:471` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (32–33 lines × 2) src/platform/context_menu.rs:34— src/platform/context_menu.rs:34-65 | src/platform/context_menu.rs:68-100 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (24–26 lines × 2) src/style/values.rs:329— src/style/values.rs:329-354 | src/style/values.rs:477-500 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/style/values.rs:329` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 4) src/receiver_signal/common/executors.rs:24— src/receiver_signal/common/executors.rs:24-44 | src/receiver_signal/common/executors.rs:70-90 | src/receiver_signal/common/executors.rs:116-136 | src/receiver_signal/common/executors.rs:171-191 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/receiver_signal/common/executors.rs:24` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 2) src/views/virtual_stack.rs:341— src/views/virtual_stack.rs:341-361 | src/views/virtual_stack.rs:392-412 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (19–20 lines × 3) src/views/label.rs:361— src/views/label.rs:361-379 | src/views/rich_text.rs:69-87 | src/views/text_input.rs:365-384 — before extracting anything, compare `src/views/label.rs` and `src/views/rich_text.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/views/label.rs:361` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19–20 lines × 2) src/view/id.rs:386— src/view/id.rs:386-405 | src/view/id.rs:434-452 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/view/id.rs:386` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `children` to `Vec<Box<dyn View>>` in one and `impl Iterator<Item = Box<dyn View>>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (24 lines × 2) src/views/dyn_stack.rs:92— src/views/dyn_stack.rs:92-115 | src/views/tab.rs:190-213 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/views/dyn_stack.rs:92` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) src/views/editor/text.rs:386— src/views/editor/text.rs:386-404 | src/views/editor/text.rs:416-434 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/views/editor/text.rs:386` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18–19 lines × 2) src/window/handle.rs:698— src/window/handle.rs:698-715 | src/window/handle.rs:742-760 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/window/handle.rs:698` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 5) src/style/components.rs:236— src/style/components.rs:236-253 | src/style/components.rs:343-360 | src/style/components.rs:482-499 | src/style/components.rs:588-605 | src/style/components.rs:694-711 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/style/components.rs:236` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/style/components.rs:254` calls `into_any` and `src/style/components.rs:361` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (17–18 lines × 2) tiny_skia/src/lib.rs:136— tiny_skia/src/lib.rs:136-153 | vger/src/lib.rs:562-578 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `tiny_skia/src/lib.rs:136` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 4) src/receiver_signal/common/executors.rs:355— src/receiver_signal/common/executors.rs:355-370 | src/receiver_signal/common/executors.rs:397-412 | src/receiver_signal/common/executors.rs:602-617 | src/receiver_signal/common/executors.rs:645-660 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/receiver_signal/common/executors.rs:355` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) editor-core/src/editor.rs:1281— editor-core/src/editor.rs:1281-1296 | editor-core/src/editor.rs:1306-1321 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor-core/src/editor.rs:1281` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12–16 lines × 2) src/style/cx.rs:871— src/style/cx.rs:871-882 | src/views/dyn_container.rs:230-245 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15 lines × 2) src/animate/mod.rs:1018— src/animate/mod.rs:1018-1032 | src/animate/mod.rs:1051-1065 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/animate/mod.rs:1018` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–15 lines × 2) src/view/mod.rs:388— src/view/mod.rs:388-399 | src/view/mod.rs:600-614 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/view/mod.rs:388` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 3) src/event/drag_state.rs:675— src/event/drag_state.rs:675-688 | src/event/drag_state.rs:689-702 | src/event/drag_state.rs:703-716 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/event/drag_state.rs:675` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 6) src/receiver_signal/common/executors.rs:22— src/receiver_signal/common/executors.rs:22-34 | src/receiver_signal/common/executors.rs:68-80 | src/receiver_signal/common/executors.rs:114-126 | src/receiver_signal/common/executors.rs:169-181 | src/receiver_signal/common/executors.rs:224-236 | src/receiver_signal/common/executors.rs:281-293 — all 6 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 (13 lines × 4) src/views/editor/gutter.rs:249— src/views/editor/gutter.rs:249-262 | src/views/label.rs:368-380 | src/views/rich_text.rs:76-88 | src/views/text_input.rs:373-385 — before extracting anything, compare `src/views/label.rs` and `src/views/rich_text.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/views/editor/gutter.rs:249` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 6) src/receiver_signal/common/executors.rs:37— src/receiver_signal/common/executors.rs:37-48 | src/receiver_signal/common/executors.rs:83-94 | src/receiver_signal/common/executors.rs:129-140 | src/receiver_signal/common/executors.rs:184-195 | src/receiver_signal/common/executors.rs:239-250 | src/receiver_signal/common/executors.rs:296-307 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/receiver_signal/common/executors.rs:37` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10–12 lines × 2) src/inspector/mod.rs:320— src/inspector/mod.rs:320-329 | src/inspector/mod.rs:402-413 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/inspector/mod.rs:320` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10–11 lines × 6) src/receiver_signal/common/executors.rs:337— src/receiver_signal/common/executors.rs:337-346 | src/receiver_signal/common/executors.rs:379-388 | src/receiver_signal/common/executors.rs:583-593 | src/receiver_signal/common/executors.rs:626-636 | src/receiver_signal/common/executors.rs:669-679 | src/receiver_signal/common/executors.rs:715-725 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/receiver_signal/common/executors.rs:337` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–11 lines × 2) src/style/values.rs:2466— src/style/values.rs:2466-2476 | src/style/values.rs:2478-2486 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/style/values.rs:2466` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8–11 lines × 2) src/text/layout.rs:569— src/text/layout.rs:569-579 | src/text/layout.rs:599-606 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 3) editor-core/src/editor.rs:1291— editor-core/src/editor.rs:1291-1300 | editor-core/src/editor.rs:1316-1325 | editor-core/src/editor.rs:1342-1351 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor-core/src/editor.rs:1291` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8–10 lines × 2) src/views/editor/visual_line.rs:602— src/views/editor/visual_line.rs:602-611 | src/views/editor/visual_line.rs:677-684 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/views/editor/visual_line.rs:602` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) src/style/transition.rs:183— src/style/transition.rs:183-191 | src/style/values.rs:414-422 | src/style/values.rs:537-545 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/style/transition.rs:183` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 4) src/views/scroll.rs:973— src/views/scroll.rs:973-981 | src/views/scroll.rs:984-992 | src/views/scroll.rs:995-1003 | src/views/scroll.rs:1005-1014 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/views/scroll.rs:973` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/views/scroll.rs:973` calls `Some` and `src/views/scroll.rs:1005` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6–8 lines × 2) src/view/id.rs:350— src/view/id.rs:350-355 | src/view/id.rs:431-438 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/view/id.rs:440` calls `insert`, `clone`, `state` and `src/view/id.rs:356` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 3) src/receiver_signal/resource/builder.rs:468— src/receiver_signal/resource/builder.rs:468-474 | src/receiver_signal/resource/builder.rs:525-531 | src/receiver_signal/resource/builder.rs:577-583 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6–7 lines × 2) src/paint/border_path_iter.rs:167— src/paint/border_path_iter.rs:167-173 | src/paint/border_path_iter.rs:199-204 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/paint/border_path_iter.rs:167` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (3–6 lines × 3) src/style/values.rs:451— src/style/values.rs:451-453 | src/style/values.rs:583-587 | src/style/values.rs:599-604 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/style/values.rs:451` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 4) editor-core/src/editor.rs:1265— editor-core/src/editor.rs:1265-1270 | editor-core/src/editor.rs:1376-1381 | editor-core/src/editor.rs:1412-1417 | editor-core/src/editor.rs:1432-1437 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `editor-core/src/editor.rs:1265` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (5 lines × 4) src/style/components.rs:265— src/style/components.rs:265-269 | src/style/components.rs:371-375 | src/style/components.rs:616-620 | src/style/components.rs:722-726 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/style/components.rs:265` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 3) src/views/editor/mod.rs:683— src/views/editor/mod.rs:683-687 | src/views/editor/mod.rs:701-705 | src/views/editor/mod.rs:715-719 — 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 (3–5 lines × 3) vello/src/lib.rs:245— vello/src/lib.rs:245-247 | vger/src/lib.rs:347-351 | vger/src/lib.rs:435-439 — before extracting anything, compare `vello/src/lib.rs` and `vger/src/lib.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `vello/src/lib.rs:245` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 3) src/views/label.rs:214— src/views/label.rs:214-219 | src/views/rich_text.rs:56-61 | src/views/text_input.rs:389-394 — before extracting anything, compare `src/views/label.rs` and `src/views/rich_text.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Orphaned file src/event/drag_state.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file editor-core/src/selection.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/views/editor/movement.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/text/layout.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file reactive/src/signal.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file reactive/src/context.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file editor-core/src/cursor.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file editor-core/src/buffer/mod.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file editor-core/src/buffer/rope_text.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/views/editor/text.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file editor-core/src/word.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/receiver_signal/common/executors.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/views/navigation_stack.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/receiver_signal/resource/builder.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file editor-core/src/command.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/paint/border_path_iter.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file skia/src/lib.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/style/custom.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file editor-core/src/line_ending.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/platform/context_menu.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file reactive/src/effect.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file reactive/src/derived.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file reactive/src/scope.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/views/editor/text_document.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/animate/easing.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
+ 55 more in this group — see findings.md.
D34 · Knowledge Freshness· Most significant orphaned file · ×3
Most significant orphaned file editor-core/src/editor.rs:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file src/event/listener.rs:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file editor-core/src/char_buffer.rs:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Duplicated predicate src/style/cx.rs:874— `anim.run_on_create && !matches!(anim.repeat_mode, RepeatMode::LoopForever)` appears character-identically in 2 files — src/style/cx.rs, src/views/dyn_container.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 src/style/cx.rs:820— `anim.run_on_remove && !matches!(anim.repeat_mode, RepeatMode::LoopForever)` appears character-identically in 2 files — src/style/cx.rs, src/views/dyn_container.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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 2 significant file(s) lose their only recent owner: src/text/layout_state.rs, src/style/recalc.rs. Pair on, review, or document these before any departure.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 9 project(s) overshoot their size bounds, lowering Project Cohesion to 7.8/10. The most over is `(repository root)` (63215 LoC, 571 module-visible types across 20 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.
Concentrated knowledge decay — 83 of 147 significant files have no living knowledge, while the repository is still being changed at a low rate (1 commit(s) in the last 90 days) — so this is one repo-wide knowledge-decay state, not 83 separate risks. Counted over 147 of the 176 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. The code moved on without the people who understood these files: document them or schedule a read-through before the next change lands in them.
ED3 · Event naming· Event not named in past tense · ×1
Event not named in past tense: UpdatePhase src/event/mod.rs:701— `UpdatePhase` is an imperative name inside a domain-event set whose siblings are past-tense facts — it reads as an intent, not something that happened. Name new events for the fact that occurred (e.g. `ItemAdded`). Do not rename this one if it is already stored or published: its type name is written with every event recorded under it, so a rename can break replay of the stored stream and every subscriber that reads it, and a clearer name does not pay for that. If it has never been written or sent, renaming it now is safe.
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.
Outdated: anyhow — `anyhow` is locked at 1.0.102 but 1.0.104 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in skia/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p anyhow` and commit the updated REDACTED.
Outdated: bitflags — `bitflags` is locked at 2.11.0 but 2.13.2 is the current stable release on crates.io, and it already satisfies the `"2.9"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p bitflags` and commit the updated REDACTED.
Outdated: console_log — `console_log` is locked at 1.0.0 but 1.1.0 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in examples/webgpu/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p console_log` and commit the updated REDACTED.
Outdated: crossbeam — `crossbeam` is locked at 0.8.4 but 0.8.5 is the current stable release on crates.io, and it already satisfies the `"0.8"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p crossbeam` and commit the updated REDACTED.
Outdated: futures — `futures` is locked at 0.3.32 but 0.3.34 is the current stable release on crates.io, and it already satisfies the `"0.3.31"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p futures` and commit the updated REDACTED.
Outdated: image — `image` is locked at 0.25.9 but 0.25.10 is the current stable release on crates.io, and it already satisfies the `"0.25"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p image` and commit the updated REDACTED.
Outdated: imbl — `imbl` is locked at 7.0.0 but 7.0.2 is the current stable release on crates.io, and it already satisfies the `"7.0"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p imbl` and commit the updated REDACTED.
Outdated: indexmap — `indexmap` is locked at 2.13.0 but 2.14.2 is the current stable release on crates.io, and it already satisfies the `"2"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p indexmap` and commit the updated REDACTED.
Outdated: kurbo — `kurbo` is locked at 0.13.0 but 0.13.1 is the current stable release on crates.io, and it already satisfies the `"0.13"` requirement declared in skia/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p kurbo` and commit the updated REDACTED.
Outdated: memchr — `memchr` is locked at 2.8.0 but 2.8.3 is the current stable release on crates.io, and it already satisfies the `"2.7.1"` requirement declared in editor-core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p memchr` 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 Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p objc2` and commit the updated REDACTED.
Outdated: open — `open` is locked at 5.3.3 but 5.4.5 is the current stable release on crates.io, and it already satisfies the `"5.3.2"` requirement declared in examples/async-resource/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p open` and commit the updated REDACTED.
Outdated: palette — `palette` is locked at 0.7.6 but 0.7.7 is the current stable release on crates.io, and it already satisfies the `"0.7.6"` requirement declared in examples/color_palette/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p palette` and commit the updated REDACTED.
Outdated: peniko — `peniko` is locked at 0.6.0 but 0.6.1 is the current stable release on crates.io, and it already satisfies the `"0.6.0"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p peniko` and commit the updated REDACTED.
Outdated: rustc-hash — `rustc-hash` is locked at 2.1.1 but 2.1.3 is the current stable release on crates.io, and it already satisfies the `"2.1"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rustc-hash` and commit the updated REDACTED.
Outdated: serde — `serde` is locked at 1.0.228 but 1.0.229 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde` and commit the updated REDACTED.
Outdated: serde_json — `serde_json` is locked at 1.0.149 but 1.0.154 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in 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: smallvec — `smallvec` is locked at 1.15.1 but 1.16.5 is the current stable release on crates.io, and it already satisfies the `"1.15"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p smallvec` and commit the updated REDACTED.
Outdated: swash — `swash` is locked at 0.2.6 but 0.2.10 is the current stable release on crates.io, and it already satisfies the `"0.2"` requirement declared in tiny_skia/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p swash` and commit the updated REDACTED.
Outdated: thiserror — `thiserror` is locked at 2.0.18 but 2.0.21 is the current stable release on crates.io, and it already satisfies the `"2"` requirement declared in examples/async-resource/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p thiserror` and commit the updated REDACTED.
Outdated: time — `time` is locked at 0.3.47 but 0.3.55 is the current stable release on crates.io, and it already satisfies the `"0.3.31"` requirement declared in examples/flight_booker/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p time` and commit the updated REDACTED.
Outdated: tokio — `tokio` is locked at 1.50.0 but 1.54.1 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tokio` and commit the updated REDACTED.
Outdated: tokio-stream — `tokio-stream` is locked at 0.1.18 but 0.1.19 is the current stable release on crates.io, and it already satisfies the `"0.1.15"` requirement declared in examples/tokio-timer/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tokio-stream` and commit the updated REDACTED.
Outdated: unicode-segmentation — `unicode-segmentation` is locked at 1.12.0 but 1.13.3 is the current stable release on crates.io, and it already satisfies the `"1.10"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p unicode-segmentation` and commit the updated REDACTED.
Outdated: wasm-bindgen — `wasm-bindgen` is locked at 0.2.114 but 0.2.130 is the current stable release on crates.io, and it already satisfies the `"0.2"` requirement declared in examples/webgpu/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p wasm-bindgen` and commit the updated REDACTED.
+ 2 more in this group — see findings.md.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
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.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1dbd1-6044-7f47-9a99-5d319a7b6f43 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 15 · Warnings: 641 · Recommendations: 91 · Info: 27 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 20: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.