AI Slop Code RIsk Monitor

clap-rs/clap

A full featured, fast Command Line Argument Parser for Rust

6.2 Moderate pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for clap-rs/clap, a Rust project with 16,765 GitHub stars. SynthScan examined 99,522 lines of code across 477 source files, recording 796 pattern matches distributed across 6 syntactic categories. The legacy adjusted pattern signal is 6.2 (Moderate 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.

6.2
Adjusted Signal
6.2
Raw Pattern Score
100%
Time Factor
2026-10-06
Last Push
16.8K
Stars
Rust
Language
99.5K
Lines of Code
477
Files
796
Pattern Hits
2026-10-12
Scan Date
0.01
HC Hit Rate

Risk Review · v3

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

Cognitive Ownership Risk 25.3/100 · MEDIUM

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

Hallucinated Dependency & Supply Chain Risk 1.1/100 · LOW

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

Agent Over-Engineering Ratio 1.0/100 · LOW

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

PR Review Velocity Impact 33.6/100 · MEDIUM

Which changes need focused human review? 796 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 4MEDIUM 0LOW 792

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 796 distinct pattern matches across 6 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 Block775 hits · 578 pts
SeverityFileLineSnippetContext
LOWdeny.toml1# Note that all fields that take a lint level have these possible values:COMMENT
LOWdeny.toml21 # The triple can be any string, but only the target triples built in toCOMMENT
LOWdeny.toml41# If true, metadata will be collected with `--no-default-features`. The sameCOMMENT
LOWdeny.toml61# The path where the advisory databases are cloned/fetched intoCOMMENT
LOWdeny.toml101]COMMENT
LOWdeny.toml121# The SPDX expression for the license requirements of the crateCOMMENT
LOWdeny.toml141# not have its license(s) checkedCOMMENT
LOWdeny.toml161# the workspace that is being checked. This can be overridden by allowing/denyingCOMMENT
LOWdeny.toml181COMMENT
LOWdeny.toml201# If true, the allowed features must exactly match the enabled feature set. IfCOMMENT
LOWdeny.toml221# https://embarkstudios.github.io/cargo-deny/checks/sources/cfg.htmlCOMMENT
LOWclap_derive/src/lib.rs1// Copyright 2018 Guillaume Pinot (@TeXitoi) <texitoi@texitoi.eu>,COMMENT
LOWclap_derive/src/item.rs1// Copyright 2018 Guillaume Pinot (@TeXitoi) <texitoi@texitoi.eu>,COMMENT
LOWclap_derive/src/utils/doc_comments.rs1//! The preprocessing we apply to doc comments.COMMENT
LOWclap_derive/src/derives/into_app.rs1// Copyright 2018 Guillaume Pinot (@TeXitoi) <texitoi@texitoi.eu>,COMMENT
LOWclap_derive/src/derives/mod.rs1// Copyright 2018 Guillaume Pinot (@TeXitoi) <texitoi@texitoi.eu>,COMMENT
LOWclap_derive/src/derives/subcommand.rs1// Copyright 2018 Guillaume Pinot (@TeXitoi) <texitoi@texitoi.eu>,COMMENT
LOWclap_derive/src/derives/args.rs1// Copyright 2018 Guillaume Pinot (@TeXitoi) <texitoi@texitoi.eu>,COMMENT
LOWclap_derive/src/derives/parser.rs1// Copyright 2018 Guillaume Pinot (@TeXitoi) <texitoi@texitoi.eu>,COMMENT
LOWclap_complete/examples/completion-derive.rs1//! How to use value hints and generate shell completions.COMMENT
LOWclap_complete/examples/completion.rs1//! Example to test arguments with different `ValueHint` values.COMMENT
LOWclap_complete/src/lib.rs1// Copyright ⓒ 2015-2018 Kevin B. KnappCOMMENT
LOWclap_complete/src/lib.rs21//! use std::io;COMMENT
LOWclap_complete/src/lib.rs41//! let mut cmd = build_cli();COMMENT
LOWclap_complete/src/engine/custom.rs21/// let mut completions = vec![];COMMENT
LOWclap_complete/src/engine/custom.rs61 }COMMENT
LOWclap_complete/src/engine/custom.rs121 }COMMENT
LOWclap_complete/src/engine/custom.rs241COMMENT
LOWclap_complete/src/aot/mod.rs1//! Prebuilt completionsCOMMENT
LOWclap_complete/src/aot/mod.rs21//!COMMENT
LOWclap_complete/src/aot/shells/zsh.rs61 }COMMENT
LOWclap_complete/src/aot/shells/zsh.rs81// (( $+functions[_rustup_commands] )) ||COMMENT
LOWclap_complete/src/aot/shells/zsh.rs141}COMMENT
LOWclap_complete/src/aot/shells/zsh.rs181COMMENT
LOWclap_complete/src/aot/shells/zsh.rs201// ([name])COMMENT
LOWclap_complete/src/aot/shells/zsh.rs301 NoneCOMMENT
LOWclap_complete/src/aot/shells/zsh.rs601}COMMENT
LOWclap_complete/src/aot/shells/shell.rs101 /// Parse a shell from a path to the executable for the shellCOMMENT
LOWclap_complete/src/aot/shells/shell.rs121 ///COMMENT
LOWclap_complete/src/aot/shells/fish.rs81 // example :COMMENT
LOWclap_complete/src/aot/generator/mod.rs21 /// # ExamplesCOMMENT
LOWclap_complete/src/aot/generator/mod.rs41 ///COMMENT
LOWclap_complete/src/aot/generator/mod.rs61 /// # }COMMENT
LOWclap_complete/src/aot/generator/mod.rs81 /// use std::{io::{Error, Write}, fmt::write};COMMENT
LOWclap_complete/src/aot/generator/mod.rs101 Ok(())COMMENT
LOWclap_complete/src/aot/generator/mod.rs121/// First, it helps if we separate out our `Command` definition into a separate file. Whether youCOMMENT
LOWclap_complete/src/aot/generator/mod.rs141/// In our regular code, we can simply call this `build_cli()` function, then callCOMMENT
LOWclap_complete/src/aot/generator/mod.rs161/// clap = "*"COMMENT
LOWclap_complete/src/aot/generator/mod.rs181///COMMENT
LOWclap_complete/src/aot/generator/mod.rs201/// **NOTE:** Please look at the individual [shells][crate::shells]COMMENT
LOWclap_complete/src/aot/generator/mod.rs261/// we can let users generate a completion script using a command:COMMENT
LOWclap_lex/src/lib.rs1//! Minimal, flexible command-line parserCOMMENT
LOWclap_lex/src/lib.rs21//!COMMENT
LOWclap_lex/src/lib.rs41//! }COMMENT
LOWclap_lex/src/lib.rs61//! while let Some(arg) = raw.next(&mut cursor) {COMMENT
LOWclap_lex/src/lib.rs81//! }COMMENT
LOWclap_lex/src/lib.rs101//! } else {COMMENT
LOWclap_lex/src/lib.rs141 ///COMMENT
LOWclap_lex/src/lib.rs161 /// ```rust,no_runCOMMENT
LOWclap_lex/src/lib.rs361COMMENT
715 more matches not shown…
Fake / Example Data14 hits · 20 pts
SeverityFileLineSnippetContext
LOWtests/derive/doc_comments_help.rs24 /// Lorem ipsumCOMMENT
LOWtests/derive/doc_comments_help.rs35Lorem ipsumCODE
LOW⚡tests/derive/doc_comments_help.rs51 /// Lorem ipsumCOMMENT
LOW⚡tests/derive/doc_comments_help.rs53 #[command(name = "lorem-ipsum", about = "Dolor sit amet")]COMMENT
LOW⚡tests/derive/doc_comments_help.rs62Dolor sit ametCODE
LOWtests/derive/doc_comments_help.rs98 /// Lorem ipsumclapCOMMENT
LOWtests/derive/doc_comments_help.rs100 #[command(name = "lorem-ipsum", about = "Dolor sit amet")]COMMENT
LOWtests/derive/doc_comments_help.rs117Dolor sit ametCODE
LOWtests/derive/doc_comments_help.rs128Dolor sit ametCODE
LOWtests/derive/doc_comments_help.rs149 /// Lorem ipsumclapCOMMENT
LOWtests/derive/doc_comments_help.rs151 #[command(name = "lorem-ipsum", about = "Dolor sit amet")]COMMENT
LOWtests/derive/doc_comments_help.rs172Dolor sit ametCODE
LOWtests/derive/doc_comments_help.rs457 /// Lorem ipsumCOMMENT
LOWtests/derive/doc_comments_help.rs468Lorem ipsumCODE
Cross-File Repetition4 hits · 20 pts
SeverityFileLineSnippetContext
HIGHtests/ui/help_cmd_stdout.toml0usage: stdio-fixture[exe] [options] [name] [env] [command] commands: more test subcommand with one visible alias [alias:STRING
HIGHtests/ui/help_flag_stdout.toml0usage: stdio-fixture[exe] [options] [name] [env] [command] commands: more test subcommand with one visible alias [alias:STRING
HIGHtests/ui/h_flag_stdout.toml0usage: stdio-fixture[exe] [options] [name] [env] [command] commands: more test subcommand with one visible alias [alias:STRING
HIGHtests/ui/arg_required_else_help_stderr.toml0usage: stdio-fixture[exe] [options] [name] [env] [command] commands: more test subcommand with one visible alias [alias:STRING
AI Slop Vocabulary1 hit · 2 pts
SeverityFileLineSnippetContext
LOWsrc/_derive/mod.rs359//! #[command(about = "I am a program and I work, just pass `-h`", long_about = None)]COMMENT
Unused Imports1 hit · 1 pts
SeverityFileLineSnippetContext
LOW.github/workflows/release-notes.py4CODE
Deep Nesting1 hit · 1 pts
SeverityFileLineSnippetContext
LOW.github/workflows/release-notes.py12CODE