AI Slop Code Risk Monitor

kubernetes-sigs/aws-load-balancer-controller

SlopCodeMonitor badge for kubernetes-sigs/aws-load-balancer-controller Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

A Kubernetes controller for Elastic Load Balancers

0.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for kubernetes-sigs/aws-load-balancer-controller, a Go project with 4,343 GitHub stars. SynthScan examined 310,884 lines of code across 1021 source files, recording 159 pattern matches distributed across 7 syntactic categories. The legacy adjusted pattern signal is 0.7 (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.7
Adjusted Signal
0.7
Raw Pattern Score
100%
Time Factor
2026-10-28
Last Push
4.3K
Stars
Go
Language
310.9K
Lines of Code
1.0K
Files
159
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 3.2/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.5/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 3.3/100 · LOW

Which changes need focused human review? 159 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 3HIGH 0MEDIUM 10LOW 146

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 159 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 Block106 hits · 106 pts
SeverityFileLineSnippetContext
LOWapis/aga/v1beta1/globalaccelerator_types.go61 ToPort int32 `json:"toPort"`COMMENT
LOWapis/aga/v1beta1/globalaccelerator_types.go81 // Client affinity gives you control over whether to always route each client to the same specific endpoint.COMMENT
LOWapis/aga/v1beta1/globalaccelerator_types.go101 // +kubebuilder:validation:MaxLength=255COMMENT
LOWapis/aga/v1beta1/globalaccelerator_types.go121COMMENT
LOWapis/aga/v1beta1/globalaccelerator_types.go161 // EndpointID is the ID of the endpoint when type is EndpointID.COMMENT
LOWapis/aga/v1beta1/globalaccelerator_types.go181 // For more information, see Endpoint Weights in the AWS Global Accelerator Developer Guide:COMMENT
LOWapis/aga/v1beta1/globalaccelerator_types.go201 // Name is the name of the Global Accelerator.COMMENT
LOWapis/elbv2/v1beta1/ingressclassparams_types.go41 LoadBalancerSchemeInternal LoadBalancerScheme = "internal"COMMENT
LOWapis/elbv2/v1beta1/albtargetcontrolconfig_types.go21 metav1 "k8s.io/apimachinery/pkg/apis/meta/v1"COMMENT
LOWapis/elbv2/v1beta1/albtargetcontrolconfig_types.go41 ControlAddress string `json:"controlAddress"`COMMENT
LOWapis/elbv2/v1beta1/albtargetcontrolconfig_types.go61 // By default, the agent generates a private key in memory.COMMENT
LOWapis/elbv2/v1beta1/targetgroupbinding_types.go161 IPAddressType *TargetGroupIPAddressType `json:"ipAddressType,omitempty"`COMMENT
LOWapis/elbv2/v1beta1/targetgroupbinding_types.go181}COMMENT
LOWapis/elbv2/v1alpha1/targetgroupbinding_types.go141 // availability zone of the pod's node instead of "all". Requires iamRoleArnToAssume. Enables in-AZ routingCOMMENT
LOWapis/gateway/v1/listenerruleconfig_types.go101 // of the reserved keywords.COMMENT
LOWapis/gateway/v1/listenerruleconfig_types.go141 UserPoolDomain string `json:"userPoolDomain"`COMMENT
LOWapis/gateway/v1/listenerruleconfig_types.go161 // The name of the cookie used to maintain session information. The default isCOMMENT
LOWapis/gateway/v1/listenerruleconfig_types.go201 // +kubebuilder:validation:MaxItems=10COMMENT
LOWapis/gateway/v1/listenerruleconfig_types.go241 // The user info endpoint of the IdP. This must be a full URL, including the HTTPSCOMMENT
LOWapis/gateway/v1/listenerruleconfig_types.go261 OnUnauthenticatedRequest *AuthenticateOidcActionConditionalBehaviorEnum `json:"onUnauthenticatedRequest,omitempty"`COMMENT
LOWapis/gateway/v1/listenerruleconfig_types.go281}COMMENT
LOWapis/gateway/v1/listenerruleconfig_types.go321// +kubebuilder:validation:XValidation:rule="!has(self.actions) || self.actions.all(a, a.type == 'authenticate-oidc' || COMMENT
LOWapis/gateway/v1/listenerruleconfig_types.go341 // please use the standard Gateway API HTTPRoute or other route resources, which provideCOMMENT
LOWapis/gateway/v1/loadbalancerconfig_types.go121// +kubebuilder:validation:XValidation:rule="!(self.mode == 'verify' && !has(self.trustStore))",message="trustStore is rCOMMENT
LOWapis/gateway/v1/loadbalancerconfig_types.go201 // +kubebuilder:validation:MinLength=1COMMENT
LOWapis/gateway/v1/loadbalancerconfig_types.go221 // +optionalCOMMENT
LOWapis/gateway/v1/loadbalancerconfig_types.go241 // +optionalCOMMENT
LOWapis/gateway/v1/loadbalancerconfig_types.go261COMMENT
LOWapis/gateway/v1/targetgroupconfig_types.go21*/COMMENT
LOWapis/gateway/v1/targetgroupconfig_types.go241 Value string `json:"value"`COMMENT
LOWapis/gateway/v1beta1/listenerruleconfig_types.go101 // of the reserved keywords.COMMENT
LOWapis/gateway/v1beta1/listenerruleconfig_types.go141 UserPoolDomain string `json:"userPoolDomain"`COMMENT
LOWapis/gateway/v1beta1/listenerruleconfig_types.go161 // The name of the cookie used to maintain session information. The default isCOMMENT
LOWapis/gateway/v1beta1/listenerruleconfig_types.go201 // +kubebuilder:validation:MaxItems=10COMMENT
LOWapis/gateway/v1beta1/listenerruleconfig_types.go241 // The user info endpoint of the IdP. This must be a full URL, including the HTTPSCOMMENT
LOWapis/gateway/v1beta1/listenerruleconfig_types.go261 OnUnauthenticatedRequest *AuthenticateOidcActionConditionalBehaviorEnum `json:"onUnauthenticatedRequest,omitempty"`COMMENT
LOWapis/gateway/v1beta1/listenerruleconfig_types.go281}COMMENT
LOWapis/gateway/v1beta1/listenerruleconfig_types.go321// +kubebuilder:validation:XValidation:rule="!has(self.actions) || self.actions.all(a, a.type == 'authenticate-oidc' || COMMENT
LOWapis/gateway/v1beta1/listenerruleconfig_types.go341 // please use the standard Gateway API HTTPRoute or other route resources, which provideCOMMENT
LOWapis/gateway/v1beta1/loadbalancerconfig_types.go121// +kubebuilder:validation:XValidation:rule="!(self.mode == 'verify' && !has(self.trustStore))",message="trustStore is rCOMMENT
LOWapis/gateway/v1beta1/loadbalancerconfig_types.go201 // +kubebuilder:validation:MinLength=1COMMENT
LOWapis/gateway/v1beta1/loadbalancerconfig_types.go221 // +optionalCOMMENT
LOWapis/gateway/v1beta1/loadbalancerconfig_types.go241 // +optionalCOMMENT
LOWapis/gateway/v1beta1/loadbalancerconfig_types.go261COMMENT
LOWapis/gateway/v1beta1/targetgroupconfig_types.go21*/COMMENT
LOWapis/gateway/v1beta1/targetgroupconfig_types.go241 Value string `json:"value"`COMMENT
LOWconfig/crd/kustomization.yaml1# This kustomization.yaml is not intended to be run by itself,COMMENT
LOWhack/sync-rbac-to-helm.sh1#!/usr/bin/env bashCOMMENT
LOWhack/verify-versions.sh1#!/usr/bin/env bashCOMMENT
LOWhack/verify-generate.sh1#!/usr/bin/env bashCOMMENT
LOWhack/install-ko.sh1#!/usr/bin/env bashCOMMENT
LOWhack/verify-crds.sh1#!/usr/bin/env bashCOMMENT
LOWhack/verify-rbac-sync.sh1#!/usr/bin/env bashCOMMENT
LOWhack/tag-release.sh1#!/bin/bash -xeCOMMENT
LOWdocs/examples/cognito-ingress-template.yaml1# Requirements:COMMENT
LOWscripts/ci_e2e_test.sh121}COMMENT
LOWscripts/ci_e2e_test.sh141#COMMENT
LOWscripts/ci_e2e_test.sh261# NoneCOMMENT
LOWscripts/lib/ecr.sh1#!/usr/bin/env bashCOMMENT
LOWscripts/lib/ecr.sh21 fiCOMMENT
46 more matches not shown…
Structural Annotation Overuse28 hits · 44 pts
SeverityFileLineSnippetContext
LOWdocs/guide/ingress/alb-target-agent.md102### Step 1: Install CRDsCOMMENT
LOWdocs/guide/ingress/alb-target-agent.md108### Step 2: Apply Mutating WebhooksCOMMENT
LOWdocs/guide/ingress/alb-target-agent.md125### Step 3: Update RBAC PermissionsCOMMENT
LOWdocs/guide/ingress/alb-target-agent.md146### Step 4: Create ALBTargetControlConfigCOMMENT
LOWdocs/guide/ingress/alb-target-agent.md168### Step 5: Enable ALB Target Control Agent in ControllerCOMMENT
LOWdocs/guide/ingress/alb-target-agent.md181### Step 6: Enable InjectionCOMMENT
LOWdocs/guide/ingress2gateway/migrate_from_ingress.md52## Step 1: Translate ManifestsCOMMENT
LOWdocs/guide/ingress2gateway/migrate_from_ingress.md92## Step 2: Preview with Dry-RunCOMMENT
LOWdocs/guide/ingress2gateway/migrate_from_ingress.md163## Step 3: Apply Gateway ManifestsCOMMENT
LOWdocs/guide/ingress2gateway/migrate_from_ingress.md201## Step 4: Verify Gateway ALBsCOMMENT
LOWdocs/guide/ingress2gateway/migrate_from_ingress.md259## Step 5: Shift TrafficCOMMENT
LOWdocs/guide/ingress2gateway/migrate_from_ingress.md279## Step 6: CleanupCOMMENT
LOWdocs/guide/globalaccelerator/examples.md378#### Step 1: Create the ReferenceGrant ResourcesCOMMENT
LOWdocs/guide/globalaccelerator/examples.md427#### Step 2: Create the GlobalAccelerator Resource with Cross-Namespace ReferencesCOMMENT
LOWdocs/guide/globalaccelerator/aga-controller.md193#### Step 1: Create a ReferenceGrant in the Target NamespaceCOMMENT
LOWdocs/guide/globalaccelerator/aga-controller.md214#### Step 2: Reference the Resource in your GlobalAcceleratorCOMMENT
LOWpkg/deploy/aga/accelerator_manager.go154 // Step 1: Try to disable the accelerator first if it's enabledCOMMENT
LOWpkg/deploy/aga/accelerator_manager.go166 // Step 2: Delete all listeners associated with this acceleratorCOMMENT
LOWpkg/deploy/aga/accelerator_manager.go188 // Step 3: Delete the acceleratorCOMMENT
LOWpkg/deploy/aga/listener_manager.go174 // Step 1: Delete all endpoint groups associated with this listenerCOMMENT
LOWpkg/deploy/aga/listener_manager.go195 // Step 2: Delete the listenerCOMMENT
LOWpkg/deploy/aga/endpoint_group_synthesizer.go106 // Step 1: Collect all desired endpoint ports by region and listenerCOMMENT
LOWpkg/deploy/aga/endpoint_group_synthesizer.go136 // Step 2: Collect all SDK endpoint ports by region and listenerCOMMENT
LOWpkg/deploy/aga/endpoint_group_synthesizer.go156 // Step 3: Find conflicts by comparing different listeners using the same port in the same regionCOMMENT
LOW⚡pkg/ingress2gateway/translate/translate.go100 // Step 1: Merge all ICPs into a fresh spec with conflict detection (ICP-vs-ICP)COMMENT
LOW⚡pkg/ingress2gateway/translate/translate.go107 // Step 2: Apply merged ICP spec on top of annotation-derived LBConfig (ICP wins over annotations)COMMENT
LOWpkg/gateway/routeutils/route_listener_mapper.go111 // Step 1 - Generate initial state maps, to allow for quick calculations.COMMENT
LOWpkg/gateway/routeutils/route_listener_mapper.go162 // Step 2 - Go through each route and each parent ref on the route.COMMENT
Hallucination Indicators3 hits · 30 pts
SeverityFileLineSnippetContext
CRITICALpkg/deploy/elbv2/target_group_binding_manager.go201 tgARN, err := resTGB.Spec.Template.Spec.TargetGroupARN.Resolve(ctx)CODE
CRITICALpkg/deploy/elbv2/target_group_binding_synthesizer.go133 tgARN, err := resTGB.Spec.Template.Spec.TargetGroupARN.Resolve(ctx)CODE
CRITICALpkg/model/elbv2/k8s/target_group_binding.go44 for _, dep := range tgb.Spec.Template.Spec.TargetGroupARN.Dependencies() {CODE
Modern AI Meta-Vocabulary6 hits · 22 pts
SeverityFileLineSnippetContext
MEDIUMmain.go82 // +kubebuilder:scaffold:importsCOMMENT
MEDIUMmain.go97 // +kubebuilder:scaffold:schemeCOMMENT
MEDIUMmain.go499 //+kubebuilder:scaffold:builderCOMMENT
MEDIUM⚡config/crd/kustomization.yaml9# +kubebuilder:scaffold:crdkustomizeresourceCOMMENT
MEDIUM⚡config/crd/kustomization.yaml16# +kubebuilder:scaffold:crdkustomizewebhookpatchCOMMENT
MEDIUM⚡config/crd/kustomization.yaml22# +kubebuilder:scaffold:crdkustomizecainjectionpatchCOMMENT
Verbosity Indicators11 hits · 18 pts
SeverityFileLineSnippetContext
LOWpkg/deploy/aga/accelerator_manager.go154 // Step 1: Try to disable the accelerator first if it's enabledCOMMENT
LOWpkg/deploy/aga/accelerator_manager.go166 // Step 2: Delete all listeners associated with this acceleratorCOMMENT
LOWpkg/deploy/aga/accelerator_manager.go188 // Step 3: Delete the acceleratorCOMMENT
LOWpkg/deploy/aga/listener_manager.go174 // Step 1: Delete all endpoint groups associated with this listenerCOMMENT
LOWpkg/deploy/aga/listener_manager.go195 // Step 2: Delete the listenerCOMMENT
LOWpkg/deploy/aga/endpoint_group_synthesizer.go106 // Step 1: Collect all desired endpoint ports by region and listenerCOMMENT
LOWpkg/deploy/aga/endpoint_group_synthesizer.go136 // Step 2: Collect all SDK endpoint ports by region and listenerCOMMENT
LOWpkg/deploy/aga/endpoint_group_synthesizer.go156 // Step 3: Find conflicts by comparing different listeners using the same port in the same regionCOMMENT
LOW⚡pkg/ingress2gateway/translate/translate.go100 // Step 1: Merge all ICPs into a fresh spec with conflict detection (ICP-vs-ICP)COMMENT
LOW⚡pkg/ingress2gateway/translate/translate.go107 // Step 2: Apply merged ICP spec on top of annotation-derived LBConfig (ICP wins over annotations)COMMENT
LOWpkg/gateway/routeutils/listener_set.go119 // Getting here means that the ListenerSet has requested attachment, we need to check if Gateway allows it.COMMENT
Self-Referential Comments4 hits · 12 pts
SeverityFileLineSnippetContext
MEDIUMcrd-ref-docs.yaml1# This file contains configuration for our reference docs generation. For moreCOMMENT
MEDIUMconfig/crd/kustomizeconfig.yaml1# This file is for teaching kustomize how to substitute name and namespace reference in CRDCOMMENT
MEDIUM…s-load-balancer-controller/templates/cert-manager.yaml2# Create a selfsigned Issuer, in order to create a root CA certificate forCOMMENT
MEDIUM…s-load-balancer-controller/templates/cert-manager.yaml33# Create an Issuer that uses the above generated CA certificate to issue certsCOMMENT
Hyper-Verbose Identifiers1 hit · 1 pts
SeverityFileLineSnippetContext
LOW…s/theme_overrides/assets/javascripts/version-select.js31 function setupVersionSelectEventHandlers() {CODE