AI Slop Code Risk Monitor

chaos-mesh/chaos-mesh

SlopCodeMonitor badge for chaos-mesh/chaos-mesh Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

A Chaos Engineering Platform for Kubernetes.

3.5 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for chaos-mesh/chaos-mesh, a Go project with 7,962 GitHub stars. SynthScan examined 279,567 lines of code across 1143 source files, recording 938 pattern matches distributed across 14 syntactic categories. The legacy adjusted pattern signal is 3.5 (Low pattern signal); it is not an authorship estimate.

Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.

3.5
Adjusted Signal
3.5
Raw Pattern Score
100%
Time Factor
2026-10-29
Last Push
8.0K
Stars
Go
Language
279.6K
Lines of Code
1.1K
Files
938
Pattern Hits
2026-10-31
Scan Date
0.00
HC Hit Rate

Risk Review · Payload v1

Use each vector to guide manual verification of the underlying findings.

Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.

Cognitive Ownership Risk 15.8/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 931 finding(s).

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

Are imports declared and package/API names verified? 2 finding(s).

Agent Over-Engineering Ratio 0.4/100 · LOW

Are wrappers, guards, and repeated structures necessary? 8 finding(s).

PR Review Velocity Impact 16.0/100 · LOW

Which changes need focused human review? 938 finding(s).

What These Metrics Mean

Adjusted Signal
Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score
Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor
A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits
Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate
High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files
Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.

Severity Breakdown

Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.

CRITICAL 0HIGH 4MEDIUM 9LOW 925

Directory Score Breakdown

This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.

Pattern Findings

The scanner identified 938 distinct pattern matches across 14 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. 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 configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.

Over-Commented Block897 hits · 897 pts
SeverityFileLineSnippetContext
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/main_test.go1// Copyright 2026 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/readers_test.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/template_fields_test.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/aws/aws_chaos_template.yaml1# Copyright 2021 Chaos Mesh Authors.COMMENT
LOWtest/integration_test/aws/aws_secret.yaml1# Copyright 2021 Chaos Mesh Authors.COMMENT
LOWtest/integration_test/aws/aws_chaos.yaml1# Copyright 2021 Chaos Mesh Authors.COMMENT
LOWtest/integration_test/aws/run.sh1#!/usr/bin/env bashCOMMENT
837 more matches not shown…
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
MEDIUM⚡config/crd/kustomization.yaml29# +kubebuilder:scaffold:crdkustomizeresourceCOMMENT
MEDIUM⚡config/crd/kustomization.yaml37# +kubebuilder:scaffold:crdkustomizewebhookpatchCOMMENT
MEDIUM⚡config/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.go107// so if you want to modify the logic here, don't forget to modify that function as well.COMMENT
LOWcontrollers/statuscheck/conditions.go118// 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.go180 // Step 4: Use the lister to query resourcesCOMMENT
LOWexamples/client-go/main.go211 // Step 5: Demonstrate informer watching changesCOMMENT
LOWexamples/client-go/main.go246 // Step 6: Compare direct API calls vs cached listerCOMMENT
Structural Annotation Overuse6 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.go180 // Step 4: Use the lister to query resourcesCOMMENT
LOWexamples/client-go/main.go211 // Step 5: Demonstrate informer watching changesCOMMENT
LOWexamples/client-go/main.go246 // 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.yaml44 # 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.yaml416 ## Set this to true in order to add the corresponding annotations for cert-managerCOMMENT
LOWhelm/chaos-mesh/values.yaml433 ## 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
Excessive Try-Catch Wrapping1 hit · 1 pts
SeverityFileLineSnippetContext
LOW.github/scripts/cleanup_ghcr.py137 except Exception:CODE