AI Slop Code RIsk Monitor

rasbt/deeplearning-models

A collection of various deep learning architectures, models, and tips

9.4 Moderate pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for rasbt/deeplearning-models, a Jupyter Notebook project with 17,611 GitHub stars. SynthScan examined 2,776 lines of code across 20 source files, recording 24 pattern matches distributed across 5 syntactic categories. The legacy adjusted pattern signal is 9.4 (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.4
Adjusted Signal
9.4
Raw Pattern Score
100%
Time Factor
2026-09-26
Last Push
17.6K
Stars
Jupyter Notebook
Language
2.8K
Lines of Code
20
Files
24
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 23.7/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 18.0/100 · LOW

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

Agent Over-Engineering Ratio 10.2/100 · LOW

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

PR Review Velocity Impact 37.4/100 · MEDIUM

Which changes need focused human review? 24 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

Run additional scans to build a history of the legacy pattern signal. Score changes are not a measure of AI adoption or code quality.

No multi-scan history yet — run the scanner again to build trend data.

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 1LOW 23

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

Unused Imports11 hits · 11 pts
SeverityFileLineSnippetContext
LOWpytorch_ipynb/helper_data.py2CODE
LOWpytorch_ipynb/helper_train.py8CODE
LOWpytorch_ipynb/helper_train.py9CODE
LOWpytorch_ipynb/helper_train.py10CODE
LOWpytorch_ipynb/helper_train.py11CODE
LOWpytorch_ipynb/helper_train.py12CODE
LOW…torch_ipynb/mechanics/deterministic_benchmark_utils.py1CODE
LOW…torch_ipynb/mechanics/deterministic_benchmark_utils.py2CODE
LOW…torch_ipynb/mechanics/deterministic_benchmark_utils.py7CODE
LOW…torch_ipynb/mechanics/deterministic_benchmark_utils.py8CODE
LOW…torch_ipynb/mechanics/deterministic_benchmark_utils.py9CODE
Deep Nesting6 hits · 6 pts
SeverityFileLineSnippetContext
LOWpytorch_ipynb/helper_train.py15CODE
LOWpytorch_ipynb/helper_train.py85CODE
LOWpytorch_ipynb/helper_plotting.py120CODE
LOW…torch_ipynb/transformer/distilbert-benchmark/shared.py40CODE
LOWtensorflow1_ipynb/helper.py198CODE
LOWtensorflow1_ipynb/helper.py205CODE
Hyper-Verbose Identifiers4 hits · 4 pts
SeverityFileLineSnippetContext
LOWpytorch_ipynb/helper.py6def quickdraw_npy_to_imagefile(inpath, outpath, filetype='png', subset=None):CODE
LOWpytorch_ipynb/viz/cnns/cats-and-dogs/datautils.py45def create_cats_and_dogs_dataloaders(batch_size, data_transforms, train_path, valid_path, test_path):CODE
LOWtensorflow1_ipynb/helper.py24def download_and_extract_cifar(target_dir,CODE
LOWtensorflow1_ipynb/helper.py205 def remove_incomplete_existing(path_prefix, expect_files):CODE
Self-Referential Comments1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUM…mplates/pytorch_lightning/tune_classification_basic.py96 # Defining the forward method is only necessaryCOMMENT
AI Structural Patterns2 hits · 2 pts
SeverityFileLineSnippetContext
LOWpytorch_ipynb/helper_plotting.py120CODE
LOW…torch_ipynb/mechanics/deterministic_benchmark_utils.py62CODE