AI Slop Code Risk Monitor

psviderski/uncloud

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

A lightweight tool for deploying and managing containerised applications across a network of Docker hosts. Bridging the gap between Docker and Kubernetes ✨

0.5 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for psviderski/uncloud, a Go project with 5,588 GitHub stars. SynthScan examined 118,331 lines of code across 507 source files, recording 43 pattern matches distributed across 7 syntactic categories. The legacy adjusted pattern signal is 0.5 (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.5

Adjusted Signal

0.5

Raw Pattern Score

100%

Time Factor

2026-10-29

Last Push

5.6K

Stars

Language

118.3K

Lines of Code

507

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

Can maintainers explain intent, assumptions, and trade-offs? 43 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? 1 finding(s).

PR Review Velocity Impact 2.0/100 · LOW

Which changes need focused human review? 43 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 3LOW 40

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 43 distinct pattern matches across 7 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 Block19 hits · 19 pts

Severity	File	Line	Snippet	Context
LOW	cmd/uc/image/rm_plan.go	161	// - Digest: resolve through RepoTags, RepoDigests, or the image ID, then select that image's names in	COMMENT
LOW	internal/grpcversion/interceptor.go	21	MetadataKeyServerVersion = "uncloud-server-version"	COMMENT
LOW	internal/machine/state.go	21	// State defines the machine-specific configuration within a cluster. It encapsulates essential identifiers	COMMENT
LOW	internal/machine/caddyconfig/caddyfile.go	101		COMMENT
LOW	internal/machine/network/peer.go	81	// peerDownInterval is the time since last handshake when established peer is considered to be down.	COMMENT
LOW	internal/machine/network/peer.go	101	//	COMMENT
LOW	internal/machine/api/proxy/backend.go	21	// AppendInfo is called to enhance response from the backend with additional data.	COMMENT
LOW	internal/machine/api/proxy/backend.go	41	// If we look at binary representation of any unary 'SomeResponse' message, it will always contain one	COMMENT
LOW	internal/machine/api/proxy/backend.go	121	//	COMMENT
LOW	internal/machine/store/replication.go	21	//	COMMENT
LOW	internal/corrosion/admin.go	141	// For all purposes, a Suspect member is treated as if it were Alive until either it refutes the suspicion	COMMENT
LOW	api/pb/machine_grpc.pb.go	41	// CheckPrerequisites verifies if the machine meets all necessary system requirements to participate in the cluster.	COMMENT
LOW	api/pb/machine_grpc.pb.go	221	Token(context.Context, emptypb.Empty) (TokenResponse, error)	COMMENT
LOW	pkg/distlock/doc.go	1	// Package distlock provides distributed, automatically renewed leases across independent nodes.	COMMENT
LOW	pkg/distlock/grpc/lease_grpc.pb.go	81	// for forward compatibility.	COMMENT
LOW	pkg/api/service.go	21	ServiceModeGlobal = "global"	COMMENT
LOW	pkg/api/service.go	281	Init *bool	COMMENT
LOW	pkg/api/container.go	301	// WaitContainerHealthyOptions configures the behaviour of WaitContainerHealthy.	COMMENT
LOW	pkg/client/machine.go	141	}	COMMENT

TODO Padding10 hits · 15 pts

Severity	File	Line	Snippet	Context
LOW	test/e2e/service_test.go	792	// TODO: implement and check for more details about the failed constraints.	COMMENT
LOW	internal/cli/cli.go	189	// TODO: implement local machine initialisation	COMMENT
LOW	internal/machine/machine.go	626	// TODO: implement timeout for graceful shutdown.	COMMENT
LOW	internal/machine/machine.go	631	// TODO: implement timeout for graceful shutdown.	COMMENT
LOW	internal/machine/cluster/dns.go	118	// TODO: implement and call Uncloud DNS endpoint to release/delete the domain.	COMMENT
LOW	internal/machine/caddyconfig/caddyfile.go	325	// TODO: implement L4 ingress routing for TCP and UDP.	COMMENT
LOW	internal/machine/dns/resolver.go	50	// TODO: implement machine membership check using Corrossion Admin client to filter available containers.	COMMENT
LOW	internal/machine/dns/resolver.go	73	// TODO: implement machine membership check using Corrossion Admin client to filter available containers.	COMMENT
LOW	experiment/syncer.go	18	// TODO: implement SessionDAGService to optimize node fetching.	COMMENT
LOW	pkg/api/resources.go	18	// TODO: implement a placement constraint that checks available memory on machines.	COMMENT

Structural Annotation Overuse5 hits · 8 pts

Severity	File	Line	Snippet	Context
LOW	website/blog/2025-08-01-wireguard-overlay/index.md	54	## Step 1: Configure Docker networks	COMMENT
LOW	website/blog/2025-08-01-wireguard-overlay/index.md	90	## Step 2: Connect Docker networks with WireGuard	COMMENT
LOW	website/blog/2025-08-01-wireguard-overlay/index.md	200	## Step 3: Configure IP routing	COMMENT
LOW	website/blog/2025-08-01-wireguard-overlay/index.md	275	## Step 4: Testing	COMMENT
LOW	website/blog/2025-08-01-wireguard-overlay/index.md	332	## Step 5: Make the configuration persistent	COMMENT

Redundant / Tautological Comments5 hits · 8 pts

Severity	File	Line	Snippet	Context
LOW	scripts/uninstall.sh	38	# Check if user is root.	COMMENT
LOW	scripts/uninstall.sh	107	# Check if the group still exists (other users may be using it).	COMMENT
LOW	scripts/install.sh	111	# Check if the installed Docker configured to use the containerd image store.	COMMENT
LOW	scripts/install_cli.sh	51	# Check if not running as root and need to use sudo to write to INSTALL_DIR.	COMMENT
LOW	.github/workflows/go-tests.yml	81	# Check if the generated files are up to date.	COMMENT

Self-Referential Comments2 hits · 6 pts

Severity	File	Line	Snippet	Context
MEDIUM	scripts/install.sh	246	# Create a temporary directory for downloads.	COMMENT
MEDIUM	scripts/install_cli.sh	97	# Create a temporary directory for downloads.	COMMENT

Modern AI Meta-Vocabulary1 hit · 3 pts

Severity	File	Line	Snippet	Context
MEDIUM	website/docs/1-overview.md	85	### No complex orchestration	COMMENT

Hyper-Verbose Identifiers1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	website/landing/hub.html	1134	(function enableFormWhenPostHogLoads() {	CODE