AI Slop Code Risk Monitor

IBM/sarama

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

Sarama is a Go library for Apache Kafka.

1.0 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for IBM/sarama, a Go project with 12,525 GitHub stars. SynthScan examined 95,752 lines of code across 385 source files, recording 82 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 1.0 (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.0
Adjusted Signal
1.0
Raw Pattern Score
100%
Time Factor
2026-10-27
Last Push
12.5K
Stars
Go
Language
95.8K
Lines of Code
385
Files
82
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 4.1/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.8/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 4.6/100 · LOW

Which changes need focused human review? 82 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 1HIGH 0MEDIUM 0LOW 81

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 82 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 Block80 hits · 78 pts
SeverityFileLineSnippetContext
LOWpartitioner.go21 // partitions (even ones known to be unavailable), and its choice must beCOMMENT
LOWconfig.go41 // Net is the namespace for network-level properties used by the Broker, andCOMMENT
LOWconfig.go61 // original address list. Similar to the `client.dns.lookup` option inCOMMENT
LOWconfig.go81 Enable boolCOMMENT
LOWconfig.go141 // cluster is in the middle of a leader election (default 3).COMMENT
LOWconfig.go161COMMENT
LOWconfig.go181 }COMMENT
LOWconfig.go201 // RequiredAcks (defaults to 10 seconds). This is only relevant whenCOMMENT
LOWconfig.go221 // Transaction specifyCOMMENT
LOWconfig.go241 }COMMENT
LOWconfig.go261 // across all its accumulated topic and partition batches. Producer.MaxMessageBytesCOMMENT
LOWconfig.go281 // Similar to the `message.send.max.retries` setting of the JVM producer.COMMENT
LOWconfig.go301 // Defaults to 0 for unlimited.COMMENT
LOWconfig.go321 Session struct {COMMENT
LOWconfig.go341 //COMMENT
LOWconfig.go381 // under-replication where a replica does not have all the data yet. It can beCOMMENT
LOWconfig.go401 }COMMENT
LOWconfig.go421 // (no limit). Similar to the JVM's `fetch.message.max.bytes`. TheCOMMENT
LOWconfig.go441 // The maximum amount of time the consumer expects a message takes toCOMMENT
LOWconfig.go461 // you must read from them to prevent deadlock.COMMENT
LOWconfig.go481 // When disabled, marked offsets are only sent byCOMMENT
LOWconfig.go501 // (default is 0: disabled).COMMENT
LOWconfig.go521 // interceptor chain.COMMENT
LOWconfig.go541 // and most 3rdparty ones.COMMENT
LOWmetadata.go241 ch, queued := m.refreshOrQueue(topics)COMMENT
LOWsync_producer.go21type SyncProducer interface {COMMENT
LOWasync_producer.go21COMMENT
LOWasync_producer.go41 // when both the Errors and Successes channels have been closed. When callingCOMMENT
LOWasync_producer.go361 // Sarama completely ignores this field and is only to be used forCOMMENT
LOWlist_transactions_request.go21 // one of the filtered states are returnedCOMMENT
LOWCHANGELOG.md1321### ImprovementsCOMMENT
LOWCHANGELOG.md1341## FixesCOMMENT
LOWsarama.go101COMMENT
LOWdescribe_groups_response.go221COMMENT
LOWrequest_test.go421 // TODO: FindCoordinatorRequest v5 is not supported, but expected for KafkaVersion 3.8.0COMMENT
LOWrequest_test.go441 // apiKeyListOffsets: 9, // up from 8COMMENT
LOWrequest_test.go461 // apiKeyEndTxn: 5, // up from 4COMMENT
LOWrequest.go221 return &UpdateFeaturesRequest{Version: version}COMMENT
LOWoffset_manager.go621}COMMENT
LOWoffset_manager.go641 // To follow upstream conventions, you are expected to mark the offset of theCOMMENT
LOWoffset_manager.go661 // Consumer.Return.Errors setting to true, and read from this channel.COMMENT
LOWclient.go21// automatically when it passes out of scope. It is safe to share a client amongst manyCOMMENT
LOWclient.go81 // available metadata for those topics. If no topics are provided, it will refreshCOMMENT
LOWclient.go121 // to call this function before a client object passes out of scope, as it willCOMMENT
LOWclient.go1081 // Close may have run since the check above, leaving nil mapsCOMMENT
LOWinterceptors.go1package saramaCOMMENT
LOWproduce_response.go1package saramaCOMMENT
LOWadmin.go21 // It may take several seconds after CreateTopic returns success for all the brokersCOMMENT
LOWadmin.go41 // If partitions are increased for a topic that has a key, the partition logic or ordering ofCOMMENT
LOWadmin.go61 // The returned configuration includes default values and the Default is trueCOMMENT
LOWadmin.go81 // This operation is supported by brokers with version 0.11.0.0 or higher.COMMENT
LOWadmin.go101 //COMMENT
LOWadmin.go121 // ElectLeaders allows to trigger the election of preferred leaders for a set of partitions.COMMENT
LOWadmin.go141 // is re-batched. Non-retriable per-group errors are returned in the per-group Err.COMMENT
LOWconsumer.go61 // This method is the same as Client.Partitions(), and is provided for convenience.COMMENT
LOWconsumer.go361 for _, partitions := range c.children {COMMENT
LOWconsumer.go381//COMMENT
LOWconsumer.go401 // Messages returns the read channel for the messages that are returned byCOMMENT
LOWfetch_request.go61 return errCOMMENT
LOWfetch_request.go81 // transactional records. Using READ_UNCOMMITTED (isolation_level = 0)COMMENT
20 more matches not shown…
Hallucination Indicators1 hit · 15 pts
SeverityFileLineSnippetContext
CRITICALpartitioner_test.go324 // org.apache.kafka.common.utils.Utils.murmur2() implementationCOMMENT
Example Usage Blocks1 hit · 2 pts
SeverityFileLineSnippetContext
LOWutils.go366// Example usage:COMMENT