AI Slop Code RIsk Monitor

watchexec/watchexec

Executes commands in response to file modifications

4.3 Low pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for watchexec/watchexec, a Rust project with 7,228 GitHub stars. SynthScan examined 34,470 lines of code across 198 source files, recording 148 pattern matches distributed across 2 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.

4.3
Adjusted Signal
4.3
Raw Pattern Score
100%
Time Factor
2026-10-09
Last Push
7.2K
Stars
Rust
Language
34.5K
Lines of Code
198
Files
148
Pattern Hits
2026-10-12
Scan Date
0.00
HC Hit Rate

Risk Review · v3

Use each vector to guide manual verification of the underlying findings.

Cognitive Ownership Risk 19.2/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 147 finding(s).

Hallucinated Dependency & Supply Chain Risk 0.1/100 · LOW

Are imports declared and package/API names verified? 1 finding(s).

Agent Over-Engineering Ratio 0.0/100 · LOW

Are wrappers, guards, and repeated structures necessary? 0 finding(s).

PR Review Velocity Impact 19.3/100 · LOW

Which changes need focused human review? 148 finding(s).

What These Metrics Mean

Adjusted Signal
Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score
Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor
A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits
Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate
High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files
Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

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.

Severity Breakdown

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.

CRITICAL 0HIGH 0MEDIUM 0LOW 148

Directory Score Breakdown

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.

Pattern Findings

The scanner identified 148 distinct pattern matches across 2 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.

