Public report of iced-rs/iced, 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, 05:13 UTC · Survey ID cd_1bb973dd7e7846de85fbc53df8dd5d6b
iced-rs/iced
Measured 14 November 2026, 05:09 UTC, at code version b2fbd3c
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 scoreStrong
CriticalWeakAdequateStrongExemplary
Up 1 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: 71,157 lines of product code in 18 projects, tests not counted · Estimated rebuild effort: about 0.8 person-years · Weakest lens: Production Readiness, 66
Findings by how serious they are
35 critical735 serious15 minor
14 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, 05:09 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
43of 43 dimensions measured by tools.
774of 785 findings point to an exact file and line, so you can open each one in the code. The other 11 concern the repository as a whole, such as missing documentation.
43dimensions across 7 lenses, read from 71,157 lines of product code in 18 projects.
iced-rs/iced meets our standard for a preview release. It scores 71 out of 100 and is rated Strong, and 33 of its 35 critical findings are security problems in the build pipeline.
Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first step is adding tests for untested code, worth about 4 points. Recording design decisions comes next, worth about 3 points.
Twenty-nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three pipeline steps install packages that can change without warning, and one secret can leak from the build pipeline. Pinning each tool to an exact version, pinning what the pipeline installs and limiting the secret to its own step would close these risks. Calling the work with await instead of starting a new runner would take care of the second task runner started inside asynchronous code.
The product code is 71,157 lines, about €120,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.
Every lens already scores high enough to be rated Strong, so no single lens holds the score back.
Code composition: what the lines of code are
Product code 78%Tests 22%
New since the last survey: 392 findings
These 392 critical or serious findings weren't in the previous survey, on 26 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 (126 shared lines) widget/src/slider.rs
Code Duplication · Near-duplicate member pair (38 shared lines) src/application.rs
Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) program/src/lib.rs
Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) widget/src/column.rs
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) widget/src/column.rs
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) widget/src/pane_grid/title_bar.rs
Code Duplication · Edited copy of a member (105 corresponding lines) widget/src/column.rs
Code Duplication · Edited copy of a member (74 corresponding lines) widget/src/slider.rs
Code Duplication · Edited copy of a member (61 corresponding lines) core/src/layout/limits.rs
Code Duplication · Edited copy of a member (60 corresponding lines) wgpu/src/triangle.rs
Code Duplication · Edited copy of a member (51 corresponding lines) tiny_skia/src/geometry.rs
Code Duplication · Edited copy of a member (46 corresponding lines) futures/src/subscription.rs
Code Duplication · Edited copy of a member (30 corresponding lines) graphics/src/gradient.rs
Code Duplication · Edited copy of a member (36 corresponding lines) tiny_skia/src/vector.rs
Code Duplication · Edited copy of a member (39 corresponding lines) widget/src/text_editor.rs
Code Duplication · Edited copy of a member (36 corresponding lines) widget/src/pane_grid/node.rs
Code Duplication · Edited copy of a member (39 corresponding lines) widget/src/checkbox.rs
Code Duplication · Edited copy of a member (37 corresponding lines) winit/src/clipboard.rs
Code Duplication · Edited copy of a member (25 corresponding lines) core/src/widget/operation/focusable.rs
Code Duplication · Edited copy of a member (35 corresponding lines) widget/src/scrollable.rs
Code Duplication · Edited copy of a member (32 corresponding lines) widget/src/checkbox.rs
Code Duplication · Edited copy of a member (29 corresponding lines) wgpu/src/geometry.rs
Code Duplication · Edited copy of a member (22 corresponding lines) src/application.rs
Code Duplication · Edited copy of a member (26 corresponding lines) widget/src/image/viewer.rs
Code Duplication · Edited copies of one member (3 members, 32+ corresponding lines) core/src/widget/operation/scrollable.rs
Code Duplication · Edited copy of a member (22 corresponding lines) widget/src/pane_grid/content.rs
Code Duplication · Edited copy of a member (25 corresponding lines) core/src/length.rs
Code Duplication · Edited copies of one member (4 members, 27+ corresponding lines) widget/src/checkbox.rs
Code Duplication · Edited copy of a member (18 corresponding lines) tiny_skia/src/layer.rs
Code Duplication · Edited copy of a member (29 corresponding lines) tiny_skia/src/lib.rs
Code Duplication · Edited copy of a member (25 corresponding lines) widget/src/combo_box.rs
Code Duplication · Edited copy of a member (16 corresponding lines) core/src/gradient.rs
Code Duplication · Edited copy of a member (17 corresponding lines) widget/src/pane_grid.rs
Code Duplication · Edited copies of one member (6 members, 22+ corresponding lines) core/src/widget/operation/focusable.rs
Code Duplication · Edited copy of a member (27 corresponding lines) widget/src/slider.rs
Code Duplication · Edited copy of a member (17 corresponding lines) core/src/rectangle.rs
Code Duplication · Edited copy of a member (15 corresponding lines) widget/src/popover.rs
Code Duplication · Edited copy of a member (16 corresponding lines) futures/src/backend/native/tokio.rs
Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) tiny_skia/src/geometry.rs
Code Duplication · Edited copy of a member (9 corresponding lines) core/src/length.rs
Code Duplication · Edited copy of a member (23 corresponding lines) wgpu/src/triangle.rs
Code Duplication · Edited copy of a member (17 corresponding lines) tester/src/recorder.rs
Code Duplication · Edited copy of a member (14 corresponding lines) futures/src/backend/native/smol.rs
Code Duplication · Edited copy of a member (20 corresponding lines) core/src/widget/operation/text.rs
Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) widget/src/column.rs
Code Duplication · Edited copy of a member (19 corresponding lines) core/src/text.rs
Code Duplication · Edited copies of one member (7 members, 13+ corresponding lines) widget/src/button.rs
Code Duplication · Edited copies of one member (4 members, 15+ corresponding lines) runtime/src/clipboard.rs
Code Duplication · Edited copy of a member (14 corresponding lines) wgpu/src/triangle.rs
Code Duplication · Edited copy of a member (13 corresponding lines) runtime/src/task.rs
Code Duplication · Edited copy of a member (19 corresponding lines) widget/src/pane_grid/node.rs
Code Duplication · Edited copy of a member (7 corresponding lines) wgpu/src/quad/gradient.rs
Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) widget/src/column.rs
Code Duplication · Edited copy of a member (14 corresponding lines) highlighter/src/lib.rs
Code Duplication · Edited copy of a member (7 corresponding lines) widget/src/button.rs
Code Duplication · Edited copy of a member (10 corresponding lines) widget/src/stack.rs
Code Duplication · Edited copy of a member (6 corresponding lines) widget/src/text_editor.rs
Code Duplication · Edited copies of one member (3 members, 19+ corresponding lines) tiny_skia/src/layer.rs
Code Duplication · Edited copy of a member (9 corresponding lines) core/src/widget.rs
Code Duplication · Edited copy of a member (14 corresponding lines) selector/src/find.rs
Code Duplication · Edited copy of a member (13 corresponding lines) tiny_skia/src/geometry.rs
Code Duplication · Edited copy of a member (15 corresponding lines) widget/src/sticky.rs
Code Duplication · Edited copy of a member (14 corresponding lines) widget/src/button.rs
Code Duplication · Edited copy of a member (13 corresponding lines) wgpu/src/quad/gradient.rs
Code Duplication · Edited copy of a member (7 corresponding lines) widget/src/checkbox.rs
Code Duplication · Edited copy of a member (11 corresponding lines) tiny_skia/src/layer.rs
Code Duplication · Edited copy of a member (11 corresponding lines) tiny_skia/src/layer.rs
Code Duplication · Edited copy of a member (7 corresponding lines) src/application.rs
Code Duplication · Edited copy of a member (4 corresponding lines) tiny_skia/src/lib.rs
Code Duplication · Edited copy of a member (4 corresponding lines) tiny_skia/src/lib.rs
Code Duplication · Edited copy of a member (4 corresponding lines) tiny_skia/src/lib.rs
Code Duplication · Edited copy of a member (9 corresponding lines) widget/src/button.rs
Code Duplication · Edited copy of a member (4 corresponding lines) tiny_skia/src/lib.rs
Code Duplication · Edited copy of a member (4 corresponding lines) tiny_skia/src/lib.rs
Code Duplication · Edited copy of a member (4 corresponding lines) widget/src/combo_box.rs
Code Duplication · Edited copy of a member (4 corresponding lines) widget/src/pane_grid/content.rs
Code Duplication · Edited copy of a member (7 corresponding lines) src/application.rs
Code Duplication · Edited copy of a member (7 corresponding lines) src/application.rs
Code Duplication · Edited copy of a member (7 corresponding lines) wgpu/src/quad.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: 51 findings
These 51 critical or serious findings were in the previous survey, on 26 October 2026, and are gone from this one.
Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
Rebuild cost: about €120,000 · Estimate
Cost to rebuild
€41,000 to €200,000, for 676 to 2,143 hours of work, about 0.8 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
×1.0 at a score of 71. 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: 71,157 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 267 Low coverage finding(s) in Code Coverage — start with main.rs (54), lib.rs (14), text.rs (7).
Raises the score by about 4 points · High effort · Code Coverage
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.
Files that change often carry extra risk · Combined risk
11 files are changed often and are hard to read, which makes them the likeliest places for a mistake. They also have under half their code tested, or were written almost entirely by one person, so a mistake there is less likely to be caught, or only one person knows the code well enough to avoid it. A change to these files therefore carries more risk than the overall score suggests.
Based on: Churn × Complexity Hotspots (16 files) · Code Coverage (152 files under half tested) · The files: lib.rs, editor.rs and text_editor.rs
What to do: Add tests to these files and have a second person review every change to them, starting with lib.rs, editor.rs and text_editor.rs.
If you do one thing first · First action
Resolve the 267 Low coverage finding(s) in Code Coverage. Of all the actions in this report, it raises the score most for the work it takes: about 4 points for high effort, because it clears the 267 Code Coverage findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.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 49,243 lines over the last 90 days, which is about 199,708 lines a year. At that pace, the extra work comes to an estimated 13.5 to 81.1 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.
281 modules, with 1912 dependencies between them. 9 loops run through 48 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 241 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.
1 pair of types, where a type in iced_core.length uses a type in iced_core.pixels.
The types involved
iced_core.length.Length → iced_core.pixels.Pixels
Direction
iced_core.length uses iced_core.pixels, so a change to iced_core.pixels can break iced_core.length, while a change to iced_core.length can't break iced_core.pixels.
Position
Below the diagonal: iced_core.length uses a module listed above it, which is the healthy direction.
7→9 iced_core.vector uses iced_core.transformationpart of a loop✕
Connections
1 pair of types, where a type in iced_core.vector uses a type in iced_core.transformation.
iced_core.vector uses iced_core.transformation, so a change to iced_core.transformation can break iced_core.vector, while a change to iced_core.vector can't break iced_core.transformation.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→13 iced_core.vector uses iced_core.sizepart of a loop✕
Connections
1 pair of types, where a type in iced_core.vector uses a type in iced_core.size.
The types involved
iced_core.vector.Vector → iced_core.size.Size
Direction
iced_core.vector uses iced_core.size, so a change to iced_core.size can break iced_core.vector, while a change to iced_core.vector can't break iced_core.size.
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.
iced_graphics.compositor uses iced_core.backend, so a change to iced_core.backend can break iced_graphics.compositor, while a change to iced_graphics.compositor can't break iced_core.backend.
Position
Below the diagonal: iced_graphics.compositor uses a module listed above it, which is the healthy direction.
iced_graphics.compositor uses iced_core.color, so a change to iced_core.color can break iced_graphics.compositor, while a change to iced_graphics.compositor can't break iced_core.color.
Position
Below the diagonal: iced_graphics.compositor uses a module listed above it, which is the healthy direction.
iced_core.transformation uses iced_core.vector, so a change to iced_core.vector can break iced_core.transformation, while a change to iced_core.transformation can't break iced_core.vector.
Position
Below the diagonal: iced_core.transformation uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in iced_core.point uses a type in iced_core.vector.
The types involved
iced_core.point.Point → iced_core.vector.Vector
Direction
iced_core.point uses iced_core.vector, so a change to iced_core.vector can break iced_core.point, while a change to iced_core.point can't break iced_core.vector.
Position
Below the diagonal: iced_core.point uses a module listed above it, which is the healthy direction.
iced_core.point uses iced_core.transformation, so a change to iced_core.transformation can break iced_core.point, while a change to iced_core.point can't break iced_core.transformation.
Position
Below the diagonal: iced_core.point uses a module listed above it, which is the healthy direction.
iced_core.rectangle uses iced_core.vector, so a change to iced_core.vector can break iced_core.rectangle, while a change to iced_core.rectangle can't break iced_core.vector.
Position
Below the diagonal: iced_core.rectangle uses a module listed above it, which is the healthy direction.
iced_core.rectangle uses iced_core.transformation, so a change to iced_core.transformation can break iced_core.rectangle, while a change to iced_core.rectangle can't break iced_core.transformation.
Position
Below the diagonal: iced_core.rectangle uses a module listed above it, which is the healthy direction.
iced_core.rectangle uses iced_core.point, so a change to iced_core.point can break iced_core.rectangle, while a change to iced_core.rectangle can't break iced_core.point.
Position
Below the diagonal: iced_core.rectangle uses a module listed above it, which is the healthy direction.
11→13 iced_core.rectangle uses iced_core.sizepart of a loop✕
Connections
1 pair of types, where a type in iced_core.rectangle uses a type in iced_core.size.
iced_core.rectangle uses iced_core.size, so a change to iced_core.size can break iced_core.rectangle, while a change to iced_core.rectangle can't break iced_core.size.
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.
iced_core.mouse.cursor uses iced_core.vector, so a change to iced_core.vector can break iced_core.mouse.cursor, while a change to iced_core.mouse.cursor can't break iced_core.vector.
Position
Below the diagonal: iced_core.mouse.cursor uses a module listed above it, which is the healthy direction.
iced_core.mouse.cursor uses iced_core.transformation, so a change to iced_core.transformation can break iced_core.mouse.cursor, while a change to iced_core.mouse.cursor can't break iced_core.transformation.
Position
Below the diagonal: iced_core.mouse.cursor uses a module listed above it, which is the healthy direction.
iced_core.mouse.cursor uses iced_core.point, so a change to iced_core.point can break iced_core.mouse.cursor, while a change to iced_core.mouse.cursor can't break iced_core.point.
Position
Below the diagonal: iced_core.mouse.cursor uses a module listed above it, which is the healthy direction.
iced_core.mouse.cursor uses iced_core.rectangle, so a change to iced_core.rectangle can break iced_core.mouse.cursor, while a change to iced_core.mouse.cursor can't break iced_core.rectangle.
Position
Below the diagonal: iced_core.mouse.cursor uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in iced_core.size uses a type in iced_core.vector.
The types involved
iced_core.size.Size → iced_core.vector.Vector
Direction
iced_core.size uses iced_core.vector, so a change to iced_core.vector can break iced_core.size, while a change to iced_core.size can't break iced_core.vector.
Position
Below the diagonal: iced_core.size uses a module listed above it, which is the healthy direction.
iced_core.size uses iced_core.transformation, so a change to iced_core.transformation can break iced_core.size, while a change to iced_core.size can't break iced_core.transformation.
Position
Below the diagonal: iced_core.size uses a module listed above it, which is the healthy direction.
iced_core.size uses iced_core.rectangle, so a change to iced_core.rectangle can break iced_core.size, while a change to iced_core.size can't break iced_core.rectangle.
Position
Below the diagonal: iced_core.size uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in iced_core.clipboard uses a type in iced_core.size.
The types involved
iced_core.clipboard.Image → iced_core.size.Size
Direction
iced_core.clipboard uses iced_core.size, so a change to iced_core.size can break iced_core.clipboard, while a change to iced_core.clipboard can't break iced_core.size.
Position
Below the diagonal: iced_core.clipboard uses a module listed above it, which is the healthy direction.
iced_core.layout.limits uses iced_core.length, so a change to iced_core.length can break iced_core.layout.limits, while a change to iced_core.layout.limits can't break iced_core.length.
Position
Below the diagonal: iced_core.layout.limits uses a module listed above it, which is the healthy direction.
iced_core.layout.limits uses iced_core.size, so a change to iced_core.size can break iced_core.layout.limits, while a change to iced_core.layout.limits can't break iced_core.size.
Position
Below the diagonal: iced_core.layout.limits uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in iced_core.image uses a type in iced_core.backend.
The types involved
iced_core.image.Error → iced_core.backend.Error
Direction
iced_core.image uses iced_core.backend, so a change to iced_core.backend can break iced_core.image, while a change to iced_core.image can't break iced_core.backend.
Position
Below the diagonal: iced_core.image uses a module listed above it, which is the healthy direction.
iced_core.image uses iced_core.rectangle, so a change to iced_core.rectangle can break iced_core.image, while a change to iced_core.image can't break iced_core.rectangle.
Position
Below the diagonal: iced_core.image uses a module listed above it, which is the healthy direction.
iced_core.image uses iced_core.size, so a change to iced_core.size can break iced_core.image, while a change to iced_core.image can't break iced_core.size.
Position
Below the diagonal: iced_core.image uses a module listed above it, which is the healthy direction.
iced_core.image uses iced_core.clipboard, so a change to iced_core.clipboard can break iced_core.image, while a change to iced_core.image can't break iced_core.clipboard.
Position
Below the diagonal: iced_core.image uses a module listed above it, which is the healthy direction.
iced_core.shell uses iced_core.clipboard, so a change to iced_core.clipboard can break iced_core.shell, while a change to iced_core.shell can't break iced_core.clipboard.
Position
Below the diagonal: iced_core.shell uses a module listed above it, which is the healthy direction.
iced_core.layout.flex uses iced_core.length, so a change to iced_core.length can break iced_core.layout.flex, while a change to iced_core.layout.flex can't break iced_core.length.
Position
Below the diagonal: iced_core.layout.flex uses a module listed above it, which is the healthy direction.
iced_core.layout.flex uses iced_core.size, so a change to iced_core.size can break iced_core.layout.flex, while a change to iced_core.layout.flex can't break iced_core.size.
Position
Below the diagonal: iced_core.layout.flex uses a module listed above it, which is the healthy direction.
iced_core.layout.flex uses iced_core.layout.limits, so a change to iced_core.layout.limits can break iced_core.layout.flex, while a change to iced_core.layout.flex can't break iced_core.layout.limits.
Position
Below the diagonal: iced_core.layout.flex uses a module listed above it, which is the healthy direction.
iced_core.layout.flex uses iced_core.image, so a change to iced_core.image can break iced_core.layout.flex, while a change to iced_core.layout.flex can't break iced_core.image.
Position
Below the diagonal: iced_core.layout.flex uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in iced_core.text uses a type in iced_core.color.
The types involved
iced_core.text.Renderer → iced_core.color.Color
iced_core.text.Span → iced_core.color.Color
Direction
iced_core.text uses iced_core.color, so a change to iced_core.color can break iced_core.text, while a change to iced_core.text can't break iced_core.color.
Position
Below the diagonal: iced_core.text uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in iced_core.text uses a type in iced_core.font.
The types involved
iced_core.text.Renderer → iced_core.font.Font
iced_core.text.Span → iced_core.font.Font
iced_core.text.Text → iced_core.font.Font
Direction
iced_core.text uses iced_core.font, so a change to iced_core.font can break iced_core.text, while a change to iced_core.text can't break iced_core.font.
Position
Below the diagonal: iced_core.text uses a module listed above it, which is the healthy direction.
iced_core.text uses iced_core.pixels, so a change to iced_core.pixels can break iced_core.text, while a change to iced_core.text can't break iced_core.pixels.
Position
Below the diagonal: iced_core.text uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in iced_core.text uses a type in iced_core.point.
The types involved
iced_core.text.Renderer → iced_core.point.Point
Direction
iced_core.text uses iced_core.point, so a change to iced_core.point can break iced_core.text, while a change to iced_core.text can't break iced_core.point.
Position
Below the diagonal: iced_core.text uses a module listed above it, which is the healthy direction.
iced_core.text uses iced_core.rectangle, so a change to iced_core.rectangle can break iced_core.text, while a change to iced_core.text can't break iced_core.rectangle.
Position
Below the diagonal: iced_core.text uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in iced_core.text uses a type in iced_core.size.
The types involved
iced_core.text.Text → iced_core.size.Size
Direction
iced_core.text uses iced_core.size, so a change to iced_core.size can break iced_core.text, while a change to iced_core.text can't break iced_core.size.
Position
Below the diagonal: iced_core.text uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in iced_core.text uses a type in iced_core.clipboard.
The types involved
iced_core.text.Text → iced_core.clipboard.Content
Direction
iced_core.text uses iced_core.clipboard, so a change to iced_core.clipboard can break iced_core.text, while a change to iced_core.text can't break iced_core.clipboard.
Position
Below the diagonal: iced_core.text uses a module listed above it, which is the healthy direction.
iced_core.text uses iced_core.image, so a change to iced_core.image can break iced_core.text, while a change to iced_core.text can't break iced_core.image.
Position
Below the diagonal: iced_core.text uses a module listed above it, which is the healthy direction.
19→20 iced_core.text uses iced_core.text.editorpart of a loop✕
Connections
1 pair of types, where a type in iced_core.text uses a type in iced_core.text.editor.
iced_core.text uses iced_core.text.editor, so a change to iced_core.text.editor can break iced_core.text, while a change to iced_core.text can't break iced_core.text.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.
iced_core.text.editor uses iced_core.color, so a change to iced_core.color can break iced_core.text.editor, while a change to iced_core.text.editor can't break iced_core.color.
Position
Below the diagonal: iced_core.text.editor uses a module listed above it, which is the healthy direction.
iced_core.text.editor uses iced_core.font, so a change to iced_core.font can break iced_core.text.editor, while a change to iced_core.text.editor can't break iced_core.font.
Position
Below the diagonal: iced_core.text.editor uses a module listed above it, which is the healthy direction.
iced_core.text.editor uses iced_core.pixels, so a change to iced_core.pixels can break iced_core.text.editor, while a change to iced_core.text.editor can't break iced_core.pixels.
Position
Below the diagonal: iced_core.text.editor uses a module listed above it, which is the healthy direction.
iced_core.text.editor uses iced_core.point, so a change to iced_core.point can break iced_core.text.editor, while a change to iced_core.text.editor can't break iced_core.point.
Position
Below the diagonal: iced_core.text.editor uses a module listed above it, which is the healthy direction.
iced_core.text.editor uses iced_core.rectangle, so a change to iced_core.rectangle can break iced_core.text.editor, while a change to iced_core.text.editor can't break iced_core.rectangle.
Position
Below the diagonal: iced_core.text.editor uses a module listed above it, which is the healthy direction.
iced_core.text.editor uses iced_core.mouse.cursor, so a change to iced_core.mouse.cursor can break iced_core.text.editor, while a change to iced_core.text.editor can't break iced_core.mouse.cursor.
Position
Below the diagonal: iced_core.text.editor uses a module listed above it, which is the healthy direction.
iced_core.text.editor uses iced_core.size, so a change to iced_core.size can break iced_core.text.editor, while a change to iced_core.text.editor can't break iced_core.size.
Position
Below the diagonal: iced_core.text.editor uses a module listed above it, which is the healthy direction.
iced_core.text.editor uses iced_core.clipboard, so a change to iced_core.clipboard can break iced_core.text.editor, while a change to iced_core.text.editor can't break iced_core.clipboard.
Position
Below the diagonal: iced_core.text.editor uses a module listed above it, which is the healthy direction.
iced_core.text.editor uses iced_core.image, so a change to iced_core.image can break iced_core.text.editor, while a change to iced_core.text.editor can't break iced_core.image.
Position
Below the diagonal: iced_core.text.editor uses a module listed above it, which is the healthy direction.
iced_core.text.editor uses iced_core.text, so a change to iced_core.text can break iced_core.text.editor, while a change to iced_core.text.editor can't break iced_core.text.
Position
Below the diagonal: iced_core.text.editor uses a module listed above it, which is the healthy direction.
iced_wgpu.geometry uses iced_core.backend, so a change to iced_core.backend can break iced_wgpu.geometry, while a change to iced_wgpu.geometry can't break iced_core.backend.
Position
Below the diagonal: iced_wgpu.geometry uses a module listed above it, which is the healthy direction.
iced_wgpu.geometry uses iced_core.font, so a change to iced_core.font can break iced_wgpu.geometry, while a change to iced_wgpu.geometry can't break iced_core.font.
Position
Below the diagonal: iced_wgpu.geometry uses a module listed above it, which is the healthy direction.
iced_wgpu.geometry uses iced_core.vector, so a change to iced_core.vector can break iced_wgpu.geometry, while a change to iced_wgpu.geometry can't break iced_core.vector.
Position
Below the diagonal: iced_wgpu.geometry uses a module listed above it, which is the healthy direction.
iced_wgpu.geometry uses iced_core.point, so a change to iced_core.point can break iced_wgpu.geometry, while a change to iced_wgpu.geometry can't break iced_core.point.
Position
Below the diagonal: iced_wgpu.geometry uses a module listed above it, which is the healthy direction.
iced_wgpu.geometry uses iced_core.rectangle, so a change to iced_core.rectangle can break iced_wgpu.geometry, while a change to iced_wgpu.geometry can't break iced_core.rectangle.
Position
Below the diagonal: iced_wgpu.geometry uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in iced_wgpu.geometry uses a type in iced_core.size.
The types involved
iced_wgpu.geometry.Frame → iced_core.size.Size
Direction
iced_wgpu.geometry uses iced_core.size, so a change to iced_core.size can break iced_wgpu.geometry, while a change to iced_wgpu.geometry can't break iced_core.size.
Position
Below the diagonal: iced_wgpu.geometry uses a module listed above it, which is the healthy direction.
iced_wgpu.geometry uses iced_core.clipboard, so a change to iced_core.clipboard can break iced_wgpu.geometry, while a change to iced_wgpu.geometry can't break iced_core.clipboard.
Position
Below the diagonal: iced_wgpu.geometry uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in iced_wgpu.geometry uses a type in iced_core.text.
The types involved
iced_wgpu.geometry.Frame → iced_core.text.Text
Direction
iced_wgpu.geometry uses iced_core.text, so a change to iced_core.text can break iced_wgpu.geometry, while a change to iced_wgpu.geometry can't break iced_core.text.
Position
Below the diagonal: iced_wgpu.geometry uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in iced_core.theme uses a type in iced_core.color.
The types involved
iced_core.theme.Style → iced_core.color.Color
iced_core.theme.Theme → iced_core.color.Color
Direction
iced_core.theme uses iced_core.color, so a change to iced_core.color can break iced_core.theme, while a change to iced_core.theme can't break iced_core.color.
Position
Below the diagonal: iced_core.theme uses a module listed above it, which is the healthy direction.
iced_core.theme uses iced_core.font, so a change to iced_core.font can break iced_core.theme, while a change to iced_core.theme can't break iced_core.font.
Position
Below the diagonal: iced_core.theme uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in iced_core.theme uses a type in iced_core.image.
The types involved
iced_core.theme.Theme → iced_core.image.Id
Direction
iced_core.theme uses iced_core.image, so a change to iced_core.image can break iced_core.theme, while a change to iced_core.theme can't break iced_core.image.
Position
Below the diagonal: iced_core.theme uses a module listed above it, which is the healthy direction.
iced_core.theme uses iced_core.text.editor, so a change to iced_core.text.editor can break iced_core.theme, while a change to iced_core.theme can't break iced_core.text.editor.
Position
Below the diagonal: iced_core.theme uses a module listed above it, which is the healthy direction.
iced_core.widget.tree uses iced_core.vector, so a change to iced_core.vector can break iced_core.widget.tree, while a change to iced_core.widget.tree can't break iced_core.vector.
Position
Below the diagonal: iced_core.widget.tree uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in iced_core.widget.tree uses a type in iced_core.size.
The types involved
iced_core.widget.tree.Tree → iced_core.size.Size
Direction
iced_core.widget.tree uses iced_core.size, so a change to iced_core.size can break iced_core.widget.tree, while a change to iced_core.widget.tree can't break iced_core.size.
Position
Below the diagonal: iced_core.widget.tree uses a module listed above it, which is the healthy direction.
iced_core.widget.tree uses iced_core.text.editor, so a change to iced_core.text.editor can break iced_core.widget.tree, while a change to iced_core.widget.tree can't break iced_core.text.editor.
Position
Below the diagonal: iced_core.widget.tree uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in iced_core.layout uses a type in iced_core.point.
The types involved
iced_core.layout.Layout → iced_core.point.Point
Direction
iced_core.layout uses iced_core.point, so a change to iced_core.point can break iced_core.layout, while a change to iced_core.layout can't break iced_core.point.
Position
Below the diagonal: iced_core.layout uses a module listed above it, which is the healthy direction.
iced_core.layout uses iced_core.rectangle, so a change to iced_core.rectangle can break iced_core.layout, while a change to iced_core.layout can't break iced_core.rectangle.
Position
Below the diagonal: iced_core.layout uses a module listed above it, which is the healthy direction.
iced_core.layout uses iced_core.size, so a change to iced_core.size can break iced_core.layout, while a change to iced_core.layout can't break iced_core.size.
Position
Below the diagonal: iced_core.layout uses a module listed above it, which is the healthy direction.
iced_core.layout uses iced_core.layout.limits, so a change to iced_core.layout.limits can break iced_core.layout, while a change to iced_core.layout can't break iced_core.layout.limits.
Position
Below the diagonal: iced_core.layout uses a module listed above it, which is the healthy direction.
iced_core.layout uses iced_core.widget.tree, so a change to iced_core.widget.tree can break iced_core.layout, while a change to iced_core.layout can't break iced_core.widget.tree.
Position
Below the diagonal: iced_core.layout uses a module listed above it, which is the healthy direction.
iced_core.overlay.element uses iced_core.font, so a change to iced_core.font can break iced_core.overlay.element, while a change to iced_core.overlay.element can't break iced_core.font.
Position
Below the diagonal: iced_core.overlay.element uses a module listed above it, which is the healthy direction.
iced_core.overlay.element uses iced_core.mouse.cursor, so a change to iced_core.mouse.cursor can break iced_core.overlay.element, while a change to iced_core.overlay.element can't break iced_core.mouse.cursor.
Position
Below the diagonal: iced_core.overlay.element uses a module listed above it, which is the healthy direction.
iced_core.overlay.element uses iced_core.clipboard, so a change to iced_core.clipboard can break iced_core.overlay.element, while a change to iced_core.overlay.element can't break iced_core.clipboard.
Position
Below the diagonal: iced_core.overlay.element uses a module listed above it, which is the healthy direction.
iced_core.overlay.element uses iced_core.image, so a change to iced_core.image can break iced_core.overlay.element, while a change to iced_core.overlay.element can't break iced_core.image.
Position
Below the diagonal: iced_core.overlay.element uses a module listed above it, which is the healthy direction.
iced_core.overlay.element uses iced_core.shell, so a change to iced_core.shell can break iced_core.overlay.element, while a change to iced_core.overlay.element can't break iced_core.shell.
Position
Below the diagonal: iced_core.overlay.element uses a module listed above it, which is the healthy direction.
iced_core.overlay.element uses iced_core.theme, so a change to iced_core.theme can break iced_core.overlay.element, while a change to iced_core.overlay.element can't break iced_core.theme.
Position
Below the diagonal: iced_core.overlay.element uses a module listed above it, which is the healthy direction.
iced_widget.combo_box uses iced_beacon.client, so a change to iced_beacon.client can break iced_widget.combo_box, while a change to iced_widget.combo_box can't break iced_beacon.client.
Position
Below the diagonal: iced_widget.combo_box uses a module listed above it, which is the healthy direction.
iced_widget.combo_box uses iced_core.font, so a change to iced_core.font can break iced_widget.combo_box, while a change to iced_widget.combo_box can't break iced_core.font.
Position
Below the diagonal: iced_widget.combo_box uses a module listed above it, which is the healthy direction.
iced_widget.combo_box uses iced_core.pixels, so a change to iced_core.pixels can break iced_widget.combo_box, while a change to iced_widget.combo_box can't break iced_core.pixels.
Position
Below the diagonal: iced_widget.combo_box uses a module listed above it, which is the healthy direction.
iced_widget.combo_box uses iced_core.length, so a change to iced_core.length can break iced_widget.combo_box, while a change to iced_widget.combo_box can't break iced_core.length.
Position
Below the diagonal: iced_widget.combo_box uses a module listed above it, which is the healthy direction.
iced_widget.combo_box uses iced_core.vector, so a change to iced_core.vector can break iced_widget.combo_box, while a change to iced_widget.combo_box can't break iced_core.vector.
Position
Below the diagonal: iced_widget.combo_box uses a module listed above it, which is the healthy direction.
iced_widget.combo_box uses iced_graphics.compositor, so a change to iced_graphics.compositor can break iced_widget.combo_box, while a change to iced_widget.combo_box can't break iced_graphics.compositor.
Position
Below the diagonal: iced_widget.combo_box uses a module listed above it, which is the healthy direction.
iced_widget.combo_box uses iced_core.rectangle, so a change to iced_core.rectangle can break iced_widget.combo_box, while a change to iced_widget.combo_box can't break iced_core.rectangle.
Position
Below the diagonal: iced_widget.combo_box uses a module listed above it, which is the healthy direction.
iced_widget.combo_box uses iced_core.mouse.cursor, so a change to iced_core.mouse.cursor can break iced_widget.combo_box, while a change to iced_widget.combo_box can't break iced_core.mouse.cursor.
Position
Below the diagonal: iced_widget.combo_box uses a module listed above it, which is the healthy direction.
iced_widget.combo_box uses iced_core.size, so a change to iced_core.size can break iced_widget.combo_box, while a change to iced_widget.combo_box can't break iced_core.size.
Position
Below the diagonal: iced_widget.combo_box uses a module listed above it, which is the healthy direction.
iced_widget.combo_box uses iced_core.layout.limits, so a change to iced_core.layout.limits can break iced_widget.combo_box, while a change to iced_widget.combo_box can't break iced_core.layout.limits.
Position
Below the diagonal: iced_widget.combo_box uses a module listed above it, which is the healthy direction.
iced_widget.combo_box uses iced_core.image, so a change to iced_core.image can break iced_widget.combo_box, while a change to iced_widget.combo_box can't break iced_core.image.
Position
Below the diagonal: iced_widget.combo_box uses a module listed above it, which is the healthy direction.
iced_widget.combo_box uses iced_core.shell, so a change to iced_core.shell can break iced_widget.combo_box, while a change to iced_widget.combo_box can't break iced_core.shell.
Position
Below the diagonal: iced_widget.combo_box uses a module listed above it, which is the healthy direction.
iced_widget.combo_box uses iced_core.layout.flex, so a change to iced_core.layout.flex can break iced_widget.combo_box, while a change to iced_widget.combo_box can't break iced_core.layout.flex.
Position
Below the diagonal: iced_widget.combo_box uses a module listed above it, which is the healthy direction.
iced_widget.combo_box uses iced_core.text, so a change to iced_core.text can break iced_widget.combo_box, while a change to iced_widget.combo_box can't break iced_core.text.
Position
Below the diagonal: iced_widget.combo_box uses a module listed above it, which is the healthy direction.
iced_widget.combo_box uses iced_core.theme, so a change to iced_core.theme can break iced_widget.combo_box, while a change to iced_widget.combo_box can't break iced_core.theme.
Position
Below the diagonal: iced_widget.combo_box uses a module listed above it, which is the healthy direction.
iced_widget.combo_box uses iced_core.widget.tree, so a change to iced_core.widget.tree can break iced_widget.combo_box, while a change to iced_widget.combo_box can't break iced_core.widget.tree.
Position
Below the diagonal: iced_widget.combo_box uses a module listed above it, which is the healthy direction.
iced_widget.combo_box uses iced_core.layout, so a change to iced_core.layout can break iced_widget.combo_box, while a change to iced_widget.combo_box can't break iced_core.layout.
Position
Below the diagonal: iced_widget.combo_box uses a module listed above it, which is the healthy direction.
iced_widget.combo_box uses iced_core.overlay.element, so a change to iced_core.overlay.element can break iced_widget.combo_box, while a change to iced_widget.combo_box can't break iced_core.overlay.element.
Position
Below the diagonal: iced_widget.combo_box uses a module listed above it, which is the healthy direction.
26→29 iced_widget.combo_box uses iced_widget.scrollablepart of a loop✕
Connections
1 pair of types, where a type in iced_widget.combo_box uses a type in iced_widget.scrollable.
iced_widget.combo_box uses iced_widget.scrollable, so a change to iced_widget.scrollable can break iced_widget.combo_box, while a change to iced_widget.combo_box can't break iced_widget.scrollable.
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→30 iced_widget.combo_box uses iced_widget.buttonpart of a loop✕
Connections
5 pairs of types, where a type in iced_widget.combo_box uses a type in iced_widget.button.
iced_widget.combo_box uses iced_widget.button, so a change to iced_widget.button can break iced_widget.combo_box, while a change to iced_widget.combo_box can't break iced_widget.button.
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→31 iced_widget.combo_box uses iced_widgetpart of a loop✕
Connections
1 pair of types, where a type in iced_widget.combo_box uses a type in iced_widget.
iced_widget.combo_box uses iced_widget, so a change to iced_widget can break iced_widget.combo_box, while a change to iced_widget.combo_box can't break iced_widget.
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.
iced_widget.component uses iced_beacon.client, so a change to iced_beacon.client can break iced_widget.component, while a change to iced_widget.component can't break iced_beacon.client.
Position
Below the diagonal: iced_widget.component uses a module listed above it, which is the healthy direction.
iced_widget.component uses iced_core.vector, so a change to iced_core.vector can break iced_widget.component, while a change to iced_widget.component can't break iced_core.vector.
Position
Below the diagonal: iced_widget.component uses a module listed above it, which is the healthy direction.
iced_widget.component uses iced_core.rectangle, so a change to iced_core.rectangle can break iced_widget.component, while a change to iced_widget.component can't break iced_core.rectangle.
Position
Below the diagonal: iced_widget.component uses a module listed above it, which is the healthy direction.
iced_widget.component uses iced_core.mouse.cursor, so a change to iced_core.mouse.cursor can break iced_widget.component, while a change to iced_widget.component can't break iced_core.mouse.cursor.
Position
Below the diagonal: iced_widget.component uses a module listed above it, which is the healthy direction.
iced_widget.component uses iced_core.size, so a change to iced_core.size can break iced_widget.component, while a change to iced_widget.component can't break iced_core.size.
Position
Below the diagonal: iced_widget.component uses a module listed above it, which is the healthy direction.
iced_widget.component uses iced_core.layout.limits, so a change to iced_core.layout.limits can break iced_widget.component, while a change to iced_widget.component can't break iced_core.layout.limits.
Position
Below the diagonal: iced_widget.component uses a module listed above it, which is the healthy direction.
iced_widget.component uses iced_core.image, so a change to iced_core.image can break iced_widget.component, while a change to iced_widget.component can't break iced_core.image.
Position
Below the diagonal: iced_widget.component uses a module listed above it, which is the healthy direction.
iced_widget.component uses iced_core.shell, so a change to iced_core.shell can break iced_widget.component, while a change to iced_widget.component can't break iced_core.shell.
Position
Below the diagonal: iced_widget.component uses a module listed above it, which is the healthy direction.
iced_widget.component uses iced_core.layout.flex, so a change to iced_core.layout.flex can break iced_widget.component, while a change to iced_widget.component can't break iced_core.layout.flex.
Position
Below the diagonal: iced_widget.component uses a module listed above it, which is the healthy direction.
iced_widget.component uses iced_core.theme, so a change to iced_core.theme can break iced_widget.component, while a change to iced_widget.component can't break iced_core.theme.
Position
Below the diagonal: iced_widget.component uses a module listed above it, which is the healthy direction.
iced_widget.component uses iced_core.widget.tree, so a change to iced_core.widget.tree can break iced_widget.component, while a change to iced_widget.component can't break iced_core.widget.tree.
Position
Below the diagonal: iced_widget.component uses a module listed above it, which is the healthy direction.
iced_widget.component uses iced_core.layout, so a change to iced_core.layout can break iced_widget.component, while a change to iced_widget.component can't break iced_core.layout.
Position
Below the diagonal: iced_widget.component uses a module listed above it, which is the healthy direction.
iced_widget.component uses iced_core.overlay.element, so a change to iced_core.overlay.element can break iced_widget.component, while a change to iced_widget.component can't break iced_core.overlay.element.
Position
Below the diagonal: iced_widget.component uses a module listed above it, which is the healthy direction.
iced_widget.component uses iced_widget.combo_box, so a change to iced_widget.combo_box can break iced_widget.component, while a change to iced_widget.component can't break iced_widget.combo_box.
Position
Below the diagonal: iced_widget.component uses a module listed above it, which is the healthy direction.
27→29 iced_widget.component uses iced_widget.scrollablepart of a loop✕
Connections
3 pairs of types, where a type in iced_widget.component uses a type in iced_widget.scrollable.
iced_widget.component uses iced_widget.scrollable, so a change to iced_widget.scrollable can break iced_widget.component, while a change to iced_widget.component can't break iced_widget.scrollable.
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.
27→30 iced_widget.component uses iced_widget.buttonpart of a loop✕
Connections
5 pairs of types, where a type in iced_widget.component uses a type in iced_widget.button.
iced_widget.component uses iced_widget.button, so a change to iced_widget.button can break iced_widget.component, while a change to iced_widget.component can't break iced_widget.button.
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.
27→31 iced_widget.component uses iced_widgetpart of a loop✕
Connections
1 pair of types, where a type in iced_widget.component uses a type in iced_widget.
iced_widget.component uses iced_widget, so a change to iced_widget can break iced_widget.component, while a change to iced_widget.component can't break iced_widget.
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.
iced_widget.pane_grid uses iced_beacon.client, so a change to iced_beacon.client can break iced_widget.pane_grid, while a change to iced_widget.pane_grid can't break iced_beacon.client.
Position
Below the diagonal: iced_widget.pane_grid uses a module listed above it, which is the healthy direction.
iced_widget.pane_grid uses iced_core.color, so a change to iced_core.color can break iced_widget.pane_grid, while a change to iced_widget.pane_grid can't break iced_core.color.
Position
Below the diagonal: iced_widget.pane_grid uses a module listed above it, which is the healthy direction.
iced_widget.pane_grid uses iced_core.length, so a change to iced_core.length can break iced_widget.pane_grid, while a change to iced_widget.pane_grid can't break iced_core.length.
Position
Below the diagonal: iced_widget.pane_grid uses a module listed above it, which is the healthy direction.
iced_widget.pane_grid uses iced_core.vector, so a change to iced_core.vector can break iced_widget.pane_grid, while a change to iced_widget.pane_grid can't break iced_core.vector.
Position
Below the diagonal: iced_widget.pane_grid uses a module listed above it, which is the healthy direction.
iced_widget.pane_grid uses iced_core.point, so a change to iced_core.point can break iced_widget.pane_grid, while a change to iced_widget.pane_grid can't break iced_core.point.
Position
Below the diagonal: iced_widget.pane_grid uses a module listed above it, which is the healthy direction.
iced_widget.pane_grid uses iced_core.rectangle, so a change to iced_core.rectangle can break iced_widget.pane_grid, while a change to iced_widget.pane_grid can't break iced_core.rectangle.
Position
Below the diagonal: iced_widget.pane_grid uses a module listed above it, which is the healthy direction.
iced_widget.pane_grid uses iced_core.mouse.cursor, so a change to iced_core.mouse.cursor can break iced_widget.pane_grid, while a change to iced_widget.pane_grid can't break iced_core.mouse.cursor.
Position
Below the diagonal: iced_widget.pane_grid uses a module listed above it, which is the healthy direction.
iced_widget.pane_grid uses iced_core.size, so a change to iced_core.size can break iced_widget.pane_grid, while a change to iced_widget.pane_grid can't break iced_core.size.
Position
Below the diagonal: iced_widget.pane_grid uses a module listed above it, which is the healthy direction.
iced_widget.pane_grid uses iced_core.layout.limits, so a change to iced_core.layout.limits can break iced_widget.pane_grid, while a change to iced_widget.pane_grid can't break iced_core.layout.limits.
Position
Below the diagonal: iced_widget.pane_grid uses a module listed above it, which is the healthy direction.
iced_widget.pane_grid uses iced_core.image, so a change to iced_core.image can break iced_widget.pane_grid, while a change to iced_widget.pane_grid can't break iced_core.image.
Position
Below the diagonal: iced_widget.pane_grid uses a module listed above it, which is the healthy direction.
iced_widget.pane_grid uses iced_core.shell, so a change to iced_core.shell can break iced_widget.pane_grid, while a change to iced_widget.pane_grid can't break iced_core.shell.
Position
Below the diagonal: iced_widget.pane_grid uses a module listed above it, which is the healthy direction.
iced_widget.pane_grid uses iced_core.layout.flex, so a change to iced_core.layout.flex can break iced_widget.pane_grid, while a change to iced_widget.pane_grid can't break iced_core.layout.flex.
Position
Below the diagonal: iced_widget.pane_grid uses a module listed above it, which is the healthy direction.
iced_widget.pane_grid uses iced_core.theme, so a change to iced_core.theme can break iced_widget.pane_grid, while a change to iced_widget.pane_grid can't break iced_core.theme.
Position
Below the diagonal: iced_widget.pane_grid uses a module listed above it, which is the healthy direction.
iced_widget.pane_grid uses iced_core.widget.tree, so a change to iced_core.widget.tree can break iced_widget.pane_grid, while a change to iced_widget.pane_grid can't break iced_core.widget.tree.
Position
Below the diagonal: iced_widget.pane_grid uses a module listed above it, which is the healthy direction.
iced_widget.pane_grid uses iced_core.layout, so a change to iced_core.layout can break iced_widget.pane_grid, while a change to iced_widget.pane_grid can't break iced_core.layout.
Position
Below the diagonal: iced_widget.pane_grid uses a module listed above it, which is the healthy direction.
iced_widget.pane_grid uses iced_core.overlay.element, so a change to iced_core.overlay.element can break iced_widget.pane_grid, while a change to iced_widget.pane_grid can't break iced_core.overlay.element.
Position
Below the diagonal: iced_widget.pane_grid uses a module listed above it, which is the healthy direction.
iced_widget.pane_grid uses iced_widget.combo_box, so a change to iced_widget.combo_box can break iced_widget.pane_grid, while a change to iced_widget.pane_grid can't break iced_widget.combo_box.
Position
Below the diagonal: iced_widget.pane_grid uses a module listed above it, which is the healthy direction.
iced_widget.pane_grid uses iced_widget.component, so a change to iced_widget.component can break iced_widget.pane_grid, while a change to iced_widget.pane_grid can't break iced_widget.component.
Position
Below the diagonal: iced_widget.pane_grid uses a module listed above it, which is the healthy direction.
28→29 iced_widget.pane_grid uses iced_widget.scrollablepart of a loop✕
Connections
1 pair of types, where a type in iced_widget.pane_grid uses a type in iced_widget.scrollable.
iced_widget.pane_grid uses iced_widget.scrollable, so a change to iced_widget.scrollable can break iced_widget.pane_grid, while a change to iced_widget.pane_grid can't break iced_widget.scrollable.
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→30 iced_widget.pane_grid uses iced_widget.buttonpart of a loop✕
Connections
6 pairs of types, where a type in iced_widget.pane_grid uses a type in iced_widget.button.
iced_widget.pane_grid uses iced_widget.button, so a change to iced_widget.button can break iced_widget.pane_grid, while a change to iced_widget.pane_grid can't break iced_widget.button.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→31 iced_widget.pane_grid uses iced_widgetpart of a loop✕
Connections
1 pair of types, where a type in iced_widget.pane_grid uses a type in iced_widget.
iced_widget.pane_grid uses iced_widget, so a change to iced_widget can break iced_widget.pane_grid, while a change to iced_widget.pane_grid can't break iced_widget.
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.
iced_widget.scrollable uses iced_beacon.client, so a change to iced_beacon.client can break iced_widget.scrollable, while a change to iced_widget.scrollable can't break iced_beacon.client.
Position
Below the diagonal: iced_widget.scrollable uses a module listed above it, which is the healthy direction.
iced_widget.scrollable uses iced_core.color, so a change to iced_core.color can break iced_widget.scrollable, while a change to iced_widget.scrollable can't break iced_core.color.
Position
Below the diagonal: iced_widget.scrollable uses a module listed above it, which is the healthy direction.
iced_widget.scrollable uses iced_core.length, so a change to iced_core.length can break iced_widget.scrollable, while a change to iced_widget.scrollable can't break iced_core.length.
Position
Below the diagonal: iced_widget.scrollable uses a module listed above it, which is the healthy direction.
iced_widget.scrollable uses iced_core.vector, so a change to iced_core.vector can break iced_widget.scrollable, while a change to iced_widget.scrollable can't break iced_core.vector.
Position
Below the diagonal: iced_widget.scrollable uses a module listed above it, which is the healthy direction.
iced_widget.scrollable uses iced_graphics.compositor, so a change to iced_graphics.compositor can break iced_widget.scrollable, while a change to iced_widget.scrollable can't break iced_graphics.compositor.
Position
Below the diagonal: iced_widget.scrollable uses a module listed above it, which is the healthy direction.
iced_widget.scrollable uses iced_core.point, so a change to iced_core.point can break iced_widget.scrollable, while a change to iced_widget.scrollable can't break iced_core.point.
Position
Below the diagonal: iced_widget.scrollable uses a module listed above it, which is the healthy direction.
iced_widget.scrollable uses iced_core.rectangle, so a change to iced_core.rectangle can break iced_widget.scrollable, while a change to iced_widget.scrollable can't break iced_core.rectangle.
Position
Below the diagonal: iced_widget.scrollable uses a module listed above it, which is the healthy direction.
iced_widget.scrollable uses iced_core.mouse.cursor, so a change to iced_core.mouse.cursor can break iced_widget.scrollable, while a change to iced_widget.scrollable can't break iced_core.mouse.cursor.
Position
Below the diagonal: iced_widget.scrollable uses a module listed above it, which is the healthy direction.
iced_widget.scrollable uses iced_core.size, so a change to iced_core.size can break iced_widget.scrollable, while a change to iced_widget.scrollable can't break iced_core.size.
Position
Below the diagonal: iced_widget.scrollable uses a module listed above it, which is the healthy direction.
iced_widget.scrollable uses iced_core.layout.limits, so a change to iced_core.layout.limits can break iced_widget.scrollable, while a change to iced_widget.scrollable can't break iced_core.layout.limits.
Position
Below the diagonal: iced_widget.scrollable uses a module listed above it, which is the healthy direction.
iced_widget.scrollable uses iced_core.image, so a change to iced_core.image can break iced_widget.scrollable, while a change to iced_widget.scrollable can't break iced_core.image.
Position
Below the diagonal: iced_widget.scrollable uses a module listed above it, which is the healthy direction.
iced_widget.scrollable uses iced_core.shell, so a change to iced_core.shell can break iced_widget.scrollable, while a change to iced_widget.scrollable can't break iced_core.shell.
Position
Below the diagonal: iced_widget.scrollable uses a module listed above it, which is the healthy direction.
iced_widget.scrollable uses iced_core.layout.flex, so a change to iced_core.layout.flex can break iced_widget.scrollable, while a change to iced_widget.scrollable can't break iced_core.layout.flex.
Position
Below the diagonal: iced_widget.scrollable uses a module listed above it, which is the healthy direction.
iced_widget.scrollable uses iced_core.theme, so a change to iced_core.theme can break iced_widget.scrollable, while a change to iced_widget.scrollable can't break iced_core.theme.
Position
Below the diagonal: iced_widget.scrollable uses a module listed above it, which is the healthy direction.
iced_widget.scrollable uses iced_core.widget.tree, so a change to iced_core.widget.tree can break iced_widget.scrollable, while a change to iced_widget.scrollable can't break iced_core.widget.tree.
Position
Below the diagonal: iced_widget.scrollable uses a module listed above it, which is the healthy direction.
iced_widget.scrollable uses iced_core.layout, so a change to iced_core.layout can break iced_widget.scrollable, while a change to iced_widget.scrollable can't break iced_core.layout.
Position
Below the diagonal: iced_widget.scrollable uses a module listed above it, which is the healthy direction.
iced_widget.scrollable uses iced_core.overlay.element, so a change to iced_core.overlay.element can break iced_widget.scrollable, while a change to iced_widget.scrollable can't break iced_core.overlay.element.
Position
Below the diagonal: iced_widget.scrollable uses a module listed above it, which is the healthy direction.
iced_widget.scrollable uses iced_widget.component, so a change to iced_widget.component can break iced_widget.scrollable, while a change to iced_widget.scrollable can't break iced_widget.component.
Position
Below the diagonal: iced_widget.scrollable uses a module listed above it, which is the healthy direction.
iced_widget.scrollable uses iced_widget.pane_grid, so a change to iced_widget.pane_grid can break iced_widget.scrollable, while a change to iced_widget.scrollable can't break iced_widget.pane_grid.
Position
Below the diagonal: iced_widget.scrollable uses a module listed above it, which is the healthy direction.
29→30 iced_widget.scrollable uses iced_widget.buttonpart of a loop✕
Connections
10 pairs of types, where a type in iced_widget.scrollable uses a type in iced_widget.button.
iced_widget.scrollable uses iced_widget.button, so a change to iced_widget.button can break iced_widget.scrollable, while a change to iced_widget.scrollable can't break iced_widget.button.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→31 iced_widget.scrollable uses iced_widgetpart of a loop✕
Connections
1 pair of types, where a type in iced_widget.scrollable uses a type in iced_widget.
iced_widget.scrollable uses iced_widget, so a change to iced_widget can break iced_widget.scrollable, while a change to iced_widget.scrollable can't break iced_widget.
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.
iced_widget.button uses iced_beacon.client, so a change to iced_beacon.client can break iced_widget.button, while a change to iced_widget.button can't break iced_beacon.client.
Position
Below the diagonal: iced_widget.button uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in iced_widget.button uses a type in iced_core.color.
The types involved
iced_widget.button.Style → iced_core.color.Color
Direction
iced_widget.button uses iced_core.color, so a change to iced_core.color can break iced_widget.button, while a change to iced_widget.button can't break iced_core.color.
Position
Below the diagonal: iced_widget.button uses a module listed above it, which is the healthy direction.
iced_widget.button uses iced_core.length, so a change to iced_core.length can break iced_widget.button, while a change to iced_widget.button can't break iced_core.length.
Position
Below the diagonal: iced_widget.button uses a module listed above it, which is the healthy direction.
iced_widget.button uses iced_core.vector, so a change to iced_core.vector can break iced_widget.button, while a change to iced_widget.button can't break iced_core.vector.
Position
Below the diagonal: iced_widget.button uses a module listed above it, which is the healthy direction.
iced_widget.button uses iced_graphics.compositor, so a change to iced_graphics.compositor can break iced_widget.button, while a change to iced_widget.button can't break iced_graphics.compositor.
Position
Below the diagonal: iced_widget.button uses a module listed above it, which is the healthy direction.
iced_widget.button uses iced_core.rectangle, so a change to iced_core.rectangle can break iced_widget.button, while a change to iced_widget.button can't break iced_core.rectangle.
Position
Below the diagonal: iced_widget.button uses a module listed above it, which is the healthy direction.
iced_widget.button uses iced_core.mouse.cursor, so a change to iced_core.mouse.cursor can break iced_widget.button, while a change to iced_widget.button can't break iced_core.mouse.cursor.
Position
Below the diagonal: iced_widget.button uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in iced_widget.button uses a type in iced_core.size.
The types involved
iced_widget.button.Button → iced_core.size.Size
Direction
iced_widget.button uses iced_core.size, so a change to iced_core.size can break iced_widget.button, while a change to iced_widget.button can't break iced_core.size.
Position
Below the diagonal: iced_widget.button uses a module listed above it, which is the healthy direction.
iced_widget.button uses iced_core.layout.limits, so a change to iced_core.layout.limits can break iced_widget.button, while a change to iced_widget.button can't break iced_core.layout.limits.
Position
Below the diagonal: iced_widget.button uses a module listed above it, which is the healthy direction.
iced_widget.button uses iced_core.image, so a change to iced_core.image can break iced_widget.button, while a change to iced_widget.button can't break iced_core.image.
Position
Below the diagonal: iced_widget.button uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in iced_widget.button uses a type in iced_core.shell.
The types involved
iced_widget.button.Button → iced_core.shell.Shell
Direction
iced_widget.button uses iced_core.shell, so a change to iced_core.shell can break iced_widget.button, while a change to iced_widget.button can't break iced_core.shell.
Position
Below the diagonal: iced_widget.button uses a module listed above it, which is the healthy direction.
iced_widget.button uses iced_core.layout.flex, so a change to iced_core.layout.flex can break iced_widget.button, while a change to iced_widget.button can't break iced_core.layout.flex.
Position
Below the diagonal: iced_widget.button uses a module listed above it, which is the healthy direction.
iced_widget.button uses iced_core.theme, so a change to iced_core.theme can break iced_widget.button, while a change to iced_widget.button can't break iced_core.theme.
Position
Below the diagonal: iced_widget.button uses a module listed above it, which is the healthy direction.
iced_widget.button uses iced_core.widget.tree, so a change to iced_core.widget.tree can break iced_widget.button, while a change to iced_widget.button can't break iced_core.widget.tree.
Position
Below the diagonal: iced_widget.button uses a module listed above it, which is the healthy direction.
iced_widget.button uses iced_core.layout, so a change to iced_core.layout can break iced_widget.button, while a change to iced_widget.button can't break iced_core.layout.
Position
Below the diagonal: iced_widget.button uses a module listed above it, which is the healthy direction.
iced_widget.button uses iced_core.overlay.element, so a change to iced_core.overlay.element can break iced_widget.button, while a change to iced_widget.button can't break iced_core.overlay.element.
Position
Below the diagonal: iced_widget.button uses a module listed above it, which is the healthy direction.
iced_widget.button uses iced_widget.scrollable, so a change to iced_widget.scrollable can break iced_widget.button, while a change to iced_widget.button can't break iced_widget.scrollable.
Position
Below the diagonal: iced_widget.button uses a module listed above it, which is the healthy direction.
30→31 iced_widget.button uses iced_widgetpart of a loop✕
Connections
1 pair of types, where a type in iced_widget.button uses a type in iced_widget.
The types involved
iced_widget.button.Button → iced_widget.Widget
Direction
iced_widget.button uses iced_widget, so a change to iced_widget can break iced_widget.button, while a change to iced_widget.button can't break iced_widget.
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.
1 pair of types, where a type in iced_widget uses a type in iced_beacon.client.
The types involved
iced_widget.Explain → iced_beacon.client.Event
Direction
iced_widget uses iced_beacon.client, so a change to iced_beacon.client can break iced_widget, while a change to iced_widget can't break iced_beacon.client.
Position
Below the diagonal: iced_widget uses a module listed above it, which is the healthy direction.
iced_widget uses iced_core.rectangle, so a change to iced_core.rectangle can break iced_widget, while a change to iced_widget can't break iced_core.rectangle.
Position
Below the diagonal: iced_widget uses a module listed above it, which is the healthy direction.
iced_widget uses iced_core.mouse.cursor, so a change to iced_core.mouse.cursor can break iced_widget, while a change to iced_widget can't break iced_core.mouse.cursor.
Position
Below the diagonal: iced_widget uses a module listed above it, which is the healthy direction.
iced_widget uses iced_core.layout.limits, so a change to iced_core.layout.limits can break iced_widget, while a change to iced_widget can't break iced_core.layout.limits.
Position
Below the diagonal: iced_widget uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in iced_widget uses a type in iced_core.layout.flex.
The types involved
iced_widget.Explain → iced_core.layout.flex.Meta
Direction
iced_widget uses iced_core.layout.flex, so a change to iced_core.layout.flex can break iced_widget, while a change to iced_widget can't break iced_core.layout.flex.
Position
Below the diagonal: iced_widget uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in iced_widget uses a type in iced_core.widget.tree.
The types involved
iced_widget.Explain → iced_core.widget.tree.Tag
iced_widget.Explain → iced_core.widget.tree.Tree
Direction
iced_widget uses iced_core.widget.tree, so a change to iced_core.widget.tree can break iced_widget, while a change to iced_widget can't break iced_core.widget.tree.
Position
Below the diagonal: iced_widget uses a module listed above it, which is the healthy direction.
iced_widget uses iced_core.overlay.element, so a change to iced_core.overlay.element can break iced_widget, while a change to iced_widget can't break iced_core.overlay.element.
Position
Below the diagonal: iced_widget uses a module listed above it, which is the healthy direction.
iced_widget uses iced_widget.scrollable, so a change to iced_widget.scrollable can break iced_widget, while a change to iced_widget can't break iced_widget.scrollable.
Position
Below the diagonal: iced_widget uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in iced_widget uses a type in iced_widget.button.
The types involved
iced_widget.Explain → iced_widget.button.State
iced_widget.Explain → iced_widget.button.Style
Direction
iced_widget uses iced_widget.button, so a change to iced_widget.button can break iced_widget, while a change to iced_widget can't break iced_widget.button.
Position
Below the diagonal: iced_widget uses a module listed above it, which is the healthy direction.
iced_widget.column uses iced_beacon.client, so a change to iced_beacon.client can break iced_widget.column, while a change to iced_widget.column can't break iced_beacon.client.
Position
Below the diagonal: iced_widget.column uses a module listed above it, which is the healthy direction.
iced_widget.column uses iced_core.length, so a change to iced_core.length can break iced_widget.column, while a change to iced_widget.column can't break iced_core.length.
Position
Below the diagonal: iced_widget.column uses a module listed above it, which is the healthy direction.
iced_widget.column uses iced_core.vector, so a change to iced_core.vector can break iced_widget.column, while a change to iced_widget.column can't break iced_core.vector.
Position
Below the diagonal: iced_widget.column uses a module listed above it, which is the healthy direction.
iced_widget.column uses iced_graphics.compositor, so a change to iced_graphics.compositor can break iced_widget.column, while a change to iced_widget.column can't break iced_graphics.compositor.
Position
Below the diagonal: iced_widget.column uses a module listed above it, which is the healthy direction.
iced_widget.column uses iced_core.rectangle, so a change to iced_core.rectangle can break iced_widget.column, while a change to iced_widget.column can't break iced_core.rectangle.
Position
Below the diagonal: iced_widget.column uses a module listed above it, which is the healthy direction.
iced_widget.column uses iced_core.mouse.cursor, so a change to iced_core.mouse.cursor can break iced_widget.column, while a change to iced_widget.column can't break iced_core.mouse.cursor.
Position
Below the diagonal: iced_widget.column uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in iced_widget.column uses a type in iced_core.size.
The types involved
iced_widget.column.Column → iced_core.size.Size
iced_widget.column.Wrapping → iced_core.size.Size
Direction
iced_widget.column uses iced_core.size, so a change to iced_core.size can break iced_widget.column, while a change to iced_widget.column can't break iced_core.size.
Position
Below the diagonal: iced_widget.column uses a module listed above it, which is the healthy direction.
iced_widget.column uses iced_core.layout.limits, so a change to iced_core.layout.limits can break iced_widget.column, while a change to iced_widget.column can't break iced_core.layout.limits.
Position
Below the diagonal: iced_widget.column uses a module listed above it, which is the healthy direction.
iced_widget.column uses iced_core.image, so a change to iced_core.image can break iced_widget.column, while a change to iced_widget.column can't break iced_core.image.
Position
Below the diagonal: iced_widget.column uses a module listed above it, which is the healthy direction.
iced_widget.column uses iced_core.shell, so a change to iced_core.shell can break iced_widget.column, while a change to iced_widget.column can't break iced_core.shell.
Position
Below the diagonal: iced_widget.column uses a module listed above it, which is the healthy direction.
iced_widget.column uses iced_core.layout.flex, so a change to iced_core.layout.flex can break iced_widget.column, while a change to iced_widget.column can't break iced_core.layout.flex.
Position
Below the diagonal: iced_widget.column uses a module listed above it, which is the healthy direction.
iced_widget.column uses iced_core.theme, so a change to iced_core.theme can break iced_widget.column, while a change to iced_widget.column can't break iced_core.theme.
Position
Below the diagonal: iced_widget.column uses a module listed above it, which is the healthy direction.
iced_widget.column uses iced_core.widget.tree, so a change to iced_core.widget.tree can break iced_widget.column, while a change to iced_widget.column can't break iced_core.widget.tree.
Position
Below the diagonal: iced_widget.column uses a module listed above it, which is the healthy direction.
iced_widget.column uses iced_core.layout, so a change to iced_core.layout can break iced_widget.column, while a change to iced_widget.column can't break iced_core.layout.
Position
Below the diagonal: iced_widget.column uses a module listed above it, which is the healthy direction.
iced_widget.column uses iced_core.overlay.element, so a change to iced_core.overlay.element can break iced_widget.column, while a change to iced_widget.column can't break iced_core.overlay.element.
Position
Below the diagonal: iced_widget.column uses a module listed above it, which is the healthy direction.
iced_widget.column uses iced_widget.scrollable, so a change to iced_widget.scrollable can break iced_widget.column, while a change to iced_widget.column can't break iced_widget.scrollable.
Position
Below the diagonal: iced_widget.column uses a module listed above it, which is the healthy direction.
iced_widget.column uses iced_widget.button, so a change to iced_widget.button can break iced_widget.column, while a change to iced_widget.column can't break iced_widget.button.
Position
Below the diagonal: iced_widget.column uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in iced_widget.column uses a type in iced_widget.
The types involved
iced_widget.column.Column → iced_widget.Widget
iced_widget.column.Wrapping → iced_widget.Widget
Direction
iced_widget.column uses iced_widget, so a change to iced_widget can break iced_widget.column, while a change to iced_widget.column can't break iced_widget.
Position
Below the diagonal: iced_widget.column uses a module listed above it, which is the healthy direction.
iced_widget.container uses iced_beacon.client, so a change to iced_beacon.client can break iced_widget.container, while a change to iced_widget.container can't break iced_beacon.client.
Position
Below the diagonal: iced_widget.container uses a module listed above it, which is the healthy direction.
iced_widget.container uses iced_core.color, so a change to iced_core.color can break iced_widget.container, while a change to iced_widget.container can't break iced_core.color.
Position
Below the diagonal: iced_widget.container uses a module listed above it, which is the healthy direction.
iced_widget.container uses iced_core.length, so a change to iced_core.length can break iced_widget.container, while a change to iced_widget.container can't break iced_core.length.
Position
Below the diagonal: iced_widget.container uses a module listed above it, which is the healthy direction.
iced_widget.container uses iced_core.vector, so a change to iced_core.vector can break iced_widget.container, while a change to iced_widget.container can't break iced_core.vector.
Position
Below the diagonal: iced_widget.container uses a module listed above it, which is the healthy direction.
iced_widget.container uses iced_graphics.compositor, so a change to iced_graphics.compositor can break iced_widget.container, while a change to iced_widget.container can't break iced_graphics.compositor.
Position
Below the diagonal: iced_widget.container uses a module listed above it, which is the healthy direction.
iced_widget.container uses iced_core.rectangle, so a change to iced_core.rectangle can break iced_widget.container, while a change to iced_widget.container can't break iced_core.rectangle.
Position
Below the diagonal: iced_widget.container uses a module listed above it, which is the healthy direction.
iced_widget.container uses iced_core.mouse.cursor, so a change to iced_core.mouse.cursor can break iced_widget.container, while a change to iced_widget.container can't break iced_core.mouse.cursor.
Position
Below the diagonal: iced_widget.container uses a module listed above it, which is the healthy direction.
iced_widget.container uses iced_core.size, so a change to iced_core.size can break iced_widget.container, while a change to iced_widget.container can't break iced_core.size.
Position
Below the diagonal: iced_widget.container uses a module listed above it, which is the healthy direction.
iced_widget.container uses iced_core.layout.limits, so a change to iced_core.layout.limits can break iced_widget.container, while a change to iced_widget.container can't break iced_core.layout.limits.
Position
Below the diagonal: iced_widget.container uses a module listed above it, which is the healthy direction.
iced_widget.container uses iced_core.image, so a change to iced_core.image can break iced_widget.container, while a change to iced_widget.container can't break iced_core.image.
Position
Below the diagonal: iced_widget.container uses a module listed above it, which is the healthy direction.
iced_widget.container uses iced_core.shell, so a change to iced_core.shell can break iced_widget.container, while a change to iced_widget.container can't break iced_core.shell.
Position
Below the diagonal: iced_widget.container uses a module listed above it, which is the healthy direction.
iced_widget.container uses iced_core.layout.flex, so a change to iced_core.layout.flex can break iced_widget.container, while a change to iced_widget.container can't break iced_core.layout.flex.
Position
Below the diagonal: iced_widget.container uses a module listed above it, which is the healthy direction.
iced_widget.container uses iced_core.theme, so a change to iced_core.theme can break iced_widget.container, while a change to iced_widget.container can't break iced_core.theme.
Position
Below the diagonal: iced_widget.container uses a module listed above it, which is the healthy direction.
iced_widget.container uses iced_core.widget.tree, so a change to iced_core.widget.tree can break iced_widget.container, while a change to iced_widget.container can't break iced_core.widget.tree.
Position
Below the diagonal: iced_widget.container uses a module listed above it, which is the healthy direction.
iced_widget.container uses iced_core.layout, so a change to iced_core.layout can break iced_widget.container, while a change to iced_widget.container can't break iced_core.layout.
Position
Below the diagonal: iced_widget.container uses a module listed above it, which is the healthy direction.
iced_widget.container uses iced_core.overlay.element, so a change to iced_core.overlay.element can break iced_widget.container, while a change to iced_widget.container can't break iced_core.overlay.element.
Position
Below the diagonal: iced_widget.container uses a module listed above it, which is the healthy direction.
iced_widget.container uses iced_widget.scrollable, so a change to iced_widget.scrollable can break iced_widget.container, while a change to iced_widget.container can't break iced_widget.scrollable.
Position
Below the diagonal: iced_widget.container uses a module listed above it, which is the healthy direction.
iced_widget.container uses iced_widget.button, so a change to iced_widget.button can break iced_widget.container, while a change to iced_widget.container can't break iced_widget.button.
Position
Below the diagonal: iced_widget.container uses a module listed above it, which is the healthy direction.
iced_widget.container uses iced_widget, so a change to iced_widget can break iced_widget.container, while a change to iced_widget.container can't break iced_widget.
Position
Below the diagonal: iced_widget.container uses a module listed above it, which is the healthy direction.
iced_widget.overlay.menu uses iced_beacon.client, so a change to iced_beacon.client can break iced_widget.overlay.menu, while a change to iced_widget.overlay.menu can't break iced_beacon.client.
Position
Below the diagonal: iced_widget.overlay.menu uses a module listed above it, which is the healthy direction.
iced_widget.overlay.menu uses iced_core.color, so a change to iced_core.color can break iced_widget.overlay.menu, while a change to iced_widget.overlay.menu can't break iced_core.color.
Position
Below the diagonal: iced_widget.overlay.menu uses a module listed above it, which is the healthy direction.
iced_widget.overlay.menu uses iced_core.font, so a change to iced_core.font can break iced_widget.overlay.menu, while a change to iced_widget.overlay.menu can't break iced_core.font.
Position
Below the diagonal: iced_widget.overlay.menu uses a module listed above it, which is the healthy direction.
iced_widget.overlay.menu uses iced_core.pixels, so a change to iced_core.pixels can break iced_widget.overlay.menu, while a change to iced_widget.overlay.menu can't break iced_core.pixels.
Position
Below the diagonal: iced_widget.overlay.menu uses a module listed above it, which is the healthy direction.
iced_widget.overlay.menu uses iced_core.length, so a change to iced_core.length can break iced_widget.overlay.menu, while a change to iced_widget.overlay.menu can't break iced_core.length.
Position
Below the diagonal: iced_widget.overlay.menu uses a module listed above it, which is the healthy direction.
iced_widget.overlay.menu uses iced_graphics.compositor, so a change to iced_graphics.compositor can break iced_widget.overlay.menu, while a change to iced_widget.overlay.menu can't break iced_graphics.compositor.
Position
Below the diagonal: iced_widget.overlay.menu uses a module listed above it, which is the healthy direction.
iced_widget.overlay.menu uses iced_core.point, so a change to iced_core.point can break iced_widget.overlay.menu, while a change to iced_widget.overlay.menu can't break iced_core.point.
Position
Below the diagonal: iced_widget.overlay.menu uses a module listed above it, which is the healthy direction.
iced_widget.overlay.menu uses iced_core.rectangle, so a change to iced_core.rectangle can break iced_widget.overlay.menu, while a change to iced_widget.overlay.menu can't break iced_core.rectangle.
Position
Below the diagonal: iced_widget.overlay.menu uses a module listed above it, which is the healthy direction.
iced_widget.overlay.menu uses iced_core.mouse.cursor, so a change to iced_core.mouse.cursor can break iced_widget.overlay.menu, while a change to iced_widget.overlay.menu can't break iced_core.mouse.cursor.
Position
Below the diagonal: iced_widget.overlay.menu uses a module listed above it, which is the healthy direction.
iced_widget.overlay.menu uses iced_core.size, so a change to iced_core.size can break iced_widget.overlay.menu, while a change to iced_widget.overlay.menu can't break iced_core.size.
Position
Below the diagonal: iced_widget.overlay.menu uses a module listed above it, which is the healthy direction.
iced_widget.overlay.menu uses iced_core.layout.limits, so a change to iced_core.layout.limits can break iced_widget.overlay.menu, while a change to iced_widget.overlay.menu can't break iced_core.layout.limits.
Position
Below the diagonal: iced_widget.overlay.menu uses a module listed above it, which is the healthy direction.
iced_widget.overlay.menu uses iced_core.image, so a change to iced_core.image can break iced_widget.overlay.menu, while a change to iced_widget.overlay.menu can't break iced_core.image.
Position
Below the diagonal: iced_widget.overlay.menu uses a module listed above it, which is the healthy direction.
iced_widget.overlay.menu uses iced_core.shell, so a change to iced_core.shell can break iced_widget.overlay.menu, while a change to iced_widget.overlay.menu can't break iced_core.shell.
Position
Below the diagonal: iced_widget.overlay.menu uses a module listed above it, which is the healthy direction.
iced_widget.overlay.menu uses iced_core.layout.flex, so a change to iced_core.layout.flex can break iced_widget.overlay.menu, while a change to iced_widget.overlay.menu can't break iced_core.layout.flex.
Position
Below the diagonal: iced_widget.overlay.menu uses a module listed above it, which is the healthy direction.
iced_widget.overlay.menu uses iced_core.text, so a change to iced_core.text can break iced_widget.overlay.menu, while a change to iced_widget.overlay.menu can't break iced_core.text.
Position
Below the diagonal: iced_widget.overlay.menu uses a module listed above it, which is the healthy direction.
iced_widget.overlay.menu uses iced_core.theme, so a change to iced_core.theme can break iced_widget.overlay.menu, while a change to iced_widget.overlay.menu can't break iced_core.theme.
Position
Below the diagonal: iced_widget.overlay.menu uses a module listed above it, which is the healthy direction.
iced_widget.overlay.menu uses iced_core.widget.tree, so a change to iced_core.widget.tree can break iced_widget.overlay.menu, while a change to iced_widget.overlay.menu can't break iced_core.widget.tree.
Position
Below the diagonal: iced_widget.overlay.menu uses a module listed above it, which is the healthy direction.
iced_widget.overlay.menu uses iced_core.layout, so a change to iced_core.layout can break iced_widget.overlay.menu, while a change to iced_widget.overlay.menu can't break iced_core.layout.
Position
Below the diagonal: iced_widget.overlay.menu uses a module listed above it, which is the healthy direction.
iced_widget.overlay.menu uses iced_core.overlay.element, so a change to iced_core.overlay.element can break iced_widget.overlay.menu, while a change to iced_widget.overlay.menu can't break iced_core.overlay.element.
Position
Below the diagonal: iced_widget.overlay.menu uses a module listed above it, which is the healthy direction.
iced_widget.overlay.menu uses iced_widget.component, so a change to iced_widget.component can break iced_widget.overlay.menu, while a change to iced_widget.overlay.menu can't break iced_widget.component.
Position
Below the diagonal: iced_widget.overlay.menu uses a module listed above it, which is the healthy direction.
iced_widget.overlay.menu uses iced_widget.scrollable, so a change to iced_widget.scrollable can break iced_widget.overlay.menu, while a change to iced_widget.overlay.menu can't break iced_widget.scrollable.
Position
Below the diagonal: iced_widget.overlay.menu uses a module listed above it, which is the healthy direction.
iced_widget.overlay.menu uses iced_widget.button, so a change to iced_widget.button can break iced_widget.overlay.menu, while a change to iced_widget.overlay.menu can't break iced_widget.button.
Position
Below the diagonal: iced_widget.overlay.menu uses a module listed above it, which is the healthy direction.
iced_widget.overlay.menu uses iced_widget, so a change to iced_widget can break iced_widget.overlay.menu, while a change to iced_widget.overlay.menu can't break iced_widget.
Position
Below the diagonal: iced_widget.overlay.menu uses a module listed above it, which is the healthy direction.
iced_widget.pick_list uses iced_beacon.client, so a change to iced_beacon.client can break iced_widget.pick_list, while a change to iced_widget.pick_list can't break iced_beacon.client.
Position
Below the diagonal: iced_widget.pick_list uses a module listed above it, which is the healthy direction.
iced_widget.pick_list uses iced_core.color, so a change to iced_core.color can break iced_widget.pick_list, while a change to iced_widget.pick_list can't break iced_core.color.
Position
Below the diagonal: iced_widget.pick_list uses a module listed above it, which is the healthy direction.
iced_widget.pick_list uses iced_core.font, so a change to iced_core.font can break iced_widget.pick_list, while a change to iced_widget.pick_list can't break iced_core.font.
Position
Below the diagonal: iced_widget.pick_list uses a module listed above it, which is the healthy direction.
iced_widget.pick_list uses iced_core.pixels, so a change to iced_core.pixels can break iced_widget.pick_list, while a change to iced_widget.pick_list can't break iced_core.pixels.
Position
Below the diagonal: iced_widget.pick_list uses a module listed above it, which is the healthy direction.
iced_widget.pick_list uses iced_core.length, so a change to iced_core.length can break iced_widget.pick_list, while a change to iced_widget.pick_list can't break iced_core.length.
Position
Below the diagonal: iced_widget.pick_list uses a module listed above it, which is the healthy direction.
iced_widget.pick_list uses iced_core.vector, so a change to iced_core.vector can break iced_widget.pick_list, while a change to iced_widget.pick_list can't break iced_core.vector.
Position
Below the diagonal: iced_widget.pick_list uses a module listed above it, which is the healthy direction.
iced_widget.pick_list uses iced_graphics.compositor, so a change to iced_graphics.compositor can break iced_widget.pick_list, while a change to iced_widget.pick_list can't break iced_graphics.compositor.
Position
Below the diagonal: iced_widget.pick_list uses a module listed above it, which is the healthy direction.
iced_widget.pick_list uses iced_core.rectangle, so a change to iced_core.rectangle can break iced_widget.pick_list, while a change to iced_widget.pick_list can't break iced_core.rectangle.
Position
Below the diagonal: iced_widget.pick_list uses a module listed above it, which is the healthy direction.
iced_widget.pick_list uses iced_core.mouse.cursor, so a change to iced_core.mouse.cursor can break iced_widget.pick_list, while a change to iced_widget.pick_list can't break iced_core.mouse.cursor.
Position
Below the diagonal: iced_widget.pick_list uses a module listed above it, which is the healthy direction.
iced_widget.pick_list uses iced_core.size, so a change to iced_core.size can break iced_widget.pick_list, while a change to iced_widget.pick_list can't break iced_core.size.
Position
Below the diagonal: iced_widget.pick_list uses a module listed above it, which is the healthy direction.
iced_widget.pick_list uses iced_core.layout.limits, so a change to iced_core.layout.limits can break iced_widget.pick_list, while a change to iced_widget.pick_list can't break iced_core.layout.limits.
Position
Below the diagonal: iced_widget.pick_list uses a module listed above it, which is the healthy direction.
iced_widget.pick_list uses iced_core.image, so a change to iced_core.image can break iced_widget.pick_list, while a change to iced_widget.pick_list can't break iced_core.image.
Position
Below the diagonal: iced_widget.pick_list uses a module listed above it, which is the healthy direction.
iced_widget.pick_list uses iced_core.shell, so a change to iced_core.shell can break iced_widget.pick_list, while a change to iced_widget.pick_list can't break iced_core.shell.
Position
Below the diagonal: iced_widget.pick_list uses a module listed above it, which is the healthy direction.
iced_widget.pick_list uses iced_core.layout.flex, so a change to iced_core.layout.flex can break iced_widget.pick_list, while a change to iced_widget.pick_list can't break iced_core.layout.flex.
Position
Below the diagonal: iced_widget.pick_list uses a module listed above it, which is the healthy direction.
iced_widget.pick_list uses iced_core.text, so a change to iced_core.text can break iced_widget.pick_list, while a change to iced_widget.pick_list can't break iced_core.text.
Position
Below the diagonal: iced_widget.pick_list uses a module listed above it, which is the healthy direction.
iced_widget.pick_list uses iced_core.theme, so a change to iced_core.theme can break iced_widget.pick_list, while a change to iced_widget.pick_list can't break iced_core.theme.
Position
Below the diagonal: iced_widget.pick_list uses a module listed above it, which is the healthy direction.
iced_widget.pick_list uses iced_core.widget.tree, so a change to iced_core.widget.tree can break iced_widget.pick_list, while a change to iced_widget.pick_list can't break iced_core.widget.tree.
Position
Below the diagonal: iced_widget.pick_list uses a module listed above it, which is the healthy direction.
iced_widget.pick_list uses iced_core.layout, so a change to iced_core.layout can break iced_widget.pick_list, while a change to iced_widget.pick_list can't break iced_core.layout.
Position
Below the diagonal: iced_widget.pick_list uses a module listed above it, which is the healthy direction.
iced_widget.pick_list uses iced_core.overlay.element, so a change to iced_core.overlay.element can break iced_widget.pick_list, while a change to iced_widget.pick_list can't break iced_core.overlay.element.
Position
Below the diagonal: iced_widget.pick_list uses a module listed above it, which is the healthy direction.
iced_widget.pick_list uses iced_widget.scrollable, so a change to iced_widget.scrollable can break iced_widget.pick_list, while a change to iced_widget.pick_list can't break iced_widget.scrollable.
Position
Below the diagonal: iced_widget.pick_list uses a module listed above it, which is the healthy direction.
iced_widget.pick_list uses iced_widget.button, so a change to iced_widget.button can break iced_widget.pick_list, while a change to iced_widget.pick_list can't break iced_widget.button.
Position
Below the diagonal: iced_widget.pick_list uses a module listed above it, which is the healthy direction.
iced_widget.pick_list uses iced_widget, so a change to iced_widget can break iced_widget.pick_list, while a change to iced_widget.pick_list can't break iced_widget.
Position
Below the diagonal: iced_widget.pick_list uses a module listed above it, which is the healthy direction.
iced_widget.checkbox uses iced_beacon.client, so a change to iced_beacon.client can break iced_widget.checkbox, while a change to iced_widget.checkbox can't break iced_beacon.client.
Position
Below the diagonal: iced_widget.checkbox uses a module listed above it, which is the healthy direction.
iced_widget.checkbox uses iced_core.color, so a change to iced_core.color can break iced_widget.checkbox, while a change to iced_widget.checkbox can't break iced_core.color.
Position
Below the diagonal: iced_widget.checkbox uses a module listed above it, which is the healthy direction.
iced_widget.checkbox uses iced_core.font, so a change to iced_core.font can break iced_widget.checkbox, while a change to iced_widget.checkbox can't break iced_core.font.
Position
Below the diagonal: iced_widget.checkbox uses a module listed above it, which is the healthy direction.
iced_widget.checkbox uses iced_core.pixels, so a change to iced_core.pixels can break iced_widget.checkbox, while a change to iced_widget.checkbox can't break iced_core.pixels.
Position
Below the diagonal: iced_widget.checkbox uses a module listed above it, which is the healthy direction.
iced_widget.checkbox uses iced_core.length, so a change to iced_core.length can break iced_widget.checkbox, while a change to iced_widget.checkbox can't break iced_core.length.
Position
Below the diagonal: iced_widget.checkbox uses a module listed above it, which is the healthy direction.
iced_widget.checkbox uses iced_core.rectangle, so a change to iced_core.rectangle can break iced_widget.checkbox, while a change to iced_widget.checkbox can't break iced_core.rectangle.
Position
Below the diagonal: iced_widget.checkbox uses a module listed above it, which is the healthy direction.
iced_widget.checkbox uses iced_core.mouse.cursor, so a change to iced_core.mouse.cursor can break iced_widget.checkbox, while a change to iced_widget.checkbox can't break iced_core.mouse.cursor.
Position
Below the diagonal: iced_widget.checkbox uses a module listed above it, which is the healthy direction.
iced_widget.checkbox uses iced_core.size, so a change to iced_core.size can break iced_widget.checkbox, while a change to iced_widget.checkbox can't break iced_core.size.
Position
Below the diagonal: iced_widget.checkbox uses a module listed above it, which is the healthy direction.
iced_widget.checkbox uses iced_core.layout.limits, so a change to iced_core.layout.limits can break iced_widget.checkbox, while a change to iced_widget.checkbox can't break iced_core.layout.limits.
Position
Below the diagonal: iced_widget.checkbox uses a module listed above it, which is the healthy direction.
iced_widget.checkbox uses iced_core.image, so a change to iced_core.image can break iced_widget.checkbox, while a change to iced_widget.checkbox can't break iced_core.image.
Position
Below the diagonal: iced_widget.checkbox uses a module listed above it, which is the healthy direction.
iced_widget.checkbox uses iced_core.shell, so a change to iced_core.shell can break iced_widget.checkbox, while a change to iced_widget.checkbox can't break iced_core.shell.
Position
Below the diagonal: iced_widget.checkbox uses a module listed above it, which is the healthy direction.
iced_widget.checkbox uses iced_core.layout.flex, so a change to iced_core.layout.flex can break iced_widget.checkbox, while a change to iced_widget.checkbox can't break iced_core.layout.flex.
Position
Below the diagonal: iced_widget.checkbox uses a module listed above it, which is the healthy direction.
iced_widget.checkbox uses iced_core.text, so a change to iced_core.text can break iced_widget.checkbox, while a change to iced_widget.checkbox can't break iced_core.text.
Position
Below the diagonal: iced_widget.checkbox uses a module listed above it, which is the healthy direction.
iced_widget.checkbox uses iced_core.theme, so a change to iced_core.theme can break iced_widget.checkbox, while a change to iced_widget.checkbox can't break iced_core.theme.
Position
Below the diagonal: iced_widget.checkbox uses a module listed above it, which is the healthy direction.
iced_widget.checkbox uses iced_core.widget.tree, so a change to iced_core.widget.tree can break iced_widget.checkbox, while a change to iced_widget.checkbox can't break iced_core.widget.tree.
Position
Below the diagonal: iced_widget.checkbox uses a module listed above it, which is the healthy direction.
iced_widget.checkbox uses iced_core.layout, so a change to iced_core.layout can break iced_widget.checkbox, while a change to iced_widget.checkbox can't break iced_core.layout.
Position
Below the diagonal: iced_widget.checkbox uses a module listed above it, which is the healthy direction.
iced_widget.checkbox uses iced_widget.scrollable, so a change to iced_widget.scrollable can break iced_widget.checkbox, while a change to iced_widget.checkbox can't break iced_widget.scrollable.
Position
Below the diagonal: iced_widget.checkbox uses a module listed above it, which is the healthy direction.
iced_widget.checkbox uses iced_widget.button, so a change to iced_widget.button can break iced_widget.checkbox, while a change to iced_widget.checkbox can't break iced_widget.button.
Position
Below the diagonal: iced_widget.checkbox uses a module listed above it, which is the healthy direction.
iced_widget.checkbox uses iced_widget, so a change to iced_widget can break iced_widget.checkbox, while a change to iced_widget.checkbox can't break iced_widget.
Position
Below the diagonal: iced_widget.checkbox uses a module listed above it, which is the healthy direction.
iced_widget.checkbox uses iced_widget.column, so a change to iced_widget.column can break iced_widget.checkbox, while a change to iced_widget.checkbox can't break iced_widget.column.
Position
Below the diagonal: iced_widget.checkbox uses a module listed above it, which is the healthy direction.
iced_widget.text_editor uses iced_beacon.client, so a change to iced_beacon.client can break iced_widget.text_editor, while a change to iced_widget.text_editor can't break iced_beacon.client.
Position
Below the diagonal: iced_widget.text_editor uses a module listed above it, which is the healthy direction.
iced_widget.text_editor uses iced_core.color, so a change to iced_core.color can break iced_widget.text_editor, while a change to iced_widget.text_editor can't break iced_core.color.
Position
Below the diagonal: iced_widget.text_editor uses a module listed above it, which is the healthy direction.
iced_widget.text_editor uses iced_core.font, so a change to iced_core.font can break iced_widget.text_editor, while a change to iced_widget.text_editor can't break iced_core.font.
Position
Below the diagonal: iced_widget.text_editor uses a module listed above it, which is the healthy direction.
iced_widget.text_editor uses iced_core.pixels, so a change to iced_core.pixels can break iced_widget.text_editor, while a change to iced_widget.text_editor can't break iced_core.pixels.
Position
Below the diagonal: iced_widget.text_editor uses a module listed above it, which is the healthy direction.
iced_widget.text_editor uses iced_core.length, so a change to iced_core.length can break iced_widget.text_editor, while a change to iced_widget.text_editor can't break iced_core.length.
Position
Below the diagonal: iced_widget.text_editor uses a module listed above it, which is the healthy direction.
iced_widget.text_editor uses iced_graphics.compositor, so a change to iced_graphics.compositor can break iced_widget.text_editor, while a change to iced_widget.text_editor can't break iced_graphics.compositor.
Position
Below the diagonal: iced_widget.text_editor uses a module listed above it, which is the healthy direction.
iced_widget.text_editor uses iced_core.rectangle, so a change to iced_core.rectangle can break iced_widget.text_editor, while a change to iced_widget.text_editor can't break iced_core.rectangle.
Position
Below the diagonal: iced_widget.text_editor uses a module listed above it, which is the healthy direction.
iced_widget.text_editor uses iced_core.mouse.cursor, so a change to iced_core.mouse.cursor can break iced_widget.text_editor, while a change to iced_widget.text_editor can't break iced_core.mouse.cursor.
Position
Below the diagonal: iced_widget.text_editor uses a module listed above it, which is the healthy direction.
iced_widget.text_editor uses iced_core.size, so a change to iced_core.size can break iced_widget.text_editor, while a change to iced_widget.text_editor can't break iced_core.size.
Position
Below the diagonal: iced_widget.text_editor uses a module listed above it, which is the healthy direction.
iced_widget.text_editor uses iced_core.layout.limits, so a change to iced_core.layout.limits can break iced_widget.text_editor, while a change to iced_widget.text_editor can't break iced_core.layout.limits.
Position
Below the diagonal: iced_widget.text_editor uses a module listed above it, which is the healthy direction.
iced_widget.text_editor uses iced_core.image, so a change to iced_core.image can break iced_widget.text_editor, while a change to iced_widget.text_editor can't break iced_core.image.
Position
Below the diagonal: iced_widget.text_editor uses a module listed above it, which is the healthy direction.
iced_widget.text_editor uses iced_core.shell, so a change to iced_core.shell can break iced_widget.text_editor, while a change to iced_widget.text_editor can't break iced_core.shell.
Position
Below the diagonal: iced_widget.text_editor uses a module listed above it, which is the healthy direction.
iced_widget.text_editor uses iced_core.layout.flex, so a change to iced_core.layout.flex can break iced_widget.text_editor, while a change to iced_widget.text_editor can't break iced_core.layout.flex.
Position
Below the diagonal: iced_widget.text_editor uses a module listed above it, which is the healthy direction.
iced_widget.text_editor uses iced_core.text, so a change to iced_core.text can break iced_widget.text_editor, while a change to iced_widget.text_editor can't break iced_core.text.
Position
Below the diagonal: iced_widget.text_editor uses a module listed above it, which is the healthy direction.
iced_widget.text_editor uses iced_core.text.editor, so a change to iced_core.text.editor can break iced_widget.text_editor, while a change to iced_widget.text_editor can't break iced_core.text.editor.
Position
Below the diagonal: iced_widget.text_editor uses a module listed above it, which is the healthy direction.
iced_widget.text_editor uses iced_core.theme, so a change to iced_core.theme can break iced_widget.text_editor, while a change to iced_widget.text_editor can't break iced_core.theme.
Position
Below the diagonal: iced_widget.text_editor uses a module listed above it, which is the healthy direction.
iced_widget.text_editor uses iced_core.widget.tree, so a change to iced_core.widget.tree can break iced_widget.text_editor, while a change to iced_widget.text_editor can't break iced_core.widget.tree.
Position
Below the diagonal: iced_widget.text_editor uses a module listed above it, which is the healthy direction.
iced_widget.text_editor uses iced_core.layout, so a change to iced_core.layout can break iced_widget.text_editor, while a change to iced_widget.text_editor can't break iced_core.layout.
Position
Below the diagonal: iced_widget.text_editor uses a module listed above it, which is the healthy direction.
iced_widget.text_editor uses iced_widget.combo_box, so a change to iced_widget.combo_box can break iced_widget.text_editor, while a change to iced_widget.text_editor can't break iced_widget.combo_box.
Position
Below the diagonal: iced_widget.text_editor uses a module listed above it, which is the healthy direction.
iced_widget.text_editor uses iced_widget.pane_grid, so a change to iced_widget.pane_grid can break iced_widget.text_editor, while a change to iced_widget.text_editor can't break iced_widget.pane_grid.
Position
Below the diagonal: iced_widget.text_editor uses a module listed above it, which is the healthy direction.
iced_widget.text_editor uses iced_widget.scrollable, so a change to iced_widget.scrollable can break iced_widget.text_editor, while a change to iced_widget.text_editor can't break iced_widget.scrollable.
Position
Below the diagonal: iced_widget.text_editor uses a module listed above it, which is the healthy direction.
iced_widget.text_editor uses iced_widget.button, so a change to iced_widget.button can break iced_widget.text_editor, while a change to iced_widget.text_editor can't break iced_widget.button.
Position
Below the diagonal: iced_widget.text_editor uses a module listed above it, which is the healthy direction.
iced_widget.text_editor uses iced_widget, so a change to iced_widget can break iced_widget.text_editor, while a change to iced_widget.text_editor can't break iced_widget.
Position
Below the diagonal: iced_widget.text_editor uses a module listed above it, which is the healthy direction.
iced_widget.text_editor uses iced_widget.column, so a change to iced_widget.column can break iced_widget.text_editor, while a change to iced_widget.text_editor can't break iced_widget.column.
Position
Below the diagonal: iced_widget.text_editor uses a module listed above it, which is the healthy direction.
iced_widget.text_input uses iced_beacon.client, so a change to iced_beacon.client can break iced_widget.text_input, while a change to iced_widget.text_input can't break iced_beacon.client.
Position
Below the diagonal: iced_widget.text_input uses a module listed above it, which is the healthy direction.
iced_widget.text_input uses iced_core.color, so a change to iced_core.color can break iced_widget.text_input, while a change to iced_widget.text_input can't break iced_core.color.
Position
Below the diagonal: iced_widget.text_input uses a module listed above it, which is the healthy direction.
iced_widget.text_input uses iced_core.font, so a change to iced_core.font can break iced_widget.text_input, while a change to iced_widget.text_input can't break iced_core.font.
Position
Below the diagonal: iced_widget.text_input uses a module listed above it, which is the healthy direction.
iced_widget.text_input uses iced_core.pixels, so a change to iced_core.pixels can break iced_widget.text_input, while a change to iced_widget.text_input can't break iced_core.pixels.
Position
Below the diagonal: iced_widget.text_input uses a module listed above it, which is the healthy direction.
iced_widget.text_input uses iced_core.length, so a change to iced_core.length can break iced_widget.text_input, while a change to iced_widget.text_input can't break iced_core.length.
Position
Below the diagonal: iced_widget.text_input uses a module listed above it, which is the healthy direction.
iced_widget.text_input uses iced_core.rectangle, so a change to iced_core.rectangle can break iced_widget.text_input, while a change to iced_widget.text_input can't break iced_core.rectangle.
Position
Below the diagonal: iced_widget.text_input uses a module listed above it, which is the healthy direction.
iced_widget.text_input uses iced_core.mouse.cursor, so a change to iced_core.mouse.cursor can break iced_widget.text_input, while a change to iced_widget.text_input can't break iced_core.mouse.cursor.
Position
Below the diagonal: iced_widget.text_input uses a module listed above it, which is the healthy direction.
iced_widget.text_input uses iced_core.size, so a change to iced_core.size can break iced_widget.text_input, while a change to iced_widget.text_input can't break iced_core.size.
Position
Below the diagonal: iced_widget.text_input uses a module listed above it, which is the healthy direction.
iced_widget.text_input uses iced_core.layout.limits, so a change to iced_core.layout.limits can break iced_widget.text_input, while a change to iced_widget.text_input can't break iced_core.layout.limits.
Position
Below the diagonal: iced_widget.text_input uses a module listed above it, which is the healthy direction.
iced_widget.text_input uses iced_core.image, so a change to iced_core.image can break iced_widget.text_input, while a change to iced_widget.text_input can't break iced_core.image.
Position
Below the diagonal: iced_widget.text_input uses a module listed above it, which is the healthy direction.
iced_widget.text_input uses iced_core.shell, so a change to iced_core.shell can break iced_widget.text_input, while a change to iced_widget.text_input can't break iced_core.shell.
Position
Below the diagonal: iced_widget.text_input uses a module listed above it, which is the healthy direction.
iced_widget.text_input uses iced_core.layout.flex, so a change to iced_core.layout.flex can break iced_widget.text_input, while a change to iced_widget.text_input can't break iced_core.layout.flex.
Position
Below the diagonal: iced_widget.text_input uses a module listed above it, which is the healthy direction.
iced_widget.text_input uses iced_core.text, so a change to iced_core.text can break iced_widget.text_input, while a change to iced_widget.text_input can't break iced_core.text.
Position
Below the diagonal: iced_widget.text_input uses a module listed above it, which is the healthy direction.
iced_widget.text_input uses iced_core.theme, so a change to iced_core.theme can break iced_widget.text_input, while a change to iced_widget.text_input can't break iced_core.theme.
Position
Below the diagonal: iced_widget.text_input uses a module listed above it, which is the healthy direction.
iced_widget.text_input uses iced_core.widget.tree, so a change to iced_core.widget.tree can break iced_widget.text_input, while a change to iced_widget.text_input can't break iced_core.widget.tree.
Position
Below the diagonal: iced_widget.text_input uses a module listed above it, which is the healthy direction.
iced_widget.text_input uses iced_core.layout, so a change to iced_core.layout can break iced_widget.text_input, while a change to iced_widget.text_input can't break iced_core.layout.
Position
Below the diagonal: iced_widget.text_input uses a module listed above it, which is the healthy direction.
iced_widget.text_input uses iced_widget.scrollable, so a change to iced_widget.scrollable can break iced_widget.text_input, while a change to iced_widget.text_input can't break iced_widget.scrollable.
Position
Below the diagonal: iced_widget.text_input uses a module listed above it, which is the healthy direction.
iced_widget.text_input uses iced_widget.button, so a change to iced_widget.button can break iced_widget.text_input, while a change to iced_widget.text_input can't break iced_widget.button.
Position
Below the diagonal: iced_widget.text_input uses a module listed above it, which is the healthy direction.
iced_widget.text_input uses iced_widget, so a change to iced_widget can break iced_widget.text_input, while a change to iced_widget.text_input can't break iced_widget.
Position
Below the diagonal: iced_widget.text_input uses a module listed above it, which is the healthy direction.
iced_widget.text_input uses iced_widget.column, so a change to iced_widget.column can break iced_widget.text_input, while a change to iced_widget.text_input can't break iced_widget.column.
Position
Below the diagonal: iced_widget.text_input uses a module listed above it, which is the healthy direction.
iced_widget.toggler uses iced_beacon.client, so a change to iced_beacon.client can break iced_widget.toggler, while a change to iced_widget.toggler can't break iced_beacon.client.
Position
Below the diagonal: iced_widget.toggler uses a module listed above it, which is the healthy direction.
iced_widget.toggler uses iced_core.color, so a change to iced_core.color can break iced_widget.toggler, while a change to iced_widget.toggler can't break iced_core.color.
Position
Below the diagonal: iced_widget.toggler uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in iced_widget.toggler uses a type in iced_core.font.
The types involved
iced_widget.toggler.Toggler → iced_core.font.Font
Direction
iced_widget.toggler uses iced_core.font, so a change to iced_core.font can break iced_widget.toggler, while a change to iced_widget.toggler can't break iced_core.font.
Position
Below the diagonal: iced_widget.toggler uses a module listed above it, which is the healthy direction.
iced_widget.toggler uses iced_core.pixels, so a change to iced_core.pixels can break iced_widget.toggler, while a change to iced_widget.toggler can't break iced_core.pixels.
Position
Below the diagonal: iced_widget.toggler uses a module listed above it, which is the healthy direction.
iced_widget.toggler uses iced_core.length, so a change to iced_core.length can break iced_widget.toggler, while a change to iced_widget.toggler can't break iced_core.length.
Position
Below the diagonal: iced_widget.toggler uses a module listed above it, which is the healthy direction.
iced_widget.toggler uses iced_core.rectangle, so a change to iced_core.rectangle can break iced_widget.toggler, while a change to iced_widget.toggler can't break iced_core.rectangle.
Position
Below the diagonal: iced_widget.toggler uses a module listed above it, which is the healthy direction.
iced_widget.toggler uses iced_core.mouse.cursor, so a change to iced_core.mouse.cursor can break iced_widget.toggler, while a change to iced_widget.toggler can't break iced_core.mouse.cursor.
Position
Below the diagonal: iced_widget.toggler uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in iced_widget.toggler uses a type in iced_core.size.
The types involved
iced_widget.toggler.Toggler → iced_core.size.Size
Direction
iced_widget.toggler uses iced_core.size, so a change to iced_core.size can break iced_widget.toggler, while a change to iced_widget.toggler can't break iced_core.size.
Position
Below the diagonal: iced_widget.toggler uses a module listed above it, which is the healthy direction.
iced_widget.toggler uses iced_core.layout.limits, so a change to iced_core.layout.limits can break iced_widget.toggler, while a change to iced_widget.toggler can't break iced_core.layout.limits.
Position
Below the diagonal: iced_widget.toggler uses a module listed above it, which is the healthy direction.
iced_widget.toggler uses iced_core.image, so a change to iced_core.image can break iced_widget.toggler, while a change to iced_widget.toggler can't break iced_core.image.
Position
Below the diagonal: iced_widget.toggler uses a module listed above it, which is the healthy direction.
iced_widget.toggler uses iced_core.shell, so a change to iced_core.shell can break iced_widget.toggler, while a change to iced_widget.toggler can't break iced_core.shell.
Position
Below the diagonal: iced_widget.toggler uses a module listed above it, which is the healthy direction.
iced_widget.toggler uses iced_core.layout.flex, so a change to iced_core.layout.flex can break iced_widget.toggler, while a change to iced_widget.toggler can't break iced_core.layout.flex.
Position
Below the diagonal: iced_widget.toggler uses a module listed above it, which is the healthy direction.
iced_widget.toggler uses iced_core.text, so a change to iced_core.text can break iced_widget.toggler, while a change to iced_widget.toggler can't break iced_core.text.
Position
Below the diagonal: iced_widget.toggler uses a module listed above it, which is the healthy direction.
iced_widget.toggler uses iced_core.theme, so a change to iced_core.theme can break iced_widget.toggler, while a change to iced_widget.toggler can't break iced_core.theme.
Position
Below the diagonal: iced_widget.toggler uses a module listed above it, which is the healthy direction.
iced_widget.toggler uses iced_core.widget.tree, so a change to iced_core.widget.tree can break iced_widget.toggler, while a change to iced_widget.toggler can't break iced_core.widget.tree.
Position
Below the diagonal: iced_widget.toggler uses a module listed above it, which is the healthy direction.
iced_widget.toggler uses iced_core.layout, so a change to iced_core.layout can break iced_widget.toggler, while a change to iced_widget.toggler can't break iced_core.layout.
Position
Below the diagonal: iced_widget.toggler uses a module listed above it, which is the healthy direction.
iced_widget.toggler uses iced_widget.scrollable, so a change to iced_widget.scrollable can break iced_widget.toggler, while a change to iced_widget.toggler can't break iced_widget.scrollable.
Position
Below the diagonal: iced_widget.toggler uses a module listed above it, which is the healthy direction.
iced_widget.toggler uses iced_widget.button, so a change to iced_widget.button can break iced_widget.toggler, while a change to iced_widget.toggler can't break iced_widget.button.
Position
Below the diagonal: iced_widget.toggler uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in iced_widget.toggler uses a type in iced_widget.
The types involved
iced_widget.toggler.Toggler → iced_widget.Widget
Direction
iced_widget.toggler uses iced_widget, so a change to iced_widget can break iced_widget.toggler, while a change to iced_widget.toggler can't break iced_widget.
Position
Below the diagonal: iced_widget.toggler uses a module listed above it, which is the healthy direction.
iced_widget.toggler uses iced_widget.column, so a change to iced_widget.column can break iced_widget.toggler, while a change to iced_widget.toggler can't break iced_widget.column.
Position
Below the diagonal: iced_widget.toggler uses a module listed above it, which is the healthy direction.
iced_widget.helpers uses iced_core.theme, so a change to iced_core.theme can break iced_widget.helpers, while a change to iced_widget.helpers can't break iced_core.theme.
Position
Below the diagonal: iced_widget.helpers uses a module listed above it, which is the healthy direction.
iced_widget.helpers uses iced_widget.combo_box, so a change to iced_widget.combo_box can break iced_widget.helpers, while a change to iced_widget.helpers can't break iced_widget.combo_box.
Position
Below the diagonal: iced_widget.helpers uses a module listed above it, which is the healthy direction.
iced_widget.helpers uses iced_widget.pane_grid, so a change to iced_widget.pane_grid can break iced_widget.helpers, while a change to iced_widget.helpers can't break iced_widget.pane_grid.
Position
Below the diagonal: iced_widget.helpers uses a module listed above it, which is the healthy direction.
iced_widget.helpers uses iced_widget.scrollable, so a change to iced_widget.scrollable can break iced_widget.helpers, while a change to iced_widget.helpers can't break iced_widget.scrollable.
Position
Below the diagonal: iced_widget.helpers uses a module listed above it, which is the healthy direction.
iced_widget.helpers uses iced_widget.button, so a change to iced_widget.button can break iced_widget.helpers, while a change to iced_widget.helpers can't break iced_widget.button.
Position
Below the diagonal: iced_widget.helpers uses a module listed above it, which is the healthy direction.
iced_widget.helpers uses iced_widget.column, so a change to iced_widget.column can break iced_widget.helpers, while a change to iced_widget.helpers can't break iced_widget.column.
Position
Below the diagonal: iced_widget.helpers uses a module listed above it, which is the healthy direction.
iced_widget.helpers uses iced_widget.container, so a change to iced_widget.container can break iced_widget.helpers, while a change to iced_widget.helpers can't break iced_widget.container.
Position
Below the diagonal: iced_widget.helpers uses a module listed above it, which is the healthy direction.
iced_widget.helpers uses iced_widget.pick_list, so a change to iced_widget.pick_list can break iced_widget.helpers, while a change to iced_widget.helpers can't break iced_widget.pick_list.
Position
Below the diagonal: iced_widget.helpers uses a module listed above it, which is the healthy direction.
iced_widget.helpers uses iced_widget.checkbox, so a change to iced_widget.checkbox can break iced_widget.helpers, while a change to iced_widget.helpers can't break iced_widget.checkbox.
Position
Below the diagonal: iced_widget.helpers uses a module listed above it, which is the healthy direction.
iced_widget.helpers uses iced_widget.text_editor, so a change to iced_widget.text_editor can break iced_widget.helpers, while a change to iced_widget.helpers can't break iced_widget.text_editor.
Position
Below the diagonal: iced_widget.helpers uses a module listed above it, which is the healthy direction.
iced_widget.helpers uses iced_widget.text_input, so a change to iced_widget.text_input can break iced_widget.helpers, while a change to iced_widget.helpers can't break iced_widget.text_input.
Position
Below the diagonal: iced_widget.helpers uses a module listed above it, which is the healthy direction.
iced_widget.helpers uses iced_widget.toggler, so a change to iced_widget.toggler can break iced_widget.helpers, while a change to iced_widget.helpers can't break iced_widget.toggler.
Position
Below the diagonal: iced_widget.helpers uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
34
High / Critical
A03:2025 — Software Supply Chain Failures
8
Medium
Roadmap
Top priorities: Resolve the 267 Low coverage finding(s) in Code Coverage — start with main.rs (54), lib.rs (14), text.rs (7); 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; Enable Dependabot/Renovate or a dependency-review gate.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 267 Low coverage finding(s) in Code Coverage — start with main.rs (54), lib.rs (14), text.rs (7).
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.
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
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.
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 — 35
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 — 735
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 — 15
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 14
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 43 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 43 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, 774 of 785 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.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (355 contributor(s) across 7288 commit(s) sampled, automation and bot accounts excluded). One of them holds 82% of the history; the other 354 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 Python, 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 Python, 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.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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.
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.
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 Python, 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.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
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.
36 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was iced_winit::run_action at 113. A further 9 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being iced_winit::conversion::key at 309 — they are counted neither in the figure above nor in this dimension's score. 2 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: core/src/keyboard/key.rs (Key::to_latin at 41), core/src/theme.rs (Theme::palette at 23). 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.
+ 21 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with iced_winit::run_action (cyclomatic 113), iced_winit::run_instance (cyclomatic 77), iced_widget::markdown::parse_with (cyclomatic 68). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 5.9 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.
+ 35 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 120 down to 120 or less in Cognitive Complexity — start with iced_winit::run_instance (cognitive 259), iced_winit::run_action (cognitive 186). — 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 Cognitive Complexity from 5.0 to about 5.8/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.2 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 21 MethodTooLong finding(s) in God Classes — start with scrollable.rs (3), lib.rs (3), editor.rs (2). — One of this dimension's main actionable groups (21 warning-level).
Resolve the 13 FileTooLong finding(s) in God Classes — start with lib.rs (3), editor.rs (2), scrollable.rs. — One of this dimension's main actionable groups (13 warning-level).
Resolve the 8 FunctionTooLong finding(s) in God Classes — start with conversion.rs (3), lib.rs (2), flex.rs. — One of this dimension's main actionable groups (8 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.
127 duplicated block group(s) detected. 7.6 % of the production lines (5,380 of 71,157) are in a reported copy. A further 80 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
Edited copy of a member (7 corresponding lines) · ×7wgpu/src/quad/gradient.rs:179
+ 95 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 12 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with application.rs (2), client.rs, focusable.rs. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 10 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with column.rs (2), client.rs, subscription.rs. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 10 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with gradient.rs (2), editor.rs (2), atlas.rs. — One of this dimension's main actionable groups (10 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.0 / 10Stronggated by 2 serious findings✓ 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.
18 production modules (Cargo), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 16 of the 18 (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).
Unstable project iced_test
Off the main sequence: iced_core
What to do
Resolve the 1 Unstable project iced_test finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Off the main sequence 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 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with mouse_area.rs, lazy.rs, border.rs. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D8 · Code Coverage4.3 / 10Weak✓ Tool-verified
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Line coverage 17.9% — 267 file(s) below 50%. Measured from the Rust suite (repository root: `cargo test --workspace` instrumented over 309 production file(s), 84 test binaries and 19 doc-test binaries).
Resolve the 267 Low coverage finding(s) in Code Coverage — start with main.rs (54), lib.rs (14), text.rs (7). — One of this dimension's main actionable groups (267 warning-level).
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
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.
6 outdated, 0 yanked direct Cargo dependencies. 66 of 88 direct crates were graded against crates.io (0 not published there, 22 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
Outdated: jiff · ×6
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 629 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 4 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. This repository publishes itself under MIT, which is its own choice and is not judged here.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 15 Hotspot finding(s) in Churn × Complexity Hotspots — start with markdown.rs, scrollable.rs, lib.rs. — One of this dimension's main actionable groups (15 warning-level).
Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with limits.rs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
69 deducted task-comment markers across 71157 LoC (0.1/KLoC) → score 9.8. 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 · ×65winit/src/clipboard.rs:154
HackComment · ×2winit/src/lib.rs:584
FixmeComment · ×2widget/src/slider.rs:511
What to do
Resolve the 65 TodoComment finding(s) in Explicit Debt — start with lib.rs (11), emulator.rs (11), text.rs (10). — One of this dimension's main actionable groups (65 warning-level).
Resolve the 2 HackComment finding(s) in Explicit Debt — start with lib.rs, highlighter.rs. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 FixmeComment finding(s) in Explicit Debt — start with slider.rs, vertical_slider.rs. — 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.
2 of 17 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).
34 finding(s): 0 critical, 33 high, 1 medium, 0 low. 29 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 2 file(s) — `examples/gallery/src/civitai.rs` (line 70), `runtime/src/task.rs` (line 510) — 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
REDACTED
REDACTED
REDACTED
What to do
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 29 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 (29 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 8 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (8). — One of this dimension's main actionable groups (8 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 185 of the 282 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with damage.rs. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 3 Change coupling finding(s) in Change Coupling — start with cache.rs (2), paragraph.rs. — One of this dimension's main actionable groups (3 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 Sourcing — Whether the recovery-replay fold is deterministic — state derived purely from each event's own fields, no clock/random/IO on the replay path.
Method: Roslyn syntax scan (event-sourcing gated): Apply/When folds checked for forbidden tokens (DateTime.Now, Guid.NewGuid, Random, IO), stripped of comments/strings. Deterministic, hard fact per fold.
Other · Event Sourcing — Whether domain events stay immutable (private fields, set once) rather than carrying mutable state.
Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
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✓ Tool-verified
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
1 public type in `iced_debug.internal` is marked as implementation by its own namespace, folder or name: `Span` (debug/src/lib.rs:309, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — debug/src/lib.rs:309
What to do
Hide `iced_debug.internal` (`Span`) (Rust: `pub(crate)`, or keep the module private): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Do you agree with this assessment?
P2 · Observability6.8 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 11/12 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download 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.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`run_instance` is async and calls block_on — a blocking call inside async code stalls the executor thread, and every task scheduled on it for as long as it runs. — winit/src/lib.rs:466
What to do
Rust: `.await` the future instead of `block_on` (on a Tokio runtime thread it panics outright) and use `tokio::time::sleep(..).await` instead of `std::thread::sleep`; where synchronous code must run, move it to `tokio::task::spawn_blocking` or `block_in_place`.
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.
This runs a future to completion from inside an `async` body, which is already being polled by an executor. tokio's `Runtime::block_on` and `Handle::block_on` panic ("Cannot start a runtime from within a runtime"), and `futures::executor::block_on` parks the worker thread on a future that may need that very thread to make progress — a deadlock. The future can simply be awaited here: `fut.await`. Where a synchronous function in between forces the bridge, make that function `async` too, or run the bridge off the executor with `tokio::task::spawn_blocking(move || handle.block_on(fut)).await`. — winit/src/lib.rs:601
What to do
`block_on` inside an `async` body
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `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 — 7 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 — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 71 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No 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 — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
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 — ~19863 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.
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
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 member alignment 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. 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 .py, .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
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 51 value object(s); 13 domain event(s); its domain events are published by services or handlers — no domain entity raises one
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Python, 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 data present for 309 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
S1 Web-Security Posture — No web surface: 284 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
X12 Unreachable branch — X12 reached only 0% of this repository's production lines — rust (71,102 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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
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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — no C# was loaded; this repository's Python and Rust were read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X27 Collection changed while being enumerated — 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: damage.rs ↔ layer.rs graphics/src/damage.rs:1— `graphics/src/damage.rs` (context graphics) and `wgpu/src/layer.rs` (context wgpu) sit in DIFFERENT parts of the tree yet change together 50% of the time (6 of the 12 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 `5467c19c` Replace `Primitive::Translate` with `Transform`; `b7b457a5` Make `shadow` optional in `renderer::Quad`; `603832e6` Introduce `RawText` to `Primitive` in `iced_graphics` — run `git show` on any of them.
X1 · Async correctness· `block_on` inside an `async` body · ×1
`block_on` inside an `async` body winit/src/lib.rs:601— This runs a future to completion from inside an `async` body, which is already being polled by an executor. tokio's `Runtime::block_on` and `Handle::block_on` panic ("Cannot start a runtime from within a runtime"), and `futures::executor::block_on` parks the worker thread on a future that may need that very thread to make progress — a deadlock. The future can simply be awaited here: `fut.await`. Where a synchronous function in between forces the bridge, make that function `async` too, or run the bridge off the executor with `tokio::task::spawn_blocking(move || handle.block_on(fut)).await`.
TodoComment winit/src/clipboard.rs:154— // TODO: Wasm 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 winit/src/conversion.rs:214— // TODO: Fix inconsistent API on Wasm — 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 winit/src/conversion.rs:230— // TODO: Fix inconsistent API on Wasm — 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 winit/src/lib.rs:216— // TODO: Remove when unnecessary — 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 winit/src/lib.rs:586— // TODO: Send compositor through proxy (?) — 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 winit/src/lib.rs:1720— // TODO: Shared image cache in compositor — 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 widget/src/pane_grid.rs:944— // TODO: Mouse translation — 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 wgpu/src/engine.rs:30— // TODO: Initialize AA pipelines lazily — 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 wgpu/src/lib.rs:88— // TODO: Centralize all the image feature handling — 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 wgpu/src/lib.rs:113— // TODO: Resize belt smartly (?) — 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 wgpu/src/lib.rs:149— // TODO: Provide window id (?) — 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 wgpu/src/image/cache.rs:186— // TODO: Concurrency — 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 wgpu/src/image/cache.rs:262— // TODO: Concurrency — 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 wgpu/src/image/cache.rs:279— // TODO: Concurrency — 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 tiny_skia/src/lib.rs:218— // TODO: Concurrency — 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 wgpu/src/image/cache.rs:225— // TODO: Concurrent Wasm 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 wgpu/src/image/cache.rs:365— // TODO: Concurrent support for Wasm — 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 wgpu/src/image/vector.rs:56— // TODO: Reuse `cosmic-text` font database — 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 tiny_skia/src/vector.rs:92— // TODO: Reuse `cosmic-text` font database — 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 wgpu/src/image/vector.rs:109— // TODO: Optimize! — 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 wgpu/src/image/vector.rs:122— // TODO: Optimize! — 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 tiny_skia/src/engine.rs:532— // TODO: Border 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.
TodoComment tiny_skia/src/geometry.rs:198— // TODO: Honor layering! — 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 tiny_skia/src/lib.rs:44— // TODO: Shared engine — 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 tiny_skia/src/text.rs:28— // TODO: Shared engine — 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.
MethodTooLong: State.update core/src/text/editor.rs:330— MethodTooLong — update runs 187 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 87 over it, 1.87× 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: UserInterface.update runtime/src/user_interface.rs:198— MethodTooLong — update runs 184 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 84 over it, 1.84× 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: State.interact widget/src/scrollable.rs:2593— MethodTooLong — interact runs 184 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 84 over it, 1.84× 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: Engine.draw_quad tiny_skia/src/engine.rs:28— MethodTooLong — draw_quad runs 183 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 83 over it, 1.83× 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: Renderer.render wgpu/src/lib.rs:395— MethodTooLong — render runs 175 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 75 over it, 1.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Editor.perform graphics/src/text/editor.rs:261— MethodTooLong — perform runs 174 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 74 over it, 1.74× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PaneGrid.update widget/src/pane_grid.rs:462— MethodTooLong — update runs 149 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 49 over it, 1.49× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Table.layout widget/src/table.rs:218— MethodTooLong — layout runs 144 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 44 over it, 1.44× 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: Content.push_str widget/src/markdown.rs:153— MethodTooLong — push_str runs 134 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Tester.controls tester/src/lib.rs:624— MethodTooLong — controls 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: Tester.update tester/src/lib.rs:205— MethodTooLong — update runs 119 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Engine.draw_text tiny_skia/src/engine.rs:285— MethodTooLong — draw_text 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.
MethodTooLong: PaneGrid.draw widget/src/pane_grid.rs:716— MethodTooLong — draw 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.
MethodTooLong: Compositor.request wgpu/src/window/compositor.rs:50— MethodTooLong — request runs 115 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Input.update core/src/text/input.rs:132— MethodTooLong — update runs 112 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 12 over it, 1.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Slider.update widget/src/slider.rs:245— MethodTooLong — update runs 110 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 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: VerticalSlider.update widget/src/vertical_slider.rs:245— MethodTooLong — update runs 110 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 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: State.update widget/src/scrollable.rs:2915— MethodTooLong — update runs 107 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ComboBox.update widget/src/combo_box.rs:470— MethodTooLong — update 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: Scrollbars.new widget/src/scrollable.rs:3160— MethodTooLong — new runs 103 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Pipeline.new wgpu/src/image/mod.rs:38— MethodTooLong — new 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.
Hotspot: widget/src/markdown.rs widget/src/markdown.rs:1075— widget/src/markdown.rs changed 47 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 68 in iced_widget::markdown::parse_with at line 1075. 11 of those changes were fix/bug commits, and the other 36 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 13:16:37 +01:00' --until='2026-11-13 13:16:37 +01:00' --full-history --no-merges -- widget/src/markdown.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: widget/src/scrollable.rs widget/src/scrollable.rs:2593— widget/src/scrollable.rs changed 51 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 46 in State::interact at line 2593. 2 of those changes were fix/bug commits, and the other 49 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 13:16:37 +01:00' --until='2026-11-13 13:16:37 +01:00' --full-history --no-merges -- widget/src/scrollable.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: winit/src/lib.rs winit/src/lib.rs:1288— winit/src/lib.rs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 113 in iced_winit::run_action at line 1288. 1 of those changes was a fix/bug commit, and the other 13 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 13:16:37 +01:00' --until='2026-11-13 13:16:37 +01:00' --full-history --no-merges -- winit/src/lib.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: runtime/src/user_interface.rs runtime/src/user_interface.rs:198— runtime/src/user_interface.rs changed 22 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in UserInterface::update at line 198. 5 of those changes were fix/bug commits, and the other 17 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 13:16:37 +01:00' --until='2026-11-13 13:16:37 +01:00' --full-history --no-merges -- runtime/src/user_interface.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: core/src/text/editor.rs core/src/text/editor.rs:330— core/src/text/editor.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 53 in State::update at line 330. 2 of those changes were fix/bug commits, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 13:16:37 +01:00' --until='2026-11-13 13:16:37 +01:00' --full-history --no-merges -- core/src/text/editor.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: core/src/layout/flex.rs core/src/layout/flex.rs:94— core/src/layout/flex.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 56 in iced_core::layout::flex::resolve at line 94. 1 of those changes was a fix/bug commit, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 13:16:37 +01:00' --until='2026-11-13 13:16:37 +01:00' --full-history --no-merges -- core/src/layout/flex.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: widget/src/text_editor.rs widget/src/text_editor.rs:386— widget/src/text_editor.rs changed 24 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in TextEditor::update at line 386. 2 of those changes were fix/bug commits, and the other 22 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 13:16:37 +01:00' --until='2026-11-13 13:16:37 +01:00' --full-history --no-merges -- widget/src/text_editor.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: widget/src/pane_grid.rs widget/src/pane_grid.rs:462— widget/src/pane_grid.rs changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in PaneGrid::update at line 462. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 13:16:37 +01:00' --until='2026-11-13 13:16:37 +01:00' --full-history --no-merges -- widget/src/pane_grid.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: widget/src/text/rich.rs widget/src/text/rich.rs:263— widget/src/text/rich.rs changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in Rich::draw at line 263. 2 of those changes were fix/bug commits, and the other 17 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 13:16:37 +01:00' --until='2026-11-13 13:16:37 +01:00' --full-history --no-merges -- widget/src/text/rich.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: widget/src/table.rs widget/src/table.rs:218— widget/src/table.rs changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in Table::layout at line 218. 1 of those changes was a fix/bug commit, and the other 14 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 13:16:37 +01:00' --until='2026-11-13 13:16:37 +01:00' --full-history --no-merges -- widget/src/table.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: widget/src/mouse_area.rs widget/src/mouse_area.rs:283— widget/src/mouse_area.rs changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in iced_widget::mouse_area::update at line 283. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 13:16:37 +01:00' --until='2026-11-13 13:16:37 +01:00' --full-history --no-merges -- widget/src/mouse_area.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: widget/src/vertical_slider.rs widget/src/vertical_slider.rs:245— widget/src/vertical_slider.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in VerticalSlider::update at line 245. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 13:16:37 +01:00' --until='2026-11-13 13:16:37 +01:00' --full-history --no-merges -- widget/src/vertical_slider.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: widget/src/sensor.rs widget/src/sensor.rs:163— widget/src/sensor.rs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in Sensor::update at line 163. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 13:16:37 +01:00' --until='2026-11-13 13:16:37 +01:00' --full-history --no-merges -- widget/src/sensor.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: widget/src/slider.rs widget/src/slider.rs:245— widget/src/slider.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in Slider::update at line 245. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 13:16:37 +01:00' --until='2026-11-13 13:16:37 +01:00' --full-history --no-merges -- widget/src/slider.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: wgpu/src/image/mod.rs wgpu/src/image/mod.rs:203— wgpu/src/image/mod.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in State::prepare at line 203. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 13:16:37 +01:00' --until='2026-11-13 13:16:37 +01:00' --full-history --no-merges -- wgpu/src/image/mod.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
FileTooLong: src/scrollable.rs widget/src/scrollable.rs— FileTooLong — 1983 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 1483 over it, 3.97× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/markdown.rs widget/src/markdown.rs— FileTooLong — 1354 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 854 over it, 2.71× 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 winit/src/lib.rs— FileTooLong — 1264 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 764 over it, 2.53× 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/conversion.rs winit/src/conversion.rs— FileTooLong — 882 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 382 over it, 1.76× 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/pane_grid.rs widget/src/pane_grid.rs— FileTooLong — 767 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 67% of them inside a single declaration: PaneGrid (4 blocks, 148-927). The bar is 500 significant lines; this is 267 over it, 1.53× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: text/editor.rs graphics/src/text/editor.rs— FileTooLong — 628 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 78% of them inside a single declaration: Editor (3 blocks, 31-850). The bar is 500 significant lines; this is 128 over it, 1.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: src/lib.rs wgpu/src/lib.rs— FileTooLong — 624 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: Renderer (12 blocks, 73-966). The bar is 500 significant lines; this is 124 over it, 1.25× 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 tester/src/lib.rs— FileTooLong — 621 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 71% of them inside a single declaration: Tester (2 blocks, 108-792). The bar is 500 significant lines; this is 121 over it, 1.24× 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/triangle.rs wgpu/src/triangle.rs— FileTooLong — 615 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 115 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: text/editor.rs core/src/text/editor.rs— FileTooLong — 612 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 112 over it, 1.22× 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/engine.rs tiny_skia/src/engine.rs— FileTooLong — 560 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 77% of them inside a single declaration: Engine (2 blocks, 8-604). The bar is 500 significant lines; this is 60 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: src/pick_list.rs widget/src/pick_list.rs— FileTooLong — 540 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 80% of them inside a single declaration: PickList (4 blocks, 146-766). The bar is 500 significant lines; this is 40 over it, 1.08× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/application.rs src/application.rs— FileTooLong — 526 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 26 over it, 1.05× 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.
Duplicated block (10 lines × 2) beacon/src/client.rs:252— beacon/src/client.rs:252-261 | beacon/src/lib.rs:286-295 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) core/src/widget/operation/focusable.rs:125— core/src/widget/operation/focusable.rs:125-134 | core/src/widget/operation/focusable.rs:157-166 — 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 `core/src/widget/operation/focusable.rs:125` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) core/src/widget/operation/text.rs:101— core/src/widget/operation/text.rs:101-110 | core/src/widget/operation/text.rs:123-132 — 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 `core/src/widget/operation/text.rs:101` 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/application.rs:113— src/application.rs:113-122 | src/daemon.rs:57-66 — before extracting anything, compare `src/application.rs` and `src/daemon.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 56 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/application.rs:113` 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/application.rs:128— src/application.rs:128-137 | src/daemon.rs:80-89 — before extracting anything, compare `src/application.rs` and `src/daemon.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 56 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/application.rs:128` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 2) wgpu/src/color.rs:80— wgpu/src/color.rs:80-89 | wgpu/src/triangle/msaa.rs:51-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `wgpu/src/color.rs:80` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) widget/src/component.rs:258— widget/src/component.rs:258-267 | widget/src/component.rs:474-483 — 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 `widget/src/component.rs:258` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) widget/src/markdown.rs:1258— widget/src/markdown.rs:1258-1267 | widget/src/markdown.rs:1286-1295 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) widget/src/sensor.rs:191— widget/src/sensor.rs:191-200 | widget/src/sensor.rs:203-212 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) widget/src/text_editor.rs:797— widget/src/text_editor.rs:797-806 | widget/src/text_input.rs:581-590 — 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 `widget/src/text_editor.rs:797` 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) core/src/gradient.rs:67— core/src/gradient.rs:67-76 | graphics/src/gradient.rs:66-75 — 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 `core/src/gradient.rs:67` 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) widget/src/popover.rs:516— widget/src/popover.rs:516-525 | widget/src/sticky.rs:420-429 — 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 `widget/src/popover.rs:516` 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) beacon/src/client.rs:238— beacon/src/client.rs:238-246 | beacon/src/lib.rs:301-309 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) futures/src/subscription.rs:322— futures/src/subscription.rs:322-330 | futures/src/subscription.rs:378-386 — 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 `futures/src/subscription.rs:322` 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) selector/src/target.rs:50— selector/src/target.rs:50-58 | selector/src/target.rs:62-70 — 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 (9 lines × 2) src/application.rs:117— src/application.rs:117-125 | src/application/timed.rs:59-67 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) widget/src/column.rs:181— widget/src/column.rs:181-189 | widget/src/keyed/column.rs:214-222 — before extracting anything, compare `widget/src/column.rs` and `widget/src/keyed/column.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 37 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 `widget/src/column.rs:181` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) widget/src/column.rs:380— widget/src/column.rs:380-388 | widget/src/row.rs:385-393 — before extracting anything, compare `widget/src/column.rs` and `widget/src/row.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 65 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 `widget/src/column.rs:380` 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) widget/src/image.rs:278— widget/src/image.rs:278-286 | widget/src/svg.rs:243-251 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) widget/src/slider.rs:426— widget/src/slider.rs:426-434 | widget/src/vertical_slider.rs:423-431 — before extracting anything, compare `widget/src/slider.rs` and `widget/src/vertical_slider.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 178 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 `widget/src/slider.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 (9 lines × 2) tiny_skia/src/layer.rs:170— tiny_skia/src/layer.rs:170-178 | wgpu/src/layer.rs:179-187 — before extracting anything, compare `tiny_skia/src/layer.rs` and `wgpu/src/layer.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `tiny_skia/src/layer.rs:170` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) wgpu/src/triangle.rs:688— wgpu/src/triangle.rs:688-696 | wgpu/src/triangle.rs:820-828 — 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 `wgpu/src/triangle.rs:688` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) wgpu/src/image/atlas.rs:385— wgpu/src/image/atlas.rs:385-390 | wgpu/src/image/atlas.rs:395-402 — 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 `wgpu/src/image/atlas.rs:395` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 2) wgpu/src/quad/gradient.rs:182— wgpu/src/quad/gradient.rs:182-187 | wgpu/src/quad/solid.rs:153-158 — before extracting anything, compare `wgpu/src/quad/gradient.rs` and `wgpu/src/quad/solid.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) widget/src/button.rs:231— widget/src/button.rs:231-236 | widget/src/container.rs:211-216 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) widget/src/table.rs:244— widget/src/table.rs:244-249 | widget/src/table.rs:320-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 `widget/src/table.rs:244` 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) core/src/text/editor.rs:85— core/src/text/editor.rs:85-90 | widget/src/text_editor.rs:677-682 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) graphics/src/text/editor.rs:908— graphics/src/text/editor.rs:908-913 | graphics/src/text/paragraph.rs:654-659 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) tiny_skia/src/geometry.rs:218— tiny_skia/src/geometry.rs:218-223 | wgpu/src/geometry.rs:265-270 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) wgpu/src/quad/gradient.rs:52— wgpu/src/quad/gradient.rs:52-57 | wgpu/src/quad/solid.rs:46-51 — before extracting anything, compare `wgpu/src/quad/gradient.rs` and `wgpu/src/quad/solid.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 62 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 `wgpu/src/quad/gradient.rs:52` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) widget/src/canvas.rs:270— widget/src/canvas.rs:270-275 | widget/src/shader.rs:119-124 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `widget/src/canvas.rs:270` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) widget/src/opaque.rs:147— widget/src/opaque.rs:147-152 | widget/src/responsive.rs:104-109 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `widget/src/opaque.rs:147` 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.
FunctionTooLong: iced_winit::run_instance winit/src/lib.rs:466— FunctionTooLong — iced_winit::run_instance runs 500 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 400 over it, 5.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.
FunctionTooLong: iced_winit::conversion::key winit/src/conversion.rs:544— FunctionTooLong — iced_winit::conversion::key runs 314 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 214 over it, 3.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: iced_core::layout::flex::resolve core/src/layout/flex.rs:94— FunctionTooLong — iced_core::layout::flex::resolve 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.
FunctionTooLong: iced_winit::run winit/src/lib.rs:70— FunctionTooLong — iced_winit::run runs 231 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 131 over it, 2.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: iced_winit::conversion::key_code winit/src/conversion.rs:884— FunctionTooLong — iced_winit::conversion::key_code runs 198 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 98 over it, 1.98× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: iced_wgpu::text::prepare wgpu/src/text.rs:433— FunctionTooLong — iced_wgpu::text::prepare runs 164 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 64 over it, 1.64× 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: iced_wgpu::color::convert wgpu/src/color.rs:5— FunctionTooLong — iced_wgpu::color::convert runs 134 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: iced_winit::conversion::window_event winit/src/conversion.rs:149— FunctionTooLong — iced_winit::conversion::window_event runs 108 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
ClassTooLong: State widget/src/scrollable.rs:1227— 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), 29 methods, 4 blocks, lines 1227-3134. 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: Renderer wgpu/src/lib.rs:73— ClassTooLong — 584 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 8 methods, 12 blocks, lines 73-966. The bar is 400 significant lines; this is 184 over it, 1.46× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: PaneGrid widget/src/pane_grid.rs:148— ClassTooLong — 516 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, 4 blocks, lines 148-927. The bar is 400 significant lines; this is 116 over it, 1.29× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Editor graphics/src/text/editor.rs:16— ClassTooLong — 488 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 5 methods, 3 blocks, lines 31-850. The bar is 400 significant lines; this is 88 over it, 1.22× 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: Scrollable widget/src/scrollable.rs:83— ClassTooLong — 476 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 21 methods, 3 blocks, lines 83-1014. The bar is 400 significant lines; this is 76 over it, 1.19× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Tester tester/src/lib.rs:108— ClassTooLong — 439 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 9 methods, 2 blocks, lines 108-792. The bar is 400 significant lines; this is 39 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: PickList widget/src/pick_list.rs:146— 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), 18 methods, 4 blocks, lines 146-766. 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: Engine tiny_skia/src/engine.rs:8— 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), 6 methods, 2 blocks, lines 8-604. 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.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×8
Duplicated block (11 lines × 2) core/src/color.rs:335— core/src/color.rs:335-345 | core/src/color.rs:346-356 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) src/application.rs:765— src/application.rs:765-775 | src/application.rs:848-858 — 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 `state` to `&Self::State` in one and `&mut Self::State` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/application.rs:761` calls `theme` and `src/application.rs:845` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 2) tiny_skia/src/engine.rs:213— tiny_skia/src/engine.rs:213-223 | tiny_skia/src/engine.rs:256-266 — 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 `tiny_skia/src/engine.rs:213` 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) wgpu/src/geometry.rs:177— wgpu/src/geometry.rs:177-187 | wgpu/src/geometry.rs:238-248 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) wgpu/src/image/atlas.rs:68— wgpu/src/image/atlas.rs:68-78 | wgpu/src/image/atlas.rs:469-479 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `wgpu/src/image/atlas.rs:68` 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) widget/src/overlay/menu.rs:448— widget/src/overlay/menu.rs:448-458 | widget/src/overlay/menu.rs:477-487 — 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 (11 lines × 2) widget/src/slider.rs:459— widget/src/slider.rs:459-469 | widget/src/slider.rs:473-483 — 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 `widget/src/slider.rs:459` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11 lines × 2) widget/src/column.rs:64— widget/src/column.rs:64-74 | widget/src/row.rs:70-80 — before extracting anything, compare `widget/src/column.rs` and `widget/src/row.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 65 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.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×7
Edited copy of a member (7 corresponding lines) wgpu/src/quad/gradient.rs:179— wgpu/src/quad/gradient.rs:179-188 | wgpu/src/quad/solid.rs:152-158 — 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) widget/src/button.rs:230— widget/src/button.rs:230-236 | widget/src/container.rs:210-216 — 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) widget/src/checkbox.rs:376— widget/src/checkbox.rs:376-382 | widget/src/toggler.rs:366-376 — 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/application.rs:454— src/application.rs:454-461 | src/daemon.rs:276-282 — 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/application.rs:400— src/application.rs:400-407 | src/daemon.rs:220-226 — 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/application.rs:426— src/application.rs:426-433 | src/daemon.rs:247-253 — 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) wgpu/src/quad.rs:313— wgpu/src/quad.rs:313-319 | wgpu/src/triangle.rs:555-561 — 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.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×7
Edited copy of a member (4 corresponding lines) tiny_skia/src/lib.rs:206— tiny_skia/src/lib.rs:206-209 | wgpu/src/lib.rs:681-684 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) tiny_skia/src/lib.rs:274— tiny_skia/src/lib.rs:274-277 | wgpu/src/lib.rs:755-758 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) tiny_skia/src/lib.rs:285— tiny_skia/src/lib.rs:285-288 | wgpu/src/lib.rs:766-769 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) tiny_skia/src/lib.rs:363— tiny_skia/src/lib.rs:363-366 | wgpu/src/lib.rs:796-799 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) tiny_skia/src/lib.rs:375— tiny_skia/src/lib.rs:375-378 | wgpu/src/lib.rs:808-811 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) widget/src/combo_box.rs:297— widget/src/combo_box.rs:297-300 | widget/src/pick_list.rs:301-304 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) widget/src/pane_grid/content.rs:57— widget/src/pane_grid/content.rs:57-60 | widget/src/pane_grid/title_bar.rs:74-77 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (17 lines × 2) tiny_skia/src/layer.rs:127— tiny_skia/src/layer.rs:127-143 | wgpu/src/layer.rs:136-152 — before extracting anything, compare `tiny_skia/src/layer.rs` and `wgpu/src/layer.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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) tiny_skia/src/text.rs:48— tiny_skia/src/text.rs:48-64 | tiny_skia/src/text.rs:75-91 — 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) tiny_skia/src/vector.rs:93— tiny_skia/src/vector.rs:93-109 | wgpu/src/image/vector.rs:57-73 — 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 (17 lines × 2) widget/src/column.rs:282— widget/src/column.rs:282-298 | widget/src/row.rs:288-304 — before extracting anything, compare `widget/src/column.rs` and `widget/src/row.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 2) widget/src/pane_grid.rs:531— widget/src/pane_grid.rs:531-547 | widget/src/pane_grid.rs:549-565 — 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 `widget/src/pane_grid.rs:531` 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 (17 lines × 2) wgpu/src/triangle.rs:640— wgpu/src/triangle.rs:640-656 | wgpu/src/triangle.rs:772-788 — 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 `wgpu/src/triangle.rs:640` 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) graphics/src/text/editor.rs:321— graphics/src/text/editor.rs:321-332 | graphics/src/text/editor.rs:525-536 — 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 `graphics/src/text/editor.rs:321` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) wgpu/src/color.rs:170— wgpu/src/color.rs:170-182 | wgpu/src/triangle/msaa.rs:318-329 — 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 `wgpu/src/color.rs:170` 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) widget/src/slider.rs:436— widget/src/slider.rs:436-447 | widget/src/vertical_slider.rs:433-444 — before extracting anything, compare `widget/src/slider.rs` and `widget/src/vertical_slider.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 178 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 `widget/src/slider.rs:436` 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) widget/src/text_editor.rs:816— widget/src/text_editor.rs:816-827 | widget/src/text_input.rs:600-611 — 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 `widget/src/text_editor.rs:816` 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) winit/src/clipboard.rs:53— winit/src/clipboard.rs:53-64 | winit/src/clipboard.rs:100-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. Read the line range as the matched WINDOW rather than a finished unit: at `winit/src/clipboard.rs:53` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `callback` to `impl FnOnce(Result<Content, Error>) + Send + 'static` in one and `impl FnOnce(Result<(), Error>) + Send + '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 (12 lines × 2) tiny_skia/src/layer.rs:151— tiny_skia/src/layer.rs:151-162 | wgpu/src/layer.rs:160-171 — before extracting anything, compare `tiny_skia/src/layer.rs` and `wgpu/src/layer.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `tiny_skia/src/layer.rs:151` 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.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×5
Edited copy of a member (14 corresponding lines) futures/src/backend/native/smol.rs:49— futures/src/backend/native/smol.rs:49-62 | futures/src/backend/native/tokio.rs:63-76 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) wgpu/src/triangle.rs:662— wgpu/src/triangle.rs:662-675 | wgpu/src/triangle.rs:794-807 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) highlighter/src/lib.rs:33— highlighter/src/lib.rs:33-46 | highlighter/src/lib.rs:164-178 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) selector/src/find.rs:151— selector/src/find.rs:151-165 | selector/src/find.rs:225-238 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) widget/src/button.rs:245— widget/src/button.rs:245-258 | widget/src/container.rs:225-239 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (13 lines × 2) core/src/length.rs:132— core/src/length.rs:132-144 | core/src/length.rs:159-171 — 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 `core/src/length.rs:132` 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) widget/src/button.rs:377— widget/src/button.rs:377-389 | widget/src/container.rs:381-393 — 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 (13 lines × 2) widget/src/canvas.rs:234— widget/src/canvas.rs:234-246 | widget/src/shader.rs:97-109 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `widget/src/canvas.rs:232` calls `Window`, `RedrawRequested` and `widget/src/shader.rs:95` 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) widget/src/slider.rs:333— widget/src/slider.rs:333-345 | widget/src/vertical_slider.rs:333-345 — before extracting anything, compare `widget/src/slider.rs` and `widget/src/vertical_slider.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 178 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 `widget/src/slider.rs:333` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) widget/src/slider.rs:401— widget/src/slider.rs:401-413 | widget/src/vertical_slider.rs:398-410 — before extracting anything, compare `widget/src/slider.rs` and `widget/src/vertical_slider.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 178 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `widget/src/slider.rs:399` calls `update` and `widget/src/vertical_slider.rs:396` 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/application.rs:715— src/application.rs:715-721 | src/application.rs:798-804 — 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) widget/src/slider.rs:348— widget/src/slider.rs:348-354 | widget/src/vertical_slider.rs:348-354 — before extracting anything, compare `widget/src/slider.rs` and `widget/src/vertical_slider.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 178 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 `widget/src/slider.rs:348` 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 (7 lines × 2) widget/src/slider.rs:357— widget/src/slider.rs:357-363 | widget/src/vertical_slider.rs:357-363 — before extracting anything, compare `widget/src/slider.rs` and `widget/src/vertical_slider.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 178 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 `widget/src/slider.rs:357` 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 (7 lines × 2) widget/src/popover.rs:303— widget/src/popover.rs:303-309 | widget/src/tooltip.rs:366-372 — 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 `widget/src/popover.rs:303` 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) widget/src/combo_box.rs:636— widget/src/combo_box.rs:636-642 | widget/src/radio.rs:367-373 — 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 `widget/src/combo_box.rs:636` 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.
iced_winit::run_action (cyclomatic 113) winit/src/lib.rs:1288— iced_winit::run_action has cyclomatic complexity 113 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: winit/src/lib.rs holds 3 of the 36 functions over the threshold — including the worst — and 163 of the 548 points over it (30%), 2.5× the next-largest file (widget/src/markdown.rs at 66). 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.
iced_winit::run_instance (cyclomatic 77) winit/src/lib.rs:466— iced_winit::run_instance has cyclomatic complexity 77 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: winit/src/lib.rs holds 3 of the 36 functions over the threshold — including the worst — and 163 of the 548 points over it (30%), 2.5× the next-largest file (widget/src/markdown.rs at 66). 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.
iced_winit::conversion::window_event (cyclomatic 29) winit/src/conversion.rs:149— iced_winit::conversion::window_event has cyclomatic complexity 29 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This is NOT this file's highest cyclomatic complexity: iced_winit::conversion::key (cyclomatic 309) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
iced_winit::run (cyclomatic 18) winit/src/lib.rs:70— iced_winit::run has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This file is where this pass's cyclomatic complexity CONCENTRATES: winit/src/lib.rs holds 3 of the 36 functions over the threshold — including the worst — and 163 of the 548 points over it (30%), 2.5× the next-largest file (widget/src/markdown.rs at 66). 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.
State::interact (cyclomatic 46) widget/src/scrollable.rs:2593— State::interact has cyclomatic complexity 46 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
State::update (cyclomatic 34) widget/src/scrollable.rs:2915— State::update 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.
State::update (cyclomatic 32) core/src/text/editor.rs:330— State::update has cyclomatic complexity 32 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
State::prepare (cyclomatic 18) wgpu/src/image/mod.rs:203— State::prepare has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
iced_winit::run_instance (cognitive 259) winit/src/lib.rs:466— iced_winit::run_instance has cognitive complexity 259 (threshold 15). Drivers by points: if/else 40 (157 pts), loops 12 (53 pts), match/switch 10 (41 pts), boolean chains 8 (nesting depth added 189). To reduce it, split the body into named stages: move each independent 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: winit/src/lib.rs holds 4 of the 63 functions over the threshold — including the worst — and 434 of the 1495 points over it (29%), 2.8× the next-largest file (widget/src/scrollable.rs at 157). 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.
iced_winit::run_action (cognitive 186) winit/src/lib.rs:1288— iced_winit::run_action has cognitive complexity 186 (threshold 15). Drivers by points: if/else 47 (141 pts), loops 9 (23 pts), match/switch 9 (20 pts), boolean chains 2 (nesting depth added 119). 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: winit/src/lib.rs holds 4 of the 63 functions over the threshold — including the worst — and 434 of the 1495 points over it (29%), 2.8× the next-largest file (widget/src/scrollable.rs at 157). 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.
iced_winit::run (cognitive 32) winit/src/lib.rs:70— iced_winit::run has cognitive complexity 32 (threshold 15). Drivers by points: match/switch 5 (19 pts), if/else 7 (11 pts), boolean chains 1, loops 1 (nesting depth added 18). 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: winit/src/lib.rs holds 4 of the 63 functions over the threshold — including the worst — and 434 of the 1495 points over it (29%), 2.8× the next-largest file (widget/src/scrollable.rs at 157). 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.
iced_winit::update (cognitive 17) winit/src/lib.rs:1233— iced_winit::update has cognitive complexity 17 (threshold 15). Drivers by points: loops 4 (9 pts), match/switch 1 (5 pts), if/else 1 (3 pts) (nesting depth added 11). 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. This file is where this pass's cognitive complexity CONCENTRATES: winit/src/lib.rs holds 4 of the 63 functions over the threshold — including the worst — and 434 of the 1495 points over it (29%), 2.8× the next-largest file (widget/src/scrollable.rs at 157). 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.
State::interact (cognitive 101) widget/src/scrollable.rs:2593— State::interact has cognitive complexity 101 (threshold 15). Drivers by points: if/else 28 (72 pts), match/switch 8 (22 pts), boolean chains 7 (nesting depth added 58). 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.
State::update (cognitive 54) widget/src/scrollable.rs:2915— State::update has cognitive complexity 54 (threshold 15). Drivers by points: if/else 19 (40 pts), boolean chains 9, match/switch 3 (5 pts) (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
State::update (cognitive 45) core/src/text/editor.rs:330— State::update has cognitive complexity 45 (threshold 15). Drivers by points: if/else 16 (33 pts), match/switch 6 (12 pts) (nesting depth added 23). Of this number, 40 points are the body's own statements and 5 belong to one function item inside it that branches. 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.
State::prepare (cognitive 31) wgpu/src/image/mod.rs:203— State::prepare has cognitive complexity 31 (threshold 15). Drivers by points: if/else 6 (14 pts), match/switch 4 (14 pts), boolean chains 2, loops 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Duplicated block (8 lines × 2) widget/src/checkbox.rs:292— widget/src/checkbox.rs:292-299 | widget/src/toggler.rs:272-279 — 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 `widget/src/checkbox.rs:292` 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) widget/src/pane_grid.rs:692— widget/src/pane_grid.rs:692-699 | widget/src/pane_grid.rs:782-789 — 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 `widget/src/pane_grid.rs:692` 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) core/src/widget/text.rs:185— core/src/widget/text.rs:185-192 | widget/src/text/rich.rs:177-184 — 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) wgpu/src/quad/gradient.rs:78— wgpu/src/quad/gradient.rs:78-85 | wgpu/src/quad/solid.rs:68-75 — before extracting anything, compare `wgpu/src/quad/gradient.rs` and `wgpu/src/quad/solid.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 62 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 `wgpu/src/quad/gradient.rs:78` 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 × 3) src/application.rs:117— src/application.rs:117-122 | src/application/timed.rs:59-64 | src/daemon.rs:61-66 — before extracting anything, compare `src/application.rs` and `src/daemon.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 56 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/application.rs:117` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) widget/src/container.rs:273— widget/src/container.rs:273-278 | widget/src/pin.rs:162-167 | widget/src/responsive.rs:88-93 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `widget/src/container.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. Note first that the copies are not typed on the same thing: the declarations holding them bind `tree` to `&mut Tree` in one and `&mut widget::Tree` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 3) widget/src/container.rs:287— widget/src/container.rs:287-292 | widget/src/pin.rs:176-181 | widget/src/responsive.rs:118-123 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `widget/src/container.rs:287` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `tree` to `&mut Tree` in one and `&mut widget::Tree` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 3) widget/src/opaque.rs:161— widget/src/opaque.rs:161-166 | widget/src/pin.rs:146-151 | widget/src/responsive.rs:132-137 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `widget/src/opaque.rs:161` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `tree` to `&mut Tree` in one and `&mut widget::Tree` 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.
Renderer::draw (cognitive 49) tiny_skia/src/lib.rs:61— Renderer::draw has cognitive complexity 49 (threshold 15). Drivers by points: loops 8 (29 pts), if/else 6 (20 pts) (nesting depth added 35). 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.
Renderer::render (cognitive 36) wgpu/src/lib.rs:395— Renderer::render has cognitive complexity 36 (threshold 15). Drivers by points: if/else 10 (26 pts), loops 3 (8 pts), boolean chains 1, match/switch 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Renderer::prepare (cognitive 16) wgpu/src/lib.rs:283— Renderer::prepare has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Scrollable::layout (cognitive 26) widget/src/scrollable.rs:512— Scrollable::layout has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 6, match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Scrollable::update (cognitive 26) widget/src/scrollable.rs:636— Scrollable::update has cognitive complexity 26 (threshold 15). Drivers by points: if/else 17 (22 pts), boolean chains 4 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Scrollable::draw (cognitive 25) widget/src/scrollable.rs:782— Scrollable::draw has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 6, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Cache::draw (cognitive 20) tiny_skia/src/vector.rs:133— Cache::draw has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 2 (6 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.
Cache::upload (cognitive 19) wgpu/src/image/vector.rs:94— Cache::upload has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 1 (3 pts), 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.
Cache::receive (cognitive 18) wgpu/src/image/cache.rs:283— Cache::receive has cognitive complexity 18 (threshold 15). Drivers by points: loops 3 (9 pts), if/else 3 (7 pts), match/switch 1 (2 pts) (nesting depth added 11). 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.
Change coupling: cache.rs ↔ paragraph.rs graphics/src/text/cache.rs:1— `graphics/src/text/cache.rs` and `graphics/src/text/paragraph.rs` change together 75% of the time (9 of the 12 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 9 shared commits counted here, the most recent 3 are `7b3ec152` Update `cosmic-text` to `0.19`; `1354cc1b` Add `Ellipsis` support :tada:; `439f4e32` Update `cosmic-text` to `0.15` :tada: — run `git show` on any of them.
Change coupling: paragraph.rs ↔ text_input.rs core/src/text/paragraph.rs:1— `core/src/text/paragraph.rs` and `widget/src/text_input.rs` change together 57% of the time (12 of the 21 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 12 shared commits counted here, the most recent 3 are `4ef3b1d3` Drop the `Font` generic in favor of the concrete `Font` type; `836a93a1` Draft `is_secure` support for new `text::Input` abstraction; `1354cc1b` Add `Ellipsis` support :tada: — run `git show` on any of them.
Change coupling: cache.rs ↔ editor.rs graphics/src/text/cache.rs:1— `graphics/src/text/cache.rs` and `graphics/src/text/editor.rs` change together 50% of the time (6 of the 12 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 6 shared commits counted here, the most recent 3 are `7b3ec152` Update `cosmic-text` to `0.19`; `439f4e32` Update `cosmic-text` to `0.15` :tada:; `6bf6fc60` Update `cosmic-text` to `0.14` — 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) wgpu/src/image/mod.rs:38— wgpu/src/image/mod.rs:38-177 | wgpu/src/quad/gradient.rs:72-170 | wgpu/src/quad/solid.rs:64-144 | wgpu/src/triangle/msaa.rs:23-118 — 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) widget/src/column.rs:261— widget/src/column.rs:261-270 | widget/src/grid.rs:277-286 | widget/src/keyed/column.rs:294-303 | widget/src/row.rs:267-276 — 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) widget/src/pane_grid/title_bar.rs:322— widget/src/pane_grid/title_bar.rs:322-360 | widget/src/pane_grid/title_bar.rs:371-428 | widget/src/pane_grid/title_bar.rs:437-477 | widget/src/pane_grid/title_bar.rs:487-541 — 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 (25 corresponding lines) · ×3
Edited copy of a member (25 corresponding lines) core/src/widget/operation/focusable.rs:107— core/src/widget/operation/focusable.rs:107-137 | core/src/widget/operation/focusable.rs:145-169 — 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.
Edited copy of a member (25 corresponding lines) core/src/length.rs:131— core/src/length.rs:131-155 | core/src/length.rs:158-182 — 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.
Edited copy of a member (25 corresponding lines) widget/src/combo_box.rs:653— widget/src/combo_box.rs:653-682 | widget/src/text_input.rs:407-431 — 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 (17 corresponding lines) · ×3
Edited copy of a member (17 corresponding lines) widget/src/pane_grid.rs:444— widget/src/pane_grid.rs:444-460 | widget/src/pane_grid.rs:685-714 — 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) core/src/rectangle.rs:195— core/src/rectangle.rs:195-215 | core/src/rectangle.rs:223-239 — 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) tester/src/recorder.rs:141— tester/src/recorder.rs:141-167 | tester/src/recorder.rs:248-264 — 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 (9 corresponding lines) · ×3
Edited copy of a member (9 corresponding lines) core/src/length.rs:55— core/src/length.rs:55-63 | core/src/length.rs:65-73 — 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) core/src/widget.rs:361— core/src/widget.rs:361-376 | core/src/overlay/element.rs:69-77 — 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) widget/src/button.rs:493— widget/src/button.rs:493-501 | widget/src/container.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.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×3
Edited copy of a member (13 corresponding lines) runtime/src/task.rs:417— runtime/src/task.rs:417-432 | runtime/src/task.rs:439-451 — 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/geometry.rs:284— tiny_skia/src/geometry.rs:284-296 | wgpu/src/geometry.rs:401-413 — 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) wgpu/src/quad/gradient.rs:32— wgpu/src/quad/gradient.rs:32-44 | wgpu/src/quad/solid.rs:26-38 — 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 (18 lines × 2) src/application.rs:93— src/application.rs:93-110 | src/daemon.rs:37-54 — before extracting anything, compare `src/application.rs` and `src/daemon.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 56 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 (18 lines × 2) wgpu/src/geometry.rs:455— wgpu/src/geometry.rs:455-472 | wgpu/src/geometry.rs:478-495 — 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) wgpu/src/lib.rs:488— wgpu/src/lib.rs:488-505 | wgpu/src/lib.rs:576-593 — 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 `wgpu/src/lib.rs:488` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `wgpu/src/lib.rs:595` calls `finish` and `wgpu/src/lib.rs:507` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) widget/src/scrollable.rs:799— widget/src/scrollable.rs:799-803 | widget/src/scrollable.rs:950-954 — 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, `widget/src/scrollable.rs:804` calls `position_over` and `widget/src/scrollable.rs:955` 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 (5 lines × 2) tiny_skia/src/lib.rs:262— tiny_skia/src/lib.rs:262-266 | wgpu/src/lib.rs:743-747 — 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:262` 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) widget/src/overlay/menu.rs:511— widget/src/overlay/menu.rs:511-515 | widget/src/overlay/menu.rs:576-580 — 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.
Low cohesion: MouseArea (LCOM4 12) widget/src/mouse_area.rs:11— MouseArea's methods fall into 12 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 12 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: Lazy (LCOM4 7) widget/src/lazy.rs:14— Lazy'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: Radius (LCOM4 4) core/src/border.rs:81— Radius'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.
iced_widget::markdown::parse_with (cyclomatic 68) widget/src/markdown.rs:1075— iced_widget::markdown::parse_with has cyclomatic complexity 68 (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.
iced_widget::mouse_area::update (cyclomatic 27) widget/src/mouse_area.rs:283— iced_widget::mouse_area::update has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Editor::perform (cyclomatic 45) graphics/src/text/editor.rs:261— Editor::perform has cyclomatic complexity 45 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Editor::update (cyclomatic 16) graphics/src/text/editor.rs:598— Editor::update has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Scrollable::update (cyclomatic 21) widget/src/scrollable.rs:636— Scrollable::update has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Scrollable::draw (cyclomatic 18) widget/src/scrollable.rs:782— Scrollable::draw has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Tester::tick (cyclomatic 20) tester/src/lib.rs:422— Tester::tick 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.
Tester::update (cyclomatic 18) tester/src/lib.rs:205— Tester::update has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This is NOT this file's highest cyclomatic complexity: Tester::view (cyclomatic 20) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
HackComment winit/src/lib.rs:584— // HACK! Send a proxy event on completion to trigger — 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.
HackComment core/src/text/highlighter.rs:29— // Hack: Best effort — 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.
FixmeComment widget/src/slider.rs:511— // FIXME: Fall back to `Pointer` on Windows — 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 widget/src/vertical_slider.rs:508— // FIXME: Fall back to `Pointer` on Windows — 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.
iced_core::layout::flex::resolve (cognitive 106) core/src/layout/flex.rs:94— iced_core::layout::flex::resolve has cognitive complexity 106 (threshold 15). Drivers by points: if/else 30 (59 pts), match/switch 12 (29 pts), loops 7 (11 pts), boolean chains 7 (nesting depth added 50). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
iced_core::widget::tree::diff_children_custom_with_search (cognitive 23) core/src/widget/tree.rs:126— iced_core::widget::tree::diff_children_custom_with_search has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (18 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.
iced_widget::markdown::parse_with (cognitive 85) widget/src/markdown.rs:1075— iced_widget::markdown::parse_with has cognitive complexity 85 (threshold 15). Drivers by points: if/else 29 (65 pts), loops 3 (9 pts), match/switch 5 (8 pts), boolean chains 3 (nesting depth added 45). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
iced_widget::mouse_area::update (cognitive 31) widget/src/mouse_area.rs:283— iced_widget::mouse_area::update has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (24 pts), boolean chains 4, match/switch 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.
PaneGrid::update (cognitive 56) widget/src/pane_grid.rs:462— PaneGrid::update has cognitive complexity 56 (threshold 15). Drivers by points: if/else 18 (39 pts), match/switch 4 (14 pts), boolean chains 2, loops 1 (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PaneGrid::draw (cognitive 21) widget/src/pane_grid.rs:716— PaneGrid::draw has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (12 pts), match/switch 3 (5 pts), boolean chains 3, 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.
Editor::perform (cognitive 55) graphics/src/text/editor.rs:261— Editor::perform has cognitive complexity 55 (threshold 15). Drivers by points: if/else 16 (36 pts), match/switch 5 (12 pts), boolean chains 4, loops 1 (3 pts) (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Editor::update (cognitive 21) graphics/src/text/editor.rs:598— Editor::update has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (13 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
iced_beacon::run (cognitive 53) beacon/src/lib.rs:94— iced_beacon::run has cognitive complexity 53 (threshold 15). Drivers by points: match/switch 7 (30 pts), if/else 5 (17 pts), loops 4 (6 pts) (nesting depth added 37). 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.
iced_beacon::client::run (cognitive 38) beacon/src/client.rs:117— iced_beacon::client::run has cognitive complexity 38 (threshold 15). Drivers by points: match/switch 5 (20 pts), if/else 2 (11 pts), loops 3 (7 pts) (nesting depth added 28). 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.
Content::push_str (cognitive 50) widget/src/markdown.rs:153— Content::push_str has cognitive complexity 50 (threshold 15). Drivers by points: if/else 23 (35 pts), boolean chains 7, match/switch 2 (5 pts), loops 2 (3 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Content::resolve_sections (cognitive 25) widget/src/markdown.rs:544— Content::resolve_sections has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 2 (6 pts), boolean chains 3, match/switch 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Tester::tick (cognitive 39) tester/src/lib.rs:422— Tester::tick has cognitive complexity 39 (threshold 15). Drivers by points: if/else 13 (31 pts), match/switch 3 (6 pts), loops 1 (2 pts) (nesting depth added 22). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Tester::controls (cognitive 21) tester/src/lib.rs:624— Tester::controls has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (13 pts), match/switch 2 (6 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Rich::draw (cognitive 39) widget/src/text/rich.rs:263— Rich::draw has cognitive complexity 39 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 5 (13 pts), boolean chains 4 (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.
Rich::update (cognitive 20) widget/src/text/rich.rs:392— Rich::update has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (16 pts), match/switch 2 (3 pts), boolean chains 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.
Engine::draw_quad (cognitive 20) tiny_skia/src/engine.rs:28— Engine::draw_quad has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (16 pts), loops 2 (3 pts), 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.
Engine::draw_text (cognitive 16) tiny_skia/src/engine.rs:285— Engine::draw_text has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 3 (4 pts) (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Wrapping::layout (cognitive 20) widget/src/column.rs:362— Wrapping::layout has cognitive complexity 20 (threshold 15). Drivers by points: loops 4 (9 pts), if/else 5 (8 pts), match/switch 2, boolean chains 1 (nesting depth added 8). 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.
Wrapping::layout (cognitive 20) widget/src/row.rs:367— Wrapping::layout has cognitive complexity 20 (threshold 15). Drivers by points: loops 4 (9 pts), if/else 5 (8 pts), match/switch 2, boolean chains 1 (nesting depth added 8). 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.
Limits::width (cognitive 16) core/src/layout/limits.rs:63— Limits::width has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 3 (5 pts) (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident. This shape REPEATS in the file: one other method here (Limits::height) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Limits::height (cognitive 16) core/src/layout/limits.rs:126— Limits::height has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 3 (5 pts) (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident. This shape REPEATS in the file: one other method here (Limits::width) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TooManyFunctions: iced_widget::helpers widget/src/helpers.rs:240— TooManyFunctions — 52 free functions. The bar is 30 free functions; 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.
TooManyFunctions: iced_runtime::window runtime/src/window.rs:196— TooManyFunctions — 41 free functions. The bar is 30 free functions; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (36 corresponding lines) · ×2
Edited copy of a member (36 corresponding lines) tiny_skia/src/vector.rs:89— tiny_skia/src/vector.rs:89-124 | wgpu/src/image/vector.rs:51-91 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (36 corresponding lines) widget/src/pane_grid/node.rs:260— widget/src/pane_grid/node.rs:260-295 | widget/src/pane_grid/node.rs:304-343 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (39 corresponding lines) · ×2
Edited copy of a member (39 corresponding lines) widget/src/text_editor.rs:796— widget/src/text_editor.rs:796-834 | widget/src/text_input.rs:580-618 — 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) widget/src/checkbox.rs:282— widget/src/checkbox.rs:282-320 | widget/src/toggler.rs:259-306 — 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 (29 corresponding lines) · ×2
Edited copy of a member (29 corresponding lines) wgpu/src/geometry.rs:170— wgpu/src/geometry.rs:170-198 | wgpu/src/geometry.rs:231-263 — 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) tiny_skia/src/lib.rs:307— tiny_skia/src/lib.rs:307-335 | wgpu/src/lib.rs:845-878 — 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 (22 corresponding lines) · ×2
Edited copy of a member (22 corresponding lines) src/application.rs:189— src/application.rs:189-217 | src/daemon.rs:131-152 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) widget/src/pane_grid/content.rs:203— widget/src/pane_grid/content.rs:203-224 | widget/src/pane_grid/content.rs:236-268 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×2
Edited copy of a member (16 corresponding lines) core/src/gradient.rs:66— core/src/gradient.rs:66-81 | graphics/src/gradient.rs:65-80 — 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) futures/src/backend/native/tokio.rs:38— futures/src/backend/native/tokio.rs:38-55 | futures/src/backend/wasm/wasm_bindgen.rs:27-42 — 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 (15 corresponding lines) · ×2
Edited copy of a member (15 corresponding lines) widget/src/popover.rs:216— widget/src/popover.rs:216-230 | widget/src/tooltip.rs:127-145 — 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) widget/src/sticky.rs:401— widget/src/sticky.rs:401-415 | widget/src/tooltip.rs:451-467 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×2
Edited copy of a member (19 corresponding lines) core/src/text.rs:502— core/src/text.rs:502-520 | core/src/text.rs:528-546 — 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) widget/src/pane_grid/node.rs:113— widget/src/pane_grid/node.rs:113-131 | widget/src/pane_grid/node.rs:141-159 — 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 copy of a member (11 corresponding lines) · ×2
Edited copy of a member (11 corresponding lines) tiny_skia/src/layer.rs:40— tiny_skia/src/layer.rs:40-50 | wgpu/src/layer.rs:69-79 — 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) tiny_skia/src/layer.rs:59— tiny_skia/src/layer.rs:59-69 | wgpu/src/layer.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.
Duplicated block (26 lines × 2) core/src/text/editor.rs:389— core/src/text/editor.rs:389-414 | core/src/text/editor.rs:455-480 — 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 (26 lines × 2) wgpu/src/image/mod.rs:61— wgpu/src/image/mod.rs:61-86 | wgpu/src/triangle/msaa.rs:28-53 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `wgpu/src/image/mod.rs:61` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (20 lines × 2) tiny_skia/src/engine.rs:141— tiny_skia/src/engine.rs:141-160 | tiny_skia/src/geometry.rs:401-420 — 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 `tiny_skia/src/engine.rs:141` 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) widget/src/slider.rs:508— widget/src/slider.rs:508-527 | widget/src/vertical_slider.rs:505-524 — before extracting anything, compare `widget/src/slider.rs` and `widget/src/vertical_slider.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 178 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (19 lines × 2) widget/src/pane_grid/node.rs:265— widget/src/pane_grid/node.rs:265-283 | widget/src/pane_grid/node.rs:313-331 — 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 `widget/src/pane_grid/node.rs:265` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) winit/src/lib.rs:846— winit/src/lib.rs:846-864 | winit/src/lib.rs:1170-1188 — 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 `winit/src/lib.rs:846` 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 (17 lines × 3) core/src/widget/operation.rs:184— core/src/widget/operation.rs:184-200 | core/src/widget/operation.rs:306-322 | core/src/widget/operation.rs:385-401 — 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 `core/src/widget/operation.rs:184` 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 (17 lines × 3) winit/src/lib.rs:718— winit/src/lib.rs:718-734 | winit/src/lib.rs:845-861 | winit/src/lib.rs:1169-1185 — 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 (16 lines × 2) runtime/src/user_interface.rs:246— runtime/src/user_interface.rs:246-261 | runtime/src/user_interface.rs:346-361 — 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 (16 lines × 2) winit/src/lib.rs:822— winit/src/lib.rs:822-837 | winit/src/lib.rs:1153-1168 — 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 `winit/src/lib.rs:822` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) wgpu/src/quad/gradient.rs:152— wgpu/src/quad/gradient.rs:152-166 | wgpu/src/quad/solid.rs:130-144 — before extracting anything, compare `wgpu/src/quad/gradient.rs` and `wgpu/src/quad/solid.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 62 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 `wgpu/src/quad/gradient.rs:152` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) wgpu/src/triangle.rs:728— wgpu/src/triangle.rs:728-742 | wgpu/src/triangle.rs:872-886 — 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 `wgpu/src/triangle.rs:728` 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) core/src/layout/flex.rs:209— core/src/layout/flex.rs:209-222 | core/src/layout/flex.rs:245-258 — 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 `core/src/layout/flex.rs:209` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) tiny_skia/src/layer.rs:79— tiny_skia/src/layer.rs:79-92 | wgpu/src/layer.rs:108-121 — before extracting anything, compare `tiny_skia/src/layer.rs` and `wgpu/src/layer.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 3) core/src/widget/operation.rs:178— core/src/widget/operation.rs:178-188 | core/src/widget/operation.rs:248-258 | core/src/widget/operation.rs:300-310 — 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 (11 lines × 3) program/src/lib.rs:174— program/src/lib.rs:174-184 | program/src/lib.rs:344-354 | src/application.rs:932-942 — before extracting anything, compare `program/src/lib.rs` and `src/application.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 4) widget/src/column.rs:262— widget/src/column.rs:262-270 | widget/src/grid.rs:278-286 | widget/src/keyed/column.rs:295-303 | widget/src/row.rs:268-276 — before extracting anything, compare `widget/src/column.rs` and `widget/src/keyed/column.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 4) widget/src/column.rs:244— widget/src/column.rs:244-252 | widget/src/grid.rs:260-268 | widget/src/keyed/column.rs:277-285 | widget/src/row.rs:250-258 — before extracting anything, compare `widget/src/column.rs` and `widget/src/keyed/column.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 37 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 `widget/src/column.rs:244` 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.
iced_core::layout::flex::resolve (cyclomatic 56) core/src/layout/flex.rs:94— iced_core::layout::flex::resolve has cyclomatic complexity 56 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
iced_beacon::run (cyclomatic 34) beacon/src/lib.rs:94— iced_beacon::run has cyclomatic complexity 34 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
UserInterface::update (cyclomatic 31) runtime/src/user_interface.rs:198— UserInterface::update 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.
Binding::from_key_press (cyclomatic 30) core/src/text/editor.rs:851— Binding::from_key_press has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Content::push_str (cyclomatic 28) widget/src/markdown.rs:153— Content::push_str has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
VerticalSlider::update (cyclomatic 28) widget/src/vertical_slider.rs:245— VerticalSlider::update has cyclomatic complexity 28 (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.
Slider::update (cyclomatic 27) widget/src/slider.rs:245— Slider::update has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ComboBox::update (cyclomatic 26) widget/src/combo_box.rs:470— ComboBox::update has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PaneGrid::update (cyclomatic 24) widget/src/pane_grid.rs:462— PaneGrid::update 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.
DevTools::update (cyclomatic 23) devtools/src/lib.rs:185— DevTools::update has cyclomatic complexity 23 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
PickList::update (cyclomatic 21) widget/src/pick_list.rs:432— PickList::update has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Table::layout (cyclomatic 21) widget/src/table.rs:218— Table::layout has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Sensor::update (cyclomatic 20) widget/src/sensor.rs:163— Sensor::update 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.
iced_wgpu::text::prepare (cyclomatic 18) wgpu/src/text.rs:433— iced_wgpu::text::prepare has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Rich::draw (cyclomatic 18) widget/src/text/rich.rs:263— Rich::draw has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Input::update::apply (cyclomatic 17) core/src/text/input.rs:140— Input::update::apply 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.
iced_graphics::image::load (cyclomatic 17) graphics/src/image.rs:46— iced_graphics::image::load 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.
Viewer::update (cyclomatic 17) widget/src/image/viewer.rs:148— Viewer::update has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Renderer::render (cyclomatic 16) wgpu/src/lib.rs:395— Renderer::render 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.
TextEditor::update (cyclomatic 16) widget/src/text_editor.rs:386— TextEditor::update has cyclomatic complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 belong to one function item inside it that branches. 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.
Repeated repair: core/src/layout/limits.rs core/src/layout/limits.rs:63— core/src/layout/limits.rs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is Limits::width at line 63), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix `Length::min` bounds inside `scrollable`”; “Disable `infinite` flags for `Length::Fixed`”; “Disable `infinite` for `Fixed` and max-`Bounded` lengths”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 13:16:37 +01:00' --until='2026-11-13 13:16:37 +01:00' --full-history --no-merges -- core/src/layout/limits.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
ComboBox::update (cognitive 54) widget/src/combo_box.rs:470— ComboBox::update has cognitive complexity 54 (threshold 15). Drivers by points: if/else 23 (49 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 28). 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.
UserInterface::update (cognitive 53) runtime/src/user_interface.rs:198— UserInterface::update has cognitive complexity 53 (threshold 15). Drivers by points: if/else 19 (36 pts), match/switch 5 (11 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Table::layout (cognitive 47) widget/src/table.rs:218— Table::layout has cognitive complexity 47 (threshold 15). Drivers by points: if/else 21 (42 pts), loops 3, 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.
Sensor::update (cognitive 40) widget/src/sensor.rs:163— Sensor::update has cognitive complexity 40 (threshold 15). Drivers by points: if/else 14 (35 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 22). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
PickList::update (cognitive 39) widget/src/pick_list.rs:432— PickList::update has cognitive complexity 39 (threshold 15). Drivers by points: if/else 20 (37 pts), boolean chains 1, match/switch 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.
Binding::from_key_press (cognitive 38) core/src/text/editor.rs:851— Binding::from_key_press has cognitive complexity 38 (threshold 15). Drivers by points: if/else 17 (26 pts), boolean chains 6, match/switch 3 (6 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.
Viewer::update (cognitive 38) widget/src/image/viewer.rs:148— Viewer::update has cognitive complexity 38 (threshold 15). Drivers by points: if/else 14 (32 pts), boolean chains 3, match/switch 2 (3 pts) (nesting depth added 19). 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.
VerticalSlider::update (cognitive 36) widget/src/vertical_slider.rs:245— VerticalSlider::update has cognitive complexity 36 (threshold 15). Drivers by points: if/else 23 (29 pts), match/switch 3 (5 pts), boolean chains 2 (nesting depth added 8). 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.
Slider::update (cognitive 35) widget/src/slider.rs:245— Slider::update has cognitive complexity 35 (threshold 15). Drivers by points: if/else 23 (29 pts), match/switch 3 (5 pts), boolean chains 1 (nesting depth added 8). 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.
DevTools::update (cognitive 33) devtools/src/lib.rs:185— DevTools::update has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (19 pts), match/switch 6 (14 pts) (nesting depth added 19). 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.
Atlas::allocate (cognitive 25) wgpu/src/image/atlas.rs:179— Atlas::allocate has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 3 (6 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Geometry::cache (cognitive 24) wgpu/src/geometry.rs:43— Geometry::cache has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (23 pts), match/switch 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
List::update (cognitive 23) widget/src/overlay/menu.rs:427— List::update has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 1, match/switch 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.
iced_graphics::text::regions (cognitive 22) graphics/src/text.rs:421— iced_graphics::text::regions has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Button::update (cognitive 21) widget/src/button.rs:277— Button::update has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (20 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.
Transition::update (cognitive 21) widget/src/transition.rs:201— Transition::update has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 3 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
GlyphCache::allocate (cognitive 19) tiny_skia/src/text.rs:258— GlyphCache::allocate has cognitive complexity 19 (threshold 15). Drivers by points: loops 4 (14 pts), if/else 2 (3 pts), match/switch 1 (2 pts) (nesting depth added 12). 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.
iced_wgpu::text::prepare (cognitive 19) wgpu/src/text.rs:433— iced_wgpu::text::prepare has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 4 (6 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.
Text::draw_with (cognitive 18) graphics/src/geometry/text.rs:52— Text::draw_with has cognitive complexity 18 (threshold 15). Drivers by points: loops 3 (7 pts), match/switch 3 (7 pts), if/else 2 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Instance::update (cognitive 18) widget/src/component.rs:200— Instance::update has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 3, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Input::update::apply (cognitive 17) core/src/text/input.rs:140— Input::update::apply has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), match/switch 2 (3 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
TextInput::update (cognitive 17) widget/src/text_input.rs:328— TextInput::update has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
iced_tiny_skia::geometry::convert_path (cognitive 16) tiny_skia/src/geometry.rs:329— iced_tiny_skia::geometry::convert_path has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (13 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TitleBar::is_over_pick_area (cognitive 16) widget/src/pane_grid/title_bar.rs:223— TitleBar::is_over_pick_area has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Near-duplicate member pair (126 shared lines) widget/src/slider.rs:254— widget/src/slider.rs:254-414 | widget/src/vertical_slider.rs:254-411 — These two members are variants of one another: 126 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/application.rs:92— src/application.rs:92-166 | src/daemon.rs:36-109 — 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) program/src/lib.rs:114— program/src/lib.rs:114-194 | program/src/lib.rs:200-277 | program/src/lib.rs:282-364 | src/application.rs:704-782 | src/application.rs:788-865 | src/application.rs:871-952 — 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· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) widget/src/column.rs:223— widget/src/column.rs:223-233 | widget/src/grid.rs:239-249 | widget/src/keyed/column.rs:256-266 | widget/src/row.rs:229-239 | widget/src/stack.rs:180-190 — 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 (105 corresponding lines) · ×1
Edited copy of a member (105 corresponding lines) widget/src/column.rs:362— widget/src/column.rs:362-467 | widget/src/row.rs:367-471 — These two members are one piece of code written twice and then edited apart: 105 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (74 corresponding lines) · ×1
Edited copy of a member (74 corresponding lines) widget/src/slider.rs:425— widget/src/slider.rs:425-498 | widget/src/vertical_slider.rs:422-495 — These two members are one piece of code written twice and then edited apart: 74 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (61 corresponding lines) · ×1
Edited copy of a member (61 corresponding lines) core/src/layout/limits.rs:63— core/src/layout/limits.rs:63-123 | core/src/layout/limits.rs:126-186 — These two members are one piece of code written twice and then edited apart: 61 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (60 corresponding lines) · ×1
Edited copy of a member (60 corresponding lines) wgpu/src/triangle.rs:683— wgpu/src/triangle.rs:683-742 | wgpu/src/triangle.rs:815-886 — These two members are one piece of code written twice and then edited apart: 60 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (51 corresponding lines) · ×1
Edited copy of a member (51 corresponding lines) tiny_skia/src/geometry.rs:159— tiny_skia/src/geometry.rs:159-216 | wgpu/src/geometry.rs:272-322 — These two members are one piece of code written twice and then edited apart: 51 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (46 corresponding lines) · ×1
Edited copy of a member (46 corresponding lines) futures/src/subscription.rs:303— futures/src/subscription.rs:303-348 | futures/src/subscription.rs:359-411 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) graphics/src/gradient.rs:94— graphics/src/gradient.rs:94-123 | graphics/src/gradient.rs:138-174 — 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 (37 corresponding lines) · ×1
Edited copy of a member (37 corresponding lines) winit/src/clipboard.rs:52— winit/src/clipboard.rs:52-92 | winit/src/clipboard.rs:99-135 — 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 (35 corresponding lines) · ×1
Edited copy of a member (35 corresponding lines) widget/src/scrollable.rs:2478— widget/src/scrollable.rs:2478-2512 | widget/src/scrollable.rs:2522-2556 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) widget/src/checkbox.rs:331— widget/src/checkbox.rs:331-367 | widget/src/radio.rs:327-358 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×1
Edited copy of a member (26 corresponding lines) widget/src/image/viewer.rs:121— widget/src/image/viewer.rs:121-146 | widget/src/svg.rs:167-194 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 32+ corresponding lines) · ×1
Edited copies of one member (3 members, 32+ corresponding lines) core/src/widget/operation/scrollable.rs:42— core/src/widget/operation/scrollable.rs:42-73 | core/src/widget/operation/scrollable.rs:81-112 | core/src/widget/operation/scrollable.rs:116-147 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 32 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 27+ corresponding lines) · ×1
Edited copies of one member (4 members, 27+ corresponding lines) widget/src/checkbox.rs:587— widget/src/checkbox.rs:587-613 | widget/src/checkbox.rs:616-642 | widget/src/checkbox.rs:645-671 | widget/src/checkbox.rs:674-700 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 27 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 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) tiny_skia/src/layer.rs:78— tiny_skia/src/layer.rs:78-95 | wgpu/src/layer.rs:107-124 — 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 (6 members, 22+ corresponding lines) · ×1
Edited copies of one member (6 members, 22+ corresponding lines) core/src/widget/operation/focusable.rs:29— core/src/widget/operation/focusable.rs:29-52 | core/src/widget/operation/text_input.rs:32-53 | core/src/widget/operation/text_input.rs:57-78 | core/src/widget/operation/text_input.rs:82-104 | core/src/widget/operation/text_input.rs:107-128 | core/src/widget/operation/text_input.rs:135-158 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×1
Edited copy of a member (27 corresponding lines) widget/src/slider.rs:125— widget/src/slider.rs:125-151 | widget/src/vertical_slider.rs:124-150 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×1
Edited copies of one member (3 members, 16+ corresponding lines) tiny_skia/src/geometry.rs:98— tiny_skia/src/geometry.rs:98-113 | tiny_skia/src/geometry.rs:115-135 | tiny_skia/src/geometry.rs:137-153 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) wgpu/src/triangle.rs:634— wgpu/src/triangle.rs:634-656 | wgpu/src/triangle.rs:766-788 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×1
Edited copy of a member (20 corresponding lines) core/src/widget/operation/text.rs:97— core/src/widget/operation/text.rs:97-116 | core/src/widget/operation/text.rs:119-138 — 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 copies of one member (3 members, 17+ corresponding lines) · ×1
Edited copies of one member (3 members, 17+ corresponding lines) widget/src/column.rs:198— widget/src/column.rs:198-214 | widget/src/keyed/column.rs:231-247 | widget/src/row.rs:204-220 — 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 (7 members, 13+ corresponding lines) · ×1
Edited copies of one member (7 members, 13+ corresponding lines) widget/src/button.rs:578— widget/src/button.rs:578-590 | widget/src/button.rs:593-605 | widget/src/button.rs:608-620 | widget/src/button.rs:623-635 | widget/src/button.rs:638-650 | widget/src/button.rs:672-688 | widget/src/button.rs:691-707 — These 7 members are one piece of code written 7 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 7 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 15+ corresponding lines) · ×1
Edited copies of one member (4 members, 15+ corresponding lines) runtime/src/clipboard.rs:39— runtime/src/clipboard.rs:39-53 | runtime/src/clipboard.rs:56-70 | runtime/src/clipboard.rs:73-87 | runtime/src/clipboard.rs:91-105 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×1
Edited copies of one member (3 members, 10+ corresponding lines) widget/src/column.rs:178— widget/src/column.rs:178-189 | widget/src/row.rs:184-195 | widget/src/stack.rs:123-132 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×1
Edited copy of a member (10 corresponding lines) widget/src/stack.rs:239— widget/src/stack.rs:239-249 | widget/src/table.rs:535-544 — 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 (6 corresponding lines) · ×1
Edited copy of a member (6 corresponding lines) widget/src/text_editor.rs:601— widget/src/text_editor.rs:601-610 | widget/src/text_input.rs:321-326 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 19+ corresponding lines) · ×1
Edited copies of one member (3 members, 19+ corresponding lines) tiny_skia/src/layer.rs:342— tiny_skia/src/layer.rs:342-360 | wgpu/src/layer.rs:308-330 | wgpu/src/layer.rs:332-354 — 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.
Duplicated block (48 lines × 2) widget/src/slider.rs:279— widget/src/slider.rs:279-326 | widget/src/vertical_slider.rs:279-326 — before extracting anything, compare `widget/src/slider.rs` and `widget/src/vertical_slider.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 178 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 `widget/src/slider.rs:279` 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 (27 lines × 2) widget/src/slider.rs:370— widget/src/slider.rs:370-396 | widget/src/vertical_slider.rs:370-396 — before extracting anything, compare `widget/src/slider.rs` and `widget/src/vertical_slider.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 178 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 `widget/src/slider.rs:370` 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 after the matched lines, `widget/src/slider.rs:399` calls `update` and `widget/src/vertical_slider.rs:398` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (25 lines × 2) graphics/src/text/paragraph.rs:77— graphics/src/text/paragraph.rs:77-101 | graphics/src/text/paragraph.rs:137-161 — 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 (23 lines × 2) tiny_skia/src/vector.rs:161— tiny_skia/src/vector.rs:161-183 | wgpu/src/image/vector.rs:134-156 — 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/vector.rs:161` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `handle` to `&Handle` in one and `&svg::Handle` 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 (22 lines × 2) program/src/lib.rs:232— program/src/lib.rs:232-253 | src/application.rs:820-841 — before extracting anything, compare `program/src/lib.rs` and `src/application.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 84 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 `program/src/lib.rs:232` 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 × 6) program/src/lib.rs:135— program/src/lib.rs:135-155 | program/src/lib.rs:221-241 | program/src/lib.rs:305-325 | src/application.rs:726-746 | src/application.rs:809-829 | src/application.rs:893-913 — before extracting anything, compare `program/src/lib.rs` and `src/application.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `program/src/lib.rs:242` calls `title` and `program/src/lib.rs:156` 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 (20–21 lines × 2) core/src/layout/flex.rs:350— core/src/layout/flex.rs:350-370 | core/src/layout/flex.rs:413-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.
Duplicated block (21 lines × 2) widget/src/scrollable.rs:3599— widget/src/scrollable.rs:3599-3619 | widget/src/scrollable.rs:3628-3648 — 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 `widget/src/scrollable.rs:3599` 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–19 lines × 2) widget/src/checkbox.rs:452— widget/src/checkbox.rs:452-469 | widget/src/toggler.rs:399-417 — 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 `widget/src/checkbox.rs:452` 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 (17–18 lines × 2) graphics/src/text/paragraph.rs:112— graphics/src/text/paragraph.rs:112-128 | graphics/src/text/paragraph.rs:199-216 — 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 `graphics/src/text/paragraph.rs:112` 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 × 3) core/src/widget/operation.rs:167— core/src/widget/operation.rs:167-182 | core/src/widget/operation.rs:289-304 | core/src/widget/operation.rs:368-383 — 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 `core/src/widget/operation.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.
Duplicated block (15–16 lines × 2) widget/src/checkbox.rs:353— widget/src/checkbox.rs:353-367 | widget/src/radio.rs:343-358 — 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 `widget/src/checkbox.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 (15 lines × 6) program/src/lib.rs:155— program/src/lib.rs:155-169 | program/src/lib.rs:246-260 | program/src/lib.rs:325-339 | src/application.rs:746-760 | src/application.rs:834-848 | src/application.rs:913-927 — before extracting anything, compare `program/src/lib.rs` and `src/application.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `program/src/lib.rs:242` calls `title` and `program/src/lib.rs:152` 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 (14–15 lines × 2) tiny_skia/src/geometry.rs:194— tiny_skia/src/geometry.rs:194-208 | wgpu/src/geometry.rs:301-314 — 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/geometry.rs:194` 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–15 lines × 2) wgpu/src/image/mod.rs:231— wgpu/src/image/mod.rs:231-245 | wgpu/src/image/mod.rs:283-295 — 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 `wgpu/src/image/mod.rs:231` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12–14 lines × 3) wgpu/src/quad/gradient.rs:152— wgpu/src/quad/gradient.rs:152-163 | wgpu/src/quad/solid.rs:130-141 | wgpu/src/triangle/msaa.rs:96-109 — before extracting anything, compare `wgpu/src/quad/gradient.rs` and `wgpu/src/quad/solid.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 62 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 `wgpu/src/quad/gradient.rs:152` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 4) wgpu/src/image/mod.rs:155— wgpu/src/image/mod.rs:155-167 | wgpu/src/quad/gradient.rs:151-163 | wgpu/src/quad/solid.rs:129-141 | wgpu/src/triangle/msaa.rs:95-107 — before extracting anything, compare `wgpu/src/quad/gradient.rs` and `wgpu/src/quad/solid.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 62 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 `wgpu/src/image/mod.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 (13 lines × 3) core/src/widget/operation/scrollable.rs:50— core/src/widget/operation/scrollable.rs:50-62 | core/src/widget/operation/scrollable.rs:89-101 | core/src/widget/operation/scrollable.rs:124-136 — 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 `core/src/widget/operation/scrollable.rs:50` 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) graphics/src/gradient.rs:99— graphics/src/gradient.rs:99-110 | graphics/src/gradient.rs:145-157 — 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 `graphics/src/gradient.rs:99` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–13 lines × 2) widget/src/combo_box.rs:551— widget/src/combo_box.rs:551-561 | widget/src/combo_box.rs:573-585 — 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 `widget/src/combo_box.rs:551` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–12 lines × 2) src/application.rs:190— src/application.rs:190-201 | src/daemon.rs:132-140 — before extracting anything, compare `src/application.rs` and `src/daemon.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 56 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10–12 lines × 2) widget/src/slider.rs:266— widget/src/slider.rs:266-275 | widget/src/vertical_slider.rs:265-276 — before extracting anything, compare `widget/src/slider.rs` and `widget/src/vertical_slider.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 178 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 `widget/src/slider.rs:266` 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 (10–11 lines × 4) core/src/widget/operation.rs:191— core/src/widget/operation.rs:191-200 | core/src/widget/operation.rs:274-284 | core/src/widget/operation.rs:313-322 | core/src/widget/operation.rs:392-401 — 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 `core/src/widget/operation.rs:191` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 5) widget/src/column.rs:224— widget/src/column.rs:224-233 | widget/src/grid.rs:240-249 | widget/src/keyed/column.rs:257-266 | widget/src/row.rs:230-239 | widget/src/stack.rs:181-190 — before extracting anything, compare `widget/src/column.rs` and `widget/src/keyed/column.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 3) widget/src/button.rs:352— widget/src/button.rs:352-361 | widget/src/slider.rs:405-414 | widget/src/vertical_slider.rs:402-411 — before extracting anything, compare `widget/src/slider.rs` and `widget/src/vertical_slider.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 178 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 `widget/src/button.rs:352` 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) selector/src/target.rs:203— selector/src/target.rs:203-211 | selector/src/target.rs:215-223 | selector/src/target.rs:227-235 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 4) program/src/lib.rs:181— program/src/lib.rs:181-188 | program/src/lib.rs:351-358 | src/application.rs:772-779 | src/application.rs:855-862 — before extracting anything, compare `program/src/lib.rs` and `src/application.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 84 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 `program/src/lib.rs:181` 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 × 3) core/src/widget/operation/text_input.rs:33— core/src/widget/operation/text_input.rs:33-40 | core/src/widget/operation/text_input.rs:58-65 | core/src/widget/operation/text_input.rs:108-115 — 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 `core/src/widget/operation/text_input.rs:33` 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 × 5) program/src/lib.rs:179— program/src/lib.rs:179-185 | program/src/lib.rs:349-355 | src/application.rs:770-776 | src/application.rs:853-859 | src/application.rs:937-943 — before extracting anything, compare `program/src/lib.rs` and `src/application.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 84 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 `program/src/lib.rs:179` 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/application.rs:766` calls `subscription` and `program/src/lib.rs:176` 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 (3–7 lines × 4) widget/src/pane_grid/title_bar.rs:326— widget/src/pane_grid/title_bar.rs:326-332 | widget/src/pane_grid/title_bar.rs:375-381 | widget/src/pane_grid/title_bar.rs:440-442 | widget/src/pane_grid/title_bar.rs:490-492 — 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 `widget/src/pane_grid/title_bar.rs:326` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 7) tester/src/recorder.rs:126— tester/src/recorder.rs:126-130 | widget/src/mouse_area.rs:175-179 | widget/src/opaque.rs:132-136 | widget/src/popover.rs:236-240 | widget/src/sensor.rs:259-263 | widget/src/sticky.rs:126-130 | widget/src/tooltip.rs:159-163 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 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 7 times. Note first that the copies are not typed on the same thing: the declarations holding them bind `tree` to `&mut widget::Tree` in one and `&mut Tree` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 5) widget/src/button.rs:435— widget/src/button.rs:435-440 | widget/src/container.rs:338-343 | widget/src/opaque.rs:222-227 | widget/src/pin.rs:218-223 | widget/src/responsive.rs:147-152 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 5 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `widget/src/button.rs:435` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `tree` to `&mut Tree` in one and `&mut widget::Tree` 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 × 4) widget/src/mouse_area.rs:249— widget/src/mouse_area.rs:249-259 | widget/src/popover.rs:272-282 | widget/src/sensor.rs:274-284 | widget/src/tooltip.rs:270-280 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `widget/src/mouse_area.rs:249` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `tree` to `&mut widget::Tree` in one and `&mut Tree` 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.
Off the main sequence: iced_core — iced_core: abstractness 0.18, instability 0.00, distance 0.82 — zone of pain — concrete and depended on by 8 project(s), so it's rigid to change.
Sync-over-async blocking winit/src/lib.rs:466— `run_instance` is async and calls block_on — a blocking call inside async code stalls the executor thread, and every task scheduled on it for as long as it runs.
Duplicated predicate wgpu/src/image/mod.rs:241— `bounds.width < 1.0 || bounds.height < 1.0` appears character-identically in 2 files — wgpu/src/image/mod.rs, widget/src/canvas.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 winit/src/lib.rs:753— `physical_size.width == 0 || physical_size.height == 0` appears character-identically in 2 files — winit/src/lib.rs, winit/src/window.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 widget/src/column.rs:181— `self.width.is_fit() || self.height.is_fit()` appears character-identically in 3 files — widget/src/column.rs, widget/src/keyed/column.rs, widget/src/row.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 widget/src/slider.rs:362— `state.keyboard_modifiers.control() && cursor.is_over(layout.bounds())` appears character-identically in 2 files — widget/src/slider.rs, widget/src/vertical_slider.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 widget/src/button.rs:377— `style.background.is_some() || style.border.width > 0.0 || style.shadow.color.a > 0.0` appears character-identically in 2 files — widget/src/button.rs, widget/src/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.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 2 of 17 project(s) overshoot their size bounds, lowering Project Cohesion to 7.6/10. The most over is `widget` (28257 LoC, 195 module-visible types across 8 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.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P10 · Library API & versioning· Implementation type on the public API · ×1
Implementation type on the public API debug/src/lib.rs:309— 1 public type in `iced_debug.internal` is marked as implementation by its own namespace, folder or name: `Span` (debug/src/lib.rs:309, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
Logging is not universal — Only 11/12 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`.
Outdated: jiff — `jiff` is locked at 0.2.38 but 0.2.43 is the current stable release on crates.io, and it already satisfies the `"0.2"` requirement declared in examples/changelog/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p jiff` and commit the updated REDACTED.
Outdated: kamadak-exif — `kamadak-exif` is locked at 0.6.1 but 0.6.2 is the current stable release on crates.io, and it already satisfies the `"0.6"` requirement declared in graphics/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p kamadak-exif` and commit the updated REDACTED.
Outdated: uuid — `uuid` is locked at 1.29.0 but 1.29.2 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in examples/todos/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p uuid` and commit the updated REDACTED.
Outdated: wasmtimer — `wasmtimer` is locked at 0.4.3 but 0.4.5 is the current stable release on crates.io, and it already satisfies the `"0.4.2"` requirement declared in futures/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p wasmtimer` and commit the updated REDACTED.
Outdated: webbrowser — `webbrowser` is locked at 1.2.6 but 1.2.7 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in examples/changelog/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p webbrowser` and commit the updated REDACTED.
Outdated: wgpu — `wgpu` is locked at 30.0.1 but 30.0.2 is the current stable release on crates.io, and it already satisfies the `"30"` requirement declared in wgpu/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p wgpu` and commit the updated REDACTED.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
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 01a1d875-f455-7dc2-8e75-750e018532f0 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 35 · Warnings: 735 · Recommendations: 9 · Info: 6 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 05:09 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.