The Cloud-Native API Gateway and AI Gateway
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.
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.
Can maintainers explain intent, assumptions, and trade-offs? 743 finding(s).
Are imports declared and package/API names verified? 7 finding(s).
Are wrappers, guards, and repeated structures necessary? 9 finding(s).
Which changes need focused human review? 757 finding(s).
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.
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.
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.
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.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | osv-scanner.toml | 1 | # OSV-Scanner ignore list. | COMMENT |
| LOW | osv-scanner.toml | 41 | # | COMMENT |
| LOW | .golangci.yaml | 181 | ignore-rules: | COMMENT |
| LOW | test_coverage.yml | 1 | # ref: https://github.com/vladopajic/go-test-coverage/blob/a5134457f681defa8eada436f1bcda10407f4f8b/.testcoverage.exampl | COMMENT |
| LOW | test_coverage.yml | 21 | COMMENT | |
| LOW | tilt-settings.yaml | 21 | # The output dir of the binary | COMMENT |
| LOW | design/12721-e2e-testing-with-gateway-api-versions.md | 61 | // MinGwApiVersion specifies the minimum Gateway API version required per channel. | COMMENT |
| LOW | design/12721-e2e-testing-with-gateway-api-versions.md | 101 | To accommodate this, we will add a new field `SetupByVersion` to the BaseTestingSuite: | COMMENT |
| LOW | …pi-key-authentication-for-kgateway-traffic-policies.md | 41 | // to query parameter if the header is not present, then to cookie if both header and query | COMMENT |
| LOW | …pi-key-authentication-for-kgateway-traffic-policies.md | 61 | Cookie *string `json:"cookie,omitempty"` | COMMENT |
| LOW | …pi-key-authentication-for-kgateway-traffic-policies.md | 81 | // In this example, the system will: | COMMENT |
| LOW | …pi-key-authentication-for-kgateway-traffic-policies.md | 101 | // Example: "x-client-id" | COMMENT |
| LOW | …pi-key-authentication-for-kgateway-traffic-policies.md | 121 | // +optional | COMMENT |
| LOW | …n/11177-ai-extensions-opentelemetry-tracing-support.md | 41 | // EndPoint specifies the URL of the OTLP Exporter for traces. | COMMENT |
| LOW | …n/11177-ai-extensions-opentelemetry-tracing-support.md | 61 | // This determines how tracing data is serialized and transported (e.g., gRPC, HTTP/Protobuf). | COMMENT |
| LOW | …n/11177-ai-extensions-opentelemetry-tracing-support.md | 121 | // All traces will be recorded and exported. Useful for development or low-traffic systems. | COMMENT |
| LOW | design/11188-fault-injection-support.md | 61 | // At least one of delay, abort, responseRateLimit, or disable must be specified. | COMMENT |
| LOW | design/11188-fault-injection-support.md | 81 | // To effectively disable fault injection, use the Disable field instead. | COMMENT |
| LOW | design/11188-fault-injection-support.md | 101 | COMMENT | |
| LOW | design/11188-fault-injection-support.md | 121 | // +optional | COMMENT |
| LOW | …sign/11173-opentelemetry-tracing-access-log-support.md | 121 | COMMENT | |
| LOW | design/12224-correct-status-on-gateway-listeners.md | 41 | // This condition indicates whether a Gateway has generated some | COMMENT |
| LOW | design/12224-correct-status-on-gateway-listeners.md | 61 | // * "AddressNotAssigned" | COMMENT |
| LOW | design/10573-aws-lambda-integration.md | 81 | BackendTypeAws = "aws" | COMMENT |
| LOW | design/10573-aws-lambda-integration.md | 141 | Qualifier string `json:"qualifier,omitempty"` | COMMENT |
| LOW | tools/osv-scanner.toml | 1 | # OSV-Scanner ignore list for the build-tooling module (tools/go.mod). | COMMENT |
| LOW | install/helm/kgateway/values.yaml | 41 | # -- Set node selector labels for pod scheduling, such as 'kubernetes.io/arch: amd64'. This field is deprecated in favor | COMMENT |
| LOW | install/helm/kgateway/values.yaml | 141 | publishNotReadyAddresses: false | COMMENT |
| LOW | install/helm/kgateway/values.yaml | 161 | # -- Extra labels for the ServiceMonitor. | COMMENT |
| LOW | install/helm/kgateway/values.yaml | 181 | # path: /readyz | COMMENT |
| LOW | install/helm/kgateway/values.yaml | 201 | # (leaseDuration 15s, renewDeadline 10s, retryPeriod 2s). | COMMENT |
| LOW | install/helm/kgateway/values.yaml | 221 | referenceAhead: "" | COMMENT |
| LOW | install/helm/kgateway/values.yaml | 241 | # | COMMENT |
| LOW | install/helm/kgateway/values.yaml | 261 | # -- Set vertical pod autoscaler for the controller. Note that this does not | COMMENT |
| LOW | install/helm/kgateway/values.yaml | 281 | # -- Set the default image tag. | COMMENT |
| LOW | install/helm/kgateway/values.yaml | 301 | # namespace: kgateway-system | COMMENT |
| LOW | install/helm/kgateway/values.yaml | 321 | # This setting determines how invalid configuration is handled to prevent security bypasses | COMMENT |
| LOW | test/crvalidation/crvalidation.go | 21 | // errors are expected, list them in the _errs field instead; each must appear in the result. For example: | COMMENT |
| LOW | test/deployer/deployer_helm.go | 341 | if tt.Validate != nil { | COMMENT |
| LOW | test/deployer/deployer_helm.go | 441 | Tag: "v2.1.0-dev", | COMMENT |
| LOW | test/deployer/internal_helm_test.go | 1 | package deployer | COMMENT |
| LOW | test/deployer/internal_helm_test.go | 641 | // 1. Configs vs Overlays precedence: overlays are applied AFTER configs | COMMENT |
| LOW | test/gomega/assertions/goroutines.go | 21 | // such as when `cancel()` is called, and the next test should not be started until all goroutines are cleaned up | COMMENT |
| LOW | test/translator/test.go | 601 | // settlePolls is how many consecutive unchanged snapshots count as quiescence. | COMMENT |
| LOW | test/e2e/installation.go | 41 | // Cluster exposes the cluster context for tests that need direct API | COMMENT |
| LOW | test/e2e/features/oauth/suite.go | 241 | // https://github.com/kgateway-dev/kgateway/issues/14062. Every other route in this suite | COMMENT |
| LOW | test/e2e/features/directresponse/suite.go | 141 | // // the parent httproute both 1) specifies a direct response and 2) delegates to another httproute which routes to a | COMMENT |
| LOW | test/e2e/features/directresponse/suite.go | 161 | COMMENT | |
| LOW | test/e2e/features/directresponse/suite.go | 181 | // ) | COMMENT |
| LOW | test/e2e/features/istio/testdata/nginx-mtls-config.yml | 1 | # Generate a set of self-signed CA, tls.key, tls.crt, example.key, example.crt for the mtls tests: | COMMENT |
| LOW | test/e2e/features/xdsidentityrace/suite.go | 21 | "github.com/kgateway-dev/kgateway/v2/test/helpers" | COMMENT |
| LOW | test/e2e/features/xdsidentityrace/suite.go | 41 | COMMENT | |
| LOW | test/e2e/features/frontendtls/suite.go | 141 | COMMENT | |
| LOW | …/e2e/features/frontendtls/testdata/tls-rsa-secret.yaml | 1 | # Self-signed RSA TLS certificate for example.com used in frontend TLS tests | COMMENT |
| LOW | …atures/frontendtls/testdata/tls-ecdsa-p256-secret.yaml | 1 | # Self-signed ECDSA P-256 TLS certificate for example.com used in frontend TLS tests | COMMENT |
| LOW | …/e2e/features/route_delegation/testdata/recursive.yaml | 1 | # Configuration: | COMMENT |
| LOW | …elegation/testdata/invalid_child_valid_standalone.yaml | 1 | # Configuration: | COMMENT |
| LOW | …/features/route_delegation/testdata/invalid_child.yaml | 1 | # Configuration: | COMMENT |
| LOW | …res/route_delegation/testdata/matcher_inheritance.yaml | 1 | # Configuration: | COMMENT |
| LOW | test/e2e/features/route_delegation/testdata/common.yaml | 1 | # Configuration: | COMMENT |
| 577 more matches not shown… | ||||
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | devel/testing/gateway-translator-tests.md | 37 | ### Step 1: Create Input Files | COMMENT |
| LOW | devel/testing/gateway-translator-tests.md | 43 | ### Step 2: Add Test Entry | COMMENT |
| LOW | devel/testing/gateway-translator-tests.md | 58 | ### Step 3: Run the Test | COMMENT |
| LOW | test/e2e/debugging.md | 11 | ## Step 1: Setting Up A Cluster | COMMENT |
| LOW | test/e2e/debugging.md | 79 | ## Step 2: Running Tests | COMMENT |
| LOW⚡ | test/e2e/features/deployer/suite.go | 409 | // Step 1: Wait for the proxy deployment to be healthy | COMMENT |
| LOW⚡ | test/e2e/features/deployer/suite.go | 412 | // Step 2: Verify PDB, HPA, and VPA were created | COMMENT |
| LOW | test/e2e/features/deployer/suite.go | 441 | // Step 3: Update PDB configuration - change minAvailable from 1 to 0 | COMMENT |
| LOW | test/e2e/features/deployer/suite.go | 462 | // Step 4: Remove HPA and VPA from GatewayParameters (keep PDB) | COMMENT |
| LOW | test/e2e/features/deployer/suite.go | 494 | // Step 5: Delete the Gateway and verify all resources are cleaned up | COMMENT |
| LOW | test/e2e/features/apikeyauth/suite.go | 309 | // Step 1: Verify initial API keys work (k-123, k-456) | COMMENT |
| LOW | test/e2e/features/apikeyauth/suite.go | 324 | // Step 2: Update the secret with new keys (k-789, k-999) and remove old ones | COMMENT |
| LOW | test/e2e/features/apikeyauth/suite.go | 359 | // Step 3: Verify new keys work | COMMENT |
| LOW | test/e2e/features/apikeyauth/suite.go | 374 | // Step 4: Verify old keys no longer work | COMMENT |
| LOW | test/e2e/features/apikeyauth/suite.go | 389 | // Step 5: Update secret again to add back an old key and add a new one | COMMENT |
| LOW | test/e2e/features/apikeyauth/suite.go | 406 | // Step 6: Verify the final set of keys work | COMMENT |
| LOW | test/e2e/features/apikeyauth/suite.go | 434 | // Step 7: Verify removed keys no longer work | COMMENT |
| LOW | test/e2e/features/apikeyauth/suite.go | 651 | // Step 1: two Secrets carry the identical credential. The repeat is collapsed, so the route is | COMMENT |
| LOW | test/e2e/features/apikeyauth/suite.go | 668 | // Step 2: the differential. A brand new credential has to land while the duplicate pair is | COMMENT |
| LOW | test/e2e/features/apikeyauth/suite.go | 696 | // Step 3: the ambiguous duplicate. A second client claiming client1's key value cannot be | COMMENT |
| LOW | test/e2e/features/apikeyauth/suite.go | 747 | // Step 4: removing the conflict recovers the route. | COMMENT |
| LOW⚡ | …e/features/frontendtls/testdata/CLIENT_CERTS_README.md | 40 | ### Step 1: Generate CA Certificate and Key | COMMENT |
| LOW⚡ | …e/features/frontendtls/testdata/CLIENT_CERTS_README.md | 47 | ### Step 2: Generate Client Certificate for Port 8443 | COMMENT |
| LOW⚡ | …e/features/frontendtls/testdata/CLIENT_CERTS_README.md | 56 | ### Step 3: Generate Client Certificate for Port 9443 | COMMENT |
| LOW⚡ | …e/features/frontendtls/testdata/CLIENT_CERTS_README.md | 65 | ### Step 4: Generate Client Certificate for FrontendTLSConfig Tests (Ports 8444/8445) | COMMENT |
| LOW | …e/features/frontendtls/testdata/CLIENT_CERTS_README.md | 77 | ### Step 5: Generate Second CA Certificate for Multiple CA Tests | COMMENT |
| LOW | …e/features/frontendtls/testdata/CLIENT_CERTS_README.md | 87 | ### Step 6: Generate Client Certificate Signed by Second CA (Port 8446) | COMMENT |
| LOW | docs/guides/frontend-tls.md | 20 | ## Step 1: Generate Certificates | COMMENT |
| LOW | docs/guides/frontend-tls.md | 69 | ## Step 2: Create Kubernetes Resources | COMMENT |
| LOW | docs/guides/frontend-tls.md | 118 | ## Step 3: Configure Gateway with FrontendTLSConfig | COMMENT |
| LOW | docs/guides/frontend-tls.md | 197 | ## Step 4: Get Gateway External IP/Port or Port Forward | COMMENT |
| LOW | docs/guides/frontend-tls.md | 207 | ## Step 5: Test the Configuration | COMMENT |
| LOW | docs/guides/frontend-tls.md | 254 | ## Step 6: Verify Configuration | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW⚡ | hack/run-e2e-test.sh | 120 | # Check if an environment variable is truthy (1, true, yes, y) | COMMENT |
| LOW⚡ | hack/run-e2e-test.sh | 126 | # Check if kind cluster exists | COMMENT |
| LOW⚡ | hack/run-e2e-test.sh | 131 | # Check if k3d cluster exists | COMMENT |
| LOW | hack/run-e2e-test.sh | 144 | # Check if cluster exists (dispatches based on CLUSTER_TYPE) | COMMENT |
| LOW | hack/run-e2e-test.sh | 243 | # Check if the pattern contains slashes (nested test path like TestKgateway/SessionPersistence/TestHeaderSessionPers | COMMENT |
| LOW | hack/run-e2e-test.sh | 268 | # Check if it's a top-level test function | COMMENT |
| LOW | hack/run-e2e-test.sh | 287 | # Check if it's a test method within a suite (e.g., TestCookieSessionPersistence) | COMMENT |
| LOW | hack/run-e2e-test.sh | 319 | # Check if this package identifier's import path matches our method's path | COMMENT |
| LOW | hack/run-e2e-test.sh | 400 | # Check if suite and method are the same across all patterns | COMMENT |
| LOW | hack/run-e2e-test.sh | 429 | # Check if it's a suite | COMMENT |
| LOW | hack/run-e2e-test.sh | 469 | # Check if the pattern might be a specific test method (starts with Test but not the suite name) | COMMENT |
| LOW | hack/run-e2e-test.sh | 640 | # Set FAIL_FAST_AND_PERSIST to true by default (for local development/debugging) | COMMENT |
| LOW | hack/run-e2e-test.sh | 707 | # Check if we should run setup | COMMENT |
| LOW | hack/run-e2e-test.sh | 810 | # Check if no tests were run | COMMENT |
| LOW | hack/run-test.sh | 210 | # Check if a pattern is an e2e test by finding where it's defined | COMMENT |
| LOW | hack/run-test.sh | 262 | # Check if pattern already starts with Test | COMMENT |
| LOW | hack/generate-release-notes.sh | 79 | # Check if a release note is effectively "NONE" | COMMENT |
| LOW | hack/generate-release-notes.sh | 85 | # Check if empty or "none" | COMMENT |
| LOW | hack/generate-release-notes.sh | 158 | # Check if git log has any output | COMMENT |
| LOW | hack/generate-release-notes.sh | 184 | # Check if PR exists | COMMENT |
| LOW | hack/generate-release-notes.sh | 316 | # Check if we found any release notes | COMMENT |
| LOW | hack/ci/get-recent-flakes.sh | 109 | # Check if this test already exists in our map | COMMENT |
| LOW | hack/ci/get-recent-flakes.sh | 145 | # Check if this test name is a prefix of any other test name in the list | COMMENT |
| LOW | hack/kind/setup-metalllb-on-kind.sh | 8 | # Set METALLB_VERSION to apply that upstream release instead, or METALLB_MANIFEST to apply | COMMENT |
| LOW | .github/actions/kube-conformance-tests/action.yaml | 114 | # Check if additional Helm values file is provided | COMMENT |
| LOW | …tions/mq-cancel-dangling-wfs/mq-cancel-dangling-wfs.sh | 43 | # Check if branch still exists | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| CRITICAL | pkg/deployer/deployer_test.go | 1707 | Expect(istioContainer.Resources.Limits.Cpu()).To(Equal(expectedGwp.Istio.IstioProxyContainer.Resources.Limits.Cpu())) | CODE |
| CRITICAL | pkg/deployer/deployer_test.go | 1708 | Expect(istioContainer.Resources.Requests.Cpu()).To(Equal(expectedGwp.Istio.IstioProxyContainer.Resources.Requests.Cpu | CODE |
| CRITICAL | …/kgateway/extensions2/plugins/listenerpolicy/common.go | 66 | if in.RetryPolicy.RetryBackOff.MaxInterval.Duration.Nanoseconds() < in.RetryPolicy.RetryBackOff.BaseInterval.Duratio | CODE |
| CRITICAL | …/kgateway/extensions2/plugins/listenerpolicy/common.go | 67 | logger.Error("retryPolicy.RetryBackOff.MaxInterval is lesser than RetryPolicy.RetryBackOff.MaxInterval. Ignoring Ma | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | test/e2e/tests/manifests/test-assertions.yaml | 1 | # This file defines Helm values that arm test-only assertions in the deployed control plane. | COMMENT |
| MEDIUM | test/e2e/tests/manifests/common-recommendations.yaml | 1 | # This file defines the common recommendations for a user who wants to run kgateway. | COMMENT |
| MEDIUM | internal/envoy_modules/generate-dockerfile.sh | 106 | # 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.yaml | 2 | # This file contains the common Gateway, HTTPRoutes, Services, and Secret | COMMENT |
| MEDIUM | …c-policy/local-and-global-combined/base-resources.yaml | 2 | # This file contains the common Gateway, HTTPRoutes, Services, and Secret | COMMENT |
| MEDIUM | …-policy/gateway-section-attachment/base-resources.yaml | 2 | # This file contains the common Gateway, HTTPRoutes, Services, and Secret | COMMENT |
| MEDIUM | …raffic-policy/filter-extension-ref/base-resources.yaml | 2 | # This file contains the common Gateway, HTTPRoutes, Services, and Secret | COMMENT |
| MEDIUM | …multiple-headers-single-descriptor/base-resources.yaml | 2 | # This file contains the common Gateway, HTTPRoutes, Services, and Secret | COMMENT |
| MEDIUM | …licy/multi-dimensional-descriptors/base-resources.yaml | 2 | # This file contains the common Gateway, HTTPRoutes, Services, and Secret | COMMENT |
| MEDIUM | …ls/inputs/traffic-policy/fail-open/base-resources.yaml | 2 | # This file contains the common Gateway, HTTPRoutes, Services, and Secret | COMMENT |
| MEDIUM | …ic-policy/route-section-attachment/base-resources.yaml | 2 | # This file contains the common Gateway, HTTPRoutes, Services, and Secret | COMMENT |
| MEDIUM | …ts/traffic-policy/global-ratelimit/base-resources.yaml | 2 | # This file contains the common Gateway, HTTPRoutes, Services, and Secret | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | test/deployer/deployer_helm.go | 362 | // and makes this helper robust to any kind the deployer might emit. | COMMENT |
| MEDIUM | test/e2e/features/route_delegation/testdata/common.yaml | 15 | # in the top-level test harness. HTTPRoutes in these testdata files use | COMMENT |
| LOW | hack/run-e2e-test.sh | 491 | # Fallback: just use the pattern as-is | COMMENT |
| MEDIUM | hack/kind/setup-metalllb-on-kind.sh | 64 | # something this harness sets up. | COMMENT |
| MEDIUM | pkg/deployer/deployer.go | 444 | // and the internal template isn't robust enough. | COMMENT |
| MEDIUM | pkg/envoyinit/run.go | 92 | // This configuration may leverage the Kubernetes Downward API | COMMENT |
| MEDIUM | …/translator/gateway/testutils/inputs/setup/common.yaml | 10 | # prioritization used its labels and locality. The translator harness does not: it | COMMENT |
| MEDIUM | …/extensions2/plugins/listenerpolicy/listener_plugin.go | 646 | // if we get more listener filters in the future we may need a more robust ordering mechanism | COMMENT |
| MEDIUM | pkg/utils/requestutils/curl/option.go | 285 | // set doesn't yet support, it should be added explicitly, to make it easier for developers to utilize | COMMENT |
| MEDIUM | pkg/krtcollections/uniqueclients_delay_test.go | 86 | // is deliberately loose (half the delay) to stay robust on slow CI. | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW⚡ | test/e2e/features/deployer/suite.go | 409 | // Step 1: Wait for the proxy deployment to be healthy | COMMENT |
| LOW⚡ | test/e2e/features/deployer/suite.go | 412 | // Step 2: Verify PDB, HPA, and VPA were created | COMMENT |
| LOW | test/e2e/features/deployer/suite.go | 441 | // Step 3: Update PDB configuration - change minAvailable from 1 to 0 | COMMENT |
| LOW | test/e2e/features/deployer/suite.go | 462 | // Step 4: Remove HPA and VPA from GatewayParameters (keep PDB) | COMMENT |
| LOW | test/e2e/features/deployer/suite.go | 494 | // Step 5: Delete the Gateway and verify all resources are cleaned up | COMMENT |
| LOW | test/e2e/features/apikeyauth/suite.go | 309 | // Step 1: Verify initial API keys work (k-123, k-456) | COMMENT |
| LOW | test/e2e/features/apikeyauth/suite.go | 324 | // Step 2: Update the secret with new keys (k-789, k-999) and remove old ones | COMMENT |
| LOW | test/e2e/features/apikeyauth/suite.go | 359 | // Step 3: Verify new keys work | COMMENT |
| LOW | test/e2e/features/apikeyauth/suite.go | 374 | // Step 4: Verify old keys no longer work | COMMENT |
| LOW | test/e2e/features/apikeyauth/suite.go | 389 | // Step 5: Update secret again to add back an old key and add a new one | COMMENT |
| LOW | test/e2e/features/apikeyauth/suite.go | 406 | // Step 6: Verify the final set of keys work | COMMENT |
| LOW | test/e2e/features/apikeyauth/suite.go | 434 | // Step 7: Verify removed keys no longer work | COMMENT |
| LOW | test/e2e/features/apikeyauth/suite.go | 651 | // Step 1: two Secrets carry the identical credential. The repeat is collapsed, so the route is | COMMENT |
| LOW | test/e2e/features/apikeyauth/suite.go | 668 | // Step 2: the differential. A brand new credential has to land while the duplicate pair is | COMMENT |
| LOW | test/e2e/features/apikeyauth/suite.go | 696 | // Step 3: the ambiguous duplicate. A second client claiming client1's key value cannot be | COMMENT |
| LOW | test/e2e/features/apikeyauth/suite.go | 747 | // Step 4: removing the conflict recovers the route. | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | test/e2e/features/http_acl/suite.go | 511 | // ── Phase 1: valid ACL policy only ─────────────────────────────────────── | COMMENT |
| MEDIUM | test/e2e/features/http_acl/suite.go | 537 | // ── Phase 2: add the invalid ACL policy ────────────────────────────────── | COMMENT |
| MEDIUM | …tutils/inputs/traffic-policy/acl-route-delegation.yaml | 12 | # ── Case 1: ShallowMergePreferChild ──────────────────────────────────────────── | COMMENT |
| MEDIUM | …tutils/inputs/traffic-policy/acl-route-delegation.yaml | 84 | # ── Case 2: ShallowMergePreferParent ─────────────────────────────────────────── | COMMENT |
| MEDIUM | …tutils/inputs/traffic-policy/acl-route-delegation.yaml | 155 | # ── Case 3: DeepMergePreferChild ─────────────────────────────────────────────── | COMMENT |
| MEDIUM | …tutils/inputs/traffic-policy/acl-route-delegation.yaml | 227 | # ── Case 4: DeepMergePreferParent ────────────────────────────────────────────── | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | test/gomega/assertions/goroutines.go | 23 | // Example usage: | COMMENT |
| LOW | test/helpers/timeouts.go | 36 | // Example usage: | COMMENT |
| LOW | test/helpers/timeouts.go | 50 | // Example usage: | COMMENT |
| LOW | hack/xds-fleet-ab.sh | 12 | # Usage: | COMMENT |
| LOW | hack/k3d/k3d-loadbalancer.sh | 12 | # Usage: | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | …ay/extensions2/plugins/backendconfigpolicy/tls_test.go | 613 | sanList: []string{"svc@example.org"}, | CODE |
| LOW | …ay/extensions2/plugins/backendconfigpolicy/tls_test.go | 618 | MatchPattern: &envoymatcher.StringMatcher_Exact{Exact: "svc@example.org"}, | CODE |
| LOW | pkg/xds/bootstrap/builder.go | 185 | StatPrefix: "placeholder", | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | …n/11177-ai-extensions-opentelemetry-tracing-support.md | 388 | async def handle_request_body_req_webhook( | CODE |
| LOW | …n/11177-ai-extensions-opentelemetry-tracing-support.md | 454 | def handle_request_body_req_regex( | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | install/helm/kgateway/values.yaml | 277 | # -- Configure the default container image for the components that Helm deploys. You can override these settings for eac | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | pkg/kgateway/extensions2/plugins/istio/plugin.go | 94 | // TODO: implement this | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | …n/11177-ai-extensions-opentelemetry-tracing-support.md | 554 | except Exception as e: | CODE |