Achieve state of the art inference performance with modern accelerators on Kubernetes
This report presents the forensic synthetic code analysis of llm-d/llm-d, a Shell project with 3,798 GitHub stars. SynthScan v2.0 examined 62,050 lines of code across 648 source files, recording 249 pattern matches distributed across 11 syntactic categories. The overall adjusted score of 9.0 places this repository in the Low AI signal band.
The scanner applied 160+ deterministic lexical heuristics, multi-line block detectors, abstract syntax tree depth profilers, and a cross-file Jaccard similarity matrix to construct a statistically normalised synthetic code estimate. All matches are individually weighted by severity coefficient and contextual multiplier before summation, and the resulting headline score is temporally discounted to account for the repository's development history relative to the commercial emergence of large language model coding tooling (November 2022 onward).
This chart maps the temporal evolution of the adjusted synthetic code score across successive scan runs. An upward trajectory indicates ongoing incorporation of AI-generated code or expanding LLM-assisted scaffolding; a stable or declining trajectory may reflect active human refactoring, code removal, or the adoption of stricter authorship policies. The dashed secondary line (right axis) independently tracks total raw pattern hit count, which can diverge from the normalised score when codebase size changes significantly between scans.
Classifies detected patterns by their diagnostic confidence and structural impact. CRITICAL patterns (coefficient 10) represent definitive synthetic signatures — hallucinated imports, explicit LLM attribution metadata — virtually never produced by human authors. HIGH (5) indicates strong structural tells such as cross-file repetition or cross-linguistic idioms. MEDIUM (2) covers recognisable conversational padding and AI-specific vocabulary. LOW (1) captures subtle indicators like tautological comments and generic boilerplate that require density to carry independent signal.
This horizontal bar chart decomposes the repository's raw synthetic code score by top-level directory, allowing you to pinpoint precisely which modules or components carry the highest AI authorship density. Directories with disproportionately high scores relative to their size warrant targeted manual review: concentrated AI signatures often trace back to mass-generated configuration layers, auto-ported test suites, LLM-scaffolded boilerplate classes, or entire subsystems authored under heavy copilot assistance. Use this view to prioritise your human code-review effort.
The scanner identified 249 distinct pattern matches across 11 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a statistically significant AI authorship indicator. 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 diagnostic confidence level (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — comment-context matches receive a ×1.5 weight because LLMs systematically over-annotate. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier as dense clusters constitute far stronger evidence of synthetic authorship than isolated hits.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | docker/scripts/cuda/common/install-efa.sh | 6 | # ------------------------------- | COMMENT |
| MEDIUM | docker/scripts/cuda/builder/build-ucx.sh | 5 | # -------------------------------------------- | COMMENT |
| MEDIUM | docker/scripts/cuda/builder/build-ucx.sh | 9 | # -------------------------------------------- | COMMENT |
| MEDIUM | guides/flow-control/scripts/tuning_wizard.py | 18 | # ========================================== | COMMENT |
| MEDIUM | guides/flow-control/scripts/tuning_wizard.py | 20 | # ========================================== | COMMENT |
| MEDIUM⚡ | guides/flow-control/scripts/tuning_wizard.py | 45 | # ========================================== | COMMENT |
| MEDIUM⚡ | guides/flow-control/scripts/tuning_wizard.py | 47 | # ========================================== | COMMENT |
| MEDIUM | guides/flow-control/scripts/tuning_wizard.py | 104 | # ========================================== | COMMENT |
| MEDIUM | guides/flow-control/scripts/tuning_wizard.py | 106 | # ========================================== | COMMENT |
| MEDIUM | …s/recipes/observability/alerts/epp-alerting-rules.yaml | 9 | # --------------------------------------------------------------------------- | COMMENT |
| MEDIUM | …s/recipes/observability/alerts/epp-alerting-rules.yaml | 11 | # --------------------------------------------------------------------------- | COMMENT |
| MEDIUM | …s/recipes/observability/alerts/epp-alerting-rules.yaml | 63 | # --------------------------------------------------------------------------- | COMMENT |
| MEDIUM | …s/recipes/observability/alerts/epp-alerting-rules.yaml | 65 | # --------------------------------------------------------------------------- | COMMENT |
| MEDIUM⚡ | …chmark-templates/agentic-serving-nemotron-3-ultra.yaml | 1 | # --------------------------------------------------------------------------- | COMMENT |
| MEDIUM⚡ | …chmark-templates/agentic-serving-nemotron-3-ultra.yaml | 18 | # --------------------------------------------------------------------------- | COMMENT |
| MEDIUM | guides/agentic-serving/benchmark-templates/guide.yaml | 1 | # --------------------------------------------------------------------------- | COMMENT |
| MEDIUM | guides/agentic-serving/benchmark-templates/guide.yaml | 22 | # --------------------------------------------------------------------------- | COMMENT |
| MEDIUM⚡ | scripts/sync-nightly-matrix.py | 14 | # --------------------------------------------------------------------------- | COMMENT |
| MEDIUM⚡ | scripts/sync-nightly-matrix.py | 16 | # --------------------------------------------------------------------------- | COMMENT |
| MEDIUM⚡ | scripts/sync-nightly-matrix.py | 22 | # --------------------------------------------------------------------------- | COMMENT |
| MEDIUM⚡ | scripts/sync-nightly-matrix.py | 24 | # --------------------------------------------------------------------------- | COMMENT |
| MEDIUM⚡ | scripts/sync-nightly-matrix.py | 29 | # --------------------------------------------------------------------------- | COMMENT |
| MEDIUM⚡ | scripts/sync-nightly-matrix.py | 31 | # --------------------------------------------------------------------------- | COMMENT |
| MEDIUM | scripts/sync-nightly-matrix.py | 66 | # --------------------------------------------------------------------------- | COMMENT |
| MEDIUM | scripts/sync-nightly-matrix.py | 69 | # --------------------------------------------------------------------------- | COMMENT |
| MEDIUM | scripts/sync-nightly-matrix.py | 175 | # --------------------------------------------------------------------------- | COMMENT |
| MEDIUM | scripts/sync-nightly-matrix.py | 177 | # --------------------------------------------------------------------------- | COMMENT |
| MEDIUM | scripts/sync-nightly-matrix.py | 201 | # --------------------------------------------------------------------------- | COMMENT |
| MEDIUM | scripts/sync-nightly-matrix.py | 203 | # --------------------------------------------------------------------------- | COMMENT |
| MEDIUM | .github/scripts/e2e/e2e-validate.sh | 4 | # ----------------------------------------------------------------------------- | COMMENT |
| MEDIUM | .github/scripts/e2e/e2e-validate.sh | 6 | # ----------------------------------------------------------------------------- | COMMENT |
| MEDIUM | .github/scripts/e2e/e2e-validate.sh | 24 | # ── Defaults ──────────────────────────────────────────────────────────────── | COMMENT |
| MEDIUM | .github/scripts/e2e/e2e-validate.sh | 30 | # ── Flag parsing ──────────────────────────────────────────────────────────── | COMMENT |
| MEDIUM | .github/scripts/e2e/e2e-validate.sh | 46 | # ── Persistent curl pod ───────────────────────────────────────────────────── | COMMENT |
| MEDIUM⚡ | .github/scripts/e2e/e2e-validate.sh | 83 | # ── Run curl via kubectl exec on the persistent pod ───────────────────────── | COMMENT |
| MEDIUM⚡ | .github/scripts/e2e/e2e-validate.sh | 93 | # ── Discover Gateway address ──────────────────────────────────────────────── | COMMENT |
| MEDIUM⚡ | .github/scripts/e2e/e2e-validate.sh | 103 | # ── Create persistent curl pod ────────────────────────────────────────────── | COMMENT |
| MEDIUM⚡ | .github/scripts/e2e/e2e-validate.sh | 106 | # ── Determine MODEL_ID ────────────────────────────────────────────────────── | COMMENT |
| MEDIUM | .github/scripts/e2e/e2e-validate.sh | 162 | # ── Main test loop (10 iterations) ────────────────────────────────────────── | COMMENT |
| MEDIUM | .github/scripts/e2e/e2e-validate.sh | 211 | # ── Optional: hand off to a guide-specific validator ──────────────────────── | COMMENT |
| MEDIUM | .github/scripts/e2e/e2e-validate-predicted-latency.sh | 4 | # ----------------------------------------------------------------------------- | COMMENT |
| MEDIUM | .github/scripts/e2e/e2e-validate-predicted-latency.sh | 6 | # ----------------------------------------------------------------------------- | COMMENT |
| MEDIUM | .github/scripts/e2e/e2e-validate-predicted-latency.sh | 21 | # ----------------------------------------------------------------------------- | COMMENT |
| MEDIUM | .github/scripts/e2e/e2e-validate-predicted-latency.sh | 90 | # ── Discover EPP service ──────────────────────────────────────────────────── | COMMENT |
| MEDIUM | .github/scripts/e2e/e2e-validate-predicted-latency.sh | 122 | # ── Discover model ────────────────────────────────────────────────────────── | COMMENT |
| MEDIUM | .github/scripts/e2e/e2e-validate-predicted-latency.sh | 144 | # ── Warmup loop: feed the predictor's training window ─────────────────────── | COMMENT |
| MEDIUM | .github/scripts/e2e/e2e-validate-predicted-latency.sh | 172 | # ── Scrape EPP /metrics ───────────────────────────────────────────────────── | COMMENT |
| MEDIUM | .github/scripts/e2e/e2e-validate-flow-control.sh | 4 | # ----------------------------------------------------------------------------- | COMMENT |
| MEDIUM | .github/scripts/e2e/e2e-validate-flow-control.sh | 6 | # ----------------------------------------------------------------------------- | COMMENT |
| MEDIUM | .github/scripts/e2e/e2e-validate-flow-control.sh | 21 | # ----------------------------------------------------------------------------- | COMMENT |
| MEDIUM | .github/scripts/e2e/e2e-validate-flow-control.sh | 92 | # ── Discover EPP service ──────────────────────────────────────────────────── | COMMENT |
| MEDIUM | .github/scripts/e2e/e2e-validate-flow-control.sh | 118 | # ── Discover model ────────────────────────────────────────────────────────── | COMMENT |
| MEDIUM | .github/scripts/e2e/e2e-validate-flow-control.sh | 140 | # ── Stage the request payload on the curl pod ─────────────────────────────── | COMMENT |
| MEDIUM | .github/scripts/e2e/e2e-validate-flow-control.sh | 147 | # ── Metric extraction helpers ─────────────────────────────────────────────── | COMMENT |
| MEDIUM | .github/scripts/e2e/e2e-validate-flow-control.sh | 213 | # ── Mixed-contention burst: all three bands at once ───────────────────────── | COMMENT |
| MEDIUM | .github/scripts/e2e/e2e-validate-flow-control.sh | 272 | # ── (1) Each band landed in its own queue ─────────────────────────────────── | COMMENT |
| MEDIUM | .github/scripts/e2e/e2e-validate-flow-control.sh | 287 | # ── (2) QoS: best-effort waits longer than premium under contention ───────── | COMMENT |
| MEDIUM | helpers/smoke-test/healthcheck.sh | 4 | # ----------------------------------------------------------------------------- | COMMENT |
| MEDIUM | helpers/smoke-test/healthcheck.sh | 19 | # ----------------------------------------------------------------------------- | COMMENT |
| MEDIUM | helpers/smoke-test/healthcheck.sh | 21 | # ── Defaults ───────────────────────────────────────────────────────────────── | COMMENT |
| 20 more matches not shown… | ||||
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | docs/operations/observability/setup.md | 11 | ## Step 1: Install Prometheus and Grafana | COMMENT |
| LOW | docs/operations/observability/setup.md | 144 | ## Step 2: Load Grafana Dashboards | COMMENT |
| LOW | docs/operations/observability/setup.md | 174 | ## Step 3: Install Distributed Tracing (Optional) | COMMENT |
| LOW | docs/operations/observability/alerting.md | 19 | ## Step 1: Apply the Alerting Rules | COMMENT |
| LOW | docs/operations/observability/alerting.md | 30 | ## Step 2: Verify | COMMENT |
| LOW | docs/operations/observability/tracing.md | 24 | ## Step 1: Deploy OTel Collector and Jaeger | COMMENT |
| LOW | docs/operations/observability/tracing.md | 68 | ## Step 2: Enable Tracing on the Model Server and Routing Proxy | COMMENT |
| LOW | docs/operations/observability/tracing.md | 89 | ## Step 3: Enable Tracing on EPP | COMMENT |
| LOW | docs/operations/observability/tracing.md | 104 | ## Step 4: View Traces | COMMENT |
| LOW | docs/operations/observability/metrics.md | 16 | ## Step 1: Enable Model Server Metrics | COMMENT |
| LOW | docs/operations/observability/metrics.md | 75 | ## Step 3: Enable EPP Metrics | COMMENT |
| LOW | docs/operations/observability/metrics.md | 125 | ## Step 4: View Dashboards | COMMENT |
| LOW | docs/operations/observability/metrics.md | 177 | ## Step 5: Query Metrics | COMMENT |
| LOW | docs/operations/rollouts/adapter-rollout.md | 58 | ## Step 1: Establishing A Baseline (Alias v1) | COMMENT |
| LOW | docs/operations/rollouts/adapter-rollout.md | 140 | ## Step 2: Gradual Rollout | COMMENT |
| LOW⚡ | docs/infrastructure/providers/openshift-aws/README.md | 16 | ## Step 1: Create a Red Hat OpenShift Service on AWS (ROSA) Cluster | COMMENT |
| LOW⚡ | docs/infrastructure/providers/openshift-aws/README.md | 25 | ## Step 2: Add a Machineset with NVIDIA GPU Instances | COMMENT |
| LOW⚡ | docs/infrastructure/providers/openshift-aws/README.md | 34 | ## Step 3: Enable GPU support on OpenShift with the NFD and GPU Operators | COMMENT |
| LOW | docs/infrastructure/gateway/gke.md | 21 | ## Step 1: Install Gateway API and Gateway API Inference Extension CRDs | COMMENT |
| LOW | docs/infrastructure/gateway/gke.md | 41 | ## Step 2: Deploy the Gateway | COMMENT |
| LOW | docs/infrastructure/gateway/gke.md | 65 | ## Step 3: Verify the Gateway | COMMENT |
| LOW | docs/infrastructure/gateway/gke.md | 82 | ## Step 4: Send a Request | COMMENT |
| LOW | docs/infrastructure/gateway/agentgateway.md | 18 | ## Step 1: Install Gateway API and Gateway API Inference Extension CRDs | COMMENT |
| LOW | docs/infrastructure/gateway/agentgateway.md | 22 | ## Step 2: Install Agentgateway | COMMENT |
| LOW | docs/infrastructure/gateway/agentgateway.md | 58 | ## Step 3: Deploy the Gateway | COMMENT |
| LOW | docs/infrastructure/gateway/agentgateway.md | 99 | ## Step 4: Send a Request | COMMENT |
| LOW | docs/infrastructure/gateway/envoy-ai-gateway.md | 18 | ## Step 1: Install Gateway API and Gateway API Inference Extension CRDs | COMMENT |
| LOW | docs/infrastructure/gateway/envoy-ai-gateway.md | 22 | ## Step 2: Install Envoy AI Gateway | COMMENT |
| LOW | docs/infrastructure/gateway/envoy-ai-gateway.md | 128 | ## Step 3: Deploy the Gateway | COMMENT |
| LOW | docs/infrastructure/gateway/envoy-ai-gateway.md | 157 | ## Step 4: Send a Request | COMMENT |
| LOW | docs/infrastructure/gateway/istio.md | 15 | ## Step 1: Install Gateway API and Gateway API Inference Extension CRDs | COMMENT |
| LOW | docs/infrastructure/gateway/istio.md | 19 | ## Step 2: Install Istio | COMMENT |
| LOW | docs/infrastructure/gateway/istio.md | 44 | ## Step 3: Deploy the Gateway | COMMENT |
| LOW | docs/infrastructure/gateway/istio.md | 73 | ## Step 4: Send a Request | COMMENT |
| LOW | guides/asynchronous-processing/README.md | 32 | #### Step 1: Deploy llm-d Router | COMMENT |
| LOW | guides/asynchronous-processing/README.md | 45 | #### Step 2: Configure Values | COMMENT |
| LOW | guides/asynchronous-processing/README.md | 52 | #### Step 3: Deploy Async Processor | COMMENT |
| LOW | …prefix-cache/modelserver/tpu/base/vllm/patch-vllm.yaml | 18 | # WARNING: This changes the HOST memory settings, not just the container. | COMMENT |
| LOW | guides/batch-gateway/README.md | 45 | ### Step 1: Create the Namespace | COMMENT |
| LOW | guides/batch-gateway/README.md | 52 | ### Step 2: Create the Secrets | COMMENT |
| LOW | guides/batch-gateway/README.md | 63 | ### Step 3: Configure the llm-d Router URL | COMMENT |
| LOW | guides/batch-gateway/README.md | 75 | ### Step 4: Deploy | COMMENT |
| LOW | guides/flow-control/tuning.md | 43 | ### Step 1: Gather System Telemetry (For Compute Bound) | COMMENT |
| LOW | guides/flow-control/tuning.md | 55 | ### Step 2: Gather Workload Statistics (For Memory Bound) | COMMENT |
| LOW | guides/flow-control/tuning.md | 65 | ### Step 3: Run the Tuning Wizard | COMMENT |
| LOW | guides/flow-control/tuning.md | 103 | ### Step 4: Apply Configuration | COMMENT |
| LOW | guides/multi-model-routing/README.md | 56 | ## Step 1: Deploy IPP | COMMENT |
| LOW | guides/multi-model-routing/README.md | 82 | ## Step 2: Create Model Mapping ConfigMaps | COMMENT |
| LOW | guides/multi-model-routing/README.md | 95 | ## Step 3: Configure HTTPRoutes | COMMENT |
| LOW | guides/multi-model-routing/README.md | 107 | ## Step 4: Test the Deployment | COMMENT |
| LOW | …s/agentic-serving/modelserver/tpu/vllm/patch-vllm.yaml | 15 | # WARNING: This changes the HOST memory settings, not just the container. | COMMENT |
| LOW | …des/workload-autoscaling/README.replica-rebalancing.md | 36 | ## Step 1: Define a GPU ResourceQuota | COMMENT |
| LOW | …des/workload-autoscaling/README.replica-rebalancing.md | 59 | ## Step 2: Enable the Replica Rebalancer | COMMENT |
| LOW | …des/workload-autoscaling/README.replica-rebalancing.md | 81 | ## Step 3: Opt HPAs Into Replica Rebalancer Management | COMMENT |
| LOW | …des/workload-autoscaling/README.replica-rebalancing.md | 146 | ## Step 4: Verify Replica Rebalancer Behavior | COMMENT |
| LOW | …es/workload-autoscaling/README.multi-inference-pool.md | 12 | ## Step 1: Deploy an Additional Helm Release | COMMENT |
| LOW | …es/workload-autoscaling/README.multi-inference-pool.md | 42 | ## Step 2: Deploy the Model Server | COMMENT |
| LOW | .github/workflows/link-checker.md | 46 | #### Step 1: Identify Changed Markdown Files | COMMENT |
| LOW | .github/workflows/link-checker.md | 56 | #### Step 2: Extract and Check Links | COMMENT |
| LOW | .github/workflows/link-checker.md | 74 | #### Step 3: Classify Results | COMMENT |
| 10 more matches not shown… | ||||
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | guides/recipes/router/calibration/calibrate.sh | 12 | # GUIDE_NAME=agentic-serving NAMESPACE=llm-d-agentic-serving \ | COMMENT |
| MEDIUM | guides/predicted-latency-routing/README.md | 300 | Uses the agentic-serving guide's `inference-perf` workload, tuned for the 480B model and very long (up to 256K-token) co | CODE |
| MEDIUM | guides/predicted-latency-routing/README.md | 303 | # Fetch the existing-stack benchmark runner from llm-d-benchmark (the script the agentic-serving guide uses). | COMMENT |
| MEDIUM | …atency-routing/modelserver/tpu/vllm/kustomization.yaml | 4 | # Reuse the agentic-serving guide's TPU model server: Qwen3-Coder-480B-A35B-Instruct-FP8 | COMMENT |
| MEDIUM | …d-latency-routing/router/predicted-latency.values.yaml | 26 | # Sized for the 256K-context TPU agentic case (Qwen3-Coder-480B): matching longer | COMMENT |
| MEDIUM | …d-latency-routing/router/predicted-latency.values.yaml | 27 | # prefixes raises the cache-hit rate on long, shared agentic prompts. Tradeoff: it | COMMENT |
| MEDIUM | …tency-routing/router/predicted-latency-slo.values.yaml | 27 | # Sized for the 256K-context TPU agentic case (Qwen3-Coder-480B): matching longer | COMMENT |
| MEDIUM | …tency-routing/router/predicted-latency-slo.values.yaml | 28 | # prefixes raises the cache-hit rate on long, shared agentic prompts. Tradeoff: it | COMMENT |
| MEDIUM | guides/agentic-serving/nemotron-3-ultra-550b-h200.md | 153 | # from the guide directory: guides/agentic-serving | COMMENT |
| MEDIUM | guides/agentic-serving/nemotron-3-ultra-550b-h200.md | 161 | # from the guide directory: guides/agentic-serving | COMMENT |
| MEDIUM | guides/agentic-serving/nemotron-3-ultra-550b-h200.md | 194 | curl -LJO "https://raw.githubusercontent.com/llm-d/llm-d/main/guides/${GUIDE_NAME}/benchmark-templates/agentic-serving-n | CODE |
| MEDIUM⚡ | …chmark-templates/agentic-serving-nemotron-3-ultra.yaml | 2 | # inference-perf workload template for the agentic-serving guide | COMMENT |
| MEDIUM⚡ | …chmark-templates/agentic-serving-nemotron-3-ultra.yaml | 12 | # Render with `envsubst < agentic-serving-nemotron-3-ultra.yaml > config.yaml` | COMMENT |
| MEDIUM | guides/agentic-serving/benchmark-templates/guide.yaml | 2 | # inference-perf workload template for the agentic-serving guide. | COMMENT |
| MEDIUM⚡ | …-serving/router/agentic-serving-tpu-disagg.values.yaml | 1 | ## agentic-serving (TPU / P/D-disaggregated) guide overrides for the llm-d router. | COMMENT |
| MEDIUM⚡ | …-serving/router/agentic-serving-tpu-disagg.values.yaml | 4 | ## This deployment serves the agentic code-generation workload on Google TPUs with | COMMENT |
| MEDIUM⚡ | …-serving/router/agentic-serving-tpu-disagg.values.yaml | 7 | ## by the non-disaggregated TPU deployment in agentic-serving.values.yaml. | COMMENT |
| MEDIUM⚡ | …agentic-serving/router/agentic-serving-gpu.values.yaml | 1 | ## agentic-serving (GPU / P/D-disaggregated) guide overrides for the llm-d router. | COMMENT |
| MEDIUM⚡ | …agentic-serving/router/agentic-serving-gpu.values.yaml | 4 | ## This deployment serves the agentic code-generation workload on NVIDIA GPUs with | COMMENT |
| MEDIUM⚡ | …agentic-serving/router/agentic-serving-gpu.values.yaml | 7 | ## by the non-disaggregated TPU deployment in agentic-serving.values.yaml. | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | …r/scripts/cuda/runtime/install-offloading-connector.sh | 1 | #!/bin/bash | COMMENT |
| LOW | docker/scripts/cuda/runtime/install-vllm.sh | 1 | #!/bin/bash | COMMENT |
| LOW | docker/scripts/cuda/builder/build-nixl.sh | 1 | #!/bin/bash | COMMENT |
| LOW | docker/scripts/cuda/builder/build-nvshmem.sh | 1 | #!/bin/bash | COMMENT |
| LOW | docker/scripts/cuda/builder/build-nvshmem.sh | 81 | CMAKE_EXTRA_FLAGS+=( | COMMENT |
| LOW | docker/scripts/cuda/builder/build-lmcache.sh | 1 | #!/bin/bash | COMMENT |
| LOW | docker/scripts/cuda/builder/build-lmcache.sh | 21 | # so libcuda.so is not available from the host. | COMMENT |
| LOW | docker/scripts/cuda/builder/build-gdrcopy.sh | 1 | #!/bin/bash | COMMENT |
| LOW | docker/scripts/cuda/builder/build-compiled-wheels.sh | 1 | #!/bin/bash | COMMENT |
| LOW | docker/scripts/cuda/builder/build-ucx.sh | 1 | #!/bin/bash | COMMENT |
| LOW | …des/no-kubernetes-deployment/router/epp/endpoints.yaml | 1 | # Endpoints file consumed by the file-discovery plugin. | COMMENT |
| LOW | guides/no-kubernetes-deployment/router/envoy/envoy.yaml | 1 | # Envoy config for the no-Kubernetes file-discovery deployment. | COMMENT |
| LOW | …des/wide-ep-lws/modelserver/gpu/vllm/base/prefill.yaml | 81 | --all2all-backend deepep_high_throughput | COMMENT |
| LOW | guides/wide-ep-lws/monitoring/kustomization.yaml | 1 | apiVersion: kustomize.config.k8s.io/v1alpha1 | COMMENT |
| LOW | …outing/router/precise-prefix-cache-routing.values.yaml | 1 | ## precise-prefix-cache-routing guide overrides for the router. | COMMENT |
| LOW | guides/recipes/observability/generate-traffic-pd.sh | 1 | #!/bin/bash | COMMENT |
| LOW | guides/recipes/router/calibration/calibrate.sh | 1 | #!/bin/bash | COMMENT |
| LOW | guides/recipes/router/calibration/calibrate.sh | 21 | # MODEL_NAME — model name vLLM is serving (default: Qwen/Qwen3-32B) | COMMENT |
| LOW | …-baseline/modelserver/gpu/vllm/gpt-oss/patch-vllm.yaml | 21 | - "--reasoning-parser=openai_gptoss" | COMMENT |
| LOW | …zed-baseline/modelserver/gpu/vllm/base/patch-vllm.yaml | 21 | - name: HF_TOKEN | COMMENT |
| LOW | …baseline/modelserver/gpu/sglang/base/patch-sglang.yaml | 21 | # - "--otlp-traces-endpoint=http://otel-collector:4317" | COMMENT |
| LOW | …ptimized-baseline/modelserver/cpu/vllm/patch-vllm.yaml | 21 | - name: HF_TOKEN | COMMENT |
| LOW | …ptimized-baseline/modelserver/xpu/vllm/patch-vllm.yaml | 21 | - "--disable-access-log-for-endpoints=/health,/metrics,/v1/models" | COMMENT |
| LOW | …ized-baseline/modelserver/amd/sglang/patch-sglang.yaml | 21 | # - "--enable-trace" | COMMENT |
| LOW | …mized-baseline/modelserver/tpu/v6/vllm/patch-vllm.yaml | 21 | # - "--otlp-traces-endpoint=http://otel-collector:4317" | COMMENT |
| LOW | …mized-baseline/modelserver/tpu/v7/vllm/patch-vllm.yaml | 21 | # - "--otlp-traces-endpoint=http://otel-collector:4317" | COMMENT |
| LOW | …chmark-templates/agentic-serving-nemotron-3-ultra.yaml | 1 | # --------------------------------------------------------------------------- | COMMENT |
| LOW | guides/agentic-serving/benchmark-templates/guide.yaml | 1 | # --------------------------------------------------------------------------- | COMMENT |
| LOW | …ving/aggregation/modelserver/base/vllm/patch-vllm.yaml | 21 | env: | COMMENT |
| LOW | …d-baseline-autoscaling/keda/base/wva-scaledobject.yaml | 1 | # KEDA ScaledObject driven by WVA's wva_desired_replicas metric. | COMMENT |
| LOW | …des/workload-autoscaling/scripts/nightly-deploy-cks.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | .github/workflows/slash-test-nightly.yaml | 1 | name: /test-nightly Slash Command | COMMENT |
| LOW | .github/workflows/slash-test-nightly.yaml | 21 | # Examples: | COMMENT |
| LOW | .github/scripts/e2e/e2e-validate-predicted-latency.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | .github/scripts/e2e/e2e-validate-predicted-latency.sh | 81 | kubectl delete pod -n "$NAMESPACE" "$CURL_POD_NAME" --ignore-not-found >/dev/null 2>&1 || true | COMMENT |
| LOW | .github/scripts/e2e/e2e-validate-flow-control.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | helpers/smoke-test/healthcheck.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | helpers/client-setup/install-deps.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | …ers/local-llm-d-cuda-builder/build-local-llm-d-cuda.sh | 1 | #!/usr/bin/env bash | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | …re/providers/digitalocean/gpu-configs/l40s-values.yaml | 38 | # Enable comprehensive metrics collection | COMMENT |
| MEDIUM | …ders/digitalocean/gpu-configs/rtx-4000-ada-values.yaml | 47 | # Enable comprehensive metrics collection | COMMENT |
| MEDIUM | …ders/digitalocean/gpu-configs/rtx-6000-ada-values.yaml | 36 | # Enable comprehensive metrics collection | COMMENT |
| MEDIUM | guides/pd-disaggregation/benchmark-templates/tpu.yaml | 17 | namespace: *namespace # Namespace where harness is deployed. Typically with stack. | CODE |
| MEDIUM | guides/pd-disaggregation/benchmark-templates/tpu.yaml | 28 | workload: # yaml configuration for harness workload(s) | CODE |
| MEDIUM | …chmark-templates/agentic-serving-nemotron-3-ultra.yaml | 35 | namespace: *namespace # Namespace where harness is deployed. Typically with stack. | CODE |
| MEDIUM | guides/agentic-serving/benchmark-templates/guide.yaml | 39 | namespace: *namespace # Namespace where harness is deployed. Typically with stack. | CODE |
| MEDIUM | guides/agentic-serving/benchmark-templates/guide.yaml | 49 | workload: # yaml configuration for harness workload(s) | CODE |
| LOW | scripts/warn-vllm-precompiled.sh | 41 | # Append to vllm user's rc if it exists; otherwise just create it | COMMENT |
| MEDIUM | .github/workflows/slash-test-nightly.yaml | 13 | # harness=<name> Benchmark harness (default: inference-perf) | COMMENT |
| MEDIUM | .github/scripts/e2e/e2e-validate-flow-control.sh | 274 | # missed by scrape timing, so it is the robust backbone assertion. | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | …ture/providers/digitalocean/verify-do-prerequisites.sh | 60 | # Check if we're on DOKS | COMMENT |
| LOW | …ture/providers/digitalocean/verify-do-prerequisites.sh | 123 | # Check if DO CSI driver is available | COMMENT |
| LOW | …/providers/digitalocean/monitoring/setup-monitoring.sh | 72 | # Check if kubectl can connect to cluster | COMMENT |
| LOW | …/providers/digitalocean/monitoring/setup-monitoring.sh | 177 | # Check if release already exists | COMMENT |
| LOW | …prefix-cache/modelserver/tpu/base/vllm/patch-vllm.yaml | 22 | # Check if the VFIO IOMMU module parameter exists, and if so, increase the | COMMENT |
| LOW | …recipes/observability/generate-prometheus-tls-certs.sh | 185 | # Check if namespace exists | COMMENT |
| LOW | guides/recipes/observability/load-llm-d-dashboards.sh | 31 | # Check if namespace exists | COMMENT |
| LOW | guides/recipes/observability/load-llm-d-dashboards.sh | 37 | # Check if dashboard directory exists | COMMENT |
| LOW | …es/recipes/observability/install-prometheus-grafana.sh | 240 | # Check if certificates already exist | COMMENT |
| LOW | …es/recipes/observability/install-prometheus-grafana.sh | 268 | # Check if user workload monitoring is enabled | COMMENT |
| LOW | …s/agentic-serving/modelserver/tpu/vllm/patch-vllm.yaml | 19 | # Check if the VFIO IOMMU module parameter exists, and if so, increase the | COMMENT |
| LOW | .github/scripts/e2e/e2e-validate.sh | 134 | # Check if we got a specific error | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | docker/scripts/cpu/install_nixl.py | 45 | def install_system_dependencies(): | CODE |
| LOW | docker/scripts/cpu/install_nixl.py | 74 | def build_and_install_prerequisites(args): | CODE |
| LOW⚡ | guides/flow-control/scripts/tuning_wizard.py | 49 | def calculate_compute_constraint(throughput: float, latency_sec: float) -> int: | CODE |
| LOW⚡ | guides/flow-control/scripts/tuning_wizard.py | 53 | def calculate_memory_constraint( | CODE |
| LOW | guides/flow-control/scripts/tuning_wizard.py | 91 | def calculate_lookahead_buffer(active_batch: int, max_num_batched_tokens: int, isl_mean: Optional[float]) -> int: | CODE |
| LOW | scripts/lint-envvars.py | 36 | def find_locally_defined_vars(script_content: str) -> Set[str]: | CODE |
| LOW | scripts/lint-dockerfile-envvars.py | 12 | def parse_script_requirements(script_path: Path) -> Set[str]: | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | …recipes/observability/generate-prometheus-tls-certs.sh | 104 | # Define the Prometheus service DNS names | COMMENT |
| MEDIUM | …recipes/observability/generate-prometheus-tls-certs.sh | 197 | # Create the secret | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | scripts/lint-envvars.py | 94 | except Exception as e: | CODE |
| LOW | scripts/lint-dockerfile-envvars.py | 16 | except Exception: | CODE |
| MEDIUM | scripts/lint-dockerfile-envvars.py | 180 | print(f"Error: Scripts directory not found: {scripts_dir}", file=sys.stderr) | CODE |
| MEDIUM | scripts/lint-dockerfile-envvars.py | 186 | print(f"Error: Dockerfile not found: {dockerfile}", file=sys.stderr) | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | guides/recipes/router/calibration/calibrate.sh | 11 | # Usage: | COMMENT |
| LOW⚡ | …ers/local-llm-d-cuda-builder/build-local-llm-d-cuda.sh | 5 | # Usage: | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | scripts/sync-nightly-matrix.py | 147 | CODE | |
| LOW | scripts/lint-dockerfile-envvars.py | 45 | CODE |