AI Slop Code Risk Monitor

TwiN/gatus

Name: TwiN/gatus — 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).

Automated developer-oriented status page with alerting and incident support

0.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for TwiN/gatus, a Go project with 12,458 GitHub stars. SynthScan examined 81,606 lines of code across 315 source files, recording 26 pattern matches distributed across 6 syntactic categories. The legacy adjusted pattern signal is 0.7 (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.7

Adjusted Signal

0.7

Raw Pattern Score

100%

Time Factor

2026-10-29

Last Push

12.5K

Stars

Language

81.6K

Lines of Code

315

Files

Pattern Hits

2026-10-31

Scan Date

0.02

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

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

Hallucinated Dependency & Supply Chain Risk 2.2/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 3.3/100 · LOW

Which changes need focused human review? 26 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 4MEDIUM 0LOW 21

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

Magic Placeholder Names4 hits · 20 pts

Severity	File	Line	Snippet	Context
HIGH	README.md	1022	api-key: "YOUR_API_KEY"	CODE
HIGH	README.md	1722	api-key: "YOUR_API_KEY"	CODE
HIGH	README.md	2266	webhook-url: "https://api.squadcast.com/v3/incidents/api/YOUR_API_KEY"	CODE
HIGH	README.md	2498	api-key: "YOUR_API_KEY"	CODE

Hallucination Indicators1 hit · 10 pts

Severity	File	Line	Snippet	Context
CRITICAL	web/static/js/chunk-vendors.js	260	const{entries:i,setPrototypeOf:r,isFrozen:o,getPrototypeOf:s,getOwnPropertyDescriptor:a}=Object;let{freeze:l,seal:c,crea	CODE

Over-Commented Block8 hits · 8 pts

Severity	File	Line	Snippet	Context
LOW	alerting/alert/alert.go	41	// MinimumReminderInterval is the interval between reminders	COMMENT
LOW	alerting/provider/pushover/pushover.go	41	// Priority of all messages, ranging from -2 (very low) to 2 (Emergency)	COMMENT
LOW	config/config.go	61		COMMENT
LOW	config/endpoint/placeholder.go	21	// Values that could replace the placeholder: 127.0.0.1, 10.0.0.1, ...	COMMENT
LOW	config/endpoint/placeholder.go	61	// Usage: len([BODY].articles) == 10, len([BODY].name) > 5	COMMENT
LOW	config/endpoint/placeholder.go	101	// ResolvePlaceholder resolves all types of placeholders to their string values.	COMMENT
LOW	config/endpoint/result.go	41		COMMENT
LOW	storage/store/sql/sql_test.go	181	t.Run(fmt.Sprintf("num-hours-%d-expected-max-entries-%d", scenario.numberOfHours, scenario.expectedMaxUptimeEntries),	COMMENT

Fake / Example Data7 hits · 7 pts

Severity	File	Line	Snippet	Context
LOW	README.md	916	to: "user@example.com"	CODE
LOW	config/gontext/gontext_test.go	40	"name": "John Doe",	CODE
LOW	config/gontext/gontext_test.go	46	"name": "John Doe",	CODE
LOW	config/gontext/gontext_test.go	197	value: "John Doe",	CODE
LOW	config/endpoint/endpoint_test.go	1254	"name": "John Doe",	CODE
LOW	config/endpoint/endpoint_test.go	1258	expectedBody: `{"name": "John Doe"}`,	CODE
LOW	web/static/js/chunk-vendors.js	260	const{entries:i,setPrototypeOf:r,isFrozen:o,getPrototypeOf:s,getOwnPropertyDescriptor:a}=Object;let{freeze:l,seal:c,crea	CODE

Structural Annotation Overuse4 hits · 6 pts

Severity	File	Line	Snippet	Context
LOW	README.md	415	# Step 1: Create an item and store the item ID	COMMENT
LOW	README.md	430	# Step 2: Update the item using the stored item ID	COMMENT
LOW	README.md	441	# Step 3: Fetch the item and validate the price	COMMENT
LOW	README.md	452	# Step 4: Delete the item (always-run: true to ensure cleanup even if step 2 or 3 fails)	COMMENT

Verbosity Indicators2 hits · 3 pts

Severity	File	Line	Snippet	Context
LOW	config/endpoint/placeholder.go	162	// For len([BODY]), we need to check if it's JSON and get the actual length	COMMENT
LOW	storage/store/sql/sql.go	259	// First, we need to check if we need to insert a new event.	COMMENT