AI Slop Code Risk Monitor

yuin/goldmark

Name: yuin/goldmark — Go Code Quality & Security Review | AI Slop Code Risk Monitor
Creator: AI Slop Code Risk Monitor

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

:trophy: The Golden Swiss Army Knife for markdown processing. 100% CommonMark compliant, AST w/ CST, Extensible, Fast, CJK-friendly.

1.0 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for yuin/goldmark, a Go project with 5,084 GitHub stars. SynthScan examined 62,929 lines of code across 146 source files, recording 50 pattern matches distributed across 4 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-31

Last Push

5.1K

Stars

Language

62.9K

Lines of Code

146

Files

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 2.7/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 2.0/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 4.3/100 · LOW

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

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 50 distinct pattern matches across 4 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.

Fake / Example Data24 hits · 26 pts

Severity	File	Line	Snippet	Context
LOW	extension/testdata/definition_list.txt	92	: This is a definition with two paragraphs. Lorem ipsum	CODE
LOW	extension/testdata/definition_list.txt	93	dolor sit amet, consectetuer adipiscing elit. Aliquam	CODE
LOW	extension/testdata/definition_list.txt	117	<p>This is a definition with two paragraphs. Lorem ipsum	CODE
LOW	extension/testdata/definition_list.txt	118	dolor sit amet, consectetuer adipiscing elit. Aliquam	CODE
LOW	_benchmark/go/testdata/commonmark-spec.md	9399	"Lorem ipsum dolor\nsit amet."	CODE
LOW	_benchmark/go/testdata/commonmark-spec.md	9458	> Lorem ipsum dolor	CODE
LOW	_benchmark/go/testdata/commonmark-spec.md	9473	> Lorem ipsum dolor	CODE
LOW	_benchmark/go/testdata/commonmark-spec.md	9485	"Lorem ipsum dolor"	CODE
LOW	_benchmark/go/testdata/commonmark-spec.md	9501	"Lorem ipsum dolor\nsit amet."	CODE
LOW	_benchmark/go/testdata/commonmark-spec.md	9519	"Lorem ipsum dolor\nsit amet."	CODE
LOW	_benchmark/go/testdata/commonmark-spec.md	9541	"Lorem ipsum dolor\nsit amet."	CODE
LOW	_benchmark/go/testdata/commonmark-spec.md	9564	str "Lorem ipsum dolor"	CODE
LOW⚡	_benchmark/go/testdata/cmark-samples/lorem1.md	1	Lorem ipsum dolor sit amet, __consectetur__ adipiscing elit. Cras imperdiet nec erat ac condimentum. Nulla vel rutrum li	CODE
LOW⚡	_benchmark/go/testdata/cmark-samples/lorem1.md	1	Lorem ipsum dolor sit amet, __consectetur__ adipiscing elit. Cras imperdiet nec erat ac condimentum. Nulla vel rutrum li	CODE
LOW⚡	_benchmark/go/testdata/cmark-samples/lorem1.md	7	Suspendisse potenti. Donec ante velit, ornare at augue quis, tristique laoreet sem. Etiam in ipsum elit. Nullam cursus d	CODE
LOW⚡	_benchmark/go/testdata/cmark-samples/lorem1.md	7	Suspendisse potenti. Donec ante velit, ornare at augue quis, tristique laoreet sem. Etiam in ipsum elit. Nullam cursus d	CODE
LOW	_benchmark/cmark/_data.md	9399	"Lorem ipsum dolor\nsit amet."	CODE
LOW	_benchmark/cmark/_data.md	9458	> Lorem ipsum dolor	CODE
LOW	_benchmark/cmark/_data.md	9473	> Lorem ipsum dolor	CODE
LOW	_benchmark/cmark/_data.md	9485	"Lorem ipsum dolor"	CODE
LOW	_benchmark/cmark/_data.md	9501	"Lorem ipsum dolor\nsit amet."	CODE
LOW	_benchmark/cmark/_data.md	9519	"Lorem ipsum dolor\nsit amet."	CODE
LOW	_benchmark/cmark/_data.md	9541	"Lorem ipsum dolor\nsit amet."	CODE
LOW	_benchmark/cmark/_data.md	9564	str "Lorem ipsum dolor"	CODE

Over-Commented Block17 hits · 17 pts

Severity	File	Line	Snippet	Context
LOW	testdata/options-auto-heading-id.txt	1	1	COMMENT
LOW	testdata/options-auto-heading-id.txt	41	3	COMMENT
LOW	testdata/options-auto-heading-id.txt	81	# Test ## {data-attr="" & ' '"}	COMMENT
LOW	extension/table.go	321	}),	COMMENT
LOW	extension/table.go	421	}	COMMENT
LOW	extension/table.go	441		COMMENT
LOW	util/util.go	141	// If the line contains tab characters, paddings may be not zero.	COMMENT
LOW	parser/list.go	161	if util.IsBlank(line) {	COMMENT
LOW	parser/parser.go	661	// A Parser interface parses Markdown text into AST nodes.	COMMENT
LOW	parser/parser.go	681	// Open parses the current line and returns a result of parsing.	COMMENT
LOW	parser/parser.go	721	// Halfspaces triggers this parser when character is any spaces characters or	COMMENT
LOW	parser/parser.go	1141		COMMENT
LOW	parser/parser.go	1521	//	COMMENT
LOW	parser/parser.go	1541	// Paragraph transformers:	COMMENT
LOW	ast/ast.go	101	// If target is not a child of this node, ReplaceChild appends insertee to the	COMMENT
LOW	text/value.go	661	// Padding is a padding length of the segment.	COMMENT
LOW	_benchmark/go/testdata/cmark-samples/block-heading.md	1	# heading	COMMENT

Structural Annotation Overuse8 hits · 12 pts

Severity	File	Line	Snippet	Context
LOW	README.md	751	### Step 1: Define AST nodes	COMMENT
LOW	README.md	827	### Step 2: Write a parser	COMMENT
LOW	README.md	961	### Step 3: Write a renderer	COMMENT
LOW	README.md	1065	### Step 4: Package as extensions	COMMENT
LOW	…sion-v1-to-v2/references/how-to-create-an-extension.md	42	### Step 1: Define AST nodes	COMMENT
LOW	…sion-v1-to-v2/references/how-to-create-an-extension.md	118	### Step 2: Write a parser	COMMENT
LOW	…sion-v1-to-v2/references/how-to-create-an-extension.md	252	### Step 3: Write a renderer	COMMENT
LOW	…sion-v1-to-v2/references/how-to-create-an-extension.md	356	### Step 4: Package as extensions	COMMENT

Synthetic Comment Markers1 hit · 5 pts

Severity	File	Line	Snippet	Context
HIGH	CONTRIBUTING.md	68	There have also been many submissions that were essentially AI slop: large amounts of low-value, unnecessary, or poo	CODE