Over-Commented Block147 hits · 147 pts
SeverityFileLineSnippetContext
LOWcrates/filterer/globset/CHANGELOG.md1# ChangelogCOMMENT
LOWcrates/filterer/globset/src/lib.rs61 ///COMMENT
LOWcrates/filterer/ignore/CHANGELOG.md1# ChangelogCOMMENT
LOWcrates/filterer/ignore/src/lib.rs1//! A Watchexec Filterer implementation for ignore files.COMMENT
LOWcrates/filterer/ignore/src/lib.rs21use watchexec_events::{Event, FileType, Priority};COMMENT
LOWcrates/project-origins/src/lib.rs1//! Resolve project origins and kinds from a path.COMMENT
LOWcrates/project-origins/src/lib.rs21use futures::StreamExt;COMMENT
LOWcrates/project-origins/src/lib.rs41COMMENT
LOWcrates/project-origins/src/lib.rs61 /// Detects when a `.hg` folder is present, or any of the files `.hgignore` or `.hgtags`.COMMENT
LOWcrates/project-origins/src/lib.rs81 /// Soft: the [C programming language](https://en.wikipedia.org/wiki/C_(programming_language)).COMMENT
LOWcrates/project-origins/src/lib.rs101 /// Soft: the [Go](https://golang.net) language.COMMENT
LOWcrates/project-origins/src/lib.rs121 /// Detects when a `project.clj` file is present.COMMENT
LOWcrates/signals/src/lib.rs1#![doc = include_str!("../README.md")]COMMENT
LOWcrates/signals/src/lib.rs21/// On Windows, only some signals are supported, as described. Others will be ignored.COMMENT
LOWcrates/signals/src/lib.rs41 /// Despite its nominal purpose, on Unix this signal is often used to reload configuration files.COMMENT
LOWcrates/signals/src/lib.rs61 /// Indicate that the process is to stop, the kernel will then dump its core.COMMENT
LOWcrates/signals/src/lib.rs81 /// This signal is generally used to start debugging.COMMENT
LOWcrates/signals/src/lib.rs101 ///COMMENT
LOWcrates/signals/src/lib.rs121 /// ignored rather than hard-erroring.COMMENT
LOWcrates/signals/src/lib.rs221}COMMENT
LOWcrates/signals/src/lib.rs281 }COMMENT
LOWcrates/bosion/src/lib.rs21/// [`gather_to`]: it writes to `bosion.rs` a pub struct named `Bosion`.COMMENT
LOWcrates/bosion/src/lib.rs81 (format!(COMMENT
LOWcrates/bosion/src/lib.rs141 {viz} struct {structname};COMMENT
LOWcrates/bosion/src/lib.rs161 /// The crate featuresCOMMENT
LOWcrates/bosion/src/lib.rs201/// See the crate-level documentation for a guide. This function is a convenience wrapper aroundCOMMENT
LOWcrates/bosion/src/info.rs1use std::{COMMENT
LOWcrates/bosion/src/info.rs21pub struct Info {COMMENT
LOWcrates/cli/tests/ignore.rs21const WATCH_TOKEN: &str = "updated";COMMENT
LOWcrates/cli/src/config.rs761const fn on_busy_signal(signal: Option<Signal>, stop_signal: Option<Signal>) -> Signal {COMMENT
LOWcrates/cli/src/args.rs21const OPTSET_FILTERING: &str = "Filtering";COMMENT
LOWcrates/cli/src/args.rs41///COMMENT
LOWcrates/cli/src/args.rs81 /// $ watchexec -w src npm run buildCOMMENT
LOWcrates/cli/src/args.rs121 /// Generate a shell completions scriptCOMMENT
LOWcrates/cli/src/args/filtering.rs21pub struct FilteringArgs {COMMENT
LOWcrates/cli/src/args/filtering.rs81 )]COMMENT
LOWcrates/cli/src/args/filtering.rs101 /// watched project. This is contrasted with '--no-vcs-ignore', which disables loading of GitCOMMENT
LOWcrates/cli/src/args/filtering.rs121 display_order = 144,COMMENT
LOWcrates/cli/src/args/filtering.rs161 ///COMMENT
LOWcrates/cli/src/args/filtering.rs201 /// Filename patterns to filter toCOMMENT
LOWcrates/cli/src/args/filtering.rs241 ///COMMENT
LOWcrates/cli/src/args/filtering.rs261 ///COMMENT
LOWcrates/cli/src/args/filtering.rs281 ///COMMENT
LOWcrates/cli/src/args/filtering.rs301 /// 'any(.tags[] | select(.kind == "fs"); .simple == "create")'COMMENT
LOWcrates/cli/src/args/events.rs41 #[arg(COMMENT
LOWcrates/cli/src/args/events.rs61 short,COMMENT
LOWcrates/cli/src/args/events.rs81 /// This option can be specified multiple times to map multiple signals.COMMENT
LOWcrates/cli/src/args/events.rs101 /// too often. Additionally, it's not infrequent that file writes are not atomic, and each writeCOMMENT
LOWcrates/cli/src/args/events.rs121 )]COMMENT
LOWcrates/cli/src/args/events.rs201 /// Watchexec can emit event information when running a command, which can be used by the childCOMMENT
LOWcrates/cli/src/args/events.rs221 ///COMMENT
LOWcrates/cli/src/args/events.rs241 /// }COMMENT
LOWcrates/cli/src/args/events.rs261 /// * 'keyboard', along with:COMMENT
LOWcrates/cli/src/args/events.rs281 /// and so should be prepended to each path to obtain the full/real path. Then:COMMENT
LOWcrates/cli/src/args/command.rs41 ///COMMENT
LOWcrates/cli/src/args/command.rs61 /// control flow, logic, or pipes.COMMENT
LOWcrates/cli/src/args/command.rs101 ///COMMENT
LOWcrates/cli/src/args/command.rs141 /// Configure how the process is wrappedCOMMENT
LOWcrates/cli/src/args/command.rs161 value_name = "MODE",COMMENT
LOWcrates/cli/src/args/command.rs181 /// events. For portability the unix signals "SIGKILL", "SIGINT", "SIGTERM", and "SIGHUP" areCOMMENT
87 more matches not shown…
Fake / Example Data1 hit · 1 pts
SeverityFileLineSnippetContext
LOWcrates/cli/README.md100 $ watchexec -n -- echo ';' lorem ipsumCODE