Executive summary
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 60 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 44, is the weakest lens and counts most in the score. The best first step is fixing focus, motion and contrast, worth about 7 points. Structuring the pages comes next, worth about 6 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,029 lines, about €87,000 to rebuild.
If Accessibility rose from 44 to 65, the lowest score rated Strong, the score would rise from 60 to about 70.
New since the last survey: 16 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Knowledge Freshness · Orphaned knowledge xilem_web/src/interfaces.rs
- Knowledge Freshness · Orphaned knowledge xilem_web/src/elements.rs
- Knowledge Freshness · Orphaned knowledge xilem_core/src/environment.rs
- Knowledge Freshness · Orphaned knowledge xilem_web/src/modifiers/style.rs
- Knowledge Freshness · Orphaned knowledge xilem_core/src/views/one_of.rs
- Knowledge Freshness · Orphaned knowledge xilem_web/src/events.rs
- Supply-chain Provenance & Signing · REDACTED
- Visual & motion safety · Animation without a prefers-reduced-motion guard xilem_web/web_examples/svgdraw/index.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard REDACTED
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement REDACTED
Fixed since the last survey: 3 findings
- Explicit Debt · FixmeComment masonry_testing/src/harness.rs
- Supply-chain Provenance & Signing REDACTED
- Visual & motion safety · Animation without a prefers-reduced-motion guard xilem_web/web_examples/fetch/index.html
Rebuild cost: about €87,000 · Estimate
| Cost to rebuild | €29,000 to €140,000, for 480 to 1,523 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.8 at a score of 60. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 68,029 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. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 masonry_core.core.events | 2 masonry_core.layout.length | 3 xilem_core.message | 4 masonry_core.core.properties_mut | 5 masonry_core.core.properties_ref | 6 masonry_core.core.widget_mut | 7 masonry_core.core.widget_pod | 8 masonry_core.layout.len_req | 9 xilem_core.message_context | 10 masonry_core.core.widget | 11 xilem_core.view | 12 masonry.widgets.button | 13 masonry_core.core.property | 14 masonry.widgets.flex | 15 masonry.widgets.image | 16 masonry.widgets.label | 17 xilem_core.environment | 18 xilem_core.docs | 19 xilem_masonry.view_ctx | 20 xilem_web.pod | 21 xilem_web.elements.svg | 22 xilem_web.interfaces | 23 masonry.widgets.portal | 24 xilem_core.element_splice | 25 xilem_masonry.view.flex | 26 xilem_masonry.view.zstack | 27 xilem_web.elements.html | 28 masonry_core.core.property_stack | 29 masonry_core.core.default_properties | 30 masonry_core.core.widget_state | 31 masonry_core.app.render_root | 32 masonry_core.core.contexts | 33 masonry_winit.event_loop_runner | 34 masonry.layers.selector_menu | 35 masonry.widgets.checkbox | 36 masonry.widgets.divider | 37 masonry.widgets.grid | 38 masonry.widgets.radio_button | 39 masonry.widgets.scroll_bar | 40 xilem_masonry.view.grid |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 masonry_core.core.events | ||||||||||||||||||||||||||||||||||||||||
| 2 masonry_core.layout.length | ||||||||||||||||||||||||||||||||||||||||
| 3 xilem_core.message | ||||||||||||||||||||||||||||||||||||||||
| 4 masonry_core.core.properties_mut | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 5 masonry_core.core.properties_ref | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 6 masonry_core.core.widget_mut | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 7 masonry_core.core.widget_pod | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 8 masonry_core.layout.len_req | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 xilem_core.message_context | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 masonry_core.core.widget | 3 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 11 | |||||||||||||||||||||||||||||||
| 11 xilem_core.view | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 12 masonry.widgets.button | 3 | 1 | 1 | 1 | 1 | 2 | 1 | 2 | 1 | 7 | ||||||||||||||||||||||||||||||
| 13 masonry_core.core.property | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 masonry.widgets.flex | 1 | 1 | 1 | 3 | 1 | 3 | 1 | 1 | 6 | |||||||||||||||||||||||||||||||
| 15 masonry.widgets.image | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 6 | ||||||||||||||||||||||||||||||
| 16 masonry.widgets.label | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 6 | ||||||||||||||||||||||||||||||
| 17 xilem_core.environment | 3 | 3 | 6 | 2 | 3 | |||||||||||||||||||||||||||||||||||
| 18 xilem_core.docs | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 xilem_masonry.view_ctx | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 xilem_web.pod | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 xilem_web.elements.svg | 63 | 63 | 126 | 1 | 63 | 63 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 22 xilem_web.interfaces | 129 | |||||||||||||||||||||||||||||||||||||||
| 23 masonry.widgets.portal | 3 | 1 | 1 | 1 | 1 | 2 | 1 | 2 | 1 | 1 | 1 | 8 | ||||||||||||||||||||||||||||
| 24 xilem_core.element_splice | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 xilem_masonry.view.flex | 4 | 2 | 4 | 8 | 2 | 4 | 5 | 2 | ||||||||||||||||||||||||||||||||
| 26 xilem_masonry.view.zstack | 2 | 2 | 2 | 4 | 2 | 3 | 2 | |||||||||||||||||||||||||||||||||
| 27 xilem_web.elements.html | 105 | 105 | 210 | 1 | 1 | 1 | 105 | 105 | 1 | 1 | ||||||||||||||||||||||||||||||
| 28 masonry_core.core.property_stack | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 masonry_core.core.default_properties | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 masonry_core.core.widget_state | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 31 masonry_core.app.render_root | 3 | 2 | 4 | 2 | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 32 masonry_core.core.contexts | 1 | 1 | 1 | 1 | 7 | 3 | 1 | 1 | 11 | 12 | ||||||||||||||||||||||||||||||
| 33 masonry_winit.event_loop_runner | 2 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 masonry.layers.selector_menu | 3 | 1 | 1 | 1 | 1 | 2 | 1 | 3 | 1 | 1 | 8 | |||||||||||||||||||||||||||||
| 35 masonry.widgets.checkbox | 3 | 1 | 1 | 1 | 1 | 2 | 1 | 2 | 1 | 1 | 7 | |||||||||||||||||||||||||||||
| 36 masonry.widgets.divider | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 2 | 1 | 1 | 1 | 6 | ||||||||||||||||||||||||||||
| 37 masonry.widgets.grid | 1 | 1 | 1 | 3 | 1 | 3 | 1 | 1 | 1 | 6 | ||||||||||||||||||||||||||||||
| 38 masonry.widgets.radio_button | 3 | 1 | 1 | 1 | 1 | 2 | 1 | 2 | 1 | 1 | 7 | |||||||||||||||||||||||||||||
| 39 masonry.widgets.scroll_bar | 2 | 1 | 1 | 1 | 1 | 1 | 3 | 1 | 1 | 1 | 7 | |||||||||||||||||||||||||||||
| 40 xilem_masonry.view.grid | 2 | 2 | 2 | 4 | 2 | 3 | 2 | 1 | 7 |
4→27 masonry_core.core.properties_mut uses xilem_web.elements.html part of a loop✕
- Connections
- 1 pair of types, where a type in masonry_core.core.properties_mut uses a type in xilem_web.elements.html.
- The types involved
masonry_core.core.properties_mut.PropertiesMut→xilem_web.elements.html.P
- Direction
- masonry_core.core.properties_mut uses xilem_web.elements.html, so a change to xilem_web.elements.html can break masonry_core.core.properties_mut, while a change to masonry_core.core.properties_mut can't break xilem_web.elements.html.
- 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.
4→28 masonry_core.core.properties_mut uses masonry_core.core.property_stack part of a loop✕
- Connections
- 1 pair of types, where a type in masonry_core.core.properties_mut uses a type in masonry_core.core.property_stack.
- The types involved
masonry_core.core.properties_mut.PropertiesMut→masonry_core.core.property_stack.PropertyStack
- 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
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→27 masonry_core.core.properties_ref uses xilem_web.elements.html part of a loop✕
- Connections
- 1 pair of types, where a type in masonry_core.core.properties_ref uses a type in xilem_web.elements.html.
- The types involved
masonry_core.core.properties_ref.PropertiesRef→xilem_web.elements.html.P
- Direction
- masonry_core.core.properties_ref uses xilem_web.elements.html, so a change to xilem_web.elements.html can break masonry_core.core.properties_ref, while a change to masonry_core.core.properties_ref can't break xilem_web.elements.html.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→28 masonry_core.core.properties_ref uses masonry_core.core.property_stack part of a loop✕
- Connections
- 1 pair of types, where a type in masonry_core.core.properties_ref uses a type in masonry_core.core.property_stack.
- The types involved
masonry_core.core.properties_ref.PropertiesRef→masonry_core.core.property_stack.PropertyStack
- 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
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→10 masonry_core.core.widget_mut uses masonry_core.core.widget part 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.
- The types involved
masonry_core.core.widget_mut.WidgetMut→masonry_core.core.widget.WidgetId
- Direction
- 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.
6→27 masonry_core.core.widget_mut uses xilem_web.elements.html part of a loop✕
- Connections
- 1 pair of types, where a type in masonry_core.core.widget_mut uses a type in xilem_web.elements.html.
- The types involved
masonry_core.core.widget_mut.WidgetMut→xilem_web.elements.html.P
- Direction
- masonry_core.core.widget_mut uses xilem_web.elements.html, so a change to xilem_web.elements.html can break masonry_core.core.widget_mut, while a change to masonry_core.core.widget_mut can't break xilem_web.elements.html.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→32 masonry_core.core.widget_mut uses masonry_core.core.contexts part 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.
- The types involved
masonry_core.core.widget_mut.WidgetMut→masonry_core.core.contexts.MutateCtx
- Direction
- 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.
7→10 masonry_core.core.widget_pod uses masonry_core.core.widget part 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.
- The types involved
masonry_core.core.widget_pod.NewWidget→masonry_core.core.widget.WidgetIdmasonry_core.core.widget_pod.WidgetPod→masonry_core.core.widget.WidgetId
- Direction
- 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.
7→28 masonry_core.core.widget_pod uses masonry_core.core.property_stack part of a loop✕
- Connections
- 1 pair of types, where a type in masonry_core.core.widget_pod uses a type in masonry_core.core.property_stack.
- The types involved
masonry_core.core.widget_pod.NewWidget→masonry_core.core.property_stack.PropertyStackId
- Direction
- 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
- 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.
8→2 masonry_core.layout.len_req uses masonry_core.layout.length✕
- Connections
- 1 pair of types, where a type in masonry_core.layout.len_req uses a type in masonry_core.layout.length.
- The types involved
masonry_core.layout.len_req.LenReq→masonry_core.layout.length.Length
- Direction
- 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.
9→3 xilem_core.message_context uses xilem_core.message✕
- Connections
- 1 pair of types, where a type in xilem_core.message_context uses a type in xilem_core.message.
- The types involved
xilem_core.message_context.MessageCtx→xilem_core.message.DynMessage
- 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.
9→17 xilem_core.message_context uses xilem_core.environment part of a loop✕
- Connections
- 1 pair of types, where a type in xilem_core.message_context uses a type in xilem_core.environment.
- The types involved
xilem_core.message_context.MessageCtx→xilem_core.environment.Environment
- Direction
- 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.
10→1 masonry_core.core.widget uses masonry_core.core.events✕
- Connections
- 3 pairs of types, where a type in masonry_core.core.widget uses a type in masonry_core.core.events.
- The types involved
masonry_core.core.widget.Widget→masonry_core.core.events.AccessEventmasonry_core.core.widget.Widget→masonry_core.core.events.TextEventmasonry_core.core.widget.Widget→masonry_core.core.events.Update
- Direction
- 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.
10→2 masonry_core.core.widget uses masonry_core.layout.length✕
- Connections
- 1 pair of types, where a type in masonry_core.core.widget uses a type in masonry_core.layout.length.
- The types involved
masonry_core.core.widget.Widget→masonry_core.layout.length.Length
- 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.
10→4 masonry_core.core.widget uses masonry_core.core.properties_mut✕
- Connections
- 1 pair of types, where a type in masonry_core.core.widget uses a type in masonry_core.core.properties_mut.
- The types involved
masonry_core.core.widget.Widget→masonry_core.core.properties_mut.PropertiesMut
- 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.
10→5 masonry_core.core.widget uses masonry_core.core.properties_ref✕
- Connections
- 1 pair of types, where a type in masonry_core.core.widget uses a type in masonry_core.core.properties_ref.
- The types involved
masonry_core.core.widget.Widget→masonry_core.core.properties_ref.PropertiesRef
- 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.
10→6 masonry_core.core.widget uses masonry_core.core.widget_mut✕
- Connections
- 1 pair of types, where a type in masonry_core.core.widget uses a type in masonry_core.core.widget_mut.
- The types involved
masonry_core.core.widget.CollectionWidget→masonry_core.core.widget_mut.WidgetMut
- 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.
10→7 masonry_core.core.widget uses masonry_core.core.widget_pod✕
- Connections
- 2 pairs of types, where a type in masonry_core.core.widget uses a type in masonry_core.core.widget_pod.
- The types involved
masonry_core.core.widget.CollectionWidget→masonry_core.core.widget_pod.NewWidgetmasonry_core.core.widget.Widget→masonry_core.core.widget_pod.NewWidget
- 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.
10→8 masonry_core.core.widget uses masonry_core.layout.len_req✕
- Connections
- 1 pair of types, where a type in masonry_core.core.widget uses a type in masonry_core.layout.len_req.
- The types involved
masonry_core.core.widget.Widget→masonry_core.layout.len_req.LenReq
- 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.
10→27 masonry_core.core.widget uses xilem_web.elements.html part of a loop✕
- Connections
- 1 pair of types, where a type in masonry_core.core.widget uses a type in xilem_web.elements.html.
- The types involved
masonry_core.core.widget.Widget→xilem_web.elements.html.Span
- Direction
- masonry_core.core.widget uses xilem_web.elements.html, so a change to xilem_web.elements.html can break masonry_core.core.widget, while a change to masonry_core.core.widget can't break xilem_web.elements.html.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→32 masonry_core.core.widget uses masonry_core.core.contexts part of a loop✕
- Connections
- 11 pairs of types, where a type in masonry_core.core.widget uses a type in masonry_core.core.contexts.
- The types involved
masonry_core.core.widget.Widget→masonry_core.core.contexts.AccessCtxmasonry_core.core.widget.Widget→masonry_core.core.contexts.ActionCtxmasonry_core.core.widget.Widget→masonry_core.core.contexts.ComposeCtxmasonry_core.core.widget.Widget→masonry_core.core.contexts.EventCtxmasonry_core.core.widget.Widget→masonry_core.core.contexts.LayoutCtxmasonry_core.core.widget.Widget→masonry_core.core.contexts.MeasureCtxmasonry_core.core.widget.Widget→masonry_core.core.contexts.PaintCtxmasonry_core.core.widget.Widget→masonry_core.core.contexts.QueryCtxmasonry_core.core.widget.Widget→masonry_core.core.contexts.RegisterCtxmasonry_core.core.widget.Widget→masonry_core.core.contexts.UpdateCtxmasonry_core.core.widget.widget$module→masonry_core.core.contexts.QueryCtx
- Direction
- 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.
11→3 xilem_core.view uses xilem_core.message✕
- Connections
- 1 pair of types, where a type in xilem_core.view uses a type in xilem_core.message.
- The types involved
xilem_core.view.View→xilem_core.message.MessageResult
- Direction
- 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.
11→9 xilem_core.view uses xilem_core.message_context✕
- Connections
- 1 pair of types, where a type in xilem_core.view uses a type in xilem_core.message_context.
- The types involved
xilem_core.view.View→xilem_core.message_context.MessageCtx
- 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.
11→18 xilem_core.view uses xilem_core.docs part 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.
12→1 masonry.widgets.button uses masonry_core.core.events✕
- Connections
- 3 pairs of types, where a type in masonry.widgets.button uses a type in masonry_core.core.events.
- The types involved
masonry.widgets.button.Button→masonry_core.core.events.AccessEventmasonry.widgets.button.Button→masonry_core.core.events.TextEventmasonry.widgets.button.Button→masonry_core.core.events.Update
- Direction
- masonry.widgets.button uses masonry_core.core.events, so a change to masonry_core.core.events can break masonry.widgets.button, while a change to masonry.widgets.button can't break masonry_core.core.events.
- Position
- Below the diagonal: masonry.widgets.button uses a module listed above it, which is the healthy direction.
12→2 masonry.widgets.button uses masonry_core.layout.length✕
- Connections
- 1 pair of types, where a type in masonry.widgets.button uses a type in masonry_core.layout.length.
- The types involved
masonry.widgets.button.Button→masonry_core.layout.length.Length
- Direction
- masonry.widgets.button uses masonry_core.layout.length, so a change to masonry_core.layout.length can break masonry.widgets.button, while a change to masonry.widgets.button can't break masonry_core.layout.length.
- Position
- Below the diagonal: masonry.widgets.button uses a module listed above it, which is the healthy direction.
12→4 masonry.widgets.button uses masonry_core.core.properties_mut✕
- Connections
- 1 pair of types, where a type in masonry.widgets.button uses a type in masonry_core.core.properties_mut.
- The types involved
masonry.widgets.button.Button→masonry_core.core.properties_mut.PropertiesMut
- Direction
- masonry.widgets.button uses masonry_core.core.properties_mut, so a change to masonry_core.core.properties_mut can break masonry.widgets.button, while a change to masonry.widgets.button can't break masonry_core.core.properties_mut.
- Position
- Below the diagonal: masonry.widgets.button uses a module listed above it, which is the healthy direction.
12→5 masonry.widgets.button uses masonry_core.core.properties_ref✕
- Connections
- 1 pair of types, where a type in masonry.widgets.button uses a type in masonry_core.core.properties_ref.
- The types involved
masonry.widgets.button.Button→masonry_core.core.properties_ref.PropertiesRef
- Direction
- masonry.widgets.button uses masonry_core.core.properties_ref, so a change to masonry_core.core.properties_ref can break masonry.widgets.button, while a change to masonry.widgets.button can't break masonry_core.core.properties_ref.
- Position
- Below the diagonal: masonry.widgets.button uses a module listed above it, which is the healthy direction.
12→6 masonry.widgets.button uses masonry_core.core.widget_mut✕
- Connections
- 1 pair of types, where a type in masonry.widgets.button uses a type in masonry_core.core.widget_mut.
- The types involved
masonry.widgets.button.Button→masonry_core.core.widget_mut.WidgetMut
- Direction
- masonry.widgets.button uses masonry_core.core.widget_mut, so a change to masonry_core.core.widget_mut can break masonry.widgets.button, while a change to masonry.widgets.button can't break masonry_core.core.widget_mut.
- Position
- Below the diagonal: masonry.widgets.button uses a module listed above it, which is the healthy direction.
12→7 masonry.widgets.button uses masonry_core.core.widget_pod✕
- Connections
- 2 pairs of types, where a type in masonry.widgets.button uses a type in masonry_core.core.widget_pod.
- The types involved
masonry.widgets.button.Button→masonry_core.core.widget_pod.NewWidgetmasonry.widgets.button.Button→masonry_core.core.widget_pod.WidgetPod
- Direction
- masonry.widgets.button uses masonry_core.core.widget_pod, so a change to masonry_core.core.widget_pod can break masonry.widgets.button, while a change to masonry.widgets.button can't break masonry_core.core.widget_pod.
- Position
- Below the diagonal: masonry.widgets.button uses a module listed above it, which is the healthy direction.
12→8 masonry.widgets.button uses masonry_core.layout.len_req✕
- Connections
- 1 pair of types, where a type in masonry.widgets.button uses a type in masonry_core.layout.len_req.
- The types involved
masonry.widgets.button.Button→masonry_core.layout.len_req.LenReq
- Direction
- masonry.widgets.button uses masonry_core.layout.len_req, so a change to masonry_core.layout.len_req can break masonry.widgets.button, while a change to masonry.widgets.button can't break masonry_core.layout.len_req.
- Position
- Below the diagonal: masonry.widgets.button uses a module listed above it, which is the healthy direction.
12→10 masonry.widgets.button uses masonry_core.core.widget✕
- Connections
- 2 pairs of types, where a type in masonry.widgets.button uses a type in masonry_core.core.widget.
- The types involved
masonry.widgets.button.Button→masonry_core.core.widget.Widgetmasonry.widgets.button.Button→masonry_core.core.widget.WidgetId
- Direction
- masonry.widgets.button uses masonry_core.core.widget, so a change to masonry_core.core.widget can break masonry.widgets.button, while a change to masonry.widgets.button can't break masonry_core.core.widget.
- Position
- Below the diagonal: masonry.widgets.button uses a module listed above it, which is the healthy direction.
12→27 masonry.widgets.button uses xilem_web.elements.html part of a loop✕
- Connections
- 1 pair of types, where a type in masonry.widgets.button uses a type in xilem_web.elements.html.
- The types involved
masonry.widgets.button.Button→xilem_web.elements.html.Span
- Direction
- masonry.widgets.button uses xilem_web.elements.html, so a change to xilem_web.elements.html can break masonry.widgets.button, while a change to masonry.widgets.button can't break xilem_web.elements.html.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→32 masonry.widgets.button uses masonry_core.core.contexts part of a loop✕
- Connections
- 7 pairs of types, where a type in masonry.widgets.button uses a type in masonry_core.core.contexts.
- The types involved
masonry.widgets.button.Button→masonry_core.core.contexts.AccessCtxmasonry.widgets.button.Button→masonry_core.core.contexts.EventCtxmasonry.widgets.button.Button→masonry_core.core.contexts.LayoutCtxmasonry.widgets.button.Button→masonry_core.core.contexts.MeasureCtxmasonry.widgets.button.Button→masonry_core.core.contexts.PaintCtxmasonry.widgets.button.Button→masonry_core.core.contexts.RegisterCtxmasonry.widgets.button.Button→masonry_core.core.contexts.UpdateCtx
- Direction
- masonry.widgets.button uses masonry_core.core.contexts, so a change to masonry_core.core.contexts can break masonry.widgets.button, while a change to masonry.widgets.button 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.
13→10 masonry_core.core.property uses masonry_core.core.widget✕
- Connections
- 1 pair of types, where a type in masonry_core.core.property uses a type in masonry_core.core.widget.
- The types involved
masonry_core.core.property.UsesProperty→masonry_core.core.widget.Widget
- Direction
- 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.
14→2 masonry.widgets.flex uses masonry_core.layout.length✕
- Connections
- 1 pair of types, where a type in masonry.widgets.flex uses a type in masonry_core.layout.length.
- The types involved
masonry.widgets.flex.Flex→masonry_core.layout.length.Length
- 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.
14→5 masonry.widgets.flex uses masonry_core.core.properties_ref✕
- Connections
- 1 pair of types, where a type in masonry.widgets.flex uses a type in masonry_core.core.properties_ref.
- The types involved
masonry.widgets.flex.Flex→masonry_core.core.properties_ref.PropertiesRef
- 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.
14→6 masonry.widgets.flex uses masonry_core.core.widget_mut✕
- Connections
- 1 pair of types, where a type in masonry.widgets.flex uses a type in masonry_core.core.widget_mut.
- The types involved
masonry.widgets.flex.Flex→masonry_core.core.widget_mut.WidgetMut
- 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.
14→7 masonry.widgets.flex uses masonry_core.core.widget_pod✕
- Connections
- 3 pairs of types, where a type in masonry.widgets.flex uses a type in masonry_core.core.widget_pod.
- The types involved
masonry.widgets.flex.Child→masonry_core.core.widget_pod.WidgetPodmasonry.widgets.flex.Flex→masonry_core.core.widget_pod.NewWidgetmasonry.widgets.flex.flex$module→masonry_core.core.widget_pod.WidgetPod
- 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.
14→8 masonry.widgets.flex uses masonry_core.layout.len_req✕
- Connections
- 1 pair of types, where a type in masonry.widgets.flex uses a type in masonry_core.layout.len_req.
- The types involved
masonry.widgets.flex.Flex→masonry_core.layout.len_req.LenReq
- 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.
14→10 masonry.widgets.flex uses masonry_core.core.widget✕
- Connections
- 3 pairs of types, where a type in masonry.widgets.flex uses a type in masonry_core.core.widget.
- The types involved
masonry.widgets.flex.Flex→masonry_core.core.widget.CollectionWidgetmasonry.widgets.flex.Flex→masonry_core.core.widget.Widgetmasonry.widgets.flex.Flex→masonry_core.core.widget.WidgetId
- 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.
14→13 masonry.widgets.flex uses masonry_core.core.property✕
- Connections
- 1 pair of types, where a type in masonry.widgets.flex uses a type in masonry_core.core.property.
- The types involved
masonry.widgets.flex.Flex→masonry_core.core.property.UsesProperty
- 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.
14→27 masonry.widgets.flex uses xilem_web.elements.html part of a loop✕
- Connections
- 1 pair of types, where a type in masonry.widgets.flex uses a type in xilem_web.elements.html.
- The types involved
masonry.widgets.flex.Flex→xilem_web.elements.html.Span
- Direction
- masonry.widgets.flex uses xilem_web.elements.html, so a change to xilem_web.elements.html can break masonry.widgets.flex, while a change to masonry.widgets.flex can't break xilem_web.elements.html.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→32 masonry.widgets.flex uses masonry_core.core.contexts part of a loop✕
- Connections
- 6 pairs of types, where a type in masonry.widgets.flex uses a type in masonry_core.core.contexts.
- The types involved
masonry.widgets.flex.Flex→masonry_core.core.contexts.AccessCtxmasonry.widgets.flex.Flex→masonry_core.core.contexts.LayoutCtxmasonry.widgets.flex.Flex→masonry_core.core.contexts.MeasureCtxmasonry.widgets.flex.Flex→masonry_core.core.contexts.PaintCtxmasonry.widgets.flex.Flex→masonry_core.core.contexts.RegisterCtxmasonry.widgets.flex.Flex→masonry_core.core.contexts.UpdateCtx
- 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
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→1 masonry.widgets.image uses masonry_core.core.events✕
- Connections
- 1 pair of types, where a type in masonry.widgets.image uses a type in masonry_core.core.events.
- The types involved
masonry.widgets.image.Image→masonry_core.core.events.Update
- Direction
- masonry.widgets.image uses masonry_core.core.events, so a change to masonry_core.core.events can break masonry.widgets.image, while a change to masonry.widgets.image can't break masonry_core.core.events.
- Position
- Below the diagonal: masonry.widgets.image uses a module listed above it, which is the healthy direction.
15→2 masonry.widgets.image uses masonry_core.layout.length✕
- Connections
- 1 pair of types, where a type in masonry.widgets.image uses a type in masonry_core.layout.length.
- The types involved
masonry.widgets.image.Image→masonry_core.layout.length.Length
- Direction
- masonry.widgets.image uses masonry_core.layout.length, so a change to masonry_core.layout.length can break masonry.widgets.image, while a change to masonry.widgets.image can't break masonry_core.layout.length.
- Position
- Below the diagonal: masonry.widgets.image uses a module listed above it, which is the healthy direction.
15→4 masonry.widgets.image uses masonry_core.core.properties_mut✕
- Connections
- 1 pair of types, where a type in masonry.widgets.image uses a type in masonry_core.core.properties_mut.
- The types involved
masonry.widgets.image.Image→masonry_core.core.properties_mut.PropertiesMut
- Direction
- masonry.widgets.image uses masonry_core.core.properties_mut, so a change to masonry_core.core.properties_mut can break masonry.widgets.image, while a change to masonry.widgets.image can't break masonry_core.core.properties_mut.
- Position
- Below the diagonal: masonry.widgets.image uses a module listed above it, which is the healthy direction.
15→5 masonry.widgets.image uses masonry_core.core.properties_ref✕
- Connections
- 1 pair of types, where a type in masonry.widgets.image uses a type in masonry_core.core.properties_ref.
- The types involved
masonry.widgets.image.Image→masonry_core.core.properties_ref.PropertiesRef
- Direction
- masonry.widgets.image uses masonry_core.core.properties_ref, so a change to masonry_core.core.properties_ref can break masonry.widgets.image, while a change to masonry.widgets.image can't break masonry_core.core.properties_ref.
- Position
- Below the diagonal: masonry.widgets.image uses a module listed above it, which is the healthy direction.
15→6 masonry.widgets.image uses masonry_core.core.widget_mut✕
- Connections
- 1 pair of types, where a type in masonry.widgets.image uses a type in masonry_core.core.widget_mut.
- The types involved
masonry.widgets.image.Image→masonry_core.core.widget_mut.WidgetMut
- Direction
- masonry.widgets.image uses masonry_core.core.widget_mut, so a change to masonry_core.core.widget_mut can break masonry.widgets.image, while a change to masonry.widgets.image can't break masonry_core.core.widget_mut.
- Position
- Below the diagonal: masonry.widgets.image uses a module listed above it, which is the healthy direction.
15→8 masonry.widgets.image uses masonry_core.layout.len_req✕
- Connections
- 1 pair of types, where a type in masonry.widgets.image uses a type in masonry_core.layout.len_req.
- The types involved
masonry.widgets.image.Image→masonry_core.layout.len_req.LenReq
- Direction
- masonry.widgets.image uses masonry_core.layout.len_req, so a change to masonry_core.layout.len_req can break masonry.widgets.image, while a change to masonry.widgets.image can't break masonry_core.layout.len_req.
- Position
- Below the diagonal: masonry.widgets.image uses a module listed above it, which is the healthy direction.
15→10 masonry.widgets.image uses masonry_core.core.widget✕
- Connections
- 2 pairs of types, where a type in masonry.widgets.image uses a type in masonry_core.core.widget.
- The types involved
masonry.widgets.image.Image→masonry_core.core.widget.Widgetmasonry.widgets.image.Image→masonry_core.core.widget.WidgetId
- Direction
- masonry.widgets.image uses masonry_core.core.widget, so a change to masonry_core.core.widget can break masonry.widgets.image, while a change to masonry.widgets.image can't break masonry_core.core.widget.
- Position
- Below the diagonal: masonry.widgets.image uses a module listed above it, which is the healthy direction.
15→13 masonry.widgets.image uses masonry_core.core.property✕
- Connections
- 1 pair of types, where a type in masonry.widgets.image uses a type in masonry_core.core.property.
- The types involved
masonry.widgets.image.Image→masonry_core.core.property.UsesProperty
- Direction
- masonry.widgets.image uses masonry_core.core.property, so a change to masonry_core.core.property can break masonry.widgets.image, while a change to masonry.widgets.image can't break masonry_core.core.property.
- Position
- Below the diagonal: masonry.widgets.image uses a module listed above it, which is the healthy direction.
15→27 masonry.widgets.image uses xilem_web.elements.html part of a loop✕
- Connections
- 1 pair of types, where a type in masonry.widgets.image uses a type in xilem_web.elements.html.
- The types involved
masonry.widgets.image.Image→xilem_web.elements.html.Span
- Direction
- masonry.widgets.image uses xilem_web.elements.html, so a change to xilem_web.elements.html can break masonry.widgets.image, while a change to masonry.widgets.image can't break xilem_web.elements.html.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→32 masonry.widgets.image uses masonry_core.core.contexts part of a loop✕
- Connections
- 6 pairs of types, where a type in masonry.widgets.image uses a type in masonry_core.core.contexts.
- The types involved
masonry.widgets.image.Image→masonry_core.core.contexts.AccessCtxmasonry.widgets.image.Image→masonry_core.core.contexts.LayoutCtxmasonry.widgets.image.Image→masonry_core.core.contexts.MeasureCtxmasonry.widgets.image.Image→masonry_core.core.contexts.PaintCtxmasonry.widgets.image.Image→masonry_core.core.contexts.RegisterCtxmasonry.widgets.image.Image→masonry_core.core.contexts.UpdateCtx
- Direction
- masonry.widgets.image uses masonry_core.core.contexts, so a change to masonry_core.core.contexts can break masonry.widgets.image, while a change to masonry.widgets.image 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.
16→1 masonry.widgets.label uses masonry_core.core.events✕
- Connections
- 1 pair of types, where a type in masonry.widgets.label uses a type in masonry_core.core.events.
- The types involved
masonry.widgets.label.Label→masonry_core.core.events.Update
- Direction
- masonry.widgets.label uses masonry_core.core.events, so a change to masonry_core.core.events can break masonry.widgets.label, while a change to masonry.widgets.label can't break masonry_core.core.events.
- Position
- Below the diagonal: masonry.widgets.label uses a module listed above it, which is the healthy direction.
16→2 masonry.widgets.label uses masonry_core.layout.length✕
- Connections
- 1 pair of types, where a type in masonry.widgets.label uses a type in masonry_core.layout.length.
- The types involved
masonry.widgets.label.Label→masonry_core.layout.length.Length
- Direction
- masonry.widgets.label uses masonry_core.layout.length, so a change to masonry_core.layout.length can break masonry.widgets.label, while a change to masonry.widgets.label can't break masonry_core.layout.length.
- Position
- Below the diagonal: masonry.widgets.label uses a module listed above it, which is the healthy direction.
16→4 masonry.widgets.label uses masonry_core.core.properties_mut✕
- Connections
- 1 pair of types, where a type in masonry.widgets.label uses a type in masonry_core.core.properties_mut.
- The types involved
masonry.widgets.label.Label→masonry_core.core.properties_mut.PropertiesMut
- Direction
- masonry.widgets.label uses masonry_core.core.properties_mut, so a change to masonry_core.core.properties_mut can break masonry.widgets.label, while a change to masonry.widgets.label can't break masonry_core.core.properties_mut.
- Position
- Below the diagonal: masonry.widgets.label uses a module listed above it, which is the healthy direction.
16→5 masonry.widgets.label uses masonry_core.core.properties_ref✕
- Connections
- 1 pair of types, where a type in masonry.widgets.label uses a type in masonry_core.core.properties_ref.
- The types involved
masonry.widgets.label.Label→masonry_core.core.properties_ref.PropertiesRef
- Direction
- masonry.widgets.label uses masonry_core.core.properties_ref, so a change to masonry_core.core.properties_ref can break masonry.widgets.label, while a change to masonry.widgets.label can't break masonry_core.core.properties_ref.
- Position
- Below the diagonal: masonry.widgets.label uses a module listed above it, which is the healthy direction.
16→6 masonry.widgets.label uses masonry_core.core.widget_mut✕
- Connections
- 1 pair of types, where a type in masonry.widgets.label uses a type in masonry_core.core.widget_mut.
- The types involved
masonry.widgets.label.Label→masonry_core.core.widget_mut.WidgetMut
- Direction
- masonry.widgets.label uses masonry_core.core.widget_mut, so a change to masonry_core.core.widget_mut can break masonry.widgets.label, while a change to masonry.widgets.label can't break masonry_core.core.widget_mut.
- Position
- Below the diagonal: masonry.widgets.label uses a module listed above it, which is the healthy direction.
16→8 masonry.widgets.label uses masonry_core.layout.len_req✕
- Connections
- 1 pair of types, where a type in masonry.widgets.label uses a type in masonry_core.layout.len_req.
- The types involved
masonry.widgets.label.Label→masonry_core.layout.len_req.LenReq
- Direction
- masonry.widgets.label uses masonry_core.layout.len_req, so a change to masonry_core.layout.len_req can break masonry.widgets.label, while a change to masonry.widgets.label can't break masonry_core.layout.len_req.
- Position
- Below the diagonal: masonry.widgets.label uses a module listed above it, which is the healthy direction.
16→10 masonry.widgets.label uses masonry_core.core.widget✕
- Connections
- 2 pairs of types, where a type in masonry.widgets.label uses a type in masonry_core.core.widget.
- The types involved
masonry.widgets.label.Label→masonry_core.core.widget.Widgetmasonry.widgets.label.Label→masonry_core.core.widget.WidgetId
- Direction
- masonry.widgets.label uses masonry_core.core.widget, so a change to masonry_core.core.widget can break masonry.widgets.label, while a change to masonry.widgets.label can't break masonry_core.core.widget.
- Position
- Below the diagonal: masonry.widgets.label uses a module listed above it, which is the healthy direction.
16→13 masonry.widgets.label uses masonry_core.core.property✕
- Connections
- 1 pair of types, where a type in masonry.widgets.label uses a type in masonry_core.core.property.
- The types involved
masonry.widgets.label.Label→masonry_core.core.property.UsesProperty
- Direction
- masonry.widgets.label uses masonry_core.core.property, so a change to masonry_core.core.property can break masonry.widgets.label, while a change to masonry.widgets.label can't break masonry_core.core.property.
- Position
- Below the diagonal: masonry.widgets.label uses a module listed above it, which is the healthy direction.
16→27 masonry.widgets.label uses xilem_web.elements.html part of a loop✕
- Connections
- 1 pair of types, where a type in masonry.widgets.label uses a type in xilem_web.elements.html.
- The types involved
masonry.widgets.label.Label→xilem_web.elements.html.Span
- Direction
- masonry.widgets.label uses xilem_web.elements.html, so a change to xilem_web.elements.html can break masonry.widgets.label, while a change to masonry.widgets.label can't break xilem_web.elements.html.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→32 masonry.widgets.label uses masonry_core.core.contexts part of a loop✕
- Connections
- 6 pairs of types, where a type in masonry.widgets.label uses a type in masonry_core.core.contexts.
- The types involved
masonry.widgets.label.Label→masonry_core.core.contexts.AccessCtxmasonry.widgets.label.Label→masonry_core.core.contexts.LayoutCtxmasonry.widgets.label.Label→masonry_core.core.contexts.MeasureCtxmasonry.widgets.label.Label→masonry_core.core.contexts.PaintCtxmasonry.widgets.label.Label→masonry_core.core.contexts.RegisterCtxmasonry.widgets.label.Label→masonry_core.core.contexts.UpdateCtx
- Direction
- masonry.widgets.label uses masonry_core.core.contexts, so a change to masonry_core.core.contexts can break masonry.widgets.label, while a change to masonry.widgets.label 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.
17→3 xilem_core.environment uses xilem_core.message✕
- Connections
- 3 pairs of types, where a type in xilem_core.environment uses a type in xilem_core.message.
- The types involved
xilem_core.environment.OnActionWithContext→xilem_core.message.MessageResultxilem_core.environment.Provides→xilem_core.message.MessageResultxilem_core.environment.WithContext→xilem_core.message.MessageResult
- 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.
17→9 xilem_core.environment uses xilem_core.message_context✕
- Connections
- 3 pairs of types, where a type in xilem_core.environment uses a type in xilem_core.message_context.
- The types involved
xilem_core.environment.OnActionWithContext→xilem_core.message_context.MessageCtxxilem_core.environment.Provides→xilem_core.message_context.MessageCtxxilem_core.environment.WithContext→xilem_core.message_context.MessageCtx
- 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.
17→11 xilem_core.environment uses xilem_core.view✕
- Connections
- 6 pairs of types, where a type in xilem_core.environment uses a type in xilem_core.view.
- The types involved
xilem_core.environment.OnActionWithContext→xilem_core.view.Viewxilem_core.environment.OnActionWithContext→xilem_core.view.ViewMarkerxilem_core.environment.Provides→xilem_core.view.Viewxilem_core.environment.Provides→xilem_core.view.ViewMarkerxilem_core.environment.WithContext→xilem_core.view.Viewxilem_core.environment.WithContext→xilem_core.view.ViewMarker
- 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.
17→14 xilem_core.environment uses masonry.widgets.flex✕
- Connections
- 2 pairs of types, where a type in xilem_core.environment uses a type in masonry.widgets.flex.
- The types involved
xilem_core.environment.WithContext→masonry.widgets.flex.Childxilem_core.environment.environment$module→masonry.widgets.flex.Child
- Direction
- xilem_core.environment uses masonry.widgets.flex, so a change to masonry.widgets.flex can break xilem_core.environment, while a change to xilem_core.environment can't break masonry.widgets.flex.
- Position
- Below the diagonal: xilem_core.environment uses a module listed above it, which is the healthy direction.
17→18 xilem_core.environment uses xilem_core.docs part of a loop✕
- Connections
- 3 pairs of types, where a type in xilem_core.environment uses a type in xilem_core.docs.
- The types involved
xilem_core.environment.OnActionWithContext→xilem_core.docs.Statexilem_core.environment.Provides→xilem_core.docs.Statexilem_core.environment.WithContext→xilem_core.docs.State
- Direction
- 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.
18→11 xilem_core.docs uses xilem_core.view✕
- Connections
- 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.
18→17 xilem_core.docs uses xilem_core.environment✕
- Connections
- 1 pair of types, where a type in xilem_core.docs uses a type in xilem_core.environment.
- The types involved
xilem_core.docs.Fake→xilem_core.environment.Environment
- 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.
19→6 xilem_masonry.view_ctx uses masonry_core.core.widget_mut✕
- Connections
- 1 pair of types, where a type in xilem_masonry.view_ctx uses a type in masonry_core.core.widget_mut.
- The types involved
xilem_masonry.view_ctx.ViewCtx→masonry_core.core.widget_mut.WidgetMut
- 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.
19→10 xilem_masonry.view_ctx uses masonry_core.core.widget✕
- Connections
- 1 pair of types, where a type in xilem_masonry.view_ctx uses a type in masonry_core.core.widget.
- The types involved
xilem_masonry.view_ctx.ViewCtx→masonry_core.core.widget.WidgetId
- 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.
19→17 xilem_masonry.view_ctx uses xilem_core.environment✕
- Connections
- 1 pair of types, where a type in xilem_masonry.view_ctx uses a type in xilem_core.environment.
- The types involved
xilem_masonry.view_ctx.ViewCtx→xilem_core.environment.Environment
- 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.
20→19 xilem_web.pod uses xilem_masonry.view_ctx✕
- Connections
- 1 pair of types, where a type in xilem_web.pod uses a type in xilem_masonry.view_ctx.
- The types involved
xilem_web.pod.Pod→xilem_masonry.view_ctx.ViewCtx
- Direction
- xilem_web.pod uses xilem_masonry.view_ctx, so a change to xilem_masonry.view_ctx can break xilem_web.pod, while a change to xilem_web.pod can't break xilem_masonry.view_ctx.
- Position
- Below the diagonal: xilem_web.pod uses a module listed above it, which is the healthy direction.
21→3 xilem_web.elements.svg uses xilem_core.message✕
- Connections
- 63 pairs of types, where a type in xilem_web.elements.svg uses a type in xilem_core.message. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
xilem_web.elements.svg.A→xilem_core.message.MessageResultxilem_web.elements.svg.Animate→xilem_core.message.MessageResultxilem_web.elements.svg.AnimateMotion→xilem_core.message.MessageResultxilem_web.elements.svg.AnimateTransform→xilem_core.message.MessageResultxilem_web.elements.svg.Circle→xilem_core.message.MessageResultxilem_web.elements.svg.ClipPath→xilem_core.message.MessageResultxilem_web.elements.svg.Defs→xilem_core.message.MessageResultxilem_web.elements.svg.Desc→xilem_core.message.MessageResultxilem_web.elements.svg.Ellipse→xilem_core.message.MessageResultxilem_web.elements.svg.FeBlend→xilem_core.message.MessageResultxilem_web.elements.svg.FeColorMatrix→xilem_core.message.MessageResultxilem_web.elements.svg.FeComponentTransfer→xilem_core.message.MessageResultxilem_web.elements.svg.FeComposite→xilem_core.message.MessageResultxilem_web.elements.svg.FeConvolveMatrix→xilem_core.message.MessageResultxilem_web.elements.svg.FeDiffuseLighting→xilem_core.message.MessageResultxilem_web.elements.svg.FeDisplacementMap→xilem_core.message.MessageResultxilem_web.elements.svg.FeDistantLight→xilem_core.message.MessageResultxilem_web.elements.svg.FeDropShadow→xilem_core.message.MessageResultxilem_web.elements.svg.FeFlood→xilem_core.message.MessageResultxilem_web.elements.svg.FeFuncA→xilem_core.message.MessageResultxilem_web.elements.svg.FeFuncB→xilem_core.message.MessageResultxilem_web.elements.svg.FeFuncG→xilem_core.message.MessageResultxilem_web.elements.svg.FeFuncR→xilem_core.message.MessageResultxilem_web.elements.svg.FeGaussianBlur→xilem_core.message.MessageResultxilem_web.elements.svg.FeImage→xilem_core.message.MessageResult
- Direction
- xilem_web.elements.svg uses xilem_core.message, so a change to xilem_core.message can break xilem_web.elements.svg, while a change to xilem_web.elements.svg can't break xilem_core.message.
- Position
- Below the diagonal: xilem_web.elements.svg uses a module listed above it, which is the healthy direction.
21→9 xilem_web.elements.svg uses xilem_core.message_context✕
- Connections
- 63 pairs of types, where a type in xilem_web.elements.svg uses a type in xilem_core.message_context. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
xilem_web.elements.svg.A→xilem_core.message_context.MessageCtxxilem_web.elements.svg.Animate→xilem_core.message_context.MessageCtxxilem_web.elements.svg.AnimateMotion→xilem_core.message_context.MessageCtxxilem_web.elements.svg.AnimateTransform→xilem_core.message_context.MessageCtxxilem_web.elements.svg.Circle→xilem_core.message_context.MessageCtxxilem_web.elements.svg.ClipPath→xilem_core.message_context.MessageCtxxilem_web.elements.svg.Defs→xilem_core.message_context.MessageCtxxilem_web.elements.svg.Desc→xilem_core.message_context.MessageCtxxilem_web.elements.svg.Ellipse→xilem_core.message_context.MessageCtxxilem_web.elements.svg.FeBlend→xilem_core.message_context.MessageCtxxilem_web.elements.svg.FeColorMatrix→xilem_core.message_context.MessageCtxxilem_web.elements.svg.FeComponentTransfer→xilem_core.message_context.MessageCtxxilem_web.elements.svg.FeComposite→xilem_core.message_context.MessageCtxxilem_web.elements.svg.FeConvolveMatrix→xilem_core.message_context.MessageCtxxilem_web.elements.svg.FeDiffuseLighting→xilem_core.message_context.MessageCtxxilem_web.elements.svg.FeDisplacementMap→xilem_core.message_context.MessageCtxxilem_web.elements.svg.FeDistantLight→xilem_core.message_context.MessageCtxxilem_web.elements.svg.FeDropShadow→xilem_core.message_context.MessageCtxxilem_web.elements.svg.FeFlood→xilem_core.message_context.MessageCtxxilem_web.elements.svg.FeFuncA→xilem_core.message_context.MessageCtxxilem_web.elements.svg.FeFuncB→xilem_core.message_context.MessageCtxxilem_web.elements.svg.FeFuncG→xilem_core.message_context.MessageCtxxilem_web.elements.svg.FeFuncR→xilem_core.message_context.MessageCtxxilem_web.elements.svg.FeGaussianBlur→xilem_core.message_context.MessageCtxxilem_web.elements.svg.FeImage→xilem_core.message_context.MessageCtx
- Direction
- xilem_web.elements.svg uses xilem_core.message_context, so a change to xilem_core.message_context can break xilem_web.elements.svg, while a change to xilem_web.elements.svg can't break xilem_core.message_context.
- Position
- Below the diagonal: xilem_web.elements.svg uses a module listed above it, which is the healthy direction.
21→11 xilem_web.elements.svg uses xilem_core.view✕
- Connections
- 126 pairs of types, where a type in xilem_web.elements.svg uses a type in xilem_core.view. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
xilem_web.elements.svg.A→xilem_core.view.Viewxilem_web.elements.svg.A→xilem_core.view.ViewMarkerxilem_web.elements.svg.Animate→xilem_core.view.Viewxilem_web.elements.svg.Animate→xilem_core.view.ViewMarkerxilem_web.elements.svg.AnimateMotion→xilem_core.view.Viewxilem_web.elements.svg.AnimateMotion→xilem_core.view.ViewMarkerxilem_web.elements.svg.AnimateTransform→xilem_core.view.Viewxilem_web.elements.svg.AnimateTransform→xilem_core.view.ViewMarkerxilem_web.elements.svg.Circle→xilem_core.view.Viewxilem_web.elements.svg.Circle→xilem_core.view.ViewMarkerxilem_web.elements.svg.ClipPath→xilem_core.view.Viewxilem_web.elements.svg.ClipPath→xilem_core.view.ViewMarkerxilem_web.elements.svg.Defs→xilem_core.view.Viewxilem_web.elements.svg.Defs→xilem_core.view.ViewMarkerxilem_web.elements.svg.Desc→xilem_core.view.Viewxilem_web.elements.svg.Desc→xilem_core.view.ViewMarkerxilem_web.elements.svg.Ellipse→xilem_core.view.Viewxilem_web.elements.svg.Ellipse→xilem_core.view.ViewMarkerxilem_web.elements.svg.FeBlend→xilem_core.view.Viewxilem_web.elements.svg.FeBlend→xilem_core.view.ViewMarkerxilem_web.elements.svg.FeColorMatrix→xilem_core.view.Viewxilem_web.elements.svg.FeColorMatrix→xilem_core.view.ViewMarkerxilem_web.elements.svg.FeComponentTransfer→xilem_core.view.Viewxilem_web.elements.svg.FeComponentTransfer→xilem_core.view.ViewMarkerxilem_web.elements.svg.FeComposite→xilem_core.view.View
- Direction
- xilem_web.elements.svg uses xilem_core.view, so a change to xilem_core.view can break xilem_web.elements.svg, while a change to xilem_web.elements.svg can't break xilem_core.view.
- Position
- Below the diagonal: xilem_web.elements.svg uses a module listed above it, which is the healthy direction.
21→15 xilem_web.elements.svg uses masonry.widgets.image✕
- Connections
- 1 pair of types, where a type in xilem_web.elements.svg uses a type in masonry.widgets.image.
- The types involved
xilem_web.elements.svg.svg$module→masonry.widgets.image.Image
- Direction
- xilem_web.elements.svg uses masonry.widgets.image, so a change to masonry.widgets.image can break xilem_web.elements.svg, while a change to xilem_web.elements.svg can't break masonry.widgets.image.
- Position
- Below the diagonal: xilem_web.elements.svg uses a module listed above it, which is the healthy direction.
21→18 xilem_web.elements.svg uses xilem_core.docs✕
- Connections
- 63 pairs of types, where a type in xilem_web.elements.svg uses a type in xilem_core.docs. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
xilem_web.elements.svg.A→xilem_core.docs.Statexilem_web.elements.svg.Animate→xilem_core.docs.Statexilem_web.elements.svg.AnimateMotion→xilem_core.docs.Statexilem_web.elements.svg.AnimateTransform→xilem_core.docs.Statexilem_web.elements.svg.Circle→xilem_core.docs.Statexilem_web.elements.svg.ClipPath→xilem_core.docs.Statexilem_web.elements.svg.Defs→xilem_core.docs.Statexilem_web.elements.svg.Desc→xilem_core.docs.Statexilem_web.elements.svg.Ellipse→xilem_core.docs.Statexilem_web.elements.svg.FeBlend→xilem_core.docs.Statexilem_web.elements.svg.FeColorMatrix→xilem_core.docs.Statexilem_web.elements.svg.FeComponentTransfer→xilem_core.docs.Statexilem_web.elements.svg.FeComposite→xilem_core.docs.Statexilem_web.elements.svg.FeConvolveMatrix→xilem_core.docs.Statexilem_web.elements.svg.FeDiffuseLighting→xilem_core.docs.Statexilem_web.elements.svg.FeDisplacementMap→xilem_core.docs.Statexilem_web.elements.svg.FeDistantLight→xilem_core.docs.Statexilem_web.elements.svg.FeDropShadow→xilem_core.docs.Statexilem_web.elements.svg.FeFlood→xilem_core.docs.Statexilem_web.elements.svg.FeFuncA→xilem_core.docs.Statexilem_web.elements.svg.FeFuncB→xilem_core.docs.Statexilem_web.elements.svg.FeFuncG→xilem_core.docs.Statexilem_web.elements.svg.FeFuncR→xilem_core.docs.Statexilem_web.elements.svg.FeGaussianBlur→xilem_core.docs.Statexilem_web.elements.svg.FeImage→xilem_core.docs.State
- Direction
- xilem_web.elements.svg uses xilem_core.docs, so a change to xilem_core.docs can break xilem_web.elements.svg, while a change to xilem_web.elements.svg can't break xilem_core.docs.
- Position
- Below the diagonal: xilem_web.elements.svg uses a module listed above it, which is the healthy direction.
21→19 xilem_web.elements.svg uses xilem_masonry.view_ctx✕
- Connections
- 63 pairs of types, where a type in xilem_web.elements.svg uses a type in xilem_masonry.view_ctx. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
xilem_web.elements.svg.A→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.svg.Animate→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.svg.AnimateMotion→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.svg.AnimateTransform→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.svg.Circle→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.svg.ClipPath→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.svg.Defs→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.svg.Desc→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.svg.Ellipse→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.svg.FeBlend→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.svg.FeColorMatrix→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.svg.FeComponentTransfer→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.svg.FeComposite→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.svg.FeConvolveMatrix→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.svg.FeDiffuseLighting→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.svg.FeDisplacementMap→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.svg.FeDistantLight→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.svg.FeDropShadow→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.svg.FeFlood→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.svg.FeFuncA→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.svg.FeFuncB→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.svg.FeFuncG→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.svg.FeFuncR→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.svg.FeGaussianBlur→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.svg.FeImage→xilem_masonry.view_ctx.ViewCtx
- Direction
- xilem_web.elements.svg uses xilem_masonry.view_ctx, so a change to xilem_masonry.view_ctx can break xilem_web.elements.svg, while a change to xilem_web.elements.svg can't break xilem_masonry.view_ctx.
- Position
- Below the diagonal: xilem_web.elements.svg uses a module listed above it, which is the healthy direction.
21→20 xilem_web.elements.svg uses xilem_web.pod✕
- Connections
- 1 pair of types, where a type in xilem_web.elements.svg uses a type in xilem_web.pod.
- The types involved
xilem_web.elements.svg.Text→xilem_web.pod.PodFlags
- Direction
- xilem_web.elements.svg uses xilem_web.pod, so a change to xilem_web.pod can break xilem_web.elements.svg, while a change to xilem_web.elements.svg can't break xilem_web.pod.
- Position
- Below the diagonal: xilem_web.elements.svg uses a module listed above it, which is the healthy direction.
21→27 xilem_web.elements.svg uses xilem_web.elements.html part of a loop✕
- Connections
- 1 pair of types, where a type in xilem_web.elements.svg uses a type in xilem_web.elements.html.
- The types involved
xilem_web.elements.svg.svg$module→xilem_web.elements.html.A
- Direction
- xilem_web.elements.svg uses xilem_web.elements.html, so a change to xilem_web.elements.html can break xilem_web.elements.svg, while a change to xilem_web.elements.svg can't break xilem_web.elements.html.
- 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.
22→20 xilem_web.interfaces uses xilem_web.pod✕
- Connections
- 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.
- The types involved
xilem_web.interfaces.Element→xilem_web.pod.PodFlagsxilem_web.interfaces.HtmlAnchorElement→xilem_web.pod.PodFlagsxilem_web.interfaces.HtmlAreaElement→xilem_web.pod.PodFlagsxilem_web.interfaces.HtmlAudioElement→xilem_web.pod.PodFlagsxilem_web.interfaces.HtmlBrElement→xilem_web.pod.PodFlagsxilem_web.interfaces.HtmlButtonElement→xilem_web.pod.PodFlagsxilem_web.interfaces.HtmlCanvasElement→xilem_web.pod.PodFlagsxilem_web.interfaces.HtmlDListElement→xilem_web.pod.PodFlagsxilem_web.interfaces.HtmlDataElement→xilem_web.pod.PodFlagsxilem_web.interfaces.HtmlDataListElement→xilem_web.pod.PodFlagsxilem_web.interfaces.HtmlDetailsElement→xilem_web.pod.PodFlagsxilem_web.interfaces.HtmlDialogElement→xilem_web.pod.PodFlagsxilem_web.interfaces.HtmlDivElement→xilem_web.pod.PodFlagsxilem_web.interfaces.HtmlElement→xilem_web.pod.PodFlagsxilem_web.interfaces.HtmlEmbedElement→xilem_web.pod.PodFlagsxilem_web.interfaces.HtmlFieldSetElement→xilem_web.pod.PodFlagsxilem_web.interfaces.HtmlFormElement→xilem_web.pod.PodFlagsxilem_web.interfaces.HtmlHeadingElement→xilem_web.pod.PodFlagsxilem_web.interfaces.HtmlHrElement→xilem_web.pod.PodFlagsxilem_web.interfaces.HtmlIFrameElement→xilem_web.pod.PodFlagsxilem_web.interfaces.HtmlImageElement→xilem_web.pod.PodFlagsxilem_web.interfaces.HtmlInputElement→xilem_web.pod.PodFlagsxilem_web.interfaces.HtmlLabelElement→xilem_web.pod.PodFlagsxilem_web.interfaces.HtmlLegendElement→xilem_web.pod.PodFlagsxilem_web.interfaces.HtmlLiElement→xilem_web.pod.PodFlags
- Direction
- 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.
23→1 masonry.widgets.portal uses masonry_core.core.events✕
- Connections
- 3 pairs of types, where a type in masonry.widgets.portal uses a type in masonry_core.core.events.
- The types involved
masonry.widgets.portal.Portal→masonry_core.core.events.AccessEventmasonry.widgets.portal.Portal→masonry_core.core.events.TextEventmasonry.widgets.portal.Portal→masonry_core.core.events.Update
- Direction
- masonry.widgets.portal uses masonry_core.core.events, so a change to masonry_core.core.events can break masonry.widgets.portal, while a change to masonry.widgets.portal can't break masonry_core.core.events.
- Position
- Below the diagonal: masonry.widgets.portal uses a module listed above it, which is the healthy direction.
23→2 masonry.widgets.portal uses masonry_core.layout.length✕
- Connections
- 1 pair of types, where a type in masonry.widgets.portal uses a type in masonry_core.layout.length.
- The types involved
masonry.widgets.portal.Portal→masonry_core.layout.length.Length
- Direction
- masonry.widgets.portal uses masonry_core.layout.length, so a change to masonry_core.layout.length can break masonry.widgets.portal, while a change to masonry.widgets.portal can't break masonry_core.layout.length.
- Position
- Below the diagonal: masonry.widgets.portal uses a module listed above it, which is the healthy direction.
23→4 masonry.widgets.portal uses masonry_core.core.properties_mut✕
- Connections
- 1 pair of types, where a type in masonry.widgets.portal uses a type in masonry_core.core.properties_mut.
- The types involved
masonry.widgets.portal.Portal→masonry_core.core.properties_mut.PropertiesMut
- Direction
- masonry.widgets.portal uses masonry_core.core.properties_mut, so a change to masonry_core.core.properties_mut can break masonry.widgets.portal, while a change to masonry.widgets.portal can't break masonry_core.core.properties_mut.
- Position
- Below the diagonal: masonry.widgets.portal uses a module listed above it, which is the healthy direction.
23→5 masonry.widgets.portal uses masonry_core.core.properties_ref✕
- Connections
- 1 pair of types, where a type in masonry.widgets.portal uses a type in masonry_core.core.properties_ref.
- The types involved
masonry.widgets.portal.Portal→masonry_core.core.properties_ref.PropertiesRef
- Direction
- masonry.widgets.portal uses masonry_core.core.properties_ref, so a change to masonry_core.core.properties_ref can break masonry.widgets.portal, while a change to masonry.widgets.portal can't break masonry_core.core.properties_ref.
- Position
- Below the diagonal: masonry.widgets.portal uses a module listed above it, which is the healthy direction.
23→6 masonry.widgets.portal uses masonry_core.core.widget_mut✕
- Connections
- 1 pair of types, where a type in masonry.widgets.portal uses a type in masonry_core.core.widget_mut.
- The types involved
masonry.widgets.portal.Portal→masonry_core.core.widget_mut.WidgetMut
- Direction
- masonry.widgets.portal uses masonry_core.core.widget_mut, so a change to masonry_core.core.widget_mut can break masonry.widgets.portal, while a change to masonry.widgets.portal can't break masonry_core.core.widget_mut.
- Position
- Below the diagonal: masonry.widgets.portal uses a module listed above it, which is the healthy direction.
23→7 masonry.widgets.portal uses masonry_core.core.widget_pod✕
- Connections
- 2 pairs of types, where a type in masonry.widgets.portal uses a type in masonry_core.core.widget_pod.
- The types involved
masonry.widgets.portal.Portal→masonry_core.core.widget_pod.NewWidgetmasonry.widgets.portal.Portal→masonry_core.core.widget_pod.WidgetPod
- Direction
- masonry.widgets.portal uses masonry_core.core.widget_pod, so a change to masonry_core.core.widget_pod can break masonry.widgets.portal, while a change to masonry.widgets.portal can't break masonry_core.core.widget_pod.
- Position
- Below the diagonal: masonry.widgets.portal uses a module listed above it, which is the healthy direction.
23→8 masonry.widgets.portal uses masonry_core.layout.len_req✕
- Connections
- 1 pair of types, where a type in masonry.widgets.portal uses a type in masonry_core.layout.len_req.
- The types involved
masonry.widgets.portal.Portal→masonry_core.layout.len_req.LenReq
- Direction
- masonry.widgets.portal uses masonry_core.layout.len_req, so a change to masonry_core.layout.len_req can break masonry.widgets.portal, while a change to masonry.widgets.portal can't break masonry_core.layout.len_req.
- Position
- Below the diagonal: masonry.widgets.portal uses a module listed above it, which is the healthy direction.
23→10 masonry.widgets.portal uses masonry_core.core.widget✕
- Connections
- 2 pairs of types, where a type in masonry.widgets.portal uses a type in masonry_core.core.widget.
- The types involved
masonry.widgets.portal.Portal→masonry_core.core.widget.Widgetmasonry.widgets.portal.Portal→masonry_core.core.widget.WidgetId
- Direction
- masonry.widgets.portal uses masonry_core.core.widget, so a change to masonry_core.core.widget can break masonry.widgets.portal, while a change to masonry.widgets.portal can't break masonry_core.core.widget.
- Position
- Below the diagonal: masonry.widgets.portal uses a module listed above it, which is the healthy direction.
23→13 masonry.widgets.portal uses masonry_core.core.property✕
- Connections
- 1 pair of types, where a type in masonry.widgets.portal uses a type in masonry_core.core.property.
- The types involved
masonry.widgets.portal.Portal→masonry_core.core.property.UsesProperty
- Direction
- masonry.widgets.portal uses masonry_core.core.property, so a change to masonry_core.core.property can break masonry.widgets.portal, while a change to masonry.widgets.portal can't break masonry_core.core.property.
- Position
- Below the diagonal: masonry.widgets.portal uses a module listed above it, which is the healthy direction.
23→21 masonry.widgets.portal uses xilem_web.elements.svg✕
- Connections
- 1 pair of types, where a type in masonry.widgets.portal uses a type in xilem_web.elements.svg.
- The types involved
masonry.widgets.portal.Portal→xilem_web.elements.svg.Rect
- Direction
- masonry.widgets.portal uses xilem_web.elements.svg, so a change to xilem_web.elements.svg can break masonry.widgets.portal, while a change to masonry.widgets.portal can't break xilem_web.elements.svg.
- Position
- Below the diagonal: masonry.widgets.portal uses a module listed above it, which is the healthy direction.
23→27 masonry.widgets.portal uses xilem_web.elements.html part of a loop✕
- Connections
- 1 pair of types, where a type in masonry.widgets.portal uses a type in xilem_web.elements.html.
- The types involved
masonry.widgets.portal.Portal→xilem_web.elements.html.Span
- Direction
- masonry.widgets.portal uses xilem_web.elements.html, so a change to xilem_web.elements.html can break masonry.widgets.portal, while a change to masonry.widgets.portal can't break xilem_web.elements.html.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→32 masonry.widgets.portal uses masonry_core.core.contexts part of a loop✕
- Connections
- 8 pairs of types, where a type in masonry.widgets.portal uses a type in masonry_core.core.contexts.
- The types involved
masonry.widgets.portal.Portal→masonry_core.core.contexts.AccessCtxmasonry.widgets.portal.Portal→masonry_core.core.contexts.ComposeCtxmasonry.widgets.portal.Portal→masonry_core.core.contexts.EventCtxmasonry.widgets.portal.Portal→masonry_core.core.contexts.LayoutCtxmasonry.widgets.portal.Portal→masonry_core.core.contexts.MeasureCtxmasonry.widgets.portal.Portal→masonry_core.core.contexts.PaintCtxmasonry.widgets.portal.Portal→masonry_core.core.contexts.RegisterCtxmasonry.widgets.portal.Portal→masonry_core.core.contexts.UpdateCtx
- Direction
- masonry.widgets.portal uses masonry_core.core.contexts, so a change to masonry_core.core.contexts can break masonry.widgets.portal, while a change to masonry.widgets.portal 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.
24→22 xilem_core.element_splice uses xilem_web.interfaces✕
- Connections
- 1 pair of types, where a type in xilem_core.element_splice uses a type in xilem_web.interfaces.
- The types involved
xilem_core.element_splice.ElementSplice→xilem_web.interfaces.Element
- Direction
- xilem_core.element_splice uses xilem_web.interfaces, so a change to xilem_web.interfaces can break xilem_core.element_splice, while a change to xilem_core.element_splice can't break xilem_web.interfaces.
- Position
- Below the diagonal: xilem_core.element_splice uses a module listed above it, which is the healthy direction.
25→3 xilem_masonry.view.flex uses xilem_core.message✕
- Connections
- 4 pairs of types, where a type in xilem_masonry.view.flex uses a type in xilem_core.message.
- The types involved
xilem_masonry.view.flex.AnyFlexChild→xilem_core.message.MessageResultxilem_masonry.view.flex.Flex→xilem_core.message.MessageResultxilem_masonry.view.flex.FlexItem→xilem_core.message.MessageResultxilem_masonry.view.flex.FlexSpacer→xilem_core.message.MessageResult
- 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.
25→6 xilem_masonry.view.flex uses masonry_core.core.widget_mut✕
- Connections
- 2 pairs of types, where a type in xilem_masonry.view.flex uses a type in masonry_core.core.widget_mut.
- The types involved
xilem_masonry.view.flex.FlexElementMut→masonry_core.core.widget_mut.WidgetMutxilem_masonry.view.flex.FlexSplice→masonry_core.core.widget_mut.WidgetMut
- 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.
25→9 xilem_masonry.view.flex uses xilem_core.message_context✕
- Connections
- 4 pairs of types, where a type in xilem_masonry.view.flex uses a type in xilem_core.message_context.
- The types involved
xilem_masonry.view.flex.AnyFlexChild→xilem_core.message_context.MessageCtxxilem_masonry.view.flex.Flex→xilem_core.message_context.MessageCtxxilem_masonry.view.flex.FlexItem→xilem_core.message_context.MessageCtxxilem_masonry.view.flex.FlexSpacer→xilem_core.message_context.MessageCtx
- 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.
25→11 xilem_masonry.view.flex uses xilem_core.view✕
- Connections
- 8 pairs of types, where a type in xilem_masonry.view.flex uses a type in xilem_core.view.
- The types involved
xilem_masonry.view.flex.AnyFlexChild→xilem_core.view.Viewxilem_masonry.view.flex.AnyFlexChild→xilem_core.view.ViewMarkerxilem_masonry.view.flex.Flex→xilem_core.view.Viewxilem_masonry.view.flex.Flex→xilem_core.view.ViewMarkerxilem_masonry.view.flex.FlexItem→xilem_core.view.Viewxilem_masonry.view.flex.FlexItem→xilem_core.view.ViewMarkerxilem_masonry.view.flex.FlexSpacer→xilem_core.view.Viewxilem_masonry.view.flex.FlexSpacer→xilem_core.view.ViewMarker
- 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.
25→14 xilem_masonry.view.flex uses masonry.widgets.flex✕
- Connections
- 2 pairs of types, where a type in xilem_masonry.view.flex uses a type in masonry.widgets.flex.
- The types involved
xilem_masonry.view.flex.FlexItem→masonry.widgets.flex.FlexParamsxilem_masonry.view.flex.flex$module→masonry.widgets.flex.Flex
- 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.
25→18 xilem_masonry.view.flex uses xilem_core.docs✕
- Connections
- 4 pairs of types, where a type in xilem_masonry.view.flex uses a type in xilem_core.docs.
- The types involved
xilem_masonry.view.flex.AnyFlexChild→xilem_core.docs.Statexilem_masonry.view.flex.Flex→xilem_core.docs.Statexilem_masonry.view.flex.FlexItem→xilem_core.docs.Statexilem_masonry.view.flex.FlexSpacer→xilem_core.docs.State
- 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.
25→19 xilem_masonry.view.flex uses xilem_masonry.view_ctx✕
- Connections
- 5 pairs of types, where a type in xilem_masonry.view.flex uses a type in xilem_masonry.view_ctx.
- The types involved
xilem_masonry.view.flex.AnyFlexChild→xilem_masonry.view_ctx.ViewCtxxilem_masonry.view.flex.Flex→xilem_masonry.view_ctx.ViewCtxxilem_masonry.view.flex.FlexElement→xilem_masonry.view_ctx.ViewCtxxilem_masonry.view.flex.FlexItem→xilem_masonry.view_ctx.ViewCtxxilem_masonry.view.flex.FlexSpacer→xilem_masonry.view_ctx.ViewCtx
- 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.
25→24 xilem_masonry.view.flex uses xilem_core.element_splice✕
- Connections
- 2 pairs of types, where a type in xilem_masonry.view.flex uses a type in xilem_core.element_splice.
- The types involved
xilem_masonry.view.flex.FlexSplice→xilem_core.element_splice.AppendVecxilem_masonry.view.flex.FlexSplice→xilem_core.element_splice.ElementSplice
- 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.
26→3 xilem_masonry.view.zstack uses xilem_core.message✕
- Connections
- 2 pairs of types, where a type in xilem_masonry.view.zstack uses a type in xilem_core.message.
- The types involved
xilem_masonry.view.zstack.ZStack→xilem_core.message.MessageResultxilem_masonry.view.zstack.ZStackItem→xilem_core.message.MessageResult
- 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.
26→6 xilem_masonry.view.zstack uses masonry_core.core.widget_mut✕
- Connections
- 2 pairs of types, where a type in xilem_masonry.view.zstack uses a type in masonry_core.core.widget_mut.
- The types involved
xilem_masonry.view.zstack.ZStackElementMut→masonry_core.core.widget_mut.WidgetMutxilem_masonry.view.zstack.ZStackSplice→masonry_core.core.widget_mut.WidgetMut
- 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.
26→9 xilem_masonry.view.zstack uses xilem_core.message_context✕
- Connections
- 2 pairs of types, where a type in xilem_masonry.view.zstack uses a type in xilem_core.message_context.
- The types involved
xilem_masonry.view.zstack.ZStack→xilem_core.message_context.MessageCtxxilem_masonry.view.zstack.ZStackItem→xilem_core.message_context.MessageCtx
- 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.
26→11 xilem_masonry.view.zstack uses xilem_core.view✕
- Connections
- 4 pairs of types, where a type in xilem_masonry.view.zstack uses a type in xilem_core.view.
- The types involved
xilem_masonry.view.zstack.ZStack→xilem_core.view.Viewxilem_masonry.view.zstack.ZStack→xilem_core.view.ViewMarkerxilem_masonry.view.zstack.ZStackItem→xilem_core.view.Viewxilem_masonry.view.zstack.ZStackItem→xilem_core.view.ViewMarker
- 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.
26→18 xilem_masonry.view.zstack uses xilem_core.docs✕
- Connections
- 2 pairs of types, where a type in xilem_masonry.view.zstack uses a type in xilem_core.docs.
- The types involved
xilem_masonry.view.zstack.ZStack→xilem_core.docs.Statexilem_masonry.view.zstack.ZStackItem→xilem_core.docs.State
- 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.
26→19 xilem_masonry.view.zstack uses xilem_masonry.view_ctx✕
- Connections
- 3 pairs of types, where a type in xilem_masonry.view.zstack uses a type in xilem_masonry.view_ctx.
- The types involved
xilem_masonry.view.zstack.ZStack→xilem_masonry.view_ctx.ViewCtxxilem_masonry.view.zstack.ZStackElement→xilem_masonry.view_ctx.ViewCtxxilem_masonry.view.zstack.ZStackItem→xilem_masonry.view_ctx.ViewCtx
- 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.
26→24 xilem_masonry.view.zstack uses xilem_core.element_splice✕
- Connections
- 2 pairs of types, where a type in xilem_masonry.view.zstack uses a type in xilem_core.element_splice.
- The types involved
xilem_masonry.view.zstack.ZStackSplice→xilem_core.element_splice.AppendVecxilem_masonry.view.zstack.ZStackSplice→xilem_core.element_splice.ElementSplice
- 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.
27→3 xilem_web.elements.html uses xilem_core.message✕
- Connections
- 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.
- The types involved
xilem_web.elements.html.A→xilem_core.message.MessageResultxilem_web.elements.html.Abbr→xilem_core.message.MessageResultxilem_web.elements.html.Address→xilem_core.message.MessageResultxilem_web.elements.html.Area→xilem_core.message.MessageResultxilem_web.elements.html.Article→xilem_core.message.MessageResultxilem_web.elements.html.Aside→xilem_core.message.MessageResultxilem_web.elements.html.Audio→xilem_core.message.MessageResultxilem_web.elements.html.B→xilem_core.message.MessageResultxilem_web.elements.html.Bdi→xilem_core.message.MessageResultxilem_web.elements.html.Bdo→xilem_core.message.MessageResultxilem_web.elements.html.Blockquote→xilem_core.message.MessageResultxilem_web.elements.html.Br→xilem_core.message.MessageResultxilem_web.elements.html.Button→xilem_core.message.MessageResultxilem_web.elements.html.Canvas→xilem_core.message.MessageResultxilem_web.elements.html.Caption→xilem_core.message.MessageResultxilem_web.elements.html.Cite→xilem_core.message.MessageResultxilem_web.elements.html.Code→xilem_core.message.MessageResultxilem_web.elements.html.Col→xilem_core.message.MessageResultxilem_web.elements.html.Colgroup→xilem_core.message.MessageResultxilem_web.elements.html.Data→xilem_core.message.MessageResultxilem_web.elements.html.Datalist→xilem_core.message.MessageResultxilem_web.elements.html.Dd→xilem_core.message.MessageResultxilem_web.elements.html.Del→xilem_core.message.MessageResultxilem_web.elements.html.Details→xilem_core.message.MessageResultxilem_web.elements.html.Dfn→xilem_core.message.MessageResult
- Direction
- 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.
27→9 xilem_web.elements.html uses xilem_core.message_context✕
- Connections
- 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.
- The types involved
xilem_web.elements.html.A→xilem_core.message_context.MessageCtxxilem_web.elements.html.Abbr→xilem_core.message_context.MessageCtxxilem_web.elements.html.Address→xilem_core.message_context.MessageCtxxilem_web.elements.html.Area→xilem_core.message_context.MessageCtxxilem_web.elements.html.Article→xilem_core.message_context.MessageCtxxilem_web.elements.html.Aside→xilem_core.message_context.MessageCtxxilem_web.elements.html.Audio→xilem_core.message_context.MessageCtxxilem_web.elements.html.B→xilem_core.message_context.MessageCtxxilem_web.elements.html.Bdi→xilem_core.message_context.MessageCtxxilem_web.elements.html.Bdo→xilem_core.message_context.MessageCtxxilem_web.elements.html.Blockquote→xilem_core.message_context.MessageCtxxilem_web.elements.html.Br→xilem_core.message_context.MessageCtxxilem_web.elements.html.Button→xilem_core.message_context.MessageCtxxilem_web.elements.html.Canvas→xilem_core.message_context.MessageCtxxilem_web.elements.html.Caption→xilem_core.message_context.MessageCtxxilem_web.elements.html.Cite→xilem_core.message_context.MessageCtxxilem_web.elements.html.Code→xilem_core.message_context.MessageCtxxilem_web.elements.html.Col→xilem_core.message_context.MessageCtxxilem_web.elements.html.Colgroup→xilem_core.message_context.MessageCtxxilem_web.elements.html.Data→xilem_core.message_context.MessageCtxxilem_web.elements.html.Datalist→xilem_core.message_context.MessageCtxxilem_web.elements.html.Dd→xilem_core.message_context.MessageCtxxilem_web.elements.html.Del→xilem_core.message_context.MessageCtxxilem_web.elements.html.Details→xilem_core.message_context.MessageCtxxilem_web.elements.html.Dfn→xilem_core.message_context.MessageCtx
- Direction
- 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.
27→11 xilem_web.elements.html uses xilem_core.view✕
- Connections
- 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.
- The types involved
xilem_web.elements.html.A→xilem_core.view.Viewxilem_web.elements.html.A→xilem_core.view.ViewMarkerxilem_web.elements.html.Abbr→xilem_core.view.Viewxilem_web.elements.html.Abbr→xilem_core.view.ViewMarkerxilem_web.elements.html.Address→xilem_core.view.Viewxilem_web.elements.html.Address→xilem_core.view.ViewMarkerxilem_web.elements.html.Area→xilem_core.view.Viewxilem_web.elements.html.Area→xilem_core.view.ViewMarkerxilem_web.elements.html.Article→xilem_core.view.Viewxilem_web.elements.html.Article→xilem_core.view.ViewMarkerxilem_web.elements.html.Aside→xilem_core.view.Viewxilem_web.elements.html.Aside→xilem_core.view.ViewMarkerxilem_web.elements.html.Audio→xilem_core.view.Viewxilem_web.elements.html.Audio→xilem_core.view.ViewMarkerxilem_web.elements.html.B→xilem_core.view.Viewxilem_web.elements.html.B→xilem_core.view.ViewMarkerxilem_web.elements.html.Bdi→xilem_core.view.Viewxilem_web.elements.html.Bdi→xilem_core.view.ViewMarkerxilem_web.elements.html.Bdo→xilem_core.view.Viewxilem_web.elements.html.Bdo→xilem_core.view.ViewMarkerxilem_web.elements.html.Blockquote→xilem_core.view.Viewxilem_web.elements.html.Blockquote→xilem_core.view.ViewMarkerxilem_web.elements.html.Br→xilem_core.view.Viewxilem_web.elements.html.Br→xilem_core.view.ViewMarkerxilem_web.elements.html.Button→xilem_core.view.View
- Direction
- 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.
27→12 xilem_web.elements.html uses masonry.widgets.button✕
- Connections
- 1 pair of types, where a type in xilem_web.elements.html uses a type in masonry.widgets.button.
- The types involved
xilem_web.elements.html.html$module→masonry.widgets.button.Button
- Direction
- xilem_web.elements.html uses masonry.widgets.button, so a change to masonry.widgets.button can break xilem_web.elements.html, while a change to xilem_web.elements.html can't break masonry.widgets.button.
- Position
- Below the diagonal: xilem_web.elements.html uses a module listed above it, which is the healthy direction.
27→16 xilem_web.elements.html uses masonry.widgets.label✕
- Connections
- 1 pair of types, where a type in xilem_web.elements.html uses a type in masonry.widgets.label.
- The types involved
xilem_web.elements.html.html$module→masonry.widgets.label.Label
- Direction
- xilem_web.elements.html uses masonry.widgets.label, so a change to masonry.widgets.label can break xilem_web.elements.html, while a change to xilem_web.elements.html can't break masonry.widgets.label.
- Position
- Below the diagonal: xilem_web.elements.html uses a module listed above it, which is the healthy direction.
27→17 xilem_web.elements.html uses xilem_core.environment✕
- Connections
- 1 pair of types, where a type in xilem_web.elements.html uses a type in xilem_core.environment.
- The types involved
xilem_web.elements.html.html$module→xilem_core.environment.Slot
- Direction
- xilem_web.elements.html uses xilem_core.environment, so a change to xilem_core.environment can break xilem_web.elements.html, while a change to xilem_web.elements.html can't break xilem_core.environment.
- Position
- Below the diagonal: xilem_web.elements.html uses a module listed above it, which is the healthy direction.
27→18 xilem_web.elements.html uses xilem_core.docs✕
- Connections
- 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.
- The types involved
xilem_web.elements.html.A→xilem_core.docs.Statexilem_web.elements.html.Abbr→xilem_core.docs.Statexilem_web.elements.html.Address→xilem_core.docs.Statexilem_web.elements.html.Area→xilem_core.docs.Statexilem_web.elements.html.Article→xilem_core.docs.Statexilem_web.elements.html.Aside→xilem_core.docs.Statexilem_web.elements.html.Audio→xilem_core.docs.Statexilem_web.elements.html.B→xilem_core.docs.Statexilem_web.elements.html.Bdi→xilem_core.docs.Statexilem_web.elements.html.Bdo→xilem_core.docs.Statexilem_web.elements.html.Blockquote→xilem_core.docs.Statexilem_web.elements.html.Br→xilem_core.docs.Statexilem_web.elements.html.Button→xilem_core.docs.Statexilem_web.elements.html.Canvas→xilem_core.docs.Statexilem_web.elements.html.Caption→xilem_core.docs.Statexilem_web.elements.html.Cite→xilem_core.docs.Statexilem_web.elements.html.Code→xilem_core.docs.Statexilem_web.elements.html.Col→xilem_core.docs.Statexilem_web.elements.html.Colgroup→xilem_core.docs.Statexilem_web.elements.html.Data→xilem_core.docs.Statexilem_web.elements.html.Datalist→xilem_core.docs.Statexilem_web.elements.html.Dd→xilem_core.docs.Statexilem_web.elements.html.Del→xilem_core.docs.Statexilem_web.elements.html.Details→xilem_core.docs.Statexilem_web.elements.html.Dfn→xilem_core.docs.State
- Direction
- 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.
27→19 xilem_web.elements.html uses xilem_masonry.view_ctx✕
- Connections
- 105 pairs of types, where a type in xilem_web.elements.html uses a type in xilem_masonry.view_ctx. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
xilem_web.elements.html.A→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.html.Abbr→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.html.Address→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.html.Area→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.html.Article→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.html.Aside→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.html.Audio→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.html.B→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.html.Bdi→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.html.Bdo→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.html.Blockquote→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.html.Br→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.html.Button→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.html.Canvas→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.html.Caption→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.html.Cite→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.html.Code→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.html.Col→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.html.Colgroup→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.html.Data→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.html.Datalist→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.html.Dd→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.html.Del→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.html.Details→xilem_masonry.view_ctx.ViewCtxxilem_web.elements.html.Dfn→xilem_masonry.view_ctx.ViewCtx
- Direction
- xilem_web.elements.html uses xilem_masonry.view_ctx, so a change to xilem_masonry.view_ctx can break xilem_web.elements.html, while a change to xilem_web.elements.html can't break xilem_masonry.view_ctx.
- Position
- Below the diagonal: xilem_web.elements.html uses a module listed above it, which is the healthy direction.
27→23 xilem_web.elements.html uses masonry.widgets.portal✕
- Connections
- 1 pair of types, where a type in xilem_web.elements.html uses a type in masonry.widgets.portal.
- The types involved
xilem_web.elements.html.html$module→masonry.widgets.portal.Portal
- Direction
- xilem_web.elements.html uses masonry.widgets.portal, so a change to masonry.widgets.portal can break xilem_web.elements.html, while a change to xilem_web.elements.html can't break masonry.widgets.portal.
- Position
- Below the diagonal: xilem_web.elements.html uses a module listed above it, which is the healthy direction.
27→24 xilem_web.elements.html uses xilem_core.element_splice✕
- Connections
- 1 pair of types, where a type in xilem_web.elements.html uses a type in xilem_core.element_splice.
- The types involved
xilem_web.elements.html.S→xilem_core.element_splice.AppendVec
- 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.
28→27 masonry_core.core.property_stack uses xilem_web.elements.html✕
- Connections
- 1 pair of types, where a type in masonry_core.core.property_stack uses a type in xilem_web.elements.html.
- The types involved
masonry_core.core.property_stack.PropertyStack→xilem_web.elements.html.P
- Direction
- masonry_core.core.property_stack uses xilem_web.elements.html, so a change to xilem_web.elements.html can break masonry_core.core.property_stack, while a change to masonry_core.core.property_stack can't break xilem_web.elements.html.
- Position
- Below the diagonal: masonry_core.core.property_stack uses a module listed above it, which is the healthy direction.
29→27 masonry_core.core.default_properties uses xilem_web.elements.html✕
- Connections
- 1 pair of types, where a type in masonry_core.core.default_properties uses a type in xilem_web.elements.html.
- The types involved
masonry_core.core.default_properties.DefaultProperties→xilem_web.elements.html.P
- Direction
- masonry_core.core.default_properties uses xilem_web.elements.html, so a change to xilem_web.elements.html can break masonry_core.core.default_properties, while a change to masonry_core.core.default_properties can't break xilem_web.elements.html.
- Position
- Below the diagonal: masonry_core.core.default_properties uses a module listed above it, which is the healthy direction.
29→28 masonry_core.core.default_properties uses masonry_core.core.property_stack✕
- Connections
- 1 pair of types, where a type in masonry_core.core.default_properties uses a type in masonry_core.core.property_stack.
- The types involved
masonry_core.core.default_properties.DefaultProperties→masonry_core.core.property_stack.PropertyStack
- Direction
- 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.
30→7 masonry_core.core.widget_state uses masonry_core.core.widget_pod✕
- Connections
- 1 pair of types, where a type in masonry_core.core.widget_state uses a type in masonry_core.core.widget_pod.
- The types involved
masonry_core.core.widget_state.WidgetState→masonry_core.core.widget_pod.WidgetOptions
- 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.
30→10 masonry_core.core.widget_state uses masonry_core.core.widget✕
- Connections
- 1 pair of types, where a type in masonry_core.core.widget_state uses a type in masonry_core.core.widget.
- The types involved
masonry_core.core.widget_state.WidgetState→masonry_core.core.widget.WidgetId
- 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.
30→21 masonry_core.core.widget_state uses xilem_web.elements.svg✕
- Connections
- 1 pair of types, where a type in masonry_core.core.widget_state uses a type in xilem_web.elements.svg.
- The types involved
masonry_core.core.widget_state.WidgetState→xilem_web.elements.svg.Rect
- Direction
- masonry_core.core.widget_state uses xilem_web.elements.svg, so a change to xilem_web.elements.svg can break masonry_core.core.widget_state, while a change to masonry_core.core.widget_state can't break xilem_web.elements.svg.
- Position
- Below the diagonal: masonry_core.core.widget_state uses a module listed above it, which is the healthy direction.
30→27 masonry_core.core.widget_state uses xilem_web.elements.html✕
- Connections
- 1 pair of types, where a type in masonry_core.core.widget_state uses a type in xilem_web.elements.html.
- The types involved
masonry_core.core.widget_state.WidgetState→xilem_web.elements.html.Span
- Direction
- masonry_core.core.widget_state uses xilem_web.elements.html, so a change to xilem_web.elements.html can break masonry_core.core.widget_state, while a change to masonry_core.core.widget_state can't break xilem_web.elements.html.
- Position
- Below the diagonal: masonry_core.core.widget_state uses a module listed above it, which is the healthy direction.
30→28 masonry_core.core.widget_state uses masonry_core.core.property_stack✕
- Connections
- 1 pair of types, where a type in masonry_core.core.widget_state uses a type in masonry_core.core.property_stack.
- The types involved
masonry_core.core.widget_state.WidgetState→masonry_core.core.property_stack.PropertyStackId
- 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.
31→1 masonry_core.app.render_root uses masonry_core.core.events✕
- Connections
- 3 pairs of types, where a type in masonry_core.app.render_root uses a type in masonry_core.core.events.
- The types involved
masonry_core.app.render_root.RenderRoot→masonry_core.core.events.Handledmasonry_core.app.render_root.RenderRoot→masonry_core.core.events.TextEventmasonry_core.app.render_root.RenderRoot→masonry_core.core.events.WindowEvent
- Direction
- 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.
31→7 masonry_core.app.render_root uses masonry_core.core.widget_pod✕
- Connections
- 2 pairs of types, where a type in masonry_core.app.render_root uses a type in masonry_core.core.widget_pod.
- The types involved
masonry_core.app.render_root.RenderRoot→masonry_core.core.widget_pod.NewWidgetmasonry_core.app.render_root.RenderRoot→masonry_core.core.widget_pod.WidgetPod
- 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.
31→10 masonry_core.app.render_root uses masonry_core.core.widget✕
- Connections
- 4 pairs of types, where a type in masonry_core.app.render_root uses a type in masonry_core.core.widget.
- The types involved
masonry_core.app.render_root.InspectorState→masonry_core.core.widget.WidgetIdmasonry_core.app.render_root.MutateCallback→masonry_core.core.widget.WidgetIdmasonry_core.app.render_root.RenderRoot→masonry_core.core.widget.WidgetIdmasonry_core.app.render_root.RenderRootState→masonry_core.core.widget.WidgetId
- 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.
31→21 masonry_core.app.render_root uses xilem_web.elements.svg✕
- Connections
- 2 pairs of types, where a type in masonry_core.app.render_root uses a type in xilem_web.elements.svg.
- The types involved
masonry_core.app.render_root.RenderRootSignal→xilem_web.elements.svg.Rectmasonry_core.app.render_root.RenderRootState→xilem_web.elements.svg.Rect
- Direction
- masonry_core.app.render_root uses xilem_web.elements.svg, so a change to xilem_web.elements.svg can break masonry_core.app.render_root, while a change to masonry_core.app.render_root can't break xilem_web.elements.svg.
- Position
- Below the diagonal: masonry_core.app.render_root uses a module listed above it, which is the healthy direction.
31→28 masonry_core.app.render_root uses masonry_core.core.property_stack✕
- Connections
- 2 pairs of types, where a type in masonry_core.app.render_root uses a type in masonry_core.core.property_stack.
- The types involved
masonry_core.app.render_root.RenderRoot→masonry_core.core.property_stack.PropertyStackmasonry_core.app.render_root.RenderRoot→masonry_core.core.property_stack.PropertyStackId
- 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.
31→29 masonry_core.app.render_root uses masonry_core.core.default_properties✕
- Connections
- 2 pairs of types, where a type in masonry_core.app.render_root uses a type in masonry_core.core.default_properties.
- The types involved
masonry_core.app.render_root.RenderRoot→masonry_core.core.default_properties.DefaultPropertiesmasonry_core.app.render_root.RenderRootOptions→masonry_core.core.default_properties.DefaultProperties
- 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.
31→30 masonry_core.app.render_root uses masonry_core.core.widget_state✕
- Connections
- 1 pair of types, where a type in masonry_core.app.render_root uses a type in masonry_core.core.widget_state.
- The types involved
masonry_core.app.render_root.RenderRoot→masonry_core.core.widget_state.WidgetState
- 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.
32→2 masonry_core.core.contexts uses masonry_core.layout.length✕
- Connections
- 1 pair of types, where a type in masonry_core.core.contexts uses a type in masonry_core.layout.length.
- The types involved
masonry_core.core.contexts.MeasureCtx→masonry_core.layout.length.Length
- 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.
32→4 masonry_core.core.contexts uses masonry_core.core.properties_mut✕
- Connections
- 1 pair of types, where a type in masonry_core.core.contexts uses a type in masonry_core.core.properties_mut.
- The types involved
masonry_core.core.contexts.MutateCtx→masonry_core.core.properties_mut.PropertiesMut
- 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.
32→5 masonry_core.core.contexts uses masonry_core.core.properties_ref✕
- Connections
- 1 pair of types, where a type in masonry_core.core.contexts uses a type in masonry_core.core.properties_ref.
- The types involved
masonry_core.core.contexts.QueryCtx→masonry_core.core.properties_ref.PropertiesRef
- 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.
32→6 masonry_core.core.contexts uses masonry_core.core.widget_mut✕
- Connections
- 1 pair of types, where a type in masonry_core.core.contexts uses a type in masonry_core.core.widget_mut.
- The types involved
masonry_core.core.contexts.MutateCtx→masonry_core.core.widget_mut.WidgetMut
- 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.
32→7 masonry_core.core.contexts uses masonry_core.core.widget_pod✕
- Connections
- 7 pairs of types, where a type in masonry_core.core.contexts uses a type in masonry_core.core.widget_pod.
- The types involved
masonry_core.core.contexts.ActionCtx→masonry_core.core.widget_pod.WidgetPodmasonry_core.core.contexts.ComposeCtx→masonry_core.core.widget_pod.WidgetPodmasonry_core.core.contexts.LayoutCtx→masonry_core.core.widget_pod.WidgetPodmasonry_core.core.contexts.MeasureCtx→masonry_core.core.widget_pod.WidgetPodmasonry_core.core.contexts.MutateCtx→masonry_core.core.widget_pod.WidgetPodmasonry_core.core.contexts.RegisterCtx→masonry_core.core.widget_pod.WidgetPodmasonry_core.core.contexts.UpdateCtx→masonry_core.core.widget_pod.WidgetPod
- 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.
32→10 masonry_core.core.contexts uses masonry_core.core.widget✕
- Connections
- 3 pairs of types, where a type in masonry_core.core.contexts uses a type in masonry_core.core.widget.
- The types involved
masonry_core.core.contexts.EventCtx→masonry_core.core.widget.WidgetIdmasonry_core.core.contexts.QueryCtx→masonry_core.core.widget.WidgetIdmasonry_core.core.contexts.RegisterCtx→masonry_core.core.widget.WidgetId
- 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.
32→21 masonry_core.core.contexts uses xilem_web.elements.svg✕
- Connections
- 1 pair of types, where a type in masonry_core.core.contexts uses a type in xilem_web.elements.svg.
- The types involved
masonry_core.core.contexts.LayoutCtx→xilem_web.elements.svg.Rect
- Direction
- masonry_core.core.contexts uses xilem_web.elements.svg, so a change to xilem_web.elements.svg can break masonry_core.core.contexts, while a change to masonry_core.core.contexts can't break xilem_web.elements.svg.
- Position
- Below the diagonal: masonry_core.core.contexts uses a module listed above it, which is the healthy direction.
32→28 masonry_core.core.contexts uses masonry_core.core.property_stack✕
- Connections
- 1 pair of types, where a type in masonry_core.core.contexts uses a type in masonry_core.core.property_stack.
- The types involved
masonry_core.core.contexts.MutateCtx→masonry_core.core.property_stack.PropertyStackId
- 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.
32→30 masonry_core.core.contexts uses masonry_core.core.widget_state✕
- Connections
- 11 pairs of types, where a type in masonry_core.core.contexts uses a type in masonry_core.core.widget_state.
- The types involved
masonry_core.core.contexts.AccessCtx→masonry_core.core.widget_state.WidgetStatemasonry_core.core.contexts.ActionCtx→masonry_core.core.widget_state.WidgetStatemasonry_core.core.contexts.ComposeCtx→masonry_core.core.widget_state.WidgetStatemasonry_core.core.contexts.EventCtx→masonry_core.core.widget_state.WidgetStatemasonry_core.core.contexts.LayoutCtx→masonry_core.core.widget_state.WidgetStatemasonry_core.core.contexts.MeasureCtx→masonry_core.core.widget_state.WidgetStatemasonry_core.core.contexts.MutateCtx→masonry_core.core.widget_state.WidgetStatemasonry_core.core.contexts.PaintCtx→masonry_core.core.widget_state.WidgetStatemasonry_core.core.contexts.QueryCtx→masonry_core.core.widget_state.WidgetStatemasonry_core.core.contexts.RawCtx→masonry_core.core.widget_state.WidgetStatemasonry_core.core.contexts.UpdateCtx→masonry_core.core.widget_state.WidgetState
- 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.
32→31 masonry_core.core.contexts uses masonry_core.app.render_root✕
- Connections
- 12 pairs of types, where a type in masonry_core.core.contexts uses a type in masonry_core.app.render_root.
- The types involved
masonry_core.core.contexts.AccessCtx→masonry_core.app.render_root.RenderRootStatemasonry_core.core.contexts.ActionCtx→masonry_core.app.render_root.RenderRootStatemasonry_core.core.contexts.ComposeCtx→masonry_core.app.render_root.RenderRootStatemasonry_core.core.contexts.EventCtx→masonry_core.app.render_root.RenderRootStatemasonry_core.core.contexts.LayoutCtx→masonry_core.app.render_root.RenderRootStatemasonry_core.core.contexts.MeasureCtx→masonry_core.app.render_root.RenderRootStatemasonry_core.core.contexts.MutateCtx→masonry_core.app.render_root.RenderRootStatemasonry_core.core.contexts.PaintCtx→masonry_core.app.render_root.RenderRootStatemasonry_core.core.contexts.QueryCtx→masonry_core.app.render_root.RenderRootStatemasonry_core.core.contexts.RawCtx→masonry_core.app.render_root.RenderRootStatemasonry_core.core.contexts.RegisterCtx→masonry_core.app.render_root.RenderRootStatemasonry_core.core.contexts.UpdateCtx→masonry_core.app.render_root.RenderRootState
- 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.
33→7 masonry_winit.event_loop_runner uses masonry_core.core.widget_pod✕
- Connections
- 2 pairs of types, where a type in masonry_winit.event_loop_runner uses a type in masonry_core.core.widget_pod.
- The types involved
masonry_winit.event_loop_runner.NewWindow→masonry_core.core.widget_pod.NewWidgetmasonry_winit.event_loop_runner.Window→masonry_core.core.widget_pod.NewWidget
- Direction
- masonry_winit.event_loop_runner uses masonry_core.core.widget_pod, so a change to masonry_core.core.widget_pod can break masonry_winit.event_loop_runner, while a change to masonry_winit.event_loop_runner can't break masonry_core.core.widget_pod.
- Position
- Below the diagonal: masonry_winit.event_loop_runner uses a module listed above it, which is the healthy direction.
33→29 masonry_winit.event_loop_runner uses masonry_core.core.default_properties✕
- Connections
- 3 pairs of types, where a type in masonry_winit.event_loop_runner uses a type in masonry_core.core.default_properties.
- The types involved
masonry_winit.event_loop_runner.MasonryState→masonry_core.core.default_properties.DefaultPropertiesmasonry_winit.event_loop_runner.Window→masonry_core.core.default_properties.DefaultPropertiesmasonry_winit.event_loop_runner.event_loop_runner$module→masonry_core.core.default_properties.DefaultProperties
- Direction
- masonry_winit.event_loop_runner uses masonry_core.core.default_properties, so a change to masonry_core.core.default_properties can break masonry_winit.event_loop_runner, while a change to masonry_winit.event_loop_runner can't break masonry_core.core.default_properties.
- Position
- Below the diagonal: masonry_winit.event_loop_runner uses a module listed above it, which is the healthy direction.
33→31 masonry_winit.event_loop_runner uses masonry_core.app.render_root✕
- Connections
- 1 pair of types, where a type in masonry_winit.event_loop_runner uses a type in masonry_core.app.render_root.
- The types involved
masonry_winit.event_loop_runner.Window→masonry_core.app.render_root.RenderRoot
- Direction
- masonry_winit.event_loop_runner uses masonry_core.app.render_root, so a change to masonry_core.app.render_root can break masonry_winit.event_loop_runner, while a change to masonry_winit.event_loop_runner can't break masonry_core.app.render_root.
- Position
- Below the diagonal: masonry_winit.event_loop_runner uses a module listed above it, which is the healthy direction.
34→1 masonry.layers.selector_menu uses masonry_core.core.events✕
- Connections
- 3 pairs of types, where a type in masonry.layers.selector_menu uses a type in masonry_core.core.events.
- The types involved
masonry.layers.selector_menu.SelectorMenu→masonry_core.core.events.AccessEventmasonry.layers.selector_menu.SelectorMenu→masonry_core.core.events.TextEventmasonry.layers.selector_menu.SelectorMenu→masonry_core.core.events.Update
- 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.
34→2 masonry.layers.selector_menu uses masonry_core.layout.length✕
- Connections
- 1 pair of types, where a type in masonry.layers.selector_menu uses a type in masonry_core.layout.length.
- The types involved
masonry.layers.selector_menu.SelectorMenu→masonry_core.layout.length.Length
- 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.
34→4 masonry.layers.selector_menu uses masonry_core.core.properties_mut✕
- Connections
- 1 pair of types, where a type in masonry.layers.selector_menu uses a type in masonry_core.core.properties_mut.
- The types involved
masonry.layers.selector_menu.SelectorMenu→masonry_core.core.properties_mut.PropertiesMut
- 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.
34→5 masonry.layers.selector_menu uses masonry_core.core.properties_ref✕
- Connections
- 1 pair of types, where a type in masonry.layers.selector_menu uses a type in masonry_core.core.properties_ref.
- The types involved
masonry.layers.selector_menu.SelectorMenu→masonry_core.core.properties_ref.PropertiesRef
- 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.
34→6 masonry.layers.selector_menu uses masonry_core.core.widget_mut✕
- Connections
- 1 pair of types, where a type in masonry.layers.selector_menu uses a type in masonry_core.core.widget_mut.
- The types involved
masonry.layers.selector_menu.SelectorMenu→masonry_core.core.widget_mut.WidgetMut
- 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.
34→7 masonry.layers.selector_menu uses masonry_core.core.widget_pod✕
- Connections
- 2 pairs of types, where a type in masonry.layers.selector_menu uses a type in masonry_core.core.widget_pod.
- The types involved
masonry.layers.selector_menu.SelectorMenu→masonry_core.core.widget_pod.NewWidgetmasonry.layers.selector_menu.SelectorMenu→masonry_core.core.widget_pod.WidgetPod
- 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.
34→8 masonry.layers.selector_menu uses masonry_core.layout.len_req✕
- Connections
- 1 pair of types, where a type in masonry.layers.selector_menu uses a type in masonry_core.layout.len_req.
- The types involved
masonry.layers.selector_menu.SelectorMenu→masonry_core.layout.len_req.LenReq
- 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.
34→10 masonry.layers.selector_menu uses masonry_core.core.widget✕
- Connections
- 3 pairs of types, where a type in masonry.layers.selector_menu uses a type in masonry_core.core.widget.
- The types involved
masonry.layers.selector_menu.SelectorMenu→masonry_core.core.widget.CollectionWidgetmasonry.layers.selector_menu.SelectorMenu→masonry_core.core.widget.Widgetmasonry.layers.selector_menu.SelectorMenu→masonry_core.core.widget.WidgetId
- 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.
34→13 masonry.layers.selector_menu uses masonry_core.core.property✕
- Connections
- 1 pair of types, where a type in masonry.layers.selector_menu uses a type in masonry_core.core.property.
- The types involved
masonry.layers.selector_menu.SelectorMenu→masonry_core.core.property.UsesProperty
- 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.
34→27 masonry.layers.selector_menu uses xilem_web.elements.html✕
- Connections
- 1 pair of types, where a type in masonry.layers.selector_menu uses a type in xilem_web.elements.html.
- The types involved
masonry.layers.selector_menu.SelectorMenu→xilem_web.elements.html.Span
- Direction
- masonry.layers.selector_menu uses xilem_web.elements.html, so a change to xilem_web.elements.html can break masonry.layers.selector_menu, while a change to masonry.layers.selector_menu can't break xilem_web.elements.html.
- Position
- Below the diagonal: masonry.layers.selector_menu uses a module listed above it, which is the healthy direction.
34→32 masonry.layers.selector_menu uses masonry_core.core.contexts✕
- Connections
- 8 pairs of types, where a type in masonry.layers.selector_menu uses a type in masonry_core.core.contexts.
- The types involved
masonry.layers.selector_menu.SelectorMenu→masonry_core.core.contexts.AccessCtxmasonry.layers.selector_menu.SelectorMenu→masonry_core.core.contexts.ComposeCtxmasonry.layers.selector_menu.SelectorMenu→masonry_core.core.contexts.EventCtxmasonry.layers.selector_menu.SelectorMenu→masonry_core.core.contexts.LayoutCtxmasonry.layers.selector_menu.SelectorMenu→masonry_core.core.contexts.MeasureCtxmasonry.layers.selector_menu.SelectorMenu→masonry_core.core.contexts.PaintCtxmasonry.layers.selector_menu.SelectorMenu→masonry_core.core.contexts.RegisterCtxmasonry.layers.selector_menu.SelectorMenu→masonry_core.core.contexts.UpdateCtx
- 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.
35→1 masonry.widgets.checkbox uses masonry_core.core.events✕
- Connections
- 3 pairs of types, where a type in masonry.widgets.checkbox uses a type in masonry_core.core.events.
- The types involved
masonry.widgets.checkbox.Checkbox→masonry_core.core.events.AccessEventmasonry.widgets.checkbox.Checkbox→masonry_core.core.events.TextEventmasonry.widgets.checkbox.Checkbox→masonry_core.core.events.Update
- Direction
- masonry.widgets.checkbox uses masonry_core.core.events, so a change to masonry_core.core.events can break masonry.widgets.checkbox, while a change to masonry.widgets.checkbox can't break masonry_core.core.events.
- Position
- Below the diagonal: masonry.widgets.checkbox uses a module listed above it, which is the healthy direction.
35→2 masonry.widgets.checkbox uses masonry_core.layout.length✕
- Connections
- 1 pair of types, where a type in masonry.widgets.checkbox uses a type in masonry_core.layout.length.
- The types involved
masonry.widgets.checkbox.Checkbox→masonry_core.layout.length.Length
- Direction
- masonry.widgets.checkbox uses masonry_core.layout.length, so a change to masonry_core.layout.length can break masonry.widgets.checkbox, while a change to masonry.widgets.checkbox can't break masonry_core.layout.length.
- Position
- Below the diagonal: masonry.widgets.checkbox uses a module listed above it, which is the healthy direction.
35→4 masonry.widgets.checkbox uses masonry_core.core.properties_mut✕
- Connections
- 1 pair of types, where a type in masonry.widgets.checkbox uses a type in masonry_core.core.properties_mut.
- The types involved
masonry.widgets.checkbox.Checkbox→masonry_core.core.properties_mut.PropertiesMut
- Direction
- masonry.widgets.checkbox uses masonry_core.core.properties_mut, so a change to masonry_core.core.properties_mut can break masonry.widgets.checkbox, while a change to masonry.widgets.checkbox can't break masonry_core.core.properties_mut.
- Position
- Below the diagonal: masonry.widgets.checkbox uses a module listed above it, which is the healthy direction.
35→5 masonry.widgets.checkbox uses masonry_core.core.properties_ref✕
- Connections
- 1 pair of types, where a type in masonry.widgets.checkbox uses a type in masonry_core.core.properties_ref.
- The types involved
masonry.widgets.checkbox.Checkbox→masonry_core.core.properties_ref.PropertiesRef
- Direction
- masonry.widgets.checkbox uses masonry_core.core.properties_ref, so a change to masonry_core.core.properties_ref can break masonry.widgets.checkbox, while a change to masonry.widgets.checkbox can't break masonry_core.core.properties_ref.
- Position
- Below the diagonal: masonry.widgets.checkbox uses a module listed above it, which is the healthy direction.
35→6 masonry.widgets.checkbox uses masonry_core.core.widget_mut✕
- Connections
- 1 pair of types, where a type in masonry.widgets.checkbox uses a type in masonry_core.core.widget_mut.
- The types involved
masonry.widgets.checkbox.Checkbox→masonry_core.core.widget_mut.WidgetMut
- Direction
- masonry.widgets.checkbox uses masonry_core.core.widget_mut, so a change to masonry_core.core.widget_mut can break masonry.widgets.checkbox, while a change to masonry.widgets.checkbox can't break masonry_core.core.widget_mut.
- Position
- Below the diagonal: masonry.widgets.checkbox uses a module listed above it, which is the healthy direction.
35→7 masonry.widgets.checkbox uses masonry_core.core.widget_pod✕
- Connections
- 2 pairs of types, where a type in masonry.widgets.checkbox uses a type in masonry_core.core.widget_pod.
- The types involved
masonry.widgets.checkbox.Checkbox→masonry_core.core.widget_pod.NewWidgetmasonry.widgets.checkbox.Checkbox→masonry_core.core.widget_pod.WidgetPod
- Direction
- masonry.widgets.checkbox uses masonry_core.core.widget_pod, so a change to masonry_core.core.widget_pod can break masonry.widgets.checkbox, while a change to masonry.widgets.checkbox can't break masonry_core.core.widget_pod.
- Position
- Below the diagonal: masonry.widgets.checkbox uses a module listed above it, which is the healthy direction.
35→8 masonry.widgets.checkbox uses masonry_core.layout.len_req✕
- Connections
- 1 pair of types, where a type in masonry.widgets.checkbox uses a type in masonry_core.layout.len_req.
- The types involved
masonry.widgets.checkbox.Checkbox→masonry_core.layout.len_req.LenReq
- Direction
- masonry.widgets.checkbox uses masonry_core.layout.len_req, so a change to masonry_core.layout.len_req can break masonry.widgets.checkbox, while a change to masonry.widgets.checkbox can't break masonry_core.layout.len_req.
- Position
- Below the diagonal: masonry.widgets.checkbox uses a module listed above it, which is the healthy direction.
35→10 masonry.widgets.checkbox uses masonry_core.core.widget✕
- Connections
- 2 pairs of types, where a type in masonry.widgets.checkbox uses a type in masonry_core.core.widget.
- The types involved
masonry.widgets.checkbox.Checkbox→masonry_core.core.widget.Widgetmasonry.widgets.checkbox.Checkbox→masonry_core.core.widget.WidgetId
- Direction
- masonry.widgets.checkbox uses masonry_core.core.widget, so a change to masonry_core.core.widget can break masonry.widgets.checkbox, while a change to masonry.widgets.checkbox can't break masonry_core.core.widget.
- Position
- Below the diagonal: masonry.widgets.checkbox uses a module listed above it, which is the healthy direction.
35→13 masonry.widgets.checkbox uses masonry_core.core.property✕
- Connections
- 1 pair of types, where a type in masonry.widgets.checkbox uses a type in masonry_core.core.property.
- The types involved
masonry.widgets.checkbox.Checkbox→masonry_core.core.property.UsesProperty
- Direction
- masonry.widgets.checkbox uses masonry_core.core.property, so a change to masonry_core.core.property can break masonry.widgets.checkbox, while a change to masonry.widgets.checkbox can't break masonry_core.core.property.
- Position
- Below the diagonal: masonry.widgets.checkbox uses a module listed above it, which is the healthy direction.
35→27 masonry.widgets.checkbox uses xilem_web.elements.html✕
- Connections
- 1 pair of types, where a type in masonry.widgets.checkbox uses a type in xilem_web.elements.html.
- The types involved
masonry.widgets.checkbox.Checkbox→xilem_web.elements.html.Span
- Direction
- masonry.widgets.checkbox uses xilem_web.elements.html, so a change to xilem_web.elements.html can break masonry.widgets.checkbox, while a change to masonry.widgets.checkbox can't break xilem_web.elements.html.
- Position
- Below the diagonal: masonry.widgets.checkbox uses a module listed above it, which is the healthy direction.
35→32 masonry.widgets.checkbox uses masonry_core.core.contexts✕
- Connections
- 7 pairs of types, where a type in masonry.widgets.checkbox uses a type in masonry_core.core.contexts.
- The types involved
masonry.widgets.checkbox.Checkbox→masonry_core.core.contexts.AccessCtxmasonry.widgets.checkbox.Checkbox→masonry_core.core.contexts.EventCtxmasonry.widgets.checkbox.Checkbox→masonry_core.core.contexts.LayoutCtxmasonry.widgets.checkbox.Checkbox→masonry_core.core.contexts.MeasureCtxmasonry.widgets.checkbox.Checkbox→masonry_core.core.contexts.PaintCtxmasonry.widgets.checkbox.Checkbox→masonry_core.core.contexts.RegisterCtxmasonry.widgets.checkbox.Checkbox→masonry_core.core.contexts.UpdateCtx
- Direction
- masonry.widgets.checkbox uses masonry_core.core.contexts, so a change to masonry_core.core.contexts can break masonry.widgets.checkbox, while a change to masonry.widgets.checkbox can't break masonry_core.core.contexts.
- Position
- Below the diagonal: masonry.widgets.checkbox uses a module listed above it, which is the healthy direction.
36→1 masonry.widgets.divider uses masonry_core.core.events✕
- Connections
- 1 pair of types, where a type in masonry.widgets.divider uses a type in masonry_core.core.events.
- The types involved
masonry.widgets.divider.Divider→masonry_core.core.events.Update
- 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.
36→2 masonry.widgets.divider uses masonry_core.layout.length✕
- Connections
- 1 pair of types, where a type in masonry.widgets.divider uses a type in masonry_core.layout.length.
- The types involved
masonry.widgets.divider.Divider→masonry_core.layout.length.Length
- 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.
36→4 masonry.widgets.divider uses masonry_core.core.properties_mut✕
- Connections
- 1 pair of types, where a type in masonry.widgets.divider uses a type in masonry_core.core.properties_mut.
- The types involved
masonry.widgets.divider.Divider→masonry_core.core.properties_mut.PropertiesMut
- 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.
36→5 masonry.widgets.divider uses masonry_core.core.properties_ref✕
- Connections
- 1 pair of types, where a type in masonry.widgets.divider uses a type in masonry_core.core.properties_ref.
- The types involved
masonry.widgets.divider.Divider→masonry_core.core.properties_ref.PropertiesRef
- 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.
36→6 masonry.widgets.divider uses masonry_core.core.widget_mut✕
- Connections
- 1 pair of types, where a type in masonry.widgets.divider uses a type in masonry_core.core.widget_mut.
- The types involved
masonry.widgets.divider.Divider→masonry_core.core.widget_mut.WidgetMut
- 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.
36→7 masonry.widgets.divider uses masonry_core.core.widget_pod✕
- Connections
- 2 pairs of types, where a type in masonry.widgets.divider uses a type in masonry_core.core.widget_pod.
- The types involved
masonry.widgets.divider.Divider→masonry_core.core.widget_pod.NewWidgetmasonry.widgets.divider.Divider→masonry_core.core.widget_pod.WidgetPod
- 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.
36→8 masonry.widgets.divider uses masonry_core.layout.len_req✕
- Connections
- 1 pair of types, where a type in masonry.widgets.divider uses a type in masonry_core.layout.len_req.
- The types involved
masonry.widgets.divider.Divider→masonry_core.layout.len_req.LenReq
- 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.
36→10 masonry.widgets.divider uses masonry_core.core.widget✕
- Connections
- 2 pairs of types, where a type in masonry.widgets.divider uses a type in masonry_core.core.widget.
- The types involved
masonry.widgets.divider.Divider→masonry_core.core.widget.Widgetmasonry.widgets.divider.Divider→masonry_core.core.widget.WidgetId
- 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.
36→13 masonry.widgets.divider uses masonry_core.core.property✕
- Connections
- 1 pair of types, where a type in masonry.widgets.divider uses a type in masonry_core.core.property.
- The types involved
masonry.widgets.divider.Divider→masonry_core.core.property.UsesProperty
- 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.
36→21 masonry.widgets.divider uses xilem_web.elements.svg✕
- Connections
- 1 pair of types, where a type in masonry.widgets.divider uses a type in xilem_web.elements.svg.
- The types involved
masonry.widgets.divider.LineLayout→xilem_web.elements.svg.Line
- Direction
- masonry.widgets.divider uses xilem_web.elements.svg, so a change to xilem_web.elements.svg can break masonry.widgets.divider, while a change to masonry.widgets.divider can't break xilem_web.elements.svg.
- Position
- Below the diagonal: masonry.widgets.divider uses a module listed above it, which is the healthy direction.
36→27 masonry.widgets.divider uses xilem_web.elements.html✕
- Connections
- 1 pair of types, where a type in masonry.widgets.divider uses a type in xilem_web.elements.html.
- The types involved
masonry.widgets.divider.Divider→xilem_web.elements.html.Span
- Direction
- masonry.widgets.divider uses xilem_web.elements.html, so a change to xilem_web.elements.html can break masonry.widgets.divider, while a change to masonry.widgets.divider can't break xilem_web.elements.html.
- Position
- Below the diagonal: masonry.widgets.divider uses a module listed above it, which is the healthy direction.
36→32 masonry.widgets.divider uses masonry_core.core.contexts✕
- Connections
- 6 pairs of types, where a type in masonry.widgets.divider uses a type in masonry_core.core.contexts.
- The types involved
masonry.widgets.divider.Divider→masonry_core.core.contexts.AccessCtxmasonry.widgets.divider.Divider→masonry_core.core.contexts.LayoutCtxmasonry.widgets.divider.Divider→masonry_core.core.contexts.MeasureCtxmasonry.widgets.divider.Divider→masonry_core.core.contexts.PaintCtxmasonry.widgets.divider.Divider→masonry_core.core.contexts.RegisterCtxmasonry.widgets.divider.Divider→masonry_core.core.contexts.UpdateCtx
- 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.
37→2 masonry.widgets.grid uses masonry_core.layout.length✕
- Connections
- 1 pair of types, where a type in masonry.widgets.grid uses a type in masonry_core.layout.length.
- The types involved
masonry.widgets.grid.Grid→masonry_core.layout.length.Length
- Direction
- masonry.widgets.grid uses masonry_core.layout.length, so a change to masonry_core.layout.length can break masonry.widgets.grid, while a change to masonry.widgets.grid can't break masonry_core.layout.length.
- Position
- Below the diagonal: masonry.widgets.grid uses a module listed above it, which is the healthy direction.
37→5 masonry.widgets.grid uses masonry_core.core.properties_ref✕
- Connections
- 1 pair of types, where a type in masonry.widgets.grid uses a type in masonry_core.core.properties_ref.
- The types involved
masonry.widgets.grid.Grid→masonry_core.core.properties_ref.PropertiesRef
- Direction
- masonry.widgets.grid uses masonry_core.core.properties_ref, so a change to masonry_core.core.properties_ref can break masonry.widgets.grid, while a change to masonry.widgets.grid can't break masonry_core.core.properties_ref.
- Position
- Below the diagonal: masonry.widgets.grid uses a module listed above it, which is the healthy direction.
37→6 masonry.widgets.grid uses masonry_core.core.widget_mut✕
- Connections
- 1 pair of types, where a type in masonry.widgets.grid uses a type in masonry_core.core.widget_mut.
- The types involved
masonry.widgets.grid.Grid→masonry_core.core.widget_mut.WidgetMut
- Direction
- masonry.widgets.grid uses masonry_core.core.widget_mut, so a change to masonry_core.core.widget_mut can break masonry.widgets.grid, while a change to masonry.widgets.grid can't break masonry_core.core.widget_mut.
- Position
- Below the diagonal: masonry.widgets.grid uses a module listed above it, which is the healthy direction.
37→7 masonry.widgets.grid uses masonry_core.core.widget_pod✕
- Connections
- 3 pairs of types, where a type in masonry.widgets.grid uses a type in masonry_core.core.widget_pod.
- The types involved
masonry.widgets.grid.Child→masonry_core.core.widget_pod.NewWidgetmasonry.widgets.grid.Child→masonry_core.core.widget_pod.WidgetPodmasonry.widgets.grid.Grid→masonry_core.core.widget_pod.NewWidget
- Direction
- masonry.widgets.grid uses masonry_core.core.widget_pod, so a change to masonry_core.core.widget_pod can break masonry.widgets.grid, while a change to masonry.widgets.grid can't break masonry_core.core.widget_pod.
- Position
- Below the diagonal: masonry.widgets.grid uses a module listed above it, which is the healthy direction.
37→8 masonry.widgets.grid uses masonry_core.layout.len_req✕
- Connections
- 1 pair of types, where a type in masonry.widgets.grid uses a type in masonry_core.layout.len_req.
- The types involved
masonry.widgets.grid.Grid→masonry_core.layout.len_req.LenReq
- Direction
- masonry.widgets.grid uses masonry_core.layout.len_req, so a change to masonry_core.layout.len_req can break masonry.widgets.grid, while a change to masonry.widgets.grid can't break masonry_core.layout.len_req.
- Position
- Below the diagonal: masonry.widgets.grid uses a module listed above it, which is the healthy direction.
37→10 masonry.widgets.grid uses masonry_core.core.widget✕
- Connections
- 3 pairs of types, where a type in masonry.widgets.grid uses a type in masonry_core.core.widget.
- The types involved
masonry.widgets.grid.Grid→masonry_core.core.widget.CollectionWidgetmasonry.widgets.grid.Grid→masonry_core.core.widget.Widgetmasonry.widgets.grid.Grid→masonry_core.core.widget.WidgetId
- Direction
- masonry.widgets.grid uses masonry_core.core.widget, so a change to masonry_core.core.widget can break masonry.widgets.grid, while a change to masonry.widgets.grid can't break masonry_core.core.widget.
- Position
- Below the diagonal: masonry.widgets.grid uses a module listed above it, which is the healthy direction.
37→13 masonry.widgets.grid uses masonry_core.core.property✕
- Connections
- 1 pair of types, where a type in masonry.widgets.grid uses a type in masonry_core.core.property.
- The types involved
masonry.widgets.grid.Grid→masonry_core.core.property.UsesProperty
- Direction
- masonry.widgets.grid uses masonry_core.core.property, so a change to masonry_core.core.property can break masonry.widgets.grid, while a change to masonry.widgets.grid can't break masonry_core.core.property.
- Position
- Below the diagonal: masonry.widgets.grid uses a module listed above it, which is the healthy direction.
37→14 masonry.widgets.grid uses masonry.widgets.flex✕
- Connections
- 1 pair of types, where a type in masonry.widgets.grid uses a type in masonry.widgets.flex.
- The types involved
masonry.widgets.grid.Grid→masonry.widgets.flex.Child
- Direction
- masonry.widgets.grid uses masonry.widgets.flex, so a change to masonry.widgets.flex can break masonry.widgets.grid, while a change to masonry.widgets.grid can't break masonry.widgets.flex.
- Position
- Below the diagonal: masonry.widgets.grid uses a module listed above it, which is the healthy direction.
37→27 masonry.widgets.grid uses xilem_web.elements.html✕
- Connections
- 1 pair of types, where a type in masonry.widgets.grid uses a type in xilem_web.elements.html.
- The types involved
masonry.widgets.grid.Grid→xilem_web.elements.html.Span
- Direction
- masonry.widgets.grid uses xilem_web.elements.html, so a change to xilem_web.elements.html can break masonry.widgets.grid, while a change to masonry.widgets.grid can't break xilem_web.elements.html.
- Position
- Below the diagonal: masonry.widgets.grid uses a module listed above it, which is the healthy direction.
37→32 masonry.widgets.grid uses masonry_core.core.contexts✕
- Connections
- 6 pairs of types, where a type in masonry.widgets.grid uses a type in masonry_core.core.contexts.
- The types involved
masonry.widgets.grid.Grid→masonry_core.core.contexts.AccessCtxmasonry.widgets.grid.Grid→masonry_core.core.contexts.LayoutCtxmasonry.widgets.grid.Grid→masonry_core.core.contexts.MeasureCtxmasonry.widgets.grid.Grid→masonry_core.core.contexts.PaintCtxmasonry.widgets.grid.Grid→masonry_core.core.contexts.RegisterCtxmasonry.widgets.grid.Grid→masonry_core.core.contexts.UpdateCtx
- Direction
- masonry.widgets.grid uses masonry_core.core.contexts, so a change to masonry_core.core.contexts can break masonry.widgets.grid, while a change to masonry.widgets.grid can't break masonry_core.core.contexts.
- Position
- Below the diagonal: masonry.widgets.grid uses a module listed above it, which is the healthy direction.
38→1 masonry.widgets.radio_button uses masonry_core.core.events✕
- Connections
- 3 pairs of types, where a type in masonry.widgets.radio_button uses a type in masonry_core.core.events.
- The types involved
masonry.widgets.radio_button.RadioButton→masonry_core.core.events.AccessEventmasonry.widgets.radio_button.RadioButton→masonry_core.core.events.TextEventmasonry.widgets.radio_button.RadioButton→masonry_core.core.events.Update
- Direction
- masonry.widgets.radio_button uses masonry_core.core.events, so a change to masonry_core.core.events can break masonry.widgets.radio_button, while a change to masonry.widgets.radio_button can't break masonry_core.core.events.
- Position
- Below the diagonal: masonry.widgets.radio_button uses a module listed above it, which is the healthy direction.
38→2 masonry.widgets.radio_button uses masonry_core.layout.length✕
- Connections
- 1 pair of types, where a type in masonry.widgets.radio_button uses a type in masonry_core.layout.length.
- The types involved
masonry.widgets.radio_button.RadioButton→masonry_core.layout.length.Length
- Direction
- masonry.widgets.radio_button uses masonry_core.layout.length, so a change to masonry_core.layout.length can break masonry.widgets.radio_button, while a change to masonry.widgets.radio_button can't break masonry_core.layout.length.
- Position
- Below the diagonal: masonry.widgets.radio_button uses a module listed above it, which is the healthy direction.
38→4 masonry.widgets.radio_button uses masonry_core.core.properties_mut✕
- Connections
- 1 pair of types, where a type in masonry.widgets.radio_button uses a type in masonry_core.core.properties_mut.
- The types involved
masonry.widgets.radio_button.RadioButton→masonry_core.core.properties_mut.PropertiesMut
- Direction
- masonry.widgets.radio_button uses masonry_core.core.properties_mut, so a change to masonry_core.core.properties_mut can break masonry.widgets.radio_button, while a change to masonry.widgets.radio_button can't break masonry_core.core.properties_mut.
- Position
- Below the diagonal: masonry.widgets.radio_button uses a module listed above it, which is the healthy direction.
38→5 masonry.widgets.radio_button uses masonry_core.core.properties_ref✕
- Connections
- 1 pair of types, where a type in masonry.widgets.radio_button uses a type in masonry_core.core.properties_ref.
- The types involved
masonry.widgets.radio_button.RadioButton→masonry_core.core.properties_ref.PropertiesRef
- Direction
- masonry.widgets.radio_button uses masonry_core.core.properties_ref, so a change to masonry_core.core.properties_ref can break masonry.widgets.radio_button, while a change to masonry.widgets.radio_button can't break masonry_core.core.properties_ref.
- Position
- Below the diagonal: masonry.widgets.radio_button uses a module listed above it, which is the healthy direction.
38→6 masonry.widgets.radio_button uses masonry_core.core.widget_mut✕
- Connections
- 1 pair of types, where a type in masonry.widgets.radio_button uses a type in masonry_core.core.widget_mut.
- The types involved
masonry.widgets.radio_button.RadioButton→masonry_core.core.widget_mut.WidgetMut
- Direction
- masonry.widgets.radio_button uses masonry_core.core.widget_mut, so a change to masonry_core.core.widget_mut can break masonry.widgets.radio_button, while a change to masonry.widgets.radio_button can't break masonry_core.core.widget_mut.
- Position
- Below the diagonal: masonry.widgets.radio_button uses a module listed above it, which is the healthy direction.
38→7 masonry.widgets.radio_button uses masonry_core.core.widget_pod✕
- Connections
- 2 pairs of types, where a type in masonry.widgets.radio_button uses a type in masonry_core.core.widget_pod.
- The types involved
masonry.widgets.radio_button.RadioButton→masonry_core.core.widget_pod.NewWidgetmasonry.widgets.radio_button.RadioButton→masonry_core.core.widget_pod.WidgetPod
- Direction
- masonry.widgets.radio_button uses masonry_core.core.widget_pod, so a change to masonry_core.core.widget_pod can break masonry.widgets.radio_button, while a change to masonry.widgets.radio_button can't break masonry_core.core.widget_pod.
- Position
- Below the diagonal: masonry.widgets.radio_button uses a module listed above it, which is the healthy direction.
38→8 masonry.widgets.radio_button uses masonry_core.layout.len_req✕
- Connections
- 1 pair of types, where a type in masonry.widgets.radio_button uses a type in masonry_core.layout.len_req.
- The types involved
masonry.widgets.radio_button.RadioButton→masonry_core.layout.len_req.LenReq
- Direction
- masonry.widgets.radio_button uses masonry_core.layout.len_req, so a change to masonry_core.layout.len_req can break masonry.widgets.radio_button, while a change to masonry.widgets.radio_button can't break masonry_core.layout.len_req.
- Position
- Below the diagonal: masonry.widgets.radio_button uses a module listed above it, which is the healthy direction.
38→10 masonry.widgets.radio_button uses masonry_core.core.widget✕
- Connections
- 2 pairs of types, where a type in masonry.widgets.radio_button uses a type in masonry_core.core.widget.
- The types involved
masonry.widgets.radio_button.RadioButton→masonry_core.core.widget.Widgetmasonry.widgets.radio_button.RadioButton→masonry_core.core.widget.WidgetId
- Direction
- masonry.widgets.radio_button uses masonry_core.core.widget, so a change to masonry_core.core.widget can break masonry.widgets.radio_button, while a change to masonry.widgets.radio_button can't break masonry_core.core.widget.
- Position
- Below the diagonal: masonry.widgets.radio_button uses a module listed above it, which is the healthy direction.
38→13 masonry.widgets.radio_button uses masonry_core.core.property✕
- Connections
- 1 pair of types, where a type in masonry.widgets.radio_button uses a type in masonry_core.core.property.
- The types involved
masonry.widgets.radio_button.RadioButton→masonry_core.core.property.UsesProperty
- Direction
- masonry.widgets.radio_button uses masonry_core.core.property, so a change to masonry_core.core.property can break masonry.widgets.radio_button, while a change to masonry.widgets.radio_button can't break masonry_core.core.property.
- Position
- Below the diagonal: masonry.widgets.radio_button uses a module listed above it, which is the healthy direction.
38→27 masonry.widgets.radio_button uses xilem_web.elements.html✕
- Connections
- 1 pair of types, where a type in masonry.widgets.radio_button uses a type in xilem_web.elements.html.
- The types involved
masonry.widgets.radio_button.RadioButton→xilem_web.elements.html.Span
- Direction
- masonry.widgets.radio_button uses xilem_web.elements.html, so a change to xilem_web.elements.html can break masonry.widgets.radio_button, while a change to masonry.widgets.radio_button can't break xilem_web.elements.html.
- Position
- Below the diagonal: masonry.widgets.radio_button uses a module listed above it, which is the healthy direction.
38→32 masonry.widgets.radio_button uses masonry_core.core.contexts✕
- Connections
- 7 pairs of types, where a type in masonry.widgets.radio_button uses a type in masonry_core.core.contexts.
- The types involved
masonry.widgets.radio_button.RadioButton→masonry_core.core.contexts.AccessCtxmasonry.widgets.radio_button.RadioButton→masonry_core.core.contexts.EventCtxmasonry.widgets.radio_button.RadioButton→masonry_core.core.contexts.LayoutCtxmasonry.widgets.radio_button.RadioButton→masonry_core.core.contexts.MeasureCtxmasonry.widgets.radio_button.RadioButton→masonry_core.core.contexts.PaintCtxmasonry.widgets.radio_button.RadioButton→masonry_core.core.contexts.RegisterCtxmasonry.widgets.radio_button.RadioButton→masonry_core.core.contexts.UpdateCtx
- Direction
- masonry.widgets.radio_button uses masonry_core.core.contexts, so a change to masonry_core.core.contexts can break masonry.widgets.radio_button, while a change to masonry.widgets.radio_button can't break masonry_core.core.contexts.
- Position
- Below the diagonal: masonry.widgets.radio_button uses a module listed above it, which is the healthy direction.
39→1 masonry.widgets.scroll_bar uses masonry_core.core.events✕
- Connections
- 2 pairs of types, where a type in masonry.widgets.scroll_bar uses a type in masonry_core.core.events.
- The types involved
masonry.widgets.scroll_bar.ScrollBar→masonry_core.core.events.AccessEventmasonry.widgets.scroll_bar.ScrollBar→masonry_core.core.events.TextEvent
- Direction
- masonry.widgets.scroll_bar uses masonry_core.core.events, so a change to masonry_core.core.events can break masonry.widgets.scroll_bar, while a change to masonry.widgets.scroll_bar can't break masonry_core.core.events.
- Position
- Below the diagonal: masonry.widgets.scroll_bar uses a module listed above it, which is the healthy direction.
39→2 masonry.widgets.scroll_bar uses masonry_core.layout.length✕
- Connections
- 1 pair of types, where a type in masonry.widgets.scroll_bar uses a type in masonry_core.layout.length.
- The types involved
masonry.widgets.scroll_bar.ScrollBar→masonry_core.layout.length.Length
- Direction
- masonry.widgets.scroll_bar uses masonry_core.layout.length, so a change to masonry_core.layout.length can break masonry.widgets.scroll_bar, while a change to masonry.widgets.scroll_bar can't break masonry_core.layout.length.
- Position
- Below the diagonal: masonry.widgets.scroll_bar uses a module listed above it, which is the healthy direction.
39→4 masonry.widgets.scroll_bar uses masonry_core.core.properties_mut✕
- Connections
- 1 pair of types, where a type in masonry.widgets.scroll_bar uses a type in masonry_core.core.properties_mut.
- The types involved
masonry.widgets.scroll_bar.ScrollBar→masonry_core.core.properties_mut.PropertiesMut
- Direction
- masonry.widgets.scroll_bar uses masonry_core.core.properties_mut, so a change to masonry_core.core.properties_mut can break masonry.widgets.scroll_bar, while a change to masonry.widgets.scroll_bar can't break masonry_core.core.properties_mut.
- Position
- Below the diagonal: masonry.widgets.scroll_bar uses a module listed above it, which is the healthy direction.
39→5 masonry.widgets.scroll_bar uses masonry_core.core.properties_ref✕
- Connections
- 1 pair of types, where a type in masonry.widgets.scroll_bar uses a type in masonry_core.core.properties_ref.
- The types involved
masonry.widgets.scroll_bar.ScrollBar→masonry_core.core.properties_ref.PropertiesRef
- Direction
- masonry.widgets.scroll_bar uses masonry_core.core.properties_ref, so a change to masonry_core.core.properties_ref can break masonry.widgets.scroll_bar, while a change to masonry.widgets.scroll_bar can't break masonry_core.core.properties_ref.
- Position
- Below the diagonal: masonry.widgets.scroll_bar uses a module listed above it, which is the healthy direction.
39→6 masonry.widgets.scroll_bar uses masonry_core.core.widget_mut✕
- Connections
- 1 pair of types, where a type in masonry.widgets.scroll_bar uses a type in masonry_core.core.widget_mut.
- The types involved
masonry.widgets.scroll_bar.ScrollBar→masonry_core.core.widget_mut.WidgetMut
- Direction
- masonry.widgets.scroll_bar uses masonry_core.core.widget_mut, so a change to masonry_core.core.widget_mut can break masonry.widgets.scroll_bar, while a change to masonry.widgets.scroll_bar can't break masonry_core.core.widget_mut.
- Position
- Below the diagonal: masonry.widgets.scroll_bar uses a module listed above it, which is the healthy direction.
39→8 masonry.widgets.scroll_bar uses masonry_core.layout.len_req✕
- Connections
- 1 pair of types, where a type in masonry.widgets.scroll_bar uses a type in masonry_core.layout.len_req.
- The types involved
masonry.widgets.scroll_bar.ScrollBar→masonry_core.layout.len_req.LenReq
- Direction
- masonry.widgets.scroll_bar uses masonry_core.layout.len_req, so a change to masonry_core.layout.len_req can break masonry.widgets.scroll_bar, while a change to masonry.widgets.scroll_bar can't break masonry_core.layout.len_req.
- Position
- Below the diagonal: masonry.widgets.scroll_bar uses a module listed above it, which is the healthy direction.
39→10 masonry.widgets.scroll_bar uses masonry_core.core.widget✕
- Connections
- 3 pairs of types, where a type in masonry.widgets.scroll_bar uses a type in masonry_core.core.widget.
- The types involved
masonry.widgets.scroll_bar.ScrollBar→masonry_core.core.widget.AllowRawMutmasonry.widgets.scroll_bar.ScrollBar→masonry_core.core.widget.Widgetmasonry.widgets.scroll_bar.ScrollBar→masonry_core.core.widget.WidgetId
- Direction
- masonry.widgets.scroll_bar uses masonry_core.core.widget, so a change to masonry_core.core.widget can break masonry.widgets.scroll_bar, while a change to masonry.widgets.scroll_bar can't break masonry_core.core.widget.
- Position
- Below the diagonal: masonry.widgets.scroll_bar uses a module listed above it, which is the healthy direction.
39→13 masonry.widgets.scroll_bar uses masonry_core.core.property✕
- Connections
- 1 pair of types, where a type in masonry.widgets.scroll_bar uses a type in masonry_core.core.property.
- The types involved
masonry.widgets.scroll_bar.ScrollBar→masonry_core.core.property.UsesProperty
- Direction
- masonry.widgets.scroll_bar uses masonry_core.core.property, so a change to masonry_core.core.property can break masonry.widgets.scroll_bar, while a change to masonry.widgets.scroll_bar can't break masonry_core.core.property.
- Position
- Below the diagonal: masonry.widgets.scroll_bar uses a module listed above it, which is the healthy direction.
39→21 masonry.widgets.scroll_bar uses xilem_web.elements.svg✕
- Connections
- 1 pair of types, where a type in masonry.widgets.scroll_bar uses a type in xilem_web.elements.svg.
- The types involved
masonry.widgets.scroll_bar.ScrollBar→xilem_web.elements.svg.Rect
- Direction
- masonry.widgets.scroll_bar uses xilem_web.elements.svg, so a change to xilem_web.elements.svg can break masonry.widgets.scroll_bar, while a change to masonry.widgets.scroll_bar can't break xilem_web.elements.svg.
- Position
- Below the diagonal: masonry.widgets.scroll_bar uses a module listed above it, which is the healthy direction.
39→27 masonry.widgets.scroll_bar uses xilem_web.elements.html✕
- Connections
- 1 pair of types, where a type in masonry.widgets.scroll_bar uses a type in xilem_web.elements.html.
- The types involved
masonry.widgets.scroll_bar.ScrollBar→xilem_web.elements.html.Span
- Direction
- masonry.widgets.scroll_bar uses xilem_web.elements.html, so a change to xilem_web.elements.html can break masonry.widgets.scroll_bar, while a change to masonry.widgets.scroll_bar can't break xilem_web.elements.html.
- Position
- Below the diagonal: masonry.widgets.scroll_bar uses a module listed above it, which is the healthy direction.
39→32 masonry.widgets.scroll_bar uses masonry_core.core.contexts✕
- Connections
- 7 pairs of types, where a type in masonry.widgets.scroll_bar uses a type in masonry_core.core.contexts.
- The types involved
masonry.widgets.scroll_bar.ScrollBar→masonry_core.core.contexts.AccessCtxmasonry.widgets.scroll_bar.ScrollBar→masonry_core.core.contexts.EventCtxmasonry.widgets.scroll_bar.ScrollBar→masonry_core.core.contexts.LayoutCtxmasonry.widgets.scroll_bar.ScrollBar→masonry_core.core.contexts.MeasureCtxmasonry.widgets.scroll_bar.ScrollBar→masonry_core.core.contexts.PaintCtxmasonry.widgets.scroll_bar.ScrollBar→masonry_core.core.contexts.RegisterCtxmasonry.widgets.scroll_bar.ScrollBar→masonry_core.core.contexts.UpdateCtx
- Direction
- masonry.widgets.scroll_bar uses masonry_core.core.contexts, so a change to masonry_core.core.contexts can break masonry.widgets.scroll_bar, while a change to masonry.widgets.scroll_bar can't break masonry_core.core.contexts.
- Position
- Below the diagonal: masonry.widgets.scroll_bar uses a module listed above it, which is the healthy direction.
40→3 xilem_masonry.view.grid uses xilem_core.message✕
- Connections
- 2 pairs of types, where a type in xilem_masonry.view.grid uses a type in xilem_core.message.
- The types involved
xilem_masonry.view.grid.Grid→xilem_core.message.MessageResultxilem_masonry.view.grid.GridItem→xilem_core.message.MessageResult
- 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.
40→6 xilem_masonry.view.grid uses masonry_core.core.widget_mut✕
- Connections
- 2 pairs of types, where a type in xilem_masonry.view.grid uses a type in masonry_core.core.widget_mut.
- The types involved
xilem_masonry.view.grid.GridElementMut→masonry_core.core.widget_mut.WidgetMutxilem_masonry.view.grid.GridSplice→masonry_core.core.widget_mut.WidgetMut
- 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.
40→9 xilem_masonry.view.grid uses xilem_core.message_context✕
- Connections
- 2 pairs of types, where a type in xilem_masonry.view.grid uses a type in xilem_core.message_context.
- The types involved
xilem_masonry.view.grid.Grid→xilem_core.message_context.MessageCtxxilem_masonry.view.grid.GridItem→xilem_core.message_context.MessageCtx
- 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.
40→11 xilem_masonry.view.grid uses xilem_core.view✕
- Connections
- 4 pairs of types, where a type in xilem_masonry.view.grid uses a type in xilem_core.view.
- The types involved
xilem_masonry.view.grid.Grid→xilem_core.view.Viewxilem_masonry.view.grid.Grid→xilem_core.view.ViewMarkerxilem_masonry.view.grid.GridItem→xilem_core.view.Viewxilem_masonry.view.grid.GridItem→xilem_core.view.ViewMarker
- 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.
40→18 xilem_masonry.view.grid uses xilem_core.docs✕
- Connections
- 2 pairs of types, where a type in xilem_masonry.view.grid uses a type in xilem_core.docs.
- The types involved
xilem_masonry.view.grid.Grid→xilem_core.docs.Statexilem_masonry.view.grid.GridItem→xilem_core.docs.State
- 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.
40→19 xilem_masonry.view.grid uses xilem_masonry.view_ctx✕
- Connections
- 3 pairs of types, where a type in xilem_masonry.view.grid uses a type in xilem_masonry.view_ctx.
- The types involved
xilem_masonry.view.grid.Grid→xilem_masonry.view_ctx.ViewCtxxilem_masonry.view.grid.GridElement→xilem_masonry.view_ctx.ViewCtxxilem_masonry.view.grid.GridItem→xilem_masonry.view_ctx.ViewCtx
- 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.
40→24 xilem_masonry.view.grid uses xilem_core.element_splice✕
- Connections
- 2 pairs of types, where a type in xilem_masonry.view.grid uses a type in xilem_core.element_splice.
- The types involved
xilem_masonry.view.grid.GridSplice→xilem_core.element_splice.AppendVecxilem_masonry.view.grid.GridSplice→xilem_core.element_splice.ElementSplice
- 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.
40→27 xilem_masonry.view.grid uses xilem_web.elements.html✕
- Connections
- 1 pair of types, where a type in xilem_masonry.view.grid uses a type in xilem_web.elements.html.
- The types involved
xilem_masonry.view.grid.Grid→xilem_web.elements.html.Col
- Direction
- xilem_masonry.view.grid uses xilem_web.elements.html, so a change to xilem_web.elements.html can break xilem_masonry.view.grid, while a change to xilem_masonry.view.grid can't break xilem_web.elements.html.
- Position
- Below the diagonal: xilem_masonry.view.grid uses a module listed above it, which is the healthy direction.
40→37 xilem_masonry.view.grid uses masonry.widgets.grid✕
- Connections
- 7 pairs of types, where a type in xilem_masonry.view.grid uses a type in masonry.widgets.grid.
- The types involved
xilem_masonry.view.grid.Grid→masonry.widgets.grid.Gridxilem_masonry.view.grid.GridElement→masonry.widgets.grid.GridParamsxilem_masonry.view.grid.GridExt→masonry.widgets.grid.GridParamsxilem_masonry.view.grid.GridItem→masonry.widgets.grid.GridParamsxilem_masonry.view.grid.grid$module→masonry.widgets.grid.Gridxilem_masonry.view.grid.grid$module→masonry.widgets.grid.GridParamsxilem_masonry.view.grid.grid$module→masonry.widgets.grid.GridTrackSize
- Direction
- xilem_masonry.view.grid uses masonry.widgets.grid, so a change to masonry.widgets.grid can break xilem_masonry.view.grid, while a change to xilem_masonry.view.grid can't break masonry.widgets.grid.
- Position
- Below the diagonal: xilem_masonry.view.grid uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 41 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 20 | High / Critical |
Roadmap
First, address visual and motion safety by ensuring visible focus styles, respecting reduced motion preferences, and fixing low-contrast colors. Next, correct page structure issues by adding required language attributes, titles, and main landmarks while maintaining proper heading order. Then, integrate accessibility checks into your existing test suite and CI pipeline to prevent future regressions. Finally, resolve structured logging errors and enable dependency scanning tools to improve security and maintainability.
| 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. | +7.1 pts | Medium | Visual & motion safety |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +6.3 pts | Medium | Page structure |
| Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge. | +5.6 pts | Medium | A11y enforcement |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.0 pts | Low | ADR Quality |
| Interpolated log message defeats structured logging | +1.7 pts | Medium | Structured logging |
| Enable Dependabot/Renovate or a dependency-review gate. | +1.4 pts | Medium | Security & performance tooling |
| Resolve the 6 Orphaned knowledge finding(s) in Knowledge Freshness — start with interfaces.rs, elements.rs, environment.rs. | +0.5 pts | Low | Knowledge Freshness |
| Keep implementation types off the public surface (Rust: `pub(crate)`, or keep the module private) so internals can change without breaking consumers. | +1.0 pts | Medium | Library API & versioning |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.6 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| masonry/src/widgets/label.rs | 3.4 | Mixed | Change Coupling: Boundary-crossing change coupling: label.rs ↔ prose.rs |
| masonry/src/widgets/text_area.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| masonry_core/src/passes/update.rs | 6.0 | Mixed | Explicit Debt: HackComment |
| placehero/src/html_content.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| masonry_winit/src/event_loop_runner.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| masonry_core/src/passes/paint.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| masonry/src/widgets/flex.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| masonry/src/widgets/step_input.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| masonry_core/src/passes/layout.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| masonry_core/src/core/text.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| xilem_masonry/src/view/virtual_scroll.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| masonry/src/widgets/slider.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| masonry_testing/src/harness.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| masonry/src/widgets/portal.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| xilem_web/src/elements.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| xilem_web/src/interfaces.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| masonry/src/theme.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| masonry_core/src/core/widget_state.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
How the grades work
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.
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.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 51 of 51 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 51 dimensions across the health lenses
- 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, 788 of 819 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 70 test files), but it was not re-run: its build outgrew the 6 GB scratch ceiling (6.046 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 21 further occurrence(s) are not listed individually; the score already reflects all 61.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- 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 is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- 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.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- 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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- 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.
Dimensions
D1 · Cyclomatic Complexity
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.
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.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
26 function(s) exceeded the cognitive complexity threshold of 15; the worst was TextArea::on_text_event at 109.
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.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
40 over-large unit(s) detected — types, modules or files that carry too much.
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).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
70 duplicated block group(s) detected. A further 4 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 1 of the 74 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.
What to do
- Resolve the 8 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with checkbox.rs (2), event.rs, update.rs. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 6 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with badge.rs (2), slider.rs, text_input.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 5 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with vertical_stack.rs, flex.rs, text.rs. — One of this dimension's main actionable groups (5 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
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).
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).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
8 of 279 classes have LCOM4 above 3.
What to do
- Resolve the 8 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 (8 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
343 test methods: 276 unit, 67 integration, 0 BDD, 0 e2e. The Rust suite contributes 343 `#[test]` function(s) across 70 file(s) declaring at least one; its unit/integration split is Cargo's own — 11 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
D12 · Dependency Hygiene
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.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 625 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.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
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.
D17 · Explicit Debt
441 deducted task-comment markers across 68029 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.
What to do
- Resolve the 415 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 (415 warning-level).
- Resolve the 14 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 (14 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).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 28 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 12 build units (Cargo) flagged as possibly oversized/incoherent.
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).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
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.
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).
D30 · Dependency Vulnerabilities
20 finding(s): 0 critical, 2 high, 18 medium, 0 low.
What to do
- 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 6 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 6 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
D34 · Knowledge Freshness
66 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.
What to do
- Resolve the 60 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 (60 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).
D35 · Change Coupling
Strongest change-coupling: label.rs↔prose.rs 75%; modular_widget.rs↔recorder_widget.rs 71%; label.rs↔prose.rs 70%
What to do
- 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, button.rs. — One of this dimension's main actionable groups (8 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
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.
Frontend & cross-cutting dimensions
AC2 · Forms & labels
AC3 · Page structure
- 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.
AC6 · Visual & motion safety
- `.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.
AC7 · A11y enforcement
- No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 11 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
M1 · Documentation (README)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 10 of 23 project(s) that lack one — worth up to 0.9 pts.
M2 · Architecture documentation
- 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.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
- 778/916 types (85%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Rust: `pub(crate)`, or keep the module private) so internals can change without breaking consumers.
P2 · Observability
- 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.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- 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.
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
X1 · Async correctness
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `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 619 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:619
- `debug!` at line 1091 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:1091
- `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 440 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:440
- `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
What to do
- Interpolated log message defeats structured logging
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 71% | Strong | Solid. |
| Architecture | 97% | Exemplary | Strongest area. |
| Maturity | 78% | Strong | Solid. |
| Readiness | 69% | Strong | Solid. |
| Security | 87% | Strong | Solid. |
| Accessibility | 44% | Weak — gated by AC3, AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 89% | Exemplary | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). 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
- 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 — 64 check(s) not relevant to this codebase
- 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 — ~12412 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 — Naming consistency is measured on C# only; Rust not measured.
- 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+ projects each declaring an entity of their own. 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# and Visual Basic comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- 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.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- 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 — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- 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
- 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.
- 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
- 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)
Critical — 49 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge xilem_web/src/interfaces.rs:1
- Orphaned knowledge xilem_web/src/elements.rs:1
- Orphaned knowledge xilem_core/src/environment.rs:1
- Orphaned knowledge xilem_web/src/modifiers/style.rs:1
- Orphaned knowledge xilem_core/src/views/one_of.rs:1
- Orphaned knowledge xilem_web/src/events.rs:1
- REDACTED
- REDACTED
- <html> without a lang xilem_web/web_examples/counter_custom_element/index.html:2
- REDACTED
- Boundary-crossing change coupling: label.rs ↔ prose.rs masonry/src/widgets/label.rs:1
Serious — 638 finding(s)
- TodoComment xilem_web/web_examples/todomvc/src/main.rs:5
- TodoComment xilem_web/web_examples/todomvc/src/main.rs:60
- TodoComment xilem_web/web_examples/todomvc/src/main.rs:189
- TodoComment xilem_web/web_examples/svgdraw/src/main.rs:86
- TodoComment xilem_web/src/app.rs:102
- TodoComment xilem_web/src/app.rs:153
- TodoComment xilem_web/src/context.rs:157
- TodoComment xilem_web/src/elements.rs:128
- TodoComment xilem_web/src/elements.rs:554
- TodoComment xilem_web/src/events.rs:64
- TodoComment xilem_web/src/events.rs:393
- TodoComment xilem_web/src/events.rs:74
- TodoComment xilem_web/src/events.rs:209
- TodoComment xilem_web/src/interfaces.rs:30
- TodoComment xilem_web/src/interfaces.rs:975
- TodoComment xilem_web/src/lib.rs:52
- TodoComment xilem_masonry/src/lib.rs:28
- TodoComment xilem/src/lib.rs:146
- TodoComment masonry_core/src/lib.rs:74
- TodoComment masonry/src/lib.rs:205
- TodoComment xilem_web/src/lib.rs:231
- TodoComment xilem_web/src/lib.rs:274
- TodoComment xilem_web/src/lib.rs:302
- TodoComment xilem_web/src/lib.rs:303
- TodoComment xilem_web/src/lib.rs:321
- FixmeComment xilem_masonry/src/view/text_input.rs:15
- FixmeComment masonry_testing/src/wrapper_widget.rs:45
- FixmeComment masonry_core/src/core/contexts.rs:2007
- FixmeComment masonry_core/src/core/contexts.rs:2072
- FixmeComment masonry_core/src/core/widget_pod.rs:226
- FixmeComment masonry/src/theme.rs:185
- FixmeComment masonry/src/widgets/checkbox.rs:43
- FixmeComment masonry/src/widgets/radio_button.rs:35
- FixmeComment masonry/src/widgets/image.rs:216
- FixmeComment masonry/src/widgets/text_input.rs:216
- FixmeComment masonry/src/widgets/text_input.rs:244
- FixmeComment masonry/src/layers/selector_menu.rs:167
- FixmeComment masonry/src/layers/selector_menu.rs:222
- FixmeComment masonry/src/layers/selector_menu.rs:373
- HackComment xilem_web/src/elements.rs:345
- HackComment xilem_masonry/src/view/worker.rs:211
- HackComment xilem/examples/variable_clock.rs:44
- HackComment placehero/src/actions.rs:18
- HackComment masonry_winit/src/event_loop_runner.rs:597
- HackComment masonry_core/src/passes/update.rs:649
- HackComment masonry/src/widgets/button.rs:197
- HackComment masonry/src/widgets/selector.rs:247
- HackComment masonry/src/widgets/text_area.rs:868
- HackComment masonry/src/widgets/text_area.rs:951
- HackComment masonry/src/widgets/text_area.rs:1161
- HackComment masonry/src/widgets/text_area.rs:1223
- FileTooLong: src/interfaces.rs xilem_web/src/interfaces.rs
- FileTooLong: core/contexts.rs masonry_core/src/core/contexts.rs
- FileTooLong: widgets/step_input.rs masonry/src/widgets/step_input.rs
- FileTooLong: passes/update.rs masonry_core/src/passes/update.rs
- FileTooLong: src/event_loop_runner.rs masonry_winit/src/event_loop_runner.rs
- FileTooLong: widgets/flex.rs masonry/src/widgets/flex.rs
- FileTooLong: src/elements.rs xilem_web/src/elements.rs
- FileTooLong: widgets/text_area.rs masonry/src/widgets/text_area.rs
- FileTooLong: app/render_root.rs masonry_core/src/app/render_root.rs
- FileTooLong: src/harness.rs masonry_testing/src/harness.rs
- FileTooLong: widgets/grid.rs masonry/src/widgets/grid.rs
- FileTooLong: widgets/portal.rs masonry/src/widgets/portal.rs
- ClassTooLong: StepInput masonry/src/widgets/step_input.rs:76
- ClassTooLong: Flex masonry/src/widgets/flex.rs:50
- ClassTooLong: TextArea masonry/src/widgets/text_area.rs:47
- ClassTooLong: MasonryState masonry_winit/src/event_loop_runner.rs:206
- ClassTooLong: Portal masonry/src/widgets/portal.rs:45
- ClassTooLong: Grid masonry/src/widgets/grid.rs:31
- ClassTooLong: TestHarness masonry_testing/src/harness.rs:146
- ClassTooLong: RenderRoot masonry_core/src/app/render_root.rs:57
- ClassTooLong: Split masonry/src/widgets/split.rs:45
- Change coupling: modular_widget.rs ↔ recorder_widget.rs masonry_testing/src/modular_widget.rs:1
- Change coupling: label.rs ↔ prose.rs masonry/src/widgets/label.rs:1
- Change coupling: button.rs ↔ checkbox.rs masonry/src/widgets/button.rs:1
- Change coupling: harness.rs ↔ modular_widget.rs masonry_testing/src/harness.rs:1
- Change coupling: label.rs ↔ prose.rs xilem_masonry/src/view/label.rs:1
- Change coupling: flex.rs ↔ indexed_stack.rs masonry/src/widgets/flex.rs:1
- Change coupling: prose.rs ↔ variable_label.rs xilem_masonry/src/view/prose.rs:1
- Change coupling: align.rs ↔ button.rs masonry/src/widgets/align.rs:1
- Duplicated block (8 lines × 2) masonry_core/src/passes/event.rs:106
- Duplicated block (8 lines × 2) masonry_core/src/passes/update.rs:889
- Duplicated block (8 lines × 2) xilem_web/src/modifiers/attribute.rs:200
- Duplicated block (8 lines × 2) masonry/src/widgets/image.rs:198
- Duplicated block (8 lines × 2) masonry/src/widgets/checkbox.rs:149
- Duplicated block (8 lines × 2) masonry/src/widgets/checkbox.rs:337
- Duplicated block (8 lines × 2) xilem_masonry/src/view/task.rs:132
- Duplicated block (8 lines × 2) xilem_web/src/pointer.rs:109
- Low cohesion: ColorRectangle (LCOM4 6) masonry/src/doc/color_rectangle.rs:45
- Low cohesion: ModularWidget (LCOM4 6) masonry_testing/src/modular_widget.rs:55
- Low cohesion: Checkbox (LCOM4 5) masonry/src/widgets/checkbox.rs:41
- Low cohesion: Slider (LCOM4 5) masonry/src/widgets/slider.rs:32
- Low cohesion: TextInput (LCOM4 5) masonry/src/widgets/text_input.rs:40
- Low cohesion: Button (LCOM4 4) masonry/src/widgets/button.rs:34
- Low cohesion: ProgressBar (LCOM4 4) masonry/src/widgets/progress_bar.rs:33
- Low cohesion: RadioButton (LCOM4 4) masonry/src/widgets/radio_button.rs:33
- masonry_core::passes::update::run_update_pointer_pass (cognitive 57) masonry_core/src/passes/update.rs:825
- masonry_core::passes::update::run_update_focus_pass (cognitive 41) masonry_core/src/passes/update.rs:619
- masonry_core::passes::paint::paint_widget (cognitive 40) masonry_core/src/passes/paint.rs:71
- masonry_core::core::text::render_text (cognitive 28) masonry_core/src/core/text.rs:45
- masonry_core::passes::update::find_first_focusable (cognitive 25) masonry_core/src/passes/update.rs:554
- masonry_core::passes::layout::run_layout_on (cognitive 20) masonry_core/src/passes/layout.rs:299
- masonry_core::passes::event::run_on_pointer_event_pass (cognitive 19) masonry_core/src/passes/event.rs:149
- MethodTooLong: Flex.layout masonry/src/widgets/flex.rs:922
- MethodTooLong: TextArea.on_text_event masonry/src/widgets/text_area.rs:544
- MethodTooLong: Grid.resolve_track_lengths masonry/src/widgets/grid.rs:320
- MethodTooLong: StepInput.paint_flow masonry/src/widgets/step_input.rs:1595
- MethodTooLong: Flex.measure masonry/src/widgets/flex.rs:695
- MethodTooLong: OneOf.rebuild xilem_core/src/views/one_of.rs:308
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (5 lines × 2) masonry/src/widgets/slider.rs:161
- Duplicated block (5 lines × 2) masonry/src/widgets/text_input.rs:233
- Duplicated block (5 lines × 2) xilem_masonry/src/view/badge.rs:82
- Duplicated block (5 lines × 2) xilem_masonry/src/view/badge.rs:104
- Duplicated block (5 lines × 2) masonry/src/widgets/grid.rs:268
- Duplicated block (5 lines × 2) xilem_web/web_examples/open_and_save_file/src/main.rs:127
- FunctionTooLong: masonry::theme::default_property_set masonry/src/theme.rs:58
- FunctionTooLong: masonry_core::passes::update::run_update_pointer_pass masonry_core/src/passes/update.rs:825
- FunctionTooLong: masonry_core::passes::paint::paint_widget masonry_core/src/passes/paint.rs:71
- FunctionTooLong: placehero::html_content::status_html_to_plaintext placehero/src/html_content.rs:30
- FunctionTooLong: masonry_core::passes::layout::run_layout_on masonry_core/src/passes/layout.rs:299
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (9 lines × 2) masonry/src/doc/vertical_stack.rs:136
- Duplicated block (9 lines × 2) masonry/src/widgets/flex.rs:376
- Duplicated block (9 lines × 2) masonry_core/src/core/text.rs:79
- Duplicated block (9 lines × 2) xilem_masonry/src/view/prose.rs:142
- Duplicated block (9 lines × 2) placehero/src/components/media.rs:95
- masonry_core::passes::update::run_update_pointer_pass (cyclomatic 35) masonry_core/src/passes/update.rs:825
- masonry_core::passes::update::run_update_focus_pass (cyclomatic 27) masonry_core/src/passes/update.rs:619
- masonry_core::passes::paint::paint_widget (cyclomatic 26) masonry_core/src/passes/paint.rs:71
- masonry_core::passes::layout::run_layout_on (cyclomatic 17) masonry_core/src/passes/layout.rs:299
- StepInput::on_text_event (cognitive 49) masonry/src/widgets/step_input.rs:995
- StepInput::on_pointer_event (cognitive 49) masonry/src/widgets/step_input.rs:1085
- StepInput::paint_flow (cognitive 28) masonry/src/widgets/step_input.rs:1595
- StepInput::update_ticks (cognitive 25) masonry/src/widgets/step_input.rs:778
- TooManyMethods: TestHarness masonry_testing/src/harness.rs:146
- TooManyMethods: RenderRoot masonry_core/src/app/render_root.rs:57
- TooManyMethods: Split masonry/src/widgets/split.rs:45
- TooManyMethods: StepInput masonry/src/widgets/step_input.rs:76
- Duplicated block (6 lines × 2) masonry/src/widgets/text_input.rs:218
- Duplicated block (6 lines × 2) masonry/src/widgets/text_input.rs:225
- Duplicated block (6 lines × 2) xilem_masonry/src/view/checkbox.rs:144
- Duplicated block (6 lines × 2) xilem_masonry/src/view/badged.rs:162
- Duplicated block (13 lines × 2) masonry/src/widgets/text_input.rs:334
- Duplicated block (13 lines × 2) xilem_masonry/src/view/flex.rs:356
- Duplicated block (13 lines × 2) masonry_testing/src/assert_any.rs:42
- Duplicated block (12 lines × 2) masonry/src/widgets/divider.rs:212
- Duplicated block (12 lines × 2) masonry/src/widgets/grid.rs:212
- Duplicated block (12 lines × 2) xilem_masonry/src/view/virtual_scroll.rs:323
- Duplicated block (5 lines × 3) masonry/src/widgets/passthrough.rs:101
- Duplicated block (5 lines × 3) masonry_core/src/core/property_stack.rs:29
- Duplicated block (5 lines × 3) xilem_masonry/src/view/flex.rs:610
- Page without a main landmark xilem_web/web_examples/counter_custom_element/index.html:2
- Page without a main landmark REDACTED:2
- Animation without a prefers-reduced-motion guard xilem_web/web_examples/svgdraw/index.html:26
- Animation without a prefers-reduced-motion guard REDACTED:135
- Grid::resolve_track_lengths (cyclomatic 33) masonry/src/widgets/grid.rs:320
- Grid::assign_cell_to_auto_placed_children (cyclomatic 24) masonry/src/widgets/grid.rs:153
- MasonryState::handle_signals (cyclomatic 29) masonry_winit/src/event_loop_runner.rs:1026
- MasonryState::handle_window_event (cyclomatic 21) masonry_winit/src/event_loop_runner.rs:808
- Flex::layout (cyclomatic 25) masonry/src/widgets/flex.rs:922
- Flex::measure (cyclomatic 17) masonry/src/widgets/flex.rs:695
- StepInput::on_pointer_event (cyclomatic 23) masonry/src/widgets/step_input.rs:1085
- StepInput::on_text_event (cyclomatic 22) masonry/src/widgets/step_input.rs:995
- Grid::assign_cell_to_auto_placed_children (cognitive 57) masonry/src/widgets/grid.rs:153
- Grid::resolve_track_lengths (cognitive 55) masonry/src/widgets/grid.rs:320
- Flex::layout (cognitive 43) masonry/src/widgets/flex.rs:922
- Flex::measure (cognitive 40) masonry/src/widgets/flex.rs:695
- MasonryState::handle_window_event (cognitive 27) masonry_winit/src/event_loop_runner.rs:808
- MasonryState::handle_signals (cognitive 17) masonry_winit/src/event_loop_runner.rs:1026
- Portal::on_access_event (cognitive 16) masonry/src/widgets/portal.rs:580
- Portal::accessibility (cognitive 16) masonry/src/widgets/portal.rs:852
- TooManyFunctions: xilem_web::elements::html xilem_web/src/elements.rs:557
- TooManyFunctions: xilem_web::elements::svg xilem_web/src/elements.rs:716
- TooManyFields: WidgetState masonry_core/src/core/widget_state.rs:71
- TooManyFields: RenderRootState masonry_core/src/app/render_root.rs:72
- Duplicated block (14 lines × 2) masonry_core/src/core/properties_mut.rs:34
- Duplicated block (14 lines × 2) xilem_masonry/src/view/task.rs:38
- Duplicated block (11 lines × 3) masonry/src/widgets/divider.rs:210
- Duplicated block (11 lines × 3) xilem_masonry/src/view/flex.rs:399
- Duplicated block (11 lines × 2) masonry/src/widgets/split.rs:506
- Duplicated block (11 lines × 2) masonry/src/widgets/selector.rs:209
- Duplicated block (10 lines × 2) masonry/src/widgets/portal.rs:289
- Duplicated block (10 lines × 2) xilem_web/src/modifiers/attribute.rs:183
- Duplicated block (9 lines × 4) masonry/src/theme.rs:85
- Duplicated block (9 lines × 4) xilem_masonry/src/view/flex.rs:389
- Duplicated block (9 lines × 3) masonry/src/theme.rs:86
- Duplicated block (9 lines × 3) xilem_masonry/src/view/flex.rs:343
- Duplicated block (7 lines × 2) xilem_core/src/views/one_of.rs:291
- Duplicated block (7 lines × 2) masonry/src/widgets/image.rs:157
- Duplicated block (6 lines × 6) masonry/src/widgets/checkbox.rs:248
- Duplicated block (6 lines × 6) masonry/src/layers/tooltip.rs:36
- Focus outline removed in CSS without a :focus replacement REDACTED:187
- Accessibility enforcement below the top rung
- TextArea::on_text_event (cyclomatic 61) masonry/src/widgets/text_area.rs:544
- placehero::html_content::status_html_to_plaintext (cyclomatic 33) placehero/src/html_content.rs:30
- linebender_include_doc_path::parsing::parse_lit_str_cooked (cyclomatic 21) include_doc_path/src/parsing.rs:65
- TextArea::on_text_event (cognitive 109) masonry/src/widgets/text_area.rs:544
- placehero::html_content::status_html_to_plaintext (cognitive 80) placehero/src/html_content.rs:30
- VirtualScroll::rebuild (cognitive 26) xilem_masonry/src/view/virtual_scroll.rs:248
- Slider::on_text_event (cognitive 24) masonry/src/widgets/slider.rs:179
- linebender_include_doc_path::parsing::parse_lit_str_cooked (cognitive 24) include_doc_path/src/parsing.rs:65
- TestHarness::check_render_snapshot (cognitive 18) masonry_testing/src/harness.rs:1106
- MemoizedAwait::rebuild (cognitive 17) xilem_web/src/concurrent/memoized_await.rs:195
- REDACTED
- REDACTED
- Edited copy of a member (38 corresponding lines) xilem_core/src/views/one_of.rs:258
- Members sharing a duplicated core (11 members, 50+ identical tokens) masonry_core/src/passes/accessibility.rs:23
- Members sharing a duplicated core (6 members, 50+ identical tokens) masonry/src/widgets/checkbox.rs:247
- Members sharing a duplicated core (5 members, 50+ identical tokens) masonry/src/layers/tooltip.rs:111
- Duplicated block (31 lines × 2) masonry/src/widgets/checkbox.rs:192
- Duplicated block (29 lines × 2) masonry/src/widgets/checkbox.rs:252
- Duplicated block (26 lines × 2) masonry_core/src/passes/update.rs:68
- Duplicated block (21 lines × 2) xilem_web/src/modifiers/class.rs:269
- Duplicated block (19–20 lines × 2) masonry/src/doc/vertical_stack.rs:99
- Duplicated block (17 lines × 2) masonry/src/widgets/button.rs:183
- Duplicated block (16 lines × 2) masonry/src/widgets/checkbox.rs:225
- Duplicated block (15 lines × 2) masonry/src/theme.rs:85
- Duplicated block (11–15 lines × 2) masonry_core/src/passes/layout.rs:139
- Duplicated block (14 lines × 4) masonry_core/src/passes/anim.rs:37
- Duplicated block (7–8 lines × 3) masonry/src/widgets/checkbox.rs:249
- Duplicated block (6–8 lines × 3) masonry_core/src/passes/mutate.rs:17
- Duplicated block (7–8 lines × 2) xilem_web/src/modifiers/attribute.rs:156
- Duplicated block (7 lines × 5) masonry/src/layers/tooltip.rs:113
- Duplicated block (7 lines × 3) masonry_core/src/passes/update.rs:310
- Duplicated block (6 lines × 8) masonry_core/src/passes/accessibility.rs:24
- Duplicated block (5 lines × 9) masonry_core/src/passes/accessibility.rs:25
- Duplicated block (12 lines × 4) masonry/src/layers/tooltip.rs:98
- Duplicated block (5 lines × 4) xilem_masonry/src/view/flex.rs:255
- Duplicated block (8 lines × 4) xilem_masonry/src/view/flex.rs:267
- Duplicated block (11 lines × 4) xilem_masonry/src/view/flex.rs:322
- Duplicated block (12 lines × 3) masonry_core/src/core/contexts.rs:875
- Off the main sequence: masonry_imaging
Minor — 114 finding(s)
- Orphaned file xilem_web/src/modifiers/overwrite.rs:1
- Orphaned file xilem_web/src/modifiers/class.rs:1
- Orphaned file xilem_web/src/vecmap.rs:1
- Orphaned file xilem_web/src/modifiers/attribute.rs:1
- Orphaned file xilem_core/src/views/any_view.rs:1
- Orphaned file xilem_masonry/src/view/divider.rs:1
- Orphaned file placehero/src/login_flow/login_model.rs:1
- Orphaned file xilem_web/src/svg/common_attrs.rs:1
- Orphaned file xilem_masonry/src/view/badged.rs:1
- Orphaned file xilem_masonry/src/view/indexed_stack.rs:1
- Orphaned file xilem_web/src/concurrent/memoized_await.rs:1
- Orphaned file placehero/src/html_content.rs:1
- Orphaned file xilem_web/src/context.rs:1
- Orphaned file xilem_core/src/views/memoize.rs:1
- Orphaned file xilem_web/src/svg/kurbo_shape.rs:1
- Orphaned file xilem_masonry/src/view/worker.rs:1
- Orphaned file xilem_web/src/one_of.rs:1
- Orphaned file xilem_web/web_examples/fetch/src/main.rs:1
- Orphaned file xilem_web/src/after_update.rs:1
- Orphaned file xilem_web/web_examples/svgdraw/src/main.rs:1
- Orphaned file xilem_web/web_examples/todomvc/src/main.rs:1
- Orphaned file xilem_masonry/src/view/badge.rs:1
- Orphaned file xilem_core/src/message_context.rs:1
- Orphaned file xilem_core/src/message.rs:1
- Orphaned file xilem_web/src/pointer.rs:1
- Interpolated log message defeats structured logging xilem_masonry/src/view/button.rs:247
- Interpolated log message defeats structured logging xilem_masonry/src/view/canvas.rs:120
- Interpolated log message defeats structured logging xilem_masonry/src/view/checkbox.rs:178
- Interpolated log message defeats structured logging xilem_masonry/src/view/radio_button.rs:138
- Interpolated log message defeats structured logging xilem_masonry/src/view/resize_observer.rs:169
- Interpolated log message defeats structured logging xilem_masonry/src/view/slider.rs:128
- Interpolated log message defeats structured logging xilem_masonry/src/view/split.rs:309
- Interpolated log message defeats structured logging xilem_masonry/src/view/switch.rs:119
- Interpolated log message defeats structured logging xilem_masonry/src/view/virtual_scroll.rs:418
- Interpolated log message defeats structured logging xilem_core/src/environment.rs:582
- Interpolated log message defeats structured logging xilem/src/driver.rs:318
- Interpolated log message defeats structured logging placehero/src/avatars.rs:126
- Interpolated log message defeats structured logging placehero/src/html_content.rs:44
- Interpolated log message defeats structured logging placehero/src/html_content.rs:59
- Interpolated log message defeats structured logging placehero/src/html_content.rs:183
- Interpolated log message defeats structured logging placehero/src/lib.rs:377
- Interpolated log message defeats structured logging placehero/src/components/media.rs:79
- Interpolated log message defeats structured logging masonry_winit/src/event_loop_runner.rs:738
- Interpolated log message defeats structured logging masonry_winit/src/event_loop_runner.rs:763
- Interpolated log message defeats structured logging masonry_winit/src/event_loop_runner.rs:771
- Interpolated log message defeats structured logging masonry_winit/src/event_loop_runner.rs:824
- Interpolated log message defeats structured logging masonry_winit/src/event_loop_runner.rs:1050
- Interpolated log message defeats structured logging masonry_winit/src/event_loop_runner.rs:1125
- Interpolated log message defeats structured logging masonry_testing/src/harness.rs:619
- Interpolated log message defeats structured logging masonry_testing/src/harness.rs:1091
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- REDACTED
- REDACTED
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- Further orphaned files (smaller)
- REDACTED
- No ADRs
- Large public API surface
- Logging is not universal
- Changelog looks stale/thin
- Duplicated predicate masonry/src/widgets/checkbox.rs:256
Minor — 18 finding(s)
- Outdated: anyhow
- Outdated: anymap3
- Outdated: console_log
- Outdated: futures-channel
- Outdated: futures-util
- Outdated: hashbrown
- Outdated: log
- Outdated: megalodon
- Outdated: proc-macro2
- Outdated: quote
- Outdated: serde
- Outdated: serde_json
- Outdated: smallvec
- Outdated: time
- Outdated: tokio
- Outdated: wasm-bindgen
- Outdated: wasm-bindgen-futures
- Outdated: web-sys
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-55bac2914fd444fc8eaf8e6b636dc975/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-55bac2914fd444fc8eaf8e6b636dc975/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 41 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 20 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | 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. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | 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. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | 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. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | 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. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | 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. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |