AI Slop Code Risk Monitor

opencontainers/runc

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

CLI tool for spawning and running containers according to the OCI specification

2.4 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for opencontainers/runc, a Go project with 13,519 GitHub stars. SynthScan examined 44,973 lines of code across 267 source files, recording 89 pattern matches distributed across 5 syntactic categories. The legacy adjusted pattern signal is 2.4 (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.4
Adjusted Signal
2.4
Raw Pattern Score
100%
Time Factor
2026-10-31
Last Push
13.5K
Stars
Go
Language
45.0K
Lines of Code
267
Files
89
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 11.4/100 · LOW

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

Which changes need focused human review? 89 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 5LOW 83

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 89 distinct pattern matches across 5 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 Block77 hits · 77 pts
SeverityFileLineSnippetContext
LOWtypes/features/features.go1// Package features provides the annotations for [github.com/opencontainers/runtime-spec/specs-go/features].COMMENT
LOWtests/rootless.sh1#!/bin/bashCOMMENT
LOWtests/rootless.sh121 chmod g+rw "$CGROUP_MOUNT/$CGROUP_PATH/cgroup.subtree_control" "$CGROUP_MOUNT/$CGROUP_PATH/cgroup.procs" "$CGROUP_MOUNCOMMENT
LOWtests/rootless.sh201 # Run the test suite!COMMENT
LOWtests/fuzzing/oss_fuzz_build.sh1#!/usr/bin/env bashCOMMENT
LOWtests/integration/bootstrap-get-images.sh21COMMENT
LOWtests/integration/helpers.bash201 [ $EUID -ne 0 ] && user="--user"COMMENT
LOWtests/integration/helpers.bash981 # Older EL9 kernels did not permit using ID map mountsCOMMENT
LOWtests/integration/get-images.sh1#!/bin/bashCOMMENT
LOWtests/integration/testdata/seccomp_syscall_test1.c1#define _GNU_SOURCECOMMENT
LOWtests/integration/lib/assert.bash1#!/bin/bashCOMMENT
LOWinternal/pathrs/mkdirall_pathrslite.go21import (COMMENT
LOWinternal/pathrs/path.go81 // do nothingCOMMENT
LOWinternal/sys/doc.go1// Package sys is an internal package that contains helper methods for dealingCOMMENT
LOWinternal/third_party/systemd/activation/files_unix.go1// Copyright 2015 CoreOS, Inc.COMMENT
LOWscript/release_sign.sh1#!/bin/bashCOMMENT
LOWscript/keyring_validate.sh1#!/bin/bashCOMMENT
LOWscript/keyring_validate.sh81 username="$(sed -En "s|^Comment:.* github=(\w+).*|\1|p" <<<"$block")"COMMENT
LOWscript/build-libpathrs.sh1#!/bin/bashCOMMENT
LOWscript/keyring_addkey.sh1#!/bin/bashCOMMENT
LOWscript/check-binary-size.sh1#!/bin/bashCOMMENT
LOWscript/release_build.sh1#!/bin/bashCOMMENT
LOW.github/zizmor.yml1# Configuration for zizmor (https://docs.zizmor.sh/), run by the zizmor jobCOMMENT
LOW.github/workflows/review-policy.yml1# Enforce the pull request merge rules described in MAINTAINERS_GUIDE.mdCOMMENT
LOW.github/workflows/review-policy.yml21# request, so a pull request can change it. Therefore it is a governance fileCOMMENT
LOWlibcontainer/init_wait_linux.go21// meaning it will never write anything to us again.COMMENT
LOWlibcontainer/init_wait_linux.go61// Should the pid get recycled while we are polling, init is gone entirely,COMMENT
LOWlibcontainer/setns_init_linux.go141 // Close the pipe to signal that we have completed our init.COMMENT
LOWlibcontainer/rootfs_linux.go681 // contrast to mount(8)'s current behaviour, but is what users probablyCOMMENT
LOWlibcontainer/rootfs_linux.go701 // only difference from mount(8) is that we do thisCOMMENT
LOWlibcontainer/rootfs_linux.go741 }COMMENT
LOWlibcontainer/rootfs_linux.go1201}COMMENT
LOWlibcontainer/sync.go21//COMMENT
LOWlibcontainer/factory_linux.go181// the following characters:COMMENT
LOWlibcontainer/mount_linux.go141// in case it failed.COMMENT
LOWlibcontainer/mount_linux.go241COMMENT
LOWlibcontainer/mount_linux.go261COMMENT
LOWlibcontainer/standard_init_linux.go301 // (which can then be opened by container processes, leading to containerCOMMENT
LOWlibcontainer/container_linux.go581 // ExtraFiles otherwise it is possible for the stdlib to clobber the fdCOMMENT
LOWlibcontainer/cmd_clone.go1package libcontainerCOMMENT
LOWlibcontainer/process.go21//COMMENT
LOWlibcontainer/process.go61COMMENT
LOWlibcontainer/process.go101 // LogLevel is a string containing a numeric representation of the currentCOMMENT
LOWlibcontainer/process_linux.go201 // cpuset.cpus, online or even present (hot-plugged) at callCOMMENT
LOWlibcontainer/process_linux.go301 return fmt.Errorf("error adding pid %d to cgroups: %w", p.pid(), err)COMMENT
LOWlibcontainer/init_linux.go441}COMMENT
LOWlibcontainer/init_linux.go521 if err := unix.Fstat(int(file.Fd()), &s); err != nil {COMMENT
LOWlibcontainer/internal/userns/usernsfd_linux.go81 // execve() is a waste of cycles because we just need some process to haveCOMMENT
LOWlibcontainer/utils/utils_unix.go101// UnsafeCloseFrom closes all file descriptors greater or equal to minFd in theCOMMENT
LOWlibcontainer/utils/utils_unix.go161 }COMMENT
LOWlibcontainer/utils/utils_unix.go181 // /proc/thread-self/, but it's better to be safe than sorry (and there areCOMMENT
LOWlibcontainer/specconv/spec_linux.go221// all containers.COMMENT
LOWlibcontainer/specconv/spec_linux.go1081 // can calculate uid and gid mappings within runc. These mappings areCOMMENT
LOWlibcontainer/system/proc.go81 if err != nil {COMMENT
LOWlibcontainer/intelrdt/intelrdt.go621 // which means L3 cache id 0's CBM is 0xff, and L3 cache id 1's CBMCOMMENT
LOWlibcontainer/intelrdt/intelrdt.go641 // predefined and can be looked up through "info/MB/min_bandwidth".COMMENT
LOWlibcontainer/exeseal/cloned_binary_linux.go61 return os.NewSyscallError("fcntl(F_ADD_SEALS)", err)COMMENT
LOWlibcontainer/exeseal/overlayfs_linux.go41COMMENT
LOWlibcontainer/exeseal/overlayfs_linux.go61COMMENT
LOWlibcontainer/exeseal/overlayfs_linux.go101 }COMMENT
17 more matches not shown…
Self-Referential Comments5 hits · 15 pts
SeverityFileLineSnippetContext
MEDIUMtests/rootless.sh62 # Create a directory owned by $ROOTLESS_AUX_UID inside container, to be usedCOMMENT
MEDIUMtests/rootless.sh115 # Create the cgroup.COMMENT
MEDIUMtests/rootless.sh174# Create a powerset of $ALL_FEATURES (the set of all subsets of $ALL_FEATURES).COMMENT
MEDIUMtests/fuzzing/oss_fuzz_build.sh3# This file is only meant to be run by OSS-fuzz and will not workCOMMENT
MEDIUMscript/keyring_validate.sh48# Create a dummy gpg keyring from the set of MAINTAINERS.COMMENT
Redundant / Tautological Comments5 hits · 8 pts
SeverityFileLineSnippetContext
LOWtests/integration/helpers.bash279# Check if a value in a cgroup file $1 matches $2 or $3 (if specified).COMMENT
LOWtests/integration/helpers.bash290# Check if a value of systemd unit property $1 matches $2 or $3 (if specified).COMMENT
LOWtests/integration/helpers.bash487# Check if criu is available.COMMENT
LOWtests/integration/helpers.bash492# Check if criu version is at least $1 (e.g. "4.3").COMMENT
LOWtests/integration/helpers.bash778 # Check if the pid is there; if not, remove it from the list.COMMENT
Synthetic Comment Markers1 hit · 8 pts
SeverityFileLineSnippetContext
HIGHlibcontainer/rootfs_linux.go283 // by mountPropagate. Remount them read-only as requested.COMMENT
Slop Phrases1 hit · 2 pts
SeverityFileLineSnippetContext
LOW.github/workflows/validate.yml174 # make sure to remove the old versionCOMMENT