AI Slop Code Risk Monitor

containerd/nerdctl

SlopCodeMonitor badge for containerd/nerdctl Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

contaiNERD CTL - Docker-compatible CLI for containerd, with support for Compose, Rootless, eStargz, OCIcrypt, IPFS, ...

1.0 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for containerd/nerdctl, a Go project with 10,458 GitHub stars. SynthScan examined 150,139 lines of code across 933 source files, recording 107 pattern matches distributed across 9 syntactic categories. The legacy adjusted pattern signal is 1.0 (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.0
Adjusted Signal
1.0
Raw Pattern Score
100%
Time Factor
2026-10-30
Last Push
10.5K
Stars
Go
Language
150.1K
Lines of Code
933
Files
107
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 4.1/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 101 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.6/100 · LOW

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

PR Review Velocity Impact 4.1/100 · LOW

Which changes need focused human review? 107 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 1MEDIUM 7LOW 99

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 107 distinct pattern matches across 9 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 Block80 hits · 80 pts
SeverityFileLineSnippetContext
LOW.golangci.yml261 # - equalFoldCOMMENT
LOWcmd/nerdctl/image/image_list.go141 }COMMENT
LOWcmd/nerdctl/search/search_linux_test.go21 "regexp"COMMENT
LOWcmd/nerdctl/container/container_list_linux_test.go41// setupPsTestContainer creates a test container with labels, volumes, and network.COMMENT
LOWhack/test-integration-rootless.sh1#!/bin/bashCOMMENT
LOWhack/test-integration-rootless.sh41# systemctl --user (and the dbus clients) locate the systemd user session throughCOMMENT
LOWhack/build-integration-canary.sh1#!/usr/bin/env bashCOMMENT
LOWhack/test-integration.sh1#!/usr/bin/env bashCOMMENT
LOWhack/git-checkout-tag-with-hash.sh1#!/bin/shCOMMENT
LOWhack/generate-release-note.sh1#!/bin/bashCOMMENT
LOWhack/provisioning/version/fetch.sh1#!/usr/bin/env bashCOMMENT
LOWhack/provisioning/linux/cni.sh1#!/usr/bin/env bashCOMMENT
LOWhack/provisioning/linux/test-integration-env.sh1#!/usr/bin/env bashCOMMENT
LOWhack/provisioning/linux/containerd.sh1#!/usr/bin/env bashCOMMENT
LOWhack/provisioning/kube/kind.sh1#!/usr/bin/env bashCOMMENT
LOWhack/provisioning/windows/cni.sh1#!/usr/bin/env bashCOMMENT
LOWhack/github/gotestsum-reporter.sh1#!/usr/bin/env bashCOMMENT
LOWhack/github/action-helpers.sh1#!/usr/bin/env bashCOMMENT
LOWhack/scripts/lib.sh1#!/usr/bin/env bashCOMMENT
LOW…pfs-registry-kubernetes/ipfs-cluster/bootstrap.yaml.sh1#!/bin/bashCOMMENT
LOW…erdctl-ipfs-registry-kubernetes/ipfs/bootstrap.yaml.sh1#!/bin/bashCOMMENT
LOW…y-kubernetes/ipfs-stargz-snapshotter/bootstrap.yaml.sh1#!/bin/bashCOMMENT
LOWmod/tigron/tig/t.go21// Expert note: using the testing.TB interface instead is tempting, but not possible, as the go authors made itCOMMENT
LOWmod/tigron/test/command.go61 // T returns the current testing objectCOMMENT
LOWmod/tigron/test/interfaces.go41 // Save will store the content in the file, ensuring parent dir exists, and return the path.COMMENT
LOWmod/tigron/test/interfaces.go101// with an Expected. A TestableCommand can be used as a Case Command obviously, but also as part ofCOMMENT
LOWmod/tigron/test/case.go41 // Env contains a map of environment variables to use as a base for all commands run in Setup,COMMENT
LOWmod/tigron/internal/assertive/assertive.go241// as (presumably) the passed function is starting with its own stack in a go routine.COMMENT
LOWmod/tigron/internal/highk/doc.go21// - get rid of lsof and implement in goCOMMENT
LOWmod/tigron/internal/com/command_test.go661// }COMMENT
LOWmod/tigron/internal/com/package_benchmark_test.go21 "testing"COMMENT
LOWmod/tigron/internal/com/doc.go21// - environment filteringCOMMENT
LOWmod/tigron/hack/dev-setup-macos.sh1#!/usr/bin/env bashCOMMENT
LOWmod/tigron/hack/dev-setup-linux.sh1#!/usr/bin/env bashCOMMENT
LOWmod/tigron/hack/headers/dockerfile.txt1# Copyright The containerd Authors.COMMENT
LOWmod/tigron/hack/headers/bash.txt1# Copyright The containerd Authors.COMMENT
LOWmod/tigron/hack/headers/makefile.txt1# Copyright The containerd Authors.COMMENT
LOWmod/soigneur/flaky-annotate.sh1#!/usr/bin/env bashCOMMENT
LOWmod/soigneur/flaky-annotate.sh21# - "flaky": the tests that failed, then passed on retry. Flaky beyond a doubt. Those only existCOMMENT
LOWmod/soigneur/flaky-issue.sh1#!/usr/bin/env bashCOMMENT
LOWmod/soigneur/flaky-issue.sh21# subscribers get notified without the issue growing a full copy of every report. Nothing hereCOMMENT
LOWmod/soigneur/lib.sh1#!/usr/bin/env bashCOMMENT
LOWmod/soigneur/lib.sh21 # The marker that flaky-annotate.sh writes to the job log, and that flaky-report.sh reads backCOMMENT
LOWmod/soigneur/flaky-report.sh1#!/usr/bin/env bashCOMMENT
LOWmod/soigneur/flaky-report.sh21# returns a zip holding the log of each of its jobs, from which the marker lines thatCOMMENT
LOWmod/soigneur/flaky-report.sh41# SOIGNEUR_PARALLEL number of runs to collect concurrently (default: 4)COMMENT
LOWmod/soigneur/test.sh1#!/usr/bin/env bashCOMMENT
LOWpkg/imgutil/converter/convert.go21COMMENT
LOWpkg/cmd/image/list.go701// container runs in the tree view.COMMENT
LOWpkg/cmd/image/list.go761// label can carry a "v8"/"8" variant while the manifest platform normalizes to a bareCOMMENT
LOWpkg/cmd/login/login.go221// isEquivalentRegistryHost reports whether acArg, the host value theCOMMENT
LOWpkg/inspecttypes/dockercompat/dockercompat.go301 // TODO IPv6Gateway string // IPv6Gateway holds gateway address specific for IPv6COMMENT
LOWpkg/mountutil/mountutil_linux.go101// https://github.com/moby/moby/pull/45278COMMENT
LOWpkg/mountutil/mountutil_linux.go301 // to set "rprivate" explicitly for preventing this bind mount from unexpectedlyCOMMENT
LOWpkg/apparmorutil/apparmorutil_linux.go81COMMENT
LOWpkg/labels/labels.go121COMMENT
LOWpkg/internal/filesystem/writefile_rename.go21 "errors"COMMENT
LOWpkg/portutil/portutil_linux_test.go21 "net"COMMENT
LOWpkg/portutil/procnet/procnet.go61 for _, i := range array {COMMENT
LOWpkg/resolvconf/resolvconf.go61COMMENT
20 more matches not shown…
Decorative Section Separators6 hits · 18 pts
SeverityFileLineSnippetContext
MEDIUM.github/dependabot.yml1# -----------------------------------------------------------------------------COMMENT
MEDIUM.github/dependabot.yml5# -----------------------------------------------------------------------------COMMENT
MEDIUMextras/rootless/containerd-rootless-setuptool.sh17# -----------------------------------------------------------------------------COMMENT
MEDIUMextras/rootless/containerd-rootless-setuptool.sh22# -----------------------------------------------------------------------------COMMENT
MEDIUMextras/rootless/containerd-rootless.sh17# -----------------------------------------------------------------------------COMMENT
MEDIUMextras/rootless/containerd-rootless.sh22# -----------------------------------------------------------------------------COMMENT
Verbosity Indicators5 hits · 11 pts
SeverityFileLineSnippetContext
LOW⚡…nerdctl/container/container_health_check_linux_test.go1230 // Step 1: Verify timer exists initiallyCOMMENT
LOW⚡…nerdctl/container/container_health_check_linux_test.go1240 // Step 2: Stop containerCOMMENT
LOW⚡…nerdctl/container/container_health_check_linux_test.go1243 // Step 3: Verify timer is removed after stopCOMMENT
LOW⚡…nerdctl/container/container_health_check_linux_test.go1253 // Step 4: Restart containerCOMMENT
LOW⚡…nerdctl/container/container_health_check_linux_test.go1257 // Step 5: Verify timer is recreated after restart - this is our final verificationCOMMENT
Structural Annotation Overuse5 hits · 11 pts
SeverityFileLineSnippetContext
LOW⚡…nerdctl/container/container_health_check_linux_test.go1230 // Step 1: Verify timer exists initiallyCOMMENT
LOW⚡…nerdctl/container/container_health_check_linux_test.go1240 // Step 2: Stop containerCOMMENT
LOW⚡…nerdctl/container/container_health_check_linux_test.go1243 // Step 3: Verify timer is removed after stopCOMMENT
LOW⚡…nerdctl/container/container_health_check_linux_test.go1253 // Step 4: Restart containerCOMMENT
LOW⚡…nerdctl/container/container_health_check_linux_test.go1257 // Step 5: Verify timer is recreated after restart - this is our final verificationCOMMENT
Synthetic Comment Markers1 hit · 8 pts
SeverityFileLineSnippetContext
HIGHpkg/mountutil/volumestore/volumestore.go368 // FIXME: we do not check if the existing volume has the same labels as requested - should we?COMMENT
Example Usage Blocks4 hits · 6 pts
SeverityFileLineSnippetContext
LOWmod/soigneur/flaky-annotate.sh30# Usage:COMMENT
LOWmod/soigneur/flaky-issue.sh26# Usage:COMMENT
LOWmod/soigneur/flaky-report.sh27# Usage:COMMENT
LOWmod/soigneur/test.sh21# Usage:COMMENT
AI Slop Vocabulary2 hits · 4 pts
SeverityFileLineSnippetContext
LOW.github/workflows/job-lint-project.yml2# To run locally, you may just use `make lint` instead, that does the same thingCOMMENT
MEDIUMpkg/cmd/container/run_linux.go240 // (FIXME: find a more robust way to get the current minimum value)COMMENT
Redundant / Tautological Comments2 hits · 3 pts
SeverityFileLineSnippetContext
LOWhack/test-integration.sh39# Set GOTESTSUM_FORMAT to override the format.COMMENT
LOWhack/scripts/lib.sh219# Set GITHUB_TOKEN to use authenticated requests to workaround limitationsCOMMENT
TODO Padding2 hits · 3 pts
SeverityFileLineSnippetContext
LOWpkg/logging/fluentd_logger_test.go66 // TODO: Add test cases.COMMENT
LOWpkg/store/filestore.go29// TODO: implement a read-lock in lockutil, in addition to the current exclusive write-lockCOMMENT