Repository Analysis

clap-rs/clap

A full featured, fast Command Line Argument Parser for Rust

6.3 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of clap-rs/clap, a Rust project with 16,570 GitHub stars. SynthScan v2.0 examined 97,807 lines of code across 468 source files, recording 793 pattern matches distributed across 6 syntactic categories. The overall adjusted score of 6.3 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).

6.3
Adjusted Score
6.3
Raw Score
100%
Time Factor
2026-07-10
Last Push
16.6K
Stars
Rust
Language
97.8K
Lines of Code
468
Files
793
Pattern Hits
2026-07-14
Scan Date
0.01
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 4MEDIUM 0LOW 789

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 793 distinct pattern matches across 6 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 Block772 hits · 574 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# The confidence threshold for detecting a license from license text.COMMENT
LOWdeny.toml121expression = "MIT AND ISC AND OpenSSL"COMMENT
LOWdeny.toml141registries = [COMMENT
LOWdeny.toml161# `default` on a crate-by-crate basis if desired.COMMENT
LOWdeny.toml181# List of features to allow/denyCOMMENT
LOWdeny.toml201# this is set there is no point setting `deny`COMMENT
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 Some(current) = current.to_str() else {COMMENT
LOWclap_complete/src/engine/custom.rs61COMMENT
LOWclap_complete/src/engine/custom.rs81 f.write_str(type_name::<Self>())COMMENT
LOWclap_complete/src/engine/custom.rs121}COMMENT
LOWclap_complete/src/engine/custom.rs161 fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> std::fmt::Result {COMMENT
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
712 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
LOWtests/derive/doc_comments_help.rs51 /// Lorem ipsumCOMMENT
LOWtests/derive/doc_comments_help.rs53 #[command(name = "lorem-ipsum", about = "Dolor sit amet")]COMMENT
LOWtests/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 [aliaseSTRING
HIGHtests/ui/help_flag_stdout.toml0usage: stdio-fixture[exe] [options] [name] [env] [command] commands: more test subcommand with one visible alias [aliaseSTRING
HIGHtests/ui/h_flag_stdout.toml0usage: stdio-fixture[exe] [options] [name] [env] [command] commands: more test subcommand with one visible alias [aliaseSTRING
HIGHtests/ui/arg_required_else_help_stderr.toml0usage: stdio-fixture[exe] [options] [name] [env] [command] commands: more test subcommand with one visible alias [aliaseSTRING
AI Slop Vocabulary1 hit · 2 pts
SeverityFileLineSnippetContext
LOWsrc/_derive/mod.rs345//! #[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