Window handling library in pure Rust
This report summarizes scanner evidence for rust-windowing/winit, a Rust project with 6,194 GitHub stars. SynthScan examined 77,856 lines of code across 286 source files, recording 371 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 4.3 (Low pattern signal); it is not an authorship estimate.
Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.
Use each vector to guide manual verification of the underlying findings.
Can maintainers explain intent, assumptions, and trade-offs? 371 finding(s).
Are imports declared and package/API names verified? 0 finding(s).
Are wrappers, guards, and repeated structures necessary? 0 finding(s).
Which changes need focused human review? 371 finding(s).
This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.
Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.
This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.
The scanner identified 371 distinct pattern matches across 4 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.
Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | winit-appkit/src/lib.rs | 1 | //! # macOS / AppKit | COMMENT |
| LOW | winit-appkit/src/lib.rs | 21 | //! use objc2::rc::Retained; | COMMENT |
| LOW | winit-appkit/src/lib.rs | 41 | //! println!("open urls: {application:?}, {urls:?}"); | COMMENT |
| LOW | winit-appkit/src/lib.rs | 101 | use self::window::Window as AppKitWindow; | COMMENT |
| LOW | winit-appkit/src/lib.rs | 141 | /// | COMMENT |
| LOW | winit-appkit/src/lib.rs | 161 | /// ``` | COMMENT |
| LOW | winit-appkit/src/lib.rs | 181 | fn set_borderless_game(&self, borderless_game: bool); | COMMENT |
| LOW | winit-appkit/src/lib.rs | 201 | /// A window marked as fullscreen auxiliary cannot itself enter (native) fullscreen; | COMMENT |
| LOW | winit-appkit/src/lib.rs | 361 | #[non_exhaustive] | COMMENT |
| LOW | winit-appkit/src/lib.rs | 501 | COMMENT | |
| LOW | winit-appkit/src/lib.rs | 561 | /// If unused, the Winit will honor the package manifest. | COMMENT |
| LOW | winit-appkit/src/lib.rs | 581 | /// Used to control whether a default menubar menu is created. | COMMENT |
| LOW | winit-appkit/src/lib.rs | 681 | Both, | COMMENT |
| LOW | winit-appkit/src/lib.rs | 701 | /// [`Window::set_blur`]: winit_core::window::Window::set_blur | COMMENT |
| LOW | winit-appkit/src/event.rs | 481 | // Follows what Chromium and Firefox do: | COMMENT |
| LOW | winit-appkit/src/window_delegate.rs | 101 | /// Whether the window is showing decorations. | COMMENT |
| LOW | winit-appkit/src/window_delegate.rs | 321 | self.ivars().in_fullscreen_transition.set(false); | COMMENT |
| LOW | winit-appkit/src/window_delegate.rs | 761 | } | COMMENT |
| LOW | winit-appkit/src/window_delegate.rs | 1901 | } | COMMENT |
| LOW | winit-appkit/src/app.rs | 61 | /// | COMMENT |
| LOW | winit-appkit/src/view.rs | 161 | impl WinitView { | COMMENT |
| LOW | winit-appkit/src/view.rs | 581 | is_synthetic: false, | COMMENT |
| LOW | winit-appkit/src/view.rs | 841 | option_as_alt: Cell::new(option_as_alt), | COMMENT |
| LOW | winit-appkit/src/view.rs | 861 | // `ActiveAlways` indicates we want to receive events when the window is not | COMMENT |
| LOW | winit-appkit/src/view.rs | 1041 | self.ivars().modifiers.set(current_modifiers); | COMMENT |
| LOW | winit-win32/src/dnd.rs | 1541 | } | COMMENT |
| LOW | winit-win32/src/raw_input.rs | 221 | unsafe { MapVirtualKeyW(keyboard.VKey as u32, MAPVK_VK_TO_VSC_EX) as u16 } | COMMENT |
| LOW | winit-win32/src/raw_input.rs | 241 | // that there's going to be another event coming, from which we can extract the | COMMENT |
| LOW | winit-win32/src/raw_input.rs | 281 | // wasn't active. The way this is exposed to applications by the system is that | COMMENT |
| LOW | winit-win32/src/keyboard_layout.rs | 181 | COMMENT | |
| LOW | winit-win32/src/keyboard_layout.rs | 301 | // but map to the numpad. | COMMENT |
| LOW | winit-win32/src/lib.rs | 41 | pub use self::monitor::{MonitorHandle, VideoModeHandle}; | COMMENT |
| LOW | winit-win32/src/lib.rs | 61 | /// | COMMENT |
| LOW | winit-win32/src/lib.rs | 121 | /// | COMMENT |
| LOW | winit-win32/src/lib.rs | 161 | } | COMMENT |
| LOW | winit-win32/src/lib.rs | 181 | /// unspecified, although explicitly not undefined, behavior. | COMMENT |
| LOW | winit-win32/src/lib.rs | 201 | /// # if false { // We can't test this part | COMMENT |
| LOW | winit-win32/src/lib.rs | 221 | /// let msg = msg as *const MSG; | COMMENT |
| LOW | winit-win32/src/lib.rs | 241 | /// | COMMENT |
| LOW | winit-win32/src/lib.rs | 261 | /// Shows or hides the background drop shadow for undecorated windows. | COMMENT |
| LOW | winit-win32/src/lib.rs | 281 | /// Sets the color of the window title. | COMMENT |
| LOW | winit-win32/src/lib.rs | 301 | /// | COMMENT |
| LOW | winit-win32/src/lib.rs | 321 | /// | COMMENT |
| LOW | winit-win32/src/lib.rs | 441 | /// This function wraps anything that implements `Borrow<Window>` into a structure that | COMMENT |
| LOW | winit-win32/src/lib.rs | 501 | } | COMMENT |
| LOW | winit-win32/src/lib.rs | 521 | /// [`WindowAttributes::with_parent_window`]: winit_core::window::WindowAttributes::with_parent_window | COMMENT |
| LOW | winit-win32/src/lib.rs | 661 | fn persistent_identifier(&self) -> Option<String> { | COMMENT |
| LOW | winit-win32/src/lib.rs | 701 | /// The valid `ordinal` values range from 1 to [`u16::MAX`] (inclusive). The value `0` is an | COMMENT |
| LOW | winit-win32/src/lib.rs | 721 | /// icon size from the file. | COMMENT |
| LOW | winit-win32/src/lib.rs | 741 | /// [`from_resource`]: Self::from_resource | COMMENT |
| LOW | winit-win32/src/keyboard.rs | 41 | } | COMMENT |
| LOW | winit-win32/src/keyboard.rs | 321 | ($vk:expr) => { | COMMENT |
| LOW | winit-win32/src/event_loop.rs | 321 | /// Doesn't peek messages itself. | COMMENT |
| LOW | winit-win32/src/event_loop.rs | 341 | // Before we potentially exit, make sure to consistently emit an event for the wake up | COMMENT |
| LOW | winit-win32/src/event_loop.rs | 641 | /// Windows has no real API to check if the current executing thread is the "main thread", unlike | COMMENT |
| LOW | winit-win32/src/event_loop.rs | 721 | ptr::null(), | COMMENT |
| LOW | winit-win32/src/event_loop.rs | 1261 | let monitor = unsafe { MonitorFromRect(¶ms.rgrc[0], MONITOR_DEFAULTTONULL) }; | COMMENT |
| LOW | winit-win32/src/event_loop.rs | 1301 | COMMENT | |
| LOW | winit-win32/src/event_loop/runner.rs | 461 | } | COMMENT |
| LOW | winit-win32/src/event_loop/runner.rs | 481 | /// ^ | | COMMENT |
| 307 more matches not shown… | ||||
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| HIGH | winit-appkit/src/window_delegate.rs | 333 | /// will be failed. In this implementation, we will try again by using | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | winit-core/src/window.rs | 673 | /// the most robust way to track the DPI you need to use to draw. | COMMENT |
| MEDIUM | winit-wayland/src/types/wp_tablet_input_v2.rs | 286 | // NOTE: even though we don't utilize serials | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | winit-appkit/src/app.rs | 69 | /// NOTE: This function assumes that the passed in application object is the one returned from | COMMENT |