Repository Analysis

kata-containers/kata-containers

Kata Containers is an open source project and community working to build a standard implementation of lightweight Virtual Machines (VMs) that feel and perform like containers, but provide the workload isolation and security advantages of VMs. https://katacontainers.io/

2.3 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of kata-containers/kata-containers, a Rust project with 8,304 GitHub stars. SynthScan v2.0 examined 506,113 lines of code across 2052 source files, recording 812 pattern matches distributed across 16 syntactic categories. The overall adjusted score of 2.3 places this repository in the Likely human-written 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).

2.3
Adjusted Score
2.3
Raw Score
100%
Time Factor
2026-07-14
Last Push
8.3K
Stars
Rust
Language
506.1K
Lines of Code
2.1K
Files
812
Pattern Hits
2026-07-14
Scan Date
0.01
HC Hit Rate

What These Metrics Mean

Adjusted Score
Primary synthetic code indicator. Raw score normalised per 1,000 lines of code and multiplied by the temporal discount factor. This is the definitive comparative metric — use it to rank repositories by AI authorship density.
Raw Score
The unmodified sum of all severity-weighted, context-multiplied pattern match scores before temporal discounting. Reflects the absolute signal strength independent of when the repository was last active.
Time Factor
The temporal discount multiplier (0–100%) applied to the raw score. Repositories last updated before ChatGPT's launch (Nov 2022) receive a 5% factor. Full signal is only assigned to repositories active in the post-adoption era (Jan 2024+).
Pattern Hits
Total count of individual pattern matches across all files and categories. A high hit count with a low score may indicate a very large codebase with isolated AI snippets; a low count with a high score indicates dense, concentrated AI signatures.
HC Hit Rate
High+Critical pattern hits per file, averaged across the repository. This orthogonal signal catches repositories where a few files are densely packed with high-severity AI tells — a strong indicator even when the normalised score appears moderate due to codebase size.
Lines of Code / Files
Total lines and files analysed. The scanner examines 94 file extensions. These denominators are used to normalise the score, enabling fair comparison between repositories of vastly different sizes.

Score History

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.

Severity Breakdown

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.

CRITICAL 14HIGH 8MEDIUM 56LOW 734

Directory Score Breakdown

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.

Pattern Findings

The scanner identified 812 distinct pattern matches across 16 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.

Over-Commented Block651 hits · 642 pts
SeverityFileLineSnippetContext
LOWCargo.toml221# Per-package release profile overrides for kata-deploy. The kata-deployCOMMENT
LOW…kaging/kata-deploy/local-build/kata-deploy-binaries.sh501 fiCOMMENT
LOW…kaging/kata-deploy/local-build/kata-deploy-binaries.sh581#COMMENT
LOW…kaging/kata-deploy/local-build/kata-deploy-binaries.sh881# nvswitch -> enable DGX like systemsCOMMENT
LOW…ackaging/kata-deploy/helm-chart/kata-deploy/Chart.yaml1apiVersion: v2COMMENT
LOW…helm-chart/kata-deploy/try-kata-nvidia-gpu.values.yaml1# Example values file to enable NVIDIA GPU shimsCOMMENT
LOW…deploy/helm-chart/kata-deploy/try-kata-tee.values.yaml1# Example values file to enable Trusted Execution Environment (TEE) shimsCOMMENT
LOW…ckaging/kata-deploy/helm-chart/kata-deploy/values.yaml1# Deployment model for installing/cleaning up Kata on nodes.COMMENT
LOW…ckaging/kata-deploy/helm-chart/kata-deploy/values.yaml21# When you add nodes later, re-run `helm upgrade` so the dispatcher enumeratesCOMMENT
LOW…ckaging/kata-deploy/helm-chart/kata-deploy/values.yaml41 # How to choose which nodes get a per-node INSTALL Job. Precedence:COMMENT
LOW…ckaging/kata-deploy/helm-chart/kata-deploy/values.yaml61 # - { key: node-role.kubernetes.io/control-plane, operator: DoesNotExist }COMMENT
LOW…ckaging/kata-deploy/helm-chart/kata-deploy/values.yaml81 # cleanup.nodeSelectorExpressions, else all nodes).COMMENT
LOW…ckaging/kata-deploy/helm-chart/kata-deploy/values.yaml141# Use these when your containerd setup doesn't match any built-in distribution preset.COMMENT
LOW…ckaging/kata-deploy/helm-chart/kata-deploy/values.yaml161# Node selector and tolerations to control which nodes the kata-deploy daemonset runs onCOMMENT
LOW…ckaging/kata-deploy/helm-chart/kata-deploy/values.yaml181# after the runtime is ready, at which point the scheduler admits the workloads.COMMENT
LOW…ckaging/kata-deploy/helm-chart/kata-deploy/values.yaml201# Extra labels for the kata-deploy DaemonSet pods (in addition to theCOMMENT
LOW…ckaging/kata-deploy/helm-chart/kata-deploy/values.yaml221# themselves. NFD virtualization requirements cannot be bypassed. podAffinity,COMMENT
LOW…ckaging/kata-deploy/helm-chart/kata-deploy/values.yaml241# topologyKey: kubernetes.io/hostnameCOMMENT
LOW…ckaging/kata-deploy/helm-chart/kata-deploy/values.yaml261# Update strategy for the kata-deploy DaemonSetCOMMENT
LOW…ckaging/kata-deploy/helm-chart/kata-deploy/values.yaml281# Defaults sized from real measurements: VmRSS of the unpatched binary onCOMMENT
LOW…ckaging/kata-deploy/helm-chart/kata-deploy/values.yaml301# When empty, debug:true implies --log-level debug; otherwise kata-deploy fallsCOMMENT
LOW…ckaging/kata-deploy/helm-chart/kata-deploy/values.yaml341 timeoutSeconds: 3COMMENT
LOW…ckaging/kata-deploy/helm-chart/kata-deploy/values.yaml361 # Independent of erofsSnapshotterMode — works with both disk and memory.COMMENT
LOW…ckaging/kata-deploy/helm-chart/kata-deploy/values.yaml381# snapshotter: "" # e.g. nydus, erofs, devmapper, or "" for defaultCOMMENT
LOW…ckaging/kata-deploy/helm-chart/kata-deploy/values.yaml721 installationPrefix: ""COMMENT
LOW…ckaging/kata-deploy/helm-chart/kata-deploy/values.yaml741# control any external node-feature-discovery configuration).COMMENT
LOW…ckaging/kata-deploy/helm-chart/kata-deploy/values.yaml761 timeout: 180COMMENT
LOW…ckaging/kata-deploy/helm-chart/kata-deploy/values.yaml781 # helm install kata-deploy ... \COMMENT
LOW…ckaging/kata-deploy/helm-chart/kata-deploy/values.yaml801# my-gpu-runtime:COMMENT
LOW…ckaging/kata-deploy/helm-chart/kata-deploy/values.yaml821# katacontainers.io/kata-runtime: "true"COMMENT
LOW…ckaging/kata-deploy/helm-chart/kata-deploy/values.yaml841 # baseConfig: "qemu-nvidia-gpu" # Required: base config nameCOMMENT
LOWtools/packaging/kata-deploy/binary/src/config.rs201 pub custom_runtimes: Vec<CustomRuntime>,COMMENT
LOWtools/packaging/kata-deploy/binary/src/main.rs61 /// the node cannot support installation.COMMENT
LOWtools/packaging/kata-deploy/binary/src/main.rs81 #[clap(name = "cleanup-stage-unlabel")]COMMENT
LOWtools/packaging/kata-deploy/binary/src/main.rs101const KATA_RUNTIME_LABEL: &str = "katacontainers.io/kata-runtime";COMMENT
LOWtools/packaging/kata-deploy/binary/src/main.rs221 // kernel after free, so a long-running idle wait here wouldCOMMENT
LOWtools/packaging/kata-deploy/binary/src/main.rs881 /// Keep this in sync with the `#[clap(name = ...)]` attributes above.COMMENT
LOW…aging/kata-deploy/binary/src/artifacts/snapshotters.rs261 //COMMENT
LOW…/packaging/kata-deploy/binary/src/artifacts/install.rs761 Ok(())COMMENT
LOW…/packaging/kata-deploy/binary/src/artifacts/install.rs1361mod tests {COMMENT
LOW…/packaging/kata-deploy/binary/src/artifacts/install.rs1381 #[case("qemu-snp-runtime-rs", "qemu")]COMMENT
LOW…packaging/kata-deploy/binary/src/runtime/containerd.rs541 let drop_in_file = get_containerd_output_path(&paths);COMMENT
LOW…packaging/kata-deploy/binary/src/runtime/containerd.rs1001 "containerd://1.6.28",COMMENT
LOW…packaging/kata-deploy/binary/src/runtime/containerd.rs1061 #[rstest]COMMENT
LOW…ls/packaging/kata-deploy/binary/src/runtime/manager.rs221}COMMENT
LOW…ls/packaging/kata-deploy/binary/src/runtime/manager.rs281 #[case("containerd://2.2.0", true)]COMMENT
LOW…a-deploy/binary/src/utils/containerd_config_version.rs41#[cfg(test)]COMMENT
LOWtools/packaging/kata-deploy/binary/src/utils/toml.rs481 #[case("", "", "")]COMMENT
LOWtools/packaging/kata-deploy/job-dispatcher/src/main.rs1// Copyright (c) 2026 NVIDIA CorporationCOMMENT
LOWtools/packaging/kata-deploy/job-dispatcher/src/main.rs41)]COMMENT
LOWtools/packaging/kata-deploy/job-dispatcher/src/main.rs61COMMENT
LOWtools/packaging/scripts/download-with-oras-cache.sh1#!/bin/bashCOMMENT
LOWtools/packaging/scripts/populate-oras-tarball-cache.sh1#!/bin/bashCOMMENT
LOWtools/packaging/scripts/configure-hypervisor.sh1#!/usr/bin/env bashCOMMENT
LOWtools/packaging/scripts/configure-hypervisor.sh21COMMENT
LOWtools/packaging/scripts/configure-hypervisor.sh321 #COMMENT
LOWtools/packaging/static-build/shim-v2/build.sh41# shellcheck disable=SC2154COMMENT
LOWtools/osbuilder/rootfs-builder/alpine/rootfs_lib.sh1#!/usr/bin/env bashCOMMENT
LOWtools/osbuilder/rootfs-builder/debian/config.sh1#!/usr/bin/env bashCOMMENT
LOWtools/osbuilder/rootfs-builder/debian/config.sh21# shellcheck disable=SC2034COMMENT
591 more matches not shown…
Hallucination Indicators14 hits · 140 pts
SeverityFileLineSnippetContext
CRITICALtests/cleanup_resources.py6from azure.core.exceptions import ResourceNotFoundErrorCODE
CRITICALsrc/tools/genpolicy/src/policy.rs786 .set_container_path(self.config.settings.devices.vfio.device_path.clone());CODE
CRITICALsrc/tools/genpolicy/src/policy.rs801 self.config.settings.devices.vfio.anno_key_regex.clone(),CODE
CRITICALsrc/tools/genpolicy/src/policy.rs840 Version: self.config.settings.kata_config.oci_version.clone(),CODE
CRITICALsrc/tools/genpolicy/src/job.rs172 self.spec.template.spec.securityContext.as_ref()CODE
CRITICALsrc/tools/genpolicy/src/deployment.rs183 self.spec.template.spec.securityContext.as_ref()CODE
CRITICALsrc/tools/genpolicy/src/stateful_set.rs216 self.spec.template.spec.securityContext.as_ref()CODE
CRITICALsrc/tools/genpolicy/src/replication_controller.rs136 self.spec.template.spec.securityContext.as_ref()CODE
CRITICALsrc/tools/genpolicy/src/replica_set.rs133 self.spec.template.spec.securityContext.as_ref()CODE
CRITICALsrc/tools/genpolicy/src/daemon_set.rs172 self.spec.template.spec.securityContext.as_ref()CODE
CRITICAL…rates/resource/src/network/endpoint/ipvlan_endpoint.rs73 self.net_pair.tap.tap_iface.hard_addr.clone()CODE
CRITICAL…ates/resource/src/network/endpoint/macvlan_endpoint.rs72 self.net_pair.tap.tap_iface.hard_addr.clone()CODE
CRITICAL…/crates/resource/src/network/endpoint/veth_endpoint.rs72 self.net_pair.tap.tap_iface.hard_addr.clone()CODE
CRITICAL…/crates/resource/src/network/endpoint/vlan_endpoint.rs72 self.net_pair.tap.tap_iface.hard_addr.clone()CODE
Self-Referential Comments29 hits · 92 pts
SeverityFileLineSnippetContext
MEDIUM…kaging/kata-deploy/local-build/kata-deploy-binaries.sh1557 # Create a sym-link with the extension removedCOMMENT
MEDIUM…ckaging/kata-deploy/helm-chart/kata-deploy/values.yaml796# Create a custom-runtimes.values.yaml file:COMMENT
MEDIUMtools/osbuilder/scripts/lib.sh153# Create a YAML metadata file inside the rootfs.COMMENT
MEDIUMtools/osbuilder/rootfs-builder/rootfs.sh657# This file is part of systemd.COMMENT
MEDIUMtools/osbuilder/rootfs-builder/rootfs.sh847 # Create an empty /etc/resolv.conf, to allow agent to bind mount container resolv.conf to Kata VMCOMMENT
MEDIUMtools/testing/kata-webhook/create-certs.sh37# Create a Certificate Signing Request configuration file.COMMENT
MEDIUMci/openshift-ci/run_smoke_test.sh16# Create a pod.COMMENT
MEDIUMci/openshift-ci/smoke/service.yaml5# Create the service on port 80 for the http-server app.COMMENT
MEDIUMci/openshift-ci/smoke/service.yaml18# Create the route to the app's service '/'.COMMENT
MEDIUMci/openshift-ci/smoke/service_kubernetes.yaml5# Create the service on port 80 for the http-server app.COMMENT
MEDIUMtests/gha-run-k8s-common.sh155 # Create the cluster.COMMENT
MEDIUMtests/gha-run-k8s-common.sh655 # Create a new namespace for the tests and switch to itCOMMENT
MEDIUMtests/common.bash7# This file contains common functions thatCOMMENT
MEDIUMtests/common.bash48 # This function is called to indicate a fatal error occurred, soCOMMENT
MEDIUMtests/common.bash1402# This function provides consistent test execution and reporting acrossCOMMENT
MEDIUMtests/cmd/github-labels/github-labels.sh109 # Create the master database from the templateCOMMENT
MEDIUMtests/integration/nerdctl/gha-run.sh54 # Create the default containerd configurationCOMMENT
MEDIUMtests/integration/kubernetes/confidential_common.sh219# Create the sealed secret test secret:COMMENT
MEDIUMtests/integration/kubernetes/confidential_common.sh225# Create the NIM test instruct secret:COMMENT
MEDIUMtests/integration/kubernetes/confidential_common.sh231# Create the NIM test embedqa secret:COMMENT
MEDIUMtests/integration/kubernetes/lib.sh34# Create a pod with a given number of retries if an output includes a timeout.COMMENT
MEDIUMtests/integration/kubernetes/lib.sh73# Create a pod and wait it be ready, otherwise fail.COMMENT
MEDIUMtests/integration/kubernetes/lib.sh189# Create a pod then assert it fails to run. Use in tests that you expect theCOMMENT
MEDIUMtests/integration/kubernetes/lib.sh238# Create a pod then assert it remains in ContainerCreating.COMMENT
MEDIUMtests/integration/kubernetes/lib.sh314# Create a pod configuration out of a template file.COMMENT
MEDIUMtests/functional/vfio-ap/run.sh168 # Create a mediated device (mdev) for the released deviceCOMMENT
MEDIUMtests/functional/vfio-ap/run.sh223 # Create a container and run the testCOMMENT
MEDIUMutils/kata-manager.sh196 # Create an array to store architecture namesCOMMENT
MEDIUMutils/kata-manager.sh215 # Create a regular expression for matchingCOMMENT
Decorative Section Separators22 hits · 77 pts
SeverityFileLineSnippetContext
MEDIUM…/packaging/kata-deploy/binary/src/artifacts/install.rs766const KATA_DEPLOY_CONFIG_WARNING: &str = r#"# ==========================================================================CODE
MEDIUM…/packaging/kata-deploy/binary/src/artifacts/install.rs777# =============================================================================COMMENT
MEDIUMtools/packaging/scripts/configure-hypervisor.sh7#---------------------------------------------------------------------COMMENT
MEDIUMtools/packaging/scripts/configure-hypervisor.sh15#---------------------------------------------------------------------COMMENT
MEDIUMtools/packaging/scripts/configure-hypervisor.sh211 #---------------------------------------------------------------------COMMENT
MEDIUMtools/packaging/scripts/configure-hypervisor.sh423 #---------------------------------------------------------------------COMMENT
MEDIUMtools/packaging/scripts/configure-hypervisor.sh480 #---------------------------------------------------------------------COMMENT
MEDIUMci/gh-util.sh17#---------------------------------------------------------------------COMMENT
MEDIUMci/check_agent_policy_coverage.sh25# ---------------------------------------------------------------------------COMMENT
MEDIUMci/check_agent_policy_coverage.sh27# ---------------------------------------------------------------------------COMMENT
MEDIUMci/check_agent_policy_coverage.sh52# ---------------------------------------------------------------------------COMMENT
MEDIUMci/check_agent_policy_coverage.sh56# ---------------------------------------------------------------------------COMMENT
MEDIUMci/check_agent_policy_coverage.sh66# ---------------------------------------------------------------------------COMMENT
MEDIUMci/check_agent_policy_coverage.sh68# ---------------------------------------------------------------------------COMMENT
MEDIUMci/check_agent_policy_coverage.sh94# ---------------------------------------------------------------------------COMMENT
MEDIUMci/check_agent_policy_coverage.sh96# ---------------------------------------------------------------------------COMMENT
MEDIUMtests/kata-doc-to-script.sh125 #----------------------------------------------COMMENT
MEDIUMtests/kata-doc-to-script.sh129 #----------------------------------------------COMMENT
MEDIUMtests/kata-doc-to-script.sh131 #----------------------------------------------COMMENT
MEDIUMtests/kata-doc-to-script.sh133 #----------------------------------------------COMMENT
MEDIUMsrc/tools/log-parser/display.go20#----------------------------------------COMMENT
MEDIUMsrc/tools/log-parser/display.go26#----------------------------------------COMMENT
Synthetic Comment Markers7 hits · 52 pts
SeverityFileLineSnippetContext
HIGH…untime-rs/crates/hypervisor/src/ch/inner_hypervisor.rs854 // Early Check to verify if boot memory is the same as requestedCOMMENT
HIGHsrc/runtime/virtcontainers/clh.go1389 // Early Check to verify if boot memory is the same as requestedCOMMENT
HIGH…gent/rustjail/src/cgroups/systemd/interface/session.rs11//! This code was generated by `zbus-xmlgen` `2.0.1` from DBus introspection data.COMMENT
HIGH…agent/rustjail/src/cgroups/systemd/interface/system.rs11//! This code was generated by `zbus-xmlgen` `3.1.1` from DBus introspection data.COMMENT
HIGHsrc/dragonball/dbs_virtio_devices/src/mem.rs1266 // Make sure we have the correct resource as requested.COMMENT
HIGH…agonball/dbs_virtio_devices/src/vhost/vhost_user/fs.rs446 // Make sure we have the correct resource as requested, and currently we only support oneCOMMENT
HIGHsrc/dragonball/dbs_virtio_devices/src/fs/device.rs886 // Make sure we have the correct resource as requested, and currently we only support oneCOMMENT
Redundant / Tautological Comments26 hits · 39 pts
SeverityFileLineSnippetContext
LOW…helm-chart/kata-deploy/templates/verification-job.yaml302 # Check if pod is stuck - look for events indicating it can't startCOMMENT
LOWtools/packaging/scripts/gen_versions_txt.sh44 # Check if qemu.version can be used to get the version and hash, otherwise use qemu.tagCOMMENT
LOWtools/packaging/scripts/download-with-oras-cache.sh100# Check if artifact exists in GHCR and pull itCOMMENT
LOWtools/packaging/scripts/download-with-oras-cache.sh147 # Check if this version already exists in cache (avoid race conditions with parallel builds)COMMENT
LOWtools/packaging/scripts/configure-hypervisor.sh66# Display message to stderr and exit indicating script failed.COMMENT
LOWtools/packaging/static-build/kernel/install_yq.sh49 # Check if we need sudo to install yqCOMMENT
LOWtools/packaging/static-build/kernel/install_yq.sh51 # Check if we have sudo privilegesCOMMENT
LOWtools/packaging/guest-image/lib_se.sh33 # Check if FAKE_SE_IMAGE mode is enabledCOMMENT
LOWtools/packaging/guest-image/build_se_image.sh52 # Check if FAKE_SE_IMAGE mode is enabledCOMMENT
LOWtools/osbuilder/image-builder/image_builder.sh222 # Check if we have alternative init systems installedCOMMENT
LOWtools/osbuilder/rootfs-builder/debian/config.sh9# Set OS_NAME to the desired debian "codename"COMMENT
LOWci/install_yq.sh49 # Check if we need sudo to install yqCOMMENT
LOWci/install_yq.sh51 # Check if we have sudo privilegesCOMMENT
LOWci/openshift-ci/cluster/install_kata.sh229# Set SELinux to permissive modeCOMMENT
LOWtests/gha-run-k8s-common.sh973 # Check if this mapping has a colon (shim-specific)COMMENT
LOWtests/static-checks.sh941 # Check if the expected linter versionCOMMENT
LOWtests/govulncheck-runner.sh93 # Check if any real vulnerabilities remainCOMMENT
LOWtests/govulncheck-runner.sh102# Check if binary existsCOMMENT
LOWtests/common.bash144 # Check if first two arguments are numbers (for max_tries and interval)COMMENT
LOWtests/common.bash200# Check if the $1 argument is the name of a 'known'COMMENT
LOWtests/common.bash908 # Check if helm is available in the system's PATHCOMMENT
LOWtests/common.bash1379# Check if the 1st argument version is greater than and equal to 2nd oneCOMMENT
LOWtests/integration/kubernetes/lib.sh114 # Check if there is an existing node debugger pod and reuse itCOMMENT
LOWtests/integration/kubernetes/run_kubernetes_nv_tests.sh26 # Check if drop-in already existsCOMMENT
LOW…n/kubernetes/runtimeclass_workloads/numa/entrypoint.sh20# Print results to stdout (readable via "kubectl logs"), then sleep toCOMMENT
LOWtests/stability/common_stability.bash12# Set variables to reasonable defaults if unset or emptyCOMMENT
Structural Annotation Overuse23 hits · 39 pts
SeverityFileLineSnippetContext
LOWtools/packaging/kata-deploy/binary/src/main.rs676 // Step 1: Check if THIS pod's owning DaemonSet still exists.COMMENT
LOWtools/packaging/kata-deploy/binary/src/main.rs692 // Step 2: Our DaemonSet is gone (uninstall). Perform instance-specificCOMMENT
LOWtools/packaging/kata-deploy/binary/src/main.rs724 // Step 3: Check if ANY other kata-deploy DaemonSets still exist.COMMENT
LOWtests/integration/kubernetes/numa-pinning-check.sh7# WARNING: This script runs directly on the host, NOT inside a container.COMMENT
LOWdocs/how-to/how-to-use-erofs-snapshotter-with-kata.md37### Step 1: Install erofs-utilsCOMMENT
LOWdocs/how-to/how-to-use-erofs-snapshotter-with-kata.md60### Step 2: Configure containerdCOMMENT
LOWdocs/how-to/how-to-use-erofs-snapshotter-with-kata.md132### Step 3: Configure Kata Containers (runtime-rs)COMMENT
LOWdocs/how-to/how-to-use-numa-with-kata.md26## Step 1: Inspect the Host NUMA TopologyCOMMENT
LOWdocs/how-to/how-to-use-numa-with-kata.md66## Step 2: Kubernetes CPU Manager PolicyCOMMENT
LOWdocs/how-to/how-to-use-numa-with-kata.md103## Step 3: Configure Kata Containers for NUMACOMMENT
LOWdocs/how-to/how-to-use-numa-with-kata.md213## Step 4: Deploy a NUMA-Aware PodCOMMENT
LOWdocs/how-to/how-to-use-numa-with-kata.md277## Step 5: Verify NUMA Inside the GuestCOMMENT
LOWdocs/how-to/how-to-use-numa-with-kata.md352## Step 6: Verify NUMA on the HostCOMMENT
LOWdocs/how-to/how-to-use-numa-with-kata.md420## Step 7: Verify GPU NUMA Placement (GPU Passthrough Only)COMMENT
LOWsrc/tools/agent-ctl/src/image.rs43 // Step 1: Use skopeo to copy the image to a local OCI directory with explicit tagCOMMENT
LOWsrc/tools/agent-ctl/src/image.rs63 // Step 2: Use umoci to unpack the OCI image into a bundleCOMMENT
LOW…rs/crates/resource/src/cdi_devices/container_device.rs47 // Step 1: Extract all devices and filter out devices without device_info for vfio_devicesCOMMENT
LOW…rs/crates/resource/src/cdi_devices/container_device.rs57 // Step 2: Group devices by vendor_id-class_idCOMMENT
LOW…rs/crates/resource/src/cdi_devices/container_device.rs73 // Step 3: Sort devices within each group by guest_pcipathCOMMENT
LOWsrc/libs/kata-types/src/dmverity.rs247 // Step 0: Remove stale device if it already existsCOMMENT
LOWsrc/libs/kata-types/src/dmverity.rs253 // Step 1: Create device as read-onlyCOMMENT
LOWsrc/libs/kata-types/src/dmverity.rs302 // Step 2: Load table and resume (activate)COMMENT
LOWsrc/libs/kata-types/src/dmverity.rs306 // Step 3: Ensure the device node exists under /dev/mapper/.COMMENT
Verbosity Indicators13 hits · 24 pts
SeverityFileLineSnippetContext
LOW…kaging/kata-deploy/local-build/kata-deploy-binaries.sh1904 # The variants could be built independently we need to check ifCOMMENT
LOWtools/packaging/kata-deploy/binary/src/main.rs676 // Step 1: Check if THIS pod's owning DaemonSet still exists.COMMENT
LOWtools/packaging/kata-deploy/binary/src/main.rs692 // Step 2: Our DaemonSet is gone (uninstall). Perform instance-specificCOMMENT
LOWtools/packaging/kata-deploy/binary/src/main.rs724 // Step 3: Check if ANY other kata-deploy DaemonSets still exist.COMMENT
LOWsrc/tools/agent-ctl/src/image.rs43 // Step 1: Use skopeo to copy the image to a local OCI directory with explicit tagCOMMENT
LOWsrc/tools/agent-ctl/src/image.rs63 // Step 2: Use umoci to unpack the OCI image into a bundleCOMMENT
LOW…rs/crates/resource/src/cdi_devices/container_device.rs47 // Step 1: Extract all devices and filter out devices without device_info for vfio_devicesCOMMENT
LOW…rs/crates/resource/src/cdi_devices/container_device.rs57 // Step 2: Group devices by vendor_id-class_idCOMMENT
LOW…rs/crates/resource/src/cdi_devices/container_device.rs73 // Step 3: Sort devices within each group by guest_pcipathCOMMENT
LOWsrc/libs/kata-types/src/dmverity.rs247 // Step 0: Remove stale device if it already existsCOMMENT
LOWsrc/libs/kata-types/src/dmverity.rs253 // Step 1: Create device as read-onlyCOMMENT
LOWsrc/libs/kata-types/src/dmverity.rs302 // Step 2: Load table and resume (activate)COMMENT
LOWsrc/libs/kata-types/src/dmverity.rs306 // Step 3: Ensure the device node exists under /dev/mapper/.COMMENT
AI Slop Vocabulary7 hits · 15 pts
SeverityFileLineSnippetContext
LOWtools/packaging/scripts/gen_versions_txt.sh161 # (ie, 1.8.0-alpha0 may live on stable-1.8 as well as master: we'd just use master in this case)COMMENT
LOWtests/gha-run-k8s-common.sh267 # Due to this issue, let's simply use a different port (:9999) andCOMMENT
LOWtests/integration/kubernetes/lib.sh14# Delete all pods if any exist, otherwise just returnCOMMENT
LOWtests/stability/soak_parallel_rm.sh43# then just set this to a very large numberCOMMENT
MEDIUM…ime-rs/crates/resource/src/coco_data/initdata_block.rs235 // Essentially, it unwraps the layered writers (compression, buffering) to get back the original temporary file (temCOMMENT
MEDIUMsrc/runtime/virtcontainers/container_test.go340 // Create container to utilize this mount/secretCOMMENT
MEDIUMsrc/runtime/virtcontainers/kata_agent.go2104// given container and will update the OCI spec to utilize this mount point as the new source for theCOMMENT
Example Usage Blocks7 hits · 10 pts
SeverityFileLineSnippetContext
LOW…helm-chart/kata-deploy/try-kata-nvidia-gpu.values.yaml4# Usage:COMMENT
LOW…deploy/helm-chart/kata-deploy/try-kata-tee.values.yaml4# Usage:COMMENT
LOW…ckaging/kata-deploy/helm-chart/kata-deploy/values.yaml780 # Usage:COMMENT
LOWtools/packaging/scripts/populate-oras-tarball-cache.sh15# Usage:COMMENT
LOWtests/common.bash136# Usage:COMMENT
LOWtests/common.bash1412# Example usage:COMMENT
LOWtests/common.bash1463# Example usage:COMMENT
AI Response Leakage1 hit · 8 pts
SeverityFileLineSnippetContext
HIGH…gonball/dbs_virtio_devices/src/vsock/csm/connection.rs60// is undefined. In this implementation, we forcefully terminate theCOMMENT
Hyper-Verbose Identifiers6 hits · 6 pts
SeverityFileLineSnippetContext
LOWtools/testing/gatekeeper/jobs.py253 def get_jobs_for_workflow_run(self, run_id):CODE
LOWtools/testing/gatekeeper/jobs.py259 def check_workflow_runs_status(self, attempt):CODE
LOWtests/integration/cri-containerd/integration-tests.sh414function TestContainerMemoryUpdate() {CODE
LOWtests/integration/cri-containerd/integration-tests.sh446function PrepareContainerMemoryUpdate() {CODE
LOWtests/integration/cri-containerd/integration-tests.sh664function startDeviceCgroupContainers() {CODE
LOWtests/integration/cri-containerd/integration-tests.sh719function stopDeviceCgroupContainers() {CODE
Modern AI Meta-Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMdocs/use-cases/NVIDIA-GPU-passthrough-and-Kata-QEMU.md176#### UVM orchestration flowCOMMENT
Slop Phrases1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUM.github/workflows/codeql.yml58 # If you are analyzing a compiled language, you can modify the 'build-mode' for that language to customize howCOMMENT
Fake / Example Data3 hits · 3 pts
SeverityFileLineSnippetContext
LOWsrc/dragonball/src/device_manager/blk_dev_mgr.rs1012 let dummy_id = String::from("1");CODE
LOWsrc/dragonball/src/device_manager/blk_dev_mgr.rs1021 drive_id: dummy_id.clone(),CODE
LOWsrc/dragonball/src/device_manager/blk_dev_mgr.rs1067 .get_index_of_drive_id(&dummy_id)CODE
Deep Nesting1 hit · 1 pts
SeverityFileLineSnippetContext
LOWtools/testing/gatekeeper/skips.py76CODE