AI Slop Code RIsk Monitor

charmbracelet/soft-serve

The mighty, self-hostable Git server for the command line🍦

6.3 Moderate pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for charmbracelet/soft-serve, a Go project with 7,254 GitHub stars. SynthScan examined 31,166 lines of code across 267 source files, recording 30 pattern matches distributed across 6 syntactic categories. The legacy adjusted pattern signal is 6.3 (Moderate 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.

6.3
Adjusted Signal
6.3
Raw Pattern Score
100%
Time Factor
2026-10-05
Last Push
7.3K
Stars
Go
Language
31.2K
Lines of Code
267
Files
30
Pattern Hits
2026-10-12
Scan Date
0.05
HC Hit Rate

Risk Review · v3

Use each vector to guide manual verification of the underlying findings.

Cognitive Ownership Risk 4.8/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 23.3/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 21.3/100 · LOW

Which changes need focused human review? 30 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 13HIGH 0MEDIUM 1LOW 16

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

Hallucination Indicators13 hits · 165 pts
SeverityFileLineSnippetContext
CRITICAL⚡pkg/ui/pages/repo/log.go504 l.common.Styles.Log.CommitHash.Render("commit "+c.ID.String()),CODE
CRITICAL⚡pkg/ui/pages/repo/log.go505 l.common.Styles.Log.CommitAuthor.Render(fmt.Sprintf("Author: %s <%s>", c.Author.Name, c.Author.Email)),CODE
CRITICAL⚡pkg/ui/pages/repo/log.go506 l.common.Styles.Log.CommitDate.Render("Date: "+c.Committer.When.Format(time.UnixDate)),CODE
CRITICAL⚡pkg/ui/pages/repo/log.go507 l.common.Styles.Log.CommitBody.Render(msg),CODE
CRITICAL⚡pkg/ui/pages/repo/files.go513 c.Styles.Tree.Blame.Hash.Render(commit.ID.String()[:7]),CODE
CRITICAL⚡pkg/ui/pages/repo/files.go514 c.Styles.Tree.Blame.Message.Render(commit.Summary()),CODE
CRITICAL⚡pkg/ui/pages/repo/files.go515 c.Styles.Tree.Blame.Who.Render(who),CODE
CRITICALpkg/ui/pages/repo/stash.go199 title := s.common.Styles.Stash.Title.Render(s.list.SelectedItem().(StashItem).Title())CODE
CRITICALpkg/ui/pages/repo/repo.go89 hm := r.common.Styles.Repo.Body.GetVerticalFrameSize() +CODE
CRITICALpkg/ui/pages/repo/repo.go91 r.common.Styles.Repo.Header.GetVerticalFrameSize() +CODE
CRITICALpkg/ui/pages/repo/repo.go331 header = r.common.Styles.Repo.HeaderName.Render(header)CODE
CRITICALpkg/ui/pages/repo/repo.go336 r.common.Styles.Repo.HeaderDesc.Render(desc),CODE
CRITICALpkg/ui/pages/repo/repo.go354 style := r.common.Styles.Repo.Header.Width(r.common.Width)CODE
Verbosity Indicators5 hits · 10 pts
SeverityFileLineSnippetContext
LOW⚡pkg/ssh/middleware_test.go120 // Step 1: SSH client offers admin's public keyCOMMENT
LOW⚡pkg/ssh/middleware_test.go125 // Step 2: Signature verification FAILS (attacker doesn't have admin's private key)COMMENT
LOW⚡pkg/ssh/middleware_test.go128 // Step 3: SSH client offers attacker's key (which SUCCEEDS)COMMENT
LOW⚡pkg/ssh/middleware_test.go133 // Step 4: AuthenticationMiddleware should re-lookup user based on authenticated keyCOMMENT
LOWpkg/lfs/scanner.go95 // Now we need to check if the pointerBuf is an LFS pointerCOMMENT
Structural Annotation Overuse4 hits · 9 pts
SeverityFileLineSnippetContext
LOW⚡pkg/ssh/middleware_test.go120 // Step 1: SSH client offers admin's public keyCOMMENT
LOW⚡pkg/ssh/middleware_test.go125 // Step 2: Signature verification FAILS (attacker doesn't have admin's private key)COMMENT
LOW⚡pkg/ssh/middleware_test.go128 // Step 3: SSH client offers attacker's key (which SUCCEEDS)COMMENT
LOW⚡pkg/ssh/middleware_test.go133 // Step 4: AuthenticationMiddleware should re-lookup user based on authenticated keyCOMMENT
Over-Commented Block5 hits · 5 pts
SeverityFileLineSnippetContext
LOW.golangci.yml1version: "2"COMMENT
LOWREADME.md281COMMENT
LOWtestscript/script_test.go221 check(ts, sess.Run(strings.Join(args, " ")), neg)COMMENT
LOWpkg/config/config.go181 // rejected at parse time by AccessLevel's TextUnmarshaler.COMMENT
LOWpkg/ssh/middleware_test.go21COMMENT
TODO Padding2 hits · 3 pts
SeverityFileLineSnippetContext
LOWpkg/webhook/push.go86 // TODO: implement a commits apiCOMMENT
LOWpkg/lfs/ssh_client.go3// TODO: implement Git LFS SSH client.COMMENT
Self-Referential Comments1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMpkg/ui/pages/repo/empty.go21## Creating a new repository on the command lineCOMMENT