A cross-platform GUI library for Rust, inspired by Elm
This report presents the forensic synthetic code analysis of iced-rs/iced, a Rust project with 30,971 GitHub stars. SynthScan v2.0 examined 100,790 lines of code across 504 source files, recording 363 pattern matches distributed across 5 syntactic categories. The overall adjusted score of 3.5 places this repository in the Likely human-written band.
The scanner applied 160+ deterministic lexical heuristics, multi-line block detectors, abstract syntax tree depth profilers, and a cross-file Jaccard similarity matrix to construct a statistically normalised synthetic code estimate. All matches are individually weighted by severity coefficient and contextual multiplier before summation, and the resulting headline score is temporally discounted to account for the repository's development history relative to the commercial emergence of large language model coding tooling (November 2022 onward).
This chart maps the temporal evolution of the adjusted synthetic code score across successive scan runs. An upward trajectory indicates ongoing incorporation of AI-generated code or expanding LLM-assisted scaffolding; a stable or declining trajectory may reflect active human refactoring, code removal, or the adoption of stricter authorship policies. The dashed secondary line (right axis) independently tracks total raw pattern hit count, which can diverge from the normalised score when codebase size changes significantly between scans.
Classifies detected patterns by their diagnostic confidence and structural impact. CRITICAL patterns (coefficient 10) represent definitive synthetic signatures — hallucinated imports, explicit LLM attribution metadata — virtually never produced by human authors. HIGH (5) indicates strong structural tells such as cross-file repetition or cross-linguistic idioms. MEDIUM (2) covers recognisable conversational padding and AI-specific vocabulary. LOW (1) captures subtle indicators like tautological comments and generic boilerplate that require density to carry independent signal.
This horizontal bar chart decomposes the repository's raw synthetic code score by top-level directory, allowing you to pinpoint precisely which modules or components carry the highest AI authorship density. Directories with disproportionately high scores relative to their size warrant targeted manual review: concentrated AI signatures often trace back to mass-generated configuration layers, auto-ported test suites, LLM-scaffolded boilerplate classes, or entire subsystems authored under heavy copilot assistance. Use this view to prioritise your human code-review effort.
The scanner identified 363 distinct pattern matches across 5 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a statistically significant AI authorship indicator. 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 diagnostic confidence level (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — comment-context matches receive a ×1.5 weight because LLMs systematically over-annotate. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier as dense clusters constitute far stronger evidence of synthetic authorship than isolated hits.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | core/src/element.rs | 41 | pub fn as_widget_mut(&mut self) -> &mut dyn Widget<Message, Theme, Renderer> { | COMMENT |
| LOW | core/src/element.rs | 61 | /// use counter::Counter; | COMMENT |
| LOW | core/src/element.rs | 81 | /// Counter(usize, counter::Message) | COMMENT |
| LOW | core/src/element.rs | 101 | /// # #[derive(Debug, Clone, Copy)] | COMMENT |
| LOW | core/src/element.rs | 121 | /// } | COMMENT |
| LOW | core/src/element.rs | 141 | /// }), | COMMENT |
| LOW | core/src/element.rs | 161 | /// # | COMMENT |
| LOW | core/src/font.rs | 81 | COMMENT | |
| LOW | core/src/renderer.rs | 61 | ); | COMMENT |
| LOW | core/src/length.rs | 1 | //! Describe amounts of space accurately. | COMMENT |
| LOW | core/src/widget.rs | 21 | /// If you want to build your own widgets, you will need to implement this | COMMENT |
| LOW | core/src/backend.rs | 1 | //! Graphical backends are designed to aid in rendering computer graphics to a monitor. | COMMENT |
| LOW | core/src/backend.rs | 141 | pub struct Settings { | COMMENT |
| LOW | core/src/color.rs | 1 | //! Manage colors in different color spaces. | COMMENT |
| LOW | core/src/color.rs | 381 | } | COMMENT |
| LOW | core/src/lib.rs | 101 | COMMENT | |
| LOW | core/src/lib.rs | 121 | /// # let element: Option<()> = Some(()); | COMMENT |
| LOW | core/src/event.rs | 41 | pub enum Status { | COMMENT |
| LOW | core/src/border.rs | 21 | /// # | COMMENT |
| LOW | core/src/image.rs | 81 | Path(Id, PathBuf), | COMMENT |
| LOW | core/src/image.rs | 221 | /// A memory allocation of a [`Handle`], often in GPU memory. | COMMENT |
| LOW | core/src/image.rs | 281 | COMMENT | |
| LOW | core/src/image.rs | 301 | /// | COMMENT |
| LOW | core/src/padding.rs | 1 | //! Space stuff around the perimeter. | COMMENT |
| LOW | core/src/padding.rs | 21 | /// # struct Widget; | COMMENT |
| LOW | core/src/content_fit.rs | 1 | //! Control the fit of some content (like an image) within a space. | COMMENT |
| LOW | core/src/content_fit.rs | 21 | /// within the window. This won't distort the image or crop/hide any edges, | COMMENT |
| LOW | core/src/content_fit.rs | 41 | Cover, | COMMENT |
| LOW | core/src/rotation.rs | 1 | //! Control the rotation of some content (like an image) within a space. | COMMENT |
| LOW | core/src/text.rs | 141 | } | COMMENT |
| LOW | core/src/text.rs | 161 | /// | COMMENT |
| LOW | core/src/text.rs | 201 | Word, | COMMENT |
| LOW | core/src/text.rs | 301 | /// No difference. | COMMENT |
| LOW | core/src/text.rs | 341 | /// [`ICON_FONT`]: Self::ICON_FONT | COMMENT |
| LOW | core/src/input_method.rs | 1 | //! Listen to input method events. | COMMENT |
| LOW | core/src/input_method.rs | 81 | /// | COMMENT |
| LOW | core/src/input_method.rs | 101 | /// preedit: Some(Preedit { content: "2".to_owned(), selection: None, text_size: None }), | COMMENT |
| LOW | core/src/input_method.rs | 141 | preedit: preedit.as_ref().map(Preedit::to_owned), | COMMENT |
| LOW | core/src/input_method.rs | 161 | /// [`Commit`][Self::Commit] events. You should also start performing IME related requests | COMMENT |
| LOW | core/src/input_method.rs | 181 | /// Notifies when the IME was disabled. | COMMENT |
| LOW | core/src/settings.rs | 21 | /// | COMMENT |
| LOW | core/src/settings.rs | 41 | /// primitives. | COMMENT |
| LOW | core/src/widget/text.rs | 1 | //! Text widgets display information through writing. | COMMENT |
| LOW | core/src/widget/text.rs | 41 | /// # pub type Element<'a, Message> = iced_core::Element<'a, Message, iced_core::Theme, ()>; | COMMENT |
| LOW | core/src/layout/flex.rs | 1 | //! Distribute elements using a flex-based layout. | COMMENT |
| LOW | core/src/window/user_attention.rs | 1 | /// The type of user attention to request. | COMMENT |
| LOW | core/src/window/event.rs | 1 | use crate::time::Instant; | COMMENT |
| LOW | core/src/window/event.rs | 41 | /// The user has requested for the window to close. | COMMENT |
| LOW | core/src/window/event.rs | 61 | /// | COMMENT |
| LOW | core/src/window/position.rs | 1 | use crate::{Point, Size}; | COMMENT |
| LOW | core/src/window/level.rs | 1 | /// A window level groups windows with respect to their z-position. | COMMENT |
| LOW | core/src/window/settings.rs | 61 | COMMENT | |
| LOW | core/src/window/settings.rs | 81 | pub blur: bool, | COMMENT |
| LOW | core/src/window/settings/windows.rs | 1 | //! Platform specific settings for Windows. | COMMENT |
| LOW | core/src/window/settings/windows.rs | 41 | /// Let the system decide when to round window corners. | COMMENT |
| LOW | core/src/window/settings/linux.rs | 1 | //! Platform specific settings for Linux. | COMMENT |
| LOW | core/src/keyboard/key.rs | 1 | //! Identify keyboard keys. | COMMENT |
| LOW | core/src/keyboard/key.rs | 41 | /// | COMMENT |
| LOW | core/src/keyboard/key.rs | 121 | fn from(named: Named) -> Self { | COMMENT |
| LOW | core/src/keyboard/key.rs | 141 | /// This key is used enable the ISO Level 3 shift modifier (the standard `Shift` key is the | COMMENT |
| 287 more matches not shown… | ||||
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | core/src/shell.rs | 11 | /// A [`Widget`] can leverage a [`Shell`] to trigger changes in an application, | COMMENT |
| MEDIUM | core/src/padding.rs | 6 | /// You can leverage the `From` trait to build [`Padding`] conveniently: | COMMENT |
| MEDIUM | core/src/text.rs | 50 | /// calculation of the [`Paragraph`] and leverage metrics hinting. | COMMENT |
| MEDIUM | futures/src/subscription.rs | 137 | /// You can leverage this helper to create a [`Subscription`] that spawns | COMMENT |
| MEDIUM | widget/src/themer.rs | 15 | /// This widget can be useful to leverage multiple `Theme` | COMMENT |
| MEDIUM | test/src/lib.rs | 38 | //! In this case, we leverage the [`Selector`] implementation of `&str`, which selects a widget by the text it contains. | COMMENT |
| MEDIUM | wgpu/src/primitive.rs | 43 | /// If you have complex composition needs, then you can leverage | COMMENT |
| MEDIUM | src/lib.rs | 377 | //! A common pattern is to leverage this composability to split an | COMMENT |
| MEDIUM | src/lib.rs | 470 | //! seamless. | COMMENT |
| MEDIUM | src/time.rs | 19 | /// You may care about purity if you want to leverage the `time-travel` | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW⚡ | benches/ipsum.txt | 1 | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Curabitur at elit mollis, dictum nunc non, tempus metus. Sed ia | CODE |
| LOW⚡ | benches/ipsum.txt | 1 | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Curabitur at elit mollis, dictum nunc non, tempus metus. Sed ia | CODE |
| LOW⚡ | benches/ipsum.txt | 3 | Cras ullamcorper tincidunt tellus non tempor. Integer pulvinar turpis quam, nec pharetra purus egestas non. Vivamus sed | CODE |
| LOW⚡ | benches/ipsum.txt | 3 | Cras ullamcorper tincidunt tellus non tempor. Integer pulvinar turpis quam, nec pharetra purus egestas non. Vivamus sed | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | futures/src/subscription.rs | 136 | /// # Creating an asynchronous worker with bidirectional communication | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | docs/release_summary.py | 30 | CODE |