AI Slop Code Risk Monitor

crossplane/crossplane

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

The Cloud Native Control Plane

1.8 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for crossplane/crossplane, a Go project with 12,210 GitHub stars. SynthScan examined 181,152 lines of code across 917 source files, recording 256 pattern matches distributed across 9 syntactic categories. The legacy adjusted pattern signal is 1.8 (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.

1.8
Adjusted Signal
1.8
Raw Pattern Score
100%
Time Factor
2026-10-31
Last Push
12.2K
Stars
Go
Language
181.2K
Lines of Code
917
Files
256
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 7.4/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

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

Agent Over-Engineering Ratio 1.1/100 · LOW

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

PR Review Velocity Impact 7.7/100 · LOW

Which changes need focused human review? 256 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 0MEDIUM 18LOW 238

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 256 distinct pattern matches across 9 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 Block216 hits · 216 pts
SeverityFileLineSnippetContext
LOWgenerate.go21// $PATH. Use './nix.sh develop' or './nix.sh run .#generate' to ensure theyCOMMENT
LOW.golangci.yml21 # this line must have a comment explaining the rationale.COMMENT
LOW.golangci.yml61 # it would have many more false positives than useful catches, though.COMMENT
LOW.golangci.yml81COMMENT
LOWnix.sh1#!/usr/bin/env bashCOMMENT
LOW.coderabbit.yaml261# =============================================================================COMMENT
LOWcmd/crossplane/render/render.go41// pipeline step returns a SEVERITY_FATAL result. It is distinct from theCOMMENT
LOWdesign/design-doc-developer-experience-tooling.md601 // is used as part of the build process to construct dependencies on theCOMMENT
LOWdesign/design-doc-developer-experience-tooling.md641 // specified, it defaults to `examples/`.COMMENT
LOWdesign/design-doc-developer-experience-tooling.md801//COMMENT
LOWdesign/design-doc-developer-experience-tooling.md821COMMENT
LOWdesign/design-doc-developer-experience-tooling.md841 RemoveFields []string `json:"removeFields,omitempty"`COMMENT
LOWdesign/design-doc-developer-experience-tooling.md861 //COMMENT
LOWdesign/design-doc-developer-experience-tooling.md881 // Optional.COMMENT
LOWdesign/design-doc-developer-experience-tooling.md961COMMENT
LOWdesign/design-doc-developer-experience-tooling.md981 // Timeout for the test in secondsCOMMENT
LOWdesign/design-doc-developer-experience-tooling.md1001 Functions Resources `json:"functions"`COMMENT
LOWdesign/design-doc-developer-experience-tooling.md1081// E2ETestCase defines the specification of a single test caseCOMMENT
LOWdesign/design-doc-developer-experience-tooling.md1101// +k8s:deepcopy-gen=trueCOMMENT
LOWdesign/design-doc-developer-experience-tooling.md1121 // defaults to 600 seconds (10 minutes). Consider increasing this value forCOMMENT
LOWdesign/design-doc-developer-experience-tooling.md1141 // Manifests contains the Kubernetes resources that will be applied as partCOMMENT
LOWdesign/design-doc-developer-experience-tooling.md1161 // prerequisite resources that the configuration depends on. Common useCOMMENT
LOWdesign/design-doc-packages-v2.md261}COMMENT
LOWdesign/design-doc-packages-v2.md281 CustomResourceDefinition string `json:"crd,omitempty"`COMMENT
LOWdesign/design-doc-packages-v2.md381 Package string `json:"package"`COMMENT
LOWdesign/design-doc-packages-v2.md501 // package when the desired CRD is known, but the package name that containsCOMMENT
LOWdesign/design-doc-packages-v2.md661 // Package is the name of the package package that is being requested, e.g.,COMMENT
LOWdesign/one-pager-package-format-v2.md121 dependsOn:COMMENT
LOWdesign/one-pager-composition-environment.md101 # These selectors are only executed if spec.environmentConfigRefs is null,COMMENT
LOW…gn/design-doc-composition-functions-extra-resources.md661COMMENT
LOW…gn/design-doc-composition-functions-extra-resources.md881 // execute.COMMENT
LOWdesign/design-doc-terrajet.md241 // Region is the region you'd like your VPC to be created in.COMMENT
LOWdesign/design-doc-composition.md541 #COMMENT
LOWdesign/design-doc-composition.md581 # Multiple compositions may potentially satisfy a particular kind ofCOMMENT
LOWdesign/design-doc-composition.md681# the composite resources they require.COMMENT
LOWdesign/design-doc-composition.md701 # phase; if the requirement and the required resource reference each otherCOMMENT
LOWdesign/design-doc-composition.md841 storageType:COMMENT
LOWdesign/design-doc-composition.md901 # The Wordpress author may explicitly select which composition should be usedCOMMENT
LOWdesign/design-doc-composition-functions.md341// State of the composite resource (XR) and any composed resources.COMMENT
LOWdesign/design-doc-composition-functions.md361 // desired connection details of the composite resource.COMMENT
LOWdesign/one-pager-managed-resource-api-design.md521 ...COMMENT
LOWdesign/one-pager-managed-resource-api-design.md641#### ExampleCOMMENT
LOWdesign/defunct/design-doc-complex-workloads.md161 app: wordpress-demoCOMMENT
LOWdesign/defunct/design-doc-template-stacks-experience.md341 type: kustomizeCOMMENT
LOW…ssets/design-doc-provider-strategy/cloudcontrol/aws.sh1#!/bin/bashCOMMENT
LOW…ssets/design-doc-provider-strategy/cloudcontrol/aws.sh21echo "Completed create-resource for ECR::Repository"COMMENT
LOWapis/generate.go21// are.COMMENT
LOWapis/generate.go41COMMENT
LOWapis/generate.go61// Generate conversion codeCOMMENT
LOWapis/core/v2/resource_cluster.go21type ClusterManagedResourceSpec struct {COMMENT
LOWapis/core/v2/resource_cluster.go41 // values would be honored if the feature flag is enabled. If both areCOMMENT
LOWapis/core/v2/observation.go21 // ObservedGeneration is the latest metadata.generationCOMMENT
LOWapis/core/v2/resource_namespace.go21type ManagedResourceSpec struct {COMMENT
LOWapis/core/v2/resource.go41 // CredentialsSecretKubeconfigKey is the key inside a connection secret for the raw kubeconfig yaml.COMMENT
LOWapis/core/v2/resource.go101COMMENT
LOWapis/core/v2/resource.go241// A CredentialsSource is a source from which provider credentials may beCOMMENT
LOWapis/core/v2/resource.go261 // credentials from an environment variable.COMMENT
LOWapis/core/v2/condition.go41 // both synced and healthy. A composite resource is healthy when the compositeCOMMENT
LOWapis/protection/v1beta1/usage_types.go41}COMMENT
LOWapis/protection/v1beta1/usage_types.go81 // MatchLabels ensures an object with matching labels is selected.COMMENT
156 more matches not shown…
Decorative Section Separators10 hits · 39 pts
SeverityFileLineSnippetContext
MEDIUM.coderabbit.yaml4# =============================================================================COMMENT
MEDIUM.coderabbit.yaml6# =============================================================================COMMENT
MEDIUM.coderabbit.yaml20# =============================================================================COMMENT
MEDIUM.coderabbit.yaml22# =============================================================================COMMENT
MEDIUM⚡.coderabbit.yaml261# =============================================================================COMMENT
MEDIUM⚡.coderabbit.yaml264# =============================================================================COMMENT
MEDIUM⚡.coderabbit.yaml270# =============================================================================COMMENT
MEDIUM⚡.coderabbit.yaml277# =============================================================================COMMENT
MEDIUM⚡.coderabbit.yaml283# =============================================================================COMMENT
MEDIUM⚡.coderabbit.yaml285# =============================================================================COMMENT
AI Slop Vocabulary9 hits · 18 pts
SeverityFileLineSnippetContext
MEDIUM.coderabbit.yaml221 # Our comprehensive golangci-lint setup with "default: all" already coversCOMMENT
MEDIUM.coderabbit.yaml224 # Go linting - disabled (we run golangci-lint with comprehensive config)COMMENT
MEDIUMtest/e2e/apiextensions_xrds_test.go95 // This test would be more robust if it could verify that the WatchingCompositeCOMMENT
LOW…ests/pkg/configuration/digest/provider-dependency.yaml1# Note that we don't directly create this manifest, we just use it to checkCOMMENT
LOW…configuration/digest/provider-revision-dependency.yaml1# Note that we don't directly create this manifest, we just use it to checkCOMMENT
LOW…/pkg/configuration/dependency/provider-dependency.yaml1# Note that we don't directly create this manifest, we just use it to checkCOMMENT
LOW…iguration/dependency/provider-revision-dependency.yaml1# Note that we don't directly create this manifest, we just use it to checkCOMMENT
LOW…r/provider-revision-common-annotations-and-labels.yaml1# Note that we don't directly create this manifest, we just use it to checkCOMMENT
LOW…g/image-config/runtime-config/provider-dependency.yaml1# Note that we don't directly create this manifest, we just use it to checkCOMMENT
Self-Referential Comments4 hits · 12 pts
SeverityFileLineSnippetContext
MEDIUMtest/e2e/functions/revision-id/crossplane.yaml3# This function is manually built and pushed toCOMMENT
MEDIUM…anifests/pkg/image-config/runtime-config/function.yaml6 # This function is directly installed (not as a dependency) and should haveCOMMENT
MEDIUM…/image-config/runtime-config/function-new-runtime.yaml6 # This function is directly installed (not as a dependency) and should haveCOMMENT
MEDIUM…nifests/pkg/composition-function-upgrade/function.yaml1# This file is NOT applied by the test. It describes the Function that the v1COMMENT
Redundant / Tautological Comments5 hits · 10 pts
SeverityFileLineSnippetContext
LOW⚡…ns/composition/required-schemas/setup/composition.yaml25 # Check if we received the schema in this iteration.COMMENT
LOW⚡…ns/composition/required-schemas/setup/composition.yaml28 # Check if the schema has the expected structure.COMMENT
LOW⚡…ns/composition/required-schemas/setup/composition.yaml38 # Check if referenced schemas (like ObjectMeta) are flattened.COMMENT
LOW…/composition/required-resources/setup/composition.yaml32 # Check if we received the resource in this iteration.COMMENT
LOW…/composition/required-resources/setup/composition.yaml35 # Check if the resource has the expected data, and echo its currentCOMMENT
Verbosity Indicators4 hits · 9 pts
SeverityFileLineSnippetContext
LOW⚡internal/ssa/managed_fields.go89// Step 1: All fields are owned by various managers, potentially includingCOMMENT
LOW⚡internal/ssa/managed_fields.go93// Step 2: Upgrade is called for the first time. We clear all field managers.COMMENT
LOW⚡internal/ssa/managed_fields.go95// Step 3: The controller server-side applies its fully specified intentCOMMENT
LOW⚡internal/ssa/managed_fields.go101// Step 4: Upgrade is called for the second time. It deletes theCOMMENT
Structural Annotation Overuse4 hits · 9 pts
SeverityFileLineSnippetContext
LOW⚡internal/ssa/managed_fields.go89// Step 1: All fields are owned by various managers, potentially includingCOMMENT
LOW⚡internal/ssa/managed_fields.go93// Step 2: Upgrade is called for the first time. We clear all field managers.COMMENT
LOW⚡internal/ssa/managed_fields.go95// Step 3: The controller server-side applies its fully specified intentCOMMENT
LOW⚡internal/ssa/managed_fields.go101// Step 4: Upgrade is called for the second time. It deletes theCOMMENT
Example Usage Blocks3 hits · 4 pts
SeverityFileLineSnippetContext
LOWapis/hack/duplicate_api_type.sh3# Usage example:COMMENT
LOWhack/duplicate_proto_type.sh3# Usage example:COMMENT
LOWhack/duplicate_api_type.sh3# Usage example:COMMENT
Modern AI Meta-Vocabulary1 hit · 2 pts
SeverityFileLineSnippetContext
MEDIUMADOPTERS.md102| [AI CoE at Vodafone Germany](https://www.vodafone.de/) | [@zouldapp](https://github.com/zouldapp) | Crossplane enablesCODE