Repository Analysis

eugr/spark-vllm-docker

Docker configuration for running VLLM on dual DGX Sparks

15.0 Moderate AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of eugr/spark-vllm-docker, a Shell project with 1,833 GitHub stars. SynthScan v2.0 examined 12,545 lines of code across 70 source files, recording 82 pattern matches distributed across 10 syntactic categories. The overall adjusted score of 15.0 places this repository in the Moderate 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).

15.0
Adjusted Score
15.0
Raw Score
100%
Time Factor
2026-07-14
Last Push
1.8K
Stars
Shell
Language
12.5K
Lines of Code
70
Files
82
Pattern Hits
2026-07-14
Scan Date
0.04
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 0HIGH 3MEDIUM 53LOW 26

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 82 distinct pattern matches across 10 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.

Decorative Section Separators30 hits · 93 pts
SeverityFileLineSnippetContext
MEDIUMbuild-and-copy.sh645# =====================================================COMMENT
MEDIUMbuild-and-copy.sh647# =====================================================COMMENT
MEDIUMbuild-and-copy.sh689 # ----------------------------------------------------------COMMENT
MEDIUMbuild-and-copy.sh691 # ----------------------------------------------------------COMMENT
MEDIUMbuild-and-copy.sh757 # ----------------------------------------------------------COMMENT
MEDIUMbuild-and-copy.sh759 # ----------------------------------------------------------COMMENT
MEDIUMbuild-and-copy.sh838 # ----------------------------------------------------------COMMENT
MEDIUMbuild-and-copy.sh840 # ----------------------------------------------------------COMMENT
MEDIUMbuild-and-copy.sh871# =====================================================COMMENT
MEDIUMbuild-and-copy.sh873# =====================================================COMMENT
MEDIUMtests/test_recipes.sh656# ==============================================================================COMMENT
MEDIUMtests/test_recipes.sh658# ==============================================================================COMMENT
MEDIUMtests/test_recipes.sh1019# ==============================================================================COMMENT
MEDIUMtests/test_recipes.sh1021# ==============================================================================COMMENT
MEDIUMtests/test_recipes.sh1243# ==============================================================================COMMENT
MEDIUMtests/test_recipes.sh1246# ==============================================================================COMMENT
MEDIUMtests/expected_commands.sh10# ==============================================================================COMMENT
MEDIUMtests/expected_commands.sh13# ==============================================================================COMMENT
MEDIUMtests/expected_commands.sh30# ==============================================================================COMMENT
MEDIUMtests/expected_commands.sh33# ==============================================================================COMMENT
MEDIUMtests/expected_commands.sh53# ==============================================================================COMMENT
MEDIUMtests/expected_commands.sh56# ==============================================================================COMMENT
MEDIUMtests/expected_commands.sh70# ==============================================================================COMMENT
MEDIUMtests/expected_commands.sh74# ==============================================================================COMMENT
MEDIUMmods/exp-b12x/run.sh28# ---------------------------------------------------------------COMMENT
MEDIUMmods/exp-b12x/run.sh33# ---------------------------------------------------------------COMMENT
MEDIUMmods/exp-b12x/run.sh49# ---------------------------------------------------------------COMMENT
MEDIUMmods/exp-b12x/run.sh52# ---------------------------------------------------------------COMMENT
MEDIUMmods/exp-b12x/run.sh89# ---------------------------------------------------------------COMMENT
MEDIUMmods/exp-b12x/run.sh96# ---------------------------------------------------------------COMMENT
Excessive Try-Catch Wrapping21 hits · 34 pts
SeverityFileLineSnippetContext
LOWbuild-and-copy.sh152except Exception:CODE
MEDIUMrun-recipe.py99 print("Error: PyYAML is required. Install with: pip install pyyaml")CODE
MEDIUMrun-recipe.py186 print(f"Error: Recipe not found: {recipe_path}")CODE
MEDIUMrun-recipe.py197 print(f"Error: Recipe missing required field: {field}")CODE
MEDIUMrun-recipe.py346 print(f"Error: Build script not found: {BUILD_SCRIPT}")CODE
MEDIUMrun-recipe.py386 print(f"Error: Download script not found: {DOWNLOAD_SCRIPT}")CODE
MEDIUMrun-recipe.py503 print(f"Error: Missing parameter in recipe command: {e}")CODE
MEDIUMrun-recipe.py611 print(f"Error: Autodiscover script not found: {AUTODISCOVER_SCRIPT}")CODE
LOWrun-recipe.py274 except Exception as e:CODE
MEDIUMrun-recipe.py634 print("Error: Autodiscover failed")STRING
MEDIUMrun-recipe.py1070 print(f"Error: Recipe '{recipe['name']}' requires cluster mode.")STRING
MEDIUMrun-recipe.py1081 print(f"Error: Recipe '{recipe['name']}' requires solo mode.")STRING
MEDIUMrun-recipe.py1097 print("Error: --earlyoom requires launch-cluster.sh to clear the image entrypoint.")STRING
MEDIUMrun-recipe.py1166 print("Error: Failed to build container")STRING
MEDIUMrun-recipe.py1181 print("Error: Failed to build/copy container")STRING
MEDIUMrun-recipe.py1206 print("Error: Failed to download model")STRING
MEDIUMrun-recipe.py1232 print("Error: Failed to build image")STRING
MEDIUMlaunch-cluster.sh228 print(f'Error: Invalid syntax at line {line_num}: missing \"=\"')CODE
MEDIUMlaunch-cluster.sh235 print(f'Error: Invalid key format at line {line_num}: {key}')CODE
MEDIUMlaunch-cluster.sh240 print(f'Error: Duplicate key at line {line_num}: {key}')CODE
LOWmods/fix-qwen3-coder-next/_triton_alloc_setup.py8except Exception:CODE
Redundant / Tautological Comments15 hits · 22 pts
SeverityFileLineSnippetContext
LOWrun-recipe.py1050 # Check if recipe requires cluster modeSTRING
LOWrun-recipe.py1221 # Check if image exists (if not using --setup)STRING
LOWlaunch-cluster.sh315 # Check if non-privileged flags were used without --non-privilegedCOMMENT
LOWlaunch-cluster.sh399 # Check if it's an absolute path or relative path that existsCOMMENT
LOWlaunch-cluster.sh402 # Check if it's just a filename, look in examples/ directoryCOMMENT
LOWlaunch-cluster.sh405 # Check if it's a name without .sh extensionCOMMENT
LOWlaunch-cluster.sh419 # Set command to run the copied script (use absolute path since docker exec may not be in /workspace)COMMENT
LOWlaunch-cluster.sh672# Check if cluster is already runningCOMMENT
LOWlaunch-cluster.sh1105 # Check if ray is responsiveCOMMENT
LOWautodiscover.sh165 # Set IB_IF to all four RoCE interfaces (hardcoded for mesh)COMMENT
LOWautodiscover.sh244 # Check if remote is a GB10 systemCOMMENT
LOWhf-download.sh130# Check if uvx is installedCOMMENT
LOWtests/test_recipes.sh1078 # Check if value is present (might be on next line due to formatting)COMMENT
LOWmods/fix-glm-4.7-flash-AWQ/run.sh7# Check if PR 34695 is already applied by looking for the changed fileCOMMENT
LOWmods/fix-glm-4.7-flash-AWQ/run.sh9 # Check if the specific line from PR 34695 is already presentCOMMENT
Self-Referential Comments5 hits · 16 pts
SeverityFileLineSnippetContext
MEDIUMtests/test_recipes.sh511 # Create a temporary recipe with unsupported versionCOMMENT
MEDIUMtests/test_recipes.sh535 # Create a temporary recipe without recipe_versionCOMMENT
MEDIUMtests/test_recipes.sh558 # Create a temporary cluster_only recipeCOMMENT
MEDIUMtests/test_recipes.sh584 # Create a temporary solo_only recipeCOMMENT
MEDIUMtests/expected_commands.sh2# This file is used by test_recipes.sh to verify recipes match README documentationCOMMENT
Docstring Block Structure3 hits · 15 pts
SeverityFileLineSnippetContext
HIGHrun-recipe.py134 Load and validate a recipe YAML file. This function handles recipe resolution from multiple locations and valiSTRING
HIGHrun-recipe.py320 Build the container image using build-and-copy.sh. Delegates to the build-and-copy.sh script which handles mulSTRING
HIGHrun-recipe.py438 Generate a bash launch script from the recipe. Creates a self-contained bash script that runs inside the contaSTRING
Over-Commented Block3 hits · 3 pts
SeverityFileLineSnippetContext
LOWtests/test_recipes.sh1#!/bin/bashCOMMENT
LOWtests/expected_commands.sh1# Expected vLLM serve arguments for each recipeCOMMENT
LOWrecipes/glm-4.7-flash-awq.yaml1# Recipe: GLM-4.7-Flash-AWQ-4bitCOMMENT
Example Usage Blocks1 hit · 2 pts
SeverityFileLineSnippetContext
LOWtests/test_recipes.sh8# Usage:COMMENT
Hyper-Verbose Identifiers1 hit · 1 pts
SeverityFileLineSnippetContext
LOWrun-recipe.py115def strip_distributed_executor_backend(command: str) -> str:CODE
Deep Nesting2 hits · 1 pts
SeverityFileLineSnippetContext
LOWrun-recipe.py567CODE
LOWrun-recipe.py646CODE
Unused Imports1 hit · 1 pts
SeverityFileLineSnippetContext
LOWmods/fix-qwen35-tp4-marlin/fix_rope.py2CODE