A Chaos Engineering Platform for Kubernetes.
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).
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.
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.
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.
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.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | .lift.toml | 1 | # lift config reference: https://help.sonatype.com/lift/configuration-reference | COMMENT |
| LOW | ui/app/src/vite-env.d.ts | 1 | /// <reference types="vite/client" /> | COMMENT |
| LOW | ui/app/src/lib/cytoscape.ts | 81 | // const first = serial[0] | COMMENT |
| LOW | cmd/generate-makefile/doc.go | 1 | // Copyright 2023 Chaos Mesh Authors. | COMMENT |
| LOW | …generate-makefile/generate_container_image_makefile.go | 1 | // Copyright 2023 Chaos Mesh Authors. | COMMENT |
| LOW | cmd/generate-makefile/funcmaps.go | 1 | // Copyright 2023 Chaos Mesh Authors. | COMMENT |
| LOW | cmd/generate-makefile/generate_local_binary_makefile.go | 1 | // Copyright 2023 Chaos Mesh Authors. | COMMENT |
| LOW | cmd/generate-makefile/main.go | 1 | // Copyright 2023 Chaos Mesh Authors. | COMMENT |
| LOW | cmd/generate-makefile/generate_binary_makefile.go | 1 | // Copyright 2023 Chaos Mesh Authors. | COMMENT |
| LOW | cmd/chaos-controller-manager/main.go | 1 | // Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | cmd/chaos-controller-manager/provider/controller.go | 1 | // Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | …aos-controller-manager/provider/updated_client_test.go | 1 | // Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | cmd/chaos-controller-manager/provider/doc.go | 1 | // Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | cmd/chaos-controller-manager/provider/updated_client.go | 1 | // Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | cmd/chaos-controller-manager/provider/suite_test.go | 1 | // Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | cmd/chaos-dashboard/main.go | 1 | // Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | cmd/chaos-daemon-helper/main.go | 1 | // Copyright 2022 Chaos Mesh Authors. | COMMENT |
| LOW | cmd/watchmaker/main_darwin.go | 1 | // Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | cmd/watchmaker/main_linux.go | 1 | // Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | cmd/chaos-daemon/main.go | 1 | // Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | cmd/chaos-builder/boilerplate.go | 1 | // Copyright Chaos Mesh Authors. | COMMENT |
| LOW | cmd/chaos-builder/boilerplate.go | 21 | // you may not use this file except in compliance with the License. | COMMENT |
| LOW | cmd/chaos-builder/config.go | 1 | // Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | cmd/chaos-builder/test.go | 1 | // Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | cmd/chaos-builder/frontend.go | 1 | // Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | cmd/chaos-builder/test_workflow.go | 1 | // Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | cmd/chaos-builder/workflow_test.go | 1 | // Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | cmd/chaos-builder/init.go | 1 | // Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | cmd/chaos-builder/main.go | 1 | // Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | cmd/chaos-builder/impl.go | 1 | // Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | cmd/chaos-builder/workflow.go | 1 | // Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | cmd/chaos-builder/schedule.go | 1 | // Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | tools/assets_generate/main.go | 1 | // Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | test/cmd/timer/main.go | 1 | // Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | test/integration_test/run.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | test/integration_test/physical_machine/chaos.yaml | 1 | # Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | test/integration_test/physical_machine/workflow.yaml | 1 | # Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | test/integration_test/physical_machine/run.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | …/integration_test/physical_machine/chaos_selector.yaml | 1 | # Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | test/integration_test/physical_machine/schedule.yaml | 1 | # Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | …ntegration_test/physical_machine/physical_machine.yaml | 1 | # Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | …egration_test/dashboard_authority/cluster-manager.yaml | 1 | # Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | …tegration_test/dashboard_authority/busybox-viewer.yaml | 1 | # Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | …egration_test/dashboard_authority/busybox-manager.yaml | 1 | # Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | test/integration_test/dashboard_authority/run.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | test/integration_test/dashboard_authority/run.sh | 101 | echo "cluster manager and viewer can list all chaos experiments in the cluster" | COMMENT |
| LOW | test/integration_test/dashboard_authority/run.sh | 221 | #echo "all token can get the report of archive experiments under namespace busybox" | COMMENT |
| LOW | …tegration_test/dashboard_authority/cluster-viewer.yaml | 1 | # Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | test/integration_test/network/delay_chaos.yaml | 1 | # Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | test/integration_test/network/run.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | test/integration_test/oidc/run.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | test/integration_test/oidc/patch-apiserver.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | test/integration_test/oidc/setup-keycloak.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | test/integration_test/oidc/manifests/keycloak.yaml | 1 | # Copyright 2025 Chaos Mesh Authors. | COMMENT |
| LOW | test/integration_test/jvm/tidb.yaml | 1 | # Copyright 2022 Chaos Mesh Authors. | COMMENT |
| LOW | test/integration_test/jvm/rule-data.yaml | 1 | # Copyright 2021 Chaos Mesh Authors. | COMMENT |
| LOW | test/integration_test/jvm/run.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | test/integration_test/jvm/mysql_query.yaml | 1 | # Copyright 2022 Chaos Mesh Authors. | COMMENT |
| LOW | test/integration_test/jvm/mysql_query_exception.yaml | 1 | # Copyright 2022 Chaos Mesh Authors. | COMMENT |
| LOW | test/integration_test/jvm/exception.yaml | 1 | # Copyright 2021 Chaos Mesh Authors. | COMMENT |
| 764 more matches not shown… | ||||
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | CONTRIBUTING.md | 24 | ### Step 1: Make changes | COMMENT |
| LOW⚡ | CONTRIBUTING.md | 83 | ### Step 2: Run unit tests | COMMENT |
| LOW⚡ | CONTRIBUTING.md | 91 | ### Step 3: Start Chaos Mesh locally and do manual tests | COMMENT |
| LOW⚡ | CONTRIBUTING.md | 97 | ### Step 4: Commit and push your changes | COMMENT |
| LOW | CONTRIBUTING.md | 121 | ### Step 5: Create a pull request | COMMENT |
| LOW | CONTRIBUTING.md | 125 | ### Step 6: Get a code review | COMMENT |
| LOW | examples/client-go/main.go | 62 | // Step 1: Set up informer factory and start it early | COMMENT |
| LOW | examples/client-go/main.go | 106 | // Step 2: List existing PodChaos resources before creation | COMMENT |
| LOW | examples/client-go/main.go | 121 | // Step 3: Create a PodChaos resource for pod-kill | COMMENT |
| LOW | examples/client-go/main.go | 182 | // Step 4: Use the lister to query resources | COMMENT |
| LOW | examples/client-go/main.go | 213 | // Step 5: Demonstrate informer watching changes | COMMENT |
| LOW | examples/client-go/main.go | 248 | // Step 6: Compare direct API calls vs cached lister | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| HIGH | config/crd/bases/chaos-mesh.org_workflows.yaml | 0 | type: string resourcefieldref: description: |- selects a resource of the container: only resources limits and requests ( | STRING |
| HIGH | config/crd/bases/chaos-mesh.org_schedules.yaml | 0 | type: string resourcefieldref: description: |- selects a resource of the container: only resources limits and requests ( | STRING |
| HIGH | helm/chaos-mesh/crds/chaos-mesh.org_workflows.yaml | 0 | type: string resourcefieldref: description: |- selects a resource of the container: only resources limits and requests ( | STRING |
| HIGH | helm/chaos-mesh/crds/chaos-mesh.org_schedules.yaml | 0 | type: string resourcefieldref: description: |- selects a resource of the container: only resources limits and requests ( | STRING |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | cmd/chaos-controller-manager/provider/controller.go | 52 | // +kubebuilder:scaffold:scheme | COMMENT |
| MEDIUM⚡ | config/crd/kustomization.yaml | 29 | # +kubebuilder:scaffold:crdkustomizeresource | COMMENT |
| MEDIUM⚡ | config/crd/kustomization.yaml | 37 | # +kubebuilder:scaffold:crdkustomizewebhookpatch | COMMENT |
| MEDIUM⚡ | config/crd/kustomization.yaml | 44 | # +kubebuilder:scaffold:crdkustomizecainjectionpatch | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | controllers/statuscheck/worker.go | 131 | // also checks the success threshold, so if you want to modify the logic here, don't forget to modify that | COMMENT |
| LOW | controllers/statuscheck/worker.go | 150 | // also checks the failure threshold, so if you want to modify the logic here, don't forget to modify that | COMMENT |
| LOW | controllers/statuscheck/conditions.go | 108 | // so if you want to modify the logic here, don't forget to modify that function as well. | COMMENT |
| LOW | controllers/statuscheck/conditions.go | 119 | // so if you want to modify the logic here, don't forget to modify that function as well. | COMMENT |
| MEDIUM | helm/chaos-mesh/values.yaml | 219 | # If you are using Kind or using containerd as CRI, you can use the | COMMENT |
| MEDIUM | helm/chaos-mesh/values.yaml | 224 | # If you are using CRI-O as CRI, you can use the | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | examples/client-go/main.go | 62 | // Step 1: Set up informer factory and start it early | COMMENT |
| LOW | examples/client-go/main.go | 106 | // Step 2: List existing PodChaos resources before creation | COMMENT |
| LOW | examples/client-go/main.go | 121 | // Step 3: Create a PodChaos resource for pod-kill | COMMENT |
| LOW | examples/client-go/main.go | 182 | // Step 4: Use the lister to query resources | COMMENT |
| LOW | examples/client-go/main.go | 213 | // Step 5: Demonstrate informer watching changes | COMMENT |
| LOW | examples/client-go/main.go | 248 | // Step 6: Compare direct API calls vs cached lister | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | test/integration_test/dashboard_authority/run.sh | 90 | # here just use busybox manager because experiment can be created only one time | COMMENT |
| LOW | test/integration_test/dashboard_authority/run.sh | 161 | # here just use cluster manager because experiment can be delete only one time | COMMENT |
| MEDIUM | helm/chaos-mesh/Chart.yaml | 46 | # Use this annotation to indicate the capabilities of the operator your chart provides. It must be one of the followin | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | config/crd/kustomizeconfig.yaml | 2 | # This file is for teaching kustomize how to substitute name and namespace reference in CRD | COMMENT |
| MEDIUM | helm/chaos-mesh/values.yaml | 66 | # Create the serviceAccount for chaos-controller-manager | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | ui/app/src/lib/formikhelpers.ts | 31 | export function parsePodsOrPhysicalMachines(data: string[]) { | CODE |
| LOW | ui/app/src/lib/formikhelpers.ts | 174 | function parsePhysicalMachineChaos(spec: any) { | CODE |
| LOW | ui/packages/openapi/factory.js | 114 | function typeReferenceToObjectLiteralExpression( | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | helm/chaos-mesh/values.yaml | 410 | ## Set this to true in order to add the corresponding annotations for cert-manager | COMMENT |
| LOW | helm/chaos-mesh/values.yaml | 427 | ## Set this to true in order to enable TLS on the ingress record | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | ui/app/src/i18n/zh.json | 308 | "placeholder": "搜索", | CODE |
| LOW | ui/app/src/i18n/en.json | 307 | "placeholder": "Search", | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | cmd/chaos-builder/workflow_test.go | 54 | // TODO: Add test cases. | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | hack/env-image-tag.sh | 19 | # Usage: | COMMENT |