AI Slop Code Risk Monitor

Canop/broot

SlopCodeMonitor badge for Canop/broot Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

A new way to see and navigate directory trees

1.8 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for Canop/broot, a Rust project with 13,120 GitHub stars. SynthScan examined 49,875 lines of code across 295 source files, recording 38 pattern matches distributed across 7 syntactic categories. The legacy adjusted pattern signal is 1.8 (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.

1.8
Adjusted Signal
1.8
Raw Pattern Score
100%
Time Factor
2026-10-20
Last Push
13.1K
Stars
Rust
Language
49.9K
Lines of Code
295
Files
38
Pattern Hits
2026-10-31
Scan Date
0.02
HC Hit Rate

Risk Review · Payload v1

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

Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.

Cognitive Ownership Risk 6.7/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 2.1/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 8.2/100 · LOW

Which changes need focused human review? 38 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 2HIGH 5MEDIUM 2LOW 29

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 38 distinct pattern matches across 7 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.

AI Response Leakage4 hits · 30 pts
SeverityFileLineSnippetContext
HIGHwebsite/src/conf_file.md387# In this example we use placeholders for the input and output filesCOMMENT
HIGHwebsite/src/conf_file.md397# In this example we use placeholders for the input and output filesCOMMENT
HIGHwebsite/src/conf_file.md441# In this example, the command refers to neither the input nor the output,COMMENT
HIGHwebsite/src/conf_file.md452# In this example, the command refers to neither the input nor the output,COMMENT
Over-Commented Block27 hits · 27 pts
SeverityFileLineSnippetContext
LOWCargo.toml121# clap-help = { path = "../clap-help" }COMMENT
LOWbuild-scripts/build-target.sh1#!/usr/bin/env bashCOMMENT
LOWbuild-scripts/build.sh1#!/usr/bin/env bashCOMMENT
LOWbuild-scripts/_targets.sh1# _targets.sh — the list of release targets and the per-target build engine,COMMENT
LOWbuild-scripts/release.sh1#!/usr/bin/env bashCOMMENT
LOWbuild-scripts/deploy.sh1#!/usr/bin/env bashCOMMENT
LOWbuild-scripts/build-all-targets.sh1#!/usr/bin/env bashCOMMENT
LOWsrc/launchable.rs41};COMMENT
LOWsrc/task_sync.rs61 /// provide an observer which can be used for periodicCOMMENT
LOWsrc/tree_build/build_report.rs1/// Information from the builder about theCOMMENT
LOWsrc/shell_install/powershell.rs1//! The goal of this mod is to ensure the launcher shell functionCOMMENT
LOWsrc/shell_install/bash.rs1//! The goal of this mod is to ensure the launcher shell functionCOMMENT
LOWsrc/shell_install/fish.rs1//! The goal of this mod is to ensure the launcher shell functionCOMMENT
LOWsrc/shell_install/nushell.rs1//! The goal of this mod is to ensure the launcher shell functionCOMMENT
LOWsrc/content_search/needle.rs201 pos += 1;COMMENT
LOWsrc/cli/args.rs181COMMENT
LOWsrc/verb/coarity.rs1/// Describe whether a command should be executed once per selection orCOMMENT
LOWsrc/verb/verb.rs21///COMMENT
LOWsrc/verb/external_execution.rs21#[derive(Debug, Clone)]COMMENT
LOWsrc/verb/verb_invocation.rs81 /// "mv!a b" -> name: "mv", args: "a b", bangCOMMENT
LOWsrc/sixel/sixel_renderer.rs141 /// `Some(terminal default background)` in Konsole (KONSOLE_VERSION set),COMMENT
LOWsrc/sixel/detect_support.rs61 Some((width, height))COMMENT
LOWsrc/kitty/image_renderer.rs61///COMMENT
LOWsrc/kitty/detect_support.rs21}COMMENT
LOWsrc/pattern/composite_pattern.rs181COMMENT
LOWsrc/graphics/mod.rs41COMMENT
LOWsrc/git/ignore.rs261 if let Some(parent) = dir.parent() {COMMENT
Hallucination Indicators2 hits · 20 pts
SeverityFileLineSnippetContext
CRITICALsrc/display/displayable_tree.rs334 let name_match = self.tree.options.pattern.pattern.find_string(&line.subpath);CODE
CRITICALsrc/display/displayable_tree.rs359 let name_match = self.tree.options.pattern.pattern.find_string(&line.name);CODE
Self-Referential Comments2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMbuild-scripts/_common.sh7# This file is not meant to be run directly.COMMENT
MEDIUMbuild-scripts/_common.sh152# Create the release tag on HEAD and push it, unless origin already has it there.COMMENT
Synthetic Comment Markers1 hit · 5 pts
SeverityFileLineSnippetContext
HIGHsrc/tree/tree_options.rs35 pub respect_git_ignore: bool, // hide files as requested by .gitignore ?CODE
Example Usage Blocks1 hit · 2 pts
SeverityFileLineSnippetContext
LOWbuild-scripts/build-target.sh7# Usage:COMMENT
Fake / Example Data1 hit · 1 pts
SeverityFileLineSnippetContext
LOWwebsite/src/js/highlight.min.js310;const e=["a","abbr","address","article","aside","audio","b","blockquote","body","button","canvas","caption","cite","codCODE