Repository Analysis

iced-rs/iced

A cross-platform GUI library for Rust, inspired by Elm

3.5 Likely human-written View on GitHub

Analysis Overview

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).

3.5
Adjusted Score
3.5
Raw Score
100%
Time Factor
2026-07-09
Last Push
31.0K
Stars
Rust
Language
100.8K
Lines of Code
504
Files
363
Pattern Hits
2026-07-14
Scan Date
0.00
HC Hit Rate

What These Metrics Mean

Adjusted Score
Primary synthetic code indicator. Raw score normalised per 1,000 lines of code and multiplied by the temporal discount factor. This is the definitive comparative metric — use it to rank repositories by AI authorship density.
Raw Score
The unmodified sum of all severity-weighted, context-multiplied pattern match scores before temporal discounting. Reflects the absolute signal strength independent of when the repository was last active.
Time Factor
The temporal discount multiplier (0–100%) applied to the raw score. Repositories last updated before ChatGPT's launch (Nov 2022) receive a 5% factor. Full signal is only assigned to repositories active in the post-adoption era (Jan 2024+).
Pattern Hits
Total count of individual pattern matches across all files and categories. A high hit count with a low score may indicate a very large codebase with isolated AI snippets; a low count with a high score indicates dense, concentrated AI signatures.
HC Hit Rate
High+Critical pattern hits per file, averaged across the repository. This orthogonal signal catches repositories where a few files are densely packed with high-severity AI tells — a strong indicator even when the normalised score appears moderate due to codebase size.
Lines of Code / Files
Total lines and files analysed. The scanner examines 94 file extensions. These denominators are used to normalise the score, enabling fair comparison between repositories of vastly different sizes.

Score History

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.

Severity Breakdown

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.

CRITICAL 0HIGH 0MEDIUM 11LOW 352

Directory Score Breakdown

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.

Pattern Findings

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.

Over-Commented Block347 hits · 312 pts
SeverityFileLineSnippetContext
LOWcore/src/element.rs41 pub fn as_widget_mut(&mut self) -> &mut dyn Widget<Message, Theme, Renderer> {COMMENT
LOWcore/src/element.rs61 /// use counter::Counter;COMMENT
LOWcore/src/element.rs81 /// Counter(usize, counter::Message)COMMENT
LOWcore/src/element.rs101 /// # #[derive(Debug, Clone, Copy)]COMMENT
LOWcore/src/element.rs121 /// }COMMENT
LOWcore/src/element.rs141 /// }),COMMENT
LOWcore/src/element.rs161 /// #COMMENT
LOWcore/src/font.rs81COMMENT
LOWcore/src/renderer.rs61 );COMMENT
LOWcore/src/length.rs1//! Describe amounts of space accurately.COMMENT
LOWcore/src/widget.rs21/// If you want to build your own widgets, you will need to implement thisCOMMENT
LOWcore/src/backend.rs1//! Graphical backends are designed to aid in rendering computer graphics to a monitor.COMMENT
LOWcore/src/backend.rs141pub struct Settings {COMMENT
LOWcore/src/color.rs1//! Manage colors in different color spaces.COMMENT
LOWcore/src/color.rs381}COMMENT
LOWcore/src/lib.rs101COMMENT
LOWcore/src/lib.rs121 /// # let element: Option<()> = Some(());COMMENT
LOWcore/src/event.rs41pub enum Status {COMMENT
LOWcore/src/border.rs21/// #COMMENT
LOWcore/src/image.rs81 Path(Id, PathBuf),COMMENT
LOWcore/src/image.rs221/// A memory allocation of a [`Handle`], often in GPU memory.COMMENT
LOWcore/src/image.rs281COMMENT
LOWcore/src/image.rs301 ///COMMENT
LOWcore/src/padding.rs1//! Space stuff around the perimeter.COMMENT
LOWcore/src/padding.rs21/// # struct Widget;COMMENT
LOWcore/src/content_fit.rs1//! Control the fit of some content (like an image) within a space.COMMENT
LOWcore/src/content_fit.rs21 /// within the window. This won't distort the image or crop/hide any edges,COMMENT
LOWcore/src/content_fit.rs41 Cover,COMMENT
LOWcore/src/rotation.rs1//! Control the rotation of some content (like an image) within a space.COMMENT
LOWcore/src/text.rs141 }COMMENT
LOWcore/src/text.rs161 ///COMMENT
LOWcore/src/text.rs201 Word,COMMENT
LOWcore/src/text.rs301 /// No difference.COMMENT
LOWcore/src/text.rs341 /// [`ICON_FONT`]: Self::ICON_FONTCOMMENT
LOWcore/src/input_method.rs1//! Listen to input method events.COMMENT
LOWcore/src/input_method.rs81 ///COMMENT
LOWcore/src/input_method.rs101 /// preedit: Some(Preedit { content: "2".to_owned(), selection: None, text_size: None }),COMMENT
LOWcore/src/input_method.rs141 preedit: preedit.as_ref().map(Preedit::to_owned),COMMENT
LOWcore/src/input_method.rs161 /// [`Commit`][Self::Commit] events. You should also start performing IME related requestsCOMMENT
LOWcore/src/input_method.rs181 /// Notifies when the IME was disabled.COMMENT
LOWcore/src/settings.rs21 ///COMMENT
LOWcore/src/settings.rs41 /// primitives.COMMENT
LOWcore/src/widget/text.rs1//! Text widgets display information through writing.COMMENT
LOWcore/src/widget/text.rs41/// # pub type Element<'a, Message> = iced_core::Element<'a, Message, iced_core::Theme, ()>;COMMENT
LOWcore/src/layout/flex.rs1//! Distribute elements using a flex-based layout.COMMENT
LOWcore/src/window/user_attention.rs1/// The type of user attention to request.COMMENT
LOWcore/src/window/event.rs1use crate::time::Instant;COMMENT
LOWcore/src/window/event.rs41 /// The user has requested for the window to close.COMMENT
LOWcore/src/window/event.rs61 ///COMMENT
LOWcore/src/window/position.rs1use crate::{Point, Size};COMMENT
LOWcore/src/window/level.rs1/// A window level groups windows with respect to their z-position.COMMENT
LOWcore/src/window/settings.rs61COMMENT
LOWcore/src/window/settings.rs81 pub blur: bool,COMMENT
LOWcore/src/window/settings/windows.rs1//! Platform specific settings for Windows.COMMENT
LOWcore/src/window/settings/windows.rs41 /// Let the system decide when to round window corners.COMMENT
LOWcore/src/window/settings/linux.rs1//! Platform specific settings for Linux.COMMENT
LOWcore/src/keyboard/key.rs1//! Identify keyboard keys.COMMENT
LOWcore/src/keyboard/key.rs41 ///COMMENT
LOWcore/src/keyboard/key.rs121 fn from(named: Named) -> Self {COMMENT
LOWcore/src/keyboard/key.rs141 /// This key is used enable the ISO Level 3 shift modifier (the standard `Shift` key is theCOMMENT
287 more matches not shown…
AI Slop Vocabulary10 hits · 30 pts
SeverityFileLineSnippetContext
MEDIUMcore/src/shell.rs11/// A [`Widget`] can leverage a [`Shell`] to trigger changes in an application,COMMENT
MEDIUMcore/src/padding.rs6/// You can leverage the `From` trait to build [`Padding`] conveniently:COMMENT
MEDIUMcore/src/text.rs50 /// calculation of the [`Paragraph`] and leverage metrics hinting.COMMENT
MEDIUMfutures/src/subscription.rs137 /// You can leverage this helper to create a [`Subscription`] that spawnsCOMMENT
MEDIUMwidget/src/themer.rs15/// This widget can be useful to leverage multiple `Theme`COMMENT
MEDIUMtest/src/lib.rs38//! In this case, we leverage the [`Selector`] implementation of `&str`, which selects a widget by the text it contains.COMMENT
MEDIUMwgpu/src/primitive.rs43 /// If you have complex composition needs, then you can leverageCOMMENT
MEDIUMsrc/lib.rs377//! A common pattern is to leverage this composability to split anCOMMENT
MEDIUMsrc/lib.rs470//! seamless.COMMENT
MEDIUMsrc/time.rs19/// You may care about purity if you want to leverage the `time-travel`COMMENT
Fake / Example Data4 hits · 6 pts
SeverityFileLineSnippetContext
LOWbenches/ipsum.txt1Lorem ipsum dolor sit amet, consectetur adipiscing elit. Curabitur at elit mollis, dictum nunc non, tempus metus. Sed iaCODE
LOWbenches/ipsum.txt1Lorem ipsum dolor sit amet, consectetur adipiscing elit. Curabitur at elit mollis, dictum nunc non, tempus metus. Sed iaCODE
LOWbenches/ipsum.txt3Cras ullamcorper tincidunt tellus non tempor. Integer pulvinar turpis quam, nec pharetra purus egestas non. Vivamus sed CODE
LOWbenches/ipsum.txt3Cras ullamcorper tincidunt tellus non tempor. Integer pulvinar turpis quam, nec pharetra purus egestas non. Vivamus sed CODE
Self-Referential Comments1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMfutures/src/subscription.rs136 /// # Creating an asynchronous worker with bidirectional communicationCOMMENT
Deep Nesting1 hit · 1 pts
SeverityFileLineSnippetContext
LOWdocs/release_summary.py30CODE