AI Slop Code Risk Monitor

cilium/ebpf

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

ebpf-go is a pure-Go library to read, modify and load eBPF programs and attach them to various hooks in the Linux kernel.

1.6 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for cilium/ebpf, a Go project with 8,024 GitHub stars. SynthScan examined 84,513 lines of code across 520 source files, recording 134 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 1.6 (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.6
Adjusted Signal
1.6
Raw Pattern Score
100%
Time Factor
2026-10-29
Last Push
8.0K
Stars
Go
Language
84.5K
Lines of Code
520
Files
134
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 7.8/100 · LOW

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

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

PR Review Velocity Impact 7.7/100 · LOW

Which changes need focused human review? 134 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 133

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 134 distinct pattern matches across 4 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 Block131 hits · 131 pts
SeverityFileLineSnippetContext
LOWmemory.go21COMMENT
LOWprog.go61const maxVerifierLogSize = math.MaxUint32 >> 2COMMENT
LOWprog.go81 // Unless LogDisabled is set, setting this to a non-zero value will enable the verifierCOMMENT
LOWprog.go121 //COMMENT
LOWprog.go141COMMENT
LOWprog.go221 return trueCOMMENT
LOWprog.go241// Diagnostics were introduced in Linux 7.3 and include human-readable adviceCOMMENT
LOWprog.go261COMMENT
LOWprog.go861 //COMMENT
LOWprog.go881COMMENT
LOWprog.go1061 if errors.Is(err, unix.EINTR) {COMMENT
LOWtypes.go21 // ProgramArray - A program array map is a special kind of array map whose mapCOMMENT
LOWtypes.go41 // GetStackIDCOMMENT
LOWtypes.go81 // Queue - FIFO storage for BPF programs.COMMENT
LOWexample_sock_extract_dist_test.go1//go:build linuxCOMMENT
LOWexample_sock_extract_dist_test.go21// this software without specific prior written permission.COMMENT
LOWcollection.go21COMMENT
LOWcollection.go101}COMMENT
LOWcollection.go161// if this sounds useful.COMMENT
LOWcollection.go821 }COMMENT
LOWcollection.go841// struct {COMMENT
LOWdoc.go1// Package ebpf is a toolkit for working with eBPF programs.COMMENT
LOWdoc.go21//COMMENT
LOWmemory_unsafe.go21// In Go, the programmer should not have to worry about freeing memory. SinceCOMMENT
LOWmemory_unsafe.go61 }COMMENT
LOWmemory_unsafe.go121 // Align the pointer to a page boundary within the allocation. This may aliasCOMMENT
LOWmemory_unsafe.go141 // new and only reference to the backing array.COMMENT
LOWmemory_unsafe.go181// unmap returns a function that takes a pointer to a memory-mapped region onCOMMENT
LOWmemory_unsafe.go321}COMMENT
LOWstruct_ops.go61 if !ok {COMMENT
LOWmap.go361}COMMENT
LOWmap.go1221 err := m.lookup(randKey, valuePtr, 0)COMMENT
LOWmap.go1241//COMMENT
LOWmap.go1801// also abort with an error, see IsIterationAborted.COMMENT
LOWinfo.go21COMMENT
LOWinfo.go181//COMMENT
LOWinfo.go201// Available from 4.10.COMMENT
LOWinfo.go221// Will contain mostly zero values if the collection of statistics is notCOMMENT
LOWinfo.go641 bytes.NewReader(pi.lineInfos),COMMENT
LOWinfo.go661// If available, the instructions will be annotated with metadata from theCOMMENT
LOWinfo.go761 return int(pi.numInsns), nilCOMMENT
LOWinfo.go781}COMMENT
LOWinfo.go821//COMMENT
LOWinfo.go841//COMMENT
LOWcmd/bpf2go/doc.go1//go:build !windowsCOMMENT
LOWcmd/bpf2go/gen/target.go101// GoArches.COMMENT
LOWtestdata/common.h21#define __type(name, val) typeof(val) *nameCOMMENT
LOWasm/opcode.go61func (cls Class) IsJump() bool {COMMENT
LOWasm/opcode.go81//COMMENT
LOWasm/alu.go1package asmCOMMENT
LOWasm/alu.go41//COMMENT
LOWasm/instruction_test.go161 // ; abc = 42COMMENT
LOWfeatures/prog.go221})COMMENT
LOWfeatures/doc.go1// Package features allows probing for BPF features available to the calling process.COMMENT
LOWinternal/prog.go1package internalCOMMENT
LOWinternal/feature.go61 done boolCOMMENT
LOWinternal/errors.go121}COMMENT
LOWinternal/errors.go141//COMMENT
LOWinternal/sysenc/marshal.go141 // code so that the panic isn't reachable.COMMENT
LOWinternal/sysenc/buffer.go21 }COMMENT
71 more matches not shown…
Modern AI Meta-Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMdocs/ebpf/guides/getting-started.md118## Compile eBPF C and generate scaffolding using bpf2goCOMMENT
Redundant / Tautological Comments1 hit · 2 pts
SeverityFileLineSnippetContext
LOWscripts/windows/setup.sh9# Check if ISO path is providedCOMMENT
AI Structural Patterns1 hit · 1 pts
SeverityFileLineSnippetContext
LOWdocs/macros.py147CODE