AI Slop Code Risk Monitor

go-git/go-git

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

A highly extensible Git implementation in pure Go.

2.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for go-git/go-git, a Go project with 7,839 GitHub stars. SynthScan examined 179,186 lines of code across 749 source files, recording 456 pattern matches distributed across 6 syntactic categories. The legacy adjusted pattern signal is 2.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.

2.7
Adjusted Signal
2.7
Raw Pattern Score
100%
Time Factor
2026-10-31
Last Push
7.8K
Stars
Go
Language
179.2K
Lines of Code
749
Files
456
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 12.0/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.4/100 · LOW

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

Agent Over-Engineering Ratio 0.2/100 · LOW

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

PR Review Velocity Impact 12.2/100 · LOW

Which changes need focused human review? 456 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 451

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 456 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 Block412 hits · 412 pts
SeverityFileLineSnippetContext
LOWoptions.go41// References with unusable names are skipped. To diagnose skipped references,COMMENT
LOWoptions.go61 // remote-tracking branches, notes etc.) and sets up a refspec configurationCOMMENT
LOWoptions.go81 // by default is AllTags.COMMENT
LOWoptions.go181 RemoteURL stringCOMMENT
LOWoptions.go221 TagFollowing = plumbing.TagFollowingCOMMENT
LOWoptions.go241 // each remote branch history.COMMENT
LOWoptions.go281COMMENT
LOWoptions.go301 Progress sideband.ProgressCOMMENT
LOWoptions.go381)COMMENT
LOWoptions.go421COMMENT
LOWoptions.go441 // SoftReset does not touch the index file or the working tree at all (butCOMMENT
LOWoptions.go521 To plumbing.HashCOMMENT
LOWoptions.go581COMMENT
LOWworktree_fs.go21//COMMENT
LOWworktree_fs.go41// boundary. Two layers apply:COMMENT
LOWworktree_fs.go281// filesystem. validPath guards the path string. This guards the on-diskCOMMENT
LOWworktree_fs.go301 }COMMENT
LOWworktree_fs_test.go361// TestWorktreeFilesystemRejectsSymlinkTraversal pins the leading-pathCOMMENT
LOWworktree_fs_test.go1061 }COMMENT
LOWworktree_fs_test.go1161 }COMMENT
LOWworktree_fs_test.go1281// final-position ".git" and HFS+/NTFS .git-disguise variants onCOMMENT
LOWremote.go381// transport operations.COMMENT
LOWremote.go661//COMMENT
LOWremote.go681COMMENT
LOWremote.go761}COMMENT
LOWremote.go1341COMMENT
LOWworktree.go441 if entry.Mode != filemode.Dir {COMMENT
LOWworktree.go681//COMMENT
LOWworktree.go721 if err := rmFileAndDirsIfEmpty(fs, name); err != nil {COMMENT
LOWworktree.go1001 return w.addIndexFromFile(fs, name, e.Hash, idx)COMMENT
LOWworktree.go1521 }COMMENT
LOWblame.go21type BlameResult struct {COMMENT
LOWdoc.go1// Package git is a highly extensible git implementation in pure Go.COMMENT
LOWrepository_test.go541//COMMENT
LOWsubmodule.go181 }COMMENT
LOWrepository_extensions.go21 // is using a format version that is not supported.COMMENT
LOWworktree_status.go161 }COMMENT
LOWworktree_reset_bench_test.go1package gitCOMMENT
LOWstatus.go81 Copied StatusCode = 'C'COMMENT
LOWrepository.go1021 return string(b), nilCOMMENT
LOWrepository.go1041// ref, err := r.Tag("v0.1.0")COMMENT
LOWrepository.go1681//COMMENT
LOWworktree_status_bench_test.go301// its own .gitignore, the shape of a monorepo in which each package carriesCOMMENT
LOWconfig/config.go61)COMMENT
LOWconfig/config.go81 // FileMode defines whether the executable bit of working tree files is to be honored.COMMENT
LOWconfig/config.go161 // e.g. when initializing a new repository or when cloningCOMMENT
LOWconfig/config.go181 ObjectFormat format.ObjectFormatCOMMENT
LOWconfig/config.go201COMMENT
LOWconfig/config.go221 // Name is the personal name of the author and the committer of a commit.COMMENT
LOWconfig/config.go1041COMMENT
LOWconfig/branch.go21 // Remote name of remote to trackCOMMENT
LOWconfig/modules.go121}COMMENT
LOWtests/fuzz/ossfuzz_test.go1// Package fuzz_test asserts the rules the OSS-Fuzz build imposes on thisCOMMENT
LOWtests/gitcompare/status_bench_test.go1// Package gitcompare_test measures go-git against the reference git binary onCOMMENT
LOWinternal/pathutil/path_util.go41// dot, so "." finds ".." and "" finds a bare "." — each with the disguisesCOMMENT
LOWinternal/pathutil/tree.go21// variants — at every position, not just the root.COMMENT
LOWinternal/pathutil/ntfs.go1package pathutilCOMMENT
LOWinternal/transport/v2.go41// CommandFunc runs a single Protocol v2 command: it encodes req into theCOMMENT
LOWinternal/transport/v2.go141type FetchRound func(args *packp.FetchArgs) (out *packp.FetchOutput, packReader io.Reader, err error)COMMENT
LOWinternal/test/gitenv/apple_git.go21// check before starting Git. Under concurrent test load this exceeded the gitCOMMENT
352 more matches not shown…
Verbosity Indicators13 hits · 22 pts
SeverityFileLineSnippetContext
LOWworktree_commit_test.go970 // Step 1: Write LICENSECOMMENT
LOWworktree_commit_test.go986 // Step 2: Write foo.COMMENT
LOWworktree_commit_test.go1000 // Step 3: CheckCOMMENT
LOWworktree.go704 // Step 1: delete files removed from the tracked tree.COMMENT
LOWworktree.go726 // Step 2: write files that are in the new index but missing or staleCOMMENT
LOWworktree.go776 // Step 3: remove tracked files that are SkipWorktree=true from disk.COMMENT
LOWrepository_test.go576 // Step 1: clone the default branch at depth=1.COMMENT
LOWrepository_test.go590 // Step 2: fetch the specific commit by hash using "+<hash>:<hash>".COMMENT
LOW⚡repository_test.go602 // Step 3: the commit object MUST now be present in the object store.COMMENT
LOW⚡repository_test.go608 // Step 4: regression 2 — no spurious refs/heads/<sha> must be created.COMMENT
LOW⚡repository_test.go615 // Step 5: the commit must also be resolvable as a revision.COMMENT
LOWrepository_test.go626 // Step 6: downstream effect — Worktree.Checkout must also succeed.COMMENT
LOWplumbing/format/packfile/encoder.go177 // We need to check if we already write that object due a cyclic delta chainCOMMENT
Structural Annotation Overuse12 hits · 20 pts
SeverityFileLineSnippetContext
LOWworktree_commit_test.go970 // Step 1: Write LICENSECOMMENT
LOWworktree_commit_test.go986 // Step 2: Write foo.COMMENT
LOWworktree_commit_test.go1000 // Step 3: CheckCOMMENT
LOWworktree.go704 // Step 1: delete files removed from the tracked tree.COMMENT
LOWworktree.go726 // Step 2: write files that are in the new index but missing or staleCOMMENT
LOWworktree.go776 // Step 3: remove tracked files that are SkipWorktree=true from disk.COMMENT
LOWrepository_test.go576 // Step 1: clone the default branch at depth=1.COMMENT
LOWrepository_test.go590 // Step 2: fetch the specific commit by hash using "+<hash>:<hash>".COMMENT
LOW⚡repository_test.go602 // Step 3: the commit object MUST now be present in the object store.COMMENT
LOW⚡repository_test.go608 // Step 4: regression 2 — no spurious refs/heads/<sha> must be created.COMMENT
LOW⚡repository_test.go615 // Step 5: the commit must also be resolvable as a revision.COMMENT
LOWrepository_test.go626 // Step 6: downstream effect — Worktree.Checkout must also succeed.COMMENT
Fake / Example Data14 hits · 14 pts
SeverityFileLineSnippetContext
LOWsigner_test.go42 Name: "John Doe",CODE
LOWworktree_status_test.go131 sig := &object.Signature{Name: "test", Email: "test@test.com"}CODE
LOWworktree_test.go4461 os.WriteFile(filepath.Join(dir, "README"), []byte("placeholder"), 0o644)CODE
LOWconfig/config_test.go82 s.Equal("John Doe", cfg.User.Name)CODE
LOWstorage/filesystem/object_test.go942 err = os.WriteFile(badTarget, []byte("placeholder"), 0o644)CODE
LOWplumbing/object/object_test.go133 Email: "foo@bar.com",CODE
LOWplumbing/object/object_test.go138 Email: "foo@bar.com",CODE
LOWplumbing/object/object_test.go153 Email: "foo@bar.com",CODE
LOWplumbing/object/object_test.go158 Email: "foo@bar.com",CODE
LOW_examples/commit/main.go54 Name: "John Doe",CODE
LOW_examples/clone-commit-push/main.go59 Name: "John Doe",CODE
LOW_examples/sha256/main.go52 Name: "John Doe",CODE
LOW_examples/restore/main.go33 Name: "John Doe",CODE
LOWx/plumbing/worktree/worktree_test.go783 Author: &object.Signature{Name: "Test", Email: "test@test.com", When: time.Now()},CODE
Decorative Section Separators3 hits · 9 pts
SeverityFileLineSnippetContext
MEDIUMrepository_test.go762 // ── Build the source repo using PlainInit + Worktree.Commit ──────────COMMENT
MEDIUMrepository_test.go797 // ── Clone from the detached-HEAD source ───────────────────────────────COMMENT
MEDIUMrepository_test.go809 // ── Verify the cloned repo behaves like `git clone` ──────────────────────COMMENT
AI Slop Vocabulary2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMinternal/server/git/git_test.go189 // robust against goroutine scheduling skew on shared CI runners.COMMENT
MEDIUMplumbing/format/config/decoder_test.go212// absolute duration, which is far more robust on a loaded machine than aCOMMENT