AI Slop Code Risk Monitor

pelletier/go-toml

SlopCodeMonitor badge for pelletier/go-toml Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

Go library for the TOML file format

1.6 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for pelletier/go-toml, a Go project with 2,000 GitHub stars. SynthScan examined 37,152 lines of code across 97 source files, recording 52 pattern matches distributed across 6 syntactic categories. The legacy adjusted pattern signal is 1.6 (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.6
Adjusted Signal
1.6
Raw Pattern Score
100%
Time Factor
2026-08-03
Last Push
2.0K
Stars
Go
Language
37.2K
Lines of Code
97
Files
52
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 7.8/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.1/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 8.0/100 · LOW

Which changes need focused human review? 52 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 5LOW 47

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 52 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 Block40 hits · 40 pts
SeverityFileLineSnippetContext
LOWmarshaler.go121// SetOmitEmptySuperTables removes the header of tables that do not directlyCOMMENT
LOWmarshaler.go141 return encCOMMENT
LOWmarshaler.go161// a position where only a value is valid (an array element, an inline table,COMMENT
LOWmarshaler.go181//COMMENT
LOWmarshaler.go201// solution is a custom type that implements encoding.TextMarshaler.COMMENT
LOWmarshaler.go221// The encoding of each public struct field can be customized by the formatCOMMENT
LOWmarshaler_test.go2301 expected := `# Int = 42COMMENT
LOWmarshaler_test.go2521 //COMMENT
LOWmarshaler_test.go2541 // # max points per metric when internal-aggregation=trueCOMMENT
LOWunmarshaler.go101// description of the missing fields.COMMENT
LOWunmarshaler.go121//COMMENT
LOWunmarshaler.go141// map[string]interface{}.COMMENT
LOWunmarshaler.go241COMMENT
LOWunmarshaler.go261COMMENT
LOWunmarshaler.go621 }COMMENT
LOWmarshaler_raw_test.go821 // [plugin]COMMENT
LOWbenchmark/benchmark.toml21[table.subtable]COMMENT
LOWcmd/tomljson/main.go1// Package tomljson is a program that converts TOML to JSON.COMMENT
LOWcmd/tomll/main.go1// Package tomll is a linter program for TOML.COMMENT
LOWcmd/jsontoml/main.go1// Package jsontoml is a program that converts JSON to TOML.COMMENT
LOWinternal/tracker/seen.go61//COMMENT
LOWinternal/parserbridge/parserbridge.go1// Package parserbridge exposes the unstable parser's non-AST scanners to theCOMMENT
LOW.github/workflows/codeql-analysis.yml1# For most projects, this workflow file will not need changing; you simply needCOMMENT
LOW.github/workflows/codeql-analysis.yml41 - name: Initialize CodeQLCOMMENT
LOWunstable/parser_test.go761COMMENT
LOWunstable/parser_test.go841 // 1:1->1:31 (0->30) | Comment [# Top of the document comment.]COMMENT
LOWunstable/parser_test.go861 // ---COMMENT
LOWunstable/parser_test.go881 // 19:1->19:20 (386->405) | KeyValue []COMMENT
LOWunstable/parser_test.go901 // 28:3->28:4 (638->639) | Integer [2]COMMENT
LOWunstable/marshaler.go1package unstableCOMMENT
LOWunstable/ast.go1package unstableCOMMENT
LOWunstable/ast.go41// Node returns a pointer to the node pointed at by the iterator.COMMENT
LOWunstable/parser.go41//COMMENT
LOWunstable/parser.go61 // unbounded mutual recursion, which would otherwise let a deeply nestedCOMMENT
LOWunstable/unmarshaler.go1package unstableCOMMENT
LOWunstable/unmarshaler.go21//COMMENT
LOWunstable/edit/edit.go1// Package edit provides comment- and layout-preserving editing of TOMLCOMMENT
LOWunstable/edit/edit.go21// unambiguous. For Set, an index equal to the array's length appends a newCOMMENT
LOWunstable/edit/edit.go41// Comments travel with the expression they annotate: the contiguousCOMMENT
LOWunstable/edit/mutate.go21// Set sets the value at the given key path, creating the tables leading toCOMMENT
Slop Phrases5 hits · 10 pts
SeverityFileLineSnippetContext
MEDIUMtoml_testgen_test.go1629 input := "[fruit]\napple.color = \"red\"\napple.taste.sweet = true\n\n[fruit.apple] # INVALID\n# [fruit.apple.taste] CODE
MEDIUMtoml_testgen_test.go1634 input := "[fruit]\napple.color = \"red\"\napple.taste.sweet = true\n\n# [fruit.apple] # INVALID\n[fruit.apple.taste] CODE
MEDIUMtoml_testgen_test.go3173 input := "[fruit]\napple.color = \"red\"\napple.taste.sweet = true\n\n# [fruit.apple] # INVALID\n# [fruit.apple.taste]CODE
MEDIUMtoml_testgen_test.go3233 input := "# This makes the key \"fruit\" into a table.\nfruit.apple.smooth = true\n\n# So then you can add to the tableCODE
LOWunstable/parser.go42// Don't forget to check Error() after you're done parsing.COMMENT
Redundant / Tautological Comments4 hits · 6 pts
SeverityFileLineSnippetContext
LOWtest-go-versions.sh146# Check if Docker is availableCOMMENT
LOWtest-go-versions.sh152# Check if Docker daemon is runningCOMMENT
LOWtest-go-versions.sh395 # Check if this version and all subsequent versions passCOMMENT
LOWtest-go-versions.sh424 # Check if the two most recent versions failedCOMMENT
Self-Referential Comments1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMtest-go-versions.sh170 # Create a temporary Dockerfile for this versionCOMMENT
Example Usage Blocks1 hit · 2 pts
SeverityFileLineSnippetContext
LOWcaps.sh5# Usage:COMMENT
Fake / Example Data1 hit · 1 pts
SeverityFileLineSnippetContext
LOWbenchmark/realworld_bench_test.go399authors = [{ name = "Jane Doe", email = "jane@example.com" }]CODE