Executes commands in response to file modifications
This report presents the forensic synthetic code analysis of watchexec/watchexec, a Rust project with 7,107 GitHub stars. SynthScan v2.0 examined 23,549 lines of code across 200 source files, recording 135 pattern matches distributed across 2 syntactic categories. The overall adjusted score of 5.7 places this repository in the Low AI signal 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).
Longitudinal tracking requires multiple scan runs. Once this repository is re-scanned after new commits land, this chart will visualise how the synthetic code signal evolves over time — enabling you to detect whether AI authorship is growing, stabilising, or being actively corrected by human engineers.
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 135 distinct pattern matches across 2 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 | crates/filterer/globset/src/lib.rs | 41 | .field("filters", &"ignore::gitignore::Gitignore{...}") | COMMENT |
| LOW | crates/filterer/ignore/tests/filtering.rs | 121 | // #[cfg(windows)] FIXME should work | COMMENT |
| LOW | crates/filterer/ignore/tests/filtering.rs | 141 | #[cfg(not(windows))] | COMMENT |
| LOW | crates/filterer/ignore/src/lib.rs | 1 | //! A Watchexec Filterer implementation for ignore files. | COMMENT |
| LOW | crates/project-origins/src/lib.rs | 1 | //! Resolve project origins and kinds from a path. | COMMENT |
| LOW | crates/project-origins/src/lib.rs | 21 | use futures::StreamExt; | COMMENT |
| LOW | crates/project-origins/src/lib.rs | 41 | COMMENT | |
| LOW | crates/project-origins/src/lib.rs | 61 | /// Detects when a `.hg` folder is present, or any of the files `.hgignore` or `.hgtags`. | COMMENT |
| LOW | crates/project-origins/src/lib.rs | 81 | /// Soft: the [C programming language](https://en.wikipedia.org/wiki/C_(programming_language)). | COMMENT |
| LOW | crates/project-origins/src/lib.rs | 101 | /// Soft: the [Go](https://golang.net) language. | COMMENT |
| LOW | crates/project-origins/src/lib.rs | 121 | /// Detects when a `project.clj` file is present. | COMMENT |
| LOW | crates/signals/src/lib.rs | 1 | #![doc = include_str!("../README.md")] | COMMENT |
| LOW | crates/signals/src/lib.rs | 21 | /// On Windows, only some signals are supported, as described. Others will be ignored. | COMMENT |
| LOW | crates/signals/src/lib.rs | 41 | /// Despite its nominal purpose, on Unix this signal is often used to reload configuration files. | COMMENT |
| LOW | crates/signals/src/lib.rs | 61 | /// Indicate that the process is to stop, the kernel will then dump its core. | COMMENT |
| LOW | crates/signals/src/lib.rs | 81 | /// This signal is generally used to start debugging. | COMMENT |
| LOW | crates/signals/src/lib.rs | 101 | /// | COMMENT |
| LOW | crates/signals/src/lib.rs | 181 | } | COMMENT |
| LOW | crates/signals/src/lib.rs | 241 | /// Parse the input as a windows control event. | COMMENT |
| LOW | crates/signals/src/lib.rs | 281 | COMMENT | |
| LOW | crates/bosion/src/lib.rs | 21 | /// [`gather_to`]: it writes to `bosion.rs` a pub struct named `Bosion`. | COMMENT |
| LOW | crates/bosion/src/lib.rs | 81 | (format!( | COMMENT |
| LOW | crates/bosion/src/lib.rs | 141 | {viz} struct {structname}; | COMMENT |
| LOW | crates/bosion/src/lib.rs | 161 | /// The crate features | COMMENT |
| LOW | crates/bosion/src/lib.rs | 201 | /// See the crate-level documentation for a guide. This function is a convenience wrapper around | COMMENT |
| LOW | crates/bosion/src/info.rs | 1 | use std::{ | COMMENT |
| LOW | crates/bosion/src/info.rs | 21 | pub struct Info { | COMMENT |
| LOW | crates/cli/tests/ignore.rs | 21 | const WATCH_TOKEN: &str = "updated"; | COMMENT |
| LOW | crates/cli/src/config.rs | 721 | } | COMMENT |
| LOW | crates/cli/src/args.rs | 21 | const OPTSET_FILTERING: &str = "Filtering"; | COMMENT |
| LOW | crates/cli/src/args.rs | 41 | /// | COMMENT |
| LOW | crates/cli/src/args.rs | 81 | /// $ watchexec -w src npm run build | COMMENT |
| LOW | crates/cli/src/args.rs | 121 | /// Generate a shell completions script | COMMENT |
| LOW | crates/cli/src/args/filtering.rs | 21 | pub struct FilteringArgs { | COMMENT |
| LOW | crates/cli/src/args/filtering.rs | 81 | )] | COMMENT |
| LOW | crates/cli/src/args/filtering.rs | 101 | /// watched project. This is contrasted with '--no-vcs-ignore', which disables loading of Git | COMMENT |
| LOW | crates/cli/src/args/filtering.rs | 121 | display_order = 144, | COMMENT |
| LOW | crates/cli/src/args/filtering.rs | 161 | /// | COMMENT |
| LOW | crates/cli/src/args/filtering.rs | 201 | /// Filename patterns to filter to | COMMENT |
| LOW | crates/cli/src/args/filtering.rs | 241 | /// | COMMENT |
| LOW | crates/cli/src/args/filtering.rs | 261 | /// | COMMENT |
| LOW | crates/cli/src/args/filtering.rs | 281 | /// | COMMENT |
| LOW | crates/cli/src/args/filtering.rs | 301 | /// 'any(.tags[] | select(.kind == "fs"); .simple == "create")' | COMMENT |
| LOW | crates/cli/src/args/events.rs | 41 | long, | COMMENT |
| LOW | crates/cli/src/args/events.rs | 61 | help_heading = OPTSET_EVENTS, | COMMENT |
| LOW | crates/cli/src/args/events.rs | 81 | /// Signal syntax is case-insensitive for short names (like "TERM", "USR2") and long names (like | COMMENT |
| LOW | crates/cli/src/args/events.rs | 101 | /// partially written. | COMMENT |
| LOW | crates/cli/src/args/events.rs | 121 | COMMENT | |
| LOW | crates/cli/src/args/events.rs | 161 | COMMENT | |
| LOW | crates/cli/src/args/events.rs | 201 | /// | COMMENT |
| LOW | crates/cli/src/args/events.rs | 221 | /// set of events Watchexec handles. Here's an example of a folder being created on Linux: | COMMENT |
| LOW | crates/cli/src/args/events.rs | 241 | /// "metadata": { | COMMENT |
| LOW | crates/cli/src/args/events.rs | 261 | /// * 'process', for events caused by processes: | COMMENT |
| LOW | crates/cli/src/args/events.rs | 281 | /// - $WATCHEXEC_CREATED_PATH is set when files/folders were created | COMMENT |
| LOW | crates/cli/src/args/command.rs | 41 | /// | COMMENT |
| LOW | crates/cli/src/args/command.rs | 61 | /// control flow, logic, or pipes. | COMMENT |
| LOW | crates/cli/src/args/command.rs | 101 | /// | COMMENT |
| LOW | crates/cli/src/args/command.rs | 141 | /// Configure how the process is wrapped | COMMENT |
| LOW | crates/cli/src/args/command.rs | 161 | )] | COMMENT |
| LOW | crates/cli/src/args/command.rs | 181 | long, | COMMENT |
| 74 more matches not shown… | ||||
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | crates/cli/README.md | 100 | $ watchexec -n -- echo ';' lorem ipsum | CODE |