Repository Analysis

chaos-mesh/chaos-mesh

A Chaos Engineering Platform for Kubernetes.

3.6 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of chaos-mesh/chaos-mesh, a Go project with 7,797 GitHub stars. SynthScan v2.0 examined 257,144 lines of code across 1079 source files, recording 870 pattern matches distributed across 13 syntactic categories. The overall adjusted score of 3.6 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).

3.6
Adjusted Score
3.6
Raw Score
100%
Time Factor
2026-07-07
Last Push
7.8K
Stars
Go
Language
257.1K
Lines of Code
1.1K
Files
870
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 4MEDIUM 9LOW 857

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 870 distinct pattern matches across 13 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 Block824 hits · 824 pts
SeverityFileLineSnippetContext
LOW.lift.toml1# lift config reference: https://help.sonatype.com/lift/configuration-referenceCOMMENT
LOWui/app/src/vite-env.d.ts1/// <reference types="vite/client" />COMMENT
LOWui/app/src/lib/cytoscape.ts81// const first = serial[0]COMMENT
LOWcmd/generate-makefile/doc.go1// Copyright 2023 Chaos Mesh Authors.COMMENT
LOW…generate-makefile/generate_container_image_makefile.go1// Copyright 2023 Chaos Mesh Authors.COMMENT
LOWcmd/generate-makefile/funcmaps.go1// Copyright 2023 Chaos Mesh Authors.COMMENT
LOWcmd/generate-makefile/generate_local_binary_makefile.go1// Copyright 2023 Chaos Mesh Authors.COMMENT
LOWcmd/generate-makefile/main.go1// Copyright 2023 Chaos Mesh Authors.COMMENT
LOWcmd/generate-makefile/generate_binary_makefile.go1// Copyright 2023 Chaos Mesh Authors.COMMENT
LOWcmd/chaos-controller-manager/main.go1// Copyright 2021 Chaos Mesh Authors.COMMENT
LOWcmd/chaos-controller-manager/provider/controller.go1// Copyright 2021 Chaos Mesh Authors.COMMENT
LOW…aos-controller-manager/provider/updated_client_test.go1// Copyright 2021 Chaos Mesh Authors.COMMENT
LOWcmd/chaos-controller-manager/provider/doc.go1// Copyright 2021 Chaos Mesh Authors.COMMENT
LOWcmd/chaos-controller-manager/provider/updated_client.go1// Copyright 2021 Chaos Mesh Authors.COMMENT
LOWcmd/chaos-controller-manager/provider/suite_test.go1// Copyright 2021 Chaos Mesh Authors.COMMENT
LOWcmd/chaos-dashboard/main.go1// Copyright 2021 Chaos Mesh Authors.COMMENT
LOWcmd/chaos-daemon-helper/main.go1// Copyright 2022 Chaos Mesh Authors.COMMENT
LOWcmd/watchmaker/main_darwin.go1// Copyright 2021 Chaos Mesh Authors.COMMENT
LOWcmd/watchmaker/main_linux.go1// Copyright 2021 Chaos Mesh Authors.COMMENT
LOWcmd/chaos-daemon/main.go1// Copyright 2021 Chaos Mesh Authors.COMMENT
LOWcmd/chaos-builder/boilerplate.go1// Copyright Chaos Mesh Authors.COMMENT
LOWcmd/chaos-builder/boilerplate.go21// you may not use this file except in compliance with the License.COMMENT
LOWcmd/chaos-builder/config.go1// Copyright 2021 Chaos Mesh Authors.COMMENT
LOWcmd/chaos-builder/test.go1// Copyright 2021 Chaos Mesh Authors.COMMENT
LOWcmd/chaos-builder/frontend.go1// Copyright 2021 Chaos Mesh Authors.COMMENT
LOWcmd/chaos-builder/test_workflow.go1// Copyright 2021 Chaos Mesh Authors.COMMENT
LOWcmd/chaos-builder/workflow_test.go1// Copyright 2021 Chaos Mesh Authors.COMMENT
LOWcmd/chaos-builder/init.go1// Copyright 2021 Chaos Mesh Authors.COMMENT
LOWcmd/chaos-builder/main.go1// Copyright 2021 Chaos Mesh Authors.COMMENT
LOWcmd/chaos-builder/impl.go1// Copyright 2021 Chaos Mesh Authors.COMMENT
LOWcmd/chaos-builder/workflow.go1// Copyright 2021 Chaos Mesh Authors.COMMENT
LOWcmd/chaos-builder/schedule.go1// Copyright 2021 Chaos Mesh Authors.COMMENT
LOWtools/assets_generate/main.go1// Copyright 2021 Chaos Mesh Authors.COMMENT
LOWtest/cmd/timer/main.go1// Copyright 2021 Chaos Mesh Authors.COMMENT
LOWtest/integration_test/run.sh1#!/usr/bin/env bashCOMMENT
LOWtest/integration_test/physical_machine/chaos.yaml1# Copyright 2021 Chaos Mesh Authors.COMMENT
LOWtest/integration_test/physical_machine/workflow.yaml1# Copyright 2021 Chaos Mesh Authors.COMMENT
LOWtest/integration_test/physical_machine/run.sh1#!/usr/bin/env bashCOMMENT
LOW…/integration_test/physical_machine/chaos_selector.yaml1# Copyright 2021 Chaos Mesh Authors.COMMENT
LOWtest/integration_test/physical_machine/schedule.yaml1# Copyright 2021 Chaos Mesh Authors.COMMENT
LOW…ntegration_test/physical_machine/physical_machine.yaml1# Copyright 2021 Chaos Mesh Authors.COMMENT
LOW…egration_test/dashboard_authority/cluster-manager.yaml1# Copyright 2021 Chaos Mesh Authors.COMMENT
LOW…tegration_test/dashboard_authority/busybox-viewer.yaml1# Copyright 2021 Chaos Mesh Authors.COMMENT
LOW…egration_test/dashboard_authority/busybox-manager.yaml1# Copyright 2021 Chaos Mesh Authors.COMMENT
LOWtest/integration_test/dashboard_authority/run.sh1#!/usr/bin/env bashCOMMENT
LOWtest/integration_test/dashboard_authority/run.sh101echo "cluster manager and viewer can list all chaos experiments in the cluster"COMMENT
LOWtest/integration_test/dashboard_authority/run.sh221#echo "all token can get the report of archive experiments under namespace busybox"COMMENT
LOW…tegration_test/dashboard_authority/cluster-viewer.yaml1# Copyright 2021 Chaos Mesh Authors.COMMENT
LOWtest/integration_test/network/delay_chaos.yaml1# Copyright 2021 Chaos Mesh Authors.COMMENT
LOWtest/integration_test/network/run.sh1#!/usr/bin/env bashCOMMENT
LOWtest/integration_test/oidc/run.sh1#!/usr/bin/env bashCOMMENT
LOWtest/integration_test/oidc/patch-apiserver.sh1#!/usr/bin/env bashCOMMENT
LOWtest/integration_test/oidc/setup-keycloak.sh1#!/usr/bin/env bashCOMMENT
LOWtest/integration_test/oidc/manifests/keycloak.yaml1# Copyright 2025 Chaos Mesh Authors.COMMENT
LOWtest/integration_test/jvm/tidb.yaml1# Copyright 2022 Chaos Mesh Authors.COMMENT
LOWtest/integration_test/jvm/rule-data.yaml1# Copyright 2021 Chaos Mesh Authors.COMMENT
LOWtest/integration_test/jvm/run.sh1#!/usr/bin/env bashCOMMENT
LOWtest/integration_test/jvm/mysql_query.yaml1# Copyright 2022 Chaos Mesh Authors.COMMENT
LOWtest/integration_test/jvm/mysql_query_exception.yaml1# Copyright 2022 Chaos Mesh Authors.COMMENT
LOWtest/integration_test/jvm/exception.yaml1# Copyright 2021 Chaos Mesh Authors.COMMENT
764 more matches not shown…
Structural Annotation Overuse12 hits · 20 pts
SeverityFileLineSnippetContext
LOWCONTRIBUTING.md24### Step 1: Make changesCOMMENT
LOWCONTRIBUTING.md83### Step 2: Run unit testsCOMMENT
LOWCONTRIBUTING.md91### Step 3: Start Chaos Mesh locally and do manual testsCOMMENT
LOWCONTRIBUTING.md97### Step 4: Commit and push your changesCOMMENT
LOWCONTRIBUTING.md121### Step 5: Create a pull requestCOMMENT
LOWCONTRIBUTING.md125### Step 6: Get a code reviewCOMMENT
LOWexamples/client-go/main.go62 // Step 1: Set up informer factory and start it earlyCOMMENT
LOWexamples/client-go/main.go106 // Step 2: List existing PodChaos resources before creationCOMMENT
LOWexamples/client-go/main.go121 // Step 3: Create a PodChaos resource for pod-killCOMMENT
LOWexamples/client-go/main.go182 // Step 4: Use the lister to query resourcesCOMMENT
LOWexamples/client-go/main.go213 // Step 5: Demonstrate informer watching changesCOMMENT
LOWexamples/client-go/main.go248 // Step 6: Compare direct API calls vs cached listerCOMMENT
Cross-File Repetition4 hits · 20 pts
SeverityFileLineSnippetContext
HIGHconfig/crd/bases/chaos-mesh.org_workflows.yaml0type: string resourcefieldref: description: |- selects a resource of the container: only resources limits and requests (STRING
HIGHconfig/crd/bases/chaos-mesh.org_schedules.yaml0type: string resourcefieldref: description: |- selects a resource of the container: only resources limits and requests (STRING
HIGHhelm/chaos-mesh/crds/chaos-mesh.org_workflows.yaml0type: string resourcefieldref: description: |- selects a resource of the container: only resources limits and requests (STRING
HIGHhelm/chaos-mesh/crds/chaos-mesh.org_schedules.yaml0type: string resourcefieldref: description: |- selects a resource of the container: only resources limits and requests (STRING
Modern AI Meta-Vocabulary4 hits · 16 pts
SeverityFileLineSnippetContext
MEDIUMcmd/chaos-controller-manager/provider/controller.go52 // +kubebuilder:scaffold:schemeCOMMENT
MEDIUMconfig/crd/kustomization.yaml29# +kubebuilder:scaffold:crdkustomizeresourceCOMMENT
MEDIUMconfig/crd/kustomization.yaml37# +kubebuilder:scaffold:crdkustomizewebhookpatchCOMMENT
MEDIUMconfig/crd/kustomization.yaml44# +kubebuilder:scaffold:crdkustomizecainjectionpatchCOMMENT
Slop Phrases6 hits · 12 pts
SeverityFileLineSnippetContext
LOWcontrollers/statuscheck/worker.go131 // also checks the success threshold, so if you want to modify the logic here, don't forget to modify thatCOMMENT
LOWcontrollers/statuscheck/worker.go150 // also checks the failure threshold, so if you want to modify the logic here, don't forget to modify thatCOMMENT
LOWcontrollers/statuscheck/conditions.go108// so if you want to modify the logic here, don't forget to modify that function as well.COMMENT
LOWcontrollers/statuscheck/conditions.go119// so if you want to modify the logic here, don't forget to modify that function as well.COMMENT
MEDIUMhelm/chaos-mesh/values.yaml219 # If you are using Kind or using containerd as CRI, you can use theCOMMENT
MEDIUMhelm/chaos-mesh/values.yaml224 # If you are using CRI-O as CRI, you can use theCOMMENT
Verbosity Indicators6 hits · 9 pts
SeverityFileLineSnippetContext
LOWexamples/client-go/main.go62 // Step 1: Set up informer factory and start it earlyCOMMENT
LOWexamples/client-go/main.go106 // Step 2: List existing PodChaos resources before creationCOMMENT
LOWexamples/client-go/main.go121 // Step 3: Create a PodChaos resource for pod-killCOMMENT
LOWexamples/client-go/main.go182 // Step 4: Use the lister to query resourcesCOMMENT
LOWexamples/client-go/main.go213 // Step 5: Demonstrate informer watching changesCOMMENT
LOWexamples/client-go/main.go248 // Step 6: Compare direct API calls vs cached listerCOMMENT
AI Slop Vocabulary3 hits · 6 pts
SeverityFileLineSnippetContext
LOWtest/integration_test/dashboard_authority/run.sh90# here just use busybox manager because experiment can be created only one timeCOMMENT
LOWtest/integration_test/dashboard_authority/run.sh161# here just use cluster manager because experiment can be delete only one timeCOMMENT
MEDIUMhelm/chaos-mesh/Chart.yaml46 # Use this annotation to indicate the capabilities of the operator your chart provides. It must be one of the followinCOMMENT
Self-Referential Comments2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMconfig/crd/kustomizeconfig.yaml2# This file is for teaching kustomize how to substitute name and namespace reference in CRDCOMMENT
MEDIUMhelm/chaos-mesh/values.yaml66 # Create the serviceAccount for chaos-controller-managerCOMMENT
Hyper-Verbose Identifiers3 hits · 3 pts
SeverityFileLineSnippetContext
LOWui/app/src/lib/formikhelpers.ts31export function parsePodsOrPhysicalMachines(data: string[]) {CODE
LOWui/app/src/lib/formikhelpers.ts174 function parsePhysicalMachineChaos(spec: any) {CODE
LOWui/packages/openapi/factory.js114function typeReferenceToObjectLiteralExpression(CODE
Redundant / Tautological Comments2 hits · 3 pts
SeverityFileLineSnippetContext
LOWhelm/chaos-mesh/values.yaml410 ## Set this to true in order to add the corresponding annotations for cert-managerCOMMENT
LOWhelm/chaos-mesh/values.yaml427 ## Set this to true in order to enable TLS on the ingress recordCOMMENT
Fake / Example Data2 hits · 2 pts
SeverityFileLineSnippetContext
LOWui/app/src/i18n/zh.json308 "placeholder": "搜索",CODE
LOWui/app/src/i18n/en.json307 "placeholder": "Search",CODE
TODO Padding1 hit · 2 pts
SeverityFileLineSnippetContext
LOWcmd/chaos-builder/workflow_test.go54 // TODO: Add test cases.COMMENT
Example Usage Blocks1 hit · 2 pts
SeverityFileLineSnippetContext
LOWhack/env-image-tag.sh19# Usage:COMMENT