This report summarizes scanner evidence for Project-HAMi/HAMi. SynthScan examined 146,102 lines of code across 497 source files, recording 140 pattern matches distributed across 8 syntactic categories. The legacy adjusted pattern signal is 1.3 (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? 139 finding(s).
Are imports declared and package/API names verified? 1 finding(s).
Are wrappers, guards, and repeated structures necessary? 0 finding(s).
Which changes need focused human review? 140 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 140 distinct pattern matches across 8 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 | cmd/vGPUmonitor/metrics.go | 741 | return fmt.Errorf("failed to create metric: %w", err) | COMMENT |
| LOW | cmd/scheduler/router_test.go | 181 | // Malformed on purpose: every handler rejects it while decoding, before it | COMMENT |
| LOW | docker/entrypoint.sh | 1 | #!/bin/bash | COMMENT |
| LOW | charts/hami/Chart.yaml | 1 | apiVersion: v2 | COMMENT |
| LOW | charts/hami/values.yaml | 1 | # Chart-wide settings; the description of each one names the components it applies to. | COMMENT |
| LOW | charts/hami/values.yaml | 61 | enabled: false | COMMENT |
| LOW | charts/hami/values.yaml | 81 | # -- (float) Bonus added to the node score for nodes matching a Pod's preferred `nodeAffinity`, scaled by the matche | COMMENT |
| LOW | charts/hami/values.yaml | 101 | # -- Loopback port the extender serves `/filter` and `/bind` on, for the kube-scheduler container in the same Pod. It | COMMENT |
| LOW | charts/hami/values.yaml | 121 | # named `schedulerName` that calls the extender yourself; the extender listens on loopback, so also change `--extend | COMMENT |
| LOW | charts/hami/values.yaml | 161 | # -- Names of existing image pull Secrets for the scheduler Pod, added after `global.imagePullSecrets`. | COMMENT |
| LOW | charts/hami/values.yaml | 201 | # -- Extra namespace selector expressions, added after the built-in one that skips namespaces labeled `hami.io/web | COMMENT |
| LOW | charts/hami/values.yaml | 221 | # writes a self-signed certificate to Secret `<fullname>-scheduler-tls`, and a post-install and post-upgrade hook Jo | COMMENT |
| LOW | charts/hami/values.yaml | 281 | enabled: false | COMMENT |
| LOW | charts/hami/values.yaml | 301 | pullPolicy: IfNotPresent | COMMENT |
| LOW | charts/hami/values.yaml | 321 | # -- Monitor image pull policy: `Always`, `IfNotPresent`, or `Never`. | COMMENT |
| LOW | charts/hami/values.yaml | 341 | # -- Additional monitor command-line arguments as a list of strings. | COMMENT |
| LOW | charts/hami/values.yaml | 361 | # memory: 100Mi | COMMENT |
| LOW | charts/hami/values.yaml | 381 | # -- Name of a Secret (key ca.crt) to mount as the CA bundle instead; used | COMMENT |
| LOW | charts/hami/values.yaml | 421 | "enablegetpreferredallocation": false | COMMENT |
| LOW | charts/hami/values.yaml | 441 | deviceListStrategy: "envvar" | COMMENT |
| LOW | charts/hami/values.yaml | 481 | COMMENT | |
| LOW | charts/hami/values.yaml | 541 | # @ignored | COMMENT |
| LOW | charts/hami/values.yaml | 561 | # `0` and `1` leave requests unscaled. | COMMENT |
| LOW | charts/hami/values.yaml | 581 | # -- Resource name for MLU compute, requested as an integer percentage from 0 to 100; omitted requests 100. | COMMENT |
| LOW | charts/hami/values.yaml | 681 | # -- In the `mig` operating mode, let the device plugin adopt, when it starts, MIG instances HAMi has no record of c | COMMENT |
| LOW | charts/hami/values.yaml | 721 | # -- Number of GPUs the admission webhook adds to a container that sets a `resourceMemoryName`, `resourceMemoryPerce | COMMENT |
| LOW | charts/hami/values.yaml | 741 | # On a shared GPU, vGPUmonitor pauses kernel launches of lower-priority tasks while higher-priority tasks are active | COMMENT |
| LOW | charts/hami/values.yaml | 761 | # Disabled by default because the `single-numa-node` Topology Manager policy then changes which Pods kubelet admits. | COMMENT |
| LOW | charts/hami/values.yaml | 781 | # so HAMi-core can apply them to processes started without the container's environment, such as from SSH, `su -`, `s | COMMENT |
| LOW | charts/hami/values.yaml | 801 | resourceCountName: "nvidia.com/remote-gpu" | COMMENT |
| LOW | charts/hami/values.yaml | 821 | # -- Names of existing image pull Secrets for the session relay Pods, added after | COMMENT |
| LOW | charts/hami/values.yaml | 841 | pullSecrets: [] | COMMENT |
| LOW | charts/hami/templates/scheduler/networkpolicy.yaml | 1 | {{- if .Values.scheduler.networkPolicy.enabled }} | COMMENT |
| LOW | hack/verify-staticcheck.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | hack/verify-license.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | hack/bench.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | hack/bench.sh | 21 | COMMENT | |
| LOW | hack/hami-mig-e2e.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | hack/bench-compare.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | hack/e2e-test-setup.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | hack/test-bench-compare.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | hack/verify-rbac.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | hack/hami-mig-e2e_test.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | hack/build.sh | 1 | #!/bin/bash | COMMENT |
| LOW | hack/deploy-helm.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | hack/e2e-runner-lock.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | hack/e2e-mig-test.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | hack/e2e-policy-test.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | hack/verify-import-aliases.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | hack/unit-test.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | hack/e2e-amd-mock.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | hack/e2e-mig-smoke-test.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | hack/verify-all.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | hack/util.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | hack/verify-chart-version.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | hack/e2e-test.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | hack/tools/rbaccheck/main.go | 21 | // Usage: go run ./hack/tools/rbaccheck/ [path ...] | COMMENT |
| LOW | examples/remotegpu/port_forward_session.yaml | 1 | # Reaching the fleet by hand, from a machine with no GPU and no NVIDIA driver. | COMMENT |
| LOW | examples/remotegpu/port_forward_session.yaml | 21 | # reports no devices to the scheduler: it serves its GPUs rather than hosting | COMMENT |
| LOW | examples/remotegpu/port_forward_session.yaml | 41 | # - name: relay | COMMENT |
| 43 more matches not shown… | ||||
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| HIGH | examples/hygon/specify_card_type_to_use.yaml | 7 | #In this example, we want this container to run on K100_AI | COMMENT |
| HIGH | examples/hygon/specify_card_type_not_use.yaml | 7 | #In this example, we don't want this container to run on K100_AI | COMMENT |
| HIGH | examples/nvidia/specify_card_type_to_use.yaml | 9 | # In this example, we want to run this job on A100 or V100 | COMMENT |
| HIGH | examples/nvidia/specify_uuid_to_use.yaml | 9 | # In this example, we want to run this job on GPU-03f69c50-207a-2038-9b45-23cac89cb67d or GPU-03f69c50-207a-2038-9b4 | COMMENT |
| HIGH | examples/nvidia/specify_card_type_not_use.yaml | 9 | # In this example, we don't want our job to run on 1080(include 1080Ti) or 2080(include 2080Ti) type of card. | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | skill/k8s-debug-gpu-pod/SKILL.md | 35 | ### Step 1: Global Pod Overview | COMMENT |
| LOW | skill/k8s-debug-gpu-pod/SKILL.md | 52 | ### Step 2: Event Triage | COMMENT |
| LOW | skill/k8s-debug-gpu-pod/SKILL.md | 75 | ### Step 3: Pending Pod Root Cause Analysis | COMMENT |
| LOW | skill/k8s-debug-gpu-pod/SKILL.md | 95 | ### Step 4: CrashLoopBackOff / Error Diagnosis | COMMENT |
| LOW | skill/k8s-debug-gpu-pod/SKILL.md | 130 | ### Step 5: ImagePullBackOff Diagnosis | COMMENT |
| LOW | skill/k8s-debug-gpu-pod/SKILL.md | 159 | ### Step 6: Resource Quota Check (Conditional) | COMMENT |
| LOW | skill/k8s-debug-gpu-pod/SKILL.md | 183 | ### Step 7: Report | COMMENT |
| LOW | skill/hami-vgpu-metrics-summary/SKILL.md | 55 | ### Step 1: Kubeconfig Discovery, Validation, and Selection | COMMENT |
| LOW | skill/hami-vgpu-metrics-summary/SKILL.md | 69 | ### Step 2: Acquire HAMi Metrics | COMMENT |
| LOW | skill/hami-vgpu-metrics-summary/SKILL.md | 132 | ### Step 3: Identify Relevant Metric Families | COMMENT |
| LOW | skill/hami-vgpu-metrics-summary/SKILL.md | 237 | ### Step 4: Normalize Units and Semantics | COMMENT |
| LOW | skill/hami-vgpu-metrics-summary/SKILL.md | 339 | ### Step 5: Build the Device-Level Summary | COMMENT |
| LOW | skill/hami-vgpu-metrics-summary/SKILL.md | 374 | ### Step 6: Build the Node-Level Summary | COMMENT |
| LOW | skill/hami-vgpu-metrics-summary/SKILL.md | 410 | ### Step 7: Build the Pod/Container-Level Summary | COMMENT |
| LOW | skill/hami-vgpu-metrics-summary/SKILL.md | 444 | ### Step 8: Build the Namespace Summary | COMMENT |
| LOW | skill/hami-vgpu-metrics-summary/SKILL.md | 492 | ### Step 9: Detect Common Usage Patterns | COMMENT |
| LOW | skill/hami-vgpu-metrics-summary/SKILL.md | 542 | ### Step 10: Consistency Checks | COMMENT |
| LOW | skill/hami-vgpu-metrics-summary/SKILL.md | 593 | ### Step 11: Collect Real GPU Usage via nvidia-smi Inside Each Pod | COMMENT |
| LOW | skill/hami-vgpu-metrics-summary/SKILL.md | 681 | ### Step 12: Produce the Final Report | COMMENT |
| LOW | pkg/scheduler/webhook_test.go | 1140 | // Step 1: Pod1 (init 20000, app 10000) should be allowed | COMMENT |
| LOW⚡ | pkg/scheduler/webhook_test.go | 1155 | // Step 2: Pod2 (same) must be DENIED | COMMENT |
| LOW⚡ | pkg/scheduler/webhook_test.go | 1161 | // Step 3: Pod1 init finished → usage drops to app only (10000) | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| HIGH | …device-plugin/nvidiadevice/nvinternal/rm/device_map.go | 335 | // Rename the resource for replicated devices as requested. | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | docker/vgpu-init.sh | 3 | # Check if the destination directory is provided as an argument | COMMENT |
| LOW | docker/vgpu-init.sh | 23 | # Check if the destination directory exists, create it if it doesn't | COMMENT |
| LOW | hack/util.sh | 21 | # Check if a command exists. | COMMENT |
| LOW | hack/util.sh | 106 | # Check if an IP is reachable. | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | pkg/scheduler/webhook_test.go | 1140 | // Step 1: Pod1 (init 20000, app 10000) should be allowed | COMMENT |
| LOW⚡ | pkg/scheduler/webhook_test.go | 1155 | // Step 2: Pod2 (same) must be DENIED | COMMENT |
| LOW⚡ | pkg/scheduler/webhook_test.go | 1161 | // Step 3: Pod1 init finished → usage drops to app only (10000) | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | docker/vgpu-init.sh | 48 | # Create the parent directory of the destination file if it doesn't exist | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | benchmarks/ai-benchmark/benchmark.py | 6 | CODE |