Public report of linebender/xilem, 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, 18:59 UTC · Survey ID cd_ec83b7ea55ca4d97a9b1a3add45ea9b3
linebender/xilem
Measured 14 November 2026, 18:55 UTC, at code version dc49687
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 scoreAdequate
CriticalWeakAdequateStrongExemplary
Up 3 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: 68,211 lines of product code in 12 projects, tests not counted · Estimated rebuild effort: about 0.6 person-years · Weakest lens: Accessibility, 49
Findings by how serious they are
49 critical722 serious132 minor
22 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, 18:55 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.
875of 903 findings point to an exact file and line, so you can open each one in the code. The other 28 concern the repository as a whole, such as missing documentation.
43dimensions across 7 lenses, read from 68,211 lines of product code in 12 projects.
linebender/xilem falls short of our standard for a preview release, held back most by its Accessibility lens, the interface's usability with a keyboard or assistive technology. It scores 63 out of 100 and is rated Adequate, and 41 of its 49 critical findings are security problems in the build pipeline and in the packages it uses.
Accessibility, at 49, is the weakest lens and counts most in the score. The best first steps are fixing focus, motion and contrast and structuring the pages, each worth about 10 points. Raising Accessibility to 65 would lift the score to about 70.
Thirty-eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two known security holes in the packages the code depends on can be used by attackers, and six parts of the code are no longer understood by anyone working on it. Pinning each tool to an exact version, updating the vulnerable packages and having someone learn the forgotten files would close these risks. The pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions. The page that doesn't say its language needs its language set.
The product code is 68,211 lines, about €91,000 to rebuild.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Accessibility rose from 49 to 65, the lowest score rated Strong, the score would rise from 63 to about 70.
Code composition: what the lines of code are
Product code 85%Tests 15%
New since the last survey: 114 findings
These 114 critical or serious findings weren't in the previous survey, on 28 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Code Duplication · Members sharing a duplicated core (11 members, 50+ identical tokens) masonry_core/src/passes/accessibility.rs
Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) masonry/src/layers/tooltip.rs
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) masonry/src/widgets/prose.rs
Code Duplication · Edited copy of a member (13 corresponding lines) xilem_web/src/one_of.rs
Code Duplication · Edited copy of a member (26 corresponding lines) masonry/src/doc/vertical_stack.rs
Code Duplication · Edited copy of a member (23 corresponding lines) masonry_core/src/core/contexts.rs
Code Duplication · Edited copy of a member (25 corresponding lines) xilem_core/src/environment.rs
Code Duplication · Edited copy of a member (25 corresponding lines) xilem_web/src/modifiers/class.rs
Code Duplication · Edited copy of a member (21 corresponding lines) xilem_web/src/events.rs
Code Duplication · Edited copy of a member (17 corresponding lines) xilem_web/src/modifiers/attribute.rs
Code Duplication · Edited copy of a member (18 corresponding lines) masonry/src/widgets/step_input.rs
Code Duplication · Edited copy of a member (18 corresponding lines) xilem_masonry/src/view/collapse_panel.rs
Code Duplication · Edited copy of a member (9 corresponding lines) xilem_web/src/modifiers/style.rs
Code Duplication · Edited copy of a member (25 corresponding lines) xilem_masonry/src/view/button.rs
Code Duplication · Edited copy of a member (22 corresponding lines) masonry_core/src/core/contexts.rs
Code Duplication · Edited copy of a member (21 corresponding lines) masonry_testing/src/assert_any.rs
Code Duplication · Edited copy of a member (14 corresponding lines) xilem_masonry/src/view/flex.rs
Code Duplication · Edited copies of one member (4 members, 20+ corresponding lines) masonry_core/src/app/render_root.rs
Code Duplication · Edited copy of a member (16 corresponding lines) masonry/src/widgets/portal.rs
Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) xilem_web/src/svg/kurbo_shape.rs
Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) xilem_masonry/src/view/grid.rs
Code Duplication · Edited copies of one member (5 members, 1+ corresponding lines) xilem_web/src/modifiers/elements.rs
Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) masonry_core/src/core/properties_mut.rs
Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) xilem_web/src/events.rs
Code Duplication · Edited copy of a member (13 corresponding lines) masonry/src/widgets/flex.rs
Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) xilem_web/src/svg/kurbo_shape.rs
Code Duplication · Edited copy of a member (8 corresponding lines) xilem_web/src/modifiers/class.rs
Code Duplication · Edited copy of a member (22 corresponding lines) masonry/src/widgets/button.rs
Code Duplication · Edited copy of a member (11 corresponding lines) xilem_masonry/src/view/image.rs
Code Duplication · Edited copy of a member (11 corresponding lines) masonry/src/widgets/step_input.rs
Code Duplication · Edited copy of a member (10 corresponding lines) xilem_web/src/modifiers/style.rs
Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) xilem_masonry/src/view/flex.rs
Code Duplication · Edited copy of a member (14 corresponding lines) masonry/src/widgets/radio_button.rs
Code Duplication · Edited copy of a member (13 corresponding lines) masonry_imaging/src/texture_render.rs
Code Duplication · Edited copy of a member (15 corresponding lines) masonry/src/widgets/divider.rs
Code Duplication · Edited copy of a member (8 corresponding lines) masonry/src/widgets/flex.rs
Code Duplication · Edited copy of a member (15 corresponding lines) masonry_core/src/app/layer_stack.rs
Code Duplication · Edited copy of a member (14 corresponding lines) xilem_web/src/modifiers/style.rs
Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) masonry/src/widgets/checkbox.rs
Code Duplication · Edited copy of a member (12 corresponding lines) placehero/src/components/media.rs
Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) masonry/src/widgets/button.rs
Code Duplication · Edited copy of a member (11 corresponding lines) masonry/src/widgets/label.rs
Code Duplication · Edited copy of a member (11 corresponding lines) masonry_core/src/app/render_root.rs
Code Duplication · Edited copy of a member (17 corresponding lines) masonry_core/src/passes/compose.rs
Code Duplication · Edited copy of a member (13 corresponding lines) xilem_masonry/src/view/checkbox.rs
Code Duplication · Edited copy of a member (15 corresponding lines) xilem_web/src/events.rs
Code Duplication · Edited copy of a member (7 corresponding lines) xilem_masonry/src/view/image.rs
Code Duplication · Edited copy of a member (13 corresponding lines) xilem_web/src/modifiers/attribute.rs
Code Duplication · Edited copy of a member (12 corresponding lines) xilem_web/src/modifiers/class.rs
Code Duplication · Edited copy of a member (8 corresponding lines) xilem_web/src/modifiers/class.rs
Code Duplication · Edited copy of a member (8 corresponding lines) masonry_core/src/core/widget_mut.rs
Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) xilem_web/src/elements.rs
Code Duplication · Edited copy of a member (14 corresponding lines) masonry/src/widgets/divider.rs
Code Duplication · Edited copy of a member (11 corresponding lines) masonry/src/widgets/flex.rs
Code Duplication · Edited copy of a member (16 corresponding lines) masonry_core/src/app/tracing_backend.rs
Code Duplication · Edited copy of a member (14 corresponding lines) masonry/src/widgets/split.rs
Code Duplication · Edited copy of a member (9 corresponding lines) xilem_core/src/views/fork.rs
Code Duplication · Edited copy of a member (11 corresponding lines) xilem_masonry/src/view/button.rs
Code Duplication · Edited copy of a member (13 corresponding lines) xilem_masonry/src/view/grid.rs
Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) xilem_web/src/modifiers/attribute.rs
Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) masonry/src/widgets/checkbox.rs
Code Duplication · Edited copy of a member (12 corresponding lines) masonry_core/src/passes/anim.rs
Code Duplication · Edited copy of a member (8 corresponding lines) xilem_masonry/src/view/radio_button.rs
Code Duplication · Edited copy of a member (6 corresponding lines) xilem_web/src/modifiers/attribute.rs
Code Duplication · Edited copy of a member (12 corresponding lines) xilem_web/src/modifiers/class.rs
Code Duplication · Edited copy of a member (5 corresponding lines) masonry/src/widgets/zstack.rs
Code Duplication · Edited copy of a member (6 corresponding lines) masonry/src/widgets/badged.rs
Code Duplication · Edited copy of a member (9 corresponding lines) xilem_web/src/modifiers/class.rs
Code Duplication · Edited copy of a member (6 corresponding lines) xilem_web/src/modifiers/attribute.rs
Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) xilem_masonry/src/view/flex.rs
Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) masonry/src/layers/selector_menu.rs
Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) masonry/src/widgets/indexed_stack.rs
Code Duplication · Edited copy of a member (4 corresponding lines) xilem_masonry/src/view/flex.rs
Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) masonry/src/layers/selector_menu.rs
Code Duplication · Edited copy of a member (4 corresponding lines) xilem_masonry/src/view/badge.rs
Code Duplication · Edited copy of a member (8 corresponding lines) masonry/src/doc/color_rectangle.rs
Code Duplication · Edited copy of a member (6 corresponding lines) masonry/src/widgets/grid.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: 30 findings
These 30 critical or serious findings were in the previous survey, on 28 October 2026, and are gone from this one.
Code Duplication · Members sharing a duplicated core (11 members, 50+ identical tokens) masonry_core/src/passes/accessibility.rs
Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) masonry/src/layers/tooltip.rs
Dependency Vulnerabilities · Medium vulnerability: [GHSA redacted] REDACTED
A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €91,000 · Estimate
Cost to rebuild
€30,000 to €150,000, for 505 to 1,602 hours of work, about 0.6 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.9 at a score of 63. 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: 68,211 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
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Raises the score by about 10 points · Medium effort · Page structure
3
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs.
Raises the score by about 1 point · Low effort · ADR Quality
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €91,000 to build again, about 0.6 person-years of work. Its weakest lens is Accessibility, at 49 (Weak). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. Of all the actions in this report, it raises the score most for the work it takes: about 10 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
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.
276 modules, with 1132 dependencies between them. 6 loops run through 49 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 236 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.
masonry_core.core.default_properties uses masonry_core.core.property_stack, so a change to masonry_core.core.property_stack can break masonry_core.core.default_properties, while a change to masonry_core.core.default_properties can't break masonry_core.core.property_stack.
Position
Below the diagonal: masonry_core.core.default_properties uses a module listed above it, which is the healthy direction.
masonry_core.core.properties_mut uses masonry_core.core.property_stack, so a change to masonry_core.core.property_stack can break masonry_core.core.properties_mut, while a change to masonry_core.core.properties_mut can't break masonry_core.core.property_stack.
Position
Below the diagonal: masonry_core.core.properties_mut uses a module listed above it, which is the healthy direction.
masonry_core.core.properties_ref uses masonry_core.core.property_stack, so a change to masonry_core.core.property_stack can break masonry_core.core.properties_ref, while a change to masonry_core.core.properties_ref can't break masonry_core.core.property_stack.
Position
Below the diagonal: masonry_core.core.properties_ref uses a module listed above it, which is the healthy direction.
9→13 masonry_core.core.widget_mut uses masonry_core.core.widgetpart of a loop✕
Connections
1 pair of types, where a type in masonry_core.core.widget_mut uses a type in masonry_core.core.widget.
masonry_core.core.widget_mut uses masonry_core.core.widget, so a change to masonry_core.core.widget can break masonry_core.core.widget_mut, while a change to masonry_core.core.widget_mut can't break masonry_core.core.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.
9→22 masonry_core.core.widget_mut uses masonry_core.core.contextspart of a loop✕
Connections
1 pair of types, where a type in masonry_core.core.widget_mut uses a type in masonry_core.core.contexts.
masonry_core.core.widget_mut uses masonry_core.core.contexts, so a change to masonry_core.core.contexts can break masonry_core.core.widget_mut, while a change to masonry_core.core.widget_mut can't break masonry_core.core.contexts.
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.
masonry_core.core.widget_pod uses masonry_core.core.property_stack, so a change to masonry_core.core.property_stack can break masonry_core.core.widget_pod, while a change to masonry_core.core.widget_pod can't break masonry_core.core.property_stack.
Position
Below the diagonal: masonry_core.core.widget_pod uses a module listed above it, which is the healthy direction.
10→13 masonry_core.core.widget_pod uses masonry_core.core.widgetpart of a loop✕
Connections
2 pairs of types, where a type in masonry_core.core.widget_pod uses a type in masonry_core.core.widget.
masonry_core.core.widget_pod uses masonry_core.core.widget, so a change to masonry_core.core.widget can break masonry_core.core.widget_pod, while a change to masonry_core.core.widget_pod can't break masonry_core.core.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.
masonry_core.layout.len_req uses masonry_core.layout.length, so a change to masonry_core.layout.length can break masonry_core.layout.len_req, while a change to masonry_core.layout.len_req can't break masonry_core.layout.length.
Position
Below the diagonal: masonry_core.layout.len_req uses a module listed above it, which is the healthy direction.
xilem_core.message_context uses xilem_core.message, so a change to xilem_core.message can break xilem_core.message_context, while a change to xilem_core.message_context can't break xilem_core.message.
Position
Below the diagonal: xilem_core.message_context uses a module listed above it, which is the healthy direction.
12→18 xilem_core.message_context uses xilem_core.environmentpart of a loop✕
Connections
1 pair of types, where a type in xilem_core.message_context uses a type in xilem_core.environment.
xilem_core.message_context uses xilem_core.environment, so a change to xilem_core.environment can break xilem_core.message_context, while a change to xilem_core.message_context can't break xilem_core.environment.
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.
masonry_core.core.widget uses masonry_core.core.events, so a change to masonry_core.core.events can break masonry_core.core.widget, while a change to masonry_core.core.widget can't break masonry_core.core.events.
Position
Below the diagonal: masonry_core.core.widget uses a module listed above it, which is the healthy direction.
masonry_core.core.widget uses masonry_core.layout.length, so a change to masonry_core.layout.length can break masonry_core.core.widget, while a change to masonry_core.core.widget can't break masonry_core.layout.length.
Position
Below the diagonal: masonry_core.core.widget uses a module listed above it, which is the healthy direction.
masonry_core.core.widget uses masonry_core.core.properties_mut, so a change to masonry_core.core.properties_mut can break masonry_core.core.widget, while a change to masonry_core.core.widget can't break masonry_core.core.properties_mut.
Position
Below the diagonal: masonry_core.core.widget uses a module listed above it, which is the healthy direction.
masonry_core.core.widget uses masonry_core.core.properties_ref, so a change to masonry_core.core.properties_ref can break masonry_core.core.widget, while a change to masonry_core.core.widget can't break masonry_core.core.properties_ref.
Position
Below the diagonal: masonry_core.core.widget uses a module listed above it, which is the healthy direction.
masonry_core.core.widget uses masonry_core.core.widget_mut, so a change to masonry_core.core.widget_mut can break masonry_core.core.widget, while a change to masonry_core.core.widget can't break masonry_core.core.widget_mut.
Position
Below the diagonal: masonry_core.core.widget uses a module listed above it, which is the healthy direction.
masonry_core.core.widget uses masonry_core.core.widget_pod, so a change to masonry_core.core.widget_pod can break masonry_core.core.widget, while a change to masonry_core.core.widget can't break masonry_core.core.widget_pod.
Position
Below the diagonal: masonry_core.core.widget uses a module listed above it, which is the healthy direction.
masonry_core.core.widget uses masonry_core.layout.len_req, so a change to masonry_core.layout.len_req can break masonry_core.core.widget, while a change to masonry_core.core.widget can't break masonry_core.layout.len_req.
Position
Below the diagonal: masonry_core.core.widget uses a module listed above it, which is the healthy direction.
13→22 masonry_core.core.widget uses masonry_core.core.contextspart of a loop✕
Connections
11 pairs of types, where a type in masonry_core.core.widget uses a type in masonry_core.core.contexts.
masonry_core.core.widget uses masonry_core.core.contexts, so a change to masonry_core.core.contexts can break masonry_core.core.widget, while a change to masonry_core.core.widget can't break masonry_core.core.contexts.
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.
xilem_core.view uses xilem_core.message, so a change to xilem_core.message can break xilem_core.view, while a change to xilem_core.view can't break xilem_core.message.
Position
Below the diagonal: xilem_core.view uses a module listed above it, which is the healthy direction.
xilem_core.view uses xilem_core.message_context, so a change to xilem_core.message_context can break xilem_core.view, while a change to xilem_core.view can't break xilem_core.message_context.
Position
Below the diagonal: xilem_core.view uses a module listed above it, which is the healthy direction.
14→20 xilem_core.view uses xilem_core.docspart of a loop✕
Connections
1 pair of types, where a type in xilem_core.view uses a type in xilem_core.docs.
The types involved
xilem_core.view.View → xilem_core.docs.State
Direction
xilem_core.view uses xilem_core.docs, so a change to xilem_core.docs can break xilem_core.view, while a change to xilem_core.view can't break xilem_core.docs.
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.
xilem_core.view_sequence uses xilem_core.element_splice, so a change to xilem_core.element_splice can break xilem_core.view_sequence, while a change to xilem_core.view_sequence can't break xilem_core.element_splice.
Position
Below the diagonal: xilem_core.view_sequence uses a module listed above it, which is the healthy direction.
xilem_core.view_sequence uses xilem_core.message, so a change to xilem_core.message can break xilem_core.view_sequence, while a change to xilem_core.view_sequence can't break xilem_core.message.
Position
Below the diagonal: xilem_core.view_sequence uses a module listed above it, which is the healthy direction.
xilem_core.view_sequence uses xilem_core.message_context, so a change to xilem_core.message_context can break xilem_core.view_sequence, while a change to xilem_core.view_sequence can't break xilem_core.message_context.
Position
Below the diagonal: xilem_core.view_sequence uses a module listed above it, which is the healthy direction.
15→20 xilem_core.view_sequence uses xilem_core.docspart of a loop✕
Connections
1 pair of types, where a type in xilem_core.view_sequence uses a type in xilem_core.docs.
xilem_core.view_sequence uses xilem_core.docs, so a change to xilem_core.docs can break xilem_core.view_sequence, while a change to xilem_core.view_sequence can't break xilem_core.docs.
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.
masonry_core.core.property uses masonry_core.core.widget, so a change to masonry_core.core.widget can break masonry_core.core.property, while a change to masonry_core.core.property can't break masonry_core.core.widget.
Position
Below the diagonal: masonry_core.core.property uses a module listed above it, which is the healthy direction.
masonry_core.core.widget_state uses masonry_core.core.property_stack, so a change to masonry_core.core.property_stack can break masonry_core.core.widget_state, while a change to masonry_core.core.widget_state can't break masonry_core.core.property_stack.
Position
Below the diagonal: masonry_core.core.widget_state uses a module listed above it, which is the healthy direction.
masonry_core.core.widget_state uses masonry_core.core.widget_pod, so a change to masonry_core.core.widget_pod can break masonry_core.core.widget_state, while a change to masonry_core.core.widget_state can't break masonry_core.core.widget_pod.
Position
Below the diagonal: masonry_core.core.widget_state uses a module listed above it, which is the healthy direction.
masonry_core.core.widget_state uses masonry_core.core.widget, so a change to masonry_core.core.widget can break masonry_core.core.widget_state, while a change to masonry_core.core.widget_state can't break masonry_core.core.widget.
Position
Below the diagonal: masonry_core.core.widget_state uses a module listed above it, which is the healthy direction.
xilem_core.environment uses xilem_core.message, so a change to xilem_core.message can break xilem_core.environment, while a change to xilem_core.environment can't break xilem_core.message.
Position
Below the diagonal: xilem_core.environment uses a module listed above it, which is the healthy direction.
xilem_core.environment uses xilem_core.message_context, so a change to xilem_core.message_context can break xilem_core.environment, while a change to xilem_core.environment can't break xilem_core.message_context.
Position
Below the diagonal: xilem_core.environment uses a module listed above it, which is the healthy direction.
xilem_core.environment uses xilem_core.view, so a change to xilem_core.view can break xilem_core.environment, while a change to xilem_core.environment can't break xilem_core.view.
Position
Below the diagonal: xilem_core.environment uses a module listed above it, which is the healthy direction.
18→20 xilem_core.environment uses xilem_core.docspart of a loop✕
Connections
3 pairs of types, where a type in xilem_core.environment uses a type in xilem_core.docs.
xilem_core.environment uses xilem_core.docs, so a change to xilem_core.docs can break xilem_core.environment, while a change to xilem_core.environment can't break xilem_core.docs.
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.
masonry_core.app.render_root uses masonry_core.core.events, so a change to masonry_core.core.events can break masonry_core.app.render_root, while a change to masonry_core.app.render_root can't break masonry_core.core.events.
Position
Below the diagonal: masonry_core.app.render_root uses a module listed above it, which is the healthy direction.
masonry_core.app.render_root uses masonry_core.core.property_stack, so a change to masonry_core.core.property_stack can break masonry_core.app.render_root, while a change to masonry_core.app.render_root can't break masonry_core.core.property_stack.
Position
Below the diagonal: masonry_core.app.render_root uses a module listed above it, which is the healthy direction.
masonry_core.app.render_root uses masonry_core.core.default_properties, so a change to masonry_core.core.default_properties can break masonry_core.app.render_root, while a change to masonry_core.app.render_root can't break masonry_core.core.default_properties.
Position
Below the diagonal: masonry_core.app.render_root uses a module listed above it, which is the healthy direction.
masonry_core.app.render_root uses masonry_core.core.widget_pod, so a change to masonry_core.core.widget_pod can break masonry_core.app.render_root, while a change to masonry_core.app.render_root can't break masonry_core.core.widget_pod.
Position
Below the diagonal: masonry_core.app.render_root uses a module listed above it, which is the healthy direction.
masonry_core.app.render_root uses masonry_core.core.widget, so a change to masonry_core.core.widget can break masonry_core.app.render_root, while a change to masonry_core.app.render_root can't break masonry_core.core.widget.
Position
Below the diagonal: masonry_core.app.render_root uses a module listed above it, which is the healthy direction.
masonry_core.app.render_root uses masonry_core.core.widget_state, so a change to masonry_core.core.widget_state can break masonry_core.app.render_root, while a change to masonry_core.app.render_root can't break masonry_core.core.widget_state.
Position
Below the diagonal: masonry_core.app.render_root uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in xilem_core.docs uses a type in xilem_core.view.
The types involved
xilem_core.docs.DocsView → xilem_core.view.View
Direction
xilem_core.docs uses xilem_core.view, so a change to xilem_core.view can break xilem_core.docs, while a change to xilem_core.docs can't break xilem_core.view.
Position
Below the diagonal: xilem_core.docs uses a module listed above it, which is the healthy direction.
xilem_core.docs uses xilem_core.view_sequence, so a change to xilem_core.view_sequence can break xilem_core.docs, while a change to xilem_core.docs can't break xilem_core.view_sequence.
Position
Below the diagonal: xilem_core.docs uses a module listed above it, which is the healthy direction.
xilem_core.docs uses xilem_core.environment, so a change to xilem_core.environment can break xilem_core.docs, while a change to xilem_core.docs can't break xilem_core.environment.
Position
Below the diagonal: xilem_core.docs uses a module listed above it, which is the healthy direction.
xilem_masonry.view_ctx uses masonry_core.core.widget_mut, so a change to masonry_core.core.widget_mut can break xilem_masonry.view_ctx, while a change to xilem_masonry.view_ctx can't break masonry_core.core.widget_mut.
Position
Below the diagonal: xilem_masonry.view_ctx uses a module listed above it, which is the healthy direction.
xilem_masonry.view_ctx uses masonry_core.core.widget, so a change to masonry_core.core.widget can break xilem_masonry.view_ctx, while a change to xilem_masonry.view_ctx can't break masonry_core.core.widget.
Position
Below the diagonal: xilem_masonry.view_ctx uses a module listed above it, which is the healthy direction.
xilem_masonry.view_ctx uses xilem_core.environment, so a change to xilem_core.environment can break xilem_masonry.view_ctx, while a change to xilem_masonry.view_ctx can't break xilem_core.environment.
Position
Below the diagonal: xilem_masonry.view_ctx uses a module listed above it, which is the healthy direction.
masonry_core.core.contexts uses masonry_core.core.property_stack, so a change to masonry_core.core.property_stack can break masonry_core.core.contexts, while a change to masonry_core.core.contexts can't break masonry_core.core.property_stack.
Position
Below the diagonal: masonry_core.core.contexts uses a module listed above it, which is the healthy direction.
masonry_core.core.contexts uses masonry_core.layout.length, so a change to masonry_core.layout.length can break masonry_core.core.contexts, while a change to masonry_core.core.contexts can't break masonry_core.layout.length.
Position
Below the diagonal: masonry_core.core.contexts uses a module listed above it, which is the healthy direction.
masonry_core.core.contexts uses masonry_core.core.properties_mut, so a change to masonry_core.core.properties_mut can break masonry_core.core.contexts, while a change to masonry_core.core.contexts can't break masonry_core.core.properties_mut.
Position
Below the diagonal: masonry_core.core.contexts uses a module listed above it, which is the healthy direction.
masonry_core.core.contexts uses masonry_core.core.properties_ref, so a change to masonry_core.core.properties_ref can break masonry_core.core.contexts, while a change to masonry_core.core.contexts can't break masonry_core.core.properties_ref.
Position
Below the diagonal: masonry_core.core.contexts uses a module listed above it, which is the healthy direction.
masonry_core.core.contexts uses masonry_core.core.widget_mut, so a change to masonry_core.core.widget_mut can break masonry_core.core.contexts, while a change to masonry_core.core.contexts can't break masonry_core.core.widget_mut.
Position
Below the diagonal: masonry_core.core.contexts uses a module listed above it, which is the healthy direction.
masonry_core.core.contexts uses masonry_core.core.widget_pod, so a change to masonry_core.core.widget_pod can break masonry_core.core.contexts, while a change to masonry_core.core.contexts can't break masonry_core.core.widget_pod.
Position
Below the diagonal: masonry_core.core.contexts uses a module listed above it, which is the healthy direction.
masonry_core.core.contexts uses masonry_core.core.widget, so a change to masonry_core.core.widget can break masonry_core.core.contexts, while a change to masonry_core.core.contexts can't break masonry_core.core.widget.
Position
Below the diagonal: masonry_core.core.contexts uses a module listed above it, which is the healthy direction.
masonry_core.core.contexts uses masonry_core.core.widget_state, so a change to masonry_core.core.widget_state can break masonry_core.core.contexts, while a change to masonry_core.core.contexts can't break masonry_core.core.widget_state.
Position
Below the diagonal: masonry_core.core.contexts uses a module listed above it, which is the healthy direction.
masonry_core.core.contexts uses masonry_core.app.render_root, so a change to masonry_core.app.render_root can break masonry_core.core.contexts, while a change to masonry_core.core.contexts can't break masonry_core.app.render_root.
Position
Below the diagonal: masonry_core.core.contexts uses a module listed above it, which is the healthy direction.
xilem.window_view uses xilem_core.message, so a change to xilem_core.message can break xilem.window_view, while a change to xilem.window_view can't break xilem_core.message.
Position
Below the diagonal: xilem.window_view uses a module listed above it, which is the healthy direction.
xilem.window_view uses masonry_core.core.default_properties, so a change to masonry_core.core.default_properties can break xilem.window_view, while a change to xilem.window_view can't break masonry_core.core.default_properties.
Position
Below the diagonal: xilem.window_view uses a module listed above it, which is the healthy direction.
xilem.window_view uses xilem_core.message_context, so a change to xilem_core.message_context can break xilem.window_view, while a change to xilem.window_view can't break xilem_core.message_context.
Position
Below the diagonal: xilem.window_view uses a module listed above it, which is the healthy direction.
xilem.window_view uses xilem_core.view, so a change to xilem_core.view can break xilem.window_view, while a change to xilem.window_view can't break xilem_core.view.
Position
Below the diagonal: xilem.window_view uses a module listed above it, which is the healthy direction.
xilem.window_view uses xilem_core.docs, so a change to xilem_core.docs can break xilem.window_view, while a change to xilem.window_view can't break xilem_core.docs.
Position
Below the diagonal: xilem.window_view uses a module listed above it, which is the healthy direction.
xilem.window_view uses xilem_masonry.view_ctx, so a change to xilem_masonry.view_ctx can break xilem.window_view, while a change to xilem.window_view can't break xilem_masonry.view_ctx.
Position
Below the diagonal: xilem.window_view uses a module listed above it, which is the healthy direction.
xilem_masonry.view.grid uses xilem_core.element_splice, so a change to xilem_core.element_splice can break xilem_masonry.view.grid, while a change to xilem_masonry.view.grid can't break xilem_core.element_splice.
Position
Below the diagonal: xilem_masonry.view.grid uses a module listed above it, which is the healthy direction.
xilem_masonry.view.grid uses xilem_core.message, so a change to xilem_core.message can break xilem_masonry.view.grid, while a change to xilem_masonry.view.grid can't break xilem_core.message.
Position
Below the diagonal: xilem_masonry.view.grid uses a module listed above it, which is the healthy direction.
xilem_masonry.view.grid uses masonry_core.core.widget_mut, so a change to masonry_core.core.widget_mut can break xilem_masonry.view.grid, while a change to xilem_masonry.view.grid can't break masonry_core.core.widget_mut.
Position
Below the diagonal: xilem_masonry.view.grid uses a module listed above it, which is the healthy direction.
xilem_masonry.view.grid uses xilem_core.message_context, so a change to xilem_core.message_context can break xilem_masonry.view.grid, while a change to xilem_masonry.view.grid can't break xilem_core.message_context.
Position
Below the diagonal: xilem_masonry.view.grid uses a module listed above it, which is the healthy direction.
xilem_masonry.view.grid uses xilem_core.view, so a change to xilem_core.view can break xilem_masonry.view.grid, while a change to xilem_masonry.view.grid can't break xilem_core.view.
Position
Below the diagonal: xilem_masonry.view.grid uses a module listed above it, which is the healthy direction.
xilem_masonry.view.grid uses xilem_core.view_sequence, so a change to xilem_core.view_sequence can break xilem_masonry.view.grid, while a change to xilem_masonry.view.grid can't break xilem_core.view_sequence.
Position
Below the diagonal: xilem_masonry.view.grid uses a module listed above it, which is the healthy direction.
xilem_masonry.view.grid uses xilem_core.docs, so a change to xilem_core.docs can break xilem_masonry.view.grid, while a change to xilem_masonry.view.grid can't break xilem_core.docs.
Position
Below the diagonal: xilem_masonry.view.grid uses a module listed above it, which is the healthy direction.
xilem_masonry.view.grid uses xilem_masonry.view_ctx, so a change to xilem_masonry.view_ctx can break xilem_masonry.view.grid, while a change to xilem_masonry.view.grid can't break xilem_masonry.view_ctx.
Position
Below the diagonal: xilem_masonry.view.grid uses a module listed above it, which is the healthy direction.
xilem_masonry.view.zstack uses xilem_core.element_splice, so a change to xilem_core.element_splice can break xilem_masonry.view.zstack, while a change to xilem_masonry.view.zstack can't break xilem_core.element_splice.
Position
Below the diagonal: xilem_masonry.view.zstack uses a module listed above it, which is the healthy direction.
xilem_masonry.view.zstack uses xilem_core.message, so a change to xilem_core.message can break xilem_masonry.view.zstack, while a change to xilem_masonry.view.zstack can't break xilem_core.message.
Position
Below the diagonal: xilem_masonry.view.zstack uses a module listed above it, which is the healthy direction.
xilem_masonry.view.zstack uses masonry_core.core.widget_mut, so a change to masonry_core.core.widget_mut can break xilem_masonry.view.zstack, while a change to xilem_masonry.view.zstack can't break masonry_core.core.widget_mut.
Position
Below the diagonal: xilem_masonry.view.zstack uses a module listed above it, which is the healthy direction.
xilem_masonry.view.zstack uses xilem_core.message_context, so a change to xilem_core.message_context can break xilem_masonry.view.zstack, while a change to xilem_masonry.view.zstack can't break xilem_core.message_context.
Position
Below the diagonal: xilem_masonry.view.zstack uses a module listed above it, which is the healthy direction.
xilem_masonry.view.zstack uses xilem_core.view, so a change to xilem_core.view can break xilem_masonry.view.zstack, while a change to xilem_masonry.view.zstack can't break xilem_core.view.
Position
Below the diagonal: xilem_masonry.view.zstack uses a module listed above it, which is the healthy direction.
xilem_masonry.view.zstack uses xilem_core.view_sequence, so a change to xilem_core.view_sequence can break xilem_masonry.view.zstack, while a change to xilem_masonry.view.zstack can't break xilem_core.view_sequence.
Position
Below the diagonal: xilem_masonry.view.zstack uses a module listed above it, which is the healthy direction.
xilem_masonry.view.zstack uses xilem_core.docs, so a change to xilem_core.docs can break xilem_masonry.view.zstack, while a change to xilem_masonry.view.zstack can't break xilem_core.docs.
Position
Below the diagonal: xilem_masonry.view.zstack uses a module listed above it, which is the healthy direction.
xilem_masonry.view.zstack uses xilem_masonry.view_ctx, so a change to xilem_masonry.view_ctx can break xilem_masonry.view.zstack, while a change to xilem_masonry.view.zstack can't break xilem_masonry.view_ctx.
Position
Below the diagonal: xilem_masonry.view.zstack uses a module listed above it, which is the healthy direction.
xilem_web.context uses xilem_core.message, so a change to xilem_core.message can break xilem_web.context, while a change to xilem_web.context can't break xilem_core.message.
Position
Below the diagonal: xilem_web.context uses a module listed above it, which is the healthy direction.
xilem_web.context uses xilem_core.message_context, so a change to xilem_core.message_context can break xilem_web.context, while a change to xilem_web.context can't break xilem_core.message_context.
Position
Below the diagonal: xilem_web.context uses a module listed above it, which is the healthy direction.
xilem_web.context uses xilem_core.environment, so a change to xilem_core.environment can break xilem_web.context, while a change to xilem_web.context can't break xilem_core.environment.
Position
Below the diagonal: xilem_web.context uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in xilem_web.context uses a type in xilem_core.docs.
The types involved
xilem_web.context.ViewCtx → xilem_core.docs.State
Direction
xilem_web.context uses xilem_core.docs, so a change to xilem_core.docs can break xilem_web.context, while a change to xilem_web.context can't break xilem_core.docs.
Position
Below the diagonal: xilem_web.context uses a module listed above it, which is the healthy direction.
masonry.layers.selector_menu uses masonry_core.core.events, so a change to masonry_core.core.events can break masonry.layers.selector_menu, while a change to masonry.layers.selector_menu can't break masonry_core.core.events.
Position
Below the diagonal: masonry.layers.selector_menu uses a module listed above it, which is the healthy direction.
masonry.layers.selector_menu uses masonry_core.layout.length, so a change to masonry_core.layout.length can break masonry.layers.selector_menu, while a change to masonry.layers.selector_menu can't break masonry_core.layout.length.
Position
Below the diagonal: masonry.layers.selector_menu uses a module listed above it, which is the healthy direction.
masonry.layers.selector_menu uses masonry_core.core.properties_mut, so a change to masonry_core.core.properties_mut can break masonry.layers.selector_menu, while a change to masonry.layers.selector_menu can't break masonry_core.core.properties_mut.
Position
Below the diagonal: masonry.layers.selector_menu uses a module listed above it, which is the healthy direction.
masonry.layers.selector_menu uses masonry_core.core.properties_ref, so a change to masonry_core.core.properties_ref can break masonry.layers.selector_menu, while a change to masonry.layers.selector_menu can't break masonry_core.core.properties_ref.
Position
Below the diagonal: masonry.layers.selector_menu uses a module listed above it, which is the healthy direction.
masonry.layers.selector_menu uses masonry_core.core.widget_mut, so a change to masonry_core.core.widget_mut can break masonry.layers.selector_menu, while a change to masonry.layers.selector_menu can't break masonry_core.core.widget_mut.
Position
Below the diagonal: masonry.layers.selector_menu uses a module listed above it, which is the healthy direction.
masonry.layers.selector_menu uses masonry_core.core.widget_pod, so a change to masonry_core.core.widget_pod can break masonry.layers.selector_menu, while a change to masonry.layers.selector_menu can't break masonry_core.core.widget_pod.
Position
Below the diagonal: masonry.layers.selector_menu uses a module listed above it, which is the healthy direction.
masonry.layers.selector_menu uses masonry_core.layout.len_req, so a change to masonry_core.layout.len_req can break masonry.layers.selector_menu, while a change to masonry.layers.selector_menu can't break masonry_core.layout.len_req.
Position
Below the diagonal: masonry.layers.selector_menu uses a module listed above it, which is the healthy direction.
masonry.layers.selector_menu uses masonry_core.core.widget, so a change to masonry_core.core.widget can break masonry.layers.selector_menu, while a change to masonry.layers.selector_menu can't break masonry_core.core.widget.
Position
Below the diagonal: masonry.layers.selector_menu uses a module listed above it, which is the healthy direction.
masonry.layers.selector_menu uses masonry_core.core.property, so a change to masonry_core.core.property can break masonry.layers.selector_menu, while a change to masonry.layers.selector_menu can't break masonry_core.core.property.
Position
Below the diagonal: masonry.layers.selector_menu uses a module listed above it, which is the healthy direction.
masonry.layers.selector_menu uses masonry_core.core.contexts, so a change to masonry_core.core.contexts can break masonry.layers.selector_menu, while a change to masonry.layers.selector_menu can't break masonry_core.core.contexts.
Position
Below the diagonal: masonry.layers.selector_menu uses a module listed above it, which is the healthy direction.
masonry.layers.tooltip uses masonry_core.core.events, so a change to masonry_core.core.events can break masonry.layers.tooltip, while a change to masonry.layers.tooltip can't break masonry_core.core.events.
Position
Below the diagonal: masonry.layers.tooltip uses a module listed above it, which is the healthy direction.
masonry.layers.tooltip uses masonry_core.layout.length, so a change to masonry_core.layout.length can break masonry.layers.tooltip, while a change to masonry.layers.tooltip can't break masonry_core.layout.length.
Position
Below the diagonal: masonry.layers.tooltip uses a module listed above it, which is the healthy direction.
masonry.layers.tooltip uses masonry_core.core.properties_mut, so a change to masonry_core.core.properties_mut can break masonry.layers.tooltip, while a change to masonry.layers.tooltip can't break masonry_core.core.properties_mut.
Position
Below the diagonal: masonry.layers.tooltip uses a module listed above it, which is the healthy direction.
masonry.layers.tooltip uses masonry_core.core.properties_ref, so a change to masonry_core.core.properties_ref can break masonry.layers.tooltip, while a change to masonry.layers.tooltip can't break masonry_core.core.properties_ref.
Position
Below the diagonal: masonry.layers.tooltip uses a module listed above it, which is the healthy direction.
masonry.layers.tooltip uses masonry_core.core.widget_mut, so a change to masonry_core.core.widget_mut can break masonry.layers.tooltip, while a change to masonry.layers.tooltip can't break masonry_core.core.widget_mut.
Position
Below the diagonal: masonry.layers.tooltip uses a module listed above it, which is the healthy direction.
masonry.layers.tooltip uses masonry_core.core.widget_pod, so a change to masonry_core.core.widget_pod can break masonry.layers.tooltip, while a change to masonry.layers.tooltip can't break masonry_core.core.widget_pod.
Position
Below the diagonal: masonry.layers.tooltip uses a module listed above it, which is the healthy direction.
masonry.layers.tooltip uses masonry_core.layout.len_req, so a change to masonry_core.layout.len_req can break masonry.layers.tooltip, while a change to masonry.layers.tooltip can't break masonry_core.layout.len_req.
Position
Below the diagonal: masonry.layers.tooltip uses a module listed above it, which is the healthy direction.
masonry.layers.tooltip uses masonry_core.core.widget, so a change to masonry_core.core.widget can break masonry.layers.tooltip, while a change to masonry.layers.tooltip can't break masonry_core.core.widget.
Position
Below the diagonal: masonry.layers.tooltip uses a module listed above it, which is the healthy direction.
masonry.layers.tooltip uses masonry_core.core.contexts, so a change to masonry_core.core.contexts can break masonry.layers.tooltip, while a change to masonry.layers.tooltip can't break masonry_core.core.contexts.
Position
Below the diagonal: masonry.layers.tooltip uses a module listed above it, which is the healthy direction.
masonry.widgets.badge uses masonry_core.core.events, so a change to masonry_core.core.events can break masonry.widgets.badge, while a change to masonry.widgets.badge can't break masonry_core.core.events.
Position
Below the diagonal: masonry.widgets.badge uses a module listed above it, which is the healthy direction.
masonry.widgets.badge uses masonry_core.layout.length, so a change to masonry_core.layout.length can break masonry.widgets.badge, while a change to masonry.widgets.badge can't break masonry_core.layout.length.
Position
Below the diagonal: masonry.widgets.badge uses a module listed above it, which is the healthy direction.
masonry.widgets.badge uses masonry_core.core.properties_mut, so a change to masonry_core.core.properties_mut can break masonry.widgets.badge, while a change to masonry.widgets.badge can't break masonry_core.core.properties_mut.
Position
Below the diagonal: masonry.widgets.badge uses a module listed above it, which is the healthy direction.
masonry.widgets.badge uses masonry_core.core.properties_ref, so a change to masonry_core.core.properties_ref can break masonry.widgets.badge, while a change to masonry.widgets.badge can't break masonry_core.core.properties_ref.
Position
Below the diagonal: masonry.widgets.badge uses a module listed above it, which is the healthy direction.
masonry.widgets.badge uses masonry_core.core.widget_mut, so a change to masonry_core.core.widget_mut can break masonry.widgets.badge, while a change to masonry.widgets.badge can't break masonry_core.core.widget_mut.
Position
Below the diagonal: masonry.widgets.badge uses a module listed above it, which is the healthy direction.
masonry.widgets.badge uses masonry_core.core.widget_pod, so a change to masonry_core.core.widget_pod can break masonry.widgets.badge, while a change to masonry.widgets.badge can't break masonry_core.core.widget_pod.
Position
Below the diagonal: masonry.widgets.badge uses a module listed above it, which is the healthy direction.
masonry.widgets.badge uses masonry_core.layout.len_req, so a change to masonry_core.layout.len_req can break masonry.widgets.badge, while a change to masonry.widgets.badge can't break masonry_core.layout.len_req.
Position
Below the diagonal: masonry.widgets.badge uses a module listed above it, which is the healthy direction.
masonry.widgets.badge uses masonry_core.core.widget, so a change to masonry_core.core.widget can break masonry.widgets.badge, while a change to masonry.widgets.badge can't break masonry_core.core.widget.
Position
Below the diagonal: masonry.widgets.badge uses a module listed above it, which is the healthy direction.
masonry.widgets.badge uses masonry_core.core.contexts, so a change to masonry_core.core.contexts can break masonry.widgets.badge, while a change to masonry.widgets.badge can't break masonry_core.core.contexts.
Position
Below the diagonal: masonry.widgets.badge uses a module listed above it, which is the healthy direction.
masonry.widgets.divider uses masonry_core.core.events, so a change to masonry_core.core.events can break masonry.widgets.divider, while a change to masonry.widgets.divider can't break masonry_core.core.events.
Position
Below the diagonal: masonry.widgets.divider uses a module listed above it, which is the healthy direction.
masonry.widgets.divider uses masonry_core.layout.length, so a change to masonry_core.layout.length can break masonry.widgets.divider, while a change to masonry.widgets.divider can't break masonry_core.layout.length.
Position
Below the diagonal: masonry.widgets.divider uses a module listed above it, which is the healthy direction.
masonry.widgets.divider uses masonry_core.core.properties_mut, so a change to masonry_core.core.properties_mut can break masonry.widgets.divider, while a change to masonry.widgets.divider can't break masonry_core.core.properties_mut.
Position
Below the diagonal: masonry.widgets.divider uses a module listed above it, which is the healthy direction.
masonry.widgets.divider uses masonry_core.core.properties_ref, so a change to masonry_core.core.properties_ref can break masonry.widgets.divider, while a change to masonry.widgets.divider can't break masonry_core.core.properties_ref.
Position
Below the diagonal: masonry.widgets.divider uses a module listed above it, which is the healthy direction.
masonry.widgets.divider uses masonry_core.core.widget_mut, so a change to masonry_core.core.widget_mut can break masonry.widgets.divider, while a change to masonry.widgets.divider can't break masonry_core.core.widget_mut.
Position
Below the diagonal: masonry.widgets.divider uses a module listed above it, which is the healthy direction.
masonry.widgets.divider uses masonry_core.core.widget_pod, so a change to masonry_core.core.widget_pod can break masonry.widgets.divider, while a change to masonry.widgets.divider can't break masonry_core.core.widget_pod.
Position
Below the diagonal: masonry.widgets.divider uses a module listed above it, which is the healthy direction.
masonry.widgets.divider uses masonry_core.layout.len_req, so a change to masonry_core.layout.len_req can break masonry.widgets.divider, while a change to masonry.widgets.divider can't break masonry_core.layout.len_req.
Position
Below the diagonal: masonry.widgets.divider uses a module listed above it, which is the healthy direction.
masonry.widgets.divider uses masonry_core.core.widget, so a change to masonry_core.core.widget can break masonry.widgets.divider, while a change to masonry.widgets.divider can't break masonry_core.core.widget.
Position
Below the diagonal: masonry.widgets.divider uses a module listed above it, which is the healthy direction.
masonry.widgets.divider uses masonry_core.core.property, so a change to masonry_core.core.property can break masonry.widgets.divider, while a change to masonry.widgets.divider can't break masonry_core.core.property.
Position
Below the diagonal: masonry.widgets.divider uses a module listed above it, which is the healthy direction.
masonry.widgets.divider uses masonry_core.core.contexts, so a change to masonry_core.core.contexts can break masonry.widgets.divider, while a change to masonry.widgets.divider can't break masonry_core.core.contexts.
Position
Below the diagonal: masonry.widgets.divider uses a module listed above it, which is the healthy direction.
masonry.widgets.flex uses masonry_core.layout.length, so a change to masonry_core.layout.length can break masonry.widgets.flex, while a change to masonry.widgets.flex can't break masonry_core.layout.length.
Position
Below the diagonal: masonry.widgets.flex uses a module listed above it, which is the healthy direction.
masonry.widgets.flex uses masonry_core.core.properties_ref, so a change to masonry_core.core.properties_ref can break masonry.widgets.flex, while a change to masonry.widgets.flex can't break masonry_core.core.properties_ref.
Position
Below the diagonal: masonry.widgets.flex uses a module listed above it, which is the healthy direction.
masonry.widgets.flex uses masonry_core.core.widget_mut, so a change to masonry_core.core.widget_mut can break masonry.widgets.flex, while a change to masonry.widgets.flex can't break masonry_core.core.widget_mut.
Position
Below the diagonal: masonry.widgets.flex uses a module listed above it, which is the healthy direction.
masonry.widgets.flex uses masonry_core.core.widget_pod, so a change to masonry_core.core.widget_pod can break masonry.widgets.flex, while a change to masonry.widgets.flex can't break masonry_core.core.widget_pod.
Position
Below the diagonal: masonry.widgets.flex uses a module listed above it, which is the healthy direction.
masonry.widgets.flex uses masonry_core.layout.len_req, so a change to masonry_core.layout.len_req can break masonry.widgets.flex, while a change to masonry.widgets.flex can't break masonry_core.layout.len_req.
Position
Below the diagonal: masonry.widgets.flex uses a module listed above it, which is the healthy direction.
masonry.widgets.flex uses masonry_core.core.widget, so a change to masonry_core.core.widget can break masonry.widgets.flex, while a change to masonry.widgets.flex can't break masonry_core.core.widget.
Position
Below the diagonal: masonry.widgets.flex uses a module listed above it, which is the healthy direction.
masonry.widgets.flex uses masonry_core.core.property, so a change to masonry_core.core.property can break masonry.widgets.flex, while a change to masonry.widgets.flex can't break masonry_core.core.property.
Position
Below the diagonal: masonry.widgets.flex uses a module listed above it, which is the healthy direction.
masonry.widgets.flex uses masonry_core.core.contexts, so a change to masonry_core.core.contexts can break masonry.widgets.flex, while a change to masonry.widgets.flex can't break masonry_core.core.contexts.
Position
Below the diagonal: masonry.widgets.flex uses a module listed above it, which is the healthy direction.
masonry.widgets.virtual_scroll uses masonry_core.core.events, so a change to masonry_core.core.events can break masonry.widgets.virtual_scroll, while a change to masonry.widgets.virtual_scroll can't break masonry_core.core.events.
Position
Below the diagonal: masonry.widgets.virtual_scroll uses a module listed above it, which is the healthy direction.
masonry.widgets.virtual_scroll uses masonry_core.layout.length, so a change to masonry_core.layout.length can break masonry.widgets.virtual_scroll, while a change to masonry.widgets.virtual_scroll can't break masonry_core.layout.length.
Position
Below the diagonal: masonry.widgets.virtual_scroll uses a module listed above it, which is the healthy direction.
masonry.widgets.virtual_scroll uses masonry_core.core.properties_mut, so a change to masonry_core.core.properties_mut can break masonry.widgets.virtual_scroll, while a change to masonry.widgets.virtual_scroll can't break masonry_core.core.properties_mut.
Position
Below the diagonal: masonry.widgets.virtual_scroll uses a module listed above it, which is the healthy direction.
masonry.widgets.virtual_scroll uses masonry_core.core.properties_ref, so a change to masonry_core.core.properties_ref can break masonry.widgets.virtual_scroll, while a change to masonry.widgets.virtual_scroll can't break masonry_core.core.properties_ref.
Position
Below the diagonal: masonry.widgets.virtual_scroll uses a module listed above it, which is the healthy direction.
masonry.widgets.virtual_scroll uses masonry_core.core.widget_mut, so a change to masonry_core.core.widget_mut can break masonry.widgets.virtual_scroll, while a change to masonry.widgets.virtual_scroll can't break masonry_core.core.widget_mut.
Position
Below the diagonal: masonry.widgets.virtual_scroll uses a module listed above it, which is the healthy direction.
masonry.widgets.virtual_scroll uses masonry_core.core.widget_pod, so a change to masonry_core.core.widget_pod can break masonry.widgets.virtual_scroll, while a change to masonry.widgets.virtual_scroll can't break masonry_core.core.widget_pod.
Position
Below the diagonal: masonry.widgets.virtual_scroll uses a module listed above it, which is the healthy direction.
masonry.widgets.virtual_scroll uses masonry_core.layout.len_req, so a change to masonry_core.layout.len_req can break masonry.widgets.virtual_scroll, while a change to masonry.widgets.virtual_scroll can't break masonry_core.layout.len_req.
Position
Below the diagonal: masonry.widgets.virtual_scroll uses a module listed above it, which is the healthy direction.
masonry.widgets.virtual_scroll uses masonry_core.core.widget, so a change to masonry_core.core.widget can break masonry.widgets.virtual_scroll, while a change to masonry.widgets.virtual_scroll can't break masonry_core.core.widget.
Position
Below the diagonal: masonry.widgets.virtual_scroll uses a module listed above it, which is the healthy direction.
masonry.widgets.virtual_scroll uses masonry_core.core.contexts, so a change to masonry_core.core.contexts can break masonry.widgets.virtual_scroll, while a change to masonry.widgets.virtual_scroll can't break masonry_core.core.contexts.
Position
Below the diagonal: masonry.widgets.virtual_scroll uses a module listed above it, which is the healthy direction.
masonry_testing.recorder_widget uses masonry_core.core.events, so a change to masonry_core.core.events can break masonry_testing.recorder_widget, while a change to masonry_testing.recorder_widget can't break masonry_core.core.events.
Position
Below the diagonal: masonry_testing.recorder_widget uses a module listed above it, which is the healthy direction.
masonry_testing.recorder_widget uses masonry_core.layout.length, so a change to masonry_core.layout.length can break masonry_testing.recorder_widget, while a change to masonry_testing.recorder_widget can't break masonry_core.layout.length.
Position
Below the diagonal: masonry_testing.recorder_widget uses a module listed above it, which is the healthy direction.
masonry_testing.recorder_widget uses masonry_core.core.properties_mut, so a change to masonry_core.core.properties_mut can break masonry_testing.recorder_widget, while a change to masonry_testing.recorder_widget can't break masonry_core.core.properties_mut.
Position
Below the diagonal: masonry_testing.recorder_widget uses a module listed above it, which is the healthy direction.
masonry_testing.recorder_widget uses masonry_core.core.properties_ref, so a change to masonry_core.core.properties_ref can break masonry_testing.recorder_widget, while a change to masonry_testing.recorder_widget can't break masonry_core.core.properties_ref.
Position
Below the diagonal: masonry_testing.recorder_widget uses a module listed above it, which is the healthy direction.
masonry_testing.recorder_widget uses masonry_core.core.widget_pod, so a change to masonry_core.core.widget_pod can break masonry_testing.recorder_widget, while a change to masonry_testing.recorder_widget can't break masonry_core.core.widget_pod.
Position
Below the diagonal: masonry_testing.recorder_widget uses a module listed above it, which is the healthy direction.
masonry_testing.recorder_widget uses masonry_core.layout.len_req, so a change to masonry_core.layout.len_req can break masonry_testing.recorder_widget, while a change to masonry_testing.recorder_widget can't break masonry_core.layout.len_req.
Position
Below the diagonal: masonry_testing.recorder_widget uses a module listed above it, which is the healthy direction.
masonry_testing.recorder_widget uses masonry_core.core.widget, so a change to masonry_core.core.widget can break masonry_testing.recorder_widget, while a change to masonry_testing.recorder_widget can't break masonry_core.core.widget.
Position
Below the diagonal: masonry_testing.recorder_widget uses a module listed above it, which is the healthy direction.
masonry_testing.recorder_widget uses masonry_core.core.contexts, so a change to masonry_core.core.contexts can break masonry_testing.recorder_widget, while a change to masonry_testing.recorder_widget can't break masonry_core.core.contexts.
Position
Below the diagonal: masonry_testing.recorder_widget uses a module listed above it, which is the healthy direction.
xilem.driver uses xilem_core.message, so a change to xilem_core.message can break xilem.driver, while a change to xilem.driver can't break xilem_core.message.
Position
Below the diagonal: xilem.driver uses a module listed above it, which is the healthy direction.
xilem.driver uses masonry_core.core.widget, so a change to masonry_core.core.widget can break xilem.driver, while a change to xilem.driver can't break masonry_core.core.widget.
Position
Below the diagonal: xilem.driver uses a module listed above it, which is the healthy direction.
xilem.driver uses xilem_masonry.view_ctx, so a change to xilem_masonry.view_ctx can break xilem.driver, while a change to xilem.driver can't break xilem_masonry.view_ctx.
Position
Below the diagonal: xilem.driver uses a module listed above it, which is the healthy direction.
xilem.driver uses xilem.window_view, so a change to xilem.window_view can break xilem.driver, while a change to xilem.driver can't break xilem.window_view.
Position
Below the diagonal: xilem.driver uses a module listed above it, which is the healthy direction.
xilem_web.elements.html uses xilem_core.element_splice, so a change to xilem_core.element_splice can break xilem_web.elements.html, while a change to xilem_web.elements.html can't break xilem_core.element_splice.
Position
Below the diagonal: xilem_web.elements.html uses a module listed above it, which is the healthy direction.
105 pairs of types, where a type in xilem_web.elements.html uses a type in xilem_core.message. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
xilem_web.elements.html uses xilem_core.message, so a change to xilem_core.message can break xilem_web.elements.html, while a change to xilem_web.elements.html can't break xilem_core.message.
Position
Below the diagonal: xilem_web.elements.html uses a module listed above it, which is the healthy direction.
105 pairs of types, where a type in xilem_web.elements.html uses a type in xilem_core.message_context. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
xilem_web.elements.html uses xilem_core.message_context, so a change to xilem_core.message_context can break xilem_web.elements.html, while a change to xilem_web.elements.html can't break xilem_core.message_context.
Position
Below the diagonal: xilem_web.elements.html uses a module listed above it, which is the healthy direction.
210 pairs of types, where a type in xilem_web.elements.html uses a type in xilem_core.view. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
xilem_web.elements.html uses xilem_core.view, so a change to xilem_core.view can break xilem_web.elements.html, while a change to xilem_web.elements.html can't break xilem_core.view.
Position
Below the diagonal: xilem_web.elements.html uses a module listed above it, which is the healthy direction.
105 pairs of types, where a type in xilem_web.elements.html uses a type in xilem_core.docs. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
xilem_web.elements.html uses xilem_core.docs, so a change to xilem_core.docs can break xilem_web.elements.html, while a change to xilem_web.elements.html can't break xilem_core.docs.
Position
Below the diagonal: xilem_web.elements.html uses a module listed above it, which is the healthy direction.
105 pairs of types, where a type in xilem_web.elements.html uses a type in xilem_web.context. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
xilem_web.elements.html uses xilem_web.context, so a change to xilem_web.context can break xilem_web.elements.html, while a change to xilem_web.elements.html can't break xilem_web.context.
Position
Below the diagonal: xilem_web.elements.html uses a module listed above it, which is the healthy direction.
xilem_web.modifiers.attribute uses xilem_core.message, so a change to xilem_core.message can break xilem_web.modifiers.attribute, while a change to xilem_web.modifiers.attribute can't break xilem_core.message.
Position
Below the diagonal: xilem_web.modifiers.attribute uses a module listed above it, which is the healthy direction.
xilem_web.modifiers.attribute uses xilem_core.message_context, so a change to xilem_core.message_context can break xilem_web.modifiers.attribute, while a change to xilem_web.modifiers.attribute can't break xilem_core.message_context.
Position
Below the diagonal: xilem_web.modifiers.attribute uses a module listed above it, which is the healthy direction.
xilem_web.modifiers.attribute uses xilem_core.view, so a change to xilem_core.view can break xilem_web.modifiers.attribute, while a change to xilem_web.modifiers.attribute can't break xilem_core.view.
Position
Below the diagonal: xilem_web.modifiers.attribute uses a module listed above it, which is the healthy direction.
xilem_web.modifiers.attribute uses xilem_core.docs, so a change to xilem_core.docs can break xilem_web.modifiers.attribute, while a change to xilem_web.modifiers.attribute can't break xilem_core.docs.
Position
Below the diagonal: xilem_web.modifiers.attribute uses a module listed above it, which is the healthy direction.
xilem_web.modifiers.attribute uses xilem_web.context, so a change to xilem_web.context can break xilem_web.modifiers.attribute, while a change to xilem_web.modifiers.attribute can't break xilem_web.context.
Position
Below the diagonal: xilem_web.modifiers.attribute uses a module listed above it, which is the healthy direction.
36→40 xilem_web.modifiers.attribute uses xilem_web.interfacespart of a loop✕
Connections
2 pairs of types, where a type in xilem_web.modifiers.attribute uses a type in xilem_web.interfaces.
xilem_web.modifiers.attribute uses xilem_web.interfaces, so a change to xilem_web.interfaces can break xilem_web.modifiers.attribute, while a change to xilem_web.modifiers.attribute can't break xilem_web.interfaces.
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 xilem_web.pod uses a type in xilem_web.context.
The types involved
xilem_web.pod.Pod → xilem_web.context.ViewCtx
Direction
xilem_web.pod uses xilem_web.context, so a change to xilem_web.context can break xilem_web.pod, while a change to xilem_web.pod can't break xilem_web.context.
Position
Below the diagonal: xilem_web.pod uses a module listed above it, which is the healthy direction.
xilem_masonry.view.flex uses xilem_core.element_splice, so a change to xilem_core.element_splice can break xilem_masonry.view.flex, while a change to xilem_masonry.view.flex can't break xilem_core.element_splice.
Position
Below the diagonal: xilem_masonry.view.flex uses a module listed above it, which is the healthy direction.
xilem_masonry.view.flex uses xilem_core.message, so a change to xilem_core.message can break xilem_masonry.view.flex, while a change to xilem_masonry.view.flex can't break xilem_core.message.
Position
Below the diagonal: xilem_masonry.view.flex uses a module listed above it, which is the healthy direction.
xilem_masonry.view.flex uses masonry_core.core.widget_mut, so a change to masonry_core.core.widget_mut can break xilem_masonry.view.flex, while a change to xilem_masonry.view.flex can't break masonry_core.core.widget_mut.
Position
Below the diagonal: xilem_masonry.view.flex uses a module listed above it, which is the healthy direction.
xilem_masonry.view.flex uses xilem_core.message_context, so a change to xilem_core.message_context can break xilem_masonry.view.flex, while a change to xilem_masonry.view.flex can't break xilem_core.message_context.
Position
Below the diagonal: xilem_masonry.view.flex uses a module listed above it, which is the healthy direction.
xilem_masonry.view.flex uses xilem_core.view, so a change to xilem_core.view can break xilem_masonry.view.flex, while a change to xilem_masonry.view.flex can't break xilem_core.view.
Position
Below the diagonal: xilem_masonry.view.flex uses a module listed above it, which is the healthy direction.
xilem_masonry.view.flex uses xilem_core.view_sequence, so a change to xilem_core.view_sequence can break xilem_masonry.view.flex, while a change to xilem_masonry.view.flex can't break xilem_core.view_sequence.
Position
Below the diagonal: xilem_masonry.view.flex uses a module listed above it, which is the healthy direction.
xilem_masonry.view.flex uses xilem_core.docs, so a change to xilem_core.docs can break xilem_masonry.view.flex, while a change to xilem_masonry.view.flex can't break xilem_core.docs.
Position
Below the diagonal: xilem_masonry.view.flex uses a module listed above it, which is the healthy direction.
xilem_masonry.view.flex uses xilem_masonry.view_ctx, so a change to xilem_masonry.view_ctx can break xilem_masonry.view.flex, while a change to xilem_masonry.view.flex can't break xilem_masonry.view_ctx.
Position
Below the diagonal: xilem_masonry.view.flex uses a module listed above it, which is the healthy direction.
xilem_masonry.view.flex uses masonry.widgets.flex, so a change to masonry.widgets.flex can break xilem_masonry.view.flex, while a change to xilem_masonry.view.flex can't break masonry.widgets.flex.
Position
Below the diagonal: xilem_masonry.view.flex uses a module listed above it, which is the healthy direction.
xilem_web.modifiers.style uses xilem_core.message, so a change to xilem_core.message can break xilem_web.modifiers.style, while a change to xilem_web.modifiers.style can't break xilem_core.message.
Position
Below the diagonal: xilem_web.modifiers.style uses a module listed above it, which is the healthy direction.
xilem_web.modifiers.style uses xilem_core.message_context, so a change to xilem_core.message_context can break xilem_web.modifiers.style, while a change to xilem_web.modifiers.style can't break xilem_core.message_context.
Position
Below the diagonal: xilem_web.modifiers.style uses a module listed above it, which is the healthy direction.
xilem_web.modifiers.style uses xilem_core.view, so a change to xilem_core.view can break xilem_web.modifiers.style, while a change to xilem_web.modifiers.style can't break xilem_core.view.
Position
Below the diagonal: xilem_web.modifiers.style uses a module listed above it, which is the healthy direction.
xilem_web.modifiers.style uses xilem_core.docs, so a change to xilem_core.docs can break xilem_web.modifiers.style, while a change to xilem_web.modifiers.style can't break xilem_core.docs.
Position
Below the diagonal: xilem_web.modifiers.style uses a module listed above it, which is the healthy direction.
xilem_web.modifiers.style uses xilem_web.context, so a change to xilem_web.context can break xilem_web.modifiers.style, while a change to xilem_web.modifiers.style can't break xilem_web.context.
Position
Below the diagonal: xilem_web.modifiers.style uses a module listed above it, which is the healthy direction.
xilem_web.modifiers.style uses xilem_web.elements.html, so a change to xilem_web.elements.html can break xilem_web.modifiers.style, while a change to xilem_web.modifiers.style can't break xilem_web.elements.html.
Position
Below the diagonal: xilem_web.modifiers.style uses a module listed above it, which is the healthy direction.
39→40 xilem_web.modifiers.style uses xilem_web.interfacespart of a loop✕
Connections
2 pairs of types, where a type in xilem_web.modifiers.style uses a type in xilem_web.interfaces.
xilem_web.modifiers.style uses xilem_web.interfaces, so a change to xilem_web.interfaces can break xilem_web.modifiers.style, while a change to xilem_web.modifiers.style can't break xilem_web.interfaces.
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.
xilem_web.interfaces uses xilem_web.modifiers.attribute, so a change to xilem_web.modifiers.attribute can break xilem_web.interfaces, while a change to xilem_web.interfaces can't break xilem_web.modifiers.attribute.
Position
Below the diagonal: xilem_web.interfaces uses a module listed above it, which is the healthy direction.
129 pairs of types, where a type in xilem_web.interfaces uses a type in xilem_web.pod. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
xilem_web.interfaces uses xilem_web.pod, so a change to xilem_web.pod can break xilem_web.interfaces, while a change to xilem_web.interfaces can't break xilem_web.pod.
Position
Below the diagonal: xilem_web.interfaces uses a module listed above it, which is the healthy direction.
xilem_web.interfaces uses xilem_web.modifiers.style, so a change to xilem_web.modifiers.style can break xilem_web.interfaces, while a change to xilem_web.interfaces can't break xilem_web.modifiers.style.
Position
Below the diagonal: xilem_web.interfaces uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
41
High / Critical
A03:2025 — Software Supply Chain Failures
22
High / Critical
Roadmap
Top priorities: Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1; Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh; Interpolated log message defeats structured logging.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
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.
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 — 49
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 — 722
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 — 132
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 22
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.8, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 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, 875 of 903 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 94 test files), but it was not re-run: its build outgrew the 6 GB scratch ceiling (6.705 GB measured) and was stopped; its suite was not run. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
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 reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — 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. 21 further occurrence(s) are not listed individually; the score already reflects all 61.
X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
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.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
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.
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.
15 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was TextArea::on_text_event at 61. A further 5 function(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being OneOf::rebuild at 27 — they are counted neither in the figure above nor in this dimension's score. 4 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: xilem_core/src/views/one_of.rs (OneOf::rebuild at 27), masonry_testing/src/harness.rs (TestHarness::process_signals at 24), masonry_core/src/core/events.rs (AccessEvent::short_name at 22), xilem_masonry/src/one_of.rs (ViewCtx::update_one_of_element_mut at 17). 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.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with TextArea::on_text_event (cyclomatic 61), masonry_core::passes::update::run_update_pointer_pass (cyclomatic 35), Grid::resolve_track_lengths (cyclomatic 33). — 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 4 together lifts Cyclomatic Complexity from 7.3 to about 8.1/10, projected with the scoring formula itself and assuming each lands exactly at 30; 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.
+ 8 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with TextArea::on_text_event (cognitive 109), placehero::html_content::status_html_to_plaintext (cognitive 80). — 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.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: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.6 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 12 FileTooLong finding(s) in God Classes — start with interfaces.rs, contexts.rs, step_input.rs. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 9 ClassTooLong finding(s) in God Classes — start with step_input.rs, flex.rs, text_area.rs. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 6 MethodTooLong finding(s) in God Classes — start with flex.rs (2), text_area.rs, grid.rs. — One of this dimension's main actionable groups (6 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.
76 duplicated block group(s) detected. 5.1 % of the production lines (3,511 of 68,211) are in a reported copy. A further 81 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 2 of the 157 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
+ 75 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with prose.rs, event.rs, attribute.rs. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 6 Edited copy of a member (13 corresponding lines) finding(s) in Code Duplication — start with one_of.rs, flex.rs, texture_render.rs. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 6 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with class.rs (2), flex.rs, widget_mut.rs. — One of this dimension's main actionable groups (6 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.3 / 10Stronggated by 1 serious finding✓ 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.
12 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 10 of the 12 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: masonry_imaging
What to do
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 9 Low cohesion finding(s) in Cohesion (LCOM4) — start with color_rectangle.rs, modular_widget.rs, checkbox.rs. — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
18 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
Outdated: anyhow · ×18
✓ On the Gold path — maintain.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 624 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. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with layout.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.
Do you agree with this assessment?
D16 · Bus Factor9.6 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
9 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is masonry_imaging/src/texture_render.rs. Counted over 213 of the 282 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1 · ×2
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D17 · Explicit Debt8.7 / 10Strong✓ Tool-verified
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.
440 deducted task-comment markers across 68211 LoC (0.6/KLoC) → score 8.7. 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.
Resolve the 412 TodoComment finding(s) in Explicit Debt — start with lib.rs (31), environment.rs (19), text_area.rs (15). — One of this dimension's main actionable groups (412 warning-level).
Resolve the 16 FixmeComment finding(s) in Explicit Debt — start with text_input.rs (3), selector_menu.rs (3), contexts.rs (2). — One of this dimension's main actionable groups (16 warning-level).
Resolve the 12 HackComment finding(s) in Explicit Debt — start with text_area.rs (4), elements.rs, worker.rs. — One of this dimension's main actionable groups (12 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 28 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
1 of 12 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).
41 finding(s): 0 critical, 39 high, 0 medium, 2 low. 38 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 19 file(s) — `masonry/src/layers/selector_menu.rs` (line 36, line 68, line 84, …), `masonry/src/layers/tooltip.rs` (line 26, line 36), `masonry/src/widgets/align.rs` (line 45, line 55, line 60, …), `masonry/src/widgets/badge.rs` (line 74, line 135), `masonry/src/widgets/badged.rs` (line 69, line 70, line 84, …), … (+14 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
No action in Static Analysis (SAST) — all 38 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (38 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. 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 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 7 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (7). — One of this dimension's main actionable groups (7 warning-level).
Resolve the 7 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (7). — One of this dimension's main actionable groups (7 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.
67 of 213 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is xilem_web/src/interfaces.rs. Counted over 213 of the 282 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 61 Orphaned file finding(s) in Knowledge Freshness — start with main.rs (6), element.rs (2), overwrite.rs. — One of this dimension's main actionable groups (61 recommendation-level).
Resolve the 6 Orphaned knowledge finding(s) in Knowledge Freshness — start with interfaces.rs, elements.rs, environment.rs. — One of this dimension's main actionable groups (6 issue-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with label.rs. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 8 Change coupling finding(s) in Change Coupling — start with label.rs (2), modular_widget.rs, harness.rs. — One of this dimension's main actionable groups (8 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.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Do you agree with this assessment?
AC3 · Page structure3.5 / 10Weak✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — xilem_web/web_examples/counter_custom_element/index.html:2
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×2) — xilem_web/web_examples/counter_custom_element/index.html:2, REDACTED:2
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`.color>input[type=radio]+div` moves (`transition: transform 0.3s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — xilem_web/web_examples/svgdraw/index.html:26
`.learn-bar > .learn` moves (`transition-property: left`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — REDACTED:135
`:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — REDACTED:187
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
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.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability6.2 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 14/19 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `xilem_web/web_examples/counter`, `xilem_web/web_examples/counter_custom_element`, `xilem_web/web_examples/mathml_svg`, `xilem_web/web_examples/svgdraw`, `xilem_web/web_examples/svgtoy`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
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.
Do you agree with this assessment?
P6 · Release Hygiene8.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
The changelog this check read carries 0 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.
What to do
Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub.
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.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`error!` at line 247 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — xilem_masonry/src/view/button.rs:247
`error!` at line 120 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — xilem_masonry/src/view/canvas.rs:120
`error!` at line 178 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — xilem_masonry/src/view/checkbox.rs:178
`error!` at line 138 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — xilem_masonry/src/view/radio_button.rs:138
`error!` at line 169 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — xilem_masonry/src/view/resize_observer.rs:169
`error!` at line 128 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — xilem_masonry/src/view/slider.rs:128
`error!` at line 309 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — xilem_masonry/src/view/split.rs:309
`error!` at line 119 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — xilem_masonry/src/view/switch.rs:119
`error!` at line 418 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — xilem_masonry/src/view/virtual_scroll.rs:418
`warn!` at line 582 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — xilem_core/src/environment.rs:582
`error!` at line 318 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — xilem/src/driver.rs:318
`warn!` at line 126 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — placehero/src/avatars.rs:126
`warn!` at line 44 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — placehero/src/html_content.rs:44
`warn!` at line 59 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — placehero/src/html_content.rs:59
`warn!` at line 183 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — placehero/src/html_content.rs:183
`error!` at line 377 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — placehero/src/lib.rs:377
`info!` at line 79 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — placehero/src/components/media.rs:79
`error!` at line 738 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — masonry_winit/src/event_loop_runner.rs:738
`error!` at line 763 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — masonry_winit/src/event_loop_runner.rs:763
`error!` at line 771 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — masonry_winit/src/event_loop_runner.rs:771
`warn!` at line 824 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — masonry_winit/src/event_loop_runner.rs:824
`trace!` at line 1050 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — masonry_winit/src/event_loop_runner.rs:1050
`info!` at line 1125 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — masonry_winit/src/event_loop_runner.rs:1125
`debug!` at line 624 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — masonry_testing/src/harness.rs:624
`debug!` at line 1096 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — masonry_testing/src/harness.rs:1096
`trace!` at line 38 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — masonry_core/src/passes/accessibility.rs:38
`trace!` at line 63 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — masonry_core/src/passes/accessibility.rs:63
`debug!` at line 75 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — masonry_core/src/passes/action.rs:75
`trace!` at line 120 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — masonry_core/src/passes/event.rs:120
`trace!` at line 152 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — masonry_core/src/passes/event.rs:152
`trace!` at line 289 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — masonry_core/src/passes/event.rs:289
`trace!` at line 368 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — masonry_core/src/passes/event.rs:368
`trace!` at line 375 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — masonry_core/src/passes/layout.rs:375
`trace!` at line 441 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — masonry_core/src/passes/layout.rs:441
`warn!` at line 160 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — masonry_core/src/passes/mod.rs:160
`trace!` at line 101 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — masonry_core/src/passes/paint.rs:101
`trace!` at line 189 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — masonry_core/src/passes/update.rs:189
`trace!` at line 704 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — masonry_core/src/passes/update.rs:704
`trace!` at line 705 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — masonry_core/src/passes/update.rs:705
`trace!` at line 878 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — masonry_core/src/passes/update.rs:878
Statically assessed 10 of 55 WCAG 2.2 Level A/AA success criteria (18%; ≈20% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 45 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 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.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 69 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — 11 markup documents under demonstration, documentation or developer-tool trees (or modules the build marks non-production) but none in the product; no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — those pages are demos or docs for the code, not something this tier can 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 — ~12493 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — D21 withholds its sibling role token rows: 2 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 .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — Rust suite
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (46 value object(s))
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
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — 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 Rust source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
S1 Web-Security Posture — No web surface: 263 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
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.
Orphaned knowledge xilem_web/src/interfaces.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge xilem_web/src/elements.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge xilem_core/src/environment.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge xilem_web/src/modifiers/style.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge xilem_core/src/views/one_of.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge xilem_web/src/events.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
<html> without a lang xilem_web/web_examples/counter_custom_element/index.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
Boundary-crossing change coupling: label.rs ↔ prose.rs masonry/src/widgets/label.rs:1— `masonry/src/widgets/label.rs` (context masonry) and `xilem_masonry/src/view/prose.rs` (context xilem_masonry) sit in DIFFERENT parts of the tree yet 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) — 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 9 shared commits counted here, the most recent 3 are `07bf193f` Merge `TextColor` and `SpinnerColor` into `ContentColor`. (#1295) (at that commit the file was still `xilem/src/view/prose.rs`); `3663cf80` Make `ObjectFit`, `LineBreaking` and `Spinner` color be properties (#… (at that commit the file was still `xilem/src/view/prose.rs`); `f5b7d147` Add TextColor and DisabledTextColor properties. (#1163) (at that commit the file was still `xilem/src/view/prose.rs`) — run `git show` on any of them.
TodoComment xilem_web/web_examples/todomvc/src/main.rs:5— // TODO: Link — 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 xilem_web/web_examples/todomvc/src/main.rs:60— // TODO There could/should be further checks, if this is indeed the right event (same DOM element) — 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 xilem_web/web_examples/todomvc/src/main.rs:189— // TODO There could/should be further checks, if this is indeed the right event (same DOM element) — 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 xilem_web/web_examples/svgdraw/src/main.rs:86— // TODO support pinch as well — 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 xilem_web/src/app.rs:102— // TODO should the element provide a separate method to access reference instead? — 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 xilem_web/src/app.rs:153— // TODO perhaps inform the user that a stale request bubbled to the top? — 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 xilem_web/src/context.rs:157— // TODO: panic? Probably not, e.g. because of empty view sequences... — 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 xilem_web/src/elements.rs:128— // TODO maybe we can save some allocations/memory (this needs two extra `Vec`s) — 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 xilem_web/src/elements.rs:554— // TODO include document metadata elements? — 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 xilem_web/src/events.rs:64— // TODO use similar Nomenclature as gloo (Phase::Bubble/Phase::Capture)? — 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 xilem_web/src/events.rs:393— // TODO use similar Nomenclature as gloo (Phase::Bubble/Phase::Capture)? — 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 xilem_web/src/events.rs:74— // TODO options — 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 xilem_web/src/events.rs:209— // TODO: is this really needed (as the element will be removed anyway)? — 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 xilem_web/src/interfaces.rs:30— // TODO: This would be nice, but although all the events are specified in `web_sys` on the `Element` interface, events such as `dragend` or `reset` link to the more relevant sub interface — 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 xilem_web/src/interfaces.rs:975— // TODO different name? — 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 xilem_web/src/lib.rs:52— // TODO: Remove any items listed as "Deferred" — 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 xilem_masonry/src/lib.rs:28— // TODO: Remove any items listed as "Deferred" — 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 xilem/src/lib.rs:146— // TODO: Remove any items listed as "Deferred" — 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 masonry_core/src/lib.rs:74— // TODO: Remove any items listed as "Deferred" — 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 masonry/src/lib.rs:205— // TODO: Remove any items listed as "Deferred" — 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 xilem_web/src/lib.rs:231— // TODO this is probably not optimal, as misleading, this is only implemented for concrete (non-type-erased) elements — 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 xilem_web/src/lib.rs:274— // TODO specialize some of these elements, maybe via features? — 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 xilem_web/src/lib.rs:302— // HtmlBaseElement, TODO include metadata? — 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 xilem_web/src/lib.rs:303— // HtmlBodyElement, TODO include body element? — 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 xilem_web/src/lib.rs:321— // HtmlHeadElement, TODO include metadata? — 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 xilem_masonry/src/view/text_input.rs:15— // FIXME - A major problem of the current approach (always setting the text_input contents) — 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 masonry_testing/src/wrapper_widget.rs:45— // FIXME - Take NewWidget argument — 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 masonry_core/src/core/contexts.rs:2007— // FIXME - Add LayerId type and use that instead. — 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 masonry_core/src/core/contexts.rs:2072— // FIXME: We should move this method out of `UpdateCtx` to avoid having this disclaimer. — 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 masonry_core/src/core/widget_pod.rs:226— // FIXME - Remove — 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 masonry/src/theme.rs:185— // FIXME — 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 masonry/src/widgets/checkbox.rs:43— // FIXME - Remove label child, have this widget only be a box with a checkmark. — 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 masonry/src/widgets/radio_button.rs:35— // FIXME - Remove label child, have this widget only be a box with a checkmark. — 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 masonry/src/widgets/image.rs:216— // FIXME - remove cfg? — 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 masonry/src/widgets/prose.rs:155— // FIXME - Find more elegant way to propagate property to child. — 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 masonry/src/widgets/prose.rs:183— // FIXME - Find more elegant way to propagate property to child. — 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 masonry/src/widgets/text_input.rs:216— // FIXME - Find more elegant way to propagate property to child. — 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 masonry/src/widgets/text_input.rs:244— // FIXME - Find more elegant way to propagate property to child. — 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 masonry/src/layers/selector_menu.rs:167— // FIXME - This might be subject to TOCTOU. — 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 masonry/src/layers/selector_menu.rs:222— // FIXME - This might be subject to TOCTOU. — 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 masonry/src/layers/selector_menu.rs:373— // FIXME - This might be subject to TOCTOU. — 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.
HackComment xilem_web/src/elements.rs:345— // HACK: This will never be read, since we're handling a message rather than making any tree changes — 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 xilem_masonry/src/view/worker.rs:211— // Hack: Use the same signature for both versions which need and don't need an environment. — 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 xilem/examples/variable_clock.rs:44— // HACK: We add a spacer at the top for Android. See https://github.com/rust-windowing/winit/issues/2308 — 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 placehero/src/actions.rs:18— /// HACK: The null navigation, because Xilem's handling of optional/None actions is not good. — 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 masonry_winit/src/event_loop_runner.rs:597— // HACK: When we exit, on some systems (known to happen with Wayland on KDE), — 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 masonry_core/src/passes/update.rs:649— // HACK: It's not valid to send an event to a non-existent widget, so we check that the "previously" — 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 masonry/src/widgets/button.rs:197— // HACK: to make sure we look okay at default sizes when beside a text input, — 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 masonry/src/widgets/selector.rs:254— // HACK: to make sure we look okay at default sizes when beside a text input, — 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 masonry/src/widgets/text_area.rs:868— // HACK: We force the editor to relayout by pretending to edit the styles. — 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 masonry/src/widgets/text_area.rs:951— // HACK: Perform layout again with the old value so that speculative measure() calls — 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 masonry/src/widgets/text_area.rs:1161— // Hack: If we are using `SKIP_RENDER_TESTS`, the output image is a 1x1 white pixel — 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 masonry/src/widgets/text_area.rs:1223— // Hack: If we are using `SKIP_RENDER_TESTS`, the output image is a 1x1 white pixel — 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.
FileTooLong: src/interfaces.rs xilem_web/src/interfaces.rs— FileTooLong — 1150 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 650 over it, 2.30× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: core/contexts.rs masonry_core/src/core/contexts.rs— FileTooLong — 950 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 450 over it, 1.90× 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: widgets/step_input.rs masonry/src/widgets/step_input.rs— FileTooLong — 939 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 87% of them inside a single declaration: StepInput (6 blocks, 76-1830). The bar is 500 significant lines; this is 439 over it, 1.88× 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: passes/update.rs masonry_core/src/passes/update.rs— FileTooLong — 746 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 246 over it, 1.49× 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/event_loop_runner.rs masonry_winit/src/event_loop_runner.rs— FileTooLong — 709 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 73% of them inside a single declaration: MasonryState (3 blocks, 206-1193). The bar is 500 significant lines; this is 209 over it, 1.42× 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: widgets/flex.rs masonry/src/widgets/flex.rs— FileTooLong — 682 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 84% of them inside a single declaration: Flex (5 blocks, 50-1248). The bar is 500 significant lines; this is 182 over it, 1.36× 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/elements.rs xilem_web/src/elements.rs— FileTooLong — 650 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 150 over it, 1.30× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: widgets/text_area.rs masonry/src/widgets/text_area.rs— FileTooLong — 592 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 95% of them inside a single declaration: TextArea (7 blocks, 47-1108). The bar is 500 significant lines; this is 92 over it, 1.18× 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: app/render_root.rs masonry_core/src/app/render_root.rs— FileTooLong — 579 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: RenderRoot (4 blocks, 57-1117). The bar is 500 significant lines; this is 79 over it, 1.16× 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/harness.rs masonry_testing/src/harness.rs— FileTooLong — 575 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 81% of them inside a single declaration: TestHarness (2 blocks, 146-1214). The bar is 500 significant lines; this is 75 over it, 1.15× 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: widgets/grid.rs masonry/src/widgets/grid.rs— FileTooLong — 571 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 83% of them inside a single declaration: Grid (6 blocks, 31-1016). The bar is 500 significant lines; this is 71 over it, 1.14× 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: widgets/portal.rs masonry/src/widgets/portal.rs— FileTooLong — 551 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 95% of them inside a single declaration: Portal (5 blocks, 45-915). The bar is 500 significant lines; this is 51 over it, 1.10× 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.
ClassTooLong: StepInput masonry/src/widgets/step_input.rs:76— ClassTooLong — 814 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 33 methods, 6 blocks, lines 76-1830. The bar is 400 significant lines; this is 414 over it, 2.04× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Flex masonry/src/widgets/flex.rs:50— ClassTooLong — 570 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 21 methods, 5 blocks, lines 50-1248. The bar is 400 significant lines; this is 170 over it, 1.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TextArea masonry/src/widgets/text_area.rs:47— ClassTooLong — 561 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 24 methods, 7 blocks, lines 47-1108. The bar is 400 significant lines; this is 161 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: MasonryState masonry_winit/src/event_loop_runner.rs:206— ClassTooLong — 521 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 25 methods, 3 blocks, lines 206-1193. The bar is 400 significant lines; this is 121 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Portal masonry/src/widgets/portal.rs:45— ClassTooLong — 521 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 21 methods, 5 blocks, lines 45-915. The bar is 400 significant lines; this is 121 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Grid masonry/src/widgets/grid.rs:31— ClassTooLong — 474 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 11 methods, 6 blocks, lines 31-1016. The bar is 400 significant lines; this is 74 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: TestHarness masonry_testing/src/harness.rs:146— ClassTooLong — 467 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 54 methods, 2 blocks, lines 146-1214. The bar is 400 significant lines; this is 67 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: RenderRoot masonry_core/src/app/render_root.rs:57— ClassTooLong — 450 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 46 methods, 4 blocks, lines 57-1117. The bar is 400 significant lines; this is 50 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Split masonry/src/widgets/split.rs:45— ClassTooLong — 420 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 35 methods, 5 blocks, lines 45-773. The bar is 400 significant lines; this is 20 over it, 1.05× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Low cohesion: ColorRectangle (LCOM4 6) masonry/src/doc/color_rectangle.rs:45— ColorRectangle's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ModularWidget (LCOM4 6) masonry_testing/src/modular_widget.rs:55— ModularWidget's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Checkbox (LCOM4 5) masonry/src/widgets/checkbox.rs:41— Checkbox's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Slider (LCOM4 5) masonry/src/widgets/slider.rs:32— Slider's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: TextInput (LCOM4 5) masonry/src/widgets/text_input.rs:40— TextInput's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Button (LCOM4 4) masonry/src/widgets/button.rs:34— Button's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ProgressBar (LCOM4 4) masonry/src/widgets/progress_bar.rs:33— ProgressBar's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Prose (LCOM4 4) masonry/src/widgets/prose.rs:41— Prose's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: RadioButton (LCOM4 4) masonry/src/widgets/radio_button.rs:33— RadioButton'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.
Change coupling: modular_widget.rs ↔ recorder_widget.rs masonry_testing/src/modular_widget.rs:1— `masonry_testing/src/modular_widget.rs` and `masonry_testing/src/recorder_widget.rs` change together 71% of the time (10 of the 14 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 10 shared commits counted here, the most recent 3 are `c8945b98` Add `action` pass. (#1677); `dbf014ac` Add `Widget::propagates_pointer_interaction` method. (#1659); `516dab63` Add Tooltip layer (#1541) — run `git show` on any of them.
Change coupling: harness.rs ↔ modular_widget.rs masonry_testing/src/harness.rs:1— `masonry_testing/src/harness.rs` and `masonry_testing/src/modular_widget.rs` change together 67% of the time (10 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `dbf014ac` Add `Widget::propagates_pointer_interaction` method. (#1659); `516dab63` Add Tooltip layer (#1541); `016ad36c` Make `WidgetId::next()` private and remove most uses. (#1571) — run `git show` on any of them.
Change coupling: label.rs ↔ prose.rs xilem_masonry/src/view/label.rs:1— `xilem_masonry/src/view/label.rs` and `xilem_masonry/src/view/prose.rs` change together 67% of the time (8 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 8 shared commits counted here, the most recent 3 are `07bf193f` Merge `TextColor` and `SpinnerColor` into `ContentColor`. (#1295) (at that commit the files were still `xilem/src/view/label.rs` and `xilem/src/view/prose.rs`); `3663cf80` Make `ObjectFit`, `LineBreaking` and `Spinner` color be properties (#… (at that commit the files were still `xilem/src/view/label.rs` and `xilem/src/view/prose.rs`); `f5b7d147` Add TextColor and DisabledTextColor properties. (#1163) (at that commit the files were still `xilem/src/view/label.rs` and `xilem/src/view/prose.rs`) — run `git show` on any of them.
Change coupling: label.rs ↔ prose.rs masonry/src/widgets/label.rs:1— `masonry/src/widgets/label.rs` and `masonry/src/widgets/prose.rs` change together 66% of the time (19 of the 29 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 19 shared commits counted here, the most recent 3 are `19c7bee9` Use `dpi`, `parley` from `masonry_core` (#1704); `d91aaffc` Add `Gap` property to `Flex` and `Grid` (#1527); `be1c8e87` Factor Axis, CrossAxisAlignment and MainAxisAlignment out of `flex.rs… — run `git show` on any of them.
Change coupling: button.rs ↔ checkbox.rs masonry/src/widgets/button.rs:1— `masonry/src/widgets/button.rs` and `masonry/src/widgets/checkbox.rs` change together 61% of the time (22 of the 36 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 22 shared commits counted here, the most recent 3 are `24a43afe` Add or tweak button parameter to Harness methods that simulate clicks…; `dbf014ac` Add `Widget::propagates_pointer_interaction` method. (#1659); `a3d034e6` Implement `Padding` in Masonry Core. (#1606) — run `git show` on any of them.
Change coupling: flex.rs ↔ indexed_stack.rs masonry/src/widgets/flex.rs:1— `masonry/src/widgets/flex.rs` and `masonry/src/widgets/indexed_stack.rs` change together 55% of the time (6 of the 11 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 `a3d034e6` Implement `Padding` in Masonry Core. (#1606); `84e92864` Add `swap_children` to collection widgets. (#1502); `97a0b696` Add efficient child replacement methods to widgets. (#1494) — run `git show` on any of them.
Change coupling: align.rs ↔ button.rs masonry/src/widgets/align.rs:1— `masonry/src/widgets/align.rs` and `masonry/src/widgets/button.rs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) 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 5 shared commits counted here, the most recent 3 are `dbfae1d1` Fix various widget baselines. (#1618); `894cda07` Allow replacing children in all widgets. (#1493); `dcea01a4` Migrate layout pass (#529) (at that commit the files were still `masonry/src/widget/align.rs` and `masonry/src/widget/button.rs`) — run `git show` on any of them.
Change coupling: prose.rs ↔ variable_label.rs xilem_masonry/src/view/prose.rs:1— `xilem_masonry/src/view/prose.rs` and `xilem_masonry/src/view/variable_label.rs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) 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 5 shared commits counted here, the most recent 3 are `07bf193f` Merge `TextColor` and `SpinnerColor` into `ContentColor`. (#1295) (at that commit the files were still `xilem/src/view/prose.rs` and `xilem/src/view/variable_label.rs`); `f5b7d147` Add TextColor and DisabledTextColor properties. (#1163) (at that commit the files were still `xilem/src/view/prose.rs` and `xilem/src/view/variable_label.rs`); `3af4d68f` Prepare for `TextAlign` (#1138) (at that commit the files were still `xilem/src/view/prose.rs` and `xilem/src/view/variable_label.rs`) — run `git show` on any of them.
masonry_core::passes::update::run_update_pointer_pass (cognitive 57) masonry_core/src/passes/update.rs:825— masonry_core::passes::update::run_update_pointer_pass has cognitive complexity 57 (threshold 15). Drivers by points: if/else 25 (38 pts), loops 6 (12 pts), boolean chains 7 (nesting depth added 19). Of this number, 53 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
masonry_core::passes::update::run_update_focus_pass (cognitive 41) masonry_core/src/passes/update.rs:619— masonry_core::passes::update::run_update_focus_pass has cognitive complexity 41 (threshold 15). Drivers by points: if/else 16 (27 pts), boolean chains 8, loops 3 (6 pts) (nesting depth added 14). Of this number, 39 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
masonry_core::passes::paint::paint_widget (cognitive 40) masonry_core/src/passes/paint.rs:71— masonry_core::passes::paint::paint_widget has cognitive complexity 40 (threshold 15). Drivers by points: if/else 20 (34 pts), boolean chains 5, match/switch 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
masonry_core::core::text::render_text (cognitive 28) masonry_core/src/core/text.rs:45— masonry_core::core::text::render_text has cognitive complexity 28 (threshold 15). Drivers by points: match/switch 4 (16 pts), if/else 3 (9 pts), loops 2 (3 pts) (nesting depth added 19). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
masonry_core::passes::update::find_first_focusable (cognitive 25) masonry_core/src/passes/update.rs:554— masonry_core::passes::update::find_first_focusable has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (20 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
masonry_core::passes::layout::run_layout_on (cognitive 22) masonry_core/src/passes/layout.rs:299— masonry_core::passes::layout::run_layout_on has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (17 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
masonry_core::passes::event::run_on_pointer_event_pass (cognitive 19) masonry_core/src/passes/event.rs:149— masonry_core::passes::event::run_on_pointer_event_pass has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (15 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.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×7
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×7
Duplicated block (8 lines × 2) masonry/src/widgets/prose.rs:193— masonry/src/widgets/prose.rs:193-200 | masonry/src/widgets/text_input.rs:248-255 — before extracting anything, compare `masonry/src/widgets/prose.rs` and `masonry/src/widgets/text_input.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `masonry/src/widgets/prose.rs:193` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 2) masonry_core/src/passes/event.rs:106— masonry_core/src/passes/event.rs:106-113 | masonry_core/src/passes/event.rs:194-201 — 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 `masonry_core/src/passes/event.rs:106` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) xilem_web/src/modifiers/attribute.rs:200— xilem_web/src/modifiers/attribute.rs:200-207 | xilem_web/src/modifiers/style.rs:332-339 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `next` to `&AttributeModifier` in one and `&StyleModifier` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (8 lines × 2) masonry/src/widgets/image.rs:198— masonry/src/widgets/image.rs:198-205 | masonry/src/widgets/svg.rs:233-240 — 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 `masonry/src/widgets/image.rs:198` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) masonry/src/widgets/checkbox.rs:149— masonry/src/widgets/checkbox.rs:149-156 | masonry/src/widgets/switch.rs:154-161 — 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 `masonry/src/widgets/checkbox.rs:149` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) xilem_masonry/src/view/task.rs:132— xilem_masonry/src/view/task.rs:132-139 | xilem_masonry/src/view/worker.rs:242-249 — 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 `xilem_masonry/src/view/task.rs:132` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) xilem_web/src/pointer.rs:109— xilem_web/src/pointer.rs:109-116 | xilem_web/src/pointer.rs:118-125 — 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 `xilem_web/src/pointer.rs:109` 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.
MethodTooLong: Flex.layout masonry/src/widgets/flex.rs:922— MethodTooLong — layout runs 200 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 100 over it, 2.00× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TextArea.on_text_event masonry/src/widgets/text_area.rs:544— MethodTooLong — on_text_event runs 192 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 92 over it, 1.92× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Grid.resolve_track_lengths masonry/src/widgets/grid.rs:320— MethodTooLong — resolve_track_lengths runs 166 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 66 over it, 1.66× 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: StepInput.paint_flow masonry/src/widgets/step_input.rs:1595— MethodTooLong — paint_flow runs 154 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 54 over it, 1.54× 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: Flex.measure masonry/src/widgets/flex.rs:695— MethodTooLong — measure runs 138 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: OneOf.rebuild xilem_core/src/views/one_of.rs:308— MethodTooLong — rebuild runs 117 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×6
Edited copy of a member (13 corresponding lines) xilem_web/src/one_of.rs:39— xilem_web/src/one_of.rs:39-51 | xilem_web/src/one_of.rs:66-85 — 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) masonry/src/widgets/flex.rs:372— masonry/src/widgets/flex.rs:372-384 | masonry/src/widgets/flex.rs:397-410 — 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) masonry_imaging/src/texture_render.rs:305— masonry_imaging/src/texture_render.rs:305-317 | masonry_imaging/src/texture_render.rs:375-389 — 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) xilem_masonry/src/view/checkbox.rs:170— xilem_masonry/src/view/checkbox.rs:170-182 | xilem_masonry/src/view/switch.rs:111-123 — 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) xilem_web/src/modifiers/attribute.rs:128— xilem_web/src/modifiers/attribute.rs:128-141 | xilem_web/src/modifiers/style.rs:265-277 — 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) xilem_masonry/src/view/grid.rs:334— xilem_masonry/src/view/grid.rs:334-346 | xilem_masonry/src/view/indexed_stack.rs:233-245 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×6
Edited copy of a member (8 corresponding lines) xilem_web/src/modifiers/class.rs:348— xilem_web/src/modifiers/class.rs:348-355 | xilem_web/src/modifiers/style.rs:473-480 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) masonry/src/widgets/flex.rs:356— masonry/src/widgets/flex.rs:356-363 | masonry/src/widgets/flex.rs:480-488 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) xilem_web/src/modifiers/class.rs:364— xilem_web/src/modifiers/class.rs:364-375 | xilem_web/src/modifiers/style.rs:489-496 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) masonry_core/src/core/widget_mut.rs:95— masonry_core/src/core/widget_mut.rs:95-102 | masonry_core/src/core/widget_mut.rs:109-116 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) xilem_masonry/src/view/radio_button.rs:86— xilem_masonry/src/view/radio_button.rs:86-94 | xilem_masonry/src/view/switch.rs:71-78 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) masonry/src/doc/color_rectangle.rs:99— masonry/src/doc/color_rectangle.rs:99-106 | masonry/src/widgets/button.rs:152-159 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×6
Edited copy of a member (11 corresponding lines) xilem_masonry/src/view/image.rs:96— xilem_masonry/src/view/image.rs:96-106 | xilem_masonry/src/view/svg.rs:86-96 — 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) masonry/src/widgets/step_input.rs:490— masonry/src/widgets/step_input.rs:490-501 | masonry/src/widgets/step_input.rs:584-594 — 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) masonry/src/widgets/label.rs:254— masonry/src/widgets/label.rs:254-264 | masonry/src/widgets/text_area.rs:220-233 — 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) masonry_core/src/app/render_root.rs:457— masonry_core/src/app/render_root.rs:457-467 | masonry_core/src/app/render_root.rs:472-484 — 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) masonry/src/widgets/flex.rs:284— masonry/src/widgets/flex.rs:284-294 | masonry/src/widgets/flex.rs:335-345 — 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) xilem_masonry/src/view/button.rs:217— xilem_masonry/src/view/button.rs:217-227 | xilem_masonry/src/view/resize_observer.rs:136-146 — 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 (9 lines × 2) masonry/src/layers/selector_menu.rs:303— masonry/src/layers/selector_menu.rs:303-311 | masonry/src/widgets/flex.rs:1203-1213 — 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 `masonry/src/layers/selector_menu.rs:303` 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) masonry/src/widgets/flex.rs:376— masonry/src/widgets/flex.rs:376-384 | masonry/src/widgets/flex.rs:402-410 — 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 `masonry/src/widgets/flex.rs:376` 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) masonry/src/widgets/prose.rs:167— masonry/src/widgets/prose.rs:167-175 | masonry/src/widgets/text_input.rs:221-229 — before extracting anything, compare `masonry/src/widgets/prose.rs` and `masonry/src/widgets/text_input.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `masonry/src/widgets/prose.rs:167` 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) masonry_core/src/core/text.rs:79— masonry_core/src/core/text.rs:79-87 | masonry_core/src/core/text.rs:138-146 — 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 `masonry_core/src/core/text.rs:79` 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) xilem_masonry/src/view/prose.rs:142— xilem_masonry/src/view/prose.rs:142-150 | xilem_masonry/src/view/text_input.rs:316-324 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) placehero/src/components/media.rs:95— placehero/src/components/media.rs:95-103 | placehero/src/components/media.rs:111-119 — 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 `placehero/src/components/media.rs:95` 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: masonry::theme::default_property_set masonry/src/theme.rs:58— FunctionTooLong — masonry::theme::default_property_set runs 234 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 134 over it, 2.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: masonry_core::passes::update::run_update_pointer_pass masonry_core/src/passes/update.rs:825— FunctionTooLong — masonry_core::passes::update::run_update_pointer_pass runs 158 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 58 over it, 1.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: masonry_core::passes::paint::paint_widget masonry_core/src/passes/paint.rs:71— FunctionTooLong — masonry_core::passes::paint::paint_widget runs 138 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: placehero::html_content::status_html_to_plaintext placehero/src/html_content.rs:30— FunctionTooLong — placehero::html_content::status_html_to_plaintext runs 128 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: masonry_core::passes::layout::run_layout_on masonry_core/src/passes/layout.rs:299— FunctionTooLong — masonry_core::passes::layout::run_layout_on 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.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×5
Edited copy of a member (14 corresponding lines) xilem_masonry/src/view/flex.rs:355— xilem_masonry/src/view/flex.rs:355-368 | xilem_masonry/src/view/flex.rs:370-387 — 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) masonry/src/widgets/radio_button.rs:63— masonry/src/widgets/radio_button.rs:63-76 | masonry/src/widgets/radio_button.rs:101-114 — 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) xilem_web/src/modifiers/style.rs:578— xilem_web/src/modifiers/style.rs:578-591 | xilem_web/src/modifiers/style.rs:703-716 — 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) masonry/src/widgets/divider.rs:149— masonry/src/widgets/divider.rs:149-162 | xilem_masonry/src/view/divider.rs:22-36 — 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) masonry/src/widgets/split.rs:69— masonry/src/widgets/split.rs:69-83 | xilem_masonry/src/view/split.rs:51-64 — 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 (5 lines × 2) masonry/src/widgets/slider.rs:161— masonry/src/widgets/slider.rs:161-165 | masonry/src/widgets/slider.rs:168-172 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) xilem_masonry/src/view/badge.rs:82— xilem_masonry/src/view/badge.rs:82-86 | xilem_masonry/src/view/radio_group.rs:81-85 — 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 `xilem_masonry/src/view/badge.rs:82` 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) xilem_masonry/src/view/badge.rs:104— xilem_masonry/src/view/badge.rs:104-108 | xilem_masonry/src/view/radio_group.rs:103-107 — 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 `xilem_masonry/src/view/badge.rs:104` 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) masonry/src/widgets/grid.rs:268— masonry/src/widgets/grid.rs:268-272 | masonry/src/widgets/grid.rs:295-299 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) xilem_web/web_examples/open_and_save_file/src/main.rs:127— xilem_web/web_examples/open_and_save_file/src/main.rs:127-131 | xilem_web/web_examples/raw_dom_access/src/main.rs:58-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
masonry_core::passes::update::run_update_pointer_pass (cyclomatic 35) masonry_core/src/passes/update.rs:825— masonry_core::passes::update::run_update_pointer_pass has cyclomatic complexity 35 (threshold 15). Of this number, 33 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
masonry_core::passes::update::run_update_focus_pass (cyclomatic 27) masonry_core/src/passes/update.rs:619— masonry_core::passes::update::run_update_focus_pass has cyclomatic complexity 27 (threshold 15). Of this number, 26 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
masonry_core::passes::paint::paint_widget (cyclomatic 26) masonry_core/src/passes/paint.rs:71— masonry_core::passes::paint::paint_widget 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.
masonry_core::passes::layout::run_layout_on (cyclomatic 17) masonry_core/src/passes/layout.rs:299— masonry_core::passes::layout::run_layout_on 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.
StepInput::on_text_event (cognitive 49) masonry/src/widgets/step_input.rs:995— StepInput::on_text_event has cognitive complexity 49 (threshold 15). Drivers by points: if/else 17 (43 pts), match/switch 3 (6 pts) (nesting depth added 29). 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.
StepInput::on_pointer_event (cognitive 49) masonry/src/widgets/step_input.rs:1085— StepInput::on_pointer_event has cognitive complexity 49 (threshold 15). Drivers by points: if/else 23 (47 pts), boolean chains 1, match/switch 1 (nesting depth added 24). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
StepInput::paint_flow (cognitive 28) masonry/src/widgets/step_input.rs:1595— StepInput::paint_flow has cognitive complexity 28 (threshold 15). Drivers by points: if/else 19 (24 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.
StepInput::update_ticks (cognitive 25) masonry/src/widgets/step_input.rs:778— StepInput::update_ticks has cognitive complexity 25 (threshold 15). Drivers by points: if/else 15 (23 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TooManyMethods: TestHarness masonry_testing/src/harness.rs:146— TooManyMethods — 54 methods. The bar is 30 methods; this is 24 over it, 1.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RenderRoot masonry_core/src/app/render_root.rs:57— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Split masonry/src/widgets/split.rs:45— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: StepInput masonry/src/widgets/step_input.rs:76— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×4
REDACTED
REDACTED
REDACTED
REDACTED
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×4
Edited copy of a member (12 corresponding lines) placehero/src/components/media.rs:92— placehero/src/components/media.rs:92-103 | placehero/src/components/media.rs:108-119 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) xilem_web/src/modifiers/class.rs:243— xilem_web/src/modifiers/class.rs:243-255 | xilem_web/src/modifiers/style.rs:348-359 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) masonry_core/src/passes/anim.rs:74— masonry_core/src/passes/anim.rs:74-85 | masonry_core/src/passes/update.rs:456-467 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) xilem_web/src/modifiers/class.rs:175— xilem_web/src/modifiers/class.rs:175-190 | xilem_web/src/modifiers/class.rs:196-207 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×4
Edited copy of a member (6 corresponding lines) xilem_web/src/modifiers/attribute.rs:312— xilem_web/src/modifiers/attribute.rs:312-317 | xilem_web/src/svg/common_attrs.rs:251-256 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) masonry/src/widgets/badged.rs:126— masonry/src/widgets/badged.rs:126-132 | masonry/src/widgets/divider.rs:401-406 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) xilem_web/src/modifiers/attribute.rs:39— xilem_web/src/modifiers/attribute.rs:39-44 | xilem_web/src/modifiers/style.rs:44-49 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) masonry/src/widgets/grid.rs:831— masonry/src/widgets/grid.rs:831-836 | masonry/src/widgets/indexed_stack.rs:208-213 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (12 lines × 2) masonry/src/widgets/divider.rs:212— masonry/src/widgets/divider.rs:212-223 | xilem_masonry/src/view/divider.rs:108-119 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `masonry/src/widgets/divider.rs:212` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) xilem_masonry/src/view/virtual_scroll.rs:323— xilem_masonry/src/view/virtual_scroll.rs:323-334 | xilem_masonry/src/view/virtual_scroll.rs:358-369 — 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 `xilem_masonry/src/view/virtual_scroll.rs:358` 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 (12 lines × 2) masonry/src/doc/vertical_stack.rs:133— masonry/src/doc/vertical_stack.rs:133-144 | masonry/src/layers/selector_menu.rs:280-291 — 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 `masonry/src/doc/vertical_stack.rs:133` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) masonry/src/widgets/prose.rs:129— masonry/src/widgets/prose.rs:129-140 | masonry/src/widgets/text_input.rs:197-208 — before extracting anything, compare `masonry/src/widgets/prose.rs` and `masonry/src/widgets/text_input.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `masonry/src/widgets/prose.rs:129` 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) masonry/src/widgets/prose.rs:164— masonry/src/widgets/prose.rs:164-169 | masonry/src/widgets/prose.rs:190-195 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) xilem_masonry/src/view/checkbox.rs:144— xilem_masonry/src/view/checkbox.rs:144-149 | xilem_masonry/src/view/label.rs:164-169 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) masonry/src/widgets/text_input.rs:232— masonry/src/widgets/text_input.rs:232-237 | masonry/src/widgets/text_input.rs:257-262 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) xilem_masonry/src/view/badged.rs:162— xilem_masonry/src/view/badged.rs:162-167 | xilem_masonry/src/view/badged.rs:186-191 — 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 `xilem_masonry/src/view/badged.rs:162` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×3
Edited copy of a member (25 corresponding lines) xilem_core/src/environment.rs:269— xilem_core/src/environment.rs:269-294 | xilem_core/src/environment.rs:330-354 — 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) xilem_web/src/modifiers/class.rs:265— xilem_web/src/modifiers/class.rs:265-289 | xilem_web/src/modifiers/style.rs:369-393 — 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) xilem_masonry/src/view/button.rs:235— xilem_masonry/src/view/button.rs:235-259 | xilem_masonry/src/view/resize_observer.rs:154-184 — 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 (9 corresponding lines) · ×3
Edited copy of a member (9 corresponding lines) xilem_web/src/modifiers/style.rs:149— xilem_web/src/modifiers/style.rs:149-157 | xilem_web/src/modifiers/style.rs:159-167 — 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) xilem_core/src/views/fork.rs:65— xilem_core/src/views/fork.rs:65-79 | xilem_core/src/views/fork.rs:86-94 — 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) xilem_web/src/modifiers/class.rs:160— xilem_web/src/modifiers/class.rs:160-169 | xilem_web/src/modifiers/style.rs:251-259 — 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 copies of one member (3 members, 10+ corresponding lines) · ×3
Edited copies of one member (3 members, 10+ corresponding lines) xilem_web/src/svg/kurbo_shape.rs:36— xilem_web/src/svg/kurbo_shape.rs:36-46 | xilem_web/src/svg/kurbo_shape.rs:93-103 | xilem_web/src/svg/kurbo_shape.rs:149-158 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 10+ corresponding lines) xilem_masonry/src/view/flex.rs:583— xilem_masonry/src/view/flex.rs:583-592 | xilem_masonry/src/view/grid.rs:553-562 | xilem_masonry/src/view/zstack.rs:220-229 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 10+ corresponding lines) masonry/src/widgets/checkbox.rs:125— masonry/src/widgets/checkbox.rs:125-134 | masonry/src/widgets/radio_button.rs:172-181 | masonry/src/widgets/switch.rs:132-143 — 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 (15 corresponding lines) · ×3
Edited copy of a member (15 corresponding lines) masonry/src/widgets/divider.rs:209— masonry/src/widgets/divider.rs:209-223 | xilem_masonry/src/view/divider.rs:105-119 — 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) masonry_core/src/app/layer_stack.rs:116— masonry_core/src/app/layer_stack.rs:116-130 | masonry_core/src/app/layer_stack.rs:148-162 — 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) xilem_web/src/events.rs:614— xilem_web/src/events.rs:614-628 | xilem_web/src/pointer.rs:171-186 — 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.
Duplicated block (13 lines × 2) masonry/src/widgets/text_input.rs:334— masonry/src/widgets/text_input.rs:334-346 | masonry_core/src/core/widget_paint.rs:50-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `masonry/src/widgets/text_input.rs:334` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `ctx` to `&mut LayoutCtx<'_>` in one and `&mut PaintCtx<'_>` 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 (13 lines × 2) xilem_masonry/src/view/flex.rs:356— xilem_masonry/src/view/flex.rs:356-368 | xilem_masonry/src/view/flex.rs:373-385 — 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 `xilem_masonry/src/view/flex.rs:373` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) masonry_testing/src/assert_any.rs:42— masonry_testing/src/assert_any.rs:42-54 | masonry_testing/src/assert_any.rs:71-85 — 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 `masonry_testing/src/assert_any.rs:42` 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) masonry/src/widgets/prose.rs:181— masonry/src/widgets/prose.rs:181-191 | masonry/src/widgets/text_input.rs:242-252 — before extracting anything, compare `masonry/src/widgets/prose.rs` and `masonry/src/widgets/text_input.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `masonry/src/widgets/prose.rs:181` 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) masonry/src/widgets/split.rs:506— masonry/src/widgets/split.rs:506-516 | masonry/src/widgets/split.rs:558-568 — 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 `masonry/src/widgets/split.rs:506` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) masonry/src/widgets/selector_item.rs:70— masonry/src/widgets/selector_item.rs:70-80 | masonry/src/widgets/split.rs:595-605 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 3) masonry/src/widgets/passthrough.rs:101— masonry/src/widgets/passthrough.rs:101-105 | masonry/src/widgets/radio_group.rs:61-65 | masonry/src/widgets/variable_label.rs:249-253 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (5 lines × 3) masonry_core/src/core/property_stack.rs:29— masonry_core/src/core/property_stack.rs:29-33 | masonry_core/src/core/widget.rs:650-654 | masonry_winit/src/app_driver.rs:28-32 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (5 lines × 3) xilem_masonry/src/view/flex.rs:610— xilem_masonry/src/view/flex.rs:610-614 | xilem_masonry/src/view/grid.rs:580-584 | xilem_masonry/src/view/zstack.rs:247-251 — before extracting anything, compare `xilem_masonry/src/view/flex.rs` and `xilem_masonry/src/view/grid.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 58 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 `xilem_masonry/src/view/flex.rs:610` 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.
AC3 · Page structure· Page without a main landmark · ×2
Page without a main landmark xilem_web/web_examples/counter_custom_element/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark REDACTED:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×2
Animation without a prefers-reduced-motion guard xilem_web/web_examples/svgdraw/index.html:26— `.color>input[type=radio]+div` moves (`transition: transform 0.3s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard REDACTED:135— `.learn-bar > .learn` moves (`transition-property: left`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Grid::resolve_track_lengths (cyclomatic 33) masonry/src/widgets/grid.rs:320— Grid::resolve_track_lengths has cyclomatic complexity 33 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
Grid::assign_cell_to_auto_placed_children (cyclomatic 24) masonry/src/widgets/grid.rs:153— Grid::assign_cell_to_auto_placed_children 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.
MasonryState::handle_signals (cyclomatic 29) masonry_winit/src/event_loop_runner.rs:1026— MasonryState::handle_signals 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.
MasonryState::handle_window_event (cyclomatic 21) masonry_winit/src/event_loop_runner.rs:808— MasonryState::handle_window_event has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Flex::layout (cyclomatic 25) masonry/src/widgets/flex.rs:922— Flex::layout has cyclomatic complexity 25 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Flex::measure (cyclomatic 17) masonry/src/widgets/flex.rs:695— Flex::measure has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
StepInput::on_pointer_event (cyclomatic 23) masonry/src/widgets/step_input.rs:1085— StepInput::on_pointer_event has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
StepInput::on_text_event (cyclomatic 22) masonry/src/widgets/step_input.rs:995— StepInput::on_text_event has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Grid::assign_cell_to_auto_placed_children (cognitive 57) masonry/src/widgets/grid.rs:153— Grid::assign_cell_to_auto_placed_children has cognitive complexity 57 (threshold 15). Drivers by points: if/else 10 (30 pts), loops 9 (23 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 35). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Grid::resolve_track_lengths (cognitive 55) masonry/src/widgets/grid.rs:320— Grid::resolve_track_lengths has cognitive complexity 55 (threshold 15). Drivers by points: if/else 15 (25 pts), match/switch 10 (21 pts), loops 4 (7 pts), boolean chains 2 (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.
Flex::layout (cognitive 43) masonry/src/widgets/flex.rs:922— Flex::layout has cognitive complexity 43 (threshold 15). Drivers by points: match/switch 9 (21 pts), if/else 10 (17 pts), loops 4 (5 pts) (nesting depth added 20). 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.
Flex::measure (cognitive 40) masonry/src/widgets/flex.rs:695— Flex::measure has cognitive complexity 40 (threshold 15). Drivers by points: match/switch 8 (18 pts), if/else 9 (13 pts), loops 4 (8 pts), boolean chains 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.
MasonryState::handle_window_event (cognitive 27) masonry_winit/src/event_loop_runner.rs:808— MasonryState::handle_window_event has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (17 pts), match/switch 4 (8 pts), boolean chains 2 (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.
MasonryState::handle_signals (cognitive 17) masonry_winit/src/event_loop_runner.rs:1026— MasonryState::handle_signals has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 3, match/switch 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Portal::on_access_event (cognitive 16) masonry/src/widgets/portal.rs:580— Portal::on_access_event has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), match/switch 3 (7 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.
Portal::accessibility (cognitive 16) masonry/src/widgets/portal.rs:852— Portal::accessibility has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TooManyFunctions: xilem_web::elements::html xilem_web/src/elements.rs:557— TooManyFunctions — 105 free functions. The bar is 30 free functions; this is 75 over it, 3.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyFunctions: xilem_web::elements::svg xilem_web/src/elements.rs:716— TooManyFunctions — 63 free functions. The bar is 30 free functions; this is 33 over it, 2.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyFields: WidgetState masonry_core/src/core/widget_state.rs:71— TooManyFields — 58 stored fields beside 16 methods. The bar is 30 stored fields; this is 28 over it, 1.93× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: RenderRootState masonry_core/src/app/render_root.rs:72— TooManyFields — 31 stored fields beside 2 methods. The bar is 30 stored fields; this is 1 over it, 1.03× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×2
Edited copy of a member (21 corresponding lines) xilem_web/src/events.rs:175— xilem_web/src/events.rs:175-195 | xilem_web/src/events.rs:282-318 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) masonry_testing/src/assert_any.rs:34— masonry_testing/src/assert_any.rs:34-54 | masonry_testing/src/assert_any.rs:63-85 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×2
Edited copy of a member (17 corresponding lines) xilem_web/src/modifiers/attribute.rs:150— xilem_web/src/modifiers/attribute.rs:150-166 | xilem_web/src/modifiers/style.rs:283-299 — 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) masonry_core/src/passes/compose.rs:79— masonry_core/src/passes/compose.rs:79-96 | masonry_core/src/passes/update.rs:363-379 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×2
Edited copy of a member (18 corresponding lines) masonry/src/widgets/step_input.rs:717— masonry/src/widgets/step_input.rs:717-734 | masonry/src/widgets/step_input.rs:741-758 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) xilem_masonry/src/view/collapse_panel.rs:86— xilem_masonry/src/view/collapse_panel.rs:86-110 | xilem_masonry/src/view/collapse_panel.rs:117-134 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×2
Edited copy of a member (22 corresponding lines) masonry_core/src/core/contexts.rs:1123— masonry_core/src/core/contexts.rs:1123-1146 | masonry_core/src/core/contexts.rs:1158-1179 — 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) masonry/src/widgets/button.rs:182— masonry/src/widgets/button.rs:182-203 | masonry/src/widgets/selector.rs:239-261 — 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) masonry/src/widgets/portal.rs:286— masonry/src/widgets/portal.rs:286-301 | masonry/src/widgets/portal.rs:389-405 — 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) masonry_core/src/app/tracing_backend.rs:182— masonry_core/src/app/tracing_backend.rs:182-197 | masonry_core/src/app/tracing_backend.rs:200-221 — 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 copies of one member (3 members, 16+ corresponding lines) · ×2
Edited copies of one member (3 members, 16+ corresponding lines) xilem_masonry/src/view/grid.rs:214— xilem_masonry/src/view/grid.rs:214-231 | xilem_masonry/src/view/indexed_stack.rs:116-132 | xilem_masonry/src/view/zstack.rs:89-104 — 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.
Edited copies of one member (3 members, 16+ corresponding lines) masonry_core/src/core/properties_mut.rs:32— masonry_core/src/core/properties_mut.rs:32-47 | masonry_core/src/core/properties_ref.rs:32-47 | masonry_core/src/core/properties_ref.rs:52-70 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 12+ corresponding lines) · ×2
Edited copies of one member (3 members, 12+ corresponding lines) masonry/src/widgets/button.rs:134— masonry/src/widgets/button.rs:134-145 | masonry/src/widgets/disclosure_button.rs:96-110 | masonry/src/widgets/selector.rs:177-192 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 12+ corresponding lines) xilem_web/src/elements.rs:285— xilem_web/src/elements.rs:285-302 | xilem_web/src/elements.rs:314-325 | xilem_web/src/elements.rs:339-358 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 4+ corresponding lines) · ×2
Edited copies of one member (3 members, 4+ corresponding lines) xilem_masonry/src/view/flex.rs:599— xilem_masonry/src/view/flex.rs:599-602 | xilem_masonry/src/view/grid.rs:569-572 | xilem_masonry/src/view/zstack.rs:236-239 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 4+ corresponding lines) masonry/src/widgets/indexed_stack.rs:169— masonry/src/widgets/indexed_stack.rs:169-172 | masonry/src/widgets/passthrough.rs:71-74 | masonry/src/widgets/resize_observer.rs:79-82 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 5+ corresponding lines) · ×2
Edited copies of one member (3 members, 5+ corresponding lines) masonry/src/layers/selector_menu.rs:86— masonry/src/layers/selector_menu.rs:86-90 | masonry/src/widgets/flex.rs:305-309 | masonry/src/widgets/zstack.rs:150-154 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 5+ corresponding lines) masonry/src/layers/selector_menu.rs:70— masonry/src/layers/selector_menu.rs:70-74 | masonry/src/widgets/flex.rs:256-260 | masonry/src/widgets/zstack.rs:134-138 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×2
Edited copy of a member (4 corresponding lines) xilem_masonry/src/view/flex.rs:568— xilem_masonry/src/view/flex.rs:568-574 | xilem_masonry/src/view/zstack.rs:208-211 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) xilem_masonry/src/view/badge.rs:93— xilem_masonry/src/view/badge.rs:93-96 | xilem_masonry/src/view/radio_group.rs:92-95 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (14 lines × 2) masonry_core/src/core/properties_mut.rs:34— masonry_core/src/core/properties_mut.rs:34-47 | masonry_core/src/core/properties_ref.rs:34-47 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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 (14 lines × 2) xilem_masonry/src/view/task.rs:38— xilem_masonry/src/view/task.rs:38-51 | xilem_web/src/concurrent/task.rs:35-48 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 3) masonry/src/widgets/divider.rs:210— masonry/src/widgets/divider.rs:210-220 | masonry/src/widgets/divider.rs:339-349 | xilem_masonry/src/view/divider.rs:106-116 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (11 lines × 3) xilem_masonry/src/view/flex.rs:399— xilem_masonry/src/view/flex.rs:399-409 | xilem_masonry/src/view/grid.rs:376-386 | xilem_masonry/src/view/zstack.rs:396-406 — before extracting anything, compare `xilem_masonry/src/view/flex.rs` and `xilem_masonry/src/view/grid.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 58 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 (10 lines × 2) masonry/src/widgets/portal.rs:289— masonry/src/widgets/portal.rs:289-298 | masonry/src/widgets/portal.rs:393-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.
Duplicated block (10 lines × 2) xilem_web/src/modifiers/attribute.rs:183— xilem_web/src/modifiers/attribute.rs:183-192 | xilem_web/src/modifiers/style.rs:318-327 — 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 × 4) masonry/src/theme.rs:85— masonry/src/theme.rs:85-93 | masonry/src/theme.rs:115-123 | masonry/src/theme.rs:161-169 | masonry/src/theme.rs:379-387 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 4) xilem_masonry/src/view/flex.rs:389— xilem_masonry/src/view/flex.rs:389-397 | xilem_masonry/src/view/grid.rs:358-366 | xilem_masonry/src/view/indexed_stack.rs:252-260 | xilem_masonry/src/view/zstack.rs:378-386 — before extracting anything, compare `xilem_masonry/src/view/flex.rs` and `xilem_masonry/src/view/grid.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 58 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 first that the copies are not typed on the same thing: the declarations holding them bind `element` to `FlexElement` in one and `GridElement` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 3) masonry/src/theme.rs:86— masonry/src/theme.rs:86-94 | masonry/src/theme.rs:116-124 | masonry/src/theme.rs:351-360 — 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 `masonry/src/theme.rs:86` 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, `masonry/src/theme.rs:349` calls `with_active`, `Color` and `masonry/src/theme.rs:86` 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 (9 lines × 3) xilem_masonry/src/view/flex.rs:343— xilem_masonry/src/view/flex.rs:343-351 | xilem_masonry/src/view/grid.rs:321-329 | xilem_masonry/src/view/zstack.rs:307-315 — before extracting anything, compare `xilem_masonry/src/view/flex.rs` and `xilem_masonry/src/view/grid.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 58 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 `xilem_masonry/src/view/flex.rs:343` 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 × 4) masonry/src/widgets/prose.rs:157— masonry/src/widgets/prose.rs:157-162 | masonry/src/widgets/prose.rs:184-189 | masonry/src/widgets/text_input.rs:218-223 | masonry/src/widgets/text_input.rs:245-250 — before extracting anything, compare `masonry/src/widgets/prose.rs` and `masonry/src/widgets/text_input.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (6 lines × 4) masonry/src/widgets/prose.rs:171— masonry/src/widgets/prose.rs:171-176 | masonry/src/widgets/prose.rs:196-201 | masonry/src/widgets/text_input.rs:225-230 | masonry/src/widgets/text_input.rs:251-256 — before extracting anything, compare `masonry/src/widgets/prose.rs` and `masonry/src/widgets/text_input.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×1
Focus outline removed in CSS without a :focus replacement REDACTED:187— `:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
TextArea::on_text_event (cyclomatic 61) masonry/src/widgets/text_area.rs:544— TextArea::on_text_event has cyclomatic complexity 61 (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.
placehero::html_content::status_html_to_plaintext (cyclomatic 33) placehero/src/html_content.rs:30— placehero::html_content::status_html_to_plaintext has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
linebender_include_doc_path::parsing::parse_lit_str_cooked (cyclomatic 21) include_doc_path/src/parsing.rs:65— linebender_include_doc_path::parsing::parse_lit_str_cooked has cyclomatic complexity 21 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
Hotspot: masonry_core/src/passes/layout.rs masonry_core/src/passes/layout.rs:299— masonry_core/src/passes/layout.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in masonry_core::passes::layout::run_layout_on at line 299. 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-05..2026-11-03, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-05 18:05:30 +00:00' --until='2026-11-03 18:05:30 +00:00' --full-history --no-merges -- masonry_core/src/passes/layout.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.
TextArea::on_text_event (cognitive 109) masonry/src/widgets/text_area.rs:544— TextArea::on_text_event has cognitive complexity 109 (threshold 15). Drivers by points: if/else 46 (94 pts), match/switch 4 (8 pts), boolean chains 7 (nesting depth added 52). 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.
placehero::html_content::status_html_to_plaintext (cognitive 80) placehero/src/html_content.rs:30— placehero::html_content::status_html_to_plaintext has cognitive complexity 80 (threshold 15). Drivers by points: if/else 18 (56 pts), match/switch 5 (18 pts), loops 2 (6 pts) (nesting depth added 55). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VirtualScroll::rebuild (cognitive 26) xilem_masonry/src/view/virtual_scroll.rs:248— VirtualScroll::rebuild has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (19 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Slider::on_text_event (cognitive 24) masonry/src/widgets/slider.rs:179— Slider::on_text_event has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (21 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
linebender_include_doc_path::parsing::parse_lit_str_cooked (cognitive 24) include_doc_path/src/parsing.rs:65— linebender_include_doc_path::parsing::parse_lit_str_cooked has cognitive complexity 24 (threshold 15). Drivers by points: match/switch 3 (10 pts), if/else 4 (9 pts), loops 2 (5 pts) (nesting depth added 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
TestHarness::check_render_snapshot (cognitive 18) masonry_testing/src/harness.rs:1111— TestHarness::check_render_snapshot has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 2 (nesting depth added 4). Of this number, 16 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MemoizedAwait::rebuild (cognitive 17) xilem_web/src/concurrent/memoized_await.rs:195— MemoizedAwait::rebuild has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 6 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Edited copy of a member (38 corresponding lines) · ×1
Edited copy of a member (38 corresponding lines) xilem_core/src/views/one_of.rs:258— xilem_core/src/views/one_of.rs:258-305 | xilem_core/src/views/one_of.rs:315-490 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (11 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (11 members, 50+ identical tokens) masonry_core/src/passes/accessibility.rs:23— masonry_core/src/passes/accessibility.rs:23-83 | masonry_core/src/passes/anim.rs:18-65 | masonry_core/src/passes/layout.rs:304-494 | masonry_core/src/passes/mutate.rs:14-64 | masonry_core/src/passes/paint.rs:79-280 | masonry_core/src/passes/update.rs:62-98 | masonry_core/src/passes/update.rs:104-146 | masonry_core/src/passes/update.rs:155-221 | masonry_core/src/passes/update.rs:308-361 | masonry_core/src/passes/update.rs:395-454 | masonry_core/src/passes/update.rs:1201-1237 — These 11 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 11 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 11 times.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) masonry/src/widgets/checkbox.rs:247— masonry/src/widgets/checkbox.rs:247-280 | masonry/src/widgets/progress_bar.rs:185-193 | masonry/src/widgets/radio_button.rs:296-329 | masonry/src/widgets/slider.rs:342-366 | masonry/src/widgets/text_input.rs:332-346 | masonry_core/src/core/widget_paint.rs:48-62 — 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) masonry/src/layers/tooltip.rs:111— masonry/src/layers/tooltip.rs:111-119 | masonry/src/widgets/badge.rs:182-190 | masonry/src/widgets/button.rs:205-213 | masonry/src/widgets/selector.rs:263-271 | masonry/src/widgets/selector_item.rs:108-116 — 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· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) masonry/src/widgets/prose.rs:154— masonry/src/widgets/prose.rs:154-178 | masonry/src/widgets/prose.rs:180-205 | masonry/src/widgets/text_input.rs:215-239 | masonry/src/widgets/text_input.rs:241-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.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×1
Edited copy of a member (26 corresponding lines) masonry/src/doc/vertical_stack.rs:98— masonry/src/doc/vertical_stack.rs:98-123 | masonry/src/layers/selector_menu.rs:240-271 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) masonry_core/src/core/contexts.rs:297— masonry_core/src/core/contexts.rs:297-322 | masonry_core/src/core/contexts.rs:366-388 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 20+ corresponding lines) · ×1
Edited copies of one member (4 members, 20+ corresponding lines) masonry_core/src/app/render_root.rs:425— masonry_core/src/app/render_root.rs:425-450 | masonry_core/src/app/render_root.rs:904-923 | masonry_core/src/app/render_root.rs:925-948 | masonry_core/src/app/render_root.rs:1071-1102 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 1+ corresponding lines) · ×1
Edited copies of one member (5 members, 1+ corresponding lines) xilem_web/src/modifiers/elements.rs:14— xilem_web/src/modifiers/elements.rs:14-14 | xilem_web/src/modifiers/elements.rs:15-15 | xilem_web/src/modifiers/elements.rs:16-16 | xilem_web/src/modifiers/elements.rs:17-17 | xilem_web/src/modifiers/elements.rs:18-18 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 15+ corresponding lines) · ×1
Edited copies of one member (3 members, 15+ corresponding lines) xilem_web/src/events.rs:231— xilem_web/src/events.rs:231-247 | xilem_web/src/events.rs:649-668 | xilem_web/src/pointer.rs:207-221 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×1
Edited copies of one member (3 members, 8+ corresponding lines) xilem_web/src/svg/kurbo_shape.rs:55— xilem_web/src/svg/kurbo_shape.rs:55-63 | xilem_web/src/svg/kurbo_shape.rs:112-120 | xilem_web/src/svg/kurbo_shape.rs:167-174 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×1
Edited copy of a member (10 corresponding lines) xilem_web/src/modifiers/style.rs:560— xilem_web/src/modifiers/style.rs:560-569 | xilem_web/src/modifiers/style.rs:685-694 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 13+ corresponding lines) · ×1
Edited copies of one member (3 members, 13+ corresponding lines) masonry/src/widgets/checkbox.rs:106— masonry/src/widgets/checkbox.rs:106-118 | masonry/src/widgets/radio_button.rs:153-165 | masonry/src/widgets/switch.rs:112-125 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×1
Edited copy of a member (7 corresponding lines) xilem_masonry/src/view/image.rs:81— xilem_masonry/src/view/image.rs:81-87 | xilem_masonry/src/view/svg.rs:71-77 — 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 copies of one member (4 members, 9+ corresponding lines) · ×1
Edited copies of one member (4 members, 9+ corresponding lines) xilem_web/src/modifiers/attribute.rs:199— xilem_web/src/modifiers/attribute.rs:199-207 | xilem_web/src/modifiers/attribute.rs:215-223 | xilem_web/src/modifiers/overwrite.rs:112-120 | xilem_web/src/modifiers/style.rs:331-339 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×1
Edited copy of a member (5 corresponding lines) masonry/src/widgets/zstack.rs:166— masonry/src/widgets/zstack.rs:166-170 | masonry/src/layers/selector_menu.rs:102-106 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (46–47 lines × 2) xilem_core/src/views/one_of.rs:396— xilem_core/src/views/one_of.rs:396-441 | xilem_core/src/views/one_of.rs:501-547 — 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 `xilem_core/src/views/one_of.rs:501` 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 (37 lines × 2) xilem_core/src/views/one_of.rs:261— xilem_core/src/views/one_of.rs:261-297 | xilem_core/src/views/one_of.rs:451-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. Read the line range as the matched WINDOW rather than a finished unit: at `xilem_core/src/views/one_of.rs:261` 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 (31 lines × 2) masonry/src/widgets/checkbox.rs:192— masonry/src/widgets/checkbox.rs:192-222 | masonry/src/widgets/radio_button.rs:241-271 — before extracting anything, compare `masonry/src/widgets/checkbox.rs` and `masonry/src/widgets/radio_button.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 98 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 (29 lines × 2) masonry/src/widgets/checkbox.rs:252— masonry/src/widgets/checkbox.rs:252-280 | masonry/src/widgets/radio_button.rs:301-329 — before extracting anything, compare `masonry/src/widgets/checkbox.rs` and `masonry/src/widgets/radio_button.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 98 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 `masonry/src/widgets/checkbox.rs:252` 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 (26 lines × 2) masonry_core/src/passes/update.rs:68— masonry_core/src/passes/update.rs:68-93 | masonry_core/src/passes/update.rs:114-139 — 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 (24 lines × 2) masonry/src/widgets/label.rs:522— masonry/src/widgets/label.rs:522-545 | masonry/src/widgets/text_area.rs:903-926 — 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 (21 lines × 2) xilem_web/src/modifiers/class.rs:269— xilem_web/src/modifiers/class.rs:269-289 | xilem_web/src/modifiers/style.rs:373-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. Read the line range as the matched WINDOW rather than a finished unit: at `xilem_web/src/modifiers/class.rs:269` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19–20 lines × 2) masonry/src/doc/vertical_stack.rs:99— masonry/src/doc/vertical_stack.rs:99-117 | masonry/src/layers/selector_menu.rs:246-265 — 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 `masonry/src/doc/vertical_stack.rs:99` 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, `masonry/src/layers/selector_menu.rs:241` calls `property_cache`, `get` and `masonry/src/doc/vertical_stack.rs:98` 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 (17 lines × 2) masonry/src/widgets/button.rs:183— masonry/src/widgets/button.rs:183-199 | masonry/src/widgets/selector.rs:240-257 — 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 `masonry/src/widgets/button.rs:183` 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 (16 lines × 2) masonry/src/widgets/checkbox.rs:225— masonry/src/widgets/checkbox.rs:225-240 | masonry/src/widgets/radio_button.rs:274-289 — before extracting anything, compare `masonry/src/widgets/checkbox.rs` and `masonry/src/widgets/radio_button.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 98 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 (15 lines × 2) masonry/src/theme.rs:85— masonry/src/theme.rs:85-99 | masonry/src/theme.rs:115-129 — 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 `masonry/src/theme.rs:85` 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–17 lines × 2) masonry_core/src/passes/layout.rs:137— masonry_core/src/passes/layout.rs:137-153 | masonry_core/src/passes/layout.rs:211-223 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `masonry_core/src/passes/layout.rs:226` calls `dim` and `masonry_core/src/passes/layout.rs:153` 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 (14 lines × 4) masonry_core/src/passes/anim.rs:37— masonry_core/src/passes/anim.rs:37-50 | masonry_core/src/passes/update.rs:324-337 | masonry_core/src/passes/update.rs:411-424 | masonry_core/src/passes/update.rs:1211-1224 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (7–8 lines × 3) masonry/src/widgets/checkbox.rs:249— masonry/src/widgets/checkbox.rs:249-256 | masonry/src/widgets/radio_button.rs:298-305 | masonry/src/widgets/slider.rs:344-350 — before extracting anything, compare `masonry/src/widgets/checkbox.rs` and `masonry/src/widgets/radio_button.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 98 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 `masonry/src/widgets/checkbox.rs:249` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `ctx` to `&mut LayoutCtx<'_>` in one and `&mut UpdateCtx<'_>` 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–8 lines × 3) masonry_core/src/passes/mutate.rs:17— masonry_core/src/passes/mutate.rs:17-22 | masonry_core/src/passes/update.rs:66-73 | masonry_core/src/passes/update.rs:112-119 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7–8 lines × 2) xilem_web/src/modifiers/attribute.rs:156— xilem_web/src/modifiers/attribute.rs:156-162 | xilem_web/src/modifiers/style.rs:287-294 — 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 `xilem_web/src/modifiers/style.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 `modifier` to `impl Into<AttributeModifier>` in one and `StyleModifier` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (8 lines × 5) masonry/src/layers/tooltip.rs:112— masonry/src/layers/tooltip.rs:112-119 | masonry/src/widgets/badge.rs:183-190 | masonry/src/widgets/button.rs:206-213 | masonry/src/widgets/selector.rs:264-271 | masonry/src/widgets/selector_item.rs:109-116 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. 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 (7 lines × 3) masonry_core/src/passes/update.rs:310— masonry_core/src/passes/update.rs:310-316 | masonry_core/src/passes/update.rs:397-403 | masonry_core/src/passes/update.rs:1203-1209 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 8) masonry_core/src/passes/accessibility.rs:24— masonry_core/src/passes/accessibility.rs:24-29 | masonry_core/src/passes/anim.rs:19-24 | masonry_core/src/passes/layout.rs:311-316 | masonry_core/src/passes/paint.rs:80-85 | masonry_core/src/passes/update.rs:156-161 | masonry_core/src/passes/update.rs:309-314 | masonry_core/src/passes/update.rs:396-401 | masonry_core/src/passes/update.rs:1202-1207 — there are 8 copies across 5 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 8 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (6 lines × 6) masonry/src/widgets/checkbox.rs:248— masonry/src/widgets/checkbox.rs:248-253 | masonry/src/widgets/progress_bar.rs:186-191 | masonry/src/widgets/radio_button.rs:297-302 | masonry/src/widgets/slider.rs:343-348 | masonry/src/widgets/text_input.rs:333-338 | masonry_core/src/core/widget_paint.rs:49-54 — before extracting anything, compare `masonry/src/widgets/checkbox.rs` and `masonry/src/widgets/radio_button.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 98 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 first that the copies are not typed on the same thing: the declarations holding them bind `ctx` to `&mut LayoutCtx<'_>` in one and `&mut UpdateCtx<'_>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 9) masonry_core/src/passes/accessibility.rs:25— masonry_core/src/passes/accessibility.rs:25-29 | masonry_core/src/passes/anim.rs:20-24 | masonry_core/src/passes/layout.rs:312-316 | masonry_core/src/passes/mutate.rs:19-23 | masonry_core/src/passes/paint.rs:81-85 | masonry_core/src/passes/update.rs:157-161 | masonry_core/src/passes/update.rs:310-314 | masonry_core/src/passes/update.rs:397-401 | masonry_core/src/passes/update.rs:1203-1207 — there are 9 copies across 6 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 9 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (6 lines × 5) masonry/src/layers/tooltip.rs:36— masonry/src/layers/tooltip.rs:36-41 | masonry/src/widgets/align.rs:101-106 | masonry/src/widgets/badge.rs:135-140 | masonry/src/widgets/button.rs:77-82 | masonry/src/widgets/collapse_panel.rs:81-86 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
Duplicated block (12 lines × 4) masonry/src/layers/tooltip.rs:98— masonry/src/layers/tooltip.rs:98-109 | masonry/src/widgets/badge.rs:169-180 | masonry/src/widgets/selector_item.rs:95-106 | masonry_testing/src/wrapper_widget.rs:104-115 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `masonry/src/layers/tooltip.rs:98` 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 `ctx` to `&mut RegisterCtx<'_>` in one and `&mut UpdateCtx<'_>` 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 (7 lines × 2) masonry/src/widgets/image.rs:157— masonry/src/widgets/image.rs:157-163 | masonry/src/widgets/svg.rs:153-159 — 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 `masonry/src/widgets/image.rs:157` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) masonry/src/widgets/checkbox.rs:337— masonry/src/widgets/checkbox.rs:337-344 | masonry/src/widgets/radio_button.rs:373-380 | masonry/src/widgets/switch.rs:298-305 — before extracting anything, compare `masonry/src/widgets/checkbox.rs` and `masonry/src/widgets/radio_button.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 98 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 `masonry/src/widgets/checkbox.rs:337` 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 × 4) xilem_masonry/src/view/flex.rs:255— xilem_masonry/src/view/flex.rs:255-259 | xilem_masonry/src/view/grid.rs:259-263 | xilem_masonry/src/view/indexed_stack.rs:161-165 | xilem_masonry/src/view/zstack.rs:129-133 — before extracting anything, compare `xilem_masonry/src/view/flex.rs` and `xilem_masonry/src/view/grid.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 58 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 `xilem_masonry/src/view/flex.rs:255` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 4) xilem_masonry/src/view/flex.rs:267— xilem_masonry/src/view/flex.rs:267-274 | xilem_masonry/src/view/grid.rs:271-278 | xilem_masonry/src/view/indexed_stack.rs:173-180 | xilem_masonry/src/view/zstack.rs:141-148 — before extracting anything, compare `xilem_masonry/src/view/flex.rs` and `xilem_masonry/src/view/grid.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 58 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 `xilem_masonry/src/view/flex.rs:267` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 4) xilem_masonry/src/view/flex.rs:322— xilem_masonry/src/view/flex.rs:322-332 | xilem_masonry/src/view/grid.rs:295-305 | xilem_masonry/src/view/indexed_stack.rs:197-207 | xilem_masonry/src/view/zstack.rs:286-296 — before extracting anything, compare `xilem_masonry/src/view/flex.rs` and `xilem_masonry/src/view/grid.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 58 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 `xilem_masonry/src/view/flex.rs:322` 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 × 3) masonry_core/src/core/contexts.rs:875— masonry_core/src/core/contexts.rs:875-886 | masonry_core/src/core/contexts.rs:1125-1136 | masonry_core/src/core/contexts.rs:1160-1171 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `masonry_core/src/core/contexts.rs:1138` calls `round` and `masonry_core/src/core/contexts.rs:1173` 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.
D4 · Code Duplication· Edited copies of one member (3 members, 6+ corresponding lines) · ×1
Edited copies of one member (3 members, 6+ corresponding lines) xilem_web/web_examples/elm/src/main.rs:49— xilem_web/web_examples/elm/src/main.rs:49-54 | xilem_web/web_examples/fetch/src/main.rs:214-221 | xilem_web/web_examples/spawn_tasks/src/main.rs:79-84 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Off the main sequence: masonry_imaging — masonry_imaging: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Orphaned file xilem_web/src/modifiers/overwrite.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file placehero/src/lib.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file xilem_web/src/modifiers/class.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file xilem_web/src/vecmap.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file xilem_web/src/modifiers/attribute.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file xilem_core/src/views/any_view.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file xilem_masonry/src/view/divider.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file placehero/src/login_flow/login_model.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file xilem_web/src/svg/common_attrs.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file xilem_masonry/src/view/badged.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file xilem_masonry/src/view/indexed_stack.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file xilem_web/src/concurrent/memoized_await.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file placehero/src/html_content.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file xilem_web/src/context.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file xilem_core/src/views/memoize.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file xilem_web/src/svg/kurbo_shape.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file xilem_masonry/src/view/worker.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file xilem_web/src/one_of.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file xilem_web/web_examples/fetch/src/main.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file xilem_web/src/after_update.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file xilem_web/web_examples/svgdraw/src/main.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file xilem_web/web_examples/todomvc/src/main.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file xilem_masonry/src/view/badge.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file xilem_core/src/message_context.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file xilem_core/src/message.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Interpolated log message defeats structured logging xilem_masonry/src/view/button.rs:247— `error!` at line 247 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging xilem_masonry/src/view/canvas.rs:120— `error!` at line 120 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging xilem_masonry/src/view/checkbox.rs:178— `error!` at line 178 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging xilem_masonry/src/view/radio_button.rs:138— `error!` at line 138 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging xilem_masonry/src/view/resize_observer.rs:169— `error!` at line 169 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging xilem_masonry/src/view/slider.rs:128— `error!` at line 128 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging xilem_masonry/src/view/split.rs:309— `error!` at line 309 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging xilem_masonry/src/view/switch.rs:119— `error!` at line 119 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging xilem_masonry/src/view/virtual_scroll.rs:418— `error!` at line 418 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging xilem_core/src/environment.rs:582— `warn!` at line 582 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging xilem/src/driver.rs:318— `error!` at line 318 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging placehero/src/avatars.rs:126— `warn!` at line 126 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging placehero/src/html_content.rs:44— `warn!` at line 44 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging placehero/src/html_content.rs:59— `warn!` at line 59 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging placehero/src/html_content.rs:183— `warn!` at line 183 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging placehero/src/lib.rs:377— `error!` at line 377 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging placehero/src/components/media.rs:79— `info!` at line 79 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging masonry_winit/src/event_loop_runner.rs:738— `error!` at line 738 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging masonry_winit/src/event_loop_runner.rs:763— `error!` at line 763 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging masonry_winit/src/event_loop_runner.rs:771— `error!` at line 771 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging masonry_winit/src/event_loop_runner.rs:824— `warn!` at line 824 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging masonry_winit/src/event_loop_runner.rs:1050— `trace!` at line 1050 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging masonry_winit/src/event_loop_runner.rs:1125— `info!` at line 1125 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging masonry_testing/src/harness.rs:624— `debug!` at line 624 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging masonry_testing/src/harness.rs:1096— `debug!` at line 1096 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 4 significant file(s) lose their only recent owner: masonry_core/src/core/widget_tag.rs, masonry_core/src/core/properties_mut.rs, masonry_core/src/core/properties_ref.rs, masonry_core/src/passes/mutate.rs. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 3 significant file(s) lose their only recent owner: masonry_imaging/src/texture_render.rs, masonry_imaging/src/lib.rs, masonry_core/src/app/visual_layers.rs. Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 2 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (9 single-owned of 213 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 213 of the 282 production source files in this repository met that bar). They are anonymized user #3 (1 file(s)), anonymized user #4 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: masonry/src/properties/object_fit.rs, xilem_web/web_examples/open_and_save_file/src/main.rs.
No ADRs found placehero/src/main.rs:1— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `placehero/src/main.rs` makes this repository a deployable product (line 1).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 12 project(s) overshoot their size bounds, lowering Project Cohesion to 8.3/10. The most over is `xilem_web` (9659 LoC, 500 module-visible types across 5 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.
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 61 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: xilem_web/src/modifiers/overwrite.rs, placehero/src/lib.rs, xilem_web/src/modifiers/class.rs, xilem_web/src/vecmap.rs, xilem_web/src/modifiers/attribute.rs, xilem_core/src/views/any_view.rs, xilem_masonry/src/view/divider.rs, placehero/src/login_flow/login_model.rs (and 53 more) (67 orphaned of 213 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 213 of the 282 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
Logging is not universal — Only 14/19 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `xilem_web/web_examples/counter`, `xilem_web/web_examples/counter_custom_element`, `xilem_web/web_examples/mathml_svg`, `xilem_web/web_examples/svgdraw`, `xilem_web/web_examples/svgtoy`.
Changelog looks stale/thin — The changelog this check read carries 0 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.
Duplicated predicate masonry/src/widgets/checkbox.rs:256— `ctx.is_focus_target() || ctx.is_hovered()` appears character-identically in 3 files — masonry/src/widgets/checkbox.rs, masonry/src/widgets/radio_button.rs, masonry/src/widgets/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.
Outdated: anyhow — `anyhow` is locked at 1.0.102 but 1.0.104 is the current stable release on crates.io, and it already satisfies the `"1.0.102"` requirement declared in placehero/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p anyhow` and commit the updated REDACTED.
Outdated: anymap3 — `anymap3` is locked at 1.0.1 but 1.1.0 is the current stable release on crates.io, and it already satisfies the `"1.0.1"` requirement declared in masonry_core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p anymap3` and commit the updated REDACTED.
Outdated: console_log — `console_log` is locked at 1.0.0 but 1.1.0 is the current stable release on crates.io, and it already satisfies the `"1.0.0"` requirement declared in xilem_web/web_examples/elm/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p console_log` and commit the updated REDACTED.
Outdated: futures-channel — `futures-channel` is locked at 0.3.32 but 0.3.34 is the current stable release on crates.io, and it already satisfies the `"0.3.32"` requirement declared in xilem_web/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p futures-channel` and commit the updated REDACTED.
Outdated: futures-util — `futures-util` is locked at 0.3.32 but 0.3.34 is the current stable release on crates.io, and it already satisfies the `"0.3.32"` requirement declared in xilem_web/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p futures-util` and commit the updated REDACTED.
Outdated: hashbrown — `hashbrown` is locked at 0.17.0 but 0.17.1 is the current stable release on crates.io, and it already satisfies the `"0.17.0"` requirement declared in tree_arena/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p hashbrown` and commit the updated REDACTED.
Outdated: log — `log` is locked at 0.4.29 but 0.4.35 is the current stable release on crates.io, and it already satisfies the `"0.4.29"` requirement declared in xilem_web/web_examples/elm/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p log` and commit the updated REDACTED.
Outdated: megalodon — `megalodon` is locked at 1.2.1 but 1.3.0 is the current stable release on crates.io, and it already satisfies the `"1.2.1"` requirement declared in placehero/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p megalodon` and commit the updated REDACTED.
Outdated: proc-macro2 — `proc-macro2` is locked at 1.0.106 but 1.0.107 is the current stable release on crates.io, and it already satisfies the `"1.0.106"` requirement declared in include_doc_path/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p proc-macro2` and commit the updated REDACTED.
Outdated: quote — `quote` is locked at 1.0.45 but 1.0.47 is the current stable release on crates.io, and it already satisfies the `"1.0.45"` requirement declared in include_doc_path/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p quote` and commit the updated REDACTED.
Outdated: serde — `serde` is locked at 1.0.228 but 1.0.229 is the current stable release on crates.io, and it already satisfies the `"1.0.228"` requirement declared in placehero/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde` and commit the updated REDACTED.
Outdated: serde_json — `serde_json` is locked at 1.0.149 but 1.0.154 is the current stable release on crates.io, and it already satisfies the `"1.0.149"` requirement declared in placehero/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde_json` and commit the updated REDACTED.
Outdated: smallvec — `smallvec` is locked at 1.15.1 but 1.16.5 is the current stable release on crates.io, and it already satisfies the `"1.15.1"` requirement declared in masonry/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p smallvec` and commit the updated REDACTED.
Outdated: time — `time` is locked at 0.3.47 but 0.3.55 is the current stable release on crates.io, and it already satisfies the `"0.3.47"` requirement declared in masonry_core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p time` and commit the updated REDACTED.
Outdated: tokio — `tokio` is locked at 1.50.0 but 1.54.1 is the current stable release on crates.io, and it already satisfies the `"1.50.0"` requirement declared in xilem/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tokio` and commit the updated REDACTED.
Outdated: wasm-bindgen — `wasm-bindgen` is locked at 0.2.114 but 0.2.130 is the current stable release on crates.io, and it already satisfies the `"0.2.114"` requirement declared in xilem_web/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p wasm-bindgen` and commit the updated REDACTED.
Outdated: wasm-bindgen-futures — `wasm-bindgen-futures` is locked at 0.4.64 but 0.4.80 is the current stable release on crates.io, and it already satisfies the `"0.4.64"` requirement declared in xilem_web/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p wasm-bindgen-futures` and commit the updated REDACTED.
Outdated: web-sys — `web-sys` is locked at 0.3.91 but 0.3.107 is the current stable release on crates.io, and it already satisfies the `"0.3.91"` requirement declared in xilem_web/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p web-sys` 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 01a1db6a-2979-7290-a793-b432d7652c69 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 49 · Warnings: 722 · Recommendations: 114 · Info: 18 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 18:55 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.