Repository Analysis

mysticaltech/terraform-hcloud-kube-hetzner

Optimized and Maintenance-free Kubernetes on Hetzner Cloud in one command!

5.1 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of mysticaltech/terraform-hcloud-kube-hetzner, a HCL project with 3,875 GitHub stars. SynthScan v2.0 examined 35,585 lines of code across 117 source files, recording 124 pattern matches distributed across 8 syntactic categories. The overall adjusted score of 5.1 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).

5.1
Adjusted Score
5.1
Raw Score
100%
Time Factor
2026-07-13
Last Push
3.9K
Stars
HCL
Language
35.6K
Lines of Code
117
Files
124
Pattern Hits
2026-07-14
Scan Date
0.00
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 0MEDIUM 8LOW 116

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 124 distinct pattern matches across 8 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.

Structural Annotation Overuse65 hits · 103 pts
SeverityFileLineSnippetContext
LOW.claude/skills/debug-node/SKILL.md49## Step 1: Identify the ServerCOMMENT
LOW.claude/skills/debug-node/SKILL.md55## Step 2: Enable Rescue Mode & RebootCOMMENT
LOW.claude/skills/debug-node/SKILL.md65## Step 3: SSH into RescueCOMMENT
LOW.claude/skills/debug-node/SKILL.md71## Step 4: Mount the FilesystemCOMMENT
LOW.claude/skills/debug-node/SKILL.md98## Step 5: Diagnostic ChecklistCOMMENT
LOW.claude/skills/debug-node/SKILL.md211## Step 6: Apply a FixCOMMENT
LOW.claude/skills/debug-node/SKILL.md232## Step 7: Reboot to NormalCOMMENT
LOW.claude/skills/test-changes/SKILL.md52## Step 1: Format CheckCOMMENT
LOW.claude/skills/test-changes/SKILL.md61## Step 2: Forbid null_resource UsageCOMMENT
LOW.claude/skills/test-changes/SKILL.md75## Step 3: Initialize Local ProvidersCOMMENT
LOW.claude/skills/test-changes/SKILL.md84## Step 4: Validate ModuleCOMMENT
LOW.claude/skills/test-changes/SKILL.md93## Step 5: Validate OpenTofu CompatibilityCOMMENT
LOW.claude/skills/test-changes/SKILL.md111## Step 6: Validate `kube.tf.example` ParseabilityCOMMENT
LOW.claude/skills/test-changes/SKILL.md169## Step 7: Initialize Test EnvironmentCOMMENT
LOW.claude/skills/test-changes/SKILL.md178## Step 8: Plan Against Test ClusterCOMMENT
LOW.claude/skills/test-changes/SKILL.md218## Step 9: Review Plan OutputCOMMENT
LOW.claude/skills/triage-issue/SKILL.md41## Step 1: Fetch Issue DetailsCOMMENT
LOW.claude/skills/triage-issue/SKILL.md51## Step 2: Classify Issue TypeCOMMENT
LOW.claude/skills/triage-issue/SKILL.md76## Step 3: Check for DuplicatesCOMMENT
LOW.claude/skills/triage-issue/SKILL.md89## Step 4: Security AnalysisCOMMENT
LOW.claude/skills/triage-issue/SKILL.md121## Step 5: Draft ResponseCOMMENT
LOW.claude/skills/triage-issue/SKILL.md216## Step 6: Recommend ActionCOMMENT
LOW.claude/skills/sync-docs/SKILL.md60## Step 1: Extract Variables from SourceCOMMENT
LOW.claude/skills/sync-docs/SKILL.md72## Step 2: Find Undocumented VariablesCOMMENT
LOW.claude/skills/sync-docs/SKILL.md80## Step 3: Generate DocumentationCOMMENT
LOW.claude/skills/sync-docs/SKILL.md107## Step 4: Update docs/llms.mdCOMMENT
LOW.claude/skills/sync-docs/SKILL.md131## Step 5: Update kube.tf.exampleCOMMENT
LOW.claude/skills/sync-docs/SKILL.md144## Step 6: Update README if NeededCOMMENT
LOW.claude/skills/sync-docs/SKILL.md223## Step 7: Verify ConsistencyCOMMENT
LOW.claude/skills/review-pr/SKILL.md57## Step 1: Fetch PR DetailsCOMMENT
LOW.claude/skills/review-pr/SKILL.md73## Step 2: Assess Author RiskCOMMENT
LOW.claude/skills/review-pr/SKILL.md93## Step 3: Analyze Changed FilesCOMMENT
LOW.claude/skills/review-pr/SKILL.md132## Step 4: Security ReviewCOMMENT
LOW.claude/skills/review-pr/SKILL.md167## Step 5: Backward CompatibilityCOMMENT
LOW.claude/skills/review-pr/SKILL.md211## Step 6: Code QualityCOMMENT
LOW.claude/skills/review-pr/SKILL.md225## Step 7: Release ClassificationCOMMENT
LOW.claude/skills/review-pr/SKILL.md245## Step 8: MANDATORY - Verify with Gemini and CodexCOMMENT
LOW.claude/skills/review-pr/SKILL.md343## Step 9: Final RecommendationCOMMENT
LOW.claude/skills/prepare-release/SKILL.md101## Step 1: Analyze ChangesCOMMENT
LOW.claude/skills/prepare-release/SKILL.md127## Step 2: Classify Release TypeCOMMENT
LOW.claude/skills/prepare-release/SKILL.md148## Step 3: Update CHANGELOG.mdCOMMENT
LOW.claude/skills/prepare-release/SKILL.md193## Step 4: Update Version BadgesCOMMENT
LOW.claude/skills/prepare-release/SKILL.md206## Step 5: Update Knowledge File (if applicable)COMMENT
LOW.claude/skills/prepare-release/SKILL.md220## Step 6: Verify Release Notes ContentCOMMENT
LOW.claude/skills/prepare-release/SKILL.md337## Step 7: Commit PreparationCOMMENT
LOW.claude/skills/fix-issue/SKILL.md45## Step 1: Fetch Issue DetailsCOMMENT
LOW.claude/skills/fix-issue/SKILL.md55## Step 2: Classify Issue TypeCOMMENT
LOW.claude/skills/fix-issue/SKILL.md82## Step 3: Verify Before FixingCOMMENT
LOW.claude/skills/fix-issue/SKILL.md100## Step 4: Deep InvestigationCOMMENT
LOW.claude/skills/fix-issue/SKILL.md139## Step 5: Enter Plan ModeCOMMENT
LOW.claude/skills/fix-issue/SKILL.md151## Step 6: Implement FixCOMMENT
LOW.claude/skills/fix-issue/SKILL.md168## Step 7: Test ChangesCOMMENT
LOW.claude/skills/fix-issue/SKILL.md206## Step 8: Commit & PushCOMMENT
LOW.claude/skills/running-stabilization-loop/SKILL.md106## Step 1: Sync Branch and Run GatesCOMMENT
LOW.claude/skills/running-stabilization-loop/SKILL.md124## Step 2: Kill Stale Runs and Clean StateCOMMENT
LOW.claude/skills/running-stabilization-loop/SKILL.md170## Step 3: Verify Snapshot PrerequisitesCOMMENT
LOW.claude/skills/running-stabilization-loop/SKILL.md197## Step 4: Run Matrix (Simple to Complex)COMMENT
LOW.claude/skills/running-stabilization-loop/SKILL.md213## Step 5: Proactive Debugging During RunsCOMMENT
LOW.claude/skills/running-stabilization-loop/SKILL.md267## Step 6: Fix + Targeted Rerun LoopCOMMENT
LOW.claude/skills/running-stabilization-loop/SKILL.md292## Step 7: Full Regression RerunCOMMENT
5 more matches not shown…
Self-Referential Comments6 hits · 22 pts
SeverityFileLineSnippetContext
MEDIUMlocals.tf3406# Create the kube_hetzner_selinux.te file, that allows in SELinux to not interfere with various needed servicesCOMMENT
MEDIUMlocals.tf3416# Create the distribution-specific registries file before Kubernetes starts.COMMENT
MEDIUMlocals.tf3423# Create the distribution-specific kubelet config file if needed.COMMENT
MEDIUMinit.tf794 # This method is a stub which could be replaced by a more practical helm implementationCOMMENT
MEDIUMscripts/create.sh42# Create the folder if folder_name is providedCOMMENT
MEDIUMmodules/host/main.tf452# Creating the swap filesystemCOMMENT
Over-Commented Block19 hits · 19 pts
SeverityFileLineSnippetContext
LOW.pre-commit-config.yaml21# - '--args=--only=terraform_documented_outputs'COMMENT
LOWdocs/llms.md321**Section 2.1: `control_plane_nodepools` - The Brains of the Operation**COMMENT
LOWdocs/llms.md361COMMENT
LOWdocs/llms.md601---COMMENT
LOWdocs/llms.md741---COMMENT
LOWdocs/llms.md761 # labels = { # Note: This is a map, not a list of strings like other labelsCOMMENT
LOWdocs/llms.md841 # The default is the official image from the Kubernetes project: registry.k8s.io/autoscaling/cluster-autoscalerCOMMENT
LOWdocs/llms.md901 #COMMENT
LOWdocs/llms.md1681 * Performing other OS-level customizations needed before k3s starts.COMMENT
LOWdocs/llms.md1701 # groups:COMMENT
LOWdocs/llms.md1881```terraformCOMMENT
LOWdocs/llms.md2241 # Useful when an external access/overlay network (ZeroTier, WireGuard,COMMENT
LOWdocs/llms.md2261 * **Tailscale Boundary:** Use `node_transport_mode = "tailscale"` when Tailscale should be the official Kubernetes nodCOMMENT
LOWdocs/llms.md2301 #COMMENT
LOWdocs/llms.md2421COMMENT
LOWdocs/llms.md2441 #COMMENT
LOWdocs/llms.md3181 # cert_manager_values = <<-EOTCOMMENT
LOWdocs/llms.md3201 # replicas: 2COMMENT
LOWdocs/llms.md3241 # nginx_values = <<-EOTCOMMENT
Hyper-Verbose Identifiers17 hits · 16 pts
SeverityFileLineSnippetContext
LOWscripts/sync_docs_site.py179def _extract_configuration_keys(example: str) -> list[str]:CODE
LOWscripts/render_harness.py136def extract_addon_default_versions() -> dict[str, str]:CODE
LOWscripts/render_harness.py172def assert_addon_default_versions() -> None:CODE
LOWscripts/render_harness.py619def node_annotation_write_files(scratch: TerraformScratch) -> list[dict[str, str]]:CODE
LOWscripts/render_harness.py656def render_cloudinit_with_vars(render_vars: dict[str, Any], template_path: Path) -> tuple[str, Any]:CODE
LOWscripts/render_harness.py665def assert_node_annotation_payload(name: str, document: Any, rendered: str) -> None:CODE
LOWscripts/render_harness.py730def run_node_annotation_cloudinit_checks(scratch: TerraformScratch) -> None:CODE
LOWscripts/render_harness.py785def run_autoscaler_manifest_checks(scratch: TerraformScratch) -> None:CODE
LOWscripts/render_harness.py980def run_kustomization_path_checks(scratch: TerraformScratch) -> None:STRING
LOWscripts/smoke_v3_plan_matrix.py158def discover_external_network_id(env: dict[str, str]) -> str | None:STRING
LOWscripts/contract_negative_tests.py149def provider_reachability_blocked(output: str) -> bool:CODE
LOWscripts/contract_negative_tests.py177def provider_rpc_sockets_available() -> bool:CODE
LOWscripts/v2_to_v3_migration_assistant.py248def collect_topology_warnings(root: Path) -> list[TopologyWarning]:CODE
LOWscripts/v2_to_v3_migration_assistant.py301def find_control_plane_network_id(root: Path) -> list[str]:CODE
LOWscripts/validate_tailscale_large_scale_examples.py73def extract_named_block_count(text: str, name: str) -> int:CODE
LOWscripts/validate_tailscale_large_scale_examples.py92def placement_groups_for_static_counts(*counts: int) -> int:CODE
LOWscripts/validate_tailscale_large_scale_examples.py96def validate_secure_tailscale_exposure(text: str, example_name: str) -> dict[str, bool]:CODE
Unused Imports8 hits · 8 pts
SeverityFileLineSnippetContext
LOWscripts/sync_docs_site.py4CODE
LOWscripts/smoke_v3_plan_matrix.py9CODE
LOWscripts/validate_v3_final_polish_examples.py4CODE
LOWscripts/contract_negative_tests.py4CODE
LOWscripts/contract_negative_tests.py13CODE
LOWscripts/v2_to_v3_migration_assistant.py8CODE
LOWscripts/validate_tailscale_large_scale_examples.py13CODE
LOWscripts/validate_tailscale_large_scale_examples.py22CODE
Deep Nesting5 hits · 5 pts
SeverityFileLineSnippetContext
LOWscripts/sync_docs_site.py41CODE
LOWscripts/sync_docs_site.py109CODE
LOWscripts/sync_docs_site.py146CODE
LOWscripts/v2_to_v3_migration_assistant.py211CODE
LOWscripts/v2_to_v3_migration_assistant.py301CODE
Modern AI Meta-Vocabulary2 hits · 4 pts
SeverityFileLineSnippetContext
MEDIUMdocs/terraform.md189| <a name="input_automatically_upgrade_os"></a> [automatically\_upgrade\_os](#input\_automatically\_upgrade\_os) | WhethCODE
MEDIUMdocs/terraform.md254| <a name="input_enable_kured"></a> [enable\_kured](#input\_enable\_kured) | Whether to include kured (the Kubernetes ReCODE
Redundant / Tautological Comments2 hits · 3 pts
SeverityFileLineSnippetContext
LOWlocals.tf196 # Check if the user has set custom DNS servers.COMMENT
LOWscripts/create.sh3# Check if terraform, packer and hcloud CLIs are presentCOMMENT