AI Slop Code Risk Monitor

projectdiscovery/katana

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

A next-generation crawling and spidering framework.

1.0 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for projectdiscovery/katana, a Go project with 17,777 GitHub stars. SynthScan examined 52,235 lines of code across 227 source files, recording 35 pattern matches distributed across 6 syntactic categories. The legacy adjusted pattern signal is 1.0 (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.0
Adjusted Signal
1.0
Raw Pattern Score
100%
Time Factor
2026-10-29
Last Push
17.8K
Stars
Go
Language
52.2K
Lines of Code
227
Files
35
Pattern Hits
2026-10-31
Scan Date
0.01
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 1.9/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 3.2/100 · LOW

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

Agent Over-Engineering Ratio 0.1/100 · LOW

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

PR Review Velocity Impact 5.0/100 · LOW

Which changes need focused human review? 35 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 1HIGH 2MEDIUM 0LOW 32

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

Over-Commented Block17 hits · 17 pts
SeverityFileLineSnippetContext
LOWinternal/testutils/authlab/lab.go1// Package authlab provides a self-hosted mini web app used to exerciseCOMMENT
LOWpkg/types/options.go141 HeadlessOptionalArguments goflags.StringSliceCOMMENT
LOWpkg/types/options.go181 // Resolvers contains custom resolversCOMMENT
LOWpkg/types/options.go241 AIReplay stringCOMMENT
LOWpkg/types/crawler_options.go41 // Options contains the user specified configuration optionsCOMMENT
LOWpkg/utils/formfill.go221COMMENT
LOWpkg/utils/filters/filters.go1package filtersCOMMENT
LOWpkg/knowledgebase/extractor.go1// Package knowledgebase defines the Extractor interface implemented byCOMMENT
LOWpkg/knowledgebase/extractors/endpoints/endpoints.go1// Package endpoints is a knowledgebase.Extractor that classifies a crawledCOMMENT
LOWpkg/engine/parser/parser_test.go181 // The test contains an inline string - ./test/html/misc/string/dot-slash-prefix.foundCOMMENT
LOWpkg/engine/parser/parser_test.go321 // <meta charset="utf-8">COMMENT
LOWpkg/engine/parser/parser_test.go401 // bodyMetaContentTagParser(resp, func(resp navigation.Request) {COMMENT
LOWpkg/engine/parser/parser.go761 return falseCOMMENT
LOWpkg/engine/headless/js/page-init.js1// This script initializes the page and hooks up event listenersCOMMENT
LOWpkg/engine/headless/crawler/hooks.go1package crawlerCOMMENT
LOWpkg/engine/headless/crawler/hooks.go21// The supplied *browser.BrowserPage embeds *rod.Page (page.Page) for callersCOMMENT
LOWpkg/engine/hybrid/hooks.go21// -timeout deadline: for BeforeNavigate it is the navigation's own context;COMMENT
Fake / Example Data13 hits · 14 pts
SeverityFileLineSnippetContext
LOWpkg/utils/formfill.go30 Placeholder string `yaml:"placeholder"`CODE
LOWpkg/utils/formfill.go34 Email: fmt.Sprintf("%s@example.org", xid.New().String()),CODE
LOWpkg/utils/formfill.go187 if placeholder, ok := input.Attributes.Get("placeholder"); ok {CODE
LOWpkg/utils/formsemantic.go27 "name": "John Doe",CODE
LOWpkg/utils/formsemantic_test.go64 require.Equal(t, "10001", semanticValue(ctx, stub, formInput("text", "plz", "placeholder", "Postleitzahl")))CODE
LOW⚡pkg/utils/formsemantic_test.go82 filled := formInput("text", "postal", "placeholder", "ZIP code")CODE
LOW⚡pkg/utils/formsemantic_test.go85 formInput("text", "zip", "placeholder", "ZIP code"),CODE
LOW⚡pkg/utils/formsemantic_test.go86 formInput("text", "q", "placeholder", "search"),CODE
LOWpkg/utils/formfill_test.go92 require.Contains(t, DefaultFormFillData.Email, "@example.org")CODE
LOWpkg/utils/formfill_test.go110 require.Contains(t, data.Email, "@example.org", "default email has no parens, should stay as-is")CODE
LOWpkg/engine/headless/types/types.go251 "placeholder": {},CODE
LOWpkg/engine/headless/auth/recording_test.go70 steps, err := StepsFromRecording([]byte(rec), "user@example.com", "secret")CODE
LOWpkg/engine/headless/crawler/normalizer/dom_utils.go182 "placeholder",CODE
Magic Placeholder Names2 hits · 10 pts
SeverityFileLineSnippetContext
HIGHREADME.md501katana -u https://example.com -headless -csp capsolver -csk YOUR_API_KEYCODE
HIGHREADME.md508export CAPTCHA_SOLVER_KEY=YOUR_API_KEYCODE
Hallucination Indicators1 hit · 10 pts
SeverityFileLineSnippetContext
CRITICALpkg/output/output.go222 if fileName, fileWriter, err := getResponseFile(w.storeResponseDir, result.Response.Resp.Request.URL.String()); err ==CODE
TODO Padding1 hit · 2 pts
SeverityFileLineSnippetContext
LOWpkg/engine/parser/parser_test.go318 // // TODO: Fix testCOMMENT
Hyper-Verbose Identifiers1 hit · 1 pts
SeverityFileLineSnippetContext
LOWpkg/engine/headless/js/page-init.js86 function hookMiscellaneousUtilities() {CODE