AI Slop Code Risk Monitor

confluentinc/confluent-kafka-go

SlopCodeMonitor badge for confluentinc/confluent-kafka-go Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

Confluent's Apache Kafka Golang client

1.4 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for confluentinc/confluent-kafka-go, a HTML project with 5,175 GitHub stars. SynthScan examined 104,283 lines of code across 323 source files, recording 143 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 1.4 (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.4
Adjusted Signal
1.4
Raw Pattern Score
100%
Time Factor
2026-10-28
Last Push
5.2K
Stars
HTML
Language
104.3K
Lines of Code
323
Files
143
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 6.7/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.1/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 6.7/100 · LOW

Which changes need focused human review? 143 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 1LOW 142

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 143 distinct pattern matches across 3 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 Block141 hits · 141 pts
SeverityFileLineSnippetContext
LOWschemaregistry/confluent/codegen.sh1#!/usr/bin/env bashCOMMENT
LOWschemaregistry/confluent/types/doc.go1// Package types held the generated confluent.type.Decimal bindings until they moved to theCOMMENT
LOWschemaregistry/cache/cache.go21 // Get returns the cache value associated with keyCOMMENT
LOWschemaregistry/test/secrets/generate_secrets_linux.sh1#!/bin/bashCOMMENT
LOWschemaregistry/internal/client_config.go41 BearerAuthToken stringCOMMENT
LOWschemaregistry/rules/cel/cel_container_test.go21// Three separate defects met here, all invisible while every fixture used scalar fields:COMMENT
LOWschemaregistry/rules/cel/lib.go41func DefaultEnv() (*cel.Env, error) {COMMENT
LOWschemaregistry/rules/cel/lib.go81// base env's adapter instead would capture a registry that never learns those descriptors, andCOMMENT
LOWschemaregistry/rules/cel/lib.go121 //COMMENT
LOWschemaregistry/rules/cel/lib.go141}COMMENT
LOWschemaregistry/rules/cel/decimal_util_test.go101 tc.in, got.Precision, got.Scale, tc.precision, tc.scale)COMMENT
LOWschemaregistry/rules/cel/decimal_util_test.go221 Value: []byte{0x01}, Scale: scale,COMMENT
LOWschemaregistry/rules/cel/decimal.go41const decimalTypeName = "confluent.type.Decimal"COMMENT
LOWschemaregistry/rules/cel/decimal.go61)COMMENT
LOWschemaregistry/rules/cel/decimal.go141// decimalBoundaryValue presents a decimal-shaped native value as this package's CEL decimal.COMMENT
LOWschemaregistry/rules/cel/decimal.go801 return fmt.Errorf("scale %d cannot be represented", scale)COMMENT
LOWschemaregistry/rules/cel/decimal.go821 return nilCOMMENT
LOWschemaregistry/rules/cel/cel_message_transform_test.go241// result map with. Measured against protobuf-java 4.35.1:COMMENT
LOWschemaregistry/rules/cel/cel_validator.go81 // A decimal-shaped value is presented as this package's CEL decimal so that a bare decimalCOMMENT
LOWschemaregistry/rules/cel/cel_null_avro_field_test.go1package celCOMMENT
LOWschemaregistry/rules/cel/cel_executor.go281 return cel.DynTypeCOMMENT
LOWschemaregistry/rules/cel/avro_result_writer.go101 // Slice from this node's offset, not from 0: a Variant fromCOMMENT
LOWschemaregistry/rules/cel/avro_result_writer.go261// maxAvroDecimalWidth bounds the positional form this writer will build, the same 10^7 digitsCOMMENT
LOWschemaregistry/rules/cel/cel_decimal_timestamp_test.go781// cannot see. Text('f') writes a zero as "0" at every non-positive scale, and 500 as "500"COMMENT
LOWschemaregistry/rules/cel/cel_decimal_timestamp_test.go841// min(preferred, minimalScale + (38 - minimalPrecision)), floored at the minimal scale.COMMENT
LOWschemaregistry/rules/cel/protobuf_result_writer.go41// A CEL rule returning a map is returning the whole new message: the transform has replaceCOMMENT
LOWschemaregistry/rules/cel/protobuf_result_writer.go121 _, ok := value.(structpb.NullValue)COMMENT
LOWschemaregistry/rules/cel/protobuf_result_writer.go141// Measured against protobuf-java. A proto3 optional field sits in a synthetic oneof of exactlyCOMMENT
LOWschemaregistry/rules/cel/protobuf_result_writer.go321// when computed.COMMENT
LOWschemaregistry/rules/cel/protobuf_result_writer.go401 return fmt.Errorf("cannot write %T to %s", value, fullName)COMMENT
LOWschemaregistry/rules/cel/decimal_util.go61 // Precision is the unscaled value's digit count, as BigDecimal.precision() reports itCOMMENT
LOWschemaregistry/rules/cel/decimal_util.go81// recovered from the reduced denominator (see terminatingScale) rather than read off a literalCOMMENT
LOWschemaregistry/serde/config.go21 // AutoRegisterSchemas determines whether to automatically register schemas during serializationCOMMENT
LOWschemaregistry/serde/serde.go441 Tags map[string]boolCOMMENT
LOWschemaregistry/serde/serde.go901}COMMENT
LOWschemaregistry/serde/kafka_builder.go21COMMENT
LOWschemaregistry/serde/kafka_builder.go61 }COMMENT
LOWschemaregistry/serde/map_key.go21 "reflect"COMMENT
LOWschemaregistry/serde/avrov2/avro.go141//COMMENT
LOWschemaregistry/serde/avrov2/avro.go321COMMENT
LOWschemaregistry/serde/avrov2/avro.go361}COMMENT
LOWschemaregistry/serde/avrov2/avro_util.go201 fieldValue = val.Interface()COMMENT
LOWschemaregistry/serde/avrov2/avro_validate.go21 "reflect"COMMENT
LOWschemaregistry/serde/avrov2/cel_null_transform_test.go21// The reference states the contract in CelFieldExecutor: CEL null is normalized to a Java nullCOMMENT
LOWschemaregistry/serde/avrov2/doc.go21// prefer package avrov3, which uses Confluent's maintained forkCOMMENT
LOW…gistry/serde/avrov2/cel_avro_message_transform_test.go21// This case existed only on the protobuf side, and its absence hid a real defect elsewhere -COMMENT
LOWschemaregistry/serde/jsonschema/json_schema_validate.go21 "reflect"COMMENT
LOWschemaregistry/serde/jsonschema/json_schema.go141// are left alone. It cannot be combined with SetSchemaRegistryConfig: BuildCOMMENT
LOWschemaregistry/serde/jsonschema/json_schema.go321// [kafka.DeserializingConsumer] uses for its keys or its values. Its settersCOMMENT
LOWschemaregistry/serde/jsonschema/json_schema.go361// SetSchemaRegistryClient supplies an already created Schema Registry client,COMMENT
LOWschemaregistry/serde/avrov3/avro.go141//COMMENT
LOWschemaregistry/serde/avrov3/avro.go321COMMENT
LOWschemaregistry/serde/avrov3/avro.go361}COMMENT
LOWschemaregistry/serde/avrov3/avro_util.go201 fieldValue = val.Interface()COMMENT
LOWschemaregistry/serde/avrov3/avro_validate.go21 "reflect"COMMENT
LOWschemaregistry/serde/avrov3/cel_null_transform_test.go21// The reference states the contract in CelFieldExecutor: CEL null is normalized to a Java nullCOMMENT
LOWschemaregistry/serde/avrov3/doc.go21// The github.com/hamba/avro/v2 library used by package avrov2 is nowCOMMENT
LOWschemaregistry/serde/variant/variant_test.go1// Copyright 2026 Confluent Inc.COMMENT
LOWschemaregistry/serde/variant/variant.go1// Copyright 2026 Confluent Inc.COMMENT
LOWschemaregistry/serde/variant/variant.go981// carry no offset, so they are ISO-8601 local date-times rather than RFC 3339 (which has noCOMMENT
81 more matches not shown…
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUM…ative_consumer_example/cooperative_consumer_example.go19// seamless reassignment of partitions to other group members.COMMENT
Fake / Example Data1 hit · 1 pts
SeverityFileLineSnippetContext
LOW…aregistry/rules/encryption/azurekms/azure_aead_test.go38 return azcore.AccessToken{Token: "fake-token"}, nilCODE