AI Slop Code Risk Monitor

restic/restic

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

Fast, secure, efficient backup program

0.3 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for restic/restic, a Go project with 36,901 GitHub stars. SynthScan examined 102,653 lines of code across 579 source files, recording 32 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 0.3 (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.3

Adjusted Signal

0.3

Raw Pattern Score

100%

Time Factor

2026-10-18

Last Push

36.9K

Stars

Language

102.7K

Lines of Code

579

Files

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

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

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 1.6/100 · LOW

Which changes need focused human review? 32 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 1LOW 31

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 32 distinct pattern matches across 3 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 Block30 hits · 30 pts

Severity	File	Line	Snippet	Context
LOW	build.go	1	// Description	COMMENT
LOW	build.go	21	// list of conditions and the following disclaimer.	COMMENT
LOW	doc.go	1	// Package restic gives a (very brief) introduction to the structure of source code.	COMMENT
LOW	internal/ui/termstatus/status.go	61	// The returned function must be called to shut down the termstatus.	COMMENT
LOW	internal/repository/doc.go	1	// Package repository implements a restic repository on top of a backend. In	COMMENT
LOW	internal/repository/doc.go	21	// # Pack	COMMENT
LOW	internal/repository/index/index.go	21	"github.com/restic/restic/internal/debug"	COMMENT
LOW	internal/repository/index/index.go	41	//	COMMENT
LOW	internal/archiver/archiver.go	101	mu sync.Mutex	COMMENT
LOW	internal/archiver/archiver.go	441	// allBlobsPresent checks if all blobs (contents) of the given node are	COMMENT
LOW	internal/backend/backend.go	41	// The function fn may be called multiple times during the same Load invocation	COMMENT
LOW	internal/backend/backend.go	61	// in the backend.	COMMENT
LOW	internal/backend/doc.go	1	// Package backend provides local and remote storage for restic repositories.	COMMENT
LOW	internal/backend/s3/s3.go	101	// getCredentials -- runs through the various credential types and returns the first one that works.	COMMENT
LOW	internal/backend/gs/gs.go	201	// This chunking allows the library to automatically handle network	COMMENT
LOW	internal/backend/cache/file_test.go	201		COMMENT
LOW	internal/backend/test/doc.go	1	// Package test contains a test suite with benchmarks for restic backends.	COMMENT
LOW	internal/backend/test/doc.go	21	// [...]	COMMENT
LOW	internal/filter/filter.go	61	func splitPath(p string) []string {	COMMENT
LOW	internal/filter/doc.go	1	// Package filter implements path filters similar to filepath.Match, but	COMMENT
LOW	internal/errors/errors.go	41	// an Unwrap method returning error. Otherwise, Unwrap returns nil.	COMMENT
LOW	internal/fs/ea_windows.go	21		COMMENT
LOW	internal/fs/ea_windows_test.go	21	// The MIT License (MIT)	COMMENT
LOW	internal/restic/doc.go	1	// Package restic is the top level package for the restic backup program,	COMMENT
LOW	internal/restic/repository.go	41		COMMENT
LOW	internal/restic/progress.go	41	E(msg string, args ...any)	COMMENT
LOW	internal/restorer/doc.go	1	// Package restorer contains code to restore data from a repository.	COMMENT
LOW	internal/restorer/doc.go	21	// file before any of the preceding file blobs. It is therefore possible to	COMMENT
LOW	doc/conf.py	1	#!/usr/bin/env python3	COMMENT
LOW	doc/conf.py	41	author = 'fd0'	COMMENT

Self-Referential Comments1 hit · 3 pts

Severity	File	Line	Snippet	Context
MEDIUM	doc/conf.py	7	# This file is execfile()d with the current directory set to its	COMMENT

Redundant / Tautological Comments1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	doc/zsh-completion.zsh	96	# Check if this is an activeHelp statement (i.e., prefixed with $activeHelpMarker)	COMMENT