AI Slop Code Risk Monitor

kgateway-dev/kgateway

SlopCodeMonitor badge for kgateway-dev/kgateway Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

The Cloud-Native API Gateway and AI Gateway

1.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for kgateway-dev/kgateway, a Go project with 5,728 GitHub stars. SynthScan examined 506,844 lines of code across 2735 source files, recording 757 pattern matches distributed across 14 syntactic categories. The legacy adjusted pattern signal is 1.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.

1.7
Adjusted Signal
1.7
Raw Pattern Score
100%
Time Factor
2026-10-30
Last Push
5.7K
Stars
Go
Language
506.8K
Lines of Code
2.7K
Files
757
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.5/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.4/100 · LOW

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

Agent Over-Engineering Ratio 0.2/100 · LOW

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

PR Review Velocity Impact 8.0/100 · LOW

Which changes need focused human review? 757 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 4HIGH 0MEDIUM 27LOW 726

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 757 distinct pattern matches across 14 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 Block637 hits · 598 pts
SeverityFileLineSnippetContext
LOWosv-scanner.toml1# OSV-Scanner ignore list.COMMENT
LOWosv-scanner.toml41#COMMENT
LOW.golangci.yaml181 ignore-rules:COMMENT
LOWtest_coverage.yml1# ref: https://github.com/vladopajic/go-test-coverage/blob/a5134457f681defa8eada436f1bcda10407f4f8b/.testcoverage.examplCOMMENT
LOWtest_coverage.yml21COMMENT
LOWtilt-settings.yaml21 # The output dir of the binaryCOMMENT
LOWdesign/12721-e2e-testing-with-gateway-api-versions.md61 // MinGwApiVersion specifies the minimum Gateway API version required per channel.COMMENT
LOWdesign/12721-e2e-testing-with-gateway-api-versions.md101To accommodate this, we will add a new field `SetupByVersion` to the BaseTestingSuite:COMMENT
LOW…pi-key-authentication-for-kgateway-traffic-policies.md41// to query parameter if the header is not present, then to cookie if both header and queryCOMMENT
LOW…pi-key-authentication-for-kgateway-traffic-policies.md61 Cookie *string `json:"cookie,omitempty"`COMMENT
LOW…pi-key-authentication-for-kgateway-traffic-policies.md81 // In this example, the system will:COMMENT
LOW…pi-key-authentication-for-kgateway-traffic-policies.md101 // Example: "x-client-id"COMMENT
LOW…pi-key-authentication-for-kgateway-traffic-policies.md121 // +optionalCOMMENT
LOW…n/11177-ai-extensions-opentelemetry-tracing-support.md41 // EndPoint specifies the URL of the OTLP Exporter for traces.COMMENT
LOW…n/11177-ai-extensions-opentelemetry-tracing-support.md61 // This determines how tracing data is serialized and transported (e.g., gRPC, HTTP/Protobuf).COMMENT
LOW…n/11177-ai-extensions-opentelemetry-tracing-support.md121 // All traces will be recorded and exported. Useful for development or low-traffic systems.COMMENT
LOWdesign/11188-fault-injection-support.md61// At least one of delay, abort, responseRateLimit, or disable must be specified.COMMENT
LOWdesign/11188-fault-injection-support.md81 // To effectively disable fault injection, use the Disable field instead.COMMENT
LOWdesign/11188-fault-injection-support.md101COMMENT
LOWdesign/11188-fault-injection-support.md121 // +optionalCOMMENT
LOW…sign/11173-opentelemetry-tracing-access-log-support.md121COMMENT
LOWdesign/12224-correct-status-on-gateway-listeners.md41 // This condition indicates whether a Gateway has generated someCOMMENT
LOWdesign/12224-correct-status-on-gateway-listeners.md61 // * "AddressNotAssigned"COMMENT
LOWdesign/10573-aws-lambda-integration.md81 BackendTypeAws = "aws"COMMENT
LOWdesign/10573-aws-lambda-integration.md141 Qualifier string `json:"qualifier,omitempty"`COMMENT
LOWtools/osv-scanner.toml1# OSV-Scanner ignore list for the build-tooling module (tools/go.mod).COMMENT
LOWinstall/helm/kgateway/values.yaml41# -- Set node selector labels for pod scheduling, such as 'kubernetes.io/arch: amd64'. This field is deprecated in favorCOMMENT
LOWinstall/helm/kgateway/values.yaml141 publishNotReadyAddresses: falseCOMMENT
LOWinstall/helm/kgateway/values.yaml161 # -- Extra labels for the ServiceMonitor.COMMENT
LOWinstall/helm/kgateway/values.yaml181 # path: /readyzCOMMENT
LOWinstall/helm/kgateway/values.yaml201 # (leaseDuration 15s, renewDeadline 10s, retryPeriod 2s).COMMENT
LOWinstall/helm/kgateway/values.yaml221 referenceAhead: ""COMMENT
LOWinstall/helm/kgateway/values.yaml241 #COMMENT
LOWinstall/helm/kgateway/values.yaml261 # -- Set vertical pod autoscaler for the controller. Note that this does notCOMMENT
LOWinstall/helm/kgateway/values.yaml281 # -- Set the default image tag.COMMENT
LOWinstall/helm/kgateway/values.yaml301# namespace: kgateway-systemCOMMENT
LOWinstall/helm/kgateway/values.yaml321# This setting determines how invalid configuration is handled to prevent security bypassesCOMMENT
LOWtest/crvalidation/crvalidation.go21// errors are expected, list them in the _errs field instead; each must appear in the result. For example:COMMENT
LOWtest/deployer/deployer_helm.go341 if tt.Validate != nil {COMMENT
LOWtest/deployer/deployer_helm.go441 Tag: "v2.1.0-dev",COMMENT
LOWtest/deployer/internal_helm_test.go1package deployerCOMMENT
LOWtest/deployer/internal_helm_test.go641 // 1. Configs vs Overlays precedence: overlays are applied AFTER configsCOMMENT
LOWtest/gomega/assertions/goroutines.go21// such as when `cancel()` is called, and the next test should not be started until all goroutines are cleaned upCOMMENT
LOWtest/translator/test.go601 // settlePolls is how many consecutive unchanged snapshots count as quiescence.COMMENT
LOWtest/e2e/installation.go41 // Cluster exposes the cluster context for tests that need direct APICOMMENT
LOWtest/e2e/features/oauth/suite.go241// https://github.com/kgateway-dev/kgateway/issues/14062. Every other route in this suiteCOMMENT
LOWtest/e2e/features/directresponse/suite.go141// // the parent httproute both 1) specifies a direct response and 2) delegates to another httproute which routes to a COMMENT
LOWtest/e2e/features/directresponse/suite.go161COMMENT
LOWtest/e2e/features/directresponse/suite.go181// )COMMENT
LOWtest/e2e/features/istio/testdata/nginx-mtls-config.yml1# Generate a set of self-signed CA, tls.key, tls.crt, example.key, example.crt for the mtls tests:COMMENT
LOWtest/e2e/features/xdsidentityrace/suite.go21 "github.com/kgateway-dev/kgateway/v2/test/helpers"COMMENT
LOWtest/e2e/features/xdsidentityrace/suite.go41COMMENT
LOWtest/e2e/features/frontendtls/suite.go141COMMENT
LOW…/e2e/features/frontendtls/testdata/tls-rsa-secret.yaml1# Self-signed RSA TLS certificate for example.com used in frontend TLS testsCOMMENT
LOW…atures/frontendtls/testdata/tls-ecdsa-p256-secret.yaml1# Self-signed ECDSA P-256 TLS certificate for example.com used in frontend TLS testsCOMMENT
LOW…/e2e/features/route_delegation/testdata/recursive.yaml1# Configuration:COMMENT
LOW…elegation/testdata/invalid_child_valid_standalone.yaml1# Configuration:COMMENT
LOW…/features/route_delegation/testdata/invalid_child.yaml1# Configuration:COMMENT
LOW…res/route_delegation/testdata/matcher_inheritance.yaml1# Configuration:COMMENT
LOWtest/e2e/features/route_delegation/testdata/common.yaml1# Configuration:COMMENT
577 more matches not shown…
Structural Annotation Overuse33 hits · 53 pts
SeverityFileLineSnippetContext
LOWdevel/testing/gateway-translator-tests.md37### Step 1: Create Input FilesCOMMENT
LOWdevel/testing/gateway-translator-tests.md43### Step 2: Add Test EntryCOMMENT
LOWdevel/testing/gateway-translator-tests.md58### Step 3: Run the TestCOMMENT
LOWtest/e2e/debugging.md11## Step 1: Setting Up A ClusterCOMMENT
LOWtest/e2e/debugging.md79## Step 2: Running TestsCOMMENT
LOW⚡test/e2e/features/deployer/suite.go409 // Step 1: Wait for the proxy deployment to be healthyCOMMENT
LOW⚡test/e2e/features/deployer/suite.go412 // Step 2: Verify PDB, HPA, and VPA were createdCOMMENT
LOWtest/e2e/features/deployer/suite.go441 // Step 3: Update PDB configuration - change minAvailable from 1 to 0COMMENT
LOWtest/e2e/features/deployer/suite.go462 // Step 4: Remove HPA and VPA from GatewayParameters (keep PDB)COMMENT
LOWtest/e2e/features/deployer/suite.go494 // Step 5: Delete the Gateway and verify all resources are cleaned upCOMMENT
LOWtest/e2e/features/apikeyauth/suite.go309 // Step 1: Verify initial API keys work (k-123, k-456)COMMENT
LOWtest/e2e/features/apikeyauth/suite.go324 // Step 2: Update the secret with new keys (k-789, k-999) and remove old onesCOMMENT
LOWtest/e2e/features/apikeyauth/suite.go359 // Step 3: Verify new keys workCOMMENT
LOWtest/e2e/features/apikeyauth/suite.go374 // Step 4: Verify old keys no longer workCOMMENT
LOWtest/e2e/features/apikeyauth/suite.go389 // Step 5: Update secret again to add back an old key and add a new oneCOMMENT
LOWtest/e2e/features/apikeyauth/suite.go406 // Step 6: Verify the final set of keys workCOMMENT
LOWtest/e2e/features/apikeyauth/suite.go434 // Step 7: Verify removed keys no longer workCOMMENT
LOWtest/e2e/features/apikeyauth/suite.go651 // Step 1: two Secrets carry the identical credential. The repeat is collapsed, so the route isCOMMENT
LOWtest/e2e/features/apikeyauth/suite.go668 // Step 2: the differential. A brand new credential has to land while the duplicate pair isCOMMENT
LOWtest/e2e/features/apikeyauth/suite.go696 // Step 3: the ambiguous duplicate. A second client claiming client1's key value cannot beCOMMENT
LOWtest/e2e/features/apikeyauth/suite.go747 // Step 4: removing the conflict recovers the route.COMMENT
LOW⚡…e/features/frontendtls/testdata/CLIENT_CERTS_README.md40### Step 1: Generate CA Certificate and KeyCOMMENT
LOW⚡…e/features/frontendtls/testdata/CLIENT_CERTS_README.md47### Step 2: Generate Client Certificate for Port 8443COMMENT
LOW⚡…e/features/frontendtls/testdata/CLIENT_CERTS_README.md56### Step 3: Generate Client Certificate for Port 9443COMMENT
LOW⚡…e/features/frontendtls/testdata/CLIENT_CERTS_README.md65### Step 4: Generate Client Certificate for FrontendTLSConfig Tests (Ports 8444/8445)COMMENT
LOW…e/features/frontendtls/testdata/CLIENT_CERTS_README.md77### Step 5: Generate Second CA Certificate for Multiple CA TestsCOMMENT
LOW…e/features/frontendtls/testdata/CLIENT_CERTS_README.md87### Step 6: Generate Client Certificate Signed by Second CA (Port 8446)COMMENT
LOWdocs/guides/frontend-tls.md20## Step 1: Generate CertificatesCOMMENT
LOWdocs/guides/frontend-tls.md69## Step 2: Create Kubernetes ResourcesCOMMENT
LOWdocs/guides/frontend-tls.md118## Step 3: Configure Gateway with FrontendTLSConfigCOMMENT
LOWdocs/guides/frontend-tls.md197## Step 4: Get Gateway External IP/Port or Port ForwardCOMMENT
LOWdocs/guides/frontend-tls.md207## Step 5: Test the ConfigurationCOMMENT
LOWdocs/guides/frontend-tls.md254## Step 6: Verify ConfigurationCOMMENT
Redundant / Tautological Comments26 hits · 41 pts
SeverityFileLineSnippetContext
LOW⚡hack/run-e2e-test.sh120# Check if an environment variable is truthy (1, true, yes, y)COMMENT
LOW⚡hack/run-e2e-test.sh126# Check if kind cluster existsCOMMENT
LOW⚡hack/run-e2e-test.sh131# Check if k3d cluster existsCOMMENT
LOWhack/run-e2e-test.sh144# Check if cluster exists (dispatches based on CLUSTER_TYPE)COMMENT
LOWhack/run-e2e-test.sh243 # Check if the pattern contains slashes (nested test path like TestKgateway/SessionPersistence/TestHeaderSessionPersCOMMENT
LOWhack/run-e2e-test.sh268 # Check if it's a top-level test functionCOMMENT
LOWhack/run-e2e-test.sh287 # Check if it's a test method within a suite (e.g., TestCookieSessionPersistence)COMMENT
LOWhack/run-e2e-test.sh319 # Check if this package identifier's import path matches our method's pathCOMMENT
LOWhack/run-e2e-test.sh400 # Check if suite and method are the same across all patternsCOMMENT
LOWhack/run-e2e-test.sh429 # Check if it's a suiteCOMMENT
LOWhack/run-e2e-test.sh469 # Check if the pattern might be a specific test method (starts with Test but not the suite name)COMMENT
LOWhack/run-e2e-test.sh640 # Set FAIL_FAST_AND_PERSIST to true by default (for local development/debugging)COMMENT
LOWhack/run-e2e-test.sh707 # Check if we should run setupCOMMENT
LOWhack/run-e2e-test.sh810 # Check if no tests were runCOMMENT
LOWhack/run-test.sh210# Check if a pattern is an e2e test by finding where it's definedCOMMENT
LOWhack/run-test.sh262 # Check if pattern already starts with TestCOMMENT
LOWhack/generate-release-notes.sh79# Check if a release note is effectively "NONE"COMMENT
LOWhack/generate-release-notes.sh85 # Check if empty or "none"COMMENT
LOWhack/generate-release-notes.sh158 # Check if git log has any outputCOMMENT
LOWhack/generate-release-notes.sh184 # Check if PR existsCOMMENT
LOWhack/generate-release-notes.sh316# Check if we found any release notesCOMMENT
LOWhack/ci/get-recent-flakes.sh109 # Check if this test already exists in our mapCOMMENT
LOWhack/ci/get-recent-flakes.sh145 # Check if this test name is a prefix of any other test name in the listCOMMENT
LOWhack/kind/setup-metalllb-on-kind.sh8# Set METALLB_VERSION to apply that upstream release instead, or METALLB_MANIFEST to applyCOMMENT
LOW.github/actions/kube-conformance-tests/action.yaml114 # Check if additional Helm values file is providedCOMMENT
LOW…tions/mq-cancel-dangling-wfs/mq-cancel-dangling-wfs.sh43 # Check if branch still existsCOMMENT
Hallucination Indicators4 hits · 40 pts
SeverityFileLineSnippetContext
CRITICALpkg/deployer/deployer_test.go1707 Expect(istioContainer.Resources.Limits.Cpu()).To(Equal(expectedGwp.Istio.IstioProxyContainer.Resources.Limits.Cpu()))CODE
CRITICALpkg/deployer/deployer_test.go1708 Expect(istioContainer.Resources.Requests.Cpu()).To(Equal(expectedGwp.Istio.IstioProxyContainer.Resources.Requests.CpuCODE
CRITICAL…/kgateway/extensions2/plugins/listenerpolicy/common.go66 if in.RetryPolicy.RetryBackOff.MaxInterval.Duration.Nanoseconds() < in.RetryPolicy.RetryBackOff.BaseInterval.DuratioCODE
CRITICAL…/kgateway/extensions2/plugins/listenerpolicy/common.go67 logger.Error("retryPolicy.RetryBackOff.MaxInterval is lesser than RetryPolicy.RetryBackOff.MaxInterval. Ignoring MaCODE
Self-Referential Comments12 hits · 36 pts
SeverityFileLineSnippetContext
MEDIUMtest/e2e/tests/manifests/test-assertions.yaml1# This file defines Helm values that arm test-only assertions in the deployed control plane.COMMENT
MEDIUMtest/e2e/tests/manifests/common-recommendations.yaml1# This file defines the common recommendations for a user who wants to run kgateway.COMMENT
MEDIUMinternal/envoy_modules/generate-dockerfile.sh106# This file is generated by internal/envoy_modules/generate-dockerfile.sh when the 'generate-all' make target is run.COMMENT
MEDIUM…fic-policy/multiple-descriptors-or/base-resources.yaml2# This file contains the common Gateway, HTTPRoutes, Services, and SecretCOMMENT
MEDIUM…c-policy/local-and-global-combined/base-resources.yaml2# This file contains the common Gateway, HTTPRoutes, Services, and SecretCOMMENT
MEDIUM…-policy/gateway-section-attachment/base-resources.yaml2# This file contains the common Gateway, HTTPRoutes, Services, and SecretCOMMENT
MEDIUM…raffic-policy/filter-extension-ref/base-resources.yaml2# This file contains the common Gateway, HTTPRoutes, Services, and SecretCOMMENT
MEDIUM…multiple-headers-single-descriptor/base-resources.yaml2# This file contains the common Gateway, HTTPRoutes, Services, and SecretCOMMENT
MEDIUM…licy/multi-dimensional-descriptors/base-resources.yaml2# This file contains the common Gateway, HTTPRoutes, Services, and SecretCOMMENT
MEDIUM…ls/inputs/traffic-policy/fail-open/base-resources.yaml2# This file contains the common Gateway, HTTPRoutes, Services, and SecretCOMMENT
MEDIUM…ic-policy/route-section-attachment/base-resources.yaml2# This file contains the common Gateway, HTTPRoutes, Services, and SecretCOMMENT
MEDIUM…ts/traffic-policy/global-ratelimit/base-resources.yaml2# This file contains the common Gateway, HTTPRoutes, Services, and SecretCOMMENT
AI Slop Vocabulary10 hits · 28 pts
SeverityFileLineSnippetContext
MEDIUMtest/deployer/deployer_helm.go362// and makes this helper robust to any kind the deployer might emit.COMMENT
MEDIUMtest/e2e/features/route_delegation/testdata/common.yaml15# in the top-level test harness. HTTPRoutes in these testdata files useCOMMENT
LOWhack/run-e2e-test.sh491 # Fallback: just use the pattern as-isCOMMENT
MEDIUMhack/kind/setup-metalllb-on-kind.sh64# something this harness sets up.COMMENT
MEDIUMpkg/deployer/deployer.go444 // and the internal template isn't robust enough.COMMENT
MEDIUMpkg/envoyinit/run.go92// This configuration may leverage the Kubernetes Downward APICOMMENT
MEDIUM…/translator/gateway/testutils/inputs/setup/common.yaml10# prioritization used its labels and locality. The translator harness does not: itCOMMENT
MEDIUM…/extensions2/plugins/listenerpolicy/listener_plugin.go646 // if we get more listener filters in the future we may need a more robust ordering mechanismCOMMENT
MEDIUMpkg/utils/requestutils/curl/option.go285// set doesn't yet support, it should be added explicitly, to make it easier for developers to utilizeCOMMENT
MEDIUMpkg/krtcollections/uniqueclients_delay_test.go86 // is deliberately loose (half the delay) to stay robust on slow CI.COMMENT
Verbosity Indicators16 hits · 25 pts
SeverityFileLineSnippetContext
LOW⚡test/e2e/features/deployer/suite.go409 // Step 1: Wait for the proxy deployment to be healthyCOMMENT
LOW⚡test/e2e/features/deployer/suite.go412 // Step 2: Verify PDB, HPA, and VPA were createdCOMMENT
LOWtest/e2e/features/deployer/suite.go441 // Step 3: Update PDB configuration - change minAvailable from 1 to 0COMMENT
LOWtest/e2e/features/deployer/suite.go462 // Step 4: Remove HPA and VPA from GatewayParameters (keep PDB)COMMENT
LOWtest/e2e/features/deployer/suite.go494 // Step 5: Delete the Gateway and verify all resources are cleaned upCOMMENT
LOWtest/e2e/features/apikeyauth/suite.go309 // Step 1: Verify initial API keys work (k-123, k-456)COMMENT
LOWtest/e2e/features/apikeyauth/suite.go324 // Step 2: Update the secret with new keys (k-789, k-999) and remove old onesCOMMENT
LOWtest/e2e/features/apikeyauth/suite.go359 // Step 3: Verify new keys workCOMMENT
LOWtest/e2e/features/apikeyauth/suite.go374 // Step 4: Verify old keys no longer workCOMMENT
LOWtest/e2e/features/apikeyauth/suite.go389 // Step 5: Update secret again to add back an old key and add a new oneCOMMENT
LOWtest/e2e/features/apikeyauth/suite.go406 // Step 6: Verify the final set of keys workCOMMENT
LOWtest/e2e/features/apikeyauth/suite.go434 // Step 7: Verify removed keys no longer workCOMMENT
LOWtest/e2e/features/apikeyauth/suite.go651 // Step 1: two Secrets carry the identical credential. The repeat is collapsed, so the route isCOMMENT
LOWtest/e2e/features/apikeyauth/suite.go668 // Step 2: the differential. A brand new credential has to land while the duplicate pair isCOMMENT
LOWtest/e2e/features/apikeyauth/suite.go696 // Step 3: the ambiguous duplicate. A second client claiming client1's key value cannot beCOMMENT
LOWtest/e2e/features/apikeyauth/suite.go747 // Step 4: removing the conflict recovers the route.COMMENT
Decorative Section Separators6 hits · 18 pts
SeverityFileLineSnippetContext
MEDIUMtest/e2e/features/http_acl/suite.go511 // ── Phase 1: valid ACL policy only ───────────────────────────────────────COMMENT
MEDIUMtest/e2e/features/http_acl/suite.go537 // ── Phase 2: add the invalid ACL policy ──────────────────────────────────COMMENT
MEDIUM…tutils/inputs/traffic-policy/acl-route-delegation.yaml12# ── Case 1: ShallowMergePreferChild ────────────────────────────────────────────COMMENT
MEDIUM…tutils/inputs/traffic-policy/acl-route-delegation.yaml84# ── Case 2: ShallowMergePreferParent ───────────────────────────────────────────COMMENT
MEDIUM…tutils/inputs/traffic-policy/acl-route-delegation.yaml155# ── Case 3: DeepMergePreferChild ───────────────────────────────────────────────COMMENT
MEDIUM…tutils/inputs/traffic-policy/acl-route-delegation.yaml227# ── Case 4: DeepMergePreferParent ──────────────────────────────────────────────COMMENT
Example Usage Blocks5 hits · 8 pts
SeverityFileLineSnippetContext
LOWtest/gomega/assertions/goroutines.go23// Example usage:COMMENT
LOWtest/helpers/timeouts.go36// Example usage:COMMENT
LOWtest/helpers/timeouts.go50// Example usage:COMMENT
LOWhack/xds-fleet-ab.sh12# Usage:COMMENT
LOWhack/k3d/k3d-loadbalancer.sh12# Usage:COMMENT
Fake / Example Data3 hits · 3 pts
SeverityFileLineSnippetContext
LOW…ay/extensions2/plugins/backendconfigpolicy/tls_test.go613 sanList: []string{"svc@example.org"},CODE
LOW…ay/extensions2/plugins/backendconfigpolicy/tls_test.go618 MatchPattern: &envoymatcher.StringMatcher_Exact{Exact: "svc@example.org"},CODE
LOWpkg/xds/bootstrap/builder.go185 StatPrefix: "placeholder",CODE
Hyper-Verbose Identifiers2 hits · 2 pts
SeverityFileLineSnippetContext
LOW…n/11177-ai-extensions-opentelemetry-tracing-support.md388async def handle_request_body_req_webhook(CODE
LOW…n/11177-ai-extensions-opentelemetry-tracing-support.md454def handle_request_body_req_regex(CODE
Slop Phrases1 hit · 2 pts
SeverityFileLineSnippetContext
LOWinstall/helm/kgateway/values.yaml277# -- Configure the default container image for the components that Helm deploys. You can override these settings for eacCOMMENT
TODO Padding1 hit · 2 pts
SeverityFileLineSnippetContext
LOWpkg/kgateway/extensions2/plugins/istio/plugin.go94 // TODO: implement thisCOMMENT
Excessive Try-Catch Wrapping1 hit · 1 pts
SeverityFileLineSnippetContext
LOW…n/11177-ai-extensions-opentelemetry-tracing-support.md554except Exception as e:CODE