AI Slop Code Risk Monitor

openshift/origin

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

Conformance test suite for OpenShift

0.8 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for openshift/origin, a Go project with 8,691 GitHub stars. SynthScan examined 748,998 lines of code across 3870 source files, recording 413 pattern matches distributed across 15 syntactic categories. The legacy adjusted pattern signal is 0.8 (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.8
Adjusted Signal
0.8
Raw Pattern Score
100%
Time Factor
2026-10-30
Last Push
8.7K
Stars
Go
Language
749.0K
Lines of Code
3.9K
Files
413
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.6/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.2/100 · LOW

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

Agent Over-Engineering Ratio 0.3/100 · LOW

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

PR Review Velocity Impact 3.5/100 · LOW

Which changes need focused human review? 413 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 45LOW 365

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 413 distinct pattern matches across 15 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 Block222 hits · 220 pts
SeverityFileLineSnippetContext
LOWdoc.go1// This is the source repository for OpenShift Origin - the best way to build, manage, and deployCOMMENT
LOWtools/junitreport/pkg/parser/stack/parser.go21 }COMMENT
LOWtest/shared/updateservice/updateservice.go1// Package updateservice deploys a fake Cincinnati update service (a podCOMMENT
LOWtest/extended/testdata/cmd/test/cmd/images.sh41#os::cmd::expect_success_and_text "oc get imageStreams test --template='{{.status.dockerImageRepository}}'" 'test'COMMENT
LOWtest/extended/testdata/cmd/test/cmd/images.sh61#os::cmd::expect_success 'oc create imagestream test'COMMENT
LOWtest/extended/testdata/cmd/test/cmd/images.sh241#os::cmd::expect_success "oc tag test:new newrepo:direct"COMMENT
LOWtest/extended/testdata/cmd/test/cmd/authentication.sh21## Logging in prints useful messagesCOMMENT
LOWtest/extended/testdata/cmd/test/cmd/authentication.sh41#os::cmd::expect_success_and_text "oc policy can-i --list -n '${project}' --as=scoped-user" 'get.*pods'COMMENT
LOWtest/extended/testdata/cmd/test/cmd/authentication.sh61#adminnonescalatingpowerstoken="$(oc process -f "${OS_ROOT}/test/testdata/authentication/scoped-token-template.yaml" TOKCOMMENT
LOWtest/extended/testdata/cmd/test/cmd/authentication.sh81#os::cmd::expect_success_and_text "oc policy can-i create subjectaccessreviews.authorization.openshift.io --token='${accCOMMENT
LOWtest/extended/testdata/cmd/hack/lib/cmd.sh161os_cmd_internal_tmpout="${os_cmd_internal_tmpdir}/tmp_stdout.log"COMMENT
LOWtest/extended/testdata/cmd/hack/lib/cmd.sh461# Globals:COMMENT
LOWtest/extended/testdata/cmd/hack/lib/cmd.sh541#COMMENT
LOWtest/extended/testdata/cmd/hack/lib/test/junit.sh1#!/usr/bin/env bashCOMMENT
LOWtest/extended/testdata/cmd/hack/lib/test/junit.sh21 export NUM_OS_JUNIT_SUITES_IN_FLIGHTCOMMENT
LOWtest/extended/testdata/cmd/hack/lib/test/junit.sh101}COMMENT
LOWtest/extended/testdata/cmd/hack/lib/test/junit.sh141 for (( i = 0; i < ${NUM_OS_JUNIT_SUITES_IN_FLIGHT:-0}; i++ )); doCOMMENT
LOWtest/extended/testdata/cmd/hack/lib/util/trap.sh1#!/usr/bin/env bashCOMMENT
LOWtest/extended/testdata/cmd/hack/lib/util/trap.sh61 if [[ "${OS_USE_STACKTRACE:-}" = "true" ]]; thenCOMMENT
LOWtest/extended/testdata/cmd/hack/lib/util/environment.sh1#!/usr/bin/env bashCOMMENT
LOWtest/extended/testdata/cmd/hack/lib/util/environment.sh41# os::util::environment::setup_all_server_vars sets up all environment variables necessary to configure and start an OpeCOMMENT
LOWtest/extended/testdata/cmd/hack/lib/util/environment.sh61# - USE_IMAGESCOMMENT
LOWtest/extended/testdata/cmd/hack/lib/util/environment.sh81# - export API_SCHEMECOMMENT
LOWtest/extended/testdata/cmd/hack/lib/util/environment.sh121# - TMPDIRCOMMENT
LOWtest/extended/testdata/cmd/hack/lib/util/environment.sh181# os::util::environment::setup_etcd_vars sets up environment variables necessary for interacting with etcdCOMMENT
LOWtest/extended/testdata/cmd/hack/lib/util/environment.sh201 export ETCD_PEER_PORTCOMMENT
LOWtest/extended/testdata/cmd/hack/lib/util/environment.sh261 export ETCD_CA_BUNDLECOMMENT
LOWtest/extended/testdata/cmd/hack/lib/util/misc.sh1#!/usr/bin/env bashCOMMENT
LOWtest/extended/testdata/cmd/hack/lib/util/misc.sh41# Arguments:COMMENT
LOWtest/extended/testdata/cmd/hack/lib/util/misc.sh141 if [[ "$(go env GOHOSTOS)" == "darwin" ]]; thenCOMMENT
LOWtest/extended/testdata/cmd/hack/lib/log/output.sh1#!/usr/bin/env bashCOMMENT
LOWtest/extended/testdata/cmd/hack/lib/log/output.sh61# Globals:COMMENT
LOWtest/extended/testdata/cmd/hack/lib/log/system.sh1#!/usr/bin/env bashCOMMENT
LOWtest/extended/testdata/cmd/hack/lib/log/system.sh21# This function stops logging and generates plots of data for easy consumption.COMMENT
LOWtest/extended/testdata/cmd/hack/lib/log/system.sh121 # for the proper flag format for 'cut', we join the list delimiting with commasCOMMENT
LOWtest/extended/testdata/cmd/hack/lib/log/system.sh221COMMENT
LOWtest/extended/testdata/cmd/hack/lib/log/stacktrace.sh1#!/usr/bin/env bashCOMMENT
LOWtest/extended/testdata/cmd/hack/lib/log/stacktrace.sh21COMMENT
LOW…/extended/edge_topologies/tnf_node_replacement_flow.go281// prefix where the gateway is the predictable ".1" / "::1" style address on that segment (IPv4: last octet 1;COMMENT
LOW…/extended/edge_topologies/tnf_node_replacement_flow.go401COMMENT
LOW…/extended/edge_topologies/tnf_node_replacement_flow.go1181// Phase 1: stonith confirm --force (Preferred)COMMENT
LOW…/extended/edge_topologies/tnf_node_replacement_flow.go1741//COMMENT
LOW…xtended/edge_topologies/tnf_node_replacement_ovn_vm.go1121COMMENT
LOWtest/extended/edge_topologies/tnf_etcd_disruption.go101//COMMENT
LOWtest/extended/edge_topologies/tnf_etcd_disruption.go661 g.By("Verifying pcs status shows etcd-clone Started on both nodes")COMMENT
LOWtest/extended/edge_topologies/tnf_etcd_disruption.go781 // that a learner member exists in etcd but the learner_node attribute is missing,COMMENT
LOWtest/extended/edge_topologies/two_node.go1// Package edge_topologies contains end-to-end tests for two-node (DualReplica) OpenShift clusters.COMMENT
LOWtest/extended/edge_topologies/utils/common.go221 return skipReasonsCOMMENT
LOWtest/extended/edge_topologies/utils/common.go461// IsClusterHealthyWithTimeout checks if the cluster is in a healthy state with a configurable timeout.COMMENT
LOW…topologies/utils/apis/pacemaker_fencing_credentials.go41COMMENT
LOWtest/extended/cluster/utils.go481// for _, v := range pods.Items {COMMENT
LOWtest/extended/operators/daemon_set.go21var _ = g.Describe("[sig-arch] Managed cluster", func() {COMMENT
LOWtest/extended/operators/operators.go301 // compute, running the post-unpause compute-settling monitor, andCOMMENT
LOWtest/extended/util/framework.go401COMMENT
LOWtest/extended/util/framework.go2321 if err != nil {COMMENT
LOWtest/extended/util/conditions.go41 }COMMENT
LOWtest/extended/util/compat_otp/terraform.go21 tfbin *tfexec.TerraformCOMMENT
LOWtest/extended/util/compat_otp/ccoctl.go21//COMMENT
LOWtest/extended/util/compat_otp/test.go181 return string(auth.Spec.Type) == string(configv1.AuthenticationTypeOIDC), nilCOMMENT
LOWtest/extended/util/compat_otp/test.go401 // default:COMMENT
162 more matches not shown…
Structural Annotation Overuse61 hits · 108 pts
SeverityFileLineSnippetContext
LOW⚡…/extended/edge_topologies/tnf_node_replacement_flow.go468 // Step 0: Restore BMC credentials before long-running VM work so BMO never sees a host without a Secret while we recovCOMMENT
LOW⚡…/extended/edge_topologies/tnf_node_replacement_flow.go475 // Step 1: Recreate the VM from backupCOMMENT
LOW⚡…/extended/edge_topologies/tnf_node_replacement_flow.go486 // Step 2: Best-effort restore etcd member Secrets from backup. recoverEtcdSecretsFromBackup does notCOMMENT
LOW⚡…/extended/edge_topologies/tnf_node_replacement_flow.go494 // Step 3: Recreate BMH from backup (no detached so Ironic can provision). Machine is created after BMH provisions.COMMENT
LOW⚡…/extended/edge_topologies/tnf_node_replacement_flow.go504 // Step 4: Wait for BMH provisioning.COMMENT
LOW⚡…/extended/edge_topologies/tnf_node_replacement_flow.go514 // Step 5: Apply detached annotation now that the host is provisioned.COMMENT
LOW⚡…/extended/edge_topologies/tnf_node_replacement_flow.go521 // Step 6: Recreate Machine from backup (after BMH has provisioned).COMMENT
LOW⚡…/extended/edge_topologies/tnf_node_replacement_flow.go531 // Step 7: Wait for node to register; approve node-bootstrapper CSR when machine-approver does not (reused node name).COMMENT
LOW⚡…/extended/edge_topologies/tnf_node_replacement_flow.go571 // Step 10: Trace→Normal operator log level bump triggers a new revision so static-pod installers re-materializeCOMMENT
LOW⚡…/extended/edge_topologies/tnf_node_replacement_flow.go579 // Step 11: Clear pacemaker fencing/cleanup state on the survivor after disruptive work.COMMENT
LOW…/extended/edge_topologies/tnf_node_replacement_flow.go1217 // Step 1: Verify the VM no longer exists before confirming fencingCOMMENT
LOW…/extended/edge_topologies/tnf_node_replacement_flow.go1244 // Step 2: Confirm the fencing of the target nodeCOMMENT
LOW…/extended/edge_topologies/tnf_node_replacement_flow.go1267 // Step 3: Wait for etcd to start after stonith confirm (poll every 30s; cap etcdPhase1StartAfterStonithTimeout).COMMENT
LOW…xtended/edge_topologies/tnf_node_replacement_finish.go69 // Step 1: Verify both nodes are in Ready stateCOMMENT
LOW…xtended/edge_topologies/tnf_node_replacement_finish.go82 // Step 2: Verify all cluster operators are available (not degraded or progressing)COMMENT
LOW…topologies/utils/apis/pacemaker_fencing_credentials.go194 //Step 1: Get an initial list of pods. The resourceVersion from this list is the "starting point" for the watch.COMMENT
LOW⚡…topologies/utils/apis/pacemaker_fencing_credentials.go225 // Step 2: Check all existing pods first. If any of them show the desired result, we're done.COMMENT
LOW⚡…topologies/utils/apis/pacemaker_fencing_credentials.go232 // Step 3: Watch for new pods and follow their logs until we see the desired result or timeout.COMMENT
LOW…topologies/utils/apis/pacemaker_fencing_credentials.go245 // Step 4: Wait for new/updated pods and check each one until we find the desired result or timeout.COMMENT
LOW⚡test/extended/apiserverauth/apiserver_util.go1831 // Step 1: Retrieve current secret countCOMMENT
LOW⚡test/extended/apiserverauth/apiserver_util.go1839 // Step 2: Create secrets and check if quota limit is reachedCOMMENT
LOW⚡test/extended/apiserverauth/apiserver_util.go1847 // Step 3: Expect failure when reaching the quota limitCOMMENT
LOWtest/extended/networking/kubevirt/console.go59// NOTE: This functions heritage limitations from `expectBatchWithValidatedSend` refer to it to check them.COMMENT
LOWtest/extended/networking/kubevirt/console.go68// NOTE: This functions inherits limitations from `expectBatchWithValidatedSend`, refer to it for more information.COMMENT
LOW⚡test/extended/node/node_utils.go468 // Step 4: Wait for CSV to be readyCOMMENT
LOW⚡test/extended/node/node_utils.go475 // Step 5: Create HyperConverged CRCOMMENT
LOW⚡test/extended/node/node_utils.go497 // Step 6: Wait for HyperConverged to be readyCOMMENT
LOW⚡test/extended/node/node_utils.go504 // Step 7: Label worker nodes for CNVCOMMENT
LOW⚡test/extended/node/node_utils.go511 // Step 8: Wait for MCP rollout to complete (if any MachineConfigs were applied)COMMENT
LOW⚡test/extended/node/node_utils.go818 // Step 2: Delete SubscriptionCOMMENT
LOW⚡test/extended/node/node_utils.go825 // Step 3: Delete all CSVs in the namespaceCOMMENT
LOW⚡test/extended/node/node_utils.go834 // Step 4: Delete OperatorGroupCOMMENT
LOW⚡test/extended/node/node_utils.go841 // Step 5: Remove node labelsCOMMENT
LOW⚡test/extended/node/node_utils.go845 // Step 6: Delete namespaceCOMMENT
LOWtest/extended/node/node_utils.go378 // Step 1: Create CNV namespace with Pod Security labelsCOMMENT
LOWtest/extended/node/node_utils.go420 // Step 2: Create OperatorGroupCOMMENT
LOWtest/extended/node/node_utils.go442 // Step 3: Create SubscriptionCOMMENT
LOWtest/extended/node/node_utils.go783 // Step 1: Delete HyperConverged CRCOMMENT
LOWtest/extended/node/node_utils.go863 // Step 7: Wait for MCP rollout to complete (if any MachineConfigs were removed)COMMENT
LOW⚡…st/extended/node/dra/nvidia/prerequisites_installer.go53 // Step 1: Validate GPU Operator is already installedCOMMENT
LOW⚡…st/extended/node/dra/nvidia/prerequisites_installer.go61 // Step 2: Wait for GPU Operator to be readyCOMMENT
LOW⚡…st/extended/node/dra/nvidia/prerequisites_installer.go68 // Step 3: Check if DRA Driver already installed (skip if present)COMMENT
LOW⚡…st/extended/node/dra/nvidia/prerequisites_installer.go72 // Step 4: Ensure Helm is availableCOMMENT
LOW⚡…st/extended/node/dra/nvidia/prerequisites_installer.go77 // Step 5: Add NVIDIA Helm repositoryCOMMENT
LOW⚡…st/extended/node/dra/nvidia/prerequisites_installer.go82 // Step 6: Install DRA Driver (latest version)COMMENT
LOW⚡…st/extended/node/dra/nvidia/prerequisites_installer.go90 // Step 7: Wait for DRA Driver to be readyCOMMENT
LOW…st/extended/node/dra/nvidia/prerequisites_installer.go288 // Step 1: Uninstall Helm releaseCOMMENT
LOW…st/extended/node/dra/nvidia/prerequisites_installer.go299 // Step 2: Delete ClusterRoleBindings created by grantSCCPermissionsCOMMENT
LOW…st/extended/node/dra/nvidia/prerequisites_installer.go316 // Step 3: Remove DRA kubelet plugin labels from GPU nodesCOMMENT
LOW…st/extended/node/dra/nvidia/prerequisites_installer.go334 // Step 4: Delete namespaceCOMMENT
LOW…st/extended/node/dra/nvidia/prerequisites_installer.go350 // Step 1: Delete ClusterRoleBindingsCOMMENT
LOW…st/extended/node/dra/nvidia/prerequisites_installer.go367 // Step 2: Remove DRA kubelet plugin labels from GPU nodesCOMMENT
LOW…st/extended/node/dra/nvidia/prerequisites_installer.go385 // Step 3: Delete namespaceCOMMENT
LOWtest/extended/node/dra/nvidia/README.md121### Step 1: Add NVIDIA Helm RepositoryCOMMENT
LOWtest/extended/node/dra/nvidia/README.md128### Step 2: Label GPU NodesCOMMENT
LOWtest/extended/node/dra/nvidia/README.md142### Step 3: Install DRA DriverCOMMENT
LOWtest/extended/node/dra/nvidia/README.md178### Step 4: Verify InstallationCOMMENT
LOW⚡pkg/test/ginkgo/queue_test.go1017 // Step 1: Get test1 and mark it as running (but don't run it yet to keep conflict active)COMMENT
LOW⚡pkg/test/ginkgo/queue_test.go1024 // Step 2: Try to get next test while test1 is "running"COMMENT
LOW⚡pkg/test/ginkgo/queue_test.go1031 // Step 3: Clean up test1's conflict (simulate test1 completing)COMMENT
1 more matches not shown…
Verbosity Indicators55 hits · 100 pts
SeverityFileLineSnippetContext
LOW⚡…/extended/edge_topologies/tnf_node_replacement_flow.go468 // Step 0: Restore BMC credentials before long-running VM work so BMO never sees a host without a Secret while we recovCOMMENT
LOW⚡…/extended/edge_topologies/tnf_node_replacement_flow.go475 // Step 1: Recreate the VM from backupCOMMENT
LOW⚡…/extended/edge_topologies/tnf_node_replacement_flow.go486 // Step 2: Best-effort restore etcd member Secrets from backup. recoverEtcdSecretsFromBackup does notCOMMENT
LOW⚡…/extended/edge_topologies/tnf_node_replacement_flow.go494 // Step 3: Recreate BMH from backup (no detached so Ironic can provision). Machine is created after BMH provisions.COMMENT
LOW⚡…/extended/edge_topologies/tnf_node_replacement_flow.go504 // Step 4: Wait for BMH provisioning.COMMENT
LOW⚡…/extended/edge_topologies/tnf_node_replacement_flow.go514 // Step 5: Apply detached annotation now that the host is provisioned.COMMENT
LOW⚡…/extended/edge_topologies/tnf_node_replacement_flow.go521 // Step 6: Recreate Machine from backup (after BMH has provisioned).COMMENT
LOW⚡…/extended/edge_topologies/tnf_node_replacement_flow.go531 // Step 7: Wait for node to register; approve node-bootstrapper CSR when machine-approver does not (reused node name).COMMENT
LOW⚡…/extended/edge_topologies/tnf_node_replacement_flow.go571 // Step 10: Trace→Normal operator log level bump triggers a new revision so static-pod installers re-materializeCOMMENT
LOW⚡…/extended/edge_topologies/tnf_node_replacement_flow.go579 // Step 11: Clear pacemaker fencing/cleanup state on the survivor after disruptive work.COMMENT
LOW…/extended/edge_topologies/tnf_node_replacement_flow.go1217 // Step 1: Verify the VM no longer exists before confirming fencingCOMMENT
LOW…/extended/edge_topologies/tnf_node_replacement_flow.go1244 // Step 2: Confirm the fencing of the target nodeCOMMENT
LOW…/extended/edge_topologies/tnf_node_replacement_flow.go1267 // Step 3: Wait for etcd to start after stonith confirm (poll every 30s; cap etcdPhase1StartAfterStonithTimeout).COMMENT
LOW…xtended/edge_topologies/tnf_node_replacement_finish.go69 // Step 1: Verify both nodes are in Ready stateCOMMENT
LOW…xtended/edge_topologies/tnf_node_replacement_finish.go82 // Step 2: Verify all cluster operators are available (not degraded or progressing)COMMENT
LOW…topologies/utils/apis/pacemaker_fencing_credentials.go194 //Step 1: Get an initial list of pods. The resourceVersion from this list is the "starting point" for the watch.COMMENT
LOW⚡…topologies/utils/apis/pacemaker_fencing_credentials.go225 // Step 2: Check all existing pods first. If any of them show the desired result, we're done.COMMENT
LOW⚡…topologies/utils/apis/pacemaker_fencing_credentials.go232 // Step 3: Watch for new pods and follow their logs until we see the desired result or timeout.COMMENT
LOW…topologies/utils/apis/pacemaker_fencing_credentials.go245 // Step 4: Wait for new/updated pods and check each one until we find the desired result or timeout.COMMENT
LOW⚡test/extended/apiserverauth/apiserver_util.go1831 // Step 1: Retrieve current secret countCOMMENT
LOW⚡test/extended/apiserverauth/apiserver_util.go1839 // Step 2: Create secrets and check if quota limit is reachedCOMMENT
LOW⚡test/extended/apiserverauth/apiserver_util.go1847 // Step 3: Expect failure when reaching the quota limitCOMMENT
LOW⚡test/extended/node/node_utils.go468 // Step 4: Wait for CSV to be readyCOMMENT
LOW⚡test/extended/node/node_utils.go475 // Step 5: Create HyperConverged CRCOMMENT
LOW⚡test/extended/node/node_utils.go497 // Step 6: Wait for HyperConverged to be readyCOMMENT
LOW⚡test/extended/node/node_utils.go504 // Step 7: Label worker nodes for CNVCOMMENT
LOW⚡test/extended/node/node_utils.go511 // Step 8: Wait for MCP rollout to complete (if any MachineConfigs were applied)COMMENT
LOW⚡test/extended/node/node_utils.go818 // Step 2: Delete SubscriptionCOMMENT
LOW⚡test/extended/node/node_utils.go825 // Step 3: Delete all CSVs in the namespaceCOMMENT
LOW⚡test/extended/node/node_utils.go834 // Step 4: Delete OperatorGroupCOMMENT
LOW⚡test/extended/node/node_utils.go841 // Step 5: Remove node labelsCOMMENT
LOW⚡test/extended/node/node_utils.go845 // Step 6: Delete namespaceCOMMENT
LOWtest/extended/node/node_utils.go378 // Step 1: Create CNV namespace with Pod Security labelsCOMMENT
LOWtest/extended/node/node_utils.go420 // Step 2: Create OperatorGroupCOMMENT
LOWtest/extended/node/node_utils.go442 // Step 3: Create SubscriptionCOMMENT
LOWtest/extended/node/node_utils.go783 // Step 1: Delete HyperConverged CRCOMMENT
LOWtest/extended/node/node_utils.go863 // Step 7: Wait for MCP rollout to complete (if any MachineConfigs were removed)COMMENT
LOW⚡…st/extended/node/dra/nvidia/prerequisites_installer.go53 // Step 1: Validate GPU Operator is already installedCOMMENT
LOW⚡…st/extended/node/dra/nvidia/prerequisites_installer.go61 // Step 2: Wait for GPU Operator to be readyCOMMENT
LOW⚡…st/extended/node/dra/nvidia/prerequisites_installer.go68 // Step 3: Check if DRA Driver already installed (skip if present)COMMENT
LOW⚡…st/extended/node/dra/nvidia/prerequisites_installer.go72 // Step 4: Ensure Helm is availableCOMMENT
LOW⚡…st/extended/node/dra/nvidia/prerequisites_installer.go77 // Step 5: Add NVIDIA Helm repositoryCOMMENT
LOW⚡…st/extended/node/dra/nvidia/prerequisites_installer.go82 // Step 6: Install DRA Driver (latest version)COMMENT
LOW⚡…st/extended/node/dra/nvidia/prerequisites_installer.go90 // Step 7: Wait for DRA Driver to be readyCOMMENT
LOW…st/extended/node/dra/nvidia/prerequisites_installer.go288 // Step 1: Uninstall Helm releaseCOMMENT
LOW…st/extended/node/dra/nvidia/prerequisites_installer.go299 // Step 2: Delete ClusterRoleBindings created by grantSCCPermissionsCOMMENT
LOW…st/extended/node/dra/nvidia/prerequisites_installer.go316 // Step 3: Remove DRA kubelet plugin labels from GPU nodesCOMMENT
LOW…st/extended/node/dra/nvidia/prerequisites_installer.go334 // Step 4: Delete namespaceCOMMENT
LOW…st/extended/node/dra/nvidia/prerequisites_installer.go350 // Step 1: Delete ClusterRoleBindingsCOMMENT
LOW…st/extended/node/dra/nvidia/prerequisites_installer.go367 // Step 2: Remove DRA kubelet plugin labels from GPU nodesCOMMENT
LOW…st/extended/node/dra/nvidia/prerequisites_installer.go385 // Step 3: Delete namespaceCOMMENT
LOW⚡pkg/test/ginkgo/queue_test.go1017 // Step 1: Get test1 and mark it as running (but don't run it yet to keep conflict active)COMMENT
LOW⚡pkg/test/ginkgo/queue_test.go1024 // Step 2: Try to get next test while test1 is "running"COMMENT
LOW⚡pkg/test/ginkgo/queue_test.go1031 // Step 3: Clean up test1's conflict (simulate test1 completing)COMMENT
LOW⚡pkg/test/ginkgo/queue_test.go1034 // Step 4: Now test2 should be runnable and returned (it maintained its position in queue)COMMENT
AI Slop Vocabulary15 hits · 42 pts
SeverityFileLineSnippetContext
MEDIUM…estdata/builds/jenkins-pipeline/jenkins-ephemeral.json326 "description": "See https://access.redhat.com/documentation/en-us/openjdk/11/html-single/configuring_openjdk_11_onCODE
MEDIUM…/extended/edge_topologies/tnf_node_replacement_flow.go256// getNodeInternalIP gets the internal IP address of a node using JSON output for robust parsingCOMMENT
MEDIUM…_otp/testdata/securityandcompliance/cert_generation.sh85# the entire configuration file. It may also hold settings pertaining to moreCOMMENT
MEDIUM…estdata/logging/external-log-stores/cert_generation.sh42# the entire configuration file. It may also hold settings pertaining to moreCOMMENT
MEDIUM…a/logging/external-log-stores/kafka/cert_generation.sh60# the entire configuration file. It may also hold settings pertaining to moreCOMMENT
MEDIUM…a/logging/external-log-stores/kafka/cert_generation.sh158# the entire configuration file. It may also hold settings pertaining to moreCOMMENT
MEDIUMtest/extended/util/compat_otp/jenkins/ref.go377// will leverage the rhel images from the terms based registry at registry.redhat.ioCOMMENT
MEDIUMtest/extended/machine_config/helpers.go128// `GetRolesToTest` gets the MCPs in a cluster with nodes associated to it. This allows a more robust way to determineCOMMENT
MEDIUMtest/extended/node/node_swap.go38 // - All nodes have swapBehavior=NoSwap to ensure kubelet does not utilize swap even if available at OS levelCOMMENT
MEDIUMhack/test-go.sh24# - DLV_DEBUG toggles running tests using delve debuggerCOMMENT
MEDIUMhack/test-go.sh88 # henceforth as packages and instead interpret them as flags to give to `go test`COMMENT
MEDIUMhack/test-go.sh212 # run tests using delve debuggerCOMMENT
MEDIUMexamples/jenkins/jenkins-ephemeral-template.json323 "description": "See https://access.redhat.com/documentation/en-us/openjdk/11/html-single/configuring_openjdk_11_on_rhCODE
MEDIUMexamples/jenkins/jenkins-persistent-template.json351 "description": "See https://access.redhat.com/documentation/en-us/openjdk/11/html-single/configuring_openjdk_11_on_rhCODE
MEDIUMpkg/monitortests/cli/adm_upgrade/status/monitortest.go186 // TODO: Maybe utilize Intervals somehow and do tests in ComputeComputedIntervals and EvaluateTestsFromConstructedInterCOMMENT
Self-Referential Comments13 hits · 38 pts
SeverityFileLineSnippetContext
MEDIUMtest/extended/testdata/cmd/hack/lib/util/text.sh3# This file contains helpful aliases for manipulating the output text to the terminal asCOMMENT
MEDIUMtest/extended/testdata/cmd/hack/lib/log/output.sh3# This file contains functions used for writing log messagesCOMMENT
MEDIUMhack/update-generated.sh13echo "# This file is generated by hack/update-generated.sh" > test/extended/util/image/zz_generated.txtCODE
MEDIUMhack/generate-docs.sh3# This file is not intended to be run automatically. It is meant to be runCOMMENT
MEDIUMhack/lib/util/text.sh3# This file contains helpful aliases for manipulating the output text to the terminal asCOMMENT
MEDIUMhack/lib/log/output.sh3# This file contains functions used for writing log messagesCOMMENT
MEDIUMexamples/prometheus/prometheus.yaml44# Create a service account for accessing prometheus dataCOMMENT
MEDIUMexamples/prometheus/prometheus.yaml51# Create a service account for prometheus to use to scrape other infrastructure componentsCOMMENT
MEDIUMexamples/prometheus/prometheus.yaml119# Create a fully end-to-end TLS connection to the prometheus proxyCOMMENT
MEDIUMexamples/prometheus/prometheus.yaml158# Create a fully end-to-end TLS connection to the alert proxyCOMMENT
MEDIUMexamples/prometheus/prometheus.yaml195# Create a fully end-to-end TLS connection to the alertmanager proxyCOMMENT
MEDIUMexamples/prometheus/prometheus-standalone.yaml38# Create a fully end-to-end TLS connection to the prometheus proxyCOMMENT
MEDIUMexamples/prometheus/prometheus-standalone.yaml214# Create a fully end-to-end TLS connection to the alert proxyCOMMENT
Hallucination Indicators3 hits · 30 pts
SeverityFileLineSnippetContext
CRITICALtest/extended/operators/daemon_set.go106 violation := fmt.Sprintf("expected daemonset %s to have maxUnavailable 10%% or 33%% (see comment) instead of %s, or CODE
CRITICALtest/extended/operators/daemon_set.go110 debug = append(debug, fmt.Sprintf("daemonset %s has %s", key, ds.Spec.UpdateStrategy.RollingUpdate.MaxUnavailable.StCODE
CRITICALtest/extended/images/oc_copy.go435 podSecurityContextCopy := rc.Spec.Template.Spec.SecurityContext.DeepCopy()CODE
Decorative Section Separators8 hits · 24 pts
SeverityFileLineSnippetContext
MEDIUMtest/extended/tls/tls_observed_config.go54// ─── Narrow target types ───────────────────────────────────────────────────COMMENT
MEDIUMtest/extended/tls/tls_observed_config.go132// ─── Typed target lists ────────────────────────────────────────────────────COMMENT
MEDIUMtest/extended/tls/tls_observed_config.go278// ── read-only tests ────────────────────────────────────────────COMMENT
MEDIUMtest/extended/tls/tls_observed_config.go359// ── Serial disruptive tests ─────────────────────────────────────────────COMMENT
MEDIUMtest/extended/tls/tls_observed_config.go528 // ── ConfigMap annotation restoration tests ────────────────────────────COMMENT
MEDIUMtest/extended/tls/tls_observed_config.go641// ─── Test implementations ──────────────────────────────────────────────────COMMENT
MEDIUMtest/extended/tls/tls_observed_config.go1126// ─── Helper functions ──────────────────────────────────────────────────────COMMENT
MEDIUMtest/extended/tls/tls_observed_config.go1790// ─── HyperShift helpers ────────────────────────────────────────────────────COMMENT
Modern AI Meta-Vocabulary6 hits · 18 pts
SeverityFileLineSnippetContext
MEDIUM…t_otp/testdata/operatorsdk/ocp-52813-data/watches.yaml8#+kubebuilder:scaffold:watchCOMMENT
MEDIUM…t_otp/testdata/operatorsdk/ocp-42928-data/watches.yaml11#+kubebuilder:scaffold:watchCOMMENT
MEDIUM…t_otp/testdata/operatorsdk/ocp-27977-data/watches.yaml11#+kubebuilder:scaffold:watchCOMMENT
MEDIUM…t_otp/testdata/operatorsdk/ocp-28586-data/watches.yaml7#+kubebuilder:scaffold:watchCOMMENT
MEDIUM…t_otp/testdata/operatorsdk/ocp-44551-data/watches.yaml8#+kubebuilder:scaffold:watchCOMMENT
MEDIUMhack/agentic_setup.sh4# Called by the TRT agentic CI workflow (jira-solver / review-responder)COMMENT
Hyper-Verbose Identifiers13 hits · 14 pts
SeverityFileLineSnippetContext
LOWe2echart/non-spyglass-e2e-chart-template.html342 function isInterestingOrPathological(eventInterval) {CODE
LOWe2echart/non-spyglass-e2e-chart-template.html400 function isKubeletStartupProbeFailure(eventInterval) {CODE
LOWe2echart/non-spyglass-e2e-chart-template.html527 function buildLocatorDisplayString(i) {CODE
LOWe2echart/test-risk-analysis.html141 function addDisruptionColumnHeaders(selector) {CODE
LOWe2echart/e2e-chart-template.html117 function isInterestingOrPathological(eventInterval) {CODE
LOW⚡e2echart/e2e-chart-template.html142 function isGracefulShutdownActivity(eventInterval) {CODE
LOW⚡e2echart/e2e-chart-template.html146 function isAPIUnreachableFromClientActivity(eventInterval) {CODE
LOW⚡e2echart/e2e-chart-template.html154 function isStaticPodInstallMonitorActivity(eventInterval) {CODE
LOWe2echart/e2e-chart-template.html305 function isAPIUnreachableFromClientValue(item) {CODE
LOWe2echart/e2e-chart-template.html313 function isStaticPodInstallMonitorValue(item) {CODE
LOWe2echart/e2e-chart-template.html327 function apiserverShutdownEventsValue(item) {CODE
LOWe2echart/e2e-chart-template.html371 function buildLocatorDisplayString(i) {CODE
LOWe2echart/e2e-chart-template.html491 function isEtcdLeadershipAndNotEmpty(item) {CODE
Fake / Example Data8 hits · 8 pts
SeverityFileLineSnippetContext
LOWtest/extended/testdata/signer-buildconfig.yaml43 %echo done \n' >> dummy_key.confCODE
LOWtest/extended/testdata/cmd/test/cmd/secrets.sh19os::cmd::expect_success 'oc create secret docker-registry dockerconfigjson --docker-username=sample-user --docker-passwoCODE
LOW…ata/builds/webhook/bitbucket/testdata/pushevent54.json6 "emailAddress":"admin@example.com",CODE
LOW…webhook/bitbucket/testdata/pushevent54-not-master.json6 "emailAddress":"admin@example.com",CODE
LOWtest/extended/images/helper.go407 Email: "test@test.com",CODE
LOWtest/extended/images/signatures.go81 "GNUPGHOME=/var/lib/origin/gnupg gpg2 --batch --gen-key --pinentry-mode=loopback --passphrase '' dummy_key.conf && " CODE
LOWtest/extended/cli/admin.go215 fakeUser := gen.GenerateName("fake-user-")CODE
LOWe2echart/non-spyglass-e2e-chart-template.html93 i.delete(t),p}function gi(n){return Ls(Vi(n,X,_o),n+"")}function yi(n){return de(n,Pc,Is)}function di(n){return dCODE
Example Usage Blocks4 hits · 6 pts
SeverityFileLineSnippetContext
LOW…xtended/edge_topologies/tnf_node_replacement_finish.go389// Example usage:COMMENT
LOWtest/extended/util/compat_otp/ccoctl.go20// Usage example:COMMENT
LOWhack/verify-jsonformat.sh3# Usage:COMMENT
LOWpkg/test/ginkgo/retries.go64// Example usage:COMMENT
Slop Phrases2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUM…metallb/frr-master-singlestack-configmap-template.yaml88 # or you can use "all_wrap" for all daemons, e.g. to use perf record:COMMENT
MEDIUMhack/verify-jsonformat.sh11# In case there is a formatting error, you can use this command to fix itCOMMENT
Excessive Try-Catch Wrapping1 hit · 2 pts
SeverityFileLineSnippetContext
MEDIUM.claude/scripts/query_operator_watch_requests.py32 print(f"Error: Invalid release format '{release}'. Expected format like '4.22'", file=sys.stderr)CODE
Redundant / Tautological Comments1 hit · 2 pts
SeverityFileLineSnippetContext
LOW.claude/scripts/update_operator_watch_limits.py99 # Check if exists in limitsCOMMENT
Deep Nesting1 hit · 1 pts
SeverityFileLineSnippetContext
LOW.claude/scripts/update_operator_watch_limits.py42CODE