AI Slop Code Risk Monitor

faridrashidi/kaggle-solutions

SlopCodeMonitor badge for faridrashidi/kaggle-solutions Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

🏅 Collection of Kaggle Solutions and Ideas 🏅

0.8 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for faridrashidi/kaggle-solutions, a Astro project with 6,547 GitHub stars. SynthScan examined 31,568 lines of code across 18 source files, recording 19 pattern matches distributed across 5 syntactic categories. The legacy adjusted pattern signal is 0.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.

0.8
Adjusted Signal
0.8
Raw Pattern Score
100%
Time Factor
2026-10-06
Last Push
6.5K
Stars
Astro
Language
31.6K
Lines of Code
18
Files
19
Pattern Hits
2026-10-31
Scan Date
0.06
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 2.2/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 13 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 3.0/100 · LOW

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

PR Review Velocity Impact 4.0/100 · LOW

Which changes need focused human review? 19 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 1MEDIUM 1LOW 17

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 19 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.

Hyper-Verbose Identifiers9 hits · 9 pts
SeverityFileLineSnippetContext
LOWscripts/extract_solutions.py136def build_competition_image_mapping(driver):CODE
LOWscripts/extract_solutions.py175def get_competition_id_from_image_path(image_path):CODE
LOWscripts/extract_solutions.py191def build_competition_thumbnail_url(comp_id):CODE
LOWscripts/extract_solutions.py196def extract_competition_image_from_page_source(page_source):CODE
LOWscripts/extract_solutions.py225def download_competition_image(CODE
LOWscripts/extract_solutions.py281def extract_rank_from_writeup_url(href):CODE
LOWscripts/extract_solutions.py298def extract_rank_from_leaderboard_row(link):CODE
LOWscripts/extract_solutions.py311def extract_solutions_from_page_source(page_source, competition_slug):CODE
LOWscripts/extract_solutions.py370def convert_png_images_to_webp(image_dir):CODE
Excessive Try-Catch Wrapping5 hits · 5 pts
SeverityFileLineSnippetContext
LOWscripts/extract_solutions.py244 except Exception as e:CODE
LOWscripts/extract_solutions.py268 except Exception as e:CODE
LOWscripts/extract_solutions.py451 except Exception as e:CODE
LOWscripts/extract_solutions.py521 except Exception:CODE
LOWscripts/extract_competitions.py34 except Exception:CODE
Empty Error Handlers1 hit · 5 pts
SeverityFileLineSnippetContext
HIGHscripts/extract_solutions.py521except Exception:CODE
Deep Nesting3 hits · 3 pts
SeverityFileLineSnippetContext
LOWscripts/extract_solutions.py136CODE
LOWscripts/extract_solutions.py225CODE
LOWscripts/extract_solutions.py463CODE
Modern AI Meta-Vocabulary1 hit · 2 pts
SeverityFileLineSnippetContext
MEDIUMdata/competitions.yml83 link: "https://www.kaggle.com/c/biohub-cell-tracking-during-development/writeups/10th-place-solution-grandmasterCODE