AI Slop Code Risk Monitor

gocolly/colly

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

Elegant Scraper and Crawler Framework for Golang

2.9 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for gocolly/colly, a Go project with 25,571 GitHub stars. SynthScan examined 9,466 lines of code across 65 source files, recording 27 pattern matches distributed across 1 syntactic category. The legacy adjusted pattern signal is 2.9 (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.

2.9
Adjusted Signal
2.9
Raw Pattern Score
100%
Time Factor
2026-10-16
Last Push
25.6K
Stars
Go
Language
9.5K
Lines of Code
65
Files
27
Pattern Hits
2026-10-31
Scan Date
0.00
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 13.3/100 · LOW

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

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

PR Review Velocity Impact 13.3/100 · LOW

Which changes need focused human review? 27 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 0LOW 27

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 27 distinct pattern matches across 1 syntactic category. 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.

Over-Commented Block27 hits · 27 pts
SeverityFileLineSnippetContext
LOWxmlelement_test.go1// Copyright 2018 Adam TauberCOMMENT
LOWhtmlelement.go1// Copyright 2018 Adam TauberCOMMENT
LOWdomain_filter_test.go1// Copyright 2026 Adam TauberCOMMENT
LOWresponse.go1// Copyright 2018 Adam TauberCOMMENT
LOWrequest.go1// Copyright 2018 Adam TauberCOMMENT
LOWunmarshal.go1// Copyright 2018 Adam TauberCOMMENT
LOWxmlelement.go1// Copyright 2018 Adam TauberCOMMENT
LOWcolly.go1// Copyright 2018 Adam TauberCOMMENT
LOWcolly.go61 // MaxDepth limits the recursion depth of visited URLs.COMMENT
LOWcolly.go81 // request won't be stopped. DisallowedURLFilters willCOMMENT
LOWcolly.go101 // be sure all requests have been finished.COMMENT
LOWcolly.go161type XMLCallback func(*XMLElement)COMMENT
LOWcolly.go521// Appengine will replace the Collector's backend http.ClientCOMMENT
LOWcolly.go581COMMENT
LOWcontext_test.go1// Copyright 2018 Adam TauberCOMMENT
LOWcolly_test.go1// Copyright 2018 Adam TauberCOMMENT
LOWcolly_test.go2181 case <-done:COMMENT
LOWcontext.go1// Copyright 2018 Adam TauberCOMMENT
LOWhttp_backend.go1// Copyright 2018 Adam TauberCOMMENT
LOWunmarshal_test.go1// Copyright 2018 Adam TauberCOMMENT
LOWcmd/colly/colly.go1// Copyright 2018 Adam TauberCOMMENT
LOWproxy/proxy.go1// Copyright 2018 Adam TauberCOMMENT
LOWstorage/storage.go1// Copyright 2018 Adam TauberCOMMENT
LOWstorage/storage.go21 "strings"COMMENT
LOWdebug/logdebugger.go1// Copyright 2018 Adam TauberCOMMENT
LOWdebug/debug.go1// Copyright 2018 Adam TauberCOMMENT
LOWdebug/webdebugger.go1// Copyright 2018 Adam TauberCOMMENT