Executive summary
rust-windowing/winit falls short of our standard for a preview release, in part because the documentation refers to links that don't exist. It scores 64 out of 100 and is rated Adequate, and 23 of its 35 critical findings are security problems in the build pipeline and in its automatic dependency updates.
Maturity, at 46, is the weakest lens and counts most in the score. The best first step is bringing the documentation in line with the code, worth about 12 points. Recording design decisions comes next, worth about 7 points. Raising Maturity to 62 would lift the score to about 71.
Twenty-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One automatic update takes new releases before a bad one can be spotted, and ten sets of files in separate parts keep changing together, which points to hidden dependencies. Pinning each tool to an exact version, setting a waiting period for automatic updates and making the hidden dependencies explicit would close these risks. The two parts of the code nobody has worked on for a long time need someone to learn and document them before anyone changes them.
The product code is 62,704 lines, about €75,000 to rebuild.
If Maturity rose from 46 to 62, the lowest score rated Strong, the score would rise from 64 to about 71.
New since the last survey: 29 findings
- Cognitive Complexity · SourceDataObjectData::GetData (cognitive 16) winit-win32/src/data_transfer.rs
- God Classes · FileTooLong: src/data_transfer.rs winit-win32/src/data_transfer.rs
- God Classes · FileTooLong: src/data_transfer.rs winit-wayland/src/data_transfer.rs
- God Classes · FileTooLong: src/data_transfer.rs winit-x11/src/data_transfer.rs
- God Classes · MethodTooLong: EventProcessor.process_xevent winit-x11/src/event_processor.rs
- Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) winit-win32/src/window.rs
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) winit-android/src/event_loop.rs
- Code Duplication · Duplicated block (11 lines × 2) winit-wayland/src/event_loop/mod.rs
- Code Duplication · Duplicated block (9 lines × 2) winit-wayland/src/data_transfer.rs
- Code Duplication · Duplicated block (7 lines × 3) winit-appkit/src/data_transfer.rs
- Code Duplication · Duplicated block (6 lines × 2) winit-appkit/src/data_transfer.rs
- Code Duplication · Duplicated block (10 lines × 2) winit-wayland/src/data_transfer.rs
- Churn × Complexity Hotspots · Hotspot: winit-x11/src/window.rs winit-x11/src/window.rs
- Explicit Debt · TodoComment winit-x11/src/data_transfer.rs
- Explicit Debt · TodoComment winit-x11/src/data_transfer.rs
- Explicit Debt · TodoComment winit-x11/src/data_transfer.rs
- Explicit Debt · TodoComment winit-x11/src/event_loop.rs
- Explicit Debt · TodoComment winit-x11/src/event_processor.rs
- Explicit Debt · TodoComment winit-x11/src/event_processor.rs
- Explicit Debt · TodoComment winit-x11/src/xdisplay.rs
- Explicit Debt · TodoComment winit-win32/src/data_transfer.rs
- Explicit Debt · TodoComment winit-win32/src/data_transfer.rs
- Explicit Debt · TodoComment winit-wayland/src/data_transfer.rs
- Explicit Debt · TodoComment winit-wayland/src/data_transfer.rs
- Explicit Debt · HackComment winit-wayland/src/data_transfer.rs
- Explicit Debt · TodoComment winit-appkit/src/data_transfer.rs
- Knowledge Freshness · Orphaned knowledge winit-win32/src/keyboard.rs
- Knowledge Freshness · Orphaned knowledge winit-web/src/monitor.rs
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 21 findings
- Cognitive Complexity · SourceDataObjectData::GetData (cognitive 16) winit-win32/src/dnd.rs
- God Classes · FileTooLong: src/dnd.rs winit-win32/src/dnd.rs
- God Classes · FileTooLong: src/dnd.rs winit-wayland/src/dnd.rs
- Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) winit-win32/src/window.rs
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) winit-android/src/event_loop.rs
- Code Duplication · Duplicated block (14 lines × 2) winit-wayland/src/event_loop/mod.rs
- Code Duplication · Duplicated block (9 lines × 2) winit-wayland/src/dnd.rs
- Code Duplication · Duplicated block (9 lines × 2) winit-wayland/src/dnd.rs
- Code Duplication · Duplicated block (8 lines × 3) winit-appkit/src/dnd.rs
- Cohesion (LCOM4) · Low cohesion: WinitState (LCOM4 4) winit-wayland/src/state.rs
- Explicit Debt · TodoComment winit-appkit/src/dnd.rs
- Explicit Debt · TodoComment winit-appkit/src/dnd.rs
- Explicit Debt · TodoComment winit-x11/src/event_processor.rs
- Explicit Debt · TodoComment winit-wayland/src/dnd.rs
- Explicit Debt · TodoComment winit-wayland/src/dnd.rs
- Explicit Debt · HackComment winit-wayland/src/event_loop/mod.rs
- Explicit Debt · TodoComment winit-win32/src/dnd.rs
- Explicit Debt · TodoComment winit-win32/src/dnd.rs
- Explicit Debt · TodoComment winit-x11/src/dnd.rs
- Change Coupling · Boundary-crossing change coupling: icon.rs ↔ mod.rs winit-win32/src/icon.rs
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €75,000 · Estimate
| Cost to rebuild | €25,000 to €130,000, for 415 to 1,316 hours of work, about 0.5 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 64. 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: 62,704 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 dpi | 2 winit_common.xkb.state | 3 winit_core.keyboard | 4 winit_web.main_thread | 5 winit_core.data_transfer | 6 winit_core.event | 7 winit_core.monitor | 8 winit_web.async.dispatcher | 9 winit_appkit.monitor | 10 winit_common.xkb | 11 winit_core.cursor | 12 winit_core.icon | 13 winit_core.window | 14 winit_core.event_loop | 15 winit_android.event_loop | 16 winit_appkit.data_transfer | 17 winit.platform_impl.linux | 18 winit_appkit.app_state | 19 winit_uikit.window | 20 winit_wayland.state | 21 winit_web.web_sys.canvas | 22 winit_appkit.event_loop | 23 winit_appkit.window_delegate | 24 winit_orbital.event_loop | 25 winit_wayland.window.state | 26 winit_web.cursor | 27 winit_web | 28 winit_win32.window_state | 29 winit.event_loop | 30 winit_web.monitor | 31 winit_win32.event_loop | 32 winit_wayland.event_loop | 33 winit_web.window | 34 winit_x11.xdisplay | 35 winit_web.event_loop.runner | 36 winit_win32.event_loop.runner | 37 winit_x11.event_loop | 38 winit_win32.data_transfer | 39 winit_win32.window | 40 winit_x11.window |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 dpi | ||||||||||||||||||||||||||||||||||||||||
| 2 winit_common.xkb.state | ||||||||||||||||||||||||||||||||||||||||
| 3 winit_core.keyboard | ||||||||||||||||||||||||||||||||||||||||
| 4 winit_web.main_thread | ||||||||||||||||||||||||||||||||||||||||
| 5 winit_core.data_transfer | 3 | |||||||||||||||||||||||||||||||||||||||
| 6 winit_core.event | 1 | 1 | 5 | |||||||||||||||||||||||||||||||||||||
| 7 winit_core.monitor | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 8 winit_web.async.dispatcher | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 winit_appkit.monitor | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 10 winit_common.xkb | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 11 winit_core.cursor | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 12 winit_core.icon | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 winit_core.window | 10 | 2 | 2 | 1 | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||
| 14 winit_core.event_loop | 1 | 1 | 1 | 2 | 1 | 3 | 4 | |||||||||||||||||||||||||||||||||
| 15 winit_android.event_loop | 6 | 2 | 1 | 3 | 1 | 14 | 6 | 1 | ||||||||||||||||||||||||||||||||
| 16 winit_appkit.data_transfer | 1 | 9 | 3 | 3 | ||||||||||||||||||||||||||||||||||||
| 17 winit.platform_impl.linux | 1 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 18 winit_appkit.app_state | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 19 winit_uikit.window | 10 | 1 | 2 | 1 | 2 | 2 | 22 | 1 | ||||||||||||||||||||||||||||||||
| 20 winit_wayland.state | 2 | 1 | 2 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 21 winit_web.web_sys.canvas | 3 | 1 | 1 | 2 | 3 | 1 | ||||||||||||||||||||||||||||||||||
| 22 winit_appkit.event_loop | 1 | 1 | 1 | 2 | 3 | 6 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||
| 23 winit_appkit.window_delegate | 6 | 2 | 1 | 2 | 2 | 1 | 1 | 16 | 3 | |||||||||||||||||||||||||||||||
| 24 winit_orbital.event_loop | 2 | 3 | 1 | 2 | 3 | 6 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 25 winit_wayland.window.state | 5 | 1 | 1 | 1 | 9 | 2 | 2 | |||||||||||||||||||||||||||||||||
| 26 winit_web.cursor | 5 | 1 | 4 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 27 winit_web | 1 | 7 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 28 winit_win32.window_state | 4 | 1 | 1 | 1 | 5 | 1 | ||||||||||||||||||||||||||||||||||
| 29 winit.event_loop | 1 | 3 | 2 | 1 | 5 | |||||||||||||||||||||||||||||||||||
| 30 winit_web.monitor | 3 | 3 | 2 | 1 | 2 | 3 | 2 | 1 | 1 | 6 | 3 | |||||||||||||||||||||||||||||
| 31 winit_win32.event_loop | 1 | 1 | 5 | 2 | 3 | 8 | 1 | 2 | 1 | 5 | 1 | |||||||||||||||||||||||||||||
| 32 winit_wayland.event_loop | 1 | 1 | 2 | 4 | 6 | 3 | 3 | 1 | ||||||||||||||||||||||||||||||||
| 33 winit_web.window | 5 | 1 | 1 | 1 | 1 | 12 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||
| 34 winit_x11.xdisplay | 1 | 3 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 35 winit_web.event_loop.runner | 2 | 1 | 1 | 1 | 4 | 6 | 1 | 4 | 2 | 2 | ||||||||||||||||||||||||||||||
| 36 winit_win32.event_loop.runner | 3 | 2 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 37 winit_x11.event_loop | 1 | 3 | 1 | 2 | 3 | 6 | 2 | 1 | 3 | |||||||||||||||||||||||||||||||
| 38 winit_win32.data_transfer | 11 | 1 | 2 | 3 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 39 winit_win32.window | 8 | 1 | 1 | 1 | 15 | 2 | 2 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||
| 40 winit_x11.window | 13 | 3 | 2 | 2 | 22 | 3 | 1 | 1 |
5→4 winit_core.data_transfer uses winit_web.main_thread✕
- Connections
- 3 pairs of types, where a type in winit_core.data_transfer uses a type in winit_web.main_thread.
- The types involved
winit_core.data_transfer.DataTransfer→winit_web.main_thread.Anywinit_core.data_transfer.TransferType→winit_web.main_thread.Anywinit_core.data_transfer.TypedData→winit_web.main_thread.Any
- Direction
- winit_core.data_transfer uses winit_web.main_thread, so a change to winit_web.main_thread can break winit_core.data_transfer, while a change to winit_core.data_transfer can't break winit_web.main_thread.
- Position
- Below the diagonal: winit_core.data_transfer uses a module listed above it, which is the healthy direction.
6→1 winit_core.event uses dpi✕
- Connections
- 1 pair of types, where a type in winit_core.event uses a type in dpi.
- The types involved
winit_core.event.SurfaceSizeWriter→dpi.PhysicalSize
- Direction
- winit_core.event uses dpi, so a change to dpi can break winit_core.event, while a change to winit_core.event can't break dpi.
- Position
- Below the diagonal: winit_core.event uses a module listed above it, which is the healthy direction.
6→2 winit_core.event uses winit_common.xkb.state✕
- Connections
- 1 pair of types, where a type in winit_core.event uses a type in winit_common.xkb.state.
- The types involved
winit_core.event.Modifiers→winit_common.xkb.state.ModifiersState
- Direction
- winit_core.event uses winit_common.xkb.state, so a change to winit_common.xkb.state can break winit_core.event, while a change to winit_core.event can't break winit_common.xkb.state.
- Position
- Below the diagonal: winit_core.event uses a module listed above it, which is the healthy direction.
6→3 winit_core.event uses winit_core.keyboard✕
- Connections
- 5 pairs of types, where a type in winit_core.event uses a type in winit_core.keyboard.
- The types involved
winit_core.event.KeyEvent→winit_core.keyboard.Keywinit_core.event.KeyEvent→winit_core.keyboard.PhysicalKeywinit_core.event.Modifiers→winit_core.keyboard.ModifiersKeyStatewinit_core.event.Modifiers→winit_core.keyboard.ModifiersKeyswinit_core.event.RawKeyEvent→winit_core.keyboard.PhysicalKey
- Direction
- winit_core.event uses winit_core.keyboard, so a change to winit_core.keyboard can break winit_core.event, while a change to winit_core.event can't break winit_core.keyboard.
- Position
- Below the diagonal: winit_core.event uses a module listed above it, which is the healthy direction.
7→1 winit_core.monitor uses dpi✕
- Connections
- 2 pairs of types, where a type in winit_core.monitor uses a type in dpi.
- The types involved
winit_core.monitor.MonitorHandleProvider→dpi.PhysicalPositionwinit_core.monitor.VideoMode→dpi.PhysicalSize
- Direction
- winit_core.monitor uses dpi, so a change to dpi can break winit_core.monitor, while a change to winit_core.monitor can't break dpi.
- Position
- Below the diagonal: winit_core.monitor uses a module listed above it, which is the healthy direction.
7→4 winit_core.monitor uses winit_web.main_thread✕
- Connections
- 1 pair of types, where a type in winit_core.monitor uses a type in winit_web.main_thread.
- The types involved
winit_core.monitor.MonitorHandleProvider→winit_web.main_thread.Any
- Direction
- winit_core.monitor uses winit_web.main_thread, so a change to winit_web.main_thread can break winit_core.monitor, while a change to winit_core.monitor can't break winit_web.main_thread.
- Position
- Below the diagonal: winit_core.monitor uses a module listed above it, which is the healthy direction.
7→9 winit_core.monitor uses winit_appkit.monitor part of a loop✕
- Connections
- 1 pair of types, where a type in winit_core.monitor uses a type in winit_appkit.monitor.
- The types involved
winit_core.monitor.VideoMode→winit_appkit.monitor.VideoModeHandle
- Direction
- winit_core.monitor uses winit_appkit.monitor, so a change to winit_appkit.monitor can break winit_core.monitor, while a change to winit_core.monitor can't break winit_appkit.monitor.
- 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→4 winit_web.async.dispatcher uses winit_web.main_thread✕
- Connections
- 2 pairs of types, where a type in winit_web.async.dispatcher uses a type in winit_web.main_thread.
- The types involved
winit_web.async.dispatcher.DispatchRunner→winit_web.main_thread.MainThreadMarkerwinit_web.async.dispatcher.Dispatcher→winit_web.main_thread.MainThreadMarker
- Direction
- winit_web.async.dispatcher uses winit_web.main_thread, so a change to winit_web.main_thread can break winit_web.async.dispatcher, while a change to winit_web.async.dispatcher can't break winit_web.main_thread.
- Position
- Below the diagonal: winit_web.async.dispatcher uses a module listed above it, which is the healthy direction.
9→1 winit_appkit.monitor uses dpi✕
- Connections
- 1 pair of types, where a type in winit_appkit.monitor uses a type in dpi.
- The types involved
winit_appkit.monitor.MonitorHandle→dpi.PhysicalPosition
- Direction
- winit_appkit.monitor uses dpi, so a change to dpi can break winit_appkit.monitor, while a change to winit_appkit.monitor can't break dpi.
- Position
- Below the diagonal: winit_appkit.monitor uses a module listed above it, which is the healthy direction.
9→4 winit_appkit.monitor uses winit_web.main_thread✕
- Connections
- 1 pair of types, where a type in winit_appkit.monitor uses a type in winit_web.main_thread.
- The types involved
winit_appkit.monitor.MonitorHandle→winit_web.main_thread.MainThreadMarker
- Direction
- winit_appkit.monitor uses winit_web.main_thread, so a change to winit_web.main_thread can break winit_appkit.monitor, while a change to winit_appkit.monitor can't break winit_web.main_thread.
- Position
- Below the diagonal: winit_appkit.monitor uses a module listed above it, which is the healthy direction.
9→7 winit_appkit.monitor uses winit_core.monitor✕
- Connections
- 3 pairs of types, where a type in winit_appkit.monitor uses a type in winit_core.monitor.
- The types involved
winit_appkit.monitor.MonitorHandle→winit_core.monitor.MonitorHandleProviderwinit_appkit.monitor.MonitorHandle→winit_core.monitor.VideoModewinit_appkit.monitor.VideoModeHandle→winit_core.monitor.VideoMode
- Direction
- winit_appkit.monitor uses winit_core.monitor, so a change to winit_core.monitor can break winit_appkit.monitor, while a change to winit_appkit.monitor can't break winit_core.monitor.
- Position
- Below the diagonal: winit_appkit.monitor uses a module listed above it, which is the healthy direction.
10→2 winit_common.xkb uses winit_common.xkb.state✕
- Connections
- 2 pairs of types, where a type in winit_common.xkb uses a type in winit_common.xkb.state.
- The types involved
winit_common.xkb.Context→winit_common.xkb.state.XkbStatewinit_common.xkb.KeyContext→winit_common.xkb.state.XkbState
- Direction
- winit_common.xkb uses winit_common.xkb.state, so a change to winit_common.xkb.state can break winit_common.xkb, while a change to winit_common.xkb can't break winit_common.xkb.state.
- Position
- Below the diagonal: winit_common.xkb uses a module listed above it, which is the healthy direction.
10→6 winit_common.xkb uses winit_core.event✕
- Connections
- 2 pairs of types, where a type in winit_common.xkb uses a type in winit_core.event.
- The types involved
winit_common.xkb.KeyContext→winit_core.event.ElementStatewinit_common.xkb.KeyContext→winit_core.event.KeyEvent
- Direction
- winit_common.xkb uses winit_core.event, so a change to winit_core.event can break winit_common.xkb, while a change to winit_common.xkb can't break winit_core.event.
- Position
- Below the diagonal: winit_common.xkb uses a module listed above it, which is the healthy direction.
11→4 winit_core.cursor uses winit_web.main_thread✕
- Connections
- 1 pair of types, where a type in winit_core.cursor uses a type in winit_web.main_thread.
- The types involved
winit_core.cursor.CustomCursorProvider→winit_web.main_thread.Any
- Direction
- winit_core.cursor uses winit_web.main_thread, so a change to winit_web.main_thread can break winit_core.cursor, while a change to winit_core.cursor can't break winit_web.main_thread.
- Position
- Below the diagonal: winit_core.cursor uses a module listed above it, which is the healthy direction.
11→10 winit_core.cursor uses winit_common.xkb✕
- Connections
- 2 pairs of types, where a type in winit_core.cursor uses a type in winit_common.xkb.
- The types involved
winit_core.cursor.BadAnimation→winit_common.xkb.Errorwinit_core.cursor.BadImage→winit_common.xkb.Error
- Direction
- winit_core.cursor uses winit_common.xkb, so a change to winit_common.xkb can break winit_core.cursor, while a change to winit_core.cursor can't break winit_common.xkb.
- Position
- Below the diagonal: winit_core.cursor uses a module listed above it, which is the healthy direction.
12→4 winit_core.icon uses winit_web.main_thread✕
- Connections
- 1 pair of types, where a type in winit_core.icon uses a type in winit_web.main_thread.
- The types involved
winit_core.icon.IconProvider→winit_web.main_thread.Any
- Direction
- winit_core.icon uses winit_web.main_thread, so a change to winit_web.main_thread can break winit_core.icon, while a change to winit_core.icon can't break winit_web.main_thread.
- Position
- Below the diagonal: winit_core.icon uses a module listed above it, which is the healthy direction.
12→10 winit_core.icon uses winit_common.xkb✕
- Connections
- 1 pair of types, where a type in winit_core.icon uses a type in winit_common.xkb.
- The types involved
winit_core.icon.BadIcon→winit_common.xkb.Error
- Direction
- winit_core.icon uses winit_common.xkb, so a change to winit_common.xkb can break winit_core.icon, while a change to winit_core.icon can't break winit_common.xkb.
- Position
- Below the diagonal: winit_core.icon uses a module listed above it, which is the healthy direction.
13→1 winit_core.window uses dpi✕
- Connections
- 10 pairs of types, where a type in winit_core.window uses a type in dpi.
- The types involved
winit_core.window.ImeRequestData→dpi.Positionwinit_core.window.ImeRequestData→dpi.Sizewinit_core.window.Window→dpi.PhysicalInsetswinit_core.window.Window→dpi.PhysicalPositionwinit_core.window.Window→dpi.PhysicalSizewinit_core.window.Window→dpi.Positionwinit_core.window.Window→dpi.Sizewinit_core.window.WindowAttributes→dpi.Positionwinit_core.window.WindowAttributes→dpi.Sizewinit_core.window.WindowPositioner→dpi.Position
- Direction
- winit_core.window uses dpi, so a change to dpi can break winit_core.window, while a change to winit_core.window can't break dpi.
- Position
- Below the diagonal: winit_core.window uses a module listed above it, which is the healthy direction.
13→4 winit_core.window uses winit_web.main_thread✕
- Connections
- 2 pairs of types, where a type in winit_core.window uses a type in winit_web.main_thread.
- The types involved
winit_core.window.PlatformWindowAttributes→winit_web.main_thread.Anywinit_core.window.Window→winit_web.main_thread.Any
- Direction
- winit_core.window uses winit_web.main_thread, so a change to winit_web.main_thread can break winit_core.window, while a change to winit_core.window can't break winit_web.main_thread.
- Position
- Below the diagonal: winit_core.window uses a module listed above it, which is the healthy direction.
13→7 winit_core.window uses winit_core.monitor✕
- Connections
- 2 pairs of types, where a type in winit_core.window uses a type in winit_core.monitor.
- The types involved
winit_core.window.Window→winit_core.monitor.Fullscreenwinit_core.window.WindowAttributes→winit_core.monitor.Fullscreen
- Direction
- winit_core.window uses winit_core.monitor, so a change to winit_core.monitor can break winit_core.window, while a change to winit_core.window can't break winit_core.monitor.
- Position
- Below the diagonal: winit_core.window uses a module listed above it, which is the healthy direction.
13→9 winit_core.window uses winit_appkit.monitor✕
- Connections
- 1 pair of types, where a type in winit_core.window uses a type in winit_appkit.monitor.
- The types involved
winit_core.window.Window→winit_appkit.monitor.MonitorHandle
- Direction
- winit_core.window uses winit_appkit.monitor, so a change to winit_appkit.monitor can break winit_core.window, while a change to winit_core.window can't break winit_appkit.monitor.
- Position
- Below the diagonal: winit_core.window uses a module listed above it, which is the healthy direction.
13→10 winit_core.window uses winit_common.xkb✕
- Connections
- 2 pairs of types, where a type in winit_core.window uses a type in winit_common.xkb.
- The types involved
winit_core.window.ImeRequestError→winit_common.xkb.Errorwinit_core.window.ImeSurroundingTextError→winit_common.xkb.Error
- Direction
- winit_core.window uses winit_common.xkb, so a change to winit_common.xkb can break winit_core.window, while a change to winit_core.window can't break winit_common.xkb.
- Position
- Below the diagonal: winit_core.window uses a module listed above it, which is the healthy direction.
13→11 winit_core.window uses winit_core.cursor✕
- Connections
- 2 pairs of types, where a type in winit_core.window uses a type in winit_core.cursor.
- The types involved
winit_core.window.Window→winit_core.cursor.Cursorwinit_core.window.WindowAttributes→winit_core.cursor.Cursor
- Direction
- winit_core.window uses winit_core.cursor, so a change to winit_core.cursor can break winit_core.window, while a change to winit_core.window can't break winit_core.cursor.
- Position
- Below the diagonal: winit_core.window uses a module listed above it, which is the healthy direction.
13→12 winit_core.window uses winit_core.icon✕
- Connections
- 2 pairs of types, where a type in winit_core.window uses a type in winit_core.icon.
- The types involved
winit_core.window.Window→winit_core.icon.Iconwinit_core.window.WindowAttributes→winit_core.icon.Icon
- Direction
- winit_core.window uses winit_core.icon, so a change to winit_core.icon can break winit_core.window, while a change to winit_core.window can't break winit_core.icon.
- Position
- Below the diagonal: winit_core.window uses a module listed above it, which is the healthy direction.
14→4 winit_core.event_loop uses winit_web.main_thread✕
- Connections
- 1 pair of types, where a type in winit_core.event_loop uses a type in winit_web.main_thread.
- The types involved
winit_core.event_loop.ActiveEventLoop→winit_web.main_thread.Any
- Direction
- winit_core.event_loop uses winit_web.main_thread, so a change to winit_web.main_thread can break winit_core.event_loop, while a change to winit_core.event_loop can't break winit_web.main_thread.
- Position
- Below the diagonal: winit_core.event_loop uses a module listed above it, which is the healthy direction.
14→5 winit_core.event_loop uses winit_core.data_transfer✕
- Connections
- 1 pair of types, where a type in winit_core.event_loop uses a type in winit_core.data_transfer.
- The types involved
winit_core.event_loop.ActiveEventLoop→winit_core.data_transfer.DataTransferId
- Direction
- winit_core.event_loop uses winit_core.data_transfer, so a change to winit_core.data_transfer can break winit_core.event_loop, while a change to winit_core.event_loop can't break winit_core.data_transfer.
- Position
- Below the diagonal: winit_core.event_loop uses a module listed above it, which is the healthy direction.
14→9 winit_core.event_loop uses winit_appkit.monitor✕
- Connections
- 1 pair of types, where a type in winit_core.event_loop uses a type in winit_appkit.monitor.
- The types involved
winit_core.event_loop.ActiveEventLoop→winit_appkit.monitor.MonitorHandle
- Direction
- winit_core.event_loop uses winit_appkit.monitor, so a change to winit_appkit.monitor can break winit_core.event_loop, while a change to winit_core.event_loop can't break winit_appkit.monitor.
- Position
- Below the diagonal: winit_core.event_loop uses a module listed above it, which is the healthy direction.
14→11 winit_core.event_loop uses winit_core.cursor✕
- Connections
- 2 pairs of types, where a type in winit_core.event_loop uses a type in winit_core.cursor.
- The types involved
winit_core.event_loop.ActiveEventLoop→winit_core.cursor.CustomCursorSourcewinit_core.event_loop.EventLoopProvider→winit_core.cursor.CustomCursorSource
- Direction
- winit_core.event_loop uses winit_core.cursor, so a change to winit_core.cursor can break winit_core.event_loop, while a change to winit_core.event_loop can't break winit_core.cursor.
- Position
- Below the diagonal: winit_core.event_loop uses a module listed above it, which is the healthy direction.
14→12 winit_core.event_loop uses winit_core.icon✕
- Connections
- 1 pair of types, where a type in winit_core.event_loop uses a type in winit_core.icon.
- The types involved
winit_core.event_loop.DragIcon→winit_core.icon.Icon
- Direction
- winit_core.event_loop uses winit_core.icon, so a change to winit_core.icon can break winit_core.event_loop, while a change to winit_core.event_loop can't break winit_core.icon.
- Position
- Below the diagonal: winit_core.event_loop uses a module listed above it, which is the healthy direction.
14→13 winit_core.event_loop uses winit_core.window✕
- Connections
- 3 pairs of types, where a type in winit_core.event_loop uses a type in winit_core.window.
- The types involved
winit_core.event_loop.ActiveEventLoop→winit_core.window.Themewinit_core.event_loop.ActiveEventLoop→winit_core.window.WindowAttributeswinit_core.event_loop.ActiveEventLoop→winit_core.window.WindowId
- Direction
- winit_core.event_loop uses winit_core.window, so a change to winit_core.window can break winit_core.event_loop, while a change to winit_core.event_loop can't break winit_core.window.
- Position
- Below the diagonal: winit_core.event_loop uses a module listed above it, which is the healthy direction.
14→15 winit_core.event_loop uses winit_android.event_loop part of a loop✕
- Connections
- 4 pairs of types, where a type in winit_core.event_loop uses a type in winit_android.event_loop.
- The types involved
winit_core.event_loop.ActiveEventLoop→winit_android.event_loop.EventLoopProxywinit_core.event_loop.ActiveEventLoop→winit_android.event_loop.OwnedDisplayHandlewinit_core.event_loop.EventLoopProvider→winit_android.event_loop.EventLoopProxywinit_core.event_loop.EventLoopProvider→winit_android.event_loop.OwnedDisplayHandle
- Direction
- winit_core.event_loop uses winit_android.event_loop, so a change to winit_android.event_loop can break winit_core.event_loop, while a change to winit_core.event_loop can't break winit_android.event_loop.
- 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 winit_android.event_loop uses dpi✕
- Connections
- 6 pairs of types, where a type in winit_android.event_loop uses a type in dpi.
- The types involved
winit_android.event_loop.Window→dpi.PhysicalInsetswinit_android.event_loop.Window→dpi.PhysicalPositionwinit_android.event_loop.Window→dpi.PhysicalSizewinit_android.event_loop.Window→dpi.Positionwinit_android.event_loop.Window→dpi.Sizewinit_android.event_loop.event_loop$module→dpi.PhysicalSize
- Direction
- winit_android.event_loop uses dpi, so a change to dpi can break winit_android.event_loop, while a change to winit_android.event_loop can't break dpi.
- Position
- Below the diagonal: winit_android.event_loop uses a module listed above it, which is the healthy direction.
15→6 winit_android.event_loop uses winit_core.event✕
- Connections
- 2 pairs of types, where a type in winit_android.event_loop uses a type in winit_core.event.
- The types involved
winit_android.event_loop.EventLoop→winit_core.event.FingerIdwinit_android.event_loop.EventLoop→winit_core.event.StartCause
- Direction
- winit_android.event_loop uses winit_core.event, so a change to winit_core.event can break winit_android.event_loop, while a change to winit_android.event_loop can't break winit_core.event.
- Position
- Below the diagonal: winit_android.event_loop uses a module listed above it, which is the healthy direction.
15→7 winit_android.event_loop uses winit_core.monitor✕
- Connections
- 1 pair of types, where a type in winit_android.event_loop uses a type in winit_core.monitor.
- The types involved
winit_android.event_loop.Window→winit_core.monitor.Fullscreen
- Direction
- winit_android.event_loop uses winit_core.monitor, so a change to winit_core.monitor can break winit_android.event_loop, while a change to winit_android.event_loop can't break winit_core.monitor.
- Position
- Below the diagonal: winit_android.event_loop uses a module listed above it, which is the healthy direction.
15→11 winit_android.event_loop uses winit_core.cursor✕
- Connections
- 3 pairs of types, where a type in winit_android.event_loop uses a type in winit_core.cursor.
- The types involved
winit_android.event_loop.ActiveEventLoop→winit_core.cursor.CustomCursorSourcewinit_android.event_loop.EventLoop→winit_core.cursor.CustomCursorSourcewinit_android.event_loop.Window→winit_core.cursor.Cursor
- Direction
- winit_android.event_loop uses winit_core.cursor, so a change to winit_core.cursor can break winit_android.event_loop, while a change to winit_android.event_loop can't break winit_core.cursor.
- Position
- Below the diagonal: winit_android.event_loop uses a module listed above it, which is the healthy direction.
15→12 winit_android.event_loop uses winit_core.icon✕
- Connections
- 1 pair of types, where a type in winit_android.event_loop uses a type in winit_core.icon.
- The types involved
winit_android.event_loop.Window→winit_core.icon.Icon
- Direction
- winit_android.event_loop uses winit_core.icon, so a change to winit_core.icon can break winit_android.event_loop, while a change to winit_android.event_loop can't break winit_core.icon.
- Position
- Below the diagonal: winit_android.event_loop uses a module listed above it, which is the healthy direction.
15→13 winit_android.event_loop uses winit_core.window✕
- Connections
- 14 pairs of types, where a type in winit_android.event_loop uses a type in winit_core.window.
- The types involved
winit_android.event_loop.ActiveEventLoop→winit_core.window.Themewinit_android.event_loop.ActiveEventLoop→winit_core.window.WindowAttributeswinit_android.event_loop.Window→winit_core.window.CursorGrabModewinit_android.event_loop.Window→winit_core.window.ImeCapabilitieswinit_android.event_loop.Window→winit_core.window.ImePurposewinit_android.event_loop.Window→winit_core.window.ImeRequestwinit_android.event_loop.Window→winit_core.window.ResizeDirectionwinit_android.event_loop.Window→winit_core.window.Themewinit_android.event_loop.Window→winit_core.window.UserAttentionTypewinit_android.event_loop.Window→winit_core.window.WindowAttributeswinit_android.event_loop.Window→winit_core.window.WindowButtonswinit_android.event_loop.Window→winit_core.window.WindowIdwinit_android.event_loop.Window→winit_core.window.WindowLevelwinit_android.event_loop.Window→winit_core.window.WindowType
- Direction
- winit_android.event_loop uses winit_core.window, so a change to winit_core.window can break winit_android.event_loop, while a change to winit_android.event_loop can't break winit_core.window.
- Position
- Below the diagonal: winit_android.event_loop uses a module listed above it, which is the healthy direction.
15→14 winit_android.event_loop uses winit_core.event_loop✕
- Connections
- 6 pairs of types, where a type in winit_android.event_loop uses a type in winit_core.event_loop.
- The types involved
winit_android.event_loop.ActiveEventLoop→winit_core.event_loop.ControlFlowwinit_android.event_loop.ActiveEventLoop→winit_core.event_loop.DeviceEventswinit_android.event_loop.EventLoop→winit_core.event_loop.ControlFlowwinit_android.event_loop.EventLoop→winit_core.event_loop.DeviceEventswinit_android.event_loop.EventLoop→winit_core.event_loop.EventLoopProviderwinit_android.event_loop.EventLoopProxy→winit_core.event_loop.EventLoopProxyProvider
- Direction
- winit_android.event_loop uses winit_core.event_loop, so a change to winit_core.event_loop can break winit_android.event_loop, while a change to winit_android.event_loop can't break winit_core.event_loop.
- Position
- Below the diagonal: winit_android.event_loop uses a module listed above it, which is the healthy direction.
15→17 winit_android.event_loop uses winit.platform_impl.linux part of a loop✕
- Connections
- 1 pair of types, where a type in winit_android.event_loop uses a type in winit.platform_impl.linux.
- The types involved
winit_android.event_loop.EventLoop→winit.platform_impl.linux.PlatformSpecificEventLoopAttributes
- Direction
- winit_android.event_loop uses winit.platform_impl.linux, so a change to winit.platform_impl.linux can break winit_android.event_loop, while a change to winit_android.event_loop can't break winit.platform_impl.linux.
- 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→4 winit_appkit.data_transfer uses winit_web.main_thread✕
- Connections
- 1 pair of types, where a type in winit_appkit.data_transfer uses a type in winit_web.main_thread.
- The types involved
winit_appkit.data_transfer.Pasteboard→winit_web.main_thread.MainThreadMarker
- Direction
- winit_appkit.data_transfer uses winit_web.main_thread, so a change to winit_web.main_thread can break winit_appkit.data_transfer, while a change to winit_appkit.data_transfer can't break winit_web.main_thread.
- Position
- Below the diagonal: winit_appkit.data_transfer uses a module listed above it, which is the healthy direction.
16→5 winit_appkit.data_transfer uses winit_core.data_transfer✕
- Connections
- 9 pairs of types, where a type in winit_appkit.data_transfer uses a type in winit_core.data_transfer.
- The types involved
winit_appkit.data_transfer.DataTransferState→winit_core.data_transfer.DataTransferIdwinit_appkit.data_transfer.DragState→winit_core.data_transfer.DataTransferIdwinit_appkit.data_transfer.Pasteboard→winit_core.data_transfer.DataTransferwinit_appkit.data_transfer.Pasteboard→winit_core.data_transfer.DataTransferIdwinit_appkit.data_transfer.PasteboardType→winit_core.data_transfer.TransferTypewinit_appkit.data_transfer.PasteboardType→winit_core.data_transfer.TypeHintwinit_appkit.data_transfer.PasteboardTypeSpec→winit_core.data_transfer.TypeHintwinit_appkit.data_transfer.PasteboardValue→winit_core.data_transfer.TypedDatawinit_appkit.data_transfer.Pasteboards→winit_core.data_transfer.DataTransferId
- Direction
- winit_appkit.data_transfer uses winit_core.data_transfer, so a change to winit_core.data_transfer can break winit_appkit.data_transfer, while a change to winit_appkit.data_transfer can't break winit_core.data_transfer.
- Position
- Below the diagonal: winit_appkit.data_transfer uses a module listed above it, which is the healthy direction.
16→13 winit_appkit.data_transfer uses winit_core.window✕
- Connections
- 3 pairs of types, where a type in winit_appkit.data_transfer uses a type in winit_core.window.
- The types involved
winit_appkit.data_transfer.ActivePasteboard→winit_core.window.WindowIdwinit_appkit.data_transfer.DataTransferState→winit_core.window.WindowIdwinit_appkit.data_transfer.Pasteboards→winit_core.window.WindowId
- Direction
- winit_appkit.data_transfer uses winit_core.window, so a change to winit_core.window can break winit_appkit.data_transfer, while a change to winit_appkit.data_transfer can't break winit_core.window.
- Position
- Below the diagonal: winit_appkit.data_transfer uses a module listed above it, which is the healthy direction.
16→14 winit_appkit.data_transfer uses winit_core.event_loop✕
- Connections
- 3 pairs of types, where a type in winit_appkit.data_transfer uses a type in winit_core.event_loop.
- The types involved
winit_appkit.data_transfer.DataTransferState→winit_core.event_loop.DndActionwinit_appkit.data_transfer.DragState→winit_core.event_loop.DndActionwinit_appkit.data_transfer.data_transfer$module→winit_core.event_loop.DndAction
- Direction
- winit_appkit.data_transfer uses winit_core.event_loop, so a change to winit_core.event_loop can break winit_appkit.data_transfer, while a change to winit_appkit.data_transfer can't break winit_core.event_loop.
- Position
- Below the diagonal: winit_appkit.data_transfer uses a module listed above it, which is the healthy direction.
17→11 winit.platform_impl.linux uses winit_core.cursor✕
- Connections
- 1 pair of types, where a type in winit.platform_impl.linux uses a type in winit_core.cursor.
- The types involved
winit.platform_impl.linux.EventLoop→winit_core.cursor.CustomCursorSource
- Direction
- winit.platform_impl.linux uses winit_core.cursor, so a change to winit_core.cursor can break winit.platform_impl.linux, while a change to winit.platform_impl.linux can't break winit_core.cursor.
- Position
- Below the diagonal: winit.platform_impl.linux uses a module listed above it, which is the healthy direction.
17→14 winit.platform_impl.linux uses winit_core.event_loop✕
- Connections
- 3 pairs of types, where a type in winit.platform_impl.linux uses a type in winit_core.event_loop.
- The types involved
winit.platform_impl.linux.EventLoop→winit_core.event_loop.ControlFlowwinit.platform_impl.linux.EventLoop→winit_core.event_loop.DeviceEventswinit.platform_impl.linux.EventLoop→winit_core.event_loop.EventLoopProvider
- Direction
- winit.platform_impl.linux uses winit_core.event_loop, so a change to winit_core.event_loop can break winit.platform_impl.linux, while a change to winit.platform_impl.linux can't break winit_core.event_loop.
- Position
- Below the diagonal: winit.platform_impl.linux uses a module listed above it, which is the healthy direction.
17→15 winit.platform_impl.linux uses winit_android.event_loop✕
- Connections
- 2 pairs of types, where a type in winit.platform_impl.linux uses a type in winit_android.event_loop.
- The types involved
winit.platform_impl.linux.EventLoop→winit_android.event_loop.EventLoopProxywinit.platform_impl.linux.EventLoop→winit_android.event_loop.OwnedDisplayHandle
- Direction
- winit.platform_impl.linux uses winit_android.event_loop, so a change to winit_android.event_loop can break winit.platform_impl.linux, while a change to winit.platform_impl.linux can't break winit_android.event_loop.
- Position
- Below the diagonal: winit.platform_impl.linux uses a module listed above it, which is the healthy direction.
18→4 winit_appkit.app_state uses winit_web.main_thread✕
- Connections
- 1 pair of types, where a type in winit_appkit.app_state uses a type in winit_web.main_thread.
- The types involved
winit_appkit.app_state.AppState→winit_web.main_thread.MainThreadMarker
- Direction
- winit_appkit.app_state uses winit_web.main_thread, so a change to winit_web.main_thread can break winit_appkit.app_state, while a change to winit_appkit.app_state can't break winit_web.main_thread.
- Position
- Below the diagonal: winit_appkit.app_state uses a module listed above it, which is the healthy direction.
18→13 winit_appkit.app_state uses winit_core.window✕
- Connections
- 1 pair of types, where a type in winit_appkit.app_state uses a type in winit_core.window.
- The types involved
winit_appkit.app_state.AppState→winit_core.window.WindowId
- Direction
- winit_appkit.app_state uses winit_core.window, so a change to winit_core.window can break winit_appkit.app_state, while a change to winit_appkit.app_state can't break winit_core.window.
- Position
- Below the diagonal: winit_appkit.app_state uses a module listed above it, which is the healthy direction.
18→14 winit_appkit.app_state uses winit_core.event_loop✕
- Connections
- 1 pair of types, where a type in winit_appkit.app_state uses a type in winit_core.event_loop.
- The types involved
winit_appkit.app_state.AppState→winit_core.event_loop.ControlFlow
- Direction
- winit_appkit.app_state uses winit_core.event_loop, so a change to winit_core.event_loop can break winit_appkit.app_state, while a change to winit_appkit.app_state can't break winit_core.event_loop.
- Position
- Below the diagonal: winit_appkit.app_state uses a module listed above it, which is the healthy direction.
18→15 winit_appkit.app_state uses winit_android.event_loop✕
- Connections
- 1 pair of types, where a type in winit_appkit.app_state uses a type in winit_android.event_loop.
- The types involved
winit_appkit.app_state.AppState→winit_android.event_loop.EventLoopProxy
- Direction
- winit_appkit.app_state uses winit_android.event_loop, so a change to winit_android.event_loop can break winit_appkit.app_state, while a change to winit_appkit.app_state can't break winit_android.event_loop.
- Position
- Below the diagonal: winit_appkit.app_state uses a module listed above it, which is the healthy direction.
18→16 winit_appkit.app_state uses winit_appkit.data_transfer✕
- Connections
- 1 pair of types, where a type in winit_appkit.app_state uses a type in winit_appkit.data_transfer.
- The types involved
winit_appkit.app_state.AppState→winit_appkit.data_transfer.DataTransferState
- Direction
- winit_appkit.app_state uses winit_appkit.data_transfer, so a change to winit_appkit.data_transfer can break winit_appkit.app_state, while a change to winit_appkit.app_state can't break winit_appkit.data_transfer.
- Position
- Below the diagonal: winit_appkit.app_state uses a module listed above it, which is the healthy direction.
19→1 winit_uikit.window uses dpi✕
- Connections
- 10 pairs of types, where a type in winit_uikit.window uses a type in dpi.
- The types involved
winit_uikit.window.Inner→dpi.PhysicalInsetswinit_uikit.window.Inner→dpi.PhysicalPositionwinit_uikit.window.Inner→dpi.PhysicalSizewinit_uikit.window.Inner→dpi.Positionwinit_uikit.window.Inner→dpi.Sizewinit_uikit.window.Window→dpi.PhysicalInsetswinit_uikit.window.Window→dpi.PhysicalPositionwinit_uikit.window.Window→dpi.PhysicalSizewinit_uikit.window.Window→dpi.Positionwinit_uikit.window.Window→dpi.Size
- Direction
- winit_uikit.window uses dpi, so a change to dpi can break winit_uikit.window, while a change to winit_uikit.window can't break dpi.
- Position
- Below the diagonal: winit_uikit.window uses a module listed above it, which is the healthy direction.
19→4 winit_uikit.window uses winit_web.main_thread✕
- Connections
- 1 pair of types, where a type in winit_uikit.window uses a type in winit_web.main_thread.
- The types involved
winit_uikit.window.WinitUIWindow→winit_web.main_thread.MainThreadMarker
- Direction
- winit_uikit.window uses winit_web.main_thread, so a change to winit_web.main_thread can break winit_uikit.window, while a change to winit_uikit.window can't break winit_web.main_thread.
- Position
- Below the diagonal: winit_uikit.window uses a module listed above it, which is the healthy direction.
19→7 winit_uikit.window uses winit_core.monitor✕
- Connections
- 2 pairs of types, where a type in winit_uikit.window uses a type in winit_core.monitor.
- The types involved
winit_uikit.window.Inner→winit_core.monitor.Fullscreenwinit_uikit.window.Window→winit_core.monitor.Fullscreen
- Direction
- winit_uikit.window uses winit_core.monitor, so a change to winit_core.monitor can break winit_uikit.window, while a change to winit_uikit.window can't break winit_core.monitor.
- Position
- Below the diagonal: winit_uikit.window uses a module listed above it, which is the healthy direction.
19→9 winit_uikit.window uses winit_appkit.monitor✕
- Connections
- 1 pair of types, where a type in winit_uikit.window uses a type in winit_appkit.monitor.
- The types involved
winit_uikit.window.Inner→winit_appkit.monitor.MonitorHandle
- Direction
- winit_uikit.window uses winit_appkit.monitor, so a change to winit_appkit.monitor can break winit_uikit.window, while a change to winit_uikit.window can't break winit_appkit.monitor.
- Position
- Below the diagonal: winit_uikit.window uses a module listed above it, which is the healthy direction.
19→11 winit_uikit.window uses winit_core.cursor✕
- Connections
- 2 pairs of types, where a type in winit_uikit.window uses a type in winit_core.cursor.
- The types involved
winit_uikit.window.Inner→winit_core.cursor.Cursorwinit_uikit.window.Window→winit_core.cursor.Cursor
- Direction
- winit_uikit.window uses winit_core.cursor, so a change to winit_core.cursor can break winit_uikit.window, while a change to winit_uikit.window can't break winit_core.cursor.
- Position
- Below the diagonal: winit_uikit.window uses a module listed above it, which is the healthy direction.
19→12 winit_uikit.window uses winit_core.icon✕
- Connections
- 2 pairs of types, where a type in winit_uikit.window uses a type in winit_core.icon.
- The types involved
winit_uikit.window.Inner→winit_core.icon.Iconwinit_uikit.window.Window→winit_core.icon.Icon
- Direction
- winit_uikit.window uses winit_core.icon, so a change to winit_core.icon can break winit_uikit.window, while a change to winit_uikit.window can't break winit_core.icon.
- Position
- Below the diagonal: winit_uikit.window uses a module listed above it, which is the healthy direction.
19→13 winit_uikit.window uses winit_core.window✕
- Connections
- 22 pairs of types, where a type in winit_uikit.window uses a type in winit_core.window.
- The types involved
winit_uikit.window.Inner→winit_core.window.CursorGrabModewinit_uikit.window.Inner→winit_core.window.ImeCapabilitieswinit_uikit.window.Inner→winit_core.window.ImeRequestwinit_uikit.window.Inner→winit_core.window.ResizeDirectionwinit_uikit.window.Inner→winit_core.window.Themewinit_uikit.window.Inner→winit_core.window.UserAttentionTypewinit_uikit.window.Inner→winit_core.window.WindowButtonswinit_uikit.window.Inner→winit_core.window.WindowIdwinit_uikit.window.Inner→winit_core.window.WindowLevelwinit_uikit.window.Window→winit_core.window.CursorGrabModewinit_uikit.window.Window→winit_core.window.ImeCapabilitieswinit_uikit.window.Window→winit_core.window.ImeRequestwinit_uikit.window.Window→winit_core.window.ResizeDirectionwinit_uikit.window.Window→winit_core.window.Themewinit_uikit.window.Window→winit_core.window.UserAttentionTypewinit_uikit.window.Window→winit_core.window.WindowAttributeswinit_uikit.window.Window→winit_core.window.WindowButtonswinit_uikit.window.Window→winit_core.window.WindowIdwinit_uikit.window.Window→winit_core.window.WindowLevelwinit_uikit.window.Window→winit_core.window.WindowTypewinit_uikit.window.WinitUIWindow→winit_core.window.WindowAttributeswinit_uikit.window.WinitUIWindow→winit_core.window.WindowId
- Direction
- winit_uikit.window uses winit_core.window, so a change to winit_core.window can break winit_uikit.window, while a change to winit_uikit.window can't break winit_core.window.
- Position
- Below the diagonal: winit_uikit.window uses a module listed above it, which is the healthy direction.
19→15 winit_uikit.window uses winit_android.event_loop✕
- Connections
- 1 pair of types, where a type in winit_uikit.window uses a type in winit_android.event_loop.
- The types involved
winit_uikit.window.Window→winit_android.event_loop.ActiveEventLoop
- Direction
- winit_uikit.window uses winit_android.event_loop, so a change to winit_android.event_loop can break winit_uikit.window, while a change to winit_uikit.window can't break winit_android.event_loop.
- Position
- Below the diagonal: winit_uikit.window uses a module listed above it, which is the healthy direction.
20→5 winit_wayland.state uses winit_core.data_transfer✕
- Connections
- 2 pairs of types, where a type in winit_wayland.state uses a type in winit_core.data_transfer.
- The types involved
winit_wayland.state.WinitState→winit_core.data_transfer.DataTransferIdwinit_wayland.state.WinitState→winit_core.data_transfer.SendData
- Direction
- winit_wayland.state uses winit_core.data_transfer, so a change to winit_core.data_transfer can break winit_wayland.state, while a change to winit_wayland.state can't break winit_core.data_transfer.
- Position
- Below the diagonal: winit_wayland.state uses a module listed above it, which is the healthy direction.
20→9 winit_wayland.state uses winit_appkit.monitor✕
- Connections
- 1 pair of types, where a type in winit_wayland.state uses a type in winit_appkit.monitor.
- The types involved
winit_wayland.state.WinitState→winit_appkit.monitor.MonitorHandle
- Direction
- winit_wayland.state uses winit_appkit.monitor, so a change to winit_appkit.monitor can break winit_wayland.state, while a change to winit_wayland.state can't break winit_appkit.monitor.
- Position
- Below the diagonal: winit_wayland.state uses a module listed above it, which is the healthy direction.
20→13 winit_wayland.state uses winit_core.window✕
- Connections
- 2 pairs of types, where a type in winit_wayland.state uses a type in winit_core.window.
- The types involved
winit_wayland.state.WindowCompositorUpdate→winit_core.window.WindowIdwinit_wayland.state.WinitState→winit_core.window.WindowId
- Direction
- winit_wayland.state uses winit_core.window, so a change to winit_core.window can break winit_wayland.state, while a change to winit_wayland.state can't break winit_core.window.
- Position
- Below the diagonal: winit_wayland.state uses a module listed above it, which is the healthy direction.
20→14 winit_wayland.state uses winit_core.event_loop✕
- Connections
- 1 pair of types, where a type in winit_wayland.state uses a type in winit_core.event_loop.
- The types involved
winit_wayland.state.WinitState→winit_core.event_loop.DragIcon
- Direction
- winit_wayland.state uses winit_core.event_loop, so a change to winit_core.event_loop can break winit_wayland.state, while a change to winit_wayland.state can't break winit_core.event_loop.
- Position
- Below the diagonal: winit_wayland.state uses a module listed above it, which is the healthy direction.
20→15 winit_wayland.state uses winit_android.event_loop✕
- Connections
- 1 pair of types, where a type in winit_wayland.state uses a type in winit_android.event_loop.
- The types involved
winit_wayland.state.WinitState→winit_android.event_loop.Window
- Direction
- winit_wayland.state uses winit_android.event_loop, so a change to winit_android.event_loop can break winit_wayland.state, while a change to winit_wayland.state can't break winit_android.event_loop.
- Position
- Below the diagonal: winit_wayland.state uses a module listed above it, which is the healthy direction.
20→16 winit_wayland.state uses winit_appkit.data_transfer✕
- Connections
- 1 pair of types, where a type in winit_wayland.state uses a type in winit_appkit.data_transfer.
- The types involved
winit_wayland.state.WinitState→winit_appkit.data_transfer.DataTransferState
- Direction
- winit_wayland.state uses winit_appkit.data_transfer, so a change to winit_appkit.data_transfer can break winit_wayland.state, while a change to winit_wayland.state can't break winit_appkit.data_transfer.
- Position
- Below the diagonal: winit_wayland.state uses a module listed above it, which is the healthy direction.
20→32 winit_wayland.state uses winit_wayland.event_loop part of a loop✕
- Connections
- 1 pair of types, where a type in winit_wayland.state uses a type in winit_wayland.event_loop.
- The types involved
winit_wayland.state.WinitState→winit_wayland.event_loop.Event
- Direction
- winit_wayland.state uses winit_wayland.event_loop, so a change to winit_wayland.event_loop can break winit_wayland.state, while a change to winit_wayland.state can't break winit_wayland.event_loop.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→1 winit_web.web_sys.canvas uses dpi✕
- Connections
- 3 pairs of types, where a type in winit_web.web_sys.canvas uses a type in dpi.
- The types involved
winit_web.web_sys.canvas.Canvas→dpi.LogicalPositionwinit_web.web_sys.canvas.Canvas→dpi.PhysicalSizewinit_web.web_sys.canvas.Common→dpi.PhysicalSize
- Direction
- winit_web.web_sys.canvas uses dpi, so a change to dpi can break winit_web.web_sys.canvas, while a change to winit_web.web_sys.canvas can't break dpi.
- Position
- Below the diagonal: winit_web.web_sys.canvas uses a module listed above it, which is the healthy direction.
21→4 winit_web.web_sys.canvas uses winit_web.main_thread✕
- Connections
- 1 pair of types, where a type in winit_web.web_sys.canvas uses a type in winit_web.main_thread.
- The types involved
winit_web.web_sys.canvas.Canvas→winit_web.main_thread.MainThreadMarker
- Direction
- winit_web.web_sys.canvas uses winit_web.main_thread, so a change to winit_web.main_thread can break winit_web.web_sys.canvas, while a change to winit_web.web_sys.canvas can't break winit_web.main_thread.
- Position
- Below the diagonal: winit_web.web_sys.canvas uses a module listed above it, which is the healthy direction.
21→7 winit_web.web_sys.canvas uses winit_core.monitor✕
- Connections
- 1 pair of types, where a type in winit_web.web_sys.canvas uses a type in winit_core.monitor.
- The types involved
winit_web.web_sys.canvas.Canvas→winit_core.monitor.Fullscreen
- Direction
- winit_web.web_sys.canvas uses winit_core.monitor, so a change to winit_core.monitor can break winit_web.web_sys.canvas, while a change to winit_web.web_sys.canvas can't break winit_core.monitor.
- Position
- Below the diagonal: winit_web.web_sys.canvas uses a module listed above it, which is the healthy direction.
21→13 winit_web.web_sys.canvas uses winit_core.window✕
- Connections
- 2 pairs of types, where a type in winit_web.web_sys.canvas uses a type in winit_core.window.
- The types involved
winit_web.web_sys.canvas.Canvas→winit_core.window.WindowAttributeswinit_web.web_sys.canvas.Canvas→winit_core.window.WindowId
- Direction
- winit_web.web_sys.canvas uses winit_core.window, so a change to winit_core.window can break winit_web.web_sys.canvas, while a change to winit_web.web_sys.canvas can't break winit_core.window.
- Position
- Below the diagonal: winit_web.web_sys.canvas uses a module listed above it, which is the healthy direction.
21→15 winit_web.web_sys.canvas uses winit_android.event_loop✕
- Connections
- 3 pairs of types, where a type in winit_web.web_sys.canvas uses a type in winit_android.event_loop.
- The types involved
winit_web.web_sys.canvas.Canvas→winit_android.event_loop.Windowwinit_web.web_sys.canvas.Common→winit_android.event_loop.Windowwinit_web.web_sys.canvas.Style→winit_android.event_loop.Window
- Direction
- winit_web.web_sys.canvas uses winit_android.event_loop, so a change to winit_android.event_loop can break winit_web.web_sys.canvas, while a change to winit_web.web_sys.canvas can't break winit_android.event_loop.
- Position
- Below the diagonal: winit_web.web_sys.canvas uses a module listed above it, which is the healthy direction.
21→26 winit_web.web_sys.canvas uses winit_web.cursor part of a loop✕
- Connections
- 1 pair of types, where a type in winit_web.web_sys.canvas uses a type in winit_web.cursor.
- The types involved
winit_web.web_sys.canvas.Canvas→winit_web.cursor.CursorHandler
- Direction
- winit_web.web_sys.canvas uses winit_web.cursor, so a change to winit_web.cursor can break winit_web.web_sys.canvas, while a change to winit_web.web_sys.canvas can't break winit_web.cursor.
- 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→4 winit_appkit.event_loop uses winit_web.main_thread✕
- Connections
- 1 pair of types, where a type in winit_appkit.event_loop uses a type in winit_web.main_thread.
- The types involved
winit_appkit.event_loop.ActiveEventLoop→winit_web.main_thread.MainThreadMarker
- Direction
- winit_appkit.event_loop uses winit_web.main_thread, so a change to winit_web.main_thread can break winit_appkit.event_loop, while a change to winit_appkit.event_loop can't break winit_web.main_thread.
- Position
- Below the diagonal: winit_appkit.event_loop uses a module listed above it, which is the healthy direction.
22→5 winit_appkit.event_loop uses winit_core.data_transfer✕
- Connections
- 1 pair of types, where a type in winit_appkit.event_loop uses a type in winit_core.data_transfer.
- The types involved
winit_appkit.event_loop.ActiveEventLoop→winit_core.data_transfer.DataTransferId
- Direction
- winit_appkit.event_loop uses winit_core.data_transfer, so a change to winit_core.data_transfer can break winit_appkit.event_loop, while a change to winit_appkit.event_loop can't break winit_core.data_transfer.
- Position
- Below the diagonal: winit_appkit.event_loop uses a module listed above it, which is the healthy direction.
22→9 winit_appkit.event_loop uses winit_appkit.monitor✕
- Connections
- 1 pair of types, where a type in winit_appkit.event_loop uses a type in winit_appkit.monitor.
- The types involved
winit_appkit.event_loop.ActiveEventLoop→winit_appkit.monitor.MonitorHandle
- Direction
- winit_appkit.event_loop uses winit_appkit.monitor, so a change to winit_appkit.monitor can break winit_appkit.event_loop, while a change to winit_appkit.event_loop can't break winit_appkit.monitor.
- Position
- Below the diagonal: winit_appkit.event_loop uses a module listed above it, which is the healthy direction.
22→11 winit_appkit.event_loop uses winit_core.cursor✕
- Connections
- 2 pairs of types, where a type in winit_appkit.event_loop uses a type in winit_core.cursor.
- The types involved
winit_appkit.event_loop.ActiveEventLoop→winit_core.cursor.CustomCursorSourcewinit_appkit.event_loop.EventLoop→winit_core.cursor.CustomCursorSource
- Direction
- winit_appkit.event_loop uses winit_core.cursor, so a change to winit_core.cursor can break winit_appkit.event_loop, while a change to winit_appkit.event_loop can't break winit_core.cursor.
- Position
- Below the diagonal: winit_appkit.event_loop uses a module listed above it, which is the healthy direction.
22→13 winit_appkit.event_loop uses winit_core.window✕
- Connections
- 3 pairs of types, where a type in winit_appkit.event_loop uses a type in winit_core.window.
- The types involved
winit_appkit.event_loop.ActiveEventLoop→winit_core.window.Themewinit_appkit.event_loop.ActiveEventLoop→winit_core.window.WindowAttributeswinit_appkit.event_loop.ActiveEventLoop→winit_core.window.WindowId
- Direction
- winit_appkit.event_loop uses winit_core.window, so a change to winit_core.window can break winit_appkit.event_loop, while a change to winit_appkit.event_loop can't break winit_core.window.
- Position
- Below the diagonal: winit_appkit.event_loop uses a module listed above it, which is the healthy direction.
22→14 winit_appkit.event_loop uses winit_core.event_loop✕
- Connections
- 6 pairs of types, where a type in winit_appkit.event_loop uses a type in winit_core.event_loop.
- The types involved
winit_appkit.event_loop.ActiveEventLoop→winit_core.event_loop.ControlFlowwinit_appkit.event_loop.ActiveEventLoop→winit_core.event_loop.DeviceEventswinit_appkit.event_loop.ActiveEventLoop→winit_core.event_loop.DragIconwinit_appkit.event_loop.EventLoop→winit_core.event_loop.ControlFlowwinit_appkit.event_loop.EventLoop→winit_core.event_loop.DeviceEventswinit_appkit.event_loop.EventLoop→winit_core.event_loop.EventLoopProvider
- Direction
- winit_appkit.event_loop uses winit_core.event_loop, so a change to winit_core.event_loop can break winit_appkit.event_loop, while a change to winit_appkit.event_loop can't break winit_core.event_loop.
- Position
- Below the diagonal: winit_appkit.event_loop uses a module listed above it, which is the healthy direction.
22→15 winit_appkit.event_loop uses winit_android.event_loop✕
- Connections
- 1 pair of types, where a type in winit_appkit.event_loop uses a type in winit_android.event_loop.
- The types involved
winit_appkit.event_loop.EventLoop→winit_android.event_loop.ActiveEventLoop
- Direction
- winit_appkit.event_loop uses winit_android.event_loop, so a change to winit_android.event_loop can break winit_appkit.event_loop, while a change to winit_appkit.event_loop can't break winit_android.event_loop.
- Position
- Below the diagonal: winit_appkit.event_loop uses a module listed above it, which is the healthy direction.
22→16 winit_appkit.event_loop uses winit_appkit.data_transfer✕
- Connections
- 1 pair of types, where a type in winit_appkit.event_loop uses a type in winit_appkit.data_transfer.
- The types involved
winit_appkit.event_loop.ActiveEventLoop→winit_appkit.data_transfer.Pasteboard
- Direction
- winit_appkit.event_loop uses winit_appkit.data_transfer, so a change to winit_appkit.data_transfer can break winit_appkit.event_loop, while a change to winit_appkit.event_loop can't break winit_appkit.data_transfer.
- Position
- Below the diagonal: winit_appkit.event_loop uses a module listed above it, which is the healthy direction.
22→17 winit_appkit.event_loop uses winit.platform_impl.linux✕
- Connections
- 1 pair of types, where a type in winit_appkit.event_loop uses a type in winit.platform_impl.linux.
- The types involved
winit_appkit.event_loop.EventLoop→winit.platform_impl.linux.PlatformSpecificEventLoopAttributes
- Direction
- winit_appkit.event_loop uses winit.platform_impl.linux, so a change to winit.platform_impl.linux can break winit_appkit.event_loop, while a change to winit_appkit.event_loop can't break winit.platform_impl.linux.
- Position
- Below the diagonal: winit_appkit.event_loop uses a module listed above it, which is the healthy direction.
22→18 winit_appkit.event_loop uses winit_appkit.app_state✕
- Connections
- 2 pairs of types, where a type in winit_appkit.event_loop uses a type in winit_appkit.app_state.
- The types involved
winit_appkit.event_loop.ActiveEventLoop→winit_appkit.app_state.AppStatewinit_appkit.event_loop.EventLoop→winit_appkit.app_state.AppState
- Direction
- winit_appkit.event_loop uses winit_appkit.app_state, so a change to winit_appkit.app_state can break winit_appkit.event_loop, while a change to winit_appkit.event_loop can't break winit_appkit.app_state.
- Position
- Below the diagonal: winit_appkit.event_loop uses a module listed above it, which is the healthy direction.
23→1 winit_appkit.window_delegate uses dpi✕
- Connections
- 6 pairs of types, where a type in winit_appkit.window_delegate uses a type in dpi.
- The types involved
winit_appkit.window_delegate.WindowDelegate→dpi.LogicalPositionwinit_appkit.window_delegate.WindowDelegate→dpi.PhysicalInsetswinit_appkit.window_delegate.WindowDelegate→dpi.PhysicalPositionwinit_appkit.window_delegate.WindowDelegate→dpi.PhysicalSizewinit_appkit.window_delegate.WindowDelegate→dpi.Positionwinit_appkit.window_delegate.WindowDelegate→dpi.Size
- Direction
- winit_appkit.window_delegate uses dpi, so a change to dpi can break winit_appkit.window_delegate, while a change to winit_appkit.window_delegate can't break dpi.
- Position
- Below the diagonal: winit_appkit.window_delegate uses a module listed above it, which is the healthy direction.
23→4 winit_appkit.window_delegate uses winit_web.main_thread✕
- Connections
- 2 pairs of types, where a type in winit_appkit.window_delegate uses a type in winit_web.main_thread.
- The types involved
winit_appkit.window_delegate.WindowDelegate→winit_web.main_thread.MainThreadMarkerwinit_appkit.window_delegate.window_delegate$module→winit_web.main_thread.MainThreadMarker
- Direction
- winit_appkit.window_delegate uses winit_web.main_thread, so a change to winit_web.main_thread can break winit_appkit.window_delegate, while a change to winit_appkit.window_delegate can't break winit_web.main_thread.
- Position
- Below the diagonal: winit_appkit.window_delegate uses a module listed above it, which is the healthy direction.
23→6 winit_appkit.window_delegate uses winit_core.event✕
- Connections
- 1 pair of types, where a type in winit_appkit.window_delegate uses a type in winit_core.event.
- The types involved
winit_appkit.window_delegate.WindowDelegate→winit_core.event.WindowEvent
- Direction
- winit_appkit.window_delegate uses winit_core.event, so a change to winit_core.event can break winit_appkit.window_delegate, while a change to winit_appkit.window_delegate can't break winit_core.event.
- Position
- Below the diagonal: winit_appkit.window_delegate uses a module listed above it, which is the healthy direction.
23→7 winit_appkit.window_delegate uses winit_core.monitor✕
- Connections
- 2 pairs of types, where a type in winit_appkit.window_delegate uses a type in winit_core.monitor.
- The types involved
winit_appkit.window_delegate.State→winit_core.monitor.Fullscreenwinit_appkit.window_delegate.WindowDelegate→winit_core.monitor.Fullscreen
- Direction
- winit_appkit.window_delegate uses winit_core.monitor, so a change to winit_core.monitor can break winit_appkit.window_delegate, while a change to winit_appkit.window_delegate can't break winit_core.monitor.
- Position
- Below the diagonal: winit_appkit.window_delegate uses a module listed above it, which is the healthy direction.
23→9 winit_appkit.window_delegate uses winit_appkit.monitor✕
- Connections
- 2 pairs of types, where a type in winit_appkit.window_delegate uses a type in winit_appkit.monitor.
- The types involved
winit_appkit.window_delegate.WindowDelegate→winit_appkit.monitor.MonitorHandlewinit_appkit.window_delegate.window_delegate$module→winit_appkit.monitor.MonitorHandle
- Direction
- winit_appkit.window_delegate uses winit_appkit.monitor, so a change to winit_appkit.monitor can break winit_appkit.window_delegate, while a change to winit_appkit.window_delegate can't break winit_appkit.monitor.
- Position
- Below the diagonal: winit_appkit.window_delegate uses a module listed above it, which is the healthy direction.
23→11 winit_appkit.window_delegate uses winit_core.cursor✕
- Connections
- 1 pair of types, where a type in winit_appkit.window_delegate uses a type in winit_core.cursor.
- The types involved
winit_appkit.window_delegate.WindowDelegate→winit_core.cursor.Cursor
- Direction
- winit_appkit.window_delegate uses winit_core.cursor, so a change to winit_core.cursor can break winit_appkit.window_delegate, while a change to winit_appkit.window_delegate can't break winit_core.cursor.
- Position
- Below the diagonal: winit_appkit.window_delegate uses a module listed above it, which is the healthy direction.
23→12 winit_appkit.window_delegate uses winit_core.icon✕
- Connections
- 1 pair of types, where a type in winit_appkit.window_delegate uses a type in winit_core.icon.
- The types involved
winit_appkit.window_delegate.WindowDelegate→winit_core.icon.Icon
- Direction
- winit_appkit.window_delegate uses winit_core.icon, so a change to winit_core.icon can break winit_appkit.window_delegate, while a change to winit_appkit.window_delegate can't break winit_core.icon.
- Position
- Below the diagonal: winit_appkit.window_delegate uses a module listed above it, which is the healthy direction.
23→13 winit_appkit.window_delegate uses winit_core.window✕
- Connections
- 16 pairs of types, where a type in winit_appkit.window_delegate uses a type in winit_core.window.
- The types involved
winit_appkit.window_delegate.State→winit_core.window.WindowPositionerwinit_appkit.window_delegate.State→winit_core.window.WindowTypewinit_appkit.window_delegate.WindowDelegate→winit_core.window.CursorGrabModewinit_appkit.window_delegate.WindowDelegate→winit_core.window.ImeCapabilitieswinit_appkit.window_delegate.WindowDelegate→winit_core.window.ImeRequestwinit_appkit.window_delegate.WindowDelegate→winit_core.window.ResizeDirectionwinit_appkit.window_delegate.WindowDelegate→winit_core.window.Themewinit_appkit.window_delegate.WindowDelegate→winit_core.window.UserAttentionTypewinit_appkit.window_delegate.WindowDelegate→winit_core.window.WindowAttributeswinit_appkit.window_delegate.WindowDelegate→winit_core.window.WindowButtonswinit_appkit.window_delegate.WindowDelegate→winit_core.window.WindowIdwinit_appkit.window_delegate.WindowDelegate→winit_core.window.WindowLevelwinit_appkit.window_delegate.WindowDelegate→winit_core.window.WindowPositionerwinit_appkit.window_delegate.WindowDelegate→winit_core.window.WindowTypewinit_appkit.window_delegate.window_delegate$module→winit_core.window.Themewinit_appkit.window_delegate.window_delegate$module→winit_core.window.WindowAttributes
- Direction
- winit_appkit.window_delegate uses winit_core.window, so a change to winit_core.window can break winit_appkit.window_delegate, while a change to winit_appkit.window_delegate can't break winit_core.window.
- Position
- Below the diagonal: winit_appkit.window_delegate uses a module listed above it, which is the healthy direction.
23→18 winit_appkit.window_delegate uses winit_appkit.app_state✕
- Connections
- 3 pairs of types, where a type in winit_appkit.window_delegate uses a type in winit_appkit.app_state.
- The types involved
winit_appkit.window_delegate.State→winit_appkit.app_state.AppStatewinit_appkit.window_delegate.WindowDelegate→winit_appkit.app_state.AppStatewinit_appkit.window_delegate.window_delegate$module→winit_appkit.app_state.AppState
- Direction
- winit_appkit.window_delegate uses winit_appkit.app_state, so a change to winit_appkit.app_state can break winit_appkit.window_delegate, while a change to winit_appkit.window_delegate can't break winit_appkit.app_state.
- Position
- Below the diagonal: winit_appkit.window_delegate uses a module listed above it, which is the healthy direction.
24→3 winit_orbital.event_loop uses winit_core.keyboard✕
- Connections
- 2 pairs of types, where a type in winit_orbital.event_loop uses a type in winit_core.keyboard.
- The types involved
winit_orbital.event_loop.EventState→winit_core.keyboard.PhysicalKeywinit_orbital.event_loop.event_loop$module→winit_core.keyboard.PhysicalKey
- Direction
- winit_orbital.event_loop uses winit_core.keyboard, so a change to winit_core.keyboard can break winit_orbital.event_loop, while a change to winit_orbital.event_loop can't break winit_core.keyboard.
- Position
- Below the diagonal: winit_orbital.event_loop uses a module listed above it, which is the healthy direction.
24→6 winit_orbital.event_loop uses winit_core.event✕
- Connections
- 3 pairs of types, where a type in winit_orbital.event_loop uses a type in winit_core.event.
- The types involved
winit_orbital.event_loop.EventLoop→winit_core.event.StartCausewinit_orbital.event_loop.EventState→winit_core.event.Modifierswinit_orbital.event_loop.event_loop$module→winit_core.event.ElementState
- Direction
- winit_orbital.event_loop uses winit_core.event, so a change to winit_core.event can break winit_orbital.event_loop, while a change to winit_orbital.event_loop can't break winit_core.event.
- Position
- Below the diagonal: winit_orbital.event_loop uses a module listed above it, which is the healthy direction.
24→9 winit_orbital.event_loop uses winit_appkit.monitor✕
- Connections
- 1 pair of types, where a type in winit_orbital.event_loop uses a type in winit_appkit.monitor.
- The types involved
winit_orbital.event_loop.ActiveEventLoop→winit_appkit.monitor.MonitorHandle
- Direction
- winit_orbital.event_loop uses winit_appkit.monitor, so a change to winit_appkit.monitor can break winit_orbital.event_loop, while a change to winit_orbital.event_loop can't break winit_appkit.monitor.
- Position
- Below the diagonal: winit_orbital.event_loop uses a module listed above it, which is the healthy direction.
24→11 winit_orbital.event_loop uses winit_core.cursor✕
- Connections
- 2 pairs of types, where a type in winit_orbital.event_loop uses a type in winit_core.cursor.
- The types involved
winit_orbital.event_loop.ActiveEventLoop→winit_core.cursor.CustomCursorSourcewinit_orbital.event_loop.EventLoop→winit_core.cursor.CustomCursorSource
- Direction
- winit_orbital.event_loop uses winit_core.cursor, so a change to winit_core.cursor can break winit_orbital.event_loop, while a change to winit_orbital.event_loop can't break winit_core.cursor.
- Position
- Below the diagonal: winit_orbital.event_loop uses a module listed above it, which is the healthy direction.
24→13 winit_orbital.event_loop uses winit_core.window✕
- Connections
- 3 pairs of types, where a type in winit_orbital.event_loop uses a type in winit_core.window.
- The types involved
winit_orbital.event_loop.ActiveEventLoop→winit_core.window.Themewinit_orbital.event_loop.ActiveEventLoop→winit_core.window.WindowAttributeswinit_orbital.event_loop.EventLoop→winit_core.window.WindowId
- Direction
- winit_orbital.event_loop uses winit_core.window, so a change to winit_core.window can break winit_orbital.event_loop, while a change to winit_orbital.event_loop can't break winit_core.window.
- Position
- Below the diagonal: winit_orbital.event_loop uses a module listed above it, which is the healthy direction.
24→14 winit_orbital.event_loop uses winit_core.event_loop✕
- Connections
- 6 pairs of types, where a type in winit_orbital.event_loop uses a type in winit_core.event_loop.
- The types involved
winit_orbital.event_loop.ActiveEventLoop→winit_core.event_loop.ControlFlowwinit_orbital.event_loop.ActiveEventLoop→winit_core.event_loop.DeviceEventswinit_orbital.event_loop.EventLoop→winit_core.event_loop.ControlFlowwinit_orbital.event_loop.EventLoop→winit_core.event_loop.DeviceEventswinit_orbital.event_loop.EventLoop→winit_core.event_loop.EventLoopProviderwinit_orbital.event_loop.EventLoopProxy→winit_core.event_loop.EventLoopProxyProvider
- Direction
- winit_orbital.event_loop uses winit_core.event_loop, so a change to winit_core.event_loop can break winit_orbital.event_loop, while a change to winit_orbital.event_loop can't break winit_core.event_loop.
- Position
- Below the diagonal: winit_orbital.event_loop uses a module listed above it, which is the healthy direction.
24→15 winit_orbital.event_loop uses winit_android.event_loop✕
- Connections
- 2 pairs of types, where a type in winit_orbital.event_loop uses a type in winit_android.event_loop.
- The types involved
winit_orbital.event_loop.ActiveEventLoop→winit_android.event_loop.EventLoopProxywinit_orbital.event_loop.EventLoop→winit_android.event_loop.ActiveEventLoop
- Direction
- winit_orbital.event_loop uses winit_android.event_loop, so a change to winit_android.event_loop can break winit_orbital.event_loop, while a change to winit_orbital.event_loop can't break winit_android.event_loop.
- Position
- Below the diagonal: winit_orbital.event_loop uses a module listed above it, which is the healthy direction.
24→17 winit_orbital.event_loop uses winit.platform_impl.linux✕
- Connections
- 1 pair of types, where a type in winit_orbital.event_loop uses a type in winit.platform_impl.linux.
- The types involved
winit_orbital.event_loop.EventLoop→winit.platform_impl.linux.PlatformSpecificEventLoopAttributes
- Direction
- winit_orbital.event_loop uses winit.platform_impl.linux, so a change to winit.platform_impl.linux can break winit_orbital.event_loop, while a change to winit_orbital.event_loop can't break winit.platform_impl.linux.
- Position
- Below the diagonal: winit_orbital.event_loop uses a module listed above it, which is the healthy direction.
25→1 winit_wayland.window.state uses dpi✕
- Connections
- 5 pairs of types, where a type in winit_wayland.window.state uses a type in dpi.
- The types involved
winit_wayland.window.state.WindowState→dpi.LogicalPositionwinit_wayland.window.state.WindowState→dpi.LogicalSizewinit_wayland.window.state.WindowState→dpi.PhysicalSizewinit_wayland.window.state.WindowState→dpi.Positionwinit_wayland.window.state.WindowState→dpi.Size
- Direction
- winit_wayland.window.state uses dpi, so a change to dpi can break winit_wayland.window.state, while a change to winit_wayland.window.state can't break dpi.
- Position
- Below the diagonal: winit_wayland.window.state uses a module listed above it, which is the healthy direction.
25→7 winit_wayland.window.state uses winit_core.monitor✕
- Connections
- 1 pair of types, where a type in winit_wayland.window.state uses a type in winit_core.monitor.
- The types involved
winit_wayland.window.state.WindowState→winit_core.monitor.Fullscreen
- Direction
- winit_wayland.window.state uses winit_core.monitor, so a change to winit_core.monitor can break winit_wayland.window.state, while a change to winit_wayland.window.state can't break winit_core.monitor.
- Position
- Below the diagonal: winit_wayland.window.state uses a module listed above it, which is the healthy direction.
25→11 winit_wayland.window.state uses winit_core.cursor✕
- Connections
- 1 pair of types, where a type in winit_wayland.window.state uses a type in winit_core.cursor.
- The types involved
winit_wayland.window.state.WindowState→winit_core.cursor.Cursor
- Direction
- winit_wayland.window.state uses winit_core.cursor, so a change to winit_core.cursor can break winit_wayland.window.state, while a change to winit_wayland.window.state can't break winit_core.cursor.
- Position
- Below the diagonal: winit_wayland.window.state uses a module listed above it, which is the healthy direction.
25→12 winit_wayland.window.state uses winit_core.icon✕
- Connections
- 1 pair of types, where a type in winit_wayland.window.state uses a type in winit_core.icon.
- The types involved
winit_wayland.window.state.WindowState→winit_core.icon.Icon
- Direction
- winit_wayland.window.state uses winit_core.icon, so a change to winit_core.icon can break winit_wayland.window.state, while a change to winit_wayland.window.state can't break winit_core.icon.
- Position
- Below the diagonal: winit_wayland.window.state uses a module listed above it, which is the healthy direction.
25→13 winit_wayland.window.state uses winit_core.window✕
- Connections
- 9 pairs of types, where a type in winit_wayland.window.state uses a type in winit_core.window.
- The types involved
winit_wayland.window.state.WindowState→winit_core.window.CursorGrabModewinit_wayland.window.state.WindowState→winit_core.window.ImeCapabilitieswinit_wayland.window.state.WindowState→winit_core.window.ImeRequestwinit_wayland.window.state.WindowState→winit_core.window.ResizeDirectionwinit_wayland.window.state.WindowState→winit_core.window.Themewinit_wayland.window.state.WindowState→winit_core.window.WindowIdwinit_wayland.window.state.WindowState→winit_core.window.WindowTypewinit_wayland.window.state.state$module→winit_core.window.ResizeDirectionwinit_wayland.window.state.state$module→winit_core.window.Theme
- Direction
- winit_wayland.window.state uses winit_core.window, so a change to winit_core.window can break winit_wayland.window.state, while a change to winit_wayland.window.state can't break winit_core.window.
- Position
- Below the diagonal: winit_wayland.window.state uses a module listed above it, which is the healthy direction.
25→15 winit_wayland.window.state uses winit_android.event_loop✕
- Connections
- 2 pairs of types, where a type in winit_wayland.window.state uses a type in winit_android.event_loop.
- The types involved
winit_wayland.window.state.WindowState→winit_android.event_loop.ActiveEventLoopwinit_wayland.window.state.WindowState→winit_android.event_loop.OwnedDisplayHandle
- Direction
- winit_wayland.window.state uses winit_android.event_loop, so a change to winit_android.event_loop can break winit_wayland.window.state, while a change to winit_wayland.window.state can't break winit_android.event_loop.
- Position
- Below the diagonal: winit_wayland.window.state uses a module listed above it, which is the healthy direction.
25→20 winit_wayland.window.state uses winit_wayland.state✕
- Connections
- 2 pairs of types, where a type in winit_wayland.window.state uses a type in winit_wayland.state.
- The types involved
winit_wayland.window.state.WindowState→winit_wayland.state.WindowCompositorUpdatewinit_wayland.window.state.WindowState→winit_wayland.state.WinitState
- Direction
- winit_wayland.window.state uses winit_wayland.state, so a change to winit_wayland.state can break winit_wayland.window.state, while a change to winit_wayland.window.state can't break winit_wayland.state.
- Position
- Below the diagonal: winit_wayland.window.state uses a module listed above it, which is the healthy direction.
26→4 winit_web.cursor uses winit_web.main_thread✕
- Connections
- 5 pairs of types, where a type in winit_web.cursor uses a type in winit_web.main_thread.
- The types involved
winit_web.cursor.CursorHandler→winit_web.main_thread.MainThreadMarkerwinit_web.cursor.CustomCursor→winit_web.main_thread.MainThreadSafewinit_web.cursor.CustomCursorFuture→winit_web.main_thread.MainThreadSafewinit_web.cursor.Inner→winit_web.main_thread.MainThreadMarkerwinit_web.cursor.cursor$module→winit_web.main_thread.MainThreadMarker
- Direction
- winit_web.cursor uses winit_web.main_thread, so a change to winit_web.main_thread can break winit_web.cursor, while a change to winit_web.cursor can't break winit_web.main_thread.
- Position
- Below the diagonal: winit_web.cursor uses a module listed above it, which is the healthy direction.
26→10 winit_web.cursor uses winit_common.xkb✕
- Connections
- 1 pair of types, where a type in winit_web.cursor uses a type in winit_common.xkb.
- The types involved
winit_web.cursor.CustomCursorFuture→winit_common.xkb.Context
- Direction
- winit_web.cursor uses winit_common.xkb, so a change to winit_common.xkb can break winit_web.cursor, while a change to winit_web.cursor can't break winit_common.xkb.
- Position
- Below the diagonal: winit_web.cursor uses a module listed above it, which is the healthy direction.
26→11 winit_web.cursor uses winit_core.cursor✕
- Connections
- 4 pairs of types, where a type in winit_web.cursor uses a type in winit_core.cursor.
- The types involved
winit_web.cursor.CursorHandler→winit_core.cursor.Cursorwinit_web.cursor.CustomCursor→winit_core.cursor.CustomCursorProviderwinit_web.cursor.CustomCursor→winit_core.cursor.CustomCursorSourcewinit_web.cursor.cursor$module→winit_core.cursor.CursorImage
- Direction
- winit_web.cursor uses winit_core.cursor, so a change to winit_core.cursor can break winit_web.cursor, while a change to winit_web.cursor can't break winit_core.cursor.
- Position
- Below the diagonal: winit_web.cursor uses a module listed above it, which is the healthy direction.
26→15 winit_web.cursor uses winit_android.event_loop✕
- Connections
- 2 pairs of types, where a type in winit_web.cursor uses a type in winit_android.event_loop.
- The types involved
winit_web.cursor.CustomCursor→winit_android.event_loop.ActiveEventLoopwinit_web.cursor.cursor$module→winit_android.event_loop.Window
- Direction
- winit_web.cursor uses winit_android.event_loop, so a change to winit_android.event_loop can break winit_web.cursor, while a change to winit_web.cursor can't break winit_android.event_loop.
- Position
- Below the diagonal: winit_web.cursor uses a module listed above it, which is the healthy direction.
26→19 winit_web.cursor uses winit_uikit.window✕
- Connections
- 1 pair of types, where a type in winit_web.cursor uses a type in winit_uikit.window.
- The types involved
winit_web.cursor.CursorHandler→winit_uikit.window.Inner
- Direction
- winit_web.cursor uses winit_uikit.window, so a change to winit_uikit.window can break winit_web.cursor, while a change to winit_web.cursor can't break winit_uikit.window.
- Position
- Below the diagonal: winit_web.cursor uses a module listed above it, which is the healthy direction.
26→21 winit_web.cursor uses winit_web.web_sys.canvas✕
- Connections
- 2 pairs of types, where a type in winit_web.cursor uses a type in winit_web.web_sys.canvas.
- The types involved
winit_web.cursor.CursorHandler→winit_web.web_sys.canvas.Stylewinit_web.cursor.Inner→winit_web.web_sys.canvas.Style
- Direction
- winit_web.cursor uses winit_web.web_sys.canvas, so a change to winit_web.web_sys.canvas can break winit_web.cursor, while a change to winit_web.cursor can't break winit_web.web_sys.canvas.
- Position
- Below the diagonal: winit_web.cursor uses a module listed above it, which is the healthy direction.
27→4 winit_web uses winit_web.main_thread✕
- Connections
- 1 pair of types, where a type in winit_web uses a type in winit_web.main_thread.
- The types involved
winit_web.WindowAttributesWeb→winit_web.main_thread.MainThreadSafe
- Direction
- winit_web uses winit_web.main_thread, so a change to winit_web.main_thread can break winit_web, while a change to winit_web can't break winit_web.main_thread.
- Position
- Below the diagonal: winit_web uses a module listed above it, which is the healthy direction.
27→10 winit_web uses winit_common.xkb✕
- Connections
- 7 pairs of types, where a type in winit_web uses a type in winit_common.xkb.
- The types involved
winit_web.CustomCursorError→winit_common.xkb.Errorwinit_web.CustomCursorFuture→winit_common.xkb.Contextwinit_web.HasMonitorPermissionFuture→winit_common.xkb.Contextwinit_web.MonitorPermissionError→winit_common.xkb.Errorwinit_web.MonitorPermissionFuture→winit_common.xkb.Contextwinit_web.OrientationLockError→winit_common.xkb.Errorwinit_web.OrientationLockFuture→winit_common.xkb.Context
- Direction
- winit_web uses winit_common.xkb, so a change to winit_common.xkb can break winit_web, while a change to winit_web can't break winit_common.xkb.
- Position
- Below the diagonal: winit_web uses a module listed above it, which is the healthy direction.
27→11 winit_web uses winit_core.cursor✕
- Connections
- 1 pair of types, where a type in winit_web uses a type in winit_core.cursor.
- The types involved
winit_web.ActiveEventLoopExtWeb→winit_core.cursor.CustomCursorSource
- Direction
- winit_web uses winit_core.cursor, so a change to winit_core.cursor can break winit_web, while a change to winit_web can't break winit_core.cursor.
- Position
- Below the diagonal: winit_web uses a module listed above it, which is the healthy direction.
27→13 winit_web uses winit_core.window✕
- Connections
- 1 pair of types, where a type in winit_web uses a type in winit_core.window.
- The types involved
winit_web.WindowAttributesWeb→winit_core.window.PlatformWindowAttributes
- Direction
- winit_web uses winit_core.window, so a change to winit_core.window can break winit_web, while a change to winit_web can't break winit_core.window.
- Position
- Below the diagonal: winit_web uses a module listed above it, which is the healthy direction.
27→26 winit_web uses winit_web.cursor✕
- Connections
- 1 pair of types, where a type in winit_web uses a type in winit_web.cursor.
- The types involved
winit_web.ActiveEventLoopExtWeb→winit_web.cursor.CustomCursorFuture
- Direction
- winit_web uses winit_web.cursor, so a change to winit_web.cursor can break winit_web, while a change to winit_web can't break winit_web.cursor.
- Position
- Below the diagonal: winit_web uses a module listed above it, which is the healthy direction.
28→1 winit_win32.window_state uses dpi✕
- Connections
- 4 pairs of types, where a type in winit_win32.window_state uses a type in dpi.
- The types involved
winit_win32.window_state.MouseProperties→dpi.PhysicalPositionwinit_win32.window_state.WindowFlags→dpi.PhysicalSizewinit_win32.window_state.WindowState→dpi.PhysicalSizewinit_win32.window_state.WindowState→dpi.Size
- Direction
- winit_win32.window_state uses dpi, so a change to dpi can break winit_win32.window_state, while a change to winit_win32.window_state can't break dpi.
- Position
- Below the diagonal: winit_win32.window_state uses a module listed above it, which is the healthy direction.
28→2 winit_win32.window_state uses winit_common.xkb.state✕
- Connections
- 1 pair of types, where a type in winit_win32.window_state uses a type in winit_common.xkb.state.
- The types involved
winit_win32.window_state.WindowState→winit_common.xkb.state.ModifiersState
- Direction
- winit_win32.window_state uses winit_common.xkb.state, so a change to winit_common.xkb.state can break winit_win32.window_state, while a change to winit_win32.window_state can't break winit_common.xkb.state.
- Position
- Below the diagonal: winit_win32.window_state uses a module listed above it, which is the healthy direction.
28→7 winit_win32.window_state uses winit_core.monitor✕
- Connections
- 1 pair of types, where a type in winit_win32.window_state uses a type in winit_core.monitor.
- The types involved
winit_win32.window_state.WindowState→winit_core.monitor.Fullscreen
- Direction
- winit_win32.window_state uses winit_core.monitor, so a change to winit_core.monitor can break winit_win32.window_state, while a change to winit_win32.window_state can't break winit_core.monitor.
- Position
- Below the diagonal: winit_win32.window_state uses a module listed above it, which is the healthy direction.
28→12 winit_win32.window_state uses winit_core.icon✕
- Connections
- 1 pair of types, where a type in winit_win32.window_state uses a type in winit_core.icon.
- The types involved
winit_win32.window_state.WindowState→winit_core.icon.Icon
- Direction
- winit_win32.window_state uses winit_core.icon, so a change to winit_core.icon can break winit_win32.window_state, while a change to winit_win32.window_state can't break winit_core.icon.
- Position
- Below the diagonal: winit_win32.window_state uses a module listed above it, which is the healthy direction.
28→13 winit_win32.window_state uses winit_core.window✕
- Connections
- 5 pairs of types, where a type in winit_win32.window_state uses a type in winit_core.window.
- The types involved
winit_win32.window_state.WindowState→winit_core.window.ImeCapabilitieswinit_win32.window_state.WindowState→winit_core.window.Themewinit_win32.window_state.WindowState→winit_core.window.WindowAttributeswinit_win32.window_state.WindowState→winit_core.window.WindowPositionerwinit_win32.window_state.WindowState→winit_core.window.WindowType
- Direction
- winit_win32.window_state uses winit_core.window, so a change to winit_core.window can break winit_win32.window_state, while a change to winit_win32.window_state can't break winit_core.window.
- Position
- Below the diagonal: winit_win32.window_state uses a module listed above it, which is the healthy direction.
28→25 winit_win32.window_state uses winit_wayland.window.state✕
- Connections
- 1 pair of types, where a type in winit_win32.window_state uses a type in winit_wayland.window.state.
- The types involved
winit_win32.window_state.WindowState→winit_wayland.window.state.WindowState
- Direction
- winit_win32.window_state uses winit_wayland.window.state, so a change to winit_wayland.window.state can break winit_win32.window_state, while a change to winit_win32.window_state can't break winit_wayland.window.state.
- Position
- Below the diagonal: winit_win32.window_state uses a module listed above it, which is the healthy direction.
29→11 winit.event_loop uses winit_core.cursor✕
- Connections
- 1 pair of types, where a type in winit.event_loop uses a type in winit_core.cursor.
- The types involved
winit.event_loop.EventLoop→winit_core.cursor.CustomCursorSource
- Direction
- winit.event_loop uses winit_core.cursor, so a change to winit_core.cursor can break winit.event_loop, while a change to winit.event_loop can't break winit_core.cursor.
- Position
- Below the diagonal: winit.event_loop uses a module listed above it, which is the healthy direction.
29→14 winit.event_loop uses winit_core.event_loop✕
- Connections
- 3 pairs of types, where a type in winit.event_loop uses a type in winit_core.event_loop.
- The types involved
winit.event_loop.EventLoop→winit_core.event_loop.ControlFlowwinit.event_loop.EventLoop→winit_core.event_loop.DeviceEventswinit.event_loop.EventLoop→winit_core.event_loop.EventLoopProvider
- Direction
- winit.event_loop uses winit_core.event_loop, so a change to winit_core.event_loop can break winit.event_loop, while a change to winit.event_loop can't break winit_core.event_loop.
- Position
- Below the diagonal: winit.event_loop uses a module listed above it, which is the healthy direction.
29→15 winit.event_loop uses winit_android.event_loop✕
- Connections
- 2 pairs of types, where a type in winit.event_loop uses a type in winit_android.event_loop.
- The types involved
winit.event_loop.EventLoop→winit_android.event_loop.EventLoopProxywinit.event_loop.EventLoop→winit_android.event_loop.OwnedDisplayHandle
- Direction
- winit.event_loop uses winit_android.event_loop, so a change to winit_android.event_loop can break winit.event_loop, while a change to winit.event_loop can't break winit_android.event_loop.
- Position
- Below the diagonal: winit.event_loop uses a module listed above it, which is the healthy direction.
29→17 winit.event_loop uses winit.platform_impl.linux✕
- Connections
- 1 pair of types, where a type in winit.event_loop uses a type in winit.platform_impl.linux.
- The types involved
winit.event_loop.EventLoopBuilder→winit.platform_impl.linux.PlatformSpecificEventLoopAttributes
- Direction
- winit.event_loop uses winit.platform_impl.linux, so a change to winit.platform_impl.linux can break winit.event_loop, while a change to winit.event_loop can't break winit.platform_impl.linux.
- Position
- Below the diagonal: winit.event_loop uses a module listed above it, which is the healthy direction.
29→27 winit.event_loop uses winit_web✕
- Connections
- 5 pairs of types, where a type in winit.event_loop uses a type in winit_web.
- The types involved
winit.event_loop.EventLoop→winit_web.EventLoopExtWebwinit.event_loop.EventLoop→winit_web.HasMonitorPermissionFuturewinit.event_loop.EventLoop→winit_web.MonitorPermissionFuturewinit.event_loop.EventLoop→winit_web.PollStrategywinit.event_loop.EventLoop→winit_web.WaitUntilStrategy
- Direction
- winit.event_loop uses winit_web, so a change to winit_web can break winit.event_loop, while a change to winit.event_loop can't break winit_web.
- Position
- Below the diagonal: winit.event_loop uses a module listed above it, which is the healthy direction.
30→1 winit_web.monitor uses dpi✕
- Connections
- 3 pairs of types, where a type in winit_web.monitor uses a type in dpi.
- The types involved
winit_web.monitor.Inner→dpi.PhysicalPositionwinit_web.monitor.Inner→dpi.PhysicalSizewinit_web.monitor.MonitorHandle→dpi.PhysicalPosition
- Direction
- winit_web.monitor uses dpi, so a change to dpi can break winit_web.monitor, while a change to winit_web.monitor can't break dpi.
- Position
- Below the diagonal: winit_web.monitor uses a module listed above it, which is the healthy direction.
30→4 winit_web.monitor uses winit_web.main_thread✕
- Connections
- 3 pairs of types, where a type in winit_web.monitor uses a type in winit_web.main_thread.
- The types involved
winit_web.monitor.Detailed→winit_web.main_thread.MainThreadMarkerwinit_web.monitor.MonitorHandle→winit_web.main_thread.MainThreadMarkerwinit_web.monitor.MonitorHandler→winit_web.main_thread.MainThreadMarker
- Direction
- winit_web.monitor uses winit_web.main_thread, so a change to winit_web.main_thread can break winit_web.monitor, while a change to winit_web.monitor can't break winit_web.main_thread.
- Position
- Below the diagonal: winit_web.monitor uses a module listed above it, which is the healthy direction.
30→7 winit_web.monitor uses winit_core.monitor✕
- Connections
- 2 pairs of types, where a type in winit_web.monitor uses a type in winit_core.monitor.
- The types involved
winit_web.monitor.MonitorHandle→winit_core.monitor.MonitorHandleProviderwinit_web.monitor.MonitorHandle→winit_core.monitor.VideoMode
- Direction
- winit_web.monitor uses winit_core.monitor, so a change to winit_core.monitor can break winit_web.monitor, while a change to winit_web.monitor can't break winit_core.monitor.
- Position
- Below the diagonal: winit_web.monitor uses a module listed above it, which is the healthy direction.
30→8 winit_web.monitor uses winit_web.async.dispatcher✕
- Connections
- 1 pair of types, where a type in winit_web.monitor uses a type in winit_web.async.dispatcher.
- The types involved
winit_web.monitor.MonitorHandle→winit_web.async.dispatcher.Dispatcher
- Direction
- winit_web.monitor uses winit_web.async.dispatcher, so a change to winit_web.async.dispatcher can break winit_web.monitor, while a change to winit_web.monitor can't break winit_web.async.dispatcher.
- Position
- Below the diagonal: winit_web.monitor uses a module listed above it, which is the healthy direction.
30→9 winit_web.monitor uses winit_appkit.monitor✕
- Connections
- 2 pairs of types, where a type in winit_web.monitor uses a type in winit_appkit.monitor.
- The types involved
winit_web.monitor.Detailed→winit_appkit.monitor.MonitorHandlewinit_web.monitor.MonitorHandler→winit_appkit.monitor.MonitorHandle
- Direction
- winit_web.monitor uses winit_appkit.monitor, so a change to winit_appkit.monitor can break winit_web.monitor, while a change to winit_web.monitor can't break winit_appkit.monitor.
- Position
- Below the diagonal: winit_web.monitor uses a module listed above it, which is the healthy direction.
30→10 winit_web.monitor uses winit_common.xkb✕
- Connections
- 3 pairs of types, where a type in winit_web.monitor uses a type in winit_common.xkb.
- The types involved
winit_web.monitor.HasMonitorPermissionFuture→winit_common.xkb.Contextwinit_web.monitor.MonitorPermissionFuture→winit_common.xkb.Contextwinit_web.monitor.OrientationLockFuture→winit_common.xkb.Context
- Direction
- winit_web.monitor uses winit_common.xkb, so a change to winit_common.xkb can break winit_web.monitor, while a change to winit_web.monitor can't break winit_common.xkb.
- Position
- Below the diagonal: winit_web.monitor uses a module listed above it, which is the healthy direction.
30→15 winit_web.monitor uses winit_android.event_loop✕
- Connections
- 2 pairs of types, where a type in winit_web.monitor uses a type in winit_android.event_loop.
- The types involved
winit_web.monitor.MonitorHandler→winit_android.event_loop.Windowwinit_web.monitor.monitor$module→winit_android.event_loop.Window
- Direction
- winit_web.monitor uses winit_android.event_loop, so a change to winit_android.event_loop can break winit_web.monitor, while a change to winit_web.monitor can't break winit_android.event_loop.
- Position
- Below the diagonal: winit_web.monitor uses a module listed above it, which is the healthy direction.
30→19 winit_web.monitor uses winit_uikit.window✕
- Connections
- 1 pair of types, where a type in winit_web.monitor uses a type in winit_uikit.window.
- The types involved
winit_web.monitor.MonitorHandle→winit_uikit.window.Inner
- Direction
- winit_web.monitor uses winit_uikit.window, so a change to winit_uikit.window can break winit_web.monitor, while a change to winit_web.monitor can't break winit_uikit.window.
- Position
- Below the diagonal: winit_web.monitor uses a module listed above it, which is the healthy direction.
30→23 winit_web.monitor uses winit_appkit.window_delegate✕
- Connections
- 1 pair of types, where a type in winit_web.monitor uses a type in winit_appkit.window_delegate.
- The types involved
winit_web.monitor.MonitorHandler→winit_appkit.window_delegate.State
- Direction
- winit_web.monitor uses winit_appkit.window_delegate, so a change to winit_appkit.window_delegate can break winit_web.monitor, while a change to winit_web.monitor can't break winit_appkit.window_delegate.
- Position
- Below the diagonal: winit_web.monitor uses a module listed above it, which is the healthy direction.
30→27 winit_web.monitor uses winit_web✕
- Connections
- 6 pairs of types, where a type in winit_web.monitor uses a type in winit_web.
- The types involved
winit_web.monitor.Inner→winit_web.OrientationDatawinit_web.monitor.MonitorHandle→winit_web.OrientationDatawinit_web.monitor.MonitorHandle→winit_web.OrientationLockwinit_web.monitor.MonitorHandle→winit_web.OrientationLockFuturewinit_web.monitor.MonitorHandler→winit_web.HasMonitorPermissionFuturewinit_web.monitor.MonitorHandler→winit_web.MonitorPermissionFuture
- Direction
- winit_web.monitor uses winit_web, so a change to winit_web can break winit_web.monitor, while a change to winit_web.monitor can't break winit_web.
- Position
- Below the diagonal: winit_web.monitor uses a module listed above it, which is the healthy direction.
30→35 winit_web.monitor uses winit_web.event_loop.runner part of a loop✕
- Connections
- 3 pairs of types, where a type in winit_web.monitor uses a type in winit_web.event_loop.runner.
- The types involved
winit_web.monitor.Detailed→winit_web.event_loop.runner.WeakSharedwinit_web.monitor.MonitorHandler→winit_web.event_loop.runner.WeakSharedwinit_web.monitor.MonitorPermissionFuture→winit_web.event_loop.runner.WeakShared
- Direction
- winit_web.monitor uses winit_web.event_loop.runner, so a change to winit_web.event_loop.runner can break winit_web.monitor, while a change to winit_web.monitor can't break winit_web.event_loop.runner.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→1 winit_win32.event_loop uses dpi✕
- Connections
- 1 pair of types, where a type in winit_win32.event_loop uses a type in dpi.
- The types involved
winit_win32.event_loop.event_loop$module→dpi.PhysicalSize
- Direction
- winit_win32.event_loop uses dpi, so a change to dpi can break winit_win32.event_loop, while a change to winit_win32.event_loop can't break dpi.
- Position
- Below the diagonal: winit_win32.event_loop uses a module listed above it, which is the healthy direction.
31→5 winit_win32.event_loop uses winit_core.data_transfer✕
- Connections
- 1 pair of types, where a type in winit_win32.event_loop uses a type in winit_core.data_transfer.
- The types involved
winit_win32.event_loop.ActiveEventLoop→winit_core.data_transfer.DataTransferId
- Direction
- winit_win32.event_loop uses winit_core.data_transfer, so a change to winit_core.data_transfer can break winit_win32.event_loop, while a change to winit_win32.event_loop can't break winit_core.data_transfer.
- Position
- Below the diagonal: winit_win32.event_loop uses a module listed above it, which is the healthy direction.
31→6 winit_win32.event_loop uses winit_core.event✕
- Connections
- 5 pairs of types, where a type in winit_win32.event_loop uses a type in winit_core.event.
- The types involved
winit_win32.event_loop.ThreadMsgTargetData→winit_core.event.DeviceEventwinit_win32.event_loop.ThreadMsgTargetData→winit_core.event.DeviceIdwinit_win32.event_loop.WindowData→winit_core.event.WindowEventwinit_win32.event_loop.event_loop$module→winit_core.event.Forcewinit_win32.event_loop.event_loop$module→winit_core.event.TabletToolButton
- Direction
- winit_win32.event_loop uses winit_core.event, so a change to winit_core.event can break winit_win32.event_loop, while a change to winit_win32.event_loop can't break winit_core.event.
- Position
- Below the diagonal: winit_win32.event_loop uses a module listed above it, which is the healthy direction.
31→11 winit_win32.event_loop uses winit_core.cursor✕
- Connections
- 2 pairs of types, where a type in winit_win32.event_loop uses a type in winit_core.cursor.
- The types involved
winit_win32.event_loop.ActiveEventLoop→winit_core.cursor.CustomCursorSourcewinit_win32.event_loop.EventLoop→winit_core.cursor.CustomCursorSource
- Direction
- winit_win32.event_loop uses winit_core.cursor, so a change to winit_core.cursor can break winit_win32.event_loop, while a change to winit_win32.event_loop can't break winit_core.cursor.
- Position
- Below the diagonal: winit_win32.event_loop uses a module listed above it, which is the healthy direction.
31→13 winit_win32.event_loop uses winit_core.window✕
- Connections
- 3 pairs of types, where a type in winit_win32.event_loop uses a type in winit_core.window.
- The types involved
winit_win32.event_loop.ActiveEventLoop→winit_core.window.Themewinit_win32.event_loop.ActiveEventLoop→winit_core.window.WindowAttributeswinit_win32.event_loop.ActiveEventLoop→winit_core.window.WindowId
- Direction
- winit_win32.event_loop uses winit_core.window, so a change to winit_core.window can break winit_win32.event_loop, while a change to winit_win32.event_loop can't break winit_core.window.
- Position
- Below the diagonal: winit_win32.event_loop uses a module listed above it, which is the healthy direction.
31→14 winit_win32.event_loop uses winit_core.event_loop✕
- Connections
- 8 pairs of types, where a type in winit_win32.event_loop uses a type in winit_core.event_loop.
- The types involved
winit_win32.event_loop.ActiveEventLoop→winit_core.event_loop.ControlFlowwinit_win32.event_loop.ActiveEventLoop→winit_core.event_loop.DeviceEventswinit_win32.event_loop.ActiveEventLoop→winit_core.event_loop.DragIconwinit_win32.event_loop.EventLoop→winit_core.event_loop.ControlFlowwinit_win32.event_loop.EventLoop→winit_core.event_loop.DeviceEventswinit_win32.event_loop.EventLoop→winit_core.event_loop.EventLoopProviderwinit_win32.event_loop.EventLoopProxy→winit_core.event_loop.EventLoopProxyProviderwinit_win32.event_loop.event_loop$module→winit_core.event_loop.ControlFlow
- Direction
- winit_win32.event_loop uses winit_core.event_loop, so a change to winit_core.event_loop can break winit_win32.event_loop, while a change to winit_win32.event_loop can't break winit_core.event_loop.
- Position
- Below the diagonal: winit_win32.event_loop uses a module listed above it, which is the healthy direction.
31→17 winit_win32.event_loop uses winit.platform_impl.linux✕
- Connections
- 1 pair of types, where a type in winit_win32.event_loop uses a type in winit.platform_impl.linux.
- The types involved
winit_win32.event_loop.EventLoop→winit.platform_impl.linux.PlatformSpecificEventLoopAttributes
- Direction
- winit_win32.event_loop uses winit.platform_impl.linux, so a change to winit.platform_impl.linux can break winit_win32.event_loop, while a change to winit_win32.event_loop can't break winit.platform_impl.linux.
- Position
- Below the diagonal: winit_win32.event_loop uses a module listed above it, which is the healthy direction.
31→25 winit_win32.event_loop uses winit_wayland.window.state✕
- Connections
- 2 pairs of types, where a type in winit_win32.event_loop uses a type in winit_wayland.window.state.
- The types involved
winit_win32.event_loop.WindowData→winit_wayland.window.state.WindowStatewinit_win32.event_loop.event_loop$module→winit_wayland.window.state.WindowState
- Direction
- winit_win32.event_loop uses winit_wayland.window.state, so a change to winit_wayland.window.state can break winit_win32.event_loop, while a change to winit_win32.event_loop can't break winit_wayland.window.state.
- Position
- Below the diagonal: winit_win32.event_loop uses a module listed above it, which is the healthy direction.
31→28 winit_win32.event_loop uses winit_win32.window_state✕
- Connections
- 1 pair of types, where a type in winit_win32.event_loop uses a type in winit_win32.window_state.
- The types involved
winit_win32.event_loop.event_loop$module→winit_win32.window_state.WindowFlags
- Direction
- winit_win32.event_loop uses winit_win32.window_state, so a change to winit_win32.window_state can break winit_win32.event_loop, while a change to winit_win32.event_loop can't break winit_win32.window_state.
- Position
- Below the diagonal: winit_win32.event_loop uses a module listed above it, which is the healthy direction.
31→36 winit_win32.event_loop uses winit_win32.event_loop.runner part of a loop✕
- Connections
- 5 pairs of types, where a type in winit_win32.event_loop uses a type in winit_win32.event_loop.runner.
- The types involved
winit_win32.event_loop.ActiveEventLoop→winit_win32.event_loop.runner.EventLoopRunnerwinit_win32.event_loop.EventLoop→winit_win32.event_loop.runner.EventLoopRunnerwinit_win32.event_loop.ThreadMsgTargetData→winit_win32.event_loop.runner.EventLoopRunnerwinit_win32.event_loop.WindowData→winit_win32.event_loop.runner.EventLoopRunnerwinit_win32.event_loop.event_loop$module→winit_win32.event_loop.runner.EventLoopRunner
- Direction
- winit_win32.event_loop uses winit_win32.event_loop.runner, so a change to winit_win32.event_loop.runner can break winit_win32.event_loop, while a change to winit_win32.event_loop can't break winit_win32.event_loop.runner.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→38 winit_win32.event_loop uses winit_win32.data_transfer part of a loop✕
- Connections
- 1 pair of types, where a type in winit_win32.event_loop uses a type in winit_win32.data_transfer.
- The types involved
winit_win32.event_loop.WindowData→winit_win32.data_transfer.FileDropHandler
- Direction
- winit_win32.event_loop uses winit_win32.data_transfer, so a change to winit_win32.data_transfer can break winit_win32.event_loop, while a change to winit_win32.event_loop can't break winit_win32.data_transfer.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→5 winit_wayland.event_loop uses winit_core.data_transfer✕
- Connections
- 1 pair of types, where a type in winit_wayland.event_loop uses a type in winit_core.data_transfer.
- The types involved
winit_wayland.event_loop.ActiveEventLoop→winit_core.data_transfer.DataTransferId
- Direction
- winit_wayland.event_loop uses winit_core.data_transfer, so a change to winit_core.data_transfer can break winit_wayland.event_loop, while a change to winit_wayland.event_loop can't break winit_core.data_transfer.
- Position
- Below the diagonal: winit_wayland.event_loop uses a module listed above it, which is the healthy direction.
32→6 winit_wayland.event_loop uses winit_core.event✕
- Connections
- 1 pair of types, where a type in winit_wayland.event_loop uses a type in winit_core.event.
- The types involved
winit_wayland.event_loop.EventLoop→winit_core.event.StartCause
- Direction
- winit_wayland.event_loop uses winit_core.event, so a change to winit_core.event can break winit_wayland.event_loop, while a change to winit_wayland.event_loop can't break winit_core.event.
- Position
- Below the diagonal: winit_wayland.event_loop uses a module listed above it, which is the healthy direction.
32→11 winit_wayland.event_loop uses winit_core.cursor✕
- Connections
- 2 pairs of types, where a type in winit_wayland.event_loop uses a type in winit_core.cursor.
- The types involved
winit_wayland.event_loop.ActiveEventLoop→winit_core.cursor.CustomCursorSourcewinit_wayland.event_loop.EventLoop→winit_core.cursor.CustomCursorSource
- Direction
- winit_wayland.event_loop uses winit_core.cursor, so a change to winit_core.cursor can break winit_wayland.event_loop, while a change to winit_wayland.event_loop can't break winit_core.cursor.
- Position
- Below the diagonal: winit_wayland.event_loop uses a module listed above it, which is the healthy direction.
32→13 winit_wayland.event_loop uses winit_core.window✕
- Connections
- 4 pairs of types, where a type in winit_wayland.event_loop uses a type in winit_core.window.
- The types involved
winit_wayland.event_loop.ActiveEventLoop→winit_core.window.Themewinit_wayland.event_loop.ActiveEventLoop→winit_core.window.WindowAttributeswinit_wayland.event_loop.ActiveEventLoop→winit_core.window.WindowIdwinit_wayland.event_loop.EventLoop→winit_core.window.WindowId
- Direction
- winit_wayland.event_loop uses winit_core.window, so a change to winit_core.window can break winit_wayland.event_loop, while a change to winit_wayland.event_loop can't break winit_core.window.
- Position
- Below the diagonal: winit_wayland.event_loop uses a module listed above it, which is the healthy direction.
32→14 winit_wayland.event_loop uses winit_core.event_loop✕
- Connections
- 6 pairs of types, where a type in winit_wayland.event_loop uses a type in winit_core.event_loop.
- The types involved
winit_wayland.event_loop.ActiveEventLoop→winit_core.event_loop.ControlFlowwinit_wayland.event_loop.ActiveEventLoop→winit_core.event_loop.DeviceEventswinit_wayland.event_loop.ActiveEventLoop→winit_core.event_loop.DragIconwinit_wayland.event_loop.EventLoop→winit_core.event_loop.ControlFlowwinit_wayland.event_loop.EventLoop→winit_core.event_loop.DeviceEventswinit_wayland.event_loop.EventLoop→winit_core.event_loop.EventLoopProvider
- Direction
- winit_wayland.event_loop uses winit_core.event_loop, so a change to winit_core.event_loop can break winit_wayland.event_loop, while a change to winit_wayland.event_loop can't break winit_core.event_loop.
- Position
- Below the diagonal: winit_wayland.event_loop uses a module listed above it, which is the healthy direction.
32→15 winit_wayland.event_loop uses winit_android.event_loop✕
- Connections
- 3 pairs of types, where a type in winit_wayland.event_loop uses a type in winit_android.event_loop.
- The types involved
winit_wayland.event_loop.ActiveEventLoop→winit_android.event_loop.OwnedDisplayHandlewinit_wayland.event_loop.EventLoop→winit_android.event_loop.ActiveEventLoopwinit_wayland.event_loop.EventLoop→winit_android.event_loop.OwnedDisplayHandle
- Direction
- winit_wayland.event_loop uses winit_android.event_loop, so a change to winit_android.event_loop can break winit_wayland.event_loop, while a change to winit_wayland.event_loop can't break winit_android.event_loop.
- Position
- Below the diagonal: winit_wayland.event_loop uses a module listed above it, which is the healthy direction.
32→20 winit_wayland.event_loop uses winit_wayland.state✕
- Connections
- 3 pairs of types, where a type in winit_wayland.event_loop uses a type in winit_wayland.state.
- The types involved
winit_wayland.event_loop.ActiveEventLoop→winit_wayland.state.WinitStatewinit_wayland.event_loop.EventLoop→winit_wayland.state.WindowCompositorUpdatewinit_wayland.event_loop.EventLoop→winit_wayland.state.WinitState
- Direction
- winit_wayland.event_loop uses winit_wayland.state, so a change to winit_wayland.state can break winit_wayland.event_loop, while a change to winit_wayland.event_loop can't break winit_wayland.state.
- Position
- Below the diagonal: winit_wayland.event_loop uses a module listed above it, which is the healthy direction.
32→29 winit_wayland.event_loop uses winit.event_loop✕
- Connections
- 1 pair of types, where a type in winit_wayland.event_loop uses a type in winit.event_loop.
- The types involved
winit_wayland.event_loop.EventLoop→winit.event_loop.EventLoop
- Direction
- winit_wayland.event_loop uses winit.event_loop, so a change to winit.event_loop can break winit_wayland.event_loop, while a change to winit_wayland.event_loop can't break winit.event_loop.
- Position
- Below the diagonal: winit_wayland.event_loop uses a module listed above it, which is the healthy direction.
33→1 winit_web.window uses dpi✕
- Connections
- 5 pairs of types, where a type in winit_web.window uses a type in dpi.
- The types involved
winit_web.window.Window→dpi.PhysicalInsetswinit_web.window.Window→dpi.PhysicalPositionwinit_web.window.Window→dpi.PhysicalSizewinit_web.window.Window→dpi.Positionwinit_web.window.Window→dpi.Size
- Direction
- winit_web.window uses dpi, so a change to dpi can break winit_web.window, while a change to winit_web.window can't break dpi.
- Position
- Below the diagonal: winit_web.window uses a module listed above it, which is the healthy direction.
33→7 winit_web.window uses winit_core.monitor✕
- Connections
- 1 pair of types, where a type in winit_web.window uses a type in winit_core.monitor.
- The types involved
winit_web.window.Window→winit_core.monitor.Fullscreen
- Direction
- winit_web.window uses winit_core.monitor, so a change to winit_core.monitor can break winit_web.window, while a change to winit_web.window can't break winit_core.monitor.
- Position
- Below the diagonal: winit_web.window uses a module listed above it, which is the healthy direction.
33→8 winit_web.window uses winit_web.async.dispatcher✕
- Connections
- 1 pair of types, where a type in winit_web.window uses a type in winit_web.async.dispatcher.
- The types involved
winit_web.window.Window→winit_web.async.dispatcher.Dispatcher
- Direction
- winit_web.window uses winit_web.async.dispatcher, so a change to winit_web.async.dispatcher can break winit_web.window, while a change to winit_web.window can't break winit_web.async.dispatcher.
- Position
- Below the diagonal: winit_web.window uses a module listed above it, which is the healthy direction.
33→11 winit_web.window uses winit_core.cursor✕
- Connections
- 1 pair of types, where a type in winit_web.window uses a type in winit_core.cursor.
- The types involved
winit_web.window.Window→winit_core.cursor.Cursor
- Direction
- winit_web.window uses winit_core.cursor, so a change to winit_core.cursor can break winit_web.window, while a change to winit_web.window can't break winit_core.cursor.
- Position
- Below the diagonal: winit_web.window uses a module listed above it, which is the healthy direction.
33→12 winit_web.window uses winit_core.icon✕
- Connections
- 1 pair of types, where a type in winit_web.window uses a type in winit_core.icon.
- The types involved
winit_web.window.Window→winit_core.icon.Icon
- Direction
- winit_web.window uses winit_core.icon, so a change to winit_core.icon can break winit_web.window, while a change to winit_web.window can't break winit_core.icon.
- Position
- Below the diagonal: winit_web.window uses a module listed above it, which is the healthy direction.
33→13 winit_web.window uses winit_core.window✕
- Connections
- 12 pairs of types, where a type in winit_web.window uses a type in winit_core.window.
- The types involved
winit_web.window.Inner→winit_core.window.WindowIdwinit_web.window.Window→winit_core.window.CursorGrabModewinit_web.window.Window→winit_core.window.ImeCapabilitieswinit_web.window.Window→winit_core.window.ImeRequestwinit_web.window.Window→winit_core.window.ResizeDirectionwinit_web.window.Window→winit_core.window.Themewinit_web.window.Window→winit_core.window.UserAttentionTypewinit_web.window.Window→winit_core.window.WindowAttributeswinit_web.window.Window→winit_core.window.WindowButtonswinit_web.window.Window→winit_core.window.WindowIdwinit_web.window.Window→winit_core.window.WindowLevelwinit_web.window.Window→winit_core.window.WindowType
- Direction
- winit_web.window uses winit_core.window, so a change to winit_core.window can break winit_web.window, while a change to winit_web.window can't break winit_core.window.
- Position
- Below the diagonal: winit_web.window uses a module listed above it, which is the healthy direction.
33→15 winit_web.window uses winit_android.event_loop✕
- Connections
- 2 pairs of types, where a type in winit_web.window uses a type in winit_android.event_loop.
- The types involved
winit_web.window.Inner→winit_android.event_loop.Windowwinit_web.window.Window→winit_android.event_loop.ActiveEventLoop
- Direction
- winit_web.window uses winit_android.event_loop, so a change to winit_android.event_loop can break winit_web.window, while a change to winit_web.window can't break winit_android.event_loop.
- Position
- Below the diagonal: winit_web.window uses a module listed above it, which is the healthy direction.
33→21 winit_web.window uses winit_web.web_sys.canvas✕
- Connections
- 1 pair of types, where a type in winit_web.window uses a type in winit_web.web_sys.canvas.
- The types involved
winit_web.window.Inner→winit_web.web_sys.canvas.Canvas
- Direction
- winit_web.window uses winit_web.web_sys.canvas, so a change to winit_web.web_sys.canvas can break winit_web.window, while a change to winit_web.window can't break winit_web.web_sys.canvas.
- Position
- Below the diagonal: winit_web.window uses a module listed above it, which is the healthy direction.
33→30 winit_web.window uses winit_web.monitor✕
- Connections
- 1 pair of types, where a type in winit_web.window uses a type in winit_web.monitor.
- The types involved
winit_web.window.Inner→winit_web.monitor.MonitorHandler
- Direction
- winit_web.window uses winit_web.monitor, so a change to winit_web.monitor can break winit_web.window, while a change to winit_web.window can't break winit_web.monitor.
- Position
- Below the diagonal: winit_web.window uses a module listed above it, which is the healthy direction.
34→9 winit_x11.xdisplay uses winit_appkit.monitor✕
- Connections
- 1 pair of types, where a type in winit_x11.xdisplay uses a type in winit_appkit.monitor.
- The types involved
winit_x11.xdisplay.XConnection→winit_appkit.monitor.MonitorHandle
- Direction
- winit_x11.xdisplay uses winit_appkit.monitor, so a change to winit_appkit.monitor can break winit_x11.xdisplay, while a change to winit_x11.xdisplay can't break winit_appkit.monitor.
- Position
- Below the diagonal: winit_x11.xdisplay uses a module listed above it, which is the healthy direction.
34→10 winit_x11.xdisplay uses winit_common.xkb✕
- Connections
- 3 pairs of types, where a type in winit_x11.xdisplay uses a type in winit_common.xkb.
- The types involved
winit_x11.xdisplay.WrapConnectError→winit_common.xkb.Errorwinit_x11.xdisplay.XError→winit_common.xkb.Errorwinit_x11.xdisplay.XNotSupported→winit_common.xkb.Error
- Direction
- winit_x11.xdisplay uses winit_common.xkb, so a change to winit_common.xkb can break winit_x11.xdisplay, while a change to winit_x11.xdisplay can't break winit_common.xkb.
- Position
- Below the diagonal: winit_x11.xdisplay uses a module listed above it, which is the healthy direction.
34→11 winit_x11.xdisplay uses winit_core.cursor✕
- Connections
- 1 pair of types, where a type in winit_x11.xdisplay uses a type in winit_core.cursor.
- The types involved
winit_x11.xdisplay.XConnection→winit_core.cursor.Cursor
- Direction
- winit_x11.xdisplay uses winit_core.cursor, so a change to winit_core.cursor can break winit_x11.xdisplay, while a change to winit_x11.xdisplay can't break winit_core.cursor.
- Position
- Below the diagonal: winit_x11.xdisplay uses a module listed above it, which is the healthy direction.
34→15 winit_x11.xdisplay uses winit_android.event_loop✕
- Connections
- 1 pair of types, where a type in winit_x11.xdisplay uses a type in winit_android.event_loop.
- The types involved
winit_x11.xdisplay.XConnection→winit_android.event_loop.Window
- Direction
- winit_x11.xdisplay uses winit_android.event_loop, so a change to winit_android.event_loop can break winit_x11.xdisplay, while a change to winit_x11.xdisplay can't break winit_android.event_loop.
- Position
- Below the diagonal: winit_x11.xdisplay uses a module listed above it, which is the healthy direction.
34→30 winit_x11.xdisplay uses winit_web.monitor✕
- Connections
- 1 pair of types, where a type in winit_x11.xdisplay uses a type in winit_web.monitor.
- The types involved
winit_x11.xdisplay.XConnection→winit_web.monitor.Screen
- Direction
- winit_x11.xdisplay uses winit_web.monitor, so a change to winit_web.monitor can break winit_x11.xdisplay, while a change to winit_x11.xdisplay can't break winit_web.monitor.
- Position
- Below the diagonal: winit_x11.xdisplay uses a module listed above it, which is the healthy direction.
35→4 winit_web.event_loop.runner uses winit_web.main_thread✕
- Connections
- 2 pairs of types, where a type in winit_web.event_loop.runner uses a type in winit_web.main_thread.
- The types involved
winit_web.event_loop.runner.Execution→winit_web.main_thread.MainThreadMarkerwinit_web.event_loop.runner.Shared→winit_web.main_thread.MainThreadMarker
- Direction
- winit_web.event_loop.runner uses winit_web.main_thread, so a change to winit_web.main_thread can break winit_web.event_loop.runner, while a change to winit_web.event_loop.runner can't break winit_web.main_thread.
- Position
- Below the diagonal: winit_web.event_loop.runner uses a module listed above it, which is the healthy direction.
35→6 winit_web.event_loop.runner uses winit_core.event✕
- Connections
- 1 pair of types, where a type in winit_web.event_loop.runner uses a type in winit_core.event.
- The types involved
winit_web.event_loop.runner.Runner→winit_core.event.StartCause
- Direction
- winit_web.event_loop.runner uses winit_core.event, so a change to winit_core.event can break winit_web.event_loop.runner, while a change to winit_web.event_loop.runner can't break winit_core.event.
- Position
- Below the diagonal: winit_web.event_loop.runner uses a module listed above it, which is the healthy direction.
35→8 winit_web.event_loop.runner uses winit_web.async.dispatcher✕
- Connections
- 1 pair of types, where a type in winit_web.event_loop.runner uses a type in winit_web.async.dispatcher.
- The types involved
winit_web.event_loop.runner.Shared→winit_web.async.dispatcher.DispatchRunner
- Direction
- winit_web.event_loop.runner uses winit_web.async.dispatcher, so a change to winit_web.async.dispatcher can break winit_web.event_loop.runner, while a change to winit_web.event_loop.runner can't break winit_web.async.dispatcher.
- Position
- Below the diagonal: winit_web.event_loop.runner uses a module listed above it, which is the healthy direction.
35→13 winit_web.event_loop.runner uses winit_core.window✕
- Connections
- 1 pair of types, where a type in winit_web.event_loop.runner uses a type in winit_core.window.
- The types involved
winit_web.event_loop.runner.Shared→winit_core.window.WindowId
- Direction
- winit_web.event_loop.runner uses winit_core.window, so a change to winit_core.window can break winit_web.event_loop.runner, while a change to winit_web.event_loop.runner can't break winit_core.window.
- Position
- Below the diagonal: winit_web.event_loop.runner uses a module listed above it, which is the healthy direction.
35→14 winit_web.event_loop.runner uses winit_core.event_loop✕
- Connections
- 4 pairs of types, where a type in winit_web.event_loop.runner uses a type in winit_core.event_loop.
- The types involved
winit_web.event_loop.runner.Execution→winit_core.event_loop.ControlFlowwinit_web.event_loop.runner.Execution→winit_core.event_loop.DeviceEventswinit_web.event_loop.runner.Shared→winit_core.event_loop.ControlFlowwinit_web.event_loop.runner.Shared→winit_core.event_loop.DeviceEvents
- Direction
- winit_web.event_loop.runner uses winit_core.event_loop, so a change to winit_core.event_loop can break winit_web.event_loop.runner, while a change to winit_web.event_loop.runner can't break winit_core.event_loop.
- Position
- Below the diagonal: winit_web.event_loop.runner uses a module listed above it, which is the healthy direction.
35→15 winit_web.event_loop.runner uses winit_android.event_loop✕
- Connections
- 6 pairs of types, where a type in winit_web.event_loop.runner uses a type in winit_android.event_loop.
- The types involved
winit_web.event_loop.runner.Execution→winit_android.event_loop.EventLoopProxywinit_web.event_loop.runner.Execution→winit_android.event_loop.Windowwinit_web.event_loop.runner.Runner→winit_android.event_loop.ActiveEventLoopwinit_web.event_loop.runner.Shared→winit_android.event_loop.ActiveEventLoopwinit_web.event_loop.runner.Shared→winit_android.event_loop.EventLoopProxywinit_web.event_loop.runner.Shared→winit_android.event_loop.Window
- Direction
- winit_web.event_loop.runner uses winit_android.event_loop, so a change to winit_android.event_loop can break winit_web.event_loop.runner, while a change to winit_web.event_loop.runner can't break winit_android.event_loop.
- Position
- Below the diagonal: winit_web.event_loop.runner uses a module listed above it, which is the healthy direction.
35→23 winit_web.event_loop.runner uses winit_appkit.window_delegate✕
- Connections
- 1 pair of types, where a type in winit_web.event_loop.runner uses a type in winit_appkit.window_delegate.
- The types involved
winit_web.event_loop.runner.Runner→winit_appkit.window_delegate.State
- Direction
- winit_web.event_loop.runner uses winit_appkit.window_delegate, so a change to winit_appkit.window_delegate can break winit_web.event_loop.runner, while a change to winit_web.event_loop.runner can't break winit_appkit.window_delegate.
- Position
- Below the diagonal: winit_web.event_loop.runner uses a module listed above it, which is the healthy direction.
35→27 winit_web.event_loop.runner uses winit_web✕
- Connections
- 4 pairs of types, where a type in winit_web.event_loop.runner uses a type in winit_web.
- The types involved
winit_web.event_loop.runner.Execution→winit_web.PollStrategywinit_web.event_loop.runner.Execution→winit_web.WaitUntilStrategywinit_web.event_loop.runner.Shared→winit_web.PollStrategywinit_web.event_loop.runner.Shared→winit_web.WaitUntilStrategy
- Direction
- winit_web.event_loop.runner uses winit_web, so a change to winit_web can break winit_web.event_loop.runner, while a change to winit_web.event_loop.runner can't break winit_web.
- Position
- Below the diagonal: winit_web.event_loop.runner uses a module listed above it, which is the healthy direction.
35→30 winit_web.event_loop.runner uses winit_web.monitor✕
- Connections
- 2 pairs of types, where a type in winit_web.event_loop.runner uses a type in winit_web.monitor.
- The types involved
winit_web.event_loop.runner.Execution→winit_web.monitor.MonitorHandlerwinit_web.event_loop.runner.Shared→winit_web.monitor.MonitorHandler
- Direction
- winit_web.event_loop.runner uses winit_web.monitor, so a change to winit_web.monitor can break winit_web.event_loop.runner, while a change to winit_web.event_loop.runner can't break winit_web.monitor.
- Position
- Below the diagonal: winit_web.event_loop.runner uses a module listed above it, which is the healthy direction.
35→32 winit_web.event_loop.runner uses winit_wayland.event_loop✕
- Connections
- 2 pairs of types, where a type in winit_web.event_loop.runner uses a type in winit_wayland.event_loop.
- The types involved
winit_web.event_loop.runner.Runner→winit_wayland.event_loop.Eventwinit_web.event_loop.runner.Shared→winit_wayland.event_loop.Event
- Direction
- winit_web.event_loop.runner uses winit_wayland.event_loop, so a change to winit_wayland.event_loop can break winit_web.event_loop.runner, while a change to winit_web.event_loop.runner can't break winit_wayland.event_loop.
- Position
- Below the diagonal: winit_web.event_loop.runner uses a module listed above it, which is the healthy direction.
36→5 winit_win32.event_loop.runner uses winit_core.data_transfer✕
- Connections
- 3 pairs of types, where a type in winit_win32.event_loop.runner uses a type in winit_core.data_transfer.
- The types involved
winit_win32.event_loop.runner.EventLoopRunner→winit_core.data_transfer.DataTransferIdwinit_win32.event_loop.runner.PendingDrag→winit_core.data_transfer.DataTransferIdwinit_win32.event_loop.runner.SourceDrag→winit_core.data_transfer.DataTransferId
- Direction
- winit_win32.event_loop.runner uses winit_core.data_transfer, so a change to winit_core.data_transfer can break winit_win32.event_loop.runner, while a change to winit_win32.event_loop.runner can't break winit_core.data_transfer.
- Position
- Below the diagonal: winit_win32.event_loop.runner uses a module listed above it, which is the healthy direction.
36→13 winit_win32.event_loop.runner uses winit_core.window✕
- Connections
- 2 pairs of types, where a type in winit_win32.event_loop.runner uses a type in winit_core.window.
- The types involved
winit_win32.event_loop.runner.EventLoopRunner→winit_core.window.WindowIdwinit_win32.event_loop.runner.PendingDrag→winit_core.window.WindowId
- Direction
- winit_win32.event_loop.runner uses winit_core.window, so a change to winit_core.window can break winit_win32.event_loop.runner, while a change to winit_win32.event_loop.runner can't break winit_core.window.
- Position
- Below the diagonal: winit_win32.event_loop.runner uses a module listed above it, which is the healthy direction.
36→14 winit_win32.event_loop.runner uses winit_core.event_loop✕
- Connections
- 1 pair of types, where a type in winit_win32.event_loop.runner uses a type in winit_core.event_loop.
- The types involved
winit_win32.event_loop.runner.EventLoopRunner→winit_core.event_loop.ControlFlow
- Direction
- winit_win32.event_loop.runner uses winit_core.event_loop, so a change to winit_core.event_loop can break winit_win32.event_loop.runner, while a change to winit_win32.event_loop.runner can't break winit_core.event_loop.
- Position
- Below the diagonal: winit_win32.event_loop.runner uses a module listed above it, which is the healthy direction.
36→16 winit_win32.event_loop.runner uses winit_appkit.data_transfer✕
- Connections
- 1 pair of types, where a type in winit_win32.event_loop.runner uses a type in winit_appkit.data_transfer.
- The types involved
winit_win32.event_loop.runner.EventLoopRunner→winit_appkit.data_transfer.DataTransferState
- Direction
- winit_win32.event_loop.runner uses winit_appkit.data_transfer, so a change to winit_appkit.data_transfer can break winit_win32.event_loop.runner, while a change to winit_win32.event_loop.runner can't break winit_appkit.data_transfer.
- Position
- Below the diagonal: winit_win32.event_loop.runner uses a module listed above it, which is the healthy direction.
36→31 winit_win32.event_loop.runner uses winit_win32.event_loop✕
- Connections
- 1 pair of types, where a type in winit_win32.event_loop.runner uses a type in winit_win32.event_loop.
- The types involved
winit_win32.event_loop.runner.EventLoopRunner→winit_win32.event_loop.EventLoopThreadExecutor
- Direction
- winit_win32.event_loop.runner uses winit_win32.event_loop, so a change to winit_win32.event_loop can break winit_win32.event_loop.runner, while a change to winit_win32.event_loop.runner can't break winit_win32.event_loop.
- Position
- Below the diagonal: winit_win32.event_loop.runner uses a module listed above it, which is the healthy direction.
36→32 winit_win32.event_loop.runner uses winit_wayland.event_loop✕
- Connections
- 1 pair of types, where a type in winit_win32.event_loop.runner uses a type in winit_wayland.event_loop.
- The types involved
winit_win32.event_loop.runner.EventLoopRunner→winit_wayland.event_loop.Event
- Direction
- winit_win32.event_loop.runner uses winit_wayland.event_loop, so a change to winit_wayland.event_loop can break winit_win32.event_loop.runner, while a change to winit_win32.event_loop.runner can't break winit_wayland.event_loop.
- Position
- Below the diagonal: winit_win32.event_loop.runner uses a module listed above it, which is the healthy direction.
36→38 winit_win32.event_loop.runner uses winit_win32.data_transfer part of a loop✕
- Connections
- 2 pairs of types, where a type in winit_win32.event_loop.runner uses a type in winit_win32.data_transfer.
- The types involved
winit_win32.event_loop.runner.PendingDrag→winit_win32.data_transfer.DropSourcewinit_win32.event_loop.runner.PendingDrag→winit_win32.data_transfer.SourceDataObject
- Direction
- winit_win32.event_loop.runner uses winit_win32.data_transfer, so a change to winit_win32.data_transfer can break winit_win32.event_loop.runner, while a change to winit_win32.event_loop.runner can't break winit_win32.data_transfer.
- 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.
37→5 winit_x11.event_loop uses winit_core.data_transfer✕
- Connections
- 1 pair of types, where a type in winit_x11.event_loop uses a type in winit_core.data_transfer.
- The types involved
winit_x11.event_loop.ActiveEventLoop→winit_core.data_transfer.DataTransferId
- Direction
- winit_x11.event_loop uses winit_core.data_transfer, so a change to winit_core.data_transfer can break winit_x11.event_loop, while a change to winit_x11.event_loop can't break winit_core.data_transfer.
- Position
- Below the diagonal: winit_x11.event_loop uses a module listed above it, which is the healthy direction.
37→6 winit_x11.event_loop uses winit_core.event✕
- Connections
- 3 pairs of types, where a type in winit_x11.event_loop uses a type in winit_core.event.
- The types involved
winit_x11.event_loop.ActiveEventLoop→winit_core.event.Imewinit_x11.event_loop.EventLoop→winit_core.event.StartCausewinit_x11.event_loop.event_loop$module→winit_core.event.DeviceId
- Direction
- winit_x11.event_loop uses winit_core.event, so a change to winit_core.event can break winit_x11.event_loop, while a change to winit_x11.event_loop can't break winit_core.event.
- Position
- Below the diagonal: winit_x11.event_loop uses a module listed above it, which is the healthy direction.
37→10 winit_x11.event_loop uses winit_common.xkb✕
- Connections
- 1 pair of types, where a type in winit_x11.event_loop uses a type in winit_common.xkb.
- The types involved
winit_x11.event_loop.X11Error→winit_common.xkb.Error
- Direction
- winit_x11.event_loop uses winit_common.xkb, so a change to winit_common.xkb can break winit_x11.event_loop, while a change to winit_x11.event_loop can't break winit_common.xkb.
- Position
- Below the diagonal: winit_x11.event_loop uses a module listed above it, which is the healthy direction.
37→11 winit_x11.event_loop uses winit_core.cursor✕
- Connections
- 2 pairs of types, where a type in winit_x11.event_loop uses a type in winit_core.cursor.
- The types involved
winit_x11.event_loop.ActiveEventLoop→winit_core.cursor.CustomCursorSourcewinit_x11.event_loop.EventLoop→winit_core.cursor.CustomCursorSource
- Direction
- winit_x11.event_loop uses winit_core.cursor, so a change to winit_core.cursor can break winit_x11.event_loop, while a change to winit_x11.event_loop can't break winit_core.cursor.
- Position
- Below the diagonal: winit_x11.event_loop uses a module listed above it, which is the healthy direction.
37→13 winit_x11.event_loop uses winit_core.window✕
- Connections
- 3 pairs of types, where a type in winit_x11.event_loop uses a type in winit_core.window.
- The types involved
winit_x11.event_loop.ActiveEventLoop→winit_core.window.Themewinit_x11.event_loop.ActiveEventLoop→winit_core.window.WindowAttributeswinit_x11.event_loop.event_loop$module→winit_core.window.WindowId
- Direction
- winit_x11.event_loop uses winit_core.window, so a change to winit_core.window can break winit_x11.event_loop, while a change to winit_x11.event_loop can't break winit_core.window.
- Position
- Below the diagonal: winit_x11.event_loop uses a module listed above it, which is the healthy direction.
37→14 winit_x11.event_loop uses winit_core.event_loop✕
- Connections
- 6 pairs of types, where a type in winit_x11.event_loop uses a type in winit_core.event_loop.
- The types involved
winit_x11.event_loop.ActiveEventLoop→winit_core.event_loop.ControlFlowwinit_x11.event_loop.ActiveEventLoop→winit_core.event_loop.DeviceEventswinit_x11.event_loop.EventLoop→winit_core.event_loop.ControlFlowwinit_x11.event_loop.EventLoop→winit_core.event_loop.DeviceEventswinit_x11.event_loop.EventLoop→winit_core.event_loop.EventLoopProviderwinit_x11.event_loop.EventLoopProxy→winit_core.event_loop.EventLoopProxyProvider
- Direction
- winit_x11.event_loop uses winit_core.event_loop, so a change to winit_core.event_loop can break winit_x11.event_loop, while a change to winit_x11.event_loop can't break winit_core.event_loop.
- Position
- Below the diagonal: winit_x11.event_loop uses a module listed above it, which is the healthy direction.
37→15 winit_x11.event_loop uses winit_android.event_loop✕
- Connections
- 2 pairs of types, where a type in winit_x11.event_loop uses a type in winit_android.event_loop.
- The types involved
winit_x11.event_loop.ActiveEventLoop→winit_android.event_loop.Windowwinit_x11.event_loop.event_loop$module→winit_android.event_loop.Window
- Direction
- winit_x11.event_loop uses winit_android.event_loop, so a change to winit_android.event_loop can break winit_x11.event_loop, while a change to winit_x11.event_loop can't break winit_android.event_loop.
- Position
- Below the diagonal: winit_x11.event_loop uses a module listed above it, which is the healthy direction.
37→16 winit_x11.event_loop uses winit_appkit.data_transfer✕
- Connections
- 1 pair of types, where a type in winit_x11.event_loop uses a type in winit_appkit.data_transfer.
- The types involved
winit_x11.event_loop.ActiveEventLoop→winit_appkit.data_transfer.DataTransferState
- Direction
- winit_x11.event_loop uses winit_appkit.data_transfer, so a change to winit_appkit.data_transfer can break winit_x11.event_loop, while a change to winit_x11.event_loop can't break winit_appkit.data_transfer.
- Position
- Below the diagonal: winit_x11.event_loop uses a module listed above it, which is the healthy direction.
37→34 winit_x11.event_loop uses winit_x11.xdisplay✕
- Connections
- 3 pairs of types, where a type in winit_x11.event_loop uses a type in winit_x11.xdisplay.
- The types involved
winit_x11.event_loop.ActiveEventLoop→winit_x11.xdisplay.XConnectionwinit_x11.event_loop.DeviceInfo→winit_x11.xdisplay.XConnectionwinit_x11.event_loop.X11Error→winit_x11.xdisplay.XError
- Direction
- winit_x11.event_loop uses winit_x11.xdisplay, so a change to winit_x11.xdisplay can break winit_x11.event_loop, while a change to winit_x11.event_loop can't break winit_x11.xdisplay.
- Position
- Below the diagonal: winit_x11.event_loop uses a module listed above it, which is the healthy direction.
38→5 winit_win32.data_transfer uses winit_core.data_transfer✕
- Connections
- 11 pairs of types, where a type in winit_win32.data_transfer uses a type in winit_core.data_transfer.
- The types involved
winit_win32.data_transfer.ClipboardState→winit_core.data_transfer.DataTransferIdwinit_win32.data_transfer.DataObject→winit_core.data_transfer.TypeHintwinit_win32.data_transfer.DataTransferState→winit_core.data_transfer.DataTransferIdwinit_win32.data_transfer.DragState→winit_core.data_transfer.DataTransferIdwinit_win32.data_transfer.FileDropHandlerData→winit_core.data_transfer.DataTransferIdwinit_win32.data_transfer.WinDataTransfer→winit_core.data_transfer.DataTransferwinit_win32.data_transfer.WinTypedData→winit_core.data_transfer.TypeHintwinit_win32.data_transfer.WinTypedData→winit_core.data_transfer.TypedDatawinit_win32.data_transfer.data_transfer$module→winit_core.data_transfer.DataTransferIdwinit_win32.data_transfer.data_transfer$module→winit_core.data_transfer.SendDatawinit_win32.data_transfer.data_transfer$module→winit_core.data_transfer.TypeHint
- Direction
- winit_win32.data_transfer uses winit_core.data_transfer, so a change to winit_core.data_transfer can break winit_win32.data_transfer, while a change to winit_win32.data_transfer can't break winit_core.data_transfer.
- Position
- Below the diagonal: winit_win32.data_transfer uses a module listed above it, which is the healthy direction.
38→10 winit_win32.data_transfer uses winit_common.xkb✕
- Connections
- 1 pair of types, where a type in winit_win32.data_transfer uses a type in winit_common.xkb.
- The types involved
winit_win32.data_transfer.OleInitError→winit_common.xkb.Error
- Direction
- winit_win32.data_transfer uses winit_common.xkb, so a change to winit_common.xkb can break winit_win32.data_transfer, while a change to winit_win32.data_transfer can't break winit_common.xkb.
- Position
- Below the diagonal: winit_win32.data_transfer uses a module listed above it, which is the healthy direction.
38→13 winit_win32.data_transfer uses winit_core.window✕
- Connections
- 2 pairs of types, where a type in winit_win32.data_transfer uses a type in winit_core.window.
- The types involved
winit_win32.data_transfer.DataTransferState→winit_core.window.WindowIdwinit_win32.data_transfer.DragState→winit_core.window.WindowId
- Direction
- winit_win32.data_transfer uses winit_core.window, so a change to winit_core.window can break winit_win32.data_transfer, while a change to winit_win32.data_transfer can't break winit_core.window.
- Position
- Below the diagonal: winit_win32.data_transfer uses a module listed above it, which is the healthy direction.
38→14 winit_win32.data_transfer uses winit_core.event_loop✕
- Connections
- 3 pairs of types, where a type in winit_win32.data_transfer uses a type in winit_core.event_loop.
- The types involved
winit_win32.data_transfer.DataTransferState→winit_core.event_loop.DndActionwinit_win32.data_transfer.DragState→winit_core.event_loop.DndActionwinit_win32.data_transfer.data_transfer$module→winit_core.event_loop.DndAction
- Direction
- winit_win32.data_transfer uses winit_core.event_loop, so a change to winit_core.event_loop can break winit_win32.data_transfer, while a change to winit_win32.data_transfer can't break winit_core.event_loop.
- Position
- Below the diagonal: winit_win32.data_transfer uses a module listed above it, which is the healthy direction.
38→16 winit_win32.data_transfer uses winit_appkit.data_transfer✕
- Connections
- 1 pair of types, where a type in winit_win32.data_transfer uses a type in winit_appkit.data_transfer.
- The types involved
winit_win32.data_transfer.DataTransferState→winit_appkit.data_transfer.DragState
- Direction
- winit_win32.data_transfer uses winit_appkit.data_transfer, so a change to winit_appkit.data_transfer can break winit_win32.data_transfer, while a change to winit_win32.data_transfer can't break winit_appkit.data_transfer.
- Position
- Below the diagonal: winit_win32.data_transfer uses a module listed above it, which is the healthy direction.
38→36 winit_win32.data_transfer uses winit_win32.event_loop.runner✕
- Connections
- 2 pairs of types, where a type in winit_win32.data_transfer uses a type in winit_win32.event_loop.runner.
- The types involved
winit_win32.data_transfer.FileDropHandler→winit_win32.event_loop.runner.EventLoopRunnerwinit_win32.data_transfer.FileDropHandlerData→winit_win32.event_loop.runner.EventLoopRunner
- Direction
- winit_win32.data_transfer uses winit_win32.event_loop.runner, so a change to winit_win32.event_loop.runner can break winit_win32.data_transfer, while a change to winit_win32.data_transfer can't break winit_win32.event_loop.runner.
- Position
- Below the diagonal: winit_win32.data_transfer uses a module listed above it, which is the healthy direction.
39→1 winit_win32.window uses dpi✕
- Connections
- 8 pairs of types, where a type in winit_win32.window uses a type in dpi.
- The types involved
winit_win32.window.Window→dpi.PhysicalInsetswinit_win32.window.Window→dpi.PhysicalPositionwinit_win32.window.Window→dpi.PhysicalSizewinit_win32.window.Window→dpi.Positionwinit_win32.window.Window→dpi.Sizewinit_win32.window.window$module→dpi.PhysicalPositionwinit_win32.window.window$module→dpi.PhysicalSizewinit_win32.window.window$module→dpi.Position
- Direction
- winit_win32.window uses dpi, so a change to dpi can break winit_win32.window, while a change to winit_win32.window can't break dpi.
- Position
- Below the diagonal: winit_win32.window uses a module listed above it, which is the healthy direction.
39→7 winit_win32.window uses winit_core.monitor✕
- Connections
- 1 pair of types, where a type in winit_win32.window uses a type in winit_core.monitor.
- The types involved
winit_win32.window.Window→winit_core.monitor.Fullscreen
- Direction
- winit_win32.window uses winit_core.monitor, so a change to winit_core.monitor can break winit_win32.window, while a change to winit_win32.window can't break winit_core.monitor.
- Position
- Below the diagonal: winit_win32.window uses a module listed above it, which is the healthy direction.
39→11 winit_win32.window uses winit_core.cursor✕
- Connections
- 1 pair of types, where a type in winit_win32.window uses a type in winit_core.cursor.
- The types involved
winit_win32.window.Window→winit_core.cursor.Cursor
- Direction
- winit_win32.window uses winit_core.cursor, so a change to winit_core.cursor can break winit_win32.window, while a change to winit_win32.window can't break winit_core.cursor.
- Position
- Below the diagonal: winit_win32.window uses a module listed above it, which is the healthy direction.
39→12 winit_win32.window uses winit_core.icon✕
- Connections
- 1 pair of types, where a type in winit_win32.window uses a type in winit_core.icon.
- The types involved
winit_win32.window.Window→winit_core.icon.Icon
- Direction
- winit_win32.window uses winit_core.icon, so a change to winit_core.icon can break winit_win32.window, while a change to winit_win32.window can't break winit_core.icon.
- Position
- Below the diagonal: winit_win32.window uses a module listed above it, which is the healthy direction.
39→13 winit_win32.window uses winit_core.window✕
- Connections
- 15 pairs of types, where a type in winit_win32.window uses a type in winit_core.window.
- The types involved
winit_win32.window.InitData→winit_core.window.WindowAttributeswinit_win32.window.Window→winit_core.window.CursorGrabModewinit_win32.window.Window→winit_core.window.ImeCapabilitieswinit_win32.window.Window→winit_core.window.ImeRequestwinit_win32.window.Window→winit_core.window.ResizeDirectionwinit_win32.window.Window→winit_core.window.Themewinit_win32.window.Window→winit_core.window.UserAttentionTypewinit_win32.window.Window→winit_core.window.WindowAttributeswinit_win32.window.Window→winit_core.window.WindowButtonswinit_win32.window.Window→winit_core.window.WindowIdwinit_win32.window.Window→winit_core.window.WindowLevelwinit_win32.window.Window→winit_core.window.WindowPositionerwinit_win32.window.Window→winit_core.window.WindowTypewinit_win32.window.window$module→winit_core.window.WindowAttributeswinit_win32.window.window$module→winit_core.window.WindowPositioner
- Direction
- winit_win32.window uses winit_core.window, so a change to winit_core.window can break winit_win32.window, while a change to winit_win32.window can't break winit_core.window.
- Position
- Below the diagonal: winit_win32.window uses a module listed above it, which is the healthy direction.
39→15 winit_win32.window uses winit_android.event_loop✕
- Connections
- 2 pairs of types, where a type in winit_win32.window uses a type in winit_android.event_loop.
- The types involved
winit_win32.window.InitData→winit_android.event_loop.Windowwinit_win32.window.Window→winit_android.event_loop.ActiveEventLoop
- Direction
- winit_win32.window uses winit_android.event_loop, so a change to winit_android.event_loop can break winit_win32.window, while a change to winit_win32.window can't break winit_android.event_loop.
- Position
- Below the diagonal: winit_win32.window uses a module listed above it, which is the healthy direction.
39→25 winit_win32.window uses winit_wayland.window.state✕
- Connections
- 2 pairs of types, where a type in winit_win32.window uses a type in winit_wayland.window.state.
- The types involved
winit_win32.window.Window→winit_wayland.window.state.WindowStatewinit_win32.window.window$module→winit_wayland.window.state.WindowState
- Direction
- winit_win32.window uses winit_wayland.window.state, so a change to winit_wayland.window.state can break winit_win32.window, while a change to winit_win32.window can't break winit_wayland.window.state.
- Position
- Below the diagonal: winit_win32.window uses a module listed above it, which is the healthy direction.
39→28 winit_win32.window uses winit_win32.window_state✕
- Connections
- 1 pair of types, where a type in winit_win32.window uses a type in winit_win32.window_state.
- The types involved
winit_win32.window.InitData→winit_win32.window_state.WindowFlags
- Direction
- winit_win32.window uses winit_win32.window_state, so a change to winit_win32.window_state can break winit_win32.window, while a change to winit_win32.window can't break winit_win32.window_state.
- Position
- Below the diagonal: winit_win32.window uses a module listed above it, which is the healthy direction.
39→31 winit_win32.window uses winit_win32.event_loop✕
- Connections
- 2 pairs of types, where a type in winit_win32.window uses a type in winit_win32.event_loop.
- The types involved
winit_win32.window.InitData→winit_win32.event_loop.WindowDatawinit_win32.window.Window→winit_win32.event_loop.EventLoopThreadExecutor
- Direction
- winit_win32.window uses winit_win32.event_loop, so a change to winit_win32.event_loop can break winit_win32.window, while a change to winit_win32.window can't break winit_win32.event_loop.
- Position
- Below the diagonal: winit_win32.window uses a module listed above it, which is the healthy direction.
39→36 winit_win32.window uses winit_win32.event_loop.runner✕
- Connections
- 2 pairs of types, where a type in winit_win32.window uses a type in winit_win32.event_loop.runner.
- The types involved
winit_win32.window.InitData→winit_win32.event_loop.runner.EventLoopRunnerwinit_win32.window.window$module→winit_win32.event_loop.runner.EventLoopRunner
- Direction
- winit_win32.window uses winit_win32.event_loop.runner, so a change to winit_win32.event_loop.runner can break winit_win32.window, while a change to winit_win32.window can't break winit_win32.event_loop.runner.
- Position
- Below the diagonal: winit_win32.window uses a module listed above it, which is the healthy direction.
40→1 winit_x11.window uses dpi✕
- Connections
- 13 pairs of types, where a type in winit_x11.window uses a type in dpi.
- The types involved
winit_x11.window.SharedState→dpi.Sizewinit_x11.window.UnownedWindow→dpi.PhysicalInsetswinit_x11.window.UnownedWindow→dpi.PhysicalPositionwinit_x11.window.UnownedWindow→dpi.PhysicalSizewinit_x11.window.UnownedWindow→dpi.Positionwinit_x11.window.UnownedWindow→dpi.Sizewinit_x11.window.Window→dpi.PhysicalInsetswinit_x11.window.Window→dpi.PhysicalPositionwinit_x11.window.Window→dpi.PhysicalSizewinit_x11.window.Window→dpi.Positionwinit_x11.window.Window→dpi.Sizewinit_x11.window.window$module→dpi.PhysicalSizewinit_x11.window.window$module→dpi.Size
- Direction
- winit_x11.window uses dpi, so a change to dpi can break winit_x11.window, while a change to winit_x11.window can't break dpi.
- Position
- Below the diagonal: winit_x11.window uses a module listed above it, which is the healthy direction.
40→7 winit_x11.window uses winit_core.monitor✕
- Connections
- 3 pairs of types, where a type in winit_x11.window uses a type in winit_core.monitor.
- The types involved
winit_x11.window.SharedState→winit_core.monitor.Fullscreenwinit_x11.window.UnownedWindow→winit_core.monitor.Fullscreenwinit_x11.window.Window→winit_core.monitor.Fullscreen
- Direction
- winit_x11.window uses winit_core.monitor, so a change to winit_core.monitor can break winit_x11.window, while a change to winit_x11.window can't break winit_core.monitor.
- Position
- Below the diagonal: winit_x11.window uses a module listed above it, which is the healthy direction.
40→11 winit_x11.window uses winit_core.cursor✕
- Connections
- 2 pairs of types, where a type in winit_x11.window uses a type in winit_core.cursor.
- The types involved
winit_x11.window.UnownedWindow→winit_core.cursor.Cursorwinit_x11.window.Window→winit_core.cursor.Cursor
- Direction
- winit_x11.window uses winit_core.cursor, so a change to winit_core.cursor can break winit_x11.window, while a change to winit_x11.window can't break winit_core.cursor.
- Position
- Below the diagonal: winit_x11.window uses a module listed above it, which is the healthy direction.
40→12 winit_x11.window uses winit_core.icon✕
- Connections
- 2 pairs of types, where a type in winit_x11.window uses a type in winit_core.icon.
- The types involved
winit_x11.window.UnownedWindow→winit_core.icon.RgbaIconwinit_x11.window.Window→winit_core.icon.Icon
- Direction
- winit_x11.window uses winit_core.icon, so a change to winit_core.icon can break winit_x11.window, while a change to winit_x11.window can't break winit_core.icon.
- Position
- Below the diagonal: winit_x11.window uses a module listed above it, which is the healthy direction.
40→13 winit_x11.window uses winit_core.window✕
- Connections
- 22 pairs of types, where a type in winit_x11.window uses a type in winit_core.window.
- The types involved
winit_x11.window.SharedState→winit_core.window.ImeCapabilitieswinit_x11.window.SharedState→winit_core.window.WindowAttributeswinit_x11.window.UnownedWindow→winit_core.window.CursorGrabModewinit_x11.window.UnownedWindow→winit_core.window.ImeCapabilitieswinit_x11.window.UnownedWindow→winit_core.window.ResizeDirectionwinit_x11.window.UnownedWindow→winit_core.window.Themewinit_x11.window.UnownedWindow→winit_core.window.UserAttentionTypewinit_x11.window.UnownedWindow→winit_core.window.WindowAttributeswinit_x11.window.UnownedWindow→winit_core.window.WindowButtonswinit_x11.window.UnownedWindow→winit_core.window.WindowIdwinit_x11.window.UnownedWindow→winit_core.window.WindowLevelwinit_x11.window.UnownedWindow→winit_core.window.WindowTypewinit_x11.window.Window→winit_core.window.CursorGrabModewinit_x11.window.Window→winit_core.window.ImeCapabilitieswinit_x11.window.Window→winit_core.window.ResizeDirectionwinit_x11.window.Window→winit_core.window.Themewinit_x11.window.Window→winit_core.window.UserAttentionTypewinit_x11.window.Window→winit_core.window.WindowAttributeswinit_x11.window.Window→winit_core.window.WindowButtonswinit_x11.window.Window→winit_core.window.WindowIdwinit_x11.window.Window→winit_core.window.WindowLevelwinit_x11.window.Window→winit_core.window.WindowType
- Direction
- winit_x11.window uses winit_core.window, so a change to winit_core.window can break winit_x11.window, while a change to winit_x11.window can't break winit_core.window.
- Position
- Below the diagonal: winit_x11.window uses a module listed above it, which is the healthy direction.
40→15 winit_x11.window uses winit_android.event_loop✕
- Connections
- 3 pairs of types, where a type in winit_x11.window uses a type in winit_android.event_loop.
- The types involved
winit_x11.window.UnownedWindow→winit_android.event_loop.ActiveEventLoopwinit_x11.window.UnownedWindow→winit_android.event_loop.Windowwinit_x11.window.Window→winit_android.event_loop.ActiveEventLoop
- Direction
- winit_x11.window uses winit_android.event_loop, so a change to winit_android.event_loop can break winit_x11.window, while a change to winit_x11.window can't break winit_android.event_loop.
- Position
- Below the diagonal: winit_x11.window uses a module listed above it, which is the healthy direction.
40→34 winit_x11.window uses winit_x11.xdisplay✕
- Connections
- 1 pair of types, where a type in winit_x11.window uses a type in winit_x11.xdisplay.
- The types involved
winit_x11.window.UnownedWindow→winit_x11.xdisplay.XConnection
- Direction
- winit_x11.window uses winit_x11.xdisplay, so a change to winit_x11.xdisplay can break winit_x11.window, while a change to winit_x11.window can't break winit_x11.xdisplay.
- Position
- Below the diagonal: winit_x11.window uses a module listed above it, which is the healthy direction.
40→37 winit_x11.window uses winit_x11.event_loop✕
- Connections
- 1 pair of types, where a type in winit_x11.window uses a type in winit_x11.event_loop.
- The types involved
winit_x11.window.UnownedWindow→winit_x11.event_loop.WakeSender
- Direction
- winit_x11.window uses winit_x11.event_loop, so a change to winit_x11.event_loop can break winit_x11.window, while a change to winit_x11.window can't break winit_x11.event_loop.
- Position
- Below the diagonal: winit_x11.window 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 — Event Sourcing
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 23 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 7 | Medium |
| A08:2025 — Software or Data Integrity Failures | 1 | Medium |
Roadmap
First, fix broken links in the README files and update documentation to reflect current code reality. Next, create a dedicated folder for architecture decision records to capture key design choices and their consequences. Then, address orphaned knowledge by resolving stale references in keyboard.rs and monitor.rs, followed by cleaning up orphaned files in raw_input.rs, geometry.rs, and schedule.rs. Finally, reduce technical debt in high-churn, high-complexity areas by refactoring event_loop.rs, mod.rs, and window.rs.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Reconcile the README with reality: winit-android/README.md links to `FEATURES.md`, but `winit-android/FEATURES.md` does not exist; winit-android/README.md links to `./CONTRIBUTING.md`, but `winit-android/CONTRIBUTING.md` does not exist; winit-appkit/README.md links to `FEATURES.md`, but `winit-appkit/FEATURES.md` does not exist; winit-appkit/README.md links to `./CONTRIBUTING.md`, but `winit-appkit/CONTRIBUTING.md` does not exist; winit-common/README.md links to `FEATURES.md`, but `winit-common/FEATURES.md` does not exist. | +11.7 pts | Medium | Documentation accuracy |
| 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. | +7.2 pts | Medium | Architecture documentation |
| Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with keyboard.rs, monitor.rs. | +3.0 pts | Low | Knowledge Freshness |
| Resolve the 23 Orphaned file finding(s) in Knowledge Freshness — start with raw_input.rs, geometry.rs, schedule.rs. | +2.4 pts | Medium | Knowledge Freshness |
| Resolve the 11 Hotspot finding(s) in Churn × Complexity Hotspots — start with event_loop.rs (2), mod.rs (2), window.rs (2). | +2.1 pts | High | Churn × Complexity Hotspots |
| Interpolated log message defeats structured logging | +1.9 pts | Medium | Structured logging |
| Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with winit_win32::event_loop::public_window_callback_inner (cognitive 261). | +0.9 pts | Medium | Cognitive Complexity |
| Resolve the 2 Off-boarding risk finding(s) in Bus Factor. | +0.9 pts | Low | Bus Factor |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| winit-android/src/event_loop.rs | 1.4 | Slop | Change Coupling: Boundary-crossing change coupling: event_loop.rs ↔ mod.rs |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| winit-uikit/src/window.rs | 2.7 | Slop | Change Coupling: Boundary-crossing change coupling: window.rs ↔ mod.rs |
| winit-wayland/src/window/mod.rs | 3.0 | Mixed | Change Coupling: Boundary-crossing change coupling: mod.rs ↔ mod.rs |
| winit-orbital/src/window.rs | 4.4 | Mixed | Change Coupling: Boundary-crossing change coupling: window.rs ↔ mod.rs |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| winit-uikit/src/view.rs | 5.1 | Mixed | Change Coupling: Boundary-crossing change coupling: view.rs ↔ mod.rs |
| winit-uikit/src/monitor.rs | 5.3 | Mixed | Change Coupling: Boundary-crossing change coupling: monitor.rs ↔ mod.rs |
| winit-wayland/src/seat/pointer/mod.rs | 5.9 | Mixed | Cyclomatic Complexity: WinitState::pointer_frame (cyclomatic 29) |
| winit-win32/src/keyboard.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| winit-win32/src/event_loop.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| winit-appkit/src/cursor.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| winit-x11/src/event_processor.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| winit-x11/src/window.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| winit-appkit/src/window_delegate.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| winit-wayland/src/seat/keyboard/mod.rs | 6.0 | Mixed | Explicit Debt: HackComment |
| winit-win32/src/keyboard_layout.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| winit-wayland/src/event_loop/mod.rs | 6.0 | Mixed | Explicit Debt: XxxComment |
| winit-wayland/src/seat/text_input/mod.rs | 6.0 | Mixed | Explicit Debt: XxxComment |
| winit-orbital/src/event_loop.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. 61 of 61 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 61 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, 449 of 464 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.
- D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A hotspot's complexity is meant to be the worst body its churn actually touched. For winit-x11/src/atoms.rs that could not be established — the complexity reader for the file reports no body extents, or the history carries no per-line attribution — so the row quotes the file's worst body, which the counted changes may never have touched. The churn count is unaffected.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — 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. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; REDACTED was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that REDACTED is free of known-vulnerable dependencies.
- D43 Malicious Dependencies — measured, with a gap in what it reached — 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. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; REDACTED was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that REDACTED is free of known-vulnerable dependencies.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). 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.
- 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. 54 further occurrence(s) are not listed individually; the score already reflects all 94.
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.
- D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- 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
27 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was winit_win32::keyboard::physicalkey_to_scancode at 160. A further 17 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 winit_android::keycodes::to_logical at 292 — they are counted neither in the figure above nor in this dimension's score. 5 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: winit-android/src/keycodes.rs (winit_android::keycodes::to_logical at 292), winit-common/src/xkb/keymap.rs (winit_common::xkb::keymap::keysym_to_key at 199), winit-appkit/src/event.rs (winit_appkit::event::physicalkey_to_scancode at 123), winit-x11/src/atoms.rs (AtomName::atom_from at 97), winit-wayland/src/window/state/frame.rs (WindowState::frame_click 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 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with winit_win32::keyboard::physicalkey_to_scancode (cyclomatic 160), winit_win32::event_loop::public_window_callback_inner (cyclomatic 155). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 5.5 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
43 function(s) exceeded the cognitive complexity threshold of 15; the worst was winit_win32::event_loop::public_window_callback_inner at 261.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with winit_win32::event_loop::public_window_callback_inner (cognitive 261). — Refactoring it lifts Cognitive Complexity from 5.0 to about 6.5/10.
- 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
74 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 23 FileTooLong finding(s) in God Classes — start with event_loop.rs (4), window.rs (4), data_transfer.rs (3). — One of this dimension's main actionable groups (23 warning-level).
- Resolve the 18 MethodTooLong finding(s) in God Classes — start with mod.rs (4), event_loop.rs (3), event_processor.rs (2). — One of this dimension's main actionable groups (18 warning-level).
- Resolve the 15 FunctionTooLong finding(s) in God Classes — start with keymap.rs (3), event_loop.rs (2), keycodes.rs (2). — One of this dimension's main actionable groups (15 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
50 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 7 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with window_delegate.rs, keymap.rs, data_transfer.rs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 6 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with window.rs (2), event_loop.rs, keymap.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 6 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with event_loop.rs, event.rs, window_delegate.rs. — One of this dimension's main actionable groups (6 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
12 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence.
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)
2 of 148 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with event_loop.rs (2). — One of this dimension's main actionable groups (2 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
66 test methods: 52 unit, 14 integration, 0 BDD, 0 e2e. The Rust suite contributes 66 `#[test]` function(s) across 16 file(s) declaring at least one; its unit/integration split is Cargo's own — 3 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.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 16 test files): measured (0 flaky).
D12 · Dependency Hygiene
1 outdated, 0 yanked direct Cargo dependencies. 46 of 49 direct crates were graded against crates.io (0 not published there, 3 not resolved by a committed Cargo.lock). 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 Cargo.lock there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 158 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository commits no Cargo.lock, so its graph was resolved here: its manifests' `[dependencies]` and `[build-dependencies]` closed over the crates.io index, each crate at the newest release its requirement admits (what a fresh `cargo generate-lockfile` picks, not a graph the repository has pinned). Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 3 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: winit-win32/src/event_loop.rs (13×155=2015); winit-appkit/src/window_delegate.rs (12×34=408); winit-wayland/src/event_loop/mod.rs (14×24=336)
What to do
- Resolve the 11 Hotspot finding(s) in Churn × Complexity Hotspots — start with event_loop.rs (2), mod.rs (2), window.rs (2). — One of this dimension's main actionable groups (11 warning-level).
D16 · Bus Factor
8 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is winit-wayland/src/window/state/configure.rs. Counted over 138 of the 189 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
116 deducted task-comment markers across 62704 LoC (0.2/KLoC) → score 9.6. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 82 TodoComment finding(s) in Explicit Debt — start with event_loop.rs (16), window.rs (14), data_transfer.rs (8). — One of this dimension's main actionable groups (82 warning-level).
- Resolve the 14 XxxComment finding(s) in Explicit Debt — start with event_loop.rs (5), mod.rs (5), popup.rs (2). — One of this dimension's main actionable groups (14 warning-level).
- Resolve the 14 FixmeComment finding(s) in Explicit Debt — start with event_loop.rs (3), event_loop_proxy.rs (2), app.rs (2). — One of this dimension's main actionable groups (14 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. 15 document(s) read across 1 unit(s).
D26 · Project Cohesion
0 of 12 build units (Cargo) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
23 finding(s): 0 critical, 23 high, 0 medium, 0 low. 22 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 4 file(s) — `winit-appkit/src/window_delegate.rs` (line 1186), `winit-web/src/cursor.rs` (line 491, lines 611–612, line 613, …), `winit-web/src/monitor.rs` (line 865, line 883, line 899), `winit-x11/src/event_processor.rs` (line 1302) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
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).
- No action in Static Analysis (SAST) — all 22 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 (22 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. REDACTED was not scanned (REDACTED: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
D34 · Knowledge Freshness
25 of 138 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is winit-win32/src/keyboard.rs. Counted over 138 of the 189 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 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with keyboard.rs, monitor.rs. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 23 Orphaned file finding(s) in Knowledge Freshness — start with raw_input.rs, geometry.rs, schedule.rs. — One of this dimension's main actionable groups (23 recommendation-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: output.rs↔mod.rs 75%; util.rs↔view.rs 67%; window.rs↔mod.rs 66%
What to do
- Resolve the 10 Boundary-crossing change coupling finding(s) in Change Coupling — start with mod.rs (3), output.rs (2), window.rs (2). — One of this dimension's main actionable groups (10 issue-level).
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with util.rs, window_target.rs, mod.rs. — One of this dimension's main actionable groups (3 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. REDACTED was not scanned (REDACTED: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
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
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
ES1 · Fold determinism
ES2 · Immutable events
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 1 of 13 project(s) that lack one — worth up to 0.2 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
- winit-android/README.md links to `FEATURES.md`, but `winit-android/FEATURES.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — winit-android/README.md:16
- winit-android/README.md links to `./CONTRIBUTING.md`, but `winit-android/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — winit-android/README.md:38
- winit-appkit/README.md links to `FEATURES.md`, but `winit-appkit/FEATURES.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — winit-appkit/README.md:16
- winit-appkit/README.md links to `./CONTRIBUTING.md`, but `winit-appkit/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — winit-appkit/README.md:38
- winit-common/README.md links to `FEATURES.md`, but `winit-common/FEATURES.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — winit-common/README.md:16
- winit-common/README.md links to `./CONTRIBUTING.md`, but `winit-common/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — winit-common/README.md:38
- winit-core/README.md links to `FEATURES.md`, but `winit-core/FEATURES.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — winit-core/README.md:16
- winit-core/README.md links to `./CONTRIBUTING.md`, but `winit-core/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — winit-core/README.md:38
- winit-orbital/README.md links to `FEATURES.md`, but `winit-orbital/FEATURES.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — winit-orbital/README.md:16
- winit-orbital/README.md links to `./CONTRIBUTING.md`, but `winit-orbital/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — winit-orbital/README.md:38
- winit-uikit/README.md links to `FEATURES.md`, but `winit-uikit/FEATURES.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — winit-uikit/README.md:16
- winit-uikit/README.md links to `./CONTRIBUTING.md`, but `winit-uikit/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — winit-uikit/README.md:38
- winit-wayland/README.md links to `FEATURES.md`, but `winit-wayland/FEATURES.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — winit-wayland/README.md:16
- winit-wayland/README.md links to `./CONTRIBUTING.md`, but `winit-wayland/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — winit-wayland/README.md:38
- winit-web/README.md links to `FEATURES.md`, but `winit-web/FEATURES.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — winit-web/README.md:16
- winit-web/README.md links to `./CONTRIBUTING.md`, but `winit-web/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — winit-web/README.md:38
- winit-win32/README.md links to `FEATURES.md`, but `winit-win32/FEATURES.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — winit-win32/README.md:16
- winit-win32/README.md links to `./CONTRIBUTING.md`, but `winit-win32/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — winit-win32/README.md:38
- winit-x11/README.md links to `FEATURES.md`, but `winit-x11/FEATURES.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — winit-x11/README.md:16
- winit-x11/README.md links to `./CONTRIBUTING.md`, but `winit-x11/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — winit-x11/README.md:38
- winit/README.md links to `./CONTRIBUTING.md`, but `winit/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — winit/README.md:38
What to do
- Reconcile the README with reality: winit-android/README.md links to `FEATURES.md`, but `winit-android/FEATURES.md` does not exist; winit-android/README.md links to `./CONTRIBUTING.md`, but `winit-android/CONTRIBUTING.md` does not exist; winit-appkit/README.md links to `FEATURES.md`, but `winit-appkit/FEATURES.md` does not exist; winit-appkit/README.md links to `./CONTRIBUTING.md`, but `winit-appkit/CONTRIBUTING.md` does not exist; winit-common/README.md links to `FEATURES.md`, but `winit-common/FEATURES.md` does not exist.
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
What to do
- Dependabot is configured but does not watch `cargo` — add that `package-ecosystem` entry to .github/dependabot.yml so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where Watchdog can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `error!` at line 458 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`. — winit-x11/src/data_transfer.rs:458
- `warn!` at line 605 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`. — winit-x11/src/data_transfer.rs:605
- `warn!` at line 609 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`. — winit-x11/src/data_transfer.rs:609
- `trace!` at line 632 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`. — winit-x11/src/data_transfer.rs:632
- `trace!` at line 641 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`. — winit-x11/src/data_transfer.rs:641
- `warn!` at line 647 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`. — winit-x11/src/data_transfer.rs:647
- `warn!` at line 658 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`. — winit-x11/src/data_transfer.rs:658
- `trace!` at line 668 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`. — winit-x11/src/data_transfer.rs:668
- `warn!` at line 674 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`. — winit-x11/src/data_transfer.rs:674
- `trace!` at line 714 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`. — winit-x11/src/data_transfer.rs:714
- `trace!` at line 730 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`. — winit-x11/src/data_transfer.rs:730
- `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`. — winit-x11/src/data_transfer.rs:763
- `trace!` at line 772 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`. — winit-x11/src/data_transfer.rs:772
- `trace!` at line 791 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`. — winit-x11/src/data_transfer.rs:791
- `error!` at line 796 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`. — winit-x11/src/data_transfer.rs:796
- `error!` at line 852 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`. — winit-x11/src/data_transfer.rs:852
- `trace!` at line 855 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`. — winit-x11/src/data_transfer.rs:855
- `trace!` at line 860 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`. — winit-x11/src/data_transfer.rs:860
- `warn!` at line 883 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`. — winit-x11/src/data_transfer.rs:883
- `trace!` at line 888 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`. — winit-x11/src/data_transfer.rs:888
- `error!` at line 922 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`. — winit-x11/src/data_transfer.rs:922
- `trace!` at line 1016 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`. — winit-x11/src/data_transfer.rs:1016
- `trace!` at line 1022 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`. — winit-x11/src/data_transfer.rs:1022
- `error!` at line 108 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`. — winit-x11/src/event_loop.rs:108
- `warn!` at line 256 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`. — winit-x11/src/event_loop.rs:256
- `warn!` at line 268 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`. — winit-x11/src/event_loop.rs:268
- `warn!` at line 270 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`. — winit-x11/src/event_loop.rs:270
- `error!` at line 552 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`. — winit-x11/src/event_loop.rs:552
- `error!` 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: `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`. — winit-x11/src/event_loop.rs:619
- `warn!` at line 631 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`. — winit-x11/src/event_processor.rs:631
- `warn!` at line 653 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`. — winit-x11/src/event_processor.rs:653
- `warn!` at line 735 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`. — winit-x11/src/event_processor.rs:735
- `warn!` at line 747 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`. — winit-x11/src/event_processor.rs:747
- `error!` at line 776 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`. — winit-x11/src/event_processor.rs:776
- `error!` at line 821 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`. — winit-x11/src/event_processor.rs:821
- `info!` at line 515 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`. — winit-x11/src/window.rs:515
- `debug!` at line 542 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`. — winit-x11/src/window.rs:542
- `error!` at line 1838 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`. — winit-x11/src/window.rs:1838
- `error!` at line 1854 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`. — winit-x11/src/window.rs:1854
- `error!` at line 1967 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`. — winit-x11/src/window.rs:1967
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 74% | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 99% | Exemplary | Solid. |
| Maturity | 46% | Adequate — gated by M2, M4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 79% | Strong | Solid. |
| Security | 77% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event Sourcing | 100% | Exemplary | Strongest area. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 57 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~2792 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.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — 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, .ts, 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 — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 81 value object(s); 6 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's Rust, JavaScript/TypeScript source (13 module(s), 189 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- S1 Web-Security Posture — No web surface: 188 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.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 35 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Boundary-crossing change coupling: output.rs ↔ mod.rs winit-wayland/src/output.rs:1
- Boundary-crossing change coupling: window.rs ↔ mod.rs winit-orbital/src/window.rs:1
- Boundary-crossing change coupling: output.rs ↔ randr.rs winit-wayland/src/output.rs:1
- Boundary-crossing change coupling: monitor.rs ↔ mod.rs winit-uikit/src/monitor.rs:1
- Boundary-crossing change coupling: window.rs ↔ mod.rs winit-uikit/src/window.rs:1
- Boundary-crossing change coupling: mod.rs ↔ mod.rs winit-wayland/src/window/mod.rs:1
- Boundary-crossing change coupling: view.rs ↔ mod.rs winit-uikit/src/view.rs:1
- Boundary-crossing change coupling: mod.rs ↔ event_loop.rs winit-wayland/src/seat/touch/mod.rs:1
- Boundary-crossing change coupling: mod.rs ↔ event_processor.rs winit-wayland/src/seat/touch/mod.rs:1
- Boundary-crossing change coupling: event_loop.rs ↔ mod.rs winit-android/src/event_loop.rs:1
- Orphaned knowledge winit-win32/src/keyboard.rs:1
- Orphaned knowledge winit-web/src/monitor.rs:1
- REDACTED
Serious — 332 finding(s)
- TodoComment winit-x11/src/data_transfer.rs:32
- TodoComment winit-x11/src/data_transfer.rs:928
- TodoComment winit-x11/src/data_transfer.rs:970
- TodoComment winit-x11/src/event_loop.rs:762
- TodoComment winit-x11/src/event_processor.rs:565
- TodoComment winit-orbital/src/event_loop.rs:170
- TodoComment winit-x11/src/event_processor.rs:771
- TodoComment winit-x11/src/window.rs:694
- TodoComment winit-x11/src/window.rs:2274
- TodoComment winit-x11/src/xdisplay.rs:27
- TodoComment winit-x11/src/xdisplay.rs:201
- TodoComment winit-x11/src/xdisplay.rs:376
- TodoComment winit-x11/src/xdisplay.rs:438
- TodoComment winit-x11/src/util/window_property.rs:239
- TodoComment winit-win32/src/data_transfer.rs:60
- TodoComment winit-win32/src/data_transfer.rs:770
- TodoComment winit-win32/src/event_loop.rs:1874
- TodoComment winit-win32/src/keyboard_layout.rs:320
- TodoComment winit-win32/src/keyboard_layout.rs:370
- TodoComment winit-win32/src/window.rs:196
- TodoComment winit-web/src/lock.rs:17
- TodoComment winit-web/src/web_sys/event.rs:177
- TodoComment winit-web/src/web_sys/event.rs:340
- TodoComment winit-web/src/web_sys/media_query_handle.rs:24
- TodoComment winit-web/src/web_sys/mod.rs:223
- FileTooLong: src/event_loop.rs winit-win32/src/event_loop.rs
- FileTooLong: src/window.rs winit-x11/src/window.rs
- FileTooLong: src/window_delegate.rs winit-appkit/src/window_delegate.rs
- FileTooLong: src/event_processor.rs winit-x11/src/event_processor.rs
- FileTooLong: src/data_transfer.rs winit-win32/src/data_transfer.rs
- FileTooLong: src/window.rs winit-win32/src/window.rs
- FileTooLong: src/data_transfer.rs winit-wayland/src/data_transfer.rs
- FileTooLong: src/keyboard.rs winit-win32/src/keyboard.rs
- FileTooLong: src/event_loop.rs winit-x11/src/event_loop.rs
- FileTooLong: src/view.rs winit-appkit/src/view.rs
- FileTooLong: src/keyboard_layout.rs winit-win32/src/keyboard_layout.rs
- FileTooLong: xkb/keymap.rs winit-common/src/xkb/keymap.rs
- FileTooLong: src/data_transfer.rs winit-x11/src/data_transfer.rs
- FileTooLong: src/event_loop.rs winit-android/src/event_loop.rs
- FileTooLong: src/event_loop.rs winit-orbital/src/event_loop.rs
- FileTooLong: src/window.rs winit-core/src/window.rs
- FileTooLong: src/monitor.rs winit-web/src/monitor.rs
- FileTooLong: event_loop/mod.rs winit-wayland/src/event_loop/mod.rs
- FileTooLong: src/window.rs winit-uikit/src/window.rs
- FileTooLong: src/view.rs winit-uikit/src/view.rs
- FileTooLong: src/event.rs winit-core/src/event.rs
- FileTooLong: event_loop/runner.rs winit-web/src/event_loop/runner.rs
- FileTooLong: src/keycodes.rs winit-android/src/keycodes.rs
- MethodTooLong: UnownedWindow.new winit-x11/src/window.rs:459
- MethodTooLong: ActiveEventLoop.register winit-web/src/event_loop/window_target.rs:71
- MethodTooLong: EventLoop.new winit-x11/src/event_loop.rs:218
- MethodTooLong: KeyEventBuilder.process_message winit-win32/src/keyboard.rs:76
- MethodTooLong: WinitState.event winit-wayland/src/seat/keyboard/mod.rs:23
- MethodTooLong: Popup.new winit-wayland/src/popup.rs:35
- MethodTooLong: WinitState.pointer_frame winit-wayland/src/seat/pointer/mod.rs:37
- MethodTooLong: EventLoop.handle_input_event winit-android/src/event_loop.rs:317
- MethodTooLong: EventProcessor.client_message winit-x11/src/event_processor.rs:376
- MethodTooLong: WinitView.handle_touches winit-uikit/src/view.rs:480
- MethodTooLong: EventLoop.single_iteration winit-wayland/src/event_loop/mod.rs:347
- MethodTooLong: Shared.set_listener winit-web/src/event_loop/runner.rs:280
- MethodTooLong: TabletToolData.event winit-wayland/src/types/wp_tablet_input_v2.rs:92
- MethodTooLong: WindowDelegate.set_fullscreen winit-appkit/src/window_delegate.rs:1815
- MethodTooLong: EventLoop.process_event winit-orbital/src/event_loop.rs:358
- MethodTooLong: WindowDelegate.new winit-appkit/src/window_delegate.rs:912
- MethodTooLong: EventProcessor.process_xevent winit-x11/src/event_processor.rs:150
- MethodTooLong: Window.new winit-wayland/src/window/mod.rs:57
- FunctionTooLong: winit_win32::event_loop::public_window_callback_inner winit-win32/src/event_loop.rs:1237
- FunctionTooLong: winit_android::keycodes::to_logical winit-android/src/keycodes.rs:238
- FunctionTooLong: winit_win32::keyboard_layout::vkey_to_non_char_key winit-win32/src/keyboard_layout.rs:735
- FunctionTooLong: winit_common::xkb::keymap::keysym_to_key winit-common/src/xkb/keymap.rs:504
- FunctionTooLong: winit_win32::keyboard_layout::keycode_to_vkey winit-win32/src/keyboard_layout.rs:519
- FunctionTooLong: winit_common::xkb::keymap::physicalkey_to_scancode winit-common/src/xkb/keymap.rs:302
- FunctionTooLong: winit_common::xkb::keymap::scancode_to_physicalkey winit-common/src/xkb/keymap.rs:34
- FunctionTooLong: winit_win32::keyboard::physicalkey_to_scancode winit-win32/src/keyboard.rs:897
- FunctionTooLong: winit_win32::keyboard::scancode_to_physicalkey winit-win32/src/keyboard.rs:1093
- FunctionTooLong: winit_android::keycodes::to_physical_key winit-android/src/keycodes.rs:7
- FunctionTooLong: winit_appkit::window_delegate::new_window winit-appkit/src/window_delegate.rs:661
- FunctionTooLong: winit_appkit::event::physicalkey_to_scancode winit-appkit/src/event.rs:348
- FunctionTooLong: winit_appkit::event::scancode_to_physicalkey winit-appkit/src/event.rs:480
- FunctionTooLong: winit_appkit::cursor::cursor_from_icon winit-appkit/src/cursor.rs:234
- FunctionTooLong: winit_orbital::event_loop::convert_scancode winit-orbital/src/event_loop.rs:39
- XxxComment winit-x11/src/event_loop.rs:109
- XxxComment winit-x11/src/ime/context.rs:192
- XxxComment winit-wayland/src/popup.rs:220
- XxxComment winit-wayland/src/window/mod.rs:195
- XxxComment winit-wayland/src/popup.rs:455
- XxxComment winit-wayland/src/window/mod.rs:376
- XxxComment winit-wayland/src/window/mod.rs:171
- XxxComment winit-wayland/src/seat/text_input/mod.rs:95
- XxxComment winit-wayland/src/event_loop/mod.rs:78
- XxxComment winit-appkit/src/window_delegate.rs:1524
- XxxComment winit-android/src/event_loop.rs:238
- XxxComment winit-android/src/event_loop.rs:256
- XxxComment winit-android/src/event_loop.rs:239
- XxxComment winit-android/src/event_loop.rs:251
- FixmeComment winit-x11/src/window.rs:1127
- FixmeComment winit-win32/src/event_loop.rs:455
- FixmeComment winit-win32/src/event_loop.rs:1177
- FixmeComment winit-win32/src/keyboard.rs:537
- FixmeComment winit-win32/src/lib.rs:5
- FixmeComment winit-win32/src/event_loop/runner.rs:122
- FixmeComment winit-uikit/src/monitor.rs:239
- FixmeComment winit-core/src/event_loop/pump_events.rs:5
- FixmeComment winit-common/src/core_foundation/event_loop_proxy.rs:23
- FixmeComment winit-common/src/core_foundation/event_loop_proxy.rs:100
- FixmeComment winit-appkit/src/app.rs:155
- FixmeComment winit-appkit/src/app.rs:164
- FixmeComment winit-android/src/event_loop.rs:819
- FixmeComment winit/examples/util/fill.rs:14
- Hotspot: winit-win32/src/event_loop.rs winit-win32/src/event_loop.rs:1237
- Hotspot: winit-appkit/src/window_delegate.rs winit-appkit/src/window_delegate.rs:661
- Hotspot: winit-wayland/src/event_loop/mod.rs winit-wayland/src/event_loop/mod.rs:347
- Hotspot: winit-x11/src/atoms.rs winit-x11/src/atoms.rs:22
- Hotspot: winit-orbital/src/event_loop.rs winit-orbital/src/event_loop.rs:358
- Hotspot: winit-x11/src/window.rs winit-x11/src/window.rs:459
- Hotspot: winit-wayland/src/seat/pointer/mod.rs winit-wayland/src/seat/pointer/mod.rs:37
- Hotspot: winit-x11/src/event_processor.rs winit-x11/src/event_processor.rs:376
- Hotspot: winit-win32/src/window.rs winit-win32/src/window.rs:1572
- Hotspot: winit-wayland/src/types/wp_tablet_input_v2.rs winit-wayland/src/types/wp_tablet_input_v2.rs:92
- Hotspot: winit-win32/src/window_state.rs winit-win32/src/window_state.rs:303
- TooManyMethods: UnownedWindow winit-x11/src/window.rs:433
- TooManyMethods: WindowDelegate winit-appkit/src/window_delegate.rs:138
- TooManyMethods: WindowState winit-wayland/src/window/state.rs:60
- TooManyMethods: Inner winit-uikit/src/window.rs:114
- TooManyMethods: XConnection winit-x11/src/xdisplay.rs:24
- TooManyMethods: WindowCommon winit-wayland/src/window/common.rs:22
- TooManyMethods: EventProcessor winit-x11/src/event_processor.rs:56
- TooManyMethods: Shared winit-web/src/event_loop/runner.rs:32
- TooManyMethods: WinitView winit-appkit/src/view.rs:154
- TooManyMethods: Canvas winit-web/src/web_sys/canvas.rs:35
- TooManyMethods: AppState winit-appkit/src/app_state.rs:27
- Duplicated block (9 lines × 2) winit-appkit/src/window_delegate.rs:1481
- Duplicated block (9 lines × 2) winit-common/src/xkb/keymap.rs:316
- Duplicated block (9 lines × 2) winit-wayland/src/data_transfer.rs:1190
- Duplicated block (9 lines × 2) winit-wayland/src/seat/pointer/pointer_gesture.rs:98
- Duplicated block (9 lines × 2) winit-win32/src/event_loop.rs:1947
- Duplicated block (9 lines × 2) winit-web/src/event_loop/runner.rs:408
- Duplicated block (9 lines × 2) winit-wayland/src/window/state.rs:311
- HackComment winit-win32/src/event_loop.rs:1304
- HackComment winit-win32/src/keyboard_layout.rs:394
- HackComment winit-wayland/src/data_transfer.rs:1050
- HackComment winit-wayland/src/window/state.rs:263
- HackComment winit-wayland/src/seat/keyboard/mod.rs:89
- HackComment winit-wayland/src/seat/keyboard/mod.rs:245
- Duplicated block (10 lines × 2) winit-android/src/event_loop.rs:365
- Duplicated block (10 lines × 2) winit-common/src/xkb/keymap.rs:373
- Duplicated block (10 lines × 2) winit-win32/src/window.rs:712
- Duplicated block (10 lines × 2) winit-appkit/src/window.rs:340
- Duplicated block (10 lines × 2) winit-wayland/src/data_transfer.rs:561
- Duplicated block (10 lines × 2) winit-android/src/keycodes.rs:257
- Duplicated block (8 lines × 2) winit-android/src/event_loop.rs:998
- Duplicated block (8 lines × 2) winit-appkit/src/event.rs:432
- Duplicated block (8 lines × 2) winit-appkit/src/window_delegate.rs:1304
- Duplicated block (8 lines × 2) winit-uikit/src/app_state.rs:361
- Duplicated block (8 lines × 2) winit-win32/src/window.rs:561
- Duplicated block (8 lines × 2) winit-web/src/event_loop/runner.rs:370
- EventLoop::single_iteration (cognitive 41) winit-wayland/src/event_loop/mod.rs:347
- EventLoop::handle_input_event (cognitive 39) winit-android/src/event_loop.rs:317
- EventLoop::single_iteration (cognitive 23) winit-android/src/event_loop.rs:173
- EventLoop::process_event (cognitive 17) winit-orbital/src/event_loop.rs:358
- EventLoop::poll_events_with_timeout (cognitive 16) winit-wayland/src/event_loop/mod.rs:246
- EventProcessor::process_xevent (cognitive 38) winit-x11/src/event_processor.rs:150
- EventProcessor::client_message (cognitive 28) winit-x11/src/event_processor.rs:376
- EventProcessor::configure_notify (cognitive 25) winit-x11/src/event_processor.rs:844
- EventProcessor::xinput_key_input (cognitive 23) winit-x11/src/event_processor.rs:1099
- EventProcessor::xkb_event (cognitive 17) winit-x11/src/event_processor.rs:1751
- ClassTooLong: UnownedWindow winit-x11/src/window.rs:433
- ClassTooLong: EventProcessor winit-x11/src/event_processor.rs:56
- ClassTooLong: WindowDelegate winit-appkit/src/window_delegate.rs:138
- ClassTooLong: Window winit-win32/src/window.rs:95
- ClassTooLong: WindowState winit-wayland/src/window/state.rs:60
- EventLoop::handle_input_event (cyclomatic 28) winit-android/src/event_loop.rs:317
- EventLoop::single_iteration (cyclomatic 27) winit-android/src/event_loop.rs:173
- EventLoop::single_iteration (cyclomatic 24) winit-wayland/src/event_loop/mod.rs:347
- EventLoop::process_event (cyclomatic 20) winit-orbital/src/event_loop.rs:358
- Duplicated block (7 lines × 2) winit-uikit/src/window.rs:89
- Duplicated block (7 lines × 2) winit-win32/src/event_loop.rs:1945
- Duplicated block (7 lines × 2) winit-win32/src/event_loop.rs:1975
- Duplicated block (7 lines × 2) winit-web/src/web_sys/mod.rs:89
- winit_win32::keyboard::physicalkey_to_scancode (cyclomatic 160) winit-win32/src/keyboard.rs:897
- winit_win32::event_loop::public_window_callback_inner (cyclomatic 155) winit-win32/src/event_loop.rs:1237
- winit_win32::event_loop::handle_raw_input (cyclomatic 16) winit-win32/src/event_loop.rs:2659
- winit_win32::event_loop::public_window_callback_inner (cognitive 261) winit-win32/src/event_loop.rs:1237
- winit_win32::event_loop::handle_raw_input (cognitive 28) winit-win32/src/event_loop.rs:2659
- winit_win32::dpi::hwnd_dpi (cognitive 16) winit-win32/src/dpi.rs:75
- winit_appkit::cursor::cursor_from_icon (cognitive 49) winit-appkit/src/cursor.rs:234
- winit_appkit::window_delegate::new_window (cognitive 38) winit-appkit/src/window_delegate.rs:661
- winit_appkit::event::create_key_event (cognitive 16) winit-appkit/src/event.rs:82
- WinitState::event (cognitive 49) winit-wayland/src/seat/keyboard/mod.rs:23
- WinitState::pointer_frame (cognitive 42) winit-wayland/src/seat/pointer/mod.rs:37
- WinitState::remove_capability (cognitive 17) winit-wayland/src/seat/mod.rs:225
- Change coupling: util.rs ↔ view.rs winit-appkit/src/util.rs:1
- Change coupling: window_target.rs ↔ pointer.rs winit-web/src/event_loop/window_target.rs:1
- Change coupling: mod.rs ↔ mod.rs winit-wayland/src/seat/pointer/mod.rs:1
- Duplicated block (12 lines × 2) winit-android/src/event_loop.rs:580
- Duplicated block (12 lines × 2) winit-common/src/xkb/keymap.rs:468
- Duplicated block (12 lines × 2) winit-win32/src/event_loop.rs:2008
- Duplicated block (6 lines × 2) winit-web/src/web_sys/pointer.rs:47
- Duplicated block (6 lines × 2) winit-appkit/src/data_transfer.rs:448
- Duplicated block (6 lines × 2) winit-appkit/src/cursor.rs:70
- Duplicated block (5 lines × 2) winit-web/src/web_sys/schedule.rs:125
- Duplicated block (5 lines × 2) winit-appkit/src/window.rs:334
- Duplicated block (5 lines × 2) winit-appkit/src/window.rs:351
- winit_appkit::cursor::cursor_from_icon (cyclomatic 48) winit-appkit/src/cursor.rs:234
- winit_appkit::window_delegate::new_window (cyclomatic 34) winit-appkit/src/window_delegate.rs:661
- EventProcessor::process_xevent (cyclomatic 42) winit-x11/src/event_processor.rs:150
- EventProcessor::client_message (cyclomatic 17) winit-x11/src/event_processor.rs:376
- WinitState::event (cyclomatic 34) winit-wayland/src/seat/keyboard/mod.rs:23
- WinitState::pointer_frame (cyclomatic 29) winit-wayland/src/seat/pointer/mod.rs:37
- WindowDelegate::set_fullscreen (cyclomatic 23) winit-appkit/src/window_delegate.rs:1815
- WindowDelegate::new (cyclomatic 19) winit-appkit/src/window_delegate.rs:912
- WindowFlags::apply_diff (cyclomatic 21) winit-win32/src/window_state.rs:383
- WindowFlags::to_window_styles (cyclomatic 19) winit-win32/src/window_state.rs:303
- KeyEventBuilder::process_message (cognitive 54) winit-win32/src/keyboard.rs:76
- KeyEventBuilder::synthesize_kbd_state (cognitive 17) winit-win32/src/keyboard.rs:311
- WinitView::handle_touches (cognitive 53) winit-uikit/src/view.rs:480
- WinitView::update_modifiers (cognitive 25) winit-appkit/src/view.rs:1083
- WindowDelegate::set_fullscreen (cognitive 28) winit-appkit/src/window_delegate.rs:1815
- WindowDelegate::new (cognitive 18) winit-appkit/src/window_delegate.rs:912
- WindowFlags::apply_diff (cognitive 27) winit-win32/src/window_state.rs:383
- WindowFlags::to_window_styles (cognitive 23) winit-win32/src/window_state.rs:303
- PartialKeyEventInfo::from_message (cognitive 18) winit-win32/src/keyboard.rs:493
- PartialKeyEventInfo::finalize (cognitive 16) winit-win32/src/keyboard.rs:586
- TooManyFields: WindowState winit-wayland/src/window/state.rs:60
- TooManyFields: WinitState winit-wayland/src/state.rs:47
- Duplicated block (17 lines × 2) winit-appkit/src/cursor.rs:51
- Duplicated block (17 lines × 2) winit-web/src/web_sys/event.rs:290
- Duplicated block (12–13 lines × 2) winit-android/src/event_loop.rs:379
- Duplicated block (12–13 lines × 2) winit-uikit/src/view.rs:565
- Duplicated block (13 lines × 2) winit-web/src/web_sys/pointer.rs:92
- Duplicated block (13 lines × 2) winit-x11/src/ime/context.rs:265
- Duplicated block (11 lines × 2) winit-wayland/src/event_loop/mod.rs:447
- Duplicated block (11 lines × 2) winit-web/src/web_sys/canvas.rs:299
- Duplicated block (7 lines × 3) winit-appkit/src/data_transfer.rs:84
- Duplicated block (7 lines × 3) winit-appkit/src/event_loop.rs:99
- Low cohesion: ActiveEventLoop (LCOM4 4) winit-appkit/src/event_loop.rs:51
- Low cohesion: ActiveEventLoop (LCOM4 4) winit-win32/src/event_loop.rs:450
- TabletToolData::event (cyclomatic 36) winit-wayland/src/types/wp_tablet_input_v2.rs:92
- UnownedWindow::new (cyclomatic 35) winit-x11/src/window.rs:459
- KeyEventBuilder::process_message (cyclomatic 29) winit-win32/src/keyboard.rs:76
- LayoutCache::prepare_layout (cyclomatic 27) winit-win32/src/keyboard_layout.rs:286
- ContentType::from (cyclomatic 22) winit-wayland/src/seat/text_input/mod.rs:398
- WinitView::handle_touches (cyclomatic 18) winit-uikit/src/view.rs:480
- TextInputState::event (cyclomatic 18) winit-wayland/src/seat/text_input/mod.rs:56
- TabletToolAngle::tilt (cyclomatic 16) winit-core/src/event.rs:1400
- WindowState::configure_frame_and_size (cyclomatic 16) winit-wayland/src/window/state/configure.rs:61
- Shared::set_listener (cyclomatic 16) winit-web/src/event_loop/runner.rs:280
- LayoutCache::prepare_layout (cognitive 59) winit-win32/src/keyboard_layout.rs:286
- UnownedWindow::new (cognitive 40) winit-x11/src/window.rs:459
- TabletToolData::event (cognitive 28) winit-wayland/src/types/wp_tablet_input_v2.rs:92
- Shared::set_listener (cognitive 24) winit-web/src/event_loop/runner.rs:280
- Device::new (cognitive 24) winit-x11/src/event_loop.rs:1225
- TextInputState::event (cognitive 21) winit-wayland/src/seat/text_input/mod.rs:56
- winit_common::core_foundation::tracing_observers::tracing_observers (cognitive 20) winit-common/src/core_foundation/tracing_observers.rs:19
- winit_uikit::app_state::handle_nonuser_events (cognitive 19) winit-uikit/src/app_state.rs:291
- WindowState::configure_frame_and_size (cognitive 18) winit-wayland/src/window/state/configure.rs:61
- CursorHandler::set_cursor (cognitive 18) winit-web/src/cursor.rs:200
- CursorFlags::refresh_os_cursor (cognitive 18) winit-win32/src/window_state.rs:549
- TabletToolTilt::angle (cognitive 16) winit-core/src/event.rs:1307
- TabletToolAngle::tilt (cognitive 16) winit-core/src/event.rs:1400
- SourceDataObjectData::GetData (cognitive 16) winit-win32/src/data_transfer.rs:1478
- REDACTED
- REDACTED
- Members sharing a duplicated core (7 members, 50+ identical tokens) winit-win32/src/window.rs:496
- Members sharing a duplicated core (4 members, 50+ identical tokens) winit-android/src/event_loop.rs:517
- Duplicated block (21 lines × 2) winit-core/src/keyboard.rs:40
- Duplicated block (20–21 lines × 2) winit-wayland/src/popup.rs:203
- Duplicated block (18–19 lines × 2) winit-wayland/src/state.rs:325
- Duplicated block (17–18 lines × 2) winit-wayland/src/event_loop/mod.rs:209
- Duplicated block (18 lines × 2) winit-wayland/src/event_loop/mod.rs:284
- Duplicated block (12–14 lines × 2) winit-x11/src/event_processor.rs:1768
- Duplicated block (11–13 lines × 4) winit-android/src/event_loop.rs:519
- Duplicated block (5 lines × 7) winit-win32/src/window.rs:497
- Off the main sequence: dpi
- JavaScript dependencies are not locked
Minor — 95 finding(s)
- Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:458
- Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:605
- Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:609
- Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:632
- Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:641
- Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:647
- Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:658
- Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:668
- Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:674
- Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:714
- Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:730
- Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:763
- Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:772
- Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:791
- Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:796
- Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:852
- Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:855
- Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:860
- Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:883
- Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:888
- Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:922
- Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:1016
- Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:1022
- Interpolated log message defeats structured logging winit-x11/src/event_loop.rs:108
- Interpolated log message defeats structured logging winit-x11/src/event_loop.rs:256
- Orphaned file winit-win32/src/raw_input.rs:1
- Orphaned file winit-x11/src/util/geometry.rs:1
- Orphaned file winit-web/src/web_sys/schedule.rs:1
- Orphaned file winit-web/src/web_sys/resize_scaling.rs:1
- Orphaned file winit-x11/src/xsettings.rs:1
- Orphaned file winit-web/src/web_sys/mod.rs:1
- Orphaned file winit-win32/src/definitions.rs:1
- Orphaned file winit-x11/src/ime/callbacks.rs:1
- Orphaned file winit-common/src/core_foundation/tracing_observers.rs:1
- Orphaned file winit-win32/src/dark_mode.rs:1
- Orphaned file winit-x11/src/util/modifiers.rs:1
- Orphaned file winit-x11/src/util/wm.rs:1
- Orphaned file winit-web/src/web_sys/fullscreen.rs:1
- Orphaned file winit-common/src/core_foundation/event_loop_proxy.rs:1
- Orphaned file winit-web/src/async/dispatcher.rs:1
- Orphaned file winit-x11/src/util/hint.rs:1
- Orphaned file winit-web/src/async/wrapper.rs:1
- Orphaned file winit-appkit/src/menu.rs:1
- Orphaned file winit-x11/src/util/input.rs:1
- Orphaned file winit-wayland/src/types/xdg_toplevel_icon_manager.rs:1
- Orphaned file winit-web/src/lock.rs:1
- Orphaned file winit-appkit/src/observer.rs:1
- Orphaned file winit-web/src/main_thread.rs:1
- README/code drift winit-android/README.md:16
- README/code drift winit-android/README.md:38
- README/code drift winit-appkit/README.md:16
- README/code drift winit-appkit/README.md:38
- README/code drift winit-common/README.md:16
- README/code drift winit-common/README.md:38
- README/code drift winit-core/README.md:16
- README/code drift winit-core/README.md:38
- README/code drift winit-orbital/README.md:16
- README/code drift winit-orbital/README.md:38
- README/code drift winit-uikit/README.md:16
- README/code drift winit-uikit/README.md:38
- README/code drift winit-wayland/README.md:16
- README/code drift winit-wayland/README.md:38
- README/code drift winit-web/README.md:16
- README/code drift winit-web/README.md:38
- README/code drift winit-win32/README.md:16
- README/code drift winit-win32/README.md:38
- README/code drift winit-x11/README.md:16
- README/code drift winit-x11/README.md:38
- README/code drift winit/README.md:38
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- REDACTED
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Silent fallback default on Err winit-orbital/src/lib.rs:114
Minor — 2 finding(s)
- Outdated: smol_str
- Off the main sequence: winit-common
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-9295060c306743a1b9efd485a926d155/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-9295060c306743a1b9efd485a926d155/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 . | 23 | 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 . | 0 | — |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.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 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |