AI Slop Code RIsk Monitor

autowarefoundation/autoware

Autoware - the world's leading open-source software project for autonomous driving

9.5 Moderate pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for autowarefoundation/autoware, a Dockerfile project with 12,148 GitHub stars. SynthScan examined 9,431 lines of code across 181 source files, recording 38 pattern matches distributed across 7 syntactic categories. The legacy adjusted pattern signal is 9.5 (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.

9.5
Adjusted Signal
9.5
Raw Pattern Score
100%
Time Factor
2026-09-29
Last Push
12.1K
Stars
Dockerfile
Language
9.4K
Lines of Code
181
Files
38
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 35.1/100 · MEDIUM

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

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

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

Agent Over-Engineering Ratio 5.2/100 · LOW

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

PR Review Velocity Impact 38.0/100 · MEDIUM

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 0HIGH 0MEDIUM 26LOW 12

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.

Self-Referential Comments23 hits · 69 pts
SeverityFileLineSnippetContext
MEDIUM.pre-commit-config-optional.yaml1# This file is automatically synced from:COMMENT
MEDIUM.pre-commit-config.yaml1# This file is automatically synced from:COMMENT
MEDIUM.yamllint.yaml1# This file is automatically synced from:COMMENT
MEDIUM.prettierrc.yaml1# This file is automatically synced from:COMMENT
MEDIUMsetup.cfg1# This file is automatically synced from:COMMENT
MEDIUM.markdownlint.yaml1# This file is automatically synced from:COMMENT
MEDIUM.pre-commit-config-ansible.yaml1# This file is automatically synced from:COMMENT
MEDIUMCPPLINT.cfg1# This file is automatically synced from:COMMENT
MEDIUM.github/dependabot.yaml1# This file is automatically synced from:COMMENT
MEDIUM.github/stale.yml1# This file is automatically synced from:COMMENT
MEDIUM.github/workflows/spell-check-differential.yaml1# This file is automatically synced from:COMMENT
MEDIUM.github/workflows/sync-files.yaml1# This file is automatically synced from:COMMENT
MEDIUM.github/workflows/github-release.yaml1# This file is automatically synced from:COMMENT
MEDIUM.github/workflows/backport.yaml1# This file is automatically synced from:COMMENT
MEDIUM.github/workflows/pre-commit-optional.yaml1# This file is automatically synced from:COMMENT
MEDIUM.github/workflows/pre-commit.yaml1# This file is automatically synced from:COMMENT
MEDIUM.github/workflows/comment-on-pr.yaml1# This file is automatically synced from:COMMENT
MEDIUM.github/workflows/pre-commit-ansible.yaml1# This file is automatically synced from:COMMENT
MEDIUM.github/workflows/semantic-pull-request.yaml1# This file is automatically synced from:COMMENT
MEDIUM.github/workflows/spell-check-daily.yaml1# This file is automatically synced from:COMMENT
MEDIUM.github/ISSUE_TEMPLATE/bug.yaml1# This file is automatically synced from:COMMENT
MEDIUM.github/ISSUE_TEMPLATE/task.yaml1# This file is automatically synced from:COMMENT
MEDIUM.github/ISSUE_TEMPLATE/config.yml1# This file is automatically synced from:COMMENT
Over-Commented Block8 hits · 8 pts
SeverityFileLineSnippetContext
LOWansible/roles/nvidia_container_toolkit/README.md41# At this point, a working setup can be tested by running a base CUDA container:COMMENT
LOWansible/roles/nvidia_container_toolkit/README.md61# +-----------------------------------------+------------------------+----------------------+COMMENT
LOWansible/roles/spconv/defaults/main.yaml1spconv_is_jetson: falseCOMMENT
LOWansible/roles/cuda/defaults/main.yaml1cuda_install_drivers: trueCOMMENT
LOWansible/roles/version_lock/tasks/reconcile.yaml1# Walk every installed package that the dated ROS snapshot serves at aCOMMENT
LOWansible/roles/version_lock/defaults/main.yaml1version_lock_arch_map:COMMENT
LOW.github/workflows/health-check-reusable.yaml1# Builds `universe-devel` on independent matrix routes, one perCOMMENT
LOW.github/workflows/docker-build.yaml1# Reusable workflow that builds and pushes one docker bake group viaCOMMENT
Decorative Section Separators2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMansible/roles/nvidia_container_toolkit/README.md44# ==========COMMENT
MEDIUMansible/roles/nvidia_container_toolkit/README.md46# ==========COMMENT
Hyper-Verbose Identifiers2 hits · 2 pts
SeverityFileLineSnippetContext
LOWansible/scripts/emit_nvidia_pins.py38def _nvidia_index_texts_from_lists_dir(lists_dir):CODE
LOWansible/scripts/emit_nvidia_pins.py60def _nvidia_index_texts_from_apt():CODE
Excessive Try-Catch Wrapping1 hit · 2 pts
SeverityFileLineSnippetContext
MEDIUMansible/scripts/update_base_image_digest.py59 print(f"Error: {exc}", file=sys.stderr)CODE
Redundant / Tautological Comments1 hit · 2 pts
SeverityFileLineSnippetContext
LOW.github/workflows/backport.yaml53 # Loop through the array of PR numbersCOMMENT
Deep Nesting1 hit · 1 pts
SeverityFileLineSnippetContext
LOWansible/scripts/emit_nvidia_pins.py22CODE