Public report of rust-windowing/winit, published 14 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 14 November 2026, 18:10 UTC · Survey ID cd_248452f4c34c449788b2ee2ed4e91469
rust-windowing/winit
Measured 14 November 2026, 18:09 UTC, at code version f0abec9
Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
No change since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 62,901 lines of product code in 12 projects, tests not counted · Estimated rebuild effort: about 0.5 person-years · Weakest lens: Maturity, 46
Findings by how serious they are
32 critical499 serious92 minor
8 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 18:09 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
44of 44 dimensions measured by tools.
615of 623 findings point to an exact file and line, so you can open each one in the code. The other 8 concern the repository as a whole, such as missing documentation.
44dimensions across 7 lenses, read from 62,901 lines of product code in 12 projects.
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 63 out of 100 and is rated Adequate, and 23 of its 32 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 nine 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 product code is 62,901 lines, about €75,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Maturity rose from 46 to 62, the lowest score rated Strong, the score would rise from 63 to about 71.
Code composition: what the lines of code are
Product code 96%Tests 4%
New since the last survey: 194 findings
These 194 critical or serious findings weren't in the previous survey, on 27 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
God Classes · FileTooLong: window/state.rs winit-wayland/src/window/state.rs
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) winit-android/src/event_loop.rs
Code Duplication · Edited copy of a member (195 corresponding lines) winit-common/src/xkb/keymap.rs
Code Duplication · Edited copy of a member (172 corresponding lines) winit-common/src/xkb/keymap.rs
Code Duplication · Edited copy of a member (61 corresponding lines) winit-wayland/src/event_loop/mod.rs
Code Duplication · Edited copy of a member (29 corresponding lines) winit-web/src/web_sys/pointer.rs
Code Duplication · Edited copy of a member (30 corresponding lines) winit-core/src/keyboard.rs
Code Duplication · Edited copy of a member (30 corresponding lines) winit-appkit/src/cursor.rs
Code Duplication · Edited copy of a member (34 corresponding lines) winit-win32/src/window.rs
Code Duplication · Edited copy of a member (31 corresponding lines) winit-wayland/src/state.rs
Code Duplication · Edited copy of a member (23 corresponding lines) winit-wayland/src/window/state.rs
Code Duplication · Edited copy of a member (18 corresponding lines) winit-appkit/src/window_delegate.rs
Code Duplication · Edited copy of a member (25 corresponding lines) winit-android/src/event_loop.rs
Code Duplication · Edited copy of a member (24 corresponding lines) winit-wayland/src/data_transfer.rs
Code Duplication · Edited copies of one member (4 members, 19+ corresponding lines) winit-uikit/src/view.rs
Code Duplication · Edited copy of a member (17 corresponding lines) winit-win32/src/window.rs
Code Duplication · Edited copy of a member (19 corresponding lines) winit-web/src/web_sys/canvas.rs
Code Duplication · Edited copy of a member (13 corresponding lines) winit-web/src/web_sys/pointer.rs
Code Duplication · Edited copy of a member (16 corresponding lines) winit-wayland/src/data_transfer.rs
Code Duplication · Edited copy of a member (16 corresponding lines) winit-win32/src/window.rs
Code Duplication · Edited copy of a member (15 corresponding lines) winit-uikit/src/app_state.rs
Code Duplication · Edited copies of one member (4 members, 20+ corresponding lines) winit-web/src/web_sys/event.rs
Code Duplication · Edited copy of a member (19 corresponding lines) winit-win32/src/icon.rs
Code Duplication · Edited copy of a member (17 corresponding lines) winit-x11/src/window.rs
Code Duplication · Edited copy of a member (20 corresponding lines) winit-appkit/src/observer.rs
Code Duplication · Edited copy of a member (8 corresponding lines) dpi/src/lib.rs
Code Duplication · Edited copy of a member (11 corresponding lines) winit-appkit/src/window_delegate.rs
Code Duplication · Edited copy of a member (10 corresponding lines) winit-win32/src/window.rs
Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) winit-web/src/web_sys/mod.rs
Code Duplication · Edited copy of a member (21 corresponding lines) winit-android/src/event_loop.rs
Code Duplication · Edited copy of a member (9 corresponding lines) winit-common/src/xkb/mod.rs
Code Duplication · Edited copy of a member (10 corresponding lines) winit-x11/src/ime/mod.rs
Code Duplication · Edited copy of a member (9 corresponding lines) winit-x11/src/xsettings.rs
Code Duplication · Edited copy of a member (8 corresponding lines) winit-wayland/src/event_loop/mod.rs
Code Duplication · Edited copy of a member (14 corresponding lines) winit-wayland/src/data_transfer.rs
Code Duplication · Edited copy of a member (7 corresponding lines) winit-common/src/xkb/mod.rs
Code Duplication · Edited copy of a member (12 corresponding lines) winit-x11/src/window.rs
Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) winit-x11/src/window.rs
Code Duplication · Edited copy of a member (7 corresponding lines) winit-wayland/src/state.rs
Code Duplication · Edited copy of a member (8 corresponding lines) winit-win32/src/util.rs
Code Duplication · Edited copy of a member (9 corresponding lines) winit-web/src/web_sys/canvas.rs
Code Duplication · Edited copies of one member (4 members, 11+ corresponding lines) winit-web/src/window.rs
Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) winit-orbital/src/window.rs
Code Duplication · Edited copy of a member (10 corresponding lines) winit-appkit/src/data_transfer.rs
Code Duplication · Edited copy of a member (6 corresponding lines) winit-appkit/src/view.rs
Code Duplication · Edited copy of a member (7 corresponding lines) winit-common/src/xkb/keymap.rs
Code Duplication · Edited copy of a member (9 corresponding lines) winit-wayland/src/seat/pointer/mod.rs
Code Duplication · Edited copy of a member (5 corresponding lines) winit-appkit/src/window_delegate.rs
Code Duplication · Edited copy of a member (7 corresponding lines) winit-appkit/src/window.rs
Code Duplication · Edited copies of one member (6 members, 3+ corresponding lines) winit-android/src/event_loop.rs
Code Duplication · Edited copy of a member (8 corresponding lines) winit-wayland/src/window/handles.rs
Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) winit-appkit/src/data_transfer.rs
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 30 findings
These 30 critical or serious findings were in the previous survey, on 27 October 2026, and are gone from this one.
€25,000 to €120,000, for 415 to 1,315 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 63. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 62,901 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
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.
Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Resolve the 115 Low coverage finding(s) in Code Coverage — start with mod.rs (15), cursor.rs (5), state.rs (4).
Raises the score by about 4 points · High effort · Code Coverage
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Files that change often carry extra risk · Combined risk
4 files are changed often and are hard to read, which makes them the likeliest places for a mistake. They also have under half their code tested, or were written almost entirely by one person, so a mistake there is less likely to be caught, or only one person knows the code well enough to avoid it. A change to these files therefore carries more risk than the overall score suggests.
Based on: Churn × Complexity Hotspots (6 files) · Code Coverage (78 files under half tested) · Bus Factor (0 files written almost entirely by one person) · The files: event_loop.rs, mod.rs and window.rs
What to do: Add tests to these files and have a second person review every change to them, starting with event_loop.rs, mod.rs and window.rs.
Where the investment is most exposed · Value at risk
This code would cost about €75,000 to build again, about 0.5 person-years of work. Its weakest lens is Maturity, at 46 (Weak). Maturity is about how well the project explains and looks after itself, which decides whether a new developer, or a new supplier, can take over. Because the weakest lens counts most in the score, work on Maturity also moves the score most.
Based on: the rebuild estimate · the Maturity grade · how much each lens counts
What to do: Start with the Maturity actions in Top priorities.
If you do one thing first · First action
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. Of all the actions in this report, it raises the score most for the work it takes: about 12 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.1 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 14,672 lines over the last 90 days, which is about 59,503 lines a year. At that pace, the extra work comes to an estimated 3.3 to 19.8 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
171 modules, with 532 dependencies between them. 5 loops run through 54 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 131 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
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.
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.
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.
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.
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.
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.
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.
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.
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.
winit_core.event_loop uses winit_core.monitor, so a change to winit_core.monitor can break winit_core.event_loop, while a change to winit_core.event_loop can't break winit_core.monitor.
Position
Below the diagonal: winit_core.event_loop uses a module listed above it, which is the healthy 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.
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.
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.Icon
winit_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.
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.
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.
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.
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.
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.
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.
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.
14→31 winit_wayland.window.state uses winit_wayland.statepart of a loop✕
Connections
3 pairs of types, where a type in winit_wayland.window.state uses a type in winit_wayland.state.
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
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→34 winit_wayland.window.state uses winit_wayland.event_looppart of a loop✕
Connections
2 pairs of types, where a type in winit_wayland.window.state uses a type in winit_wayland.event_loop.
winit_wayland.window.state uses winit_wayland.event_loop, so a change to winit_wayland.event_loop can break winit_wayland.window.state, while a change to winit_wayland.window.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.
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.
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.
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.
15→22 winit_web.web_sys.canvas uses winit_web.windowpart of a loop✕
Connections
3 pairs of types, where a type in winit_web.web_sys.canvas uses a type in winit_web.window.
winit_web.web_sys.canvas uses winit_web.window, so a change to winit_web.window can break winit_web.web_sys.canvas, while a change to winit_web.web_sys.canvas can't break winit_web.window.
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→38 winit_web.web_sys.canvas uses winit_web.cursorpart of a loop✕
Connections
1 pair of types, where a type in winit_web.web_sys.canvas uses a type in winit_web.cursor.
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.
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.
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.
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.
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.
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.
17→24 winit_x11.xdisplay uses winit_x11.windowpart of a loop✕
Connections
1 pair of types, where a type in winit_x11.xdisplay uses a type in winit_x11.window.
winit_x11.xdisplay uses winit_x11.window, so a change to winit_x11.window can break winit_x11.xdisplay, while a change to winit_x11.xdisplay can't break winit_x11.window.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
winit_orbital.event_loop uses winit_core.monitor, so a change to winit_core.monitor can break winit_orbital.event_loop, while a change to winit_orbital.event_loop can't break winit_core.monitor.
Position
Below the diagonal: winit_orbital.event_loop uses a module listed above it, which is the healthy 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.
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.
winit_wayland.window.common uses dpi, so a change to dpi can break winit_wayland.window.common, while a change to winit_wayland.window.common can't break dpi.
Position
Below the diagonal: winit_wayland.window.common uses a module listed above it, which is the healthy direction.
winit_wayland.window.common uses winit_core.cursor, so a change to winit_core.cursor can break winit_wayland.window.common, while a change to winit_wayland.window.common can't break winit_core.cursor.
Position
Below the diagonal: winit_wayland.window.common uses a module listed above it, which is the healthy direction.
winit_wayland.window.common uses winit_core.icon, so a change to winit_core.icon can break winit_wayland.window.common, while a change to winit_wayland.window.common can't break winit_core.icon.
Position
Below the diagonal: winit_wayland.window.common uses a module listed above it, which is the healthy direction.
winit_wayland.window.common uses winit_core.monitor, so a change to winit_core.monitor can break winit_wayland.window.common, while a change to winit_wayland.window.common can't break winit_core.monitor.
Position
Below the diagonal: winit_wayland.window.common uses a module listed above it, which is the healthy direction.
winit_wayland.window.common uses winit_core.window, so a change to winit_core.window can break winit_wayland.window.common, while a change to winit_wayland.window.common can't break winit_core.window.
Position
Below the diagonal: winit_wayland.window.common uses a module listed above it, which is the healthy direction.
winit_wayland.window.common uses winit_wayland.window.state, so a change to winit_wayland.window.state can break winit_wayland.window.common, while a change to winit_wayland.window.common can't break winit_wayland.window.state.
Position
Below the diagonal: winit_wayland.window.common uses a module listed above it, which is the healthy 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.
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.
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.
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.
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.
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.
22→28 winit_web.window uses winit_web.monitorpart of a loop✕
Connections
1 pair of types, where a type in winit_web.window uses a type in winit_web.monitor.
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
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→37 winit_web.window uses winit_web.event_loop.window_targetpart of a loop✕
Connections
1 pair of types, where a type in winit_web.window uses a type in winit_web.event_loop.window_target.
winit_web.window uses winit_web.event_loop.window_target, so a change to winit_web.event_loop.window_target can break winit_web.window, while a change to winit_web.window can't break winit_web.event_loop.window_target.
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.
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.
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.
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.
23→29 winit_win32.event_loop.runner uses winit_win32.event_looppart of a loop✕
Connections
1 pair of types, where a type in winit_win32.event_loop.runner uses a type in winit_win32.event_loop.
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
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.
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.
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.
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.
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.
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.
24→30 winit_x11.window uses winit_x11.event_looppart of a loop✕
Connections
3 pairs of types, where a type in winit_x11.window uses a type in winit_x11.event_loop.
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
winit_wayland.window uses winit_core.cursor, so a change to winit_core.cursor can break winit_wayland.window, while a change to winit_wayland.window can't break winit_core.cursor.
Position
Below the diagonal: winit_wayland.window uses a module listed above it, which is the healthy direction.
winit_wayland.window uses winit_core.icon, so a change to winit_core.icon can break winit_wayland.window, while a change to winit_wayland.window can't break winit_core.icon.
Position
Below the diagonal: winit_wayland.window uses a module listed above it, which is the healthy direction.
winit_wayland.window uses winit_core.monitor, so a change to winit_core.monitor can break winit_wayland.window, while a change to winit_wayland.window can't break winit_core.monitor.
Position
Below the diagonal: winit_wayland.window uses a module listed above it, which is the healthy direction.
winit_wayland.window uses winit_common.xkb, so a change to winit_common.xkb can break winit_wayland.window, while a change to winit_wayland.window can't break winit_common.xkb.
Position
Below the diagonal: winit_wayland.window uses a module listed above it, which is the healthy direction.
winit_wayland.window uses winit_core.window, so a change to winit_core.window can break winit_wayland.window, while a change to winit_wayland.window can't break winit_core.window.
Position
Below the diagonal: winit_wayland.window uses a module listed above it, which is the healthy direction.
winit_wayland.window uses winit_wayland.window.state, so a change to winit_wayland.window.state can break winit_wayland.window, while a change to winit_wayland.window can't break winit_wayland.window.state.
Position
Below the diagonal: winit_wayland.window uses a module listed above it, which is the healthy direction.
winit_wayland.window uses winit_wayland.window.common, so a change to winit_wayland.window.common can break winit_wayland.window, while a change to winit_wayland.window can't break winit_wayland.window.common.
Position
Below the diagonal: winit_wayland.window uses a module listed above it, which is the healthy direction.
27→31 winit_wayland.window uses winit_wayland.statepart of a loop✕
Connections
2 pairs of types, where a type in winit_wayland.window uses a type in winit_wayland.state.
winit_wayland.window uses winit_wayland.state, so a change to winit_wayland.state can break winit_wayland.window, while a change to winit_wayland.window can't break winit_wayland.state.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→34 winit_wayland.window uses winit_wayland.event_looppart of a loop✕
Connections
2 pairs of types, where a type in winit_wayland.window uses a type in winit_wayland.event_loop.
winit_wayland.window uses winit_wayland.event_loop, so a change to winit_wayland.event_loop can break winit_wayland.window, while a change to winit_wayland.window 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.
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.
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.
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.
winit_web.monitor uses winit_web.window, so a change to winit_web.window can break winit_web.monitor, while a change to winit_web.monitor can't break winit_web.window.
Position
Below the diagonal: winit_web.monitor uses a module listed above it, which is the healthy direction.
28→32 winit_web.monitor uses winit_web.event_loop.runnerpart of a loop✕
Connections
3 pairs of types, where a type in winit_web.monitor uses a type in winit_web.event_loop.runner.
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.
28→35 winit_web.monitor uses winit_web.event_loop.proxypart of a loop✕
Connections
1 pair of types, where a type in winit_web.monitor uses a type in winit_web.event_loop.proxy.
winit_web.monitor uses winit_web.event_loop.proxy, so a change to winit_web.event_loop.proxy can break winit_web.monitor, while a change to winit_web.monitor can't break winit_web.event_loop.proxy.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→39 winit_web.monitor uses winit_webpart of a loop✕
Connections
6 pairs of types, where a type in winit_web.monitor uses a type in winit_web.
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.
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.
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.
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.
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.
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.
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
Below the diagonal: winit_win32.event_loop uses a module listed above it, which is the healthy 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.
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.
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.
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.
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.
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.
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.
winit_x11.event_loop uses winit_x11.window, so a change to winit_x11.window can break winit_x11.event_loop, while a change to winit_x11.event_loop can't break winit_x11.window.
Position
Below the diagonal: winit_x11.event_loop uses a module listed above it, which is the healthy 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.
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.
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.
winit_wayland.state uses winit_wayland.window, so a change to winit_wayland.window can break winit_wayland.state, while a change to winit_wayland.state can't break winit_wayland.window.
Position
Below the diagonal: winit_wayland.state uses a module listed above it, which is the healthy direction.
31→34 winit_wayland.state uses winit_wayland.event_looppart of a loop✕
Connections
1 pair of types, where a type in winit_wayland.state uses a type in winit_wayland.event_loop.
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.
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.
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.
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.
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.
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.
winit_web.event_loop.runner uses winit_web.window, so a change to winit_web.window can break winit_web.event_loop.runner, while a change to winit_web.event_loop.runner can't break winit_web.window.
Position
Below the diagonal: winit_web.event_loop.runner uses a module listed above it, which is the healthy 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.
32→35 winit_web.event_loop.runner uses winit_web.event_loop.proxypart of a loop✕
Connections
3 pairs of types, where a type in winit_web.event_loop.runner uses a type in winit_web.event_loop.proxy.
winit_web.event_loop.runner uses winit_web.event_loop.proxy, so a change to winit_web.event_loop.proxy can break winit_web.event_loop.runner, while a change to winit_web.event_loop.runner can't break winit_web.event_loop.proxy.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→37 winit_web.event_loop.runner uses winit_web.event_loop.window_targetpart of a loop✕
Connections
2 pairs of types, where a type in winit_web.event_loop.runner uses a type in winit_web.event_loop.window_target.
winit_web.event_loop.runner uses winit_web.event_loop.window_target, so a change to winit_web.event_loop.window_target can break winit_web.event_loop.runner, while a change to winit_web.event_loop.runner can't break winit_web.event_loop.window_target.
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→39 winit_web.event_loop.runner uses winit_webpart of a loop✕
Connections
4 pairs of types, where a type in winit_web.event_loop.runner uses a type in winit_web.
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
winit_web.event_loop.proxy uses winit_web.main_thread, so a change to winit_web.main_thread can break winit_web.event_loop.proxy, while a change to winit_web.event_loop.proxy can't break winit_web.main_thread.
Position
Below the diagonal: winit_web.event_loop.proxy uses a module listed above it, which is the healthy direction.
winit_web.event_loop.proxy uses winit_core.event_loop, so a change to winit_core.event_loop can break winit_web.event_loop.proxy, while a change to winit_web.event_loop.proxy can't break winit_core.event_loop.
Position
Below the diagonal: winit_web.event_loop.proxy uses a module listed above it, which is the healthy direction.
winit_web.event_loop.proxy uses winit_web.event_loop.runner, so a change to winit_web.event_loop.runner can break winit_web.event_loop.proxy, while a change to winit_web.event_loop.proxy can't break winit_web.event_loop.runner.
Position
Below the diagonal: winit_web.event_loop.proxy uses a module listed above it, which is the healthy direction.
winit_wayland.popup uses winit_core.cursor, so a change to winit_core.cursor can break winit_wayland.popup, while a change to winit_wayland.popup can't break winit_core.cursor.
Position
Below the diagonal: winit_wayland.popup uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in winit_wayland.popup uses a type in winit_core.icon.
The types involved
winit_wayland.popup.Popup → winit_core.icon.Icon
Direction
winit_wayland.popup uses winit_core.icon, so a change to winit_core.icon can break winit_wayland.popup, while a change to winit_wayland.popup can't break winit_core.icon.
Position
Below the diagonal: winit_wayland.popup uses a module listed above it, which is the healthy direction.
winit_wayland.popup uses winit_core.monitor, so a change to winit_core.monitor can break winit_wayland.popup, while a change to winit_wayland.popup can't break winit_core.monitor.
Position
Below the diagonal: winit_wayland.popup uses a module listed above it, which is the healthy direction.
winit_wayland.popup uses winit_common.xkb, so a change to winit_common.xkb can break winit_wayland.popup, while a change to winit_wayland.popup can't break winit_common.xkb.
Position
Below the diagonal: winit_wayland.popup uses a module listed above it, which is the healthy direction.
winit_wayland.popup uses winit_core.window, so a change to winit_core.window can break winit_wayland.popup, while a change to winit_wayland.popup can't break winit_core.window.
Position
Below the diagonal: winit_wayland.popup uses a module listed above it, which is the healthy direction.
winit_wayland.popup uses winit_wayland.window.common, so a change to winit_wayland.window.common can break winit_wayland.popup, while a change to winit_wayland.popup can't break winit_wayland.window.common.
Position
Below the diagonal: winit_wayland.popup uses a module listed above it, which is the healthy direction.
winit_wayland.popup uses winit_wayland.event_loop, so a change to winit_wayland.event_loop can break winit_wayland.popup, while a change to winit_wayland.popup can't break winit_wayland.event_loop.
Position
Below the diagonal: winit_wayland.popup uses a module listed above it, which is the healthy direction.
winit_web.event_loop.window_target uses winit_core.cursor, so a change to winit_core.cursor can break winit_web.event_loop.window_target, while a change to winit_web.event_loop.window_target can't break winit_core.cursor.
Position
Below the diagonal: winit_web.event_loop.window_target uses a module listed above it, which is the healthy direction.
winit_web.event_loop.window_target uses winit_core.window, so a change to winit_core.window can break winit_web.event_loop.window_target, while a change to winit_web.event_loop.window_target can't break winit_core.window.
Position
Below the diagonal: winit_web.event_loop.window_target uses a module listed above it, which is the healthy direction.
winit_web.event_loop.window_target uses winit_core.event_loop, so a change to winit_core.event_loop can break winit_web.event_loop.window_target, while a change to winit_web.event_loop.window_target can't break winit_core.event_loop.
Position
Below the diagonal: winit_web.event_loop.window_target uses a module listed above it, which is the healthy direction.
winit_web.event_loop.window_target uses winit_web.web_sys.canvas, so a change to winit_web.web_sys.canvas can break winit_web.event_loop.window_target, while a change to winit_web.event_loop.window_target can't break winit_web.web_sys.canvas.
Position
Below the diagonal: winit_web.event_loop.window_target uses a module listed above it, which is the healthy direction.
winit_web.event_loop.window_target uses winit_web.event_loop.proxy, so a change to winit_web.event_loop.proxy can break winit_web.event_loop.window_target, while a change to winit_web.event_loop.window_target can't break winit_web.event_loop.proxy.
Position
Below the diagonal: winit_web.event_loop.window_target uses a module listed above it, which is the healthy direction.
37→38 winit_web.event_loop.window_target uses winit_web.cursorpart of a loop✕
Connections
1 pair of types, where a type in winit_web.event_loop.window_target uses a type in winit_web.cursor.
winit_web.event_loop.window_target uses winit_web.cursor, so a change to winit_web.cursor can break winit_web.event_loop.window_target, while a change to winit_web.event_loop.window_target 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.
37→39 winit_web.event_loop.window_target uses winit_webpart of a loop✕
Connections
3 pairs of types, where a type in winit_web.event_loop.window_target uses a type in winit_web.
winit_web.event_loop.window_target uses winit_web, so a change to winit_web can break winit_web.event_loop.window_target, while a change to winit_web.event_loop.window_target can't break winit_web.
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.
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.
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.
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.
winit_web.cursor uses winit_web.window, so a change to winit_web.window can break winit_web.cursor, while a change to winit_web.cursor can't break winit_web.window.
Position
Below the diagonal: winit_web.cursor uses a module listed above it, which is the healthy direction.
winit_web.cursor uses winit_web.event_loop.window_target, so a change to winit_web.event_loop.window_target can break winit_web.cursor, while a change to winit_web.cursor can't break winit_web.event_loop.window_target.
Position
Below the diagonal: winit_web.cursor uses a module listed above it, which is the healthy 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.
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.
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.
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.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
23
High / Critical
Roadmap
Top priorities: 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; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Resolve the 115 Low coverage finding(s) in Code Coverage — start with mod.rs (15), cursor.rs (5), state.rs (4).
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
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.
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
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 255).
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 32
A definite problem that already costs you something and drags the score down: a
missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here
tends to cause failures elsewhere.
Serious — 499
Likely wrong, but not failing yet. It degrades
the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to
carry for two years either.
Minor — 92
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 8
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 44 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 44 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 615 of 623 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
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; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies. osv: the scanner produced no output at all, so no dependency was actually scanned. This is reported as a measurement gap rather than a clean pass. osv-scanner documents exit 128 as "no package sources found" — but this scan only invoked it because the tree declares a source it supports (`pom.xml` and the resolved lockfiles among them), so the tool's report and this repository disagree. Check that those sources are reachable from the directory the scan ran in before concluding anything is missing. If this tree really does commit only range-pinned manifests, commit the lockfile your package manager produces — but only where your ecosystem HAS one and commits it: Maven has none at all (osv-scanner reads `pom.xml` directly) and Gradle writes one only under opt-in dependency locking, while a published Composer package and a published Dart library both deliberately exclude theirs. In those three, generate one in CI before the scan instead — a resolved dependency list or an SBOM fed to the scanner.
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; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies. osv: the scanner produced no output at all, so no dependency was actually scanned. This is reported as a measurement gap rather than a clean pass. osv-scanner documents exit 128 as "no package sources found" — but this scan only invoked it because the tree declares a source it supports (`pom.xml` and the resolved lockfiles among them), so the tool's report and this repository disagree. Check that those sources are reachable from the directory the scan ran in before concluding anything is missing. If this tree really does commit only range-pinned manifests, commit the lockfile your package manager produces — but only where your ecosystem HAS one and commits it: Maven has none at all (osv-scanner reads `pom.xml` directly) and Gradle writes one only under opt-in dependency locking, while a published Composer package and a published Dart library both deliberately exclude theirs. In those three, generate one in CI before the scan instead — a resolved dependency list or an SBOM fed to the scanner.
AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and 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 — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X4 Structured logging — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 58 further occurrence(s) are not listed individually; the score already reflects all 98.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
26 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.
+ 11 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with 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.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 17 more group(s) — more in Appendix A; the complete list is findings.md.
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 255). — Refactoring it lifts Cognitive Complexity from 5.0 to about 6.5/10.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.2 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 24 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 (24 warning-level).
Resolve the 17 MethodTooLong finding(s) in God Classes — start with event_loop.rs (3), mod.rs (3), event_processor.rs (2). — One of this dimension's main actionable groups (17 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).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
62 duplicated block group(s) detected. 4.7 % of the production lines (2,979 of 62,901) are in a reported copy. A further 52 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
Edited copy of a member (8 corresponding lines) · ×4dpi/src/lib.rs:694
+ 56 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 10 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with keymap.rs (2), runner.rs (2), window.rs (2). — One of this dimension's main actionable groups (10 warning-level).
Resolve the 8 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with event_loop.rs (2), keymap.rs (2), keycodes.rs. — One of this dimension's main actionable groups (8 warning-level).
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).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.3 / 10Stronggated by 1 serious finding✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
12 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence.
Off the main sequence: dpi
Off the main sequence: winit-common
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 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).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D8 · Code Coverage1.0 / 10Critical✓ Tool-verified
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Line coverage 2.8% — 115 file(s) below 50%. Measured from the Rust suite (repository root: `cargo test --workspace` instrumented over 120 production file(s), 15 test binaries and 1 doc-test binaries).
Resolve the 115 Low coverage finding(s) in Code Coverage — start with mod.rs (15), cursor.rs (5), state.rs (4). — One of this dimension's main actionable groups (115 warning-level).
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
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.
Outdated: smol_str
✓ On the Gold path — maintain.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 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.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 7 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs (2), event_loop.rs, window_delegate.rs. — One of this dimension's main actionable groups (7 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.6 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
5 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is winit-appkit/src/app.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.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
115 deducted task-comment markers across 62901 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.
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 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).
Resolve the 13 XxxComment finding(s) in Explicit Debt — start with event_loop.rs (5), mod.rs (5), context.rs. — One of this dimension's main actionable groups (13 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
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 1184), `winit-web/src/cursor.rs` (line 489, lines 609–610, line 611, …), `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.
REDACTED
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
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).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
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. osv was not scanned (osv: 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.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
22 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-x11/src/util/geometry.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.
Resolve the 22 Orphaned file finding(s) in Knowledge Freshness — start with geometry.rs, schedule.rs, resize_scaling.rs. — One of this dimension's main actionable groups (22 recommendation-level).
Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 9 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 (9 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).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
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. osv was not scanned (osv: 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.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Other · Event Sourcing — Whether domain events stay immutable (private fields, set once) rather than carrying mutable state.
Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
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.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
`REDACTED` schedules updates, but no `package-ecosystem` entry covers `cargo`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:3
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.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`error!` at line 457 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:457
`warn!` at line 604 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:604
`warn!` at line 608 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:608
`trace!` 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: `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:631
`trace!` at line 640 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:640
`warn!` at line 646 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:646
`warn!` at line 657 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:657
`trace!` at line 667 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:667
`warn!` at line 673 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:673
`trace!` at line 713 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:713
`trace!` at line 729 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:729
`error!` at line 762 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:762
`trace!` at line 771 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `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:771
`trace!` at line 790 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:790
`error!` at line 795 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:795
`error!` at line 851 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:851
`trace!` at line 854 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:854
`trace!` at line 859 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:859
`warn!` at line 884 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:884
`trace!` at line 889 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:889
`error!` at line 923 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:923
`trace!` at line 1015 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:1015
`trace!` at line 1021 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:1021
`error!` at line 109 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:109
`warn!` at line 257 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:257
`warn!` at line 269 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:269
`warn!` at line 271 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:271
`error!` at line 553 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:553
`error!` at line 620 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:620
`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 1839 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:1839
`error!` at line 1855 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:1855
`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
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
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
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 70 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D10 Test Quality — ~2814 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 — D21 withholds its sibling role token rows: 1 candidate(s) found and not reported.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .rs source were not judged.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 83 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
ES1 Fold determinism — not applicable — the code was read and holds no event-replay fold, so there is nothing for this check to judge
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 — coverage data present for 120 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
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 scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
S1 Web-Security Posture — No web surface: 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.
X12 Unreachable branch — X12 reached only 0% of this repository's production lines — rust (62,892 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — Not applicable: 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.
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X3 Exception handling — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
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)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Boundary-crossing change coupling: output.rs ↔ mod.rs winit-wayland/src/output.rs:1— `winit-wayland/src/output.rs` (context winit-wayland) and `winit/src/platform_impl/linux/mod.rs` (context winit) sit in DIFFERENT parts of the tree yet change together 67% of the time (8 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `ee245c56` api: make VideoModeHandle into VideoMode (at that commit the files were still `src/platform_impl/linux/wayland/output.rs` and `src/platform_impl/linux/mod.rs`); `58142680` Various `Monitor/VideoModeHandle` methods now return an `Option` (at that commit the files were still `src/platform_impl/linux/wayland/output.rs` and `src/platform_impl/linux/mod.rs`); `0ffcfd8a` Remove `MonitorHandle::size/refresh_rate_millihertz()` (at that commit the files were still `src/platform_impl/linux/wayland/output.rs` and `src/platform_impl/linux/mod.rs`) — run `git show` on any of them.
Boundary-crossing change coupling: window.rs ↔ mod.rs winit-orbital/src/window.rs:1— `winit-orbital/src/window.rs` (context winit-orbital) and `winit/src/platform_impl/linux/mod.rs` (context winit) sit in DIFFERENT parts of the tree yet change together 66% of the time (19 of the 29 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 19 shared commits counted here, the most recent 3 are `3a60cbab` api: make EventLoopProxy wrap an opaque type (at that commit the files were still `src/platform_impl/orbital/window.rs` and `src/platform_impl/linux/mod.rs`); `b2896d74` chore: always pull raw-window-handle (at that commit the files were still `src/platform_impl/orbital/window.rs` and `src/platform_impl/linux/mod.rs`); `02a0a91a` Remove `raw-window-handle` v0.4 and v0.5 support (#3831) (at that commit the files were still `src/platform_impl/orbital/window.rs` and `src/platform_impl/linux/mod.rs`) — run `git show` on any of them.
Boundary-crossing change coupling: window.rs ↔ mod.rs winit-uikit/src/window.rs:1— `winit-uikit/src/window.rs` (context winit-uikit) and `winit/src/platform_impl/linux/mod.rs` (context winit) sit in DIFFERENT parts of the tree yet change together 52% of the time (44 of the 84 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 44 shared commits counted here, the most recent 3 are `ee245c56` api: make VideoModeHandle into VideoMode (at that commit the files were still `src/platform_impl/apple/uikit/window.rs` and `src/platform_impl/linux/mod.rs`); `b2896d74` chore: always pull raw-window-handle (at that commit the files were still `src/platform_impl/apple/uikit/window.rs` and `src/platform_impl/linux/mod.rs`); `6e1b9fa2` api: replace `WindowId` `From/Into` `u64` with `WindowId::{from,into}… (at that commit the files were still `src/platform_impl/apple/uikit/window.rs` and `src/platform_impl/linux/mod.rs`) — run `git show` on any of them.
Boundary-crossing change coupling: mod.rs ↔ mod.rs winit-wayland/src/window/mod.rs:1— `winit-wayland/src/window/mod.rs` (context winit-wayland) and `winit/src/platform_impl/linux/mod.rs` (context winit) sit in DIFFERENT parts of the tree yet change together 50% of the time (42 of the 84 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 42 shared commits counted here, the most recent 3 are `ee245c56` api: make VideoModeHandle into VideoMode (at that commit the files were still `src/platform_impl/linux/wayland/window/mod.rs` and `src/platform_impl/linux/mod.rs`); `59b1eb54` api: make OwnedDisplayHandle wrap an opaque type (at that commit the files were still `src/platform_impl/linux/wayland/window/mod.rs` and `src/platform_impl/linux/mod.rs`); `b2896d74` chore: always pull raw-window-handle (at that commit the files were still `src/platform_impl/linux/wayland/window/mod.rs` and `src/platform_impl/linux/mod.rs`) — run `git show` on any of them.
Boundary-crossing change coupling: output.rs ↔ randr.rs winit-wayland/src/output.rs:1— `winit-wayland/src/output.rs` (context winit-wayland) and `winit-x11/src/util/randr.rs` (context winit-x11) sit in DIFFERENT parts of the tree yet change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `31423554` winit-core: move monitor handle (at that commit the files were still `src/platform_impl/linux/wayland/output.rs` and `src/platform_impl/linux/x11/util/randr.rs`); `ee245c56` api: make VideoModeHandle into VideoMode (at that commit the files were still `src/platform_impl/linux/wayland/output.rs` and `src/platform_impl/linux/x11/util/randr.rs`); `58142680` Various `Monitor/VideoModeHandle` methods now return an `Option` (at that commit the files were still `src/platform_impl/linux/wayland/output.rs` and `src/platform_impl/linux/x11/util/randr.rs`) — run `git show` on any of them.
Boundary-crossing change coupling: mod.rs ↔ event_processor.rs winit-wayland/src/seat/touch/mod.rs:1— `winit-wayland/src/seat/touch/mod.rs` (context winit-wayland) and `winit-x11/src/event_processor.rs` (context winit-x11) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `6a8a3344` macOS: add `WindowEvent::PointerButton::is_macos_activation_click`; `edfb4b03` chore: remove platform FingerId (at that commit the files were still `src/platform_impl/linux/wayland/seat/touch/mod.rs` and `src/platform_impl/linux/x11/event_processor.rs`); `c8c1eca3` api: move primary from FingerId to Pointer events (at that commit the files were still `src/platform_impl/linux/wayland/seat/touch/mod.rs` and `src/platform_impl/linux/x11/event_processor.rs`) — run `git show` on any of them.
Boundary-crossing change coupling: mod.rs ↔ event_loop.rs winit-wayland/src/seat/touch/mod.rs:1— `winit-wayland/src/seat/touch/mod.rs` (context winit-wayland) and `winit-win32/src/event_loop.rs` (context winit-win32) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `6a8a3344` macOS: add `WindowEvent::PointerButton::is_macos_activation_click`; `edfb4b03` chore: remove platform FingerId (at that commit the files were still `src/platform_impl/linux/wayland/seat/touch/mod.rs` and `src/platform_impl/windows/event_loop.rs`); `c8c1eca3` api: move primary from FingerId to Pointer events (at that commit the files were still `src/platform_impl/linux/wayland/seat/touch/mod.rs` and `src/platform_impl/windows/event_loop.rs`) — run `git show` on any of them.
Boundary-crossing change coupling: event_loop.rs ↔ mod.rs winit-android/src/event_loop.rs:1— `winit-android/src/event_loop.rs` (context winit-android) and `winit-wayland/src/seat/touch/mod.rs` (context winit-wayland) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `6a8a3344` macOS: add `WindowEvent::PointerButton::is_macos_activation_click`; `edfb4b03` chore: remove platform FingerId (at that commit the files were still `src/platform_impl/android/mod.rs` and `src/platform_impl/linux/wayland/seat/touch/mod.rs`); `c8c1eca3` api: move primary from FingerId to Pointer events (at that commit the files were still `src/platform_impl/android/mod.rs` and `src/platform_impl/linux/wayland/seat/touch/mod.rs`) — run `git show` on any of them.
Boundary-crossing change coupling: view.rs ↔ mod.rs winit-uikit/src/view.rs:1— `winit-uikit/src/view.rs` (context winit-uikit) and `winit-wayland/src/seat/touch/mod.rs` (context winit-wayland) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `6a8a3344` macOS: add `WindowEvent::PointerButton::is_macos_activation_click`; `edfb4b03` chore: remove platform FingerId (at that commit the files were still `src/platform_impl/apple/uikit/view.rs` and `src/platform_impl/linux/wayland/seat/touch/mod.rs`); `c8c1eca3` api: move primary from FingerId to Pointer events (at that commit the files were still `src/platform_impl/apple/uikit/view.rs` and `src/platform_impl/linux/wayland/seat/touch/mod.rs`) — run `git show` on any of them.
TodoComment winit-x11/src/data_transfer.rs:32— /// TODO: this is copied from wayland. Is this the right approach for X11 as well? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment winit-x11/src/data_transfer.rs:929— // TODO: skip the X11 protocol when we own the clipboard. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment winit-x11/src/data_transfer.rs:971— // TODO: The result is stored into a property with the same name as the selection. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment winit-x11/src/event_loop.rs:763— /// focused window (TODO: better strategy?). — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment winit-x11/src/event_processor.rs:565— // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment winit-orbital/src/event_loop.rs:170— // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment winit-x11/src/event_processor.rs:771— // TODO: The result is stored into a property named XdndSelection. Consider using a — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment winit-x11/src/window.rs:694— // Enable drag and drop (TODO: extend API to make this toggleable) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment winit-x11/src/window.rs:2274— // TODO timer — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment winit-x11/src/xdisplay.rs:27— // TODO(notgull): I'd like to remove this, but apparently Xlib and Xinput2 are tied together — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment winit-x11/src/xdisplay.rs:201— // TODO: The XSETTINGS window here can change. In the future, listen for DestroyNotify on — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment winit-x11/src/xdisplay.rs:376— // TODO: Using the current time is not the suggested convention but it doesn't seem — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment winit-x11/src/xdisplay.rs:438— // TODO: add better message. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment winit-x11/src/util/window_property.rs:239— // TODO(notgull): It may be worth it to use `unsafe` to copy directly from — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment winit-win32/src/data_transfer.rs:60— // TODO: Exposing the full native API to client applications is too error-prone so long as — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment winit-win32/src/data_transfer.rs:770— // TODO: On macOS, option will disable copy (so if copy has higher precedence than move you can — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment winit-win32/src/event_loop.rs:1872— // TODO: figure out how to handle page scrolls — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment winit-win32/src/keyboard_layout.rs:319— // TODO: validate that we can skip on unidentified keys (probably never occurs?) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment winit-win32/src/keyboard_layout.rs:369— // TODO: validate that we can skip on unidentified keys (probably never occurs?) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment winit-win32/src/window.rs:196— // TODO: Write a test once integration framework is ready to ensure that it holds. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment winit-web/src/lock.rs:17— // TODO: Remove when Chrome can better advertise that they don't support unaccelerated — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment winit-web/src/web_sys/event.rs:177— // TODO: Remove this when Firefox supports correct movement values in coalesced events and browsers — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment winit-web/src/web_sys/event.rs:340— // TODO: Remove when Safari supports `getCoalescedEvents`. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment winit-web/src/web_sys/media_query_handle.rs:24— // TODO: Replace obsolete `addListener()` with `addEventListener()` and use — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment winit-web/src/web_sys/mod.rs:223— // TODO: verify when Firefox actually implements it. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FileTooLong: src/event_loop.rs winit-win32/src/event_loop.rs— FileTooLong — 1699 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 1199 over it, 3.40× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/window.rs winit-x11/src/window.rs— FileTooLong — 1532 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 82% of them inside a single declaration: UnownedWindow (2 blocks, 433-2313). The bar is 500 significant lines; this is 1032 over it, 3.06× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/window_delegate.rs winit-appkit/src/window_delegate.rs— FileTooLong — 1467 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 81% of them inside a single declaration: WindowDelegate (7 blocks, 143-2505). The bar is 500 significant lines; this is 967 over it, 2.93× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/event_processor.rs winit-x11/src/event_processor.rs— FileTooLong — 1257 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 96% of them inside a single declaration: EventProcessor (2 blocks, 56-2049). The bar is 500 significant lines; this is 757 over it, 2.51× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/data_transfer.rs winit-win32/src/data_transfer.rs— FileTooLong — 1148 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 648 over it, 2.30× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/window.rs winit-win32/src/window.rs— FileTooLong — 1129 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 61% of them inside a single declaration: Window (6 blocks, 95-1231). The bar is 500 significant lines; this is 629 over it, 2.26× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/data_transfer.rs winit-wayland/src/data_transfer.rs— FileTooLong — 904 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 404 over it, 1.81× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/keyboard.rs winit-win32/src/keyboard.rs— FileTooLong — 881 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 381 over it, 1.76× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/event_loop.rs winit-x11/src/event_loop.rs— FileTooLong — 810 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 310 over it, 1.62× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/view.rs winit-appkit/src/view.rs— FileTooLong — 773 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 273 over it, 1.55× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/keyboard_layout.rs winit-win32/src/keyboard_layout.rs— FileTooLong — 743 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 243 over it, 1.49× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: xkb/keymap.rs winit-common/src/xkb/keymap.rs— FileTooLong — 741 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 241 over it, 1.48× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/data_transfer.rs winit-x11/src/data_transfer.rs— FileTooLong — 656 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 61% of them inside a single declaration: DataTransferState (2 blocks, 298-1026). The bar is 500 significant lines; this is 156 over it, 1.31× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/event_loop.rs winit-android/src/event_loop.rs— FileTooLong — 653 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 153 over it, 1.31× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/event_loop.rs winit-orbital/src/event_loop.rs— FileTooLong — 591 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 91 over it, 1.18× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/window.rs winit-core/src/window.rs— FileTooLong — 588 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 88 over it, 1.18× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/monitor.rs winit-web/src/monitor.rs— FileTooLong — 576 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 76 over it, 1.15× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: event_loop/mod.rs winit-wayland/src/event_loop/mod.rs— FileTooLong — 539 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 39 over it, 1.08× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/window.rs winit-uikit/src/window.rs— FileTooLong — 536 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 36 over it, 1.07× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/view.rs winit-uikit/src/view.rs— FileTooLong — 518 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 93% of them inside a single declaration: WinitView (4 blocks, 45-749). The bar is 500 significant lines; this is 18 over it, 1.04× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/event.rs winit-core/src/event.rs— FileTooLong — 514 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 14 over it, 1.03× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: window/state.rs winit-wayland/src/window/state.rs— FileTooLong — 514 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 83% of them inside a single declaration: WindowState (3 blocks, 103-889). The bar is 500 significant lines; this is 14 over it, 1.03× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: event_loop/runner.rs winit-web/src/event_loop/runner.rs— FileTooLong — 513 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 75% of them inside a single declaration: Shared (2 blocks, 34-855). The bar is 500 significant lines; this is 13 over it, 1.03× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/keycodes.rs winit-android/src/keycodes.rs— FileTooLong — 509 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 9 over it, 1.02× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
MethodTooLong: UnownedWindow.new winit-x11/src/window.rs:459— MethodTooLong — new runs 307 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 207 over it, 3.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ActiveEventLoop.register winit-web/src/event_loop/window_target.rs:71— MethodTooLong — register runs 246 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 146 over it, 2.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: EventLoop.new winit-x11/src/event_loop.rs:219— MethodTooLong — new runs 167 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 67 over it, 1.67× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: KeyEventBuilder.process_message winit-win32/src/keyboard.rs:76— MethodTooLong — process_message runs 160 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 60 over it, 1.60× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WinitState.event winit-wayland/src/seat/keyboard/mod.rs:23— MethodTooLong — event runs 156 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 56 over it, 1.56× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WinitState.pointer_frame winit-wayland/src/seat/pointer/mod.rs:37— MethodTooLong — pointer_frame runs 135 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: EventLoop.handle_input_event winit-android/src/event_loop.rs:317— MethodTooLong — handle_input_event runs 134 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Popup.new winit-wayland/src/popup.rs:33— MethodTooLong — new runs 134 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: EventProcessor.client_message winit-x11/src/event_processor.rs:376— MethodTooLong — client_message runs 133 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WinitView.handle_touches winit-uikit/src/view.rs:480— MethodTooLong — handle_touches runs 129 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 29 over it, 1.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: EventLoop.single_iteration winit-wayland/src/event_loop/mod.rs:319— MethodTooLong — single_iteration runs 125 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Shared.set_listener winit-web/src/event_loop/runner.rs:280— MethodTooLong — set_listener runs 118 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TabletToolData.event winit-wayland/src/types/wp_tablet_input_v2.rs:92— MethodTooLong — event runs 115 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WindowDelegate.set_fullscreen winit-appkit/src/window_delegate.rs:1813— MethodTooLong — set_fullscreen runs 110 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: EventLoop.process_event winit-orbital/src/event_loop.rs:358— MethodTooLong — process_event runs 110 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WindowDelegate.new winit-appkit/src/window_delegate.rs:910— MethodTooLong — new runs 106 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: EventProcessor.process_xevent winit-x11/src/event_processor.rs:150— MethodTooLong — process_xevent runs 104 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: winit_win32::event_loop::public_window_callback_inner winit-win32/src/event_loop.rs:1236— FunctionTooLong — winit_win32::event_loop::public_window_callback_inner runs 821 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 721 over it, 8.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: winit_android::keycodes::to_logical winit-android/src/keycodes.rs:238— FunctionTooLong — winit_android::keycodes::to_logical runs 297 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 197 over it, 2.97× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: winit_win32::keyboard_layout::vkey_to_non_char_key winit-win32/src/keyboard_layout.rs:734— FunctionTooLong — winit_win32::keyboard_layout::vkey_to_non_char_key runs 209 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 109 over it, 2.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: winit_common::xkb::keymap::keysym_to_key winit-common/src/xkb/keymap.rs:504— FunctionTooLong — winit_common::xkb::keymap::keysym_to_key runs 204 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 104 over it, 2.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: winit_win32::keyboard_layout::keycode_to_vkey winit-win32/src/keyboard_layout.rs:518— FunctionTooLong — winit_win32::keyboard_layout::keycode_to_vkey runs 203 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 103 over it, 2.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: winit_common::xkb::keymap::physicalkey_to_scancode winit-common/src/xkb/keymap.rs:302— FunctionTooLong — winit_common::xkb::keymap::physicalkey_to_scancode runs 194 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 94 over it, 1.94× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: winit_common::xkb::keymap::scancode_to_physicalkey winit-common/src/xkb/keymap.rs:34— FunctionTooLong — winit_common::xkb::keymap::scancode_to_physicalkey runs 189 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: winit_win32::keyboard::physicalkey_to_scancode winit-win32/src/keyboard.rs:897— FunctionTooLong — winit_win32::keyboard::physicalkey_to_scancode runs 175 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 75 over it, 1.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: winit_win32::keyboard::scancode_to_physicalkey winit-win32/src/keyboard.rs:1093— FunctionTooLong — winit_win32::keyboard::scancode_to_physicalkey runs 162 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 62 over it, 1.62× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: winit_android::keycodes::to_physical_key winit-android/src/keycodes.rs:7— FunctionTooLong — winit_android::keycodes::to_physical_key runs 135 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: winit_appkit::window_delegate::new_window winit-appkit/src/window_delegate.rs:659— FunctionTooLong — winit_appkit::window_delegate::new_window runs 133 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: winit_appkit::event::physicalkey_to_scancode winit-appkit/src/event.rs:348— FunctionTooLong — winit_appkit::event::physicalkey_to_scancode runs 127 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: winit_appkit::event::scancode_to_physicalkey winit-appkit/src/event.rs:480— FunctionTooLong — winit_appkit::event::scancode_to_physicalkey runs 124 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: winit_appkit::cursor::cursor_from_icon winit-appkit/src/cursor.rs:234— FunctionTooLong — winit_appkit::cursor::cursor_from_icon runs 122 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: winit_orbital::event_loop::convert_scancode winit-orbital/src/event_loop.rs:39— FunctionTooLong — winit_orbital::event_loop::convert_scancode runs 114 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FixmeComment winit-x11/src/window.rs:1127— // FIXME: this is actually not correct if we're setting the — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment winit-win32/src/event_loop.rs:456— // FIXME(madsmtm): Implement `ActiveEventLoop` for `Rc<EventLoopRunner>` directly. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment winit-win32/src/event_loop.rs:1176— // FIXME: detect WM_DWMCOMPOSITIONCHANGED and call DwmEnableBlurBehindWindow if necessary — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment winit-win32/src/keyboard.rs:537— // FIXME(madsmtm): Is the `chars != " "` check desired here? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment winit-win32/src/lib.rs:5— // FIXME(madsmtm): Allow compiling on all platforms. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment winit-win32/src/event_loop/runner.rs:122— // FIXME(madsmtm): Coalesce these into a flag (or similar) instead of handling them as events. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment winit-uikit/src/monitor.rs:239— // FIXME: earlier OSs could calculate the refresh rate using — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment winit-core/src/event_loop/pump_events.rs:5— // FIXME(madsmtm): Fix these. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment winit-common/src/core_foundation/event_loop_proxy.rs:23— // FIXME(madsmtm): Mark `CFRunLoopSource` + `CFRunLoop` as `Send` + `Sync`. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment winit-common/src/core_foundation/event_loop_proxy.rs:100— // FIXME(madsmtm): Use this on macOS too. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment winit-appkit/src/app.rs:155— // FIXME(madsmtm): Ensure this always runs (maybe use cargo-nextest or `--test-threads=1`?) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment winit-appkit/src/app.rs:164— // FIXME(madsmtm): Can't test this yet, need some way to mock AppState. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment winit-android/src/event_loop.rs:819— // FIXME this ignores the rest of the requested window attributes — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment winit/examples/util/fill.rs:14— // FIXME(madsmtm): This should be done by softbuffer internally in the future: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment winit-x11/src/event_loop.rs:110— // XXX only update the error, if it wasn't handled by any of the hooks. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment winit-x11/src/ime/context.rs:192— // XXX: this struct doesn't destroy its XIC resource when dropped. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment winit-wayland/src/popup.rs:410— // XXX clients don't know whether they are minimized or not. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment winit-wayland/src/window/mod.rs:497— // XXX clients don't know whether they are minimized or not. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment winit-wayland/src/window/mod.rs:88— // XXX Wait for the initial configure to arrive. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment winit-wayland/src/window/mod.rs:327— // XXX Do initial commit. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment winit-wayland/src/seat/text_input/mod.rs:95— // XXX this check is essential, because `leave` could have a — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment winit-wayland/src/event_loop/mod.rs:79— // XXX drop after everything else, just to be safe. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment winit-appkit/src/window_delegate.rs:1522— // XXX the resize increments are only used during live resizes. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment winit-android/src/event_loop.rs:238— // XXX: how to forward this state to applications? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment winit-android/src/event_loop.rs:256— // XXX: how to forward this state to applications? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment winit-android/src/event_loop.rs:239— // XXX: also how do we expose state restoration to apps? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment winit-android/src/event_loop.rs:251— // XXX: maybe exit mainloop to drop things before being — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TooManyMethods: UnownedWindow winit-x11/src/window.rs:433— TooManyMethods — 97 methods. The bar is 30 methods; this is 67 over it, 3.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WindowDelegate winit-appkit/src/window_delegate.rs:138— TooManyMethods — 78 methods. The bar is 30 methods; this is 48 over it, 2.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WindowState winit-wayland/src/window/state.rs:103— TooManyMethods — 78 methods, declared across 5 files: window/state.rs (47), state/frame.rs (12), state/cursor.rs (11), state/ime.rs (5), +1 more file(s). The bar is 30 methods; this is 48 over it, 2.60× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Inner winit-uikit/src/window.rs:114— TooManyMethods — 70 methods. The bar is 30 methods; this is 40 over it, 2.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: XConnection winit-x11/src/xdisplay.rs:24— TooManyMethods — 66 methods, declared across 14 files: src/xdisplay.rs (20), util/geometry.rs (8), util/cursor.rs (7), src/monitor.rs (6), +10 more file(s). The bar is 30 methods; this is 36 over it, 2.20× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WindowCommon winit-wayland/src/window/common.rs:23— TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: EventProcessor winit-x11/src/event_processor.rs:56— TooManyMethods — 44 methods. The bar is 30 methods; this is 14 over it, 1.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Shared winit-web/src/event_loop/runner.rs:32— TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WinitView winit-appkit/src/view.rs:157— TooManyMethods — 36 methods, declared across 2 files: src/view.rs (27), src/view.rs (9). The bar is 30 methods; this is 6 over it, 1.20× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Canvas winit-web/src/web_sys/canvas.rs:35— TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AppState winit-appkit/src/app_state.rs:27— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (10 lines × 2) winit-android/src/event_loop.rs:365— winit-android/src/event_loop.rs:365-374 | winit-android/src/event_loop.rs:441-450 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-android/src/event_loop.rs:365` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `winit-android/src/event_loop.rs:440` calls `Some` and `winit-android/src/event_loop.rs:364` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) winit-common/src/xkb/keymap.rs:107— winit-common/src/xkb/keymap.rs:107-116 | winit-win32/src/keyboard.rs:1200-1209 — before extracting anything, compare `winit-common/src/xkb/keymap.rs` and `winit-win32/src/keyboard.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) winit-common/src/xkb/keymap.rs:373— winit-common/src/xkb/keymap.rs:373-382 | winit-win32/src/keyboard.rs:1027-1036 — before extracting anything, compare `winit-common/src/xkb/keymap.rs` and `winit-win32/src/keyboard.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) winit-web/src/event_loop/runner.rs:372— winit-web/src/event_loop/runner.rs:372-381 | winit-web/src/event_loop/runner.rs:391-400 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-web/src/event_loop/runner.rs:372` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) winit-win32/src/window.rs:712— winit-win32/src/window.rs:712-721 | winit-win32/src/window.rs:734-743 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-win32/src/window.rs:712` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) winit-x11/src/event_processor.rs:1238— winit-x11/src/event_processor.rs:1238-1247 | winit-x11/src/event_processor.rs:1329-1338 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-x11/src/event_processor.rs:1238` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) winit-appkit/src/window.rs:340— winit-appkit/src/window.rs:340-349 | winit-uikit/src/window.rs:822-831 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) winit-wayland/src/data_transfer.rs:576— winit-wayland/src/data_transfer.rs:576-585 | winit-x11/src/data_transfer.rs:37-46 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) winit-web/src/event_loop/runner.rs:408— winit-web/src/event_loop/runner.rs:408-417 | winit-web/src/event_loop/runner.rs:426-435 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-web/src/event_loop/runner.rs:408` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) winit-android/src/keycodes.rs:257— winit-android/src/keycodes.rs:257-266 | winit-android/src/keycodes.rs:384-393 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) winit-android/src/event_loop.rs:580— winit-android/src/event_loop.rs:580-591 | winit-x11/src/event_loop.rs:536-547 — before extracting anything, compare `winit-android/src/event_loop.rs` and `winit-x11/src/event_loop.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `winit-android/src/event_loop.rs:580` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) winit-android/src/keycodes.rs:371— winit-android/src/keycodes.rs:371-382 | winit-win32/src/keyboard_layout.rs:826-837 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) winit-common/src/xkb/keymap.rs:230— winit-common/src/xkb/keymap.rs:230-241 | winit-win32/src/keyboard.rs:1212-1223 — before extracting anything, compare `winit-common/src/xkb/keymap.rs` and `winit-win32/src/keyboard.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) winit-common/src/xkb/keymap.rs:468— winit-common/src/xkb/keymap.rs:468-479 | winit-win32/src/keyboard.rs:1039-1050 — before extracting anything, compare `winit-common/src/xkb/keymap.rs` and `winit-win32/src/keyboard.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) winit-wayland/src/event_loop/mod.rs:285— winit-wayland/src/event_loop/mod.rs:285-296 | winit-x11/src/event_loop.rs:554-565 — before extracting anything, compare `winit-wayland/src/event_loop/mod.rs` and `winit-x11/src/event_loop.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `winit-wayland/src/event_loop/mod.rs:285` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) winit-web/src/event_loop/window_target.rs:312— winit-web/src/event_loop/window_target.rs:312-323 | winit-web/src/event_loop/window_target.rs:341-352 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-web/src/event_loop/window_target.rs:312` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) winit-win32/src/event_loop.rs:2006— winit-win32/src/event_loop.rs:2006-2017 | winit-win32/src/event_loop.rs:2036-2047 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-win32/src/event_loop.rs:2006` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) winit-win32/src/window.rs:902— winit-win32/src/window.rs:902-913 | winit-win32/src/window.rs:919-930 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-win32/src/window.rs:902` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Hotspot: winit-win32/src/event_loop.rs winit-win32/src/event_loop.rs:1236— winit-win32/src/event_loop.rs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 155 in winit_win32::event_loop::public_window_callback_inner at line 1236. 1 of those changes was a fix/bug commit, and the other 13 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 10:00:08 +01:00' --until='2026-11-13 10:00:08 +01:00' --full-history --no-merges -- winit-win32/src/event_loop.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: winit-wayland/src/event_loop/mod.rs winit-wayland/src/event_loop/mod.rs:319— winit-wayland/src/event_loop/mod.rs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in EventLoop::single_iteration at line 319. 1 of those changes was a fix/bug commit, and the other 13 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 10:00:08 +01:00' --until='2026-11-13 10:00:08 +01:00' --full-history --no-merges -- winit-wayland/src/event_loop/mod.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: winit-appkit/src/window_delegate.rs winit-appkit/src/window_delegate.rs:659— winit-appkit/src/window_delegate.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in winit_appkit::window_delegate::new_window at line 659. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 10:00:08 +01:00' --until='2026-11-13 10:00:08 +01:00' --full-history --no-merges -- winit-appkit/src/window_delegate.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: winit-x11/src/window.rs winit-x11/src/window.rs:459— winit-x11/src/window.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in UnownedWindow::new at line 459. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 10:00:08 +01:00' --until='2026-11-13 10:00:08 +01:00' --full-history --no-merges -- winit-x11/src/window.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: winit-x11/src/event_processor.rs winit-x11/src/event_processor.rs:376— winit-x11/src/event_processor.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in EventProcessor::client_message at line 376. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 10:00:08 +01:00' --until='2026-11-13 10:00:08 +01:00' --full-history --no-merges -- winit-x11/src/event_processor.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: winit-win32/src/window_state.rs winit-win32/src/window_state.rs:303— winit-win32/src/window_state.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in WindowFlags::to_window_styles at line 303. 1 of those changes was a fix/bug commit, and the other 1 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 10:00:08 +01:00' --until='2026-11-13 10:00:08 +01:00' --full-history --no-merges -- winit-win32/src/window_state.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: winit-wayland/src/seat/text_input/mod.rs winit-wayland/src/seat/text_input/mod.rs:56— winit-wayland/src/seat/text_input/mod.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in TextInputState::event at line 56. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 10:00:08 +01:00' --until='2026-11-13 10:00:08 +01:00' --full-history --no-merges -- winit-wayland/src/seat/text_input/mod.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Duplicated block (9 lines × 2) winit-appkit/src/window_delegate.rs:1479— winit-appkit/src/window_delegate.rs:1479-1487 | winit-appkit/src/window_delegate.rs:1501-1509 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-appkit/src/window_delegate.rs:1479` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) winit-common/src/xkb/keymap.rs:316— winit-common/src/xkb/keymap.rs:316-324 | winit-win32/src/keyboard.rs:923-931 — before extracting anything, compare `winit-common/src/xkb/keymap.rs` and `winit-win32/src/keyboard.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) winit-wayland/src/data_transfer.rs:1205— winit-wayland/src/data_transfer.rs:1205-1213 | winit-wayland/src/data_transfer.rs:1250-1258 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-wayland/src/data_transfer.rs:1205` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) winit-wayland/src/seat/pointer/pointer_gesture.rs:98— winit-wayland/src/seat/pointer/pointer_gesture.rs:98-106 | winit-wayland/src/seat/pointer/pointer_gesture.rs:173-181 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) winit-web/src/web_sys/pointer.rs:44— winit-web/src/web_sys/pointer.rs:44-52 | winit-web/src/web_sys/pointer.rs:62-70 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-web/src/web_sys/pointer.rs:44` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) winit-win32/src/event_loop.rs:1945— winit-win32/src/event_loop.rs:1945-1953 | winit-win32/src/event_loop.rs:1975-1983 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-win32/src/event_loop.rs:1945` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) winit-wayland/src/window/state.rs:357— winit-wayland/src/window/state.rs:357-365 | winit-wayland/src/window/state.rs:382-390 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-wayland/src/window/state.rs:357` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
HackComment winit-win32/src/event_loop.rs:1303— // HACK(msiglreith): To add the drop shadow we slightly tweak the non-client area. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment winit-win32/src/keyboard_layout.rs:393— // HACK: `ToUnicodeEx` seems to fail getting the string for the numpad — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment winit-wayland/src/data_transfer.rs:1065— // HACK: How do we get the correct seat for pointers here? — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment winit-wayland/src/window/state.rs:309— // HACK: Currently to get the data device to initiate a drag-and-drop, we iterate through all — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment winit-wayland/src/seat/keyboard/mod.rs:89— // HACK: this is just for GNOME not fixing their ordering issue of modifiers. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment winit-wayland/src/seat/keyboard/mod.rs:245— // HACK: part of the workaround from `WlKeyboardEvent::Enter`. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
EventLoop::single_iteration (cognitive 47) winit-wayland/src/event_loop/mod.rs:319— EventLoop::single_iteration has cognitive complexity 47 (threshold 15). Drivers by points: if/else 15 (31 pts), loops 7 (9 pts), match/switch 3 (6 pts), boolean chains 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventLoop::handle_input_event (cognitive 39) winit-android/src/event_loop.rs:317— EventLoop::handle_input_event has cognitive complexity 39 (threshold 15). Drivers by points: match/switch 10 (19 pts), if/else 5 (16 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 21). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
EventLoop::single_iteration (cognitive 23) winit-android/src/event_loop.rs:173— EventLoop::single_iteration has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (18 pts), match/switch 2 (3 pts), loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventLoop::process_event (cognitive 17) winit-orbital/src/event_loop.rs:358— EventLoop::process_event has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventLoop::poll_events_with_timeout (cognitive 16) winit-wayland/src/event_loop/mod.rs:247— EventLoop::poll_events_with_timeout has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), match/switch 2 (4 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventProcessor::process_xevent (cognitive 38) winit-x11/src/event_processor.rs:150— EventProcessor::process_xevent has cognitive complexity 38 (threshold 15). Drivers by points: if/else 13 (25 pts), match/switch 5 (11 pts), boolean chains 2 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventProcessor::client_message (cognitive 28) winit-x11/src/event_processor.rs:376— EventProcessor::client_message has cognitive complexity 28 (threshold 15). Drivers by points: if/else 19 (26 pts), match/switch 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventProcessor::configure_notify (cognitive 25) winit-x11/src/event_processor.rs:844— EventProcessor::configure_notify has cognitive complexity 25 (threshold 15). Drivers by points: if/else 16 (23 pts), boolean chains 1, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventProcessor::xinput_key_input (cognitive 23) winit-x11/src/event_processor.rs:1099— EventProcessor::xinput_key_input has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 1, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventProcessor::xkb_event (cognitive 17) winit-x11/src/event_processor.rs:1751— EventProcessor::xkb_event has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), match/switch 4 (6 pts), boolean chains 2 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ClassTooLong: UnownedWindow winit-x11/src/window.rs:433— ClassTooLong — 1255 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 97 methods, 2 blocks, lines 433-2313. The bar is 400 significant lines; this is 855 over it, 3.14× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: EventProcessor winit-x11/src/event_processor.rs:56— ClassTooLong — 1201 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 44 methods, 2 blocks, lines 56-2049. The bar is 400 significant lines; this is 801 over it, 3.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: WindowDelegate winit-appkit/src/window_delegate.rs:138— ClassTooLong — 1189 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 78 methods, 7 blocks, lines 143-2505. The bar is 400 significant lines; this is 789 over it, 2.97× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Window winit-win32/src/window.rs:95— ClassTooLong — 686 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 23 methods, 6 blocks, lines 95-1231. The bar is 400 significant lines; this is 286 over it, 1.72× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: WindowState winit-wayland/src/window/state.rs:103— ClassTooLong — 428 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 78 methods, 3 blocks, lines 103-889. The bar is 400 significant lines; this is 28 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (8 lines × 2) winit-android/src/event_loop.rs:998— winit-android/src/event_loop.rs:998-1005 | winit-uikit/src/window.rs:386-393 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `winit-android/src/event_loop.rs:998` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) winit-appkit/src/event.rs:432— winit-appkit/src/event.rs:432-439 | winit-win32/src/keyboard.rs:1008-1015 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) winit-appkit/src/window_delegate.rs:1302— winit-appkit/src/window_delegate.rs:1302-1309 | winit-appkit/src/window_delegate.rs:1321-1328 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) winit-uikit/src/app_state.rs:361— winit-uikit/src/app_state.rs:361-368 | winit-uikit/src/app_state.rs:420-427 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-uikit/src/app_state.rs:361` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) winit-win32/src/window.rs:561— winit-win32/src/window.rs:561-568 | winit-win32/src/window.rs:600-607 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
EventLoop::handle_input_event (cyclomatic 28) winit-android/src/event_loop.rs:317— EventLoop::handle_input_event has cyclomatic complexity 28 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
EventLoop::single_iteration (cyclomatic 27) winit-android/src/event_loop.rs:173— EventLoop::single_iteration has cyclomatic complexity 27 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
EventLoop::single_iteration (cyclomatic 27) winit-wayland/src/event_loop/mod.rs:319— EventLoop::single_iteration has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EventLoop::process_event (cyclomatic 20) winit-orbital/src/event_loop.rs:358— EventLoop::process_event has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: winit_orbital::event_loop::convert_scancode (cyclomatic 110) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×4
Edited copy of a member (8 corresponding lines) dpi/src/lib.rs:694— dpi/src/lib.rs:694-701 | dpi/src/lib.rs:745-752 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) winit-wayland/src/event_loop/mod.rs:855— winit-wayland/src/event_loop/mod.rs:855-864 | winit-wayland/src/window/common.rs:324-331 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) winit-win32/src/util.rs:343— winit-win32/src/util.rs:343-350 | winit-win32/src/util.rs:357-367 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) winit-wayland/src/window/handles.rs:67— winit-wayland/src/window/handles.rs:67-76 | winit-x11/src/window.rs:304-311 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×4
Edited copy of a member (9 corresponding lines) winit-common/src/xkb/mod.rs:129— winit-common/src/xkb/mod.rs:129-137 | winit-common/src/xkb/mod.rs:140-148 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) winit-x11/src/xsettings.rs:205— winit-x11/src/xsettings.rs:205-213 | winit-x11/src/xsettings.rs:216-224 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) winit-web/src/web_sys/canvas.rs:258— winit-web/src/web_sys/canvas.rs:258-266 | winit-web/src/web_sys/canvas.rs:457-465 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) winit-wayland/src/seat/pointer/mod.rs:369— winit-wayland/src/seat/pointer/mod.rs:369-377 | winit-wayland/src/window/state.rs:877-888 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×4
Edited copy of a member (7 corresponding lines) winit-common/src/xkb/mod.rs:151— winit-common/src/xkb/mod.rs:151-158 | winit-common/src/xkb/mod.rs:167-173 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) winit-wayland/src/state.rs:511— winit-wayland/src/state.rs:511-519 | winit-wayland/src/state.rs:521-527 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) winit-common/src/xkb/keymap.rs:1006— winit-common/src/xkb/keymap.rs:1006-1017 | winit-common/src/xkb/state.rs:32-38 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) winit-appkit/src/window.rs:65— winit-appkit/src/window.rs:65-71 | winit-uikit/src/window.rs:567-573 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (7 lines × 2) winit-uikit/src/window.rs:89— winit-uikit/src/window.rs:89-95 | winit-uikit/src/window.rs:314-320 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) winit-win32/src/event_loop.rs:1943— winit-win32/src/event_loop.rs:1943-1949 | winit-win32/src/event_loop.rs:2004-2010 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) winit-win32/src/event_loop.rs:1973— winit-win32/src/event_loop.rs:1973-1979 | winit-win32/src/event_loop.rs:2034-2040 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) winit-web/src/web_sys/mod.rs:89— winit-web/src/web_sys/mod.rs:89-95 | winit-web/src/web_sys/mod.rs:110-116 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) winit-web/src/web_sys/pointer.rs:81— winit-web/src/web_sys/pointer.rs:81-85 | winit-web/src/web_sys/pointer.rs:127-131 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-web/src/web_sys/pointer.rs:81` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) winit-web/src/web_sys/schedule.rs:125— winit-web/src/web_sys/schedule.rs:125-129 | winit-web/src/web_sys/schedule.rs:182-190 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) winit-appkit/src/window.rs:334— winit-appkit/src/window.rs:334-338 | winit-uikit/src/window.rs:816-820 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) winit-appkit/src/window.rs:351— winit-appkit/src/window.rs:351-355 | winit-uikit/src/window.rs:833-837 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
winit_win32::keyboard::physicalkey_to_scancode (cyclomatic 160) winit-win32/src/keyboard.rs:897— winit_win32::keyboard::physicalkey_to_scancode has cyclomatic complexity 160 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
winit_win32::event_loop::public_window_callback_inner (cyclomatic 155) winit-win32/src/event_loop.rs:1236— winit_win32::event_loop::public_window_callback_inner has cyclomatic complexity 155 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
winit_win32::event_loop::handle_raw_input (cyclomatic 16) winit-win32/src/event_loop.rs:2657— winit_win32::event_loop::handle_raw_input has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
winit_win32::event_loop::public_window_callback_inner (cognitive 255) winit-win32/src/event_loop.rs:1236— winit_win32::event_loop::public_window_callback_inner has cognitive complexity 255 (threshold 15). Drivers by points: if/else 83 (198 pts), match/switch 15 (38 pts), boolean chains 12, loops 3 (7 pts) (nesting depth added 142). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: winit-win32/src/event_loop.rs holds 2 of the 40 functions over the threshold — including the worst — and 253 of the 736 points over it (34%), 4.5× the next-largest file (winit-x11/src/event_processor.rs at 56). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
winit_win32::event_loop::handle_raw_input (cognitive 28) winit-win32/src/event_loop.rs:2657— winit_win32::event_loop::handle_raw_input has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: winit-win32/src/event_loop.rs holds 2 of the 40 functions over the threshold — including the worst — and 253 of the 736 points over it (34%), 4.5× the next-largest file (winit-x11/src/event_processor.rs at 56). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
winit_win32::dpi::hwnd_dpi (cognitive 16) winit-win32/src/dpi.rs:75— winit_win32::dpi::hwnd_dpi has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), match/switch 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
winit_appkit::cursor::cursor_from_icon (cognitive 49) winit-appkit/src/cursor.rs:234— winit_appkit::cursor::cursor_from_icon has cognitive complexity 49 (threshold 15). Drivers by points: if/else 32 (48 pts), match/switch 1 (nesting depth added 16). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
winit_appkit::window_delegate::new_window (cognitive 37) winit-appkit/src/window_delegate.rs:659— winit_appkit::window_delegate::new_window has cognitive complexity 37 (threshold 15). Drivers by points: if/else 22 (24 pts), match/switch 4 (6 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
winit_appkit::event::create_key_event (cognitive 16) winit-appkit/src/event.rs:82— winit_appkit::event::create_key_event has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (10 pts), match/switch 2 (5 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Change coupling: util.rs ↔ view.rs winit-appkit/src/util.rs:1— `winit-appkit/src/util.rs` and `winit-appkit/src/view.rs` change together 67% of the time (10 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `cb39ab29` macOS: Move util::EMPTY_RANGE to usage spot (#3685) (at that commit the files were still `src/platform_impl/macos/util.rs` and `src/platform_impl/macos/view.rs`); `29419d6c` Refactor macOS cursor code (#2463) (at that commit the files were still `src/platform_impl/macos/util/mod.rs` and `src/platform_impl/macos/view.rs`); `6474891f` Fix macOS 32bit (#2327) (at that commit the files were still `src/platform_impl/macos/util/mod.rs` and `src/platform_impl/macos/view.rs`) — run `git show` on any of them.
Change coupling: window_target.rs ↔ pointer.rs winit-web/src/event_loop/window_target.rs:1— `winit-web/src/event_loop/window_target.rs` and `winit-web/src/web_sys/pointer.rs` change together 61% of the time (19 of the 31 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 19 shared commits counted here, the most recent 3 are `c8c1eca3` api: move primary from FingerId to Pointer events (at that commit the files were still `src/platform_impl/web/event_loop/window_target.rs` and `src/platform_impl/web/web_sys/pointer.rs`); `4e3165f3` chore: remove platform DeviceId (at that commit the files were still `src/platform_impl/web/event_loop/window_target.rs` and `src/platform_impl/web/web_sys/pointer.rs`); `eccd9e41` api: overhaul pointer API (at that commit the files were still `src/platform_impl/web/event_loop/window_target.rs` and `src/platform_impl/web/web_sys/pointer.rs`) — run `git show` on any of them.
Change coupling: mod.rs ↔ mod.rs winit-wayland/src/seat/pointer/mod.rs:1— `winit-wayland/src/seat/pointer/mod.rs` and `winit-wayland/src/seat/touch/mod.rs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `6a8a3344` macOS: add `WindowEvent::PointerButton::is_macos_activation_click`; `a9e7bef8` wayland: Update `sctk` to 0.21; `c8c1eca3` api: move primary from FingerId to Pointer events (at that commit the files were still `src/platform_impl/linux/wayland/seat/pointer/mod.rs` and `src/platform_impl/linux/wayland/seat/touch/mod.rs`) — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×3
Edited copy of a member (10 corresponding lines) winit-win32/src/window.rs:222— winit-win32/src/window.rs:222-231 | winit-win32/src/window.rs:802-812 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) winit-x11/src/ime/mod.rs:174— winit-x11/src/ime/mod.rs:174-183 | winit-x11/src/ime/mod.rs:185-194 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) winit-appkit/src/data_transfer.rs:460— winit-appkit/src/data_transfer.rs:460-469 | winit-win32/src/data_transfer.rs:928-937 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
winit_appkit::cursor::cursor_from_icon (cyclomatic 48) winit-appkit/src/cursor.rs:234— winit_appkit::cursor::cursor_from_icon has cyclomatic complexity 48 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
winit_appkit::window_delegate::new_window (cyclomatic 34) winit-appkit/src/window_delegate.rs:659— winit_appkit::window_delegate::new_window has cyclomatic complexity 34 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
EventProcessor::process_xevent (cyclomatic 42) winit-x11/src/event_processor.rs:150— EventProcessor::process_xevent has cyclomatic complexity 42 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
EventProcessor::client_message (cyclomatic 17) winit-x11/src/event_processor.rs:376— EventProcessor::client_message has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WinitState::event (cyclomatic 34) winit-wayland/src/seat/keyboard/mod.rs:23— WinitState::event has cyclomatic complexity 34 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
WinitState::pointer_frame (cyclomatic 29) winit-wayland/src/seat/pointer/mod.rs:37— WinitState::pointer_frame has cyclomatic complexity 29 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
WindowDelegate::set_fullscreen (cyclomatic 23) winit-appkit/src/window_delegate.rs:1813— WindowDelegate::set_fullscreen has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WindowDelegate::new (cyclomatic 19) winit-appkit/src/window_delegate.rs:910— WindowDelegate::new has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
WindowFlags::apply_diff (cyclomatic 21) winit-win32/src/window_state.rs:383— WindowFlags::apply_diff has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
WindowFlags::to_window_styles (cyclomatic 19) winit-win32/src/window_state.rs:303— WindowFlags::to_window_styles has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
KeyEventBuilder::process_message (cognitive 54) winit-win32/src/keyboard.rs:76— KeyEventBuilder::process_message has cognitive complexity 54 (threshold 15). Drivers by points: if/else 20 (43 pts), match/switch 4 (8 pts), boolean chains 3 (nesting depth added 27). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
KeyEventBuilder::synthesize_kbd_state (cognitive 17) winit-win32/src/keyboard.rs:311— KeyEventBuilder::synthesize_kbd_state has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 2 (3 pts), loops 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WinitView::handle_touches (cognitive 53) winit-uikit/src/view.rs:480— WinitView::handle_touches has cognitive complexity 53 (threshold 15). Drivers by points: if/else 20 (43 pts), match/switch 3 (9 pts), loops 1 (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WinitView::update_modifiers (cognitive 25) winit-appkit/src/view.rs:1102— WinitView::update_modifiers has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (22 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WinitState::event (cognitive 49) winit-wayland/src/seat/keyboard/mod.rs:23— WinitState::event has cognitive complexity 49 (threshold 15). Drivers by points: if/else 12 (25 pts), match/switch 14 (23 pts), boolean chains 1 (nesting depth added 22). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
WinitState::pointer_frame (cognitive 42) winit-wayland/src/seat/pointer/mod.rs:37— WinitState::pointer_frame has cognitive complexity 42 (threshold 15). Drivers by points: if/else 9 (19 pts), match/switch 8 (18 pts), boolean chains 4, loops 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WindowDelegate::set_fullscreen (cognitive 28) winit-appkit/src/window_delegate.rs:1813— WindowDelegate::set_fullscreen has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (21 pts), match/switch 3 (5 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WindowDelegate::new (cognitive 18) winit-appkit/src/window_delegate.rs:910— WindowDelegate::new has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (13 pts), match/switch 3, boolean chains 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
WindowFlags::apply_diff (cognitive 27) winit-win32/src/window_state.rs:383— WindowFlags::apply_diff has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (18 pts), match/switch 3 (6 pts), boolean chains 3 (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
WindowFlags::to_window_styles (cognitive 23) winit-win32/src/window_state.rs:303— WindowFlags::to_window_styles has cognitive complexity 23 (threshold 15). Drivers by points: if/else 18 (22 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
PartialKeyEventInfo::from_message (cognitive 18) winit-win32/src/keyboard.rs:493— PartialKeyEventInfo::from_message has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (13 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PartialKeyEventInfo::finalize (cognitive 16) winit-win32/src/keyboard.rs:586— PartialKeyEventInfo::finalize has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 3 (4 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TooManyFields: WindowState winit-wayland/src/window/state.rs:103— TooManyFields — 40 stored fields beside 78 methods. The bar is 30 stored fields; this is 10 over it, 1.33× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: WinitState winit-wayland/src/state.rs:48— TooManyFields — 33 stored fields beside 17 methods. The bar is 30 stored fields; this is 3 over it, 1.10× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×2
Edited copy of a member (30 corresponding lines) winit-core/src/keyboard.rs:38— winit-core/src/keyboard.rs:38-67 | winit-core/src/keyboard.rs:101-134 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (30 corresponding lines) winit-appkit/src/cursor.rs:46— winit-appkit/src/cursor.rs:46-78 | winit-appkit/src/cursor.rs:82-111 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×2
Edited copy of a member (17 corresponding lines) winit-win32/src/window.rs:711— winit-win32/src/window.rs:711-731 | winit-win32/src/window.rs:733-749 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) winit-x11/src/window.rs:1219— winit-x11/src/window.rs:1219-1235 | winit-x11/src/window.rs:1318-1336 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×2
Edited copy of a member (19 corresponding lines) winit-web/src/web_sys/canvas.rs:291— winit-web/src/web_sys/canvas.rs:291-309 | winit-web/src/web_sys/canvas.rs:314-332 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) winit-win32/src/icon.rs:31— winit-win32/src/icon.rs:31-52 | winit-win32/src/icon.rs:72-90 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×2
Edited copy of a member (16 corresponding lines) winit-wayland/src/data_transfer.rs:151— winit-wayland/src/data_transfer.rs:151-170 | winit-x11/src/data_transfer.rs:394-409 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) winit-win32/src/window.rs:138— winit-win32/src/window.rs:138-154 | winit-win32/src/window.rs:1260-1275 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×2
Edited copies of one member (3 members, 10+ corresponding lines) winit-web/src/web_sys/mod.rs:71— winit-web/src/web_sys/mod.rs:71-80 | winit-web/src/web_sys/mod.rs:87-101 | winit-web/src/web_sys/mod.rs:108-122 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 10+ corresponding lines) winit-x11/src/window.rs:1523— winit-x11/src/window.rs:1523-1532 | winit-x11/src/window.rs:1535-1544 | winit-x11/src/window.rs:1615-1624 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (17 lines × 2) winit-appkit/src/cursor.rs:51— winit-appkit/src/cursor.rs:51-67 | winit-appkit/src/cursor.rs:83-99 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-appkit/src/cursor.rs:51` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) winit-web/src/web_sys/event.rs:290— winit-web/src/web_sys/event.rs:290-306 | winit-web/src/web_sys/event.rs:309-325 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `event` to `&KeyboardEvent` in one and `&MouseEvent` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (15 lines × 2) winit-wayland/src/event_loop/mod.rs:432— winit-wayland/src/event_loop/mod.rs:432-446 | winit-wayland/src/event_loop/mod.rs:451-465 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-wayland/src/event_loop/mod.rs:432` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) winit-web/src/web_sys/canvas.rs:295— winit-web/src/web_sys/canvas.rs:295-309 | winit-web/src/web_sys/canvas.rs:318-332 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-web/src/web_sys/canvas.rs:295` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–13 lines × 2) winit-android/src/event_loop.rs:379— winit-android/src/event_loop.rs:379-390 | winit-android/src/event_loop.rs:423-435 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-android/src/event_loop.rs:379` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12–13 lines × 2) winit-uikit/src/view.rs:565— winit-uikit/src/view.rs:565-576 | winit-uikit/src/view.rs:624-636 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-uikit/src/view.rs:565` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 3) winit-appkit/src/data_transfer.rs:85— winit-appkit/src/data_transfer.rs:85-92 | winit-wayland/src/data_transfer.rs:238-245 | winit-x11/src/data_transfer.rs:421-427 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (7 lines × 3) winit-appkit/src/event_loop.rs:105— winit-appkit/src/event_loop.rs:105-111 | winit-win32/src/event_loop.rs:486-492 | winit-win32/src/window.rs:1055-1061 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (6 lines × 2) winit-appkit/src/data_transfer.rs:445— winit-appkit/src/data_transfer.rs:445-450 | winit-win32/src/data_transfer.rs:911-916 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) winit-appkit/src/cursor.rs:70— winit-appkit/src/cursor.rs:70-75 | winit-appkit/src/cursor.rs:101-106 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Low cohesion: ActiveEventLoop (LCOM4 4) winit-appkit/src/event_loop.rs:54— ActiveEventLoop's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ActiveEventLoop (LCOM4 4) winit-win32/src/event_loop.rs:451— ActiveEventLoop's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
TabletToolData::event (cyclomatic 36) winit-wayland/src/types/wp_tablet_input_v2.rs:92— TabletToolData::event has cyclomatic complexity 36 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
UnownedWindow::new (cyclomatic 35) winit-x11/src/window.rs:459— UnownedWindow::new has cyclomatic complexity 35 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
KeyEventBuilder::process_message (cyclomatic 29) winit-win32/src/keyboard.rs:76— KeyEventBuilder::process_message has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: winit_win32::keyboard::scancode_to_physicalkey (cyclomatic 160) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
LayoutCache::prepare_layout (cyclomatic 27) winit-win32/src/keyboard_layout.rs:285— LayoutCache::prepare_layout has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: winit_win32::keyboard_layout::keycode_to_vkey (cyclomatic 196) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
ContentType::from (cyclomatic 22) winit-wayland/src/seat/text_input/mod.rs:398— ContentType::from has cyclomatic complexity 22 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
WinitView::handle_touches (cyclomatic 18) winit-uikit/src/view.rs:480— WinitView::handle_touches has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TextInputState::event (cyclomatic 18) winit-wayland/src/seat/text_input/mod.rs:56— TextInputState::event has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
TabletToolAngle::tilt (cyclomatic 16) winit-core/src/event.rs:1397— TabletToolAngle::tilt has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: MouseButton::try_from_u8 (cyclomatic 33) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
Shared::set_listener (cyclomatic 16) winit-web/src/event_loop/runner.rs:280— Shared::set_listener has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LayoutCache::prepare_layout (cognitive 52) winit-win32/src/keyboard_layout.rs:285— LayoutCache::prepare_layout has cognitive complexity 52 (threshold 15). Drivers by points: if/else 12 (31 pts), match/switch 4 (9 pts), loops 5 (7 pts), boolean chains 5 (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UnownedWindow::new (cognitive 40) winit-x11/src/window.rs:459— UnownedWindow::new has cognitive complexity 40 (threshold 15). Drivers by points: if/else 27 (32 pts), match/switch 4, loops 2 (3 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
TabletToolData::event (cognitive 28) winit-wayland/src/types/wp_tablet_input_v2.rs:92— TabletToolData::event has cognitive complexity 28 (threshold 15). Drivers by points: match/switch 7 (16 pts), if/else 3 (10 pts), loops 1 (2 pts) (nesting depth added 17). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Shared::set_listener (cognitive 24) winit-web/src/event_loop/runner.rs:280— Shared::set_listener has cognitive complexity 24 (threshold 15). Drivers by points: if/else 16 (22 pts), loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Device::new (cognitive 24) winit-x11/src/event_loop.rs:1226— Device::new has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (16 pts), match/switch 1 (4 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 13). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
winit_common::core_foundation::tracing_observers::tracing_observers (cognitive 20) winit-common/src/core_foundation/tracing_observers.rs:19— winit_common::core_foundation::tracing_observers::tracing_observers has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (18 pts), match/switch 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
winit_uikit::app_state::handle_nonuser_events (cognitive 19) winit-uikit/src/app_state.rs:291— winit_uikit::app_state::handle_nonuser_events has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 4, loops 3 (4 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TextInputState::event (cognitive 19) winit-wayland/src/seat/text_input/mod.rs:56— TextInputState::event has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 4 (6 pts), boolean chains 2 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
CursorFlags::refresh_os_cursor (cognitive 18) winit-win32/src/window_state.rs:549— CursorFlags::refresh_os_cursor has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 2 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TabletToolTilt::angle (cognitive 16) winit-core/src/event.rs:1304— TabletToolTilt::angle has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
TabletToolAngle::tilt (cognitive 16) winit-core/src/event.rs:1397— TabletToolAngle::tilt has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 5 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
WindowState::configure_frame_and_size (cognitive 16) winit-wayland/src/window/state/configure.rs:61— WindowState::configure_frame_and_size has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7, match/switch 3 (6 pts), boolean chains 3 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (7 members, 50+ identical tokens) winit-win32/src/window.rs:496— winit-win32/src/window.rs:496-505 | winit-win32/src/window.rs:509-518 | winit-win32/src/window.rs:641-651 | winit-win32/src/window.rs:658-670 | winit-win32/src/window.rs:839-849 | winit-win32/src/window.rs:1021-1031 | winit-win32/src/window.rs:1038-1049 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) winit-android/src/event_loop.rs:517— winit-android/src/event_loop.rs:517-532 | winit-orbital/src/event_loop.rs:527-555 | winit-wayland/src/event_loop/mod.rs:180-203 | winit-x11/src/event_loop.rs:464-491 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (195 corresponding lines) · ×1
Edited copy of a member (195 corresponding lines) winit-common/src/xkb/keymap.rs:302— winit-common/src/xkb/keymap.rs:302-502 | winit-win32/src/keyboard.rs:897-1091 — These two members are one piece of code written twice and then edited apart: 195 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (172 corresponding lines) · ×1
Edited copy of a member (172 corresponding lines) winit-common/src/xkb/keymap.rs:34— winit-common/src/xkb/keymap.rs:34-300 | winit-win32/src/keyboard.rs:1093-1264 — These two members are one piece of code written twice and then edited apart: 172 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (61 corresponding lines) · ×1
Edited copy of a member (61 corresponding lines) winit-wayland/src/event_loop/mod.rs:251— winit-wayland/src/event_loop/mod.rs:251-317 | winit-x11/src/event_loop.rs:529-589 — These two members are one piece of code written twice and then edited apart: 61 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×1
Edited copy of a member (29 corresponding lines) winit-web/src/web_sys/pointer.rs:76— winit-web/src/web_sys/pointer.rs:76-104 | winit-web/src/web_sys/pointer.rs:114-166 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (34 corresponding lines) · ×1
Edited copy of a member (34 corresponding lines) winit-win32/src/window.rs:1750— winit-win32/src/window.rs:1750-1783 | winit-win32/src/window.rs:1785-1822 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×1
Edited copy of a member (31 corresponding lines) winit-wayland/src/state.rs:387— winit-wayland/src/state.rs:387-418 | winit-wayland/src/state.rs:457-487 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) winit-wayland/src/window/state.rs:355— winit-wayland/src/window/state.rs:355-377 | winit-wayland/src/window/state.rs:380-403 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×1
Edited copy of a member (18 corresponding lines) winit-appkit/src/window_delegate.rs:1470— winit-appkit/src/window_delegate.rs:1470-1487 | winit-appkit/src/window_delegate.rs:1489-1509 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×1
Edited copy of a member (25 corresponding lines) winit-android/src/event_loop.rs:997— winit-android/src/event_loop.rs:997-1021 | winit-uikit/src/window.rs:385-410 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×1
Edited copy of a member (24 corresponding lines) winit-wayland/src/data_transfer.rs:784— winit-wayland/src/data_transfer.rs:784-807 | winit-wayland/src/data_transfer.rs:821-844 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 19+ corresponding lines) · ×1
Edited copies of one member (4 members, 19+ corresponding lines) winit-uikit/src/view.rs:391— winit-uikit/src/view.rs:391-409 | winit-uikit/src/view.rs:416-436 | winit-uikit/src/view.rs:438-458 | winit-uikit/src/view.rs:460-478 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×1
Edited copy of a member (13 corresponding lines) winit-web/src/web_sys/pointer.rs:40— winit-web/src/web_sys/pointer.rs:40-52 | winit-web/src/web_sys/pointer.rs:58-70 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×1
Edited copy of a member (15 corresponding lines) winit-uikit/src/app_state.rs:360— winit-uikit/src/app_state.rs:360-374 | winit-uikit/src/app_state.rs:419-440 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 20+ corresponding lines) · ×1
Edited copies of one member (4 members, 20+ corresponding lines) winit-web/src/web_sys/event.rs:342— winit-web/src/web_sys/event.rs:342-361 | winit-web/src/web_sys/fullscreen.rs:139-158 | winit-web/src/web_sys/schedule.rs:230-250 | winit-web/src/web_sys/schedule.rs:252-271 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×1
Edited copy of a member (20 corresponding lines) winit-appkit/src/observer.rs:31— winit-appkit/src/observer.rs:31-50 | winit-uikit/src/app_state.rs:490-510 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×1
Edited copy of a member (11 corresponding lines) winit-appkit/src/window_delegate.rs:1301— winit-appkit/src/window_delegate.rs:1301-1311 | winit-appkit/src/window_delegate.rs:1320-1330 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) winit-android/src/event_loop.rs:538— winit-android/src/event_loop.rs:538-564 | winit-x11/src/event_loop.rs:497-517 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×1
Edited copy of a member (14 corresponding lines) winit-wayland/src/data_transfer.rs:648— winit-wayland/src/data_transfer.rs:648-661 | winit-wayland/src/data_transfer.rs:1360-1377 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×1
Edited copy of a member (12 corresponding lines) winit-x11/src/window.rs:1437— winit-x11/src/window.rs:1437-1448 | winit-x11/src/window.rs:1450-1461 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 11+ corresponding lines) · ×1
Edited copies of one member (4 members, 11+ corresponding lines) winit-web/src/window.rs:143— winit-web/src/window.rs:143-153 | winit-web/src/window.rs:159-170 | winit-web/src/window.rs:205-215 | winit-web/src/window.rs:217-227 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 6+ corresponding lines) · ×1
Edited copies of one member (3 members, 6+ corresponding lines) winit-orbital/src/window.rs:133— winit-orbital/src/window.rs:133-138 | winit-orbital/src/window.rs:221-226 | winit-orbital/src/window.rs:236-241 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×1
Edited copy of a member (6 corresponding lines) winit-appkit/src/view.rs:959— winit-appkit/src/view.rs:959-964 | winit-appkit/src/window_delegate.rs:1099-1104 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×1
Edited copy of a member (5 corresponding lines) winit-appkit/src/window_delegate.rs:1427— winit-appkit/src/window_delegate.rs:1427-1431 | winit-uikit/src/window.rs:196-200 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 3+ corresponding lines) · ×1
Edited copies of one member (6 members, 3+ corresponding lines) winit-android/src/event_loop.rs:40— winit-android/src/event_loop.rs:40-42 | winit-appkit/src/app_state.rs:418-420 | winit-orbital/src/event_loop.rs:902-904 | winit-wayland/src/event_loop/mod.rs:961-963 | winit-win32/src/event_loop.rs:724-726 | winit-x11/src/event_loop.rs:1327-1329 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 3+ corresponding lines) · ×1
Edited copies of one member (3 members, 3+ corresponding lines) winit-appkit/src/data_transfer.rs:181— winit-appkit/src/data_transfer.rs:181-183 | winit-wayland/src/data_transfer.rs:363-365 | winit-x11/src/data_transfer.rs:434-436 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (21 lines × 2) winit-core/src/keyboard.rs:40— winit-core/src/keyboard.rs:40-60 | winit-core/src/keyboard.rs:103-123 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-core/src/keyboard.rs:40` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) winit-web/src/event_loop/window_target.rs:127— winit-web/src/event_loop/window_target.rs:127-145 | winit-web/src/event_loop/window_target.rs:162-180 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-web/src/event_loop/window_target.rs:127` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17–18 lines × 2) winit-wayland/src/event_loop/mod.rs:210— winit-wayland/src/event_loop/mod.rs:210-227 | winit-x11/src/event_loop.rs:498-514 — before extracting anything, compare `winit-wayland/src/event_loop/mod.rs` and `winit-x11/src/event_loop.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `winit-wayland/src/event_loop/mod.rs:210` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15–17 lines × 2) winit-wayland/src/state.rs:388— winit-wayland/src/state.rs:388-404 | winit-wayland/src/state.rs:459-473 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14 lines × 2) winit-web/src/web_sys/pointer.rs:91— winit-web/src/web_sys/pointer.rs:91-104 | winit-web/src/web_sys/pointer.rs:153-166 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-web/src/web_sys/pointer.rs:91` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `winit-web/src/web_sys/pointer.rs:151` calls `set_pointer_capture` and `winit-web/src/web_sys/pointer.rs:90` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12–14 lines × 2) winit-x11/src/event_processor.rs:1768— winit-x11/src/event_processor.rs:1768-1781 | winit-x11/src/event_processor.rs:1784-1795 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11–13 lines × 4) winit-android/src/event_loop.rs:519— winit-android/src/event_loop.rs:519-531 | winit-orbital/src/event_loop.rs:530-540 | winit-wayland/src/event_loop/mod.rs:183-193 | winit-x11/src/event_loop.rs:467-477 — before extracting anything, compare `winit-android/src/event_loop.rs` and `winit-x11/src/event_loop.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `winit-wayland/src/event_loop/mod.rs:200` calls `roundtrip`, `map_err` and `winit-android/src/event_loop.rs:532` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) winit-x11/src/ime/context.rs:265— winit-x11/src/ime/context.rs:265-277 | winit-x11/src/ime/context.rs:325-337 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 3) winit-android/src/event_loop.rs:625— winit-android/src/event_loop.rs:625-634 | winit-wayland/src/event_loop/mod.rs:293-302 | winit-x11/src/event_loop.rs:562-571 — before extracting anything, compare `winit-android/src/event_loop.rs` and `winit-x11/src/event_loop.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9–10 lines × 3) winit-web/src/event_loop/window_target.rs:196— winit-web/src/event_loop/window_target.rs:196-204 | winit-web/src/event_loop/window_target.rs:222-230 | winit-web/src/event_loop/window_target.rs:334-343 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-web/src/event_loop/window_target.rs:196` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 5) winit-web/src/event_loop/window_target.rs:202— winit-web/src/event_loop/window_target.rs:202-210 | winit-web/src/event_loop/window_target.rs:228-236 | winit-web/src/event_loop/window_target.rs:312-320 | winit-web/src/event_loop/window_target.rs:341-349 | winit-web/src/event_loop/window_target.rs:367-376 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-web/src/event_loop/window_target.rs:202` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7–9 lines × 3) winit-web/src/event_loop/window_target.rs:128— winit-web/src/event_loop/window_target.rs:128-136 | winit-web/src/event_loop/window_target.rs:163-171 | winit-web/src/event_loop/window_target.rs:311-317 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-web/src/event_loop/window_target.rs:128` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 5) winit-web/src/event_loop/window_target.rs:201— winit-web/src/event_loop/window_target.rs:201-207 | winit-web/src/event_loop/window_target.rs:227-233 | winit-web/src/event_loop/window_target.rs:282-289 | winit-web/src/event_loop/window_target.rs:339-346 | winit-web/src/event_loop/window_target.rs:365-372 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 7) winit-win32/src/window.rs:497— winit-win32/src/window.rs:497-501 | winit-win32/src/window.rs:510-514 | winit-win32/src/window.rs:642-647 | winit-win32/src/window.rs:659-664 | winit-win32/src/window.rs:840-845 | winit-win32/src/window.rs:1022-1027 | winit-win32/src/window.rs:1039-1044 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `winit-win32/src/window.rs:497` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Off the main sequence: dpi — dpi: abstractness 0.11, instability 0.00, distance 0.89 — zone of pain — concrete and depended on by 11 project(s), so it's rigid to change.
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×1
JavaScript dependencies are not locked winit-web/src/script/package.json:2— winit-web/src/script/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:457— `error!` at line 457 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:604— `warn!` at line 604 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:608— `warn!` at line 608 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:631— `trace!` 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: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:640— `trace!` at line 640 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:646— `warn!` at line 646 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:657— `warn!` at line 657 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:667— `trace!` at line 667 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:673— `warn!` at line 673 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:713— `trace!` at line 713 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:729— `trace!` at line 729 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:762— `error!` at line 762 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:771— `trace!` at line 771 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:790— `trace!` at line 790 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:795— `error!` at line 795 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:851— `error!` at line 851 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:854— `trace!` at line 854 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:859— `trace!` at line 859 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:884— `warn!` at line 884 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:889— `trace!` at line 889 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:923— `error!` at line 923 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:1015— `trace!` at line 1015 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging winit-x11/src/data_transfer.rs:1021— `trace!` at line 1021 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging winit-x11/src/event_loop.rs:109— `error!` at line 109 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging winit-x11/src/event_loop.rs:257— `warn!` at line 257 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`.
Orphaned file winit-x11/src/util/geometry.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file winit-web/src/web_sys/schedule.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file winit-web/src/web_sys/resize_scaling.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file winit-x11/src/xsettings.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file winit-web/src/web_sys/mod.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file winit-win32/src/definitions.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file winit-x11/src/ime/callbacks.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file winit-common/src/core_foundation/tracing_observers.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file winit-win32/src/dark_mode.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file winit-x11/src/util/modifiers.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file winit-x11/src/util/wm.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file winit-web/src/web_sys/fullscreen.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file winit-common/src/core_foundation/event_loop_proxy.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file winit-web/src/async/dispatcher.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file winit-x11/src/util/hint.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file winit-web/src/async/wrapper.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file winit-appkit/src/menu.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file winit-x11/src/util/input.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file winit-wayland/src/types/xdg_toplevel_icon_manager.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file winit-web/src/lock.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file winit-appkit/src/observer.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file winit-web/src/main_thread.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
README/code drift winit-android/README.md:16— 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.
README/code drift winit-android/README.md:38— 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.
README/code drift winit-appkit/README.md:16— 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.
README/code drift winit-appkit/README.md:38— 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.
README/code drift winit-common/README.md:16— 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.
README/code drift winit-common/README.md:38— 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.
README/code drift winit-core/README.md:16— 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.
README/code drift winit-core/README.md:38— 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.
README/code drift winit-orbital/README.md:16— 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.
README/code drift winit-orbital/README.md:38— 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.
README/code drift winit-uikit/README.md:16— 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.
README/code drift winit-uikit/README.md:38— 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.
README/code drift winit-wayland/README.md:16— 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.
README/code drift winit-wayland/README.md:38— 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.
README/code drift winit-web/README.md:16— 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.
README/code drift winit-web/README.md:38— 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.
README/code drift winit-win32/README.md:16— 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.
README/code drift winit-win32/README.md:38— 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.
README/code drift winit-x11/README.md:16— 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.
README/code drift winit-x11/README.md:38— 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.
README/code drift winit/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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 3 significant file(s) lose their only recent owner: winit-appkit/src/app.rs, winit-common/src/core_foundation/main_run_loop.rs, winit-appkit/src/ffi.rs. Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 1 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (5 single-owned of 138 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 138 of the 189 production source files in this repository met that bar). They are anonymized user #2 (2 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: winit-common/src/xkb/compose.rs, winit-wayland/src/window/state/ime.rs.
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 22 of 138 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 138 of the 189 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: winit-x11/src/util/geometry.rs, winit-web/src/web_sys/schedule.rs, winit-web/src/web_sys/resize_scaling.rs, winit-x11/src/xsettings.rs, winit-web/src/web_sys/mod.rs, winit-win32/src/definitions.rs, winit-x11/src/ime/callbacks.rs, winit-common/src/core_foundation/tracing_observers.rs (and 14 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P3 · Security & performance tooling· Dependabot does not watch cargo · ×1
Dependabot does not watch cargo REDACTED:3— `REDACTED` schedules updates, but no `package-ecosystem` entry covers `cargo`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list.
Silent fallback default on Err winit-orbital/src/lib.rs:114— `new` turns every `Err` into `0` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Outdated: smol_str — `smol_str` is locked at 0.3.2 but 0.3.7 is the current stable release on crates.io, and it already satisfies the `"0.3"` requirement declared in winit-android/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p smol_str` and commit the updated Cargo.lock.
Off the main sequence: winit-common — winit-common: abstractness 0.00, instability 0.25, distance 0.75 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1db3f-a44e-7519-9b2a-8e7ba6c39df7 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 32 · Warnings: 499 · Recommendations: 90 · Info: 2 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 18:09 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.