AI Slop Code Risk Monitor

Project-HAMi/HAMi

SlopCodeMonitor badge for Project-HAMi/HAMi Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).
1.3 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

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.

1.3
Adjusted Signal
1.3
Raw Pattern Score
100%
Time Factor
—
Last Push
—
Stars
—
Language
146.1K
Lines of Code
497
Files
140
Pattern Hits
2026-10-31
Scan Date
0.01
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 6.4/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 5.7/100 · LOW

Which changes need focused human review? 140 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 0HIGH 6MEDIUM 1LOW 133

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 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.

Over-Commented Block103 hits · 99 pts
SeverityFileLineSnippetContext
LOWcmd/vGPUmonitor/metrics.go741 return fmt.Errorf("failed to create metric: %w", err)COMMENT
LOWcmd/scheduler/router_test.go181// Malformed on purpose: every handler rejects it while decoding, before itCOMMENT
LOWdocker/entrypoint.sh1#!/bin/bashCOMMENT
LOWcharts/hami/Chart.yaml1apiVersion: v2COMMENT
LOWcharts/hami/values.yaml1# Chart-wide settings; the description of each one names the components it applies to.COMMENT
LOWcharts/hami/values.yaml61 enabled: falseCOMMENT
LOWcharts/hami/values.yaml81 # -- (float) Bonus added to the node score for nodes matching a Pod's preferred `nodeAffinity`, scaled by the matcheCOMMENT
LOWcharts/hami/values.yaml101 # -- Loopback port the extender serves `/filter` and `/bind` on, for the kube-scheduler container in the same Pod. It COMMENT
LOWcharts/hami/values.yaml121 # named `schedulerName` that calls the extender yourself; the extender listens on loopback, so also change `--extendCOMMENT
LOWcharts/hami/values.yaml161 # -- Names of existing image pull Secrets for the scheduler Pod, added after `global.imagePullSecrets`.COMMENT
LOWcharts/hami/values.yaml201 # -- Extra namespace selector expressions, added after the built-in one that skips namespaces labeled `hami.io/webCOMMENT
LOWcharts/hami/values.yaml221 # writes a self-signed certificate to Secret `<fullname>-scheduler-tls`, and a post-install and post-upgrade hook JoCOMMENT
LOWcharts/hami/values.yaml281 enabled: falseCOMMENT
LOWcharts/hami/values.yaml301 pullPolicy: IfNotPresentCOMMENT
LOWcharts/hami/values.yaml321 # -- Monitor image pull policy: `Always`, `IfNotPresent`, or `Never`.COMMENT
LOWcharts/hami/values.yaml341 # -- Additional monitor command-line arguments as a list of strings.COMMENT
LOWcharts/hami/values.yaml361# memory: 100MiCOMMENT
LOWcharts/hami/values.yaml381 # -- Name of a Secret (key ca.crt) to mount as the CA bundle instead; usedCOMMENT
LOWcharts/hami/values.yaml421 "enablegetpreferredallocation": falseCOMMENT
LOWcharts/hami/values.yaml441 deviceListStrategy: "envvar"COMMENT
LOWcharts/hami/values.yaml481COMMENT
LOWcharts/hami/values.yaml541 # @ignoredCOMMENT
LOWcharts/hami/values.yaml561 # `0` and `1` leave requests unscaled.COMMENT
LOWcharts/hami/values.yaml581 # -- Resource name for MLU compute, requested as an integer percentage from 0 to 100; omitted requests 100.COMMENT
LOWcharts/hami/values.yaml681 # -- In the `mig` operating mode, let the device plugin adopt, when it starts, MIG instances HAMi has no record of cCOMMENT
LOWcharts/hami/values.yaml721 # -- Number of GPUs the admission webhook adds to a container that sets a `resourceMemoryName`, `resourceMemoryPerceCOMMENT
LOWcharts/hami/values.yaml741 # On a shared GPU, vGPUmonitor pauses kernel launches of lower-priority tasks while higher-priority tasks are activeCOMMENT
LOWcharts/hami/values.yaml761 # Disabled by default because the `single-numa-node` Topology Manager policy then changes which Pods kubelet admits.COMMENT
LOWcharts/hami/values.yaml781 # so HAMi-core can apply them to processes started without the container's environment, such as from SSH, `su -`, `sCOMMENT
LOWcharts/hami/values.yaml801 resourceCountName: "nvidia.com/remote-gpu"COMMENT
LOWcharts/hami/values.yaml821 # -- Names of existing image pull Secrets for the session relay Pods, added afterCOMMENT
LOWcharts/hami/values.yaml841 pullSecrets: []COMMENT
LOWcharts/hami/templates/scheduler/networkpolicy.yaml1{{- if .Values.scheduler.networkPolicy.enabled }}COMMENT
LOWhack/verify-staticcheck.sh1#!/usr/bin/env bashCOMMENT
LOWhack/verify-license.sh1#!/usr/bin/env bashCOMMENT
LOWhack/bench.sh1#!/usr/bin/env bashCOMMENT
LOWhack/bench.sh21COMMENT
LOWhack/hami-mig-e2e.sh1#!/usr/bin/env bashCOMMENT
LOWhack/bench-compare.sh1#!/usr/bin/env bashCOMMENT
LOWhack/e2e-test-setup.sh1#!/usr/bin/env bashCOMMENT
LOWhack/test-bench-compare.sh1#!/usr/bin/env bashCOMMENT
LOWhack/verify-rbac.sh1#!/usr/bin/env bashCOMMENT
LOWhack/hami-mig-e2e_test.sh1#!/usr/bin/env bashCOMMENT
LOWhack/build.sh1#!/bin/bashCOMMENT
LOWhack/deploy-helm.sh1#!/usr/bin/env bashCOMMENT
LOWhack/e2e-runner-lock.sh1#!/usr/bin/env bashCOMMENT
LOWhack/e2e-mig-test.sh1#!/usr/bin/env bashCOMMENT
LOWhack/e2e-policy-test.sh1#!/usr/bin/env bashCOMMENT
LOWhack/verify-import-aliases.sh1#!/usr/bin/env bashCOMMENT
LOWhack/unit-test.sh1#!/usr/bin/env bashCOMMENT
LOWhack/e2e-amd-mock.sh1#!/usr/bin/env bashCOMMENT
LOWhack/e2e-mig-smoke-test.sh1#!/usr/bin/env bashCOMMENT
LOWhack/verify-all.sh1#!/usr/bin/env bashCOMMENT
LOWhack/util.sh1#!/usr/bin/env bashCOMMENT
LOWhack/verify-chart-version.sh1#!/usr/bin/env bashCOMMENT
LOWhack/e2e-test.sh1#!/usr/bin/env bashCOMMENT
LOWhack/tools/rbaccheck/main.go21// Usage: go run ./hack/tools/rbaccheck/ [path ...]COMMENT
LOWexamples/remotegpu/port_forward_session.yaml1# Reaching the fleet by hand, from a machine with no GPU and no NVIDIA driver.COMMENT
LOWexamples/remotegpu/port_forward_session.yaml21# reports no devices to the scheduler: it serves its GPUs rather than hostingCOMMENT
LOWexamples/remotegpu/port_forward_session.yaml41# - name: relayCOMMENT
43 more matches not shown…
AI Response Leakage5 hits · 38 pts
SeverityFileLineSnippetContext
HIGHexamples/hygon/specify_card_type_to_use.yaml7 #In this example, we want this container to run on K100_AICOMMENT
HIGHexamples/hygon/specify_card_type_not_use.yaml7 #In this example, we don't want this container to run on K100_AICOMMENT
HIGHexamples/nvidia/specify_card_type_to_use.yaml9 # In this example, we want to run this job on A100 or V100COMMENT
HIGHexamples/nvidia/specify_uuid_to_use.yaml9 # In this example, we want to run this job on GPU-03f69c50-207a-2038-9b45-23cac89cb67d or GPU-03f69c50-207a-2038-9b4COMMENT
HIGHexamples/nvidia/specify_card_type_not_use.yaml9 # In this example, we don't want our job to run on 1080(include 1080Ti) or 2080(include 2080Ti) type of card.COMMENT
Structural Annotation Overuse22 hits · 34 pts
SeverityFileLineSnippetContext
LOWskill/k8s-debug-gpu-pod/SKILL.md35### Step 1: Global Pod OverviewCOMMENT
LOWskill/k8s-debug-gpu-pod/SKILL.md52### Step 2: Event TriageCOMMENT
LOWskill/k8s-debug-gpu-pod/SKILL.md75### Step 3: Pending Pod Root Cause AnalysisCOMMENT
LOWskill/k8s-debug-gpu-pod/SKILL.md95### Step 4: CrashLoopBackOff / Error DiagnosisCOMMENT
LOWskill/k8s-debug-gpu-pod/SKILL.md130### Step 5: ImagePullBackOff DiagnosisCOMMENT
LOWskill/k8s-debug-gpu-pod/SKILL.md159### Step 6: Resource Quota Check (Conditional)COMMENT
LOWskill/k8s-debug-gpu-pod/SKILL.md183### Step 7: ReportCOMMENT
LOWskill/hami-vgpu-metrics-summary/SKILL.md55### Step 1: Kubeconfig Discovery, Validation, and SelectionCOMMENT
LOWskill/hami-vgpu-metrics-summary/SKILL.md69### Step 2: Acquire HAMi MetricsCOMMENT
LOWskill/hami-vgpu-metrics-summary/SKILL.md132### Step 3: Identify Relevant Metric FamiliesCOMMENT
LOWskill/hami-vgpu-metrics-summary/SKILL.md237### Step 4: Normalize Units and SemanticsCOMMENT
LOWskill/hami-vgpu-metrics-summary/SKILL.md339### Step 5: Build the Device-Level SummaryCOMMENT
LOWskill/hami-vgpu-metrics-summary/SKILL.md374### Step 6: Build the Node-Level SummaryCOMMENT
LOWskill/hami-vgpu-metrics-summary/SKILL.md410### Step 7: Build the Pod/Container-Level SummaryCOMMENT
LOWskill/hami-vgpu-metrics-summary/SKILL.md444### Step 8: Build the Namespace SummaryCOMMENT
LOWskill/hami-vgpu-metrics-summary/SKILL.md492### Step 9: Detect Common Usage PatternsCOMMENT
LOWskill/hami-vgpu-metrics-summary/SKILL.md542### Step 10: Consistency ChecksCOMMENT
LOWskill/hami-vgpu-metrics-summary/SKILL.md593### Step 11: Collect Real GPU Usage via nvidia-smi Inside Each PodCOMMENT
LOWskill/hami-vgpu-metrics-summary/SKILL.md681### Step 12: Produce the Final ReportCOMMENT
LOWpkg/scheduler/webhook_test.go1140 // Step 1: Pod1 (init 20000, app 10000) should be allowedCOMMENT
LOW⚡pkg/scheduler/webhook_test.go1155 // Step 2: Pod2 (same) must be DENIEDCOMMENT
LOW⚡pkg/scheduler/webhook_test.go1161 // Step 3: Pod1 init finished → usage drops to app only (10000)COMMENT
Synthetic Comment Markers1 hit · 8 pts
SeverityFileLineSnippetContext
HIGH…device-plugin/nvidiadevice/nvinternal/rm/device_map.go335 // Rename the resource for replicated devices as requested.COMMENT
Redundant / Tautological Comments4 hits · 6 pts
SeverityFileLineSnippetContext
LOWdocker/vgpu-init.sh3# Check if the destination directory is provided as an argumentCOMMENT
LOWdocker/vgpu-init.sh23# Check if the destination directory exists, create it if it doesn'tCOMMENT
LOWhack/util.sh21# Check if a command exists.COMMENT
LOWhack/util.sh106# Check if an IP is reachable.COMMENT
Verbosity Indicators3 hits · 6 pts
SeverityFileLineSnippetContext
LOWpkg/scheduler/webhook_test.go1140 // Step 1: Pod1 (init 20000, app 10000) should be allowedCOMMENT
LOW⚡pkg/scheduler/webhook_test.go1155 // Step 2: Pod2 (same) must be DENIEDCOMMENT
LOW⚡pkg/scheduler/webhook_test.go1161 // Step 3: Pod1 init finished → usage drops to app only (10000)COMMENT
Self-Referential Comments1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMdocker/vgpu-init.sh48 # Create the parent directory of the destination file if it doesn't existCOMMENT
Unused Imports1 hit · 1 pts
SeverityFileLineSnippetContext
LOWbenchmarks/ai-benchmark/benchmark.py6CODE