AI Slop Code RIsk Monitor

uber-go/zap

Blazing fast, structured, leveled logging in Go.

7.6 Moderate pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for uber-go/zap, a Go project with 24,664 GitHub stars. SynthScan examined 25,905 lines of code across 159 source files, recording 198 pattern matches distributed across 2 syntactic categories. The legacy adjusted pattern signal is 7.6 (Moderate 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.

7.6
Adjusted Signal
7.6
Raw Pattern Score
100%
Time Factor
2026-09-16
Last Push
24.7K
Stars
Go
Language
25.9K
Lines of Code
159
Files
198
Pattern Hits
2026-10-12
Scan Date
0.00
HC Hit Rate

Risk Review · v3

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

Cognitive Ownership Risk 31.5/100 · MEDIUM

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

Hallucinated Dependency & Supply Chain Risk 0.4/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 31.8/100 · MEDIUM

Which changes need focused human review? 198 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 0LOW 198

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 198 distinct pattern matches across 2 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 Block196 hits · 196 pts
SeverityFileLineSnippetContext
LOWsink.go1// Copyright (c) 2016-2022 Uber Technologies, Inc.COMMENT
LOWglobal.go1// Copyright (c) 2016 Uber Technologies, Inc.COMMENT
LOWconfig.go1// Copyright (c) 2016 Uber Technologies, Inc.COMMENT
LOWconfig.go41 Thereafter int `json:"thereafter" yaml:"thereafter"`COMMENT
LOWconfig.go61 // level of all loggers descended from this config.COMMENT
LOWconfig.go81 EncoderConfig zapcore.EncoderConfig `json:"encoderConfig" yaml:"encoderConfig"`COMMENT
LOWconfig.go101//COMMENT
LOWconfig.go141// NewProductionConfig builds a reasonable default production loggingCOMMENT
LOWconfig.go181// - The message passed to the log statement.COMMENT
LOWerror.go1// Copyright (c) 2017 Uber Technologies, Inc.COMMENT
LOWexample_test.go1// Copyright (c) 2016 Uber Technologies, Inc.COMMENT
LOWexample_test.go61 )COMMENT
LOWflag.go1// Copyright (c) 2016 Uber Technologies, Inc.COMMENT
LOWincrease_level_test.go1// Copyright (c) 2020 Uber Technologies, Inc.COMMENT
LOWoptions.go1// Copyright (c) 2016 Uber Technologies, Inc.COMMENT
LOWoptions.go161// WithFatalHook sets a CheckWriteHook to run on fatal logs.COMMENT
LOWwriter_test.go1// Copyright (c) 2016-2022 Uber Technologies, Inc.COMMENT
LOWfield.go1// Copyright (c) 2016 Uber Technologies, Inc.COMMENT
LOWfield.go41// Skip constructs a no-op field, which is often useful when handling invalidCOMMENT
LOWfield.go321// any object into the logging context, but it's relatively slow andCOMMENT
LOWfield.go441 return dictObject(val)COMMENT
LOWfield.go461// and then call a function on it.COMMENT
LOWtime.go1// Copyright (c) 2016 Uber Technologies, Inc.COMMENT
LOWencoder.go1// Copyright (c) 2016 Uber Technologies, Inc.COMMENT
LOWsink_windows_test.go1// Copyright (c) 2022 Uber Technologies, Inc.COMMENT
LOWlogger.go1// Copyright (c) 2016 Uber Technologies, Inc.COMMENT
LOWlogger.go181 if len(fields) == 0 {COMMENT
LOWlogger_bench_test.go1// Copyright (c) 2016 Uber Technologies, Inc.COMMENT
LOWsugar_test.go1// Copyright (c) 2016 Uber Technologies, Inc.COMMENT
LOWcommon_test.go1// Copyright (c) 2016 Uber Technologies, Inc.COMMENT
LOWwriter.go1// Copyright (c) 2016-2022 Uber Technologies, Inc.COMMENT
LOWflag_test.go1// Copyright (c) 2016 Uber Technologies, Inc.COMMENT
LOWlevel_test.go1// Copyright (c) 2016 Uber Technologies, Inc.COMMENT
LOWdoc.go1// Copyright (c) 2016 Uber Technologies, Inc.COMMENT
LOWdoc.go21// Package zap provides fast, structured, leveled logging.COMMENT
LOWdoc.go41// variadic number of key-value pairs. (For more advanced use cases, they alsoCOMMENT
LOWdoc.go61//COMMENT
LOWdoc.go81// The simplest way to build a Logger is to use zap's opinionated presets:COMMENT
LOWdoc.go101// # Extending ZapCOMMENT
LOWlevel.go1// Copyright (c) 2016 Uber Technologies, Inc.COMMENT
LOWlevel.go41 ErrorLevel = zapcore.ErrorLevelCOMMENT
LOWlevel.go61COMMENT
LOWhttp_handler_test.go1// Copyright (c) 2016 Uber Technologies, Inc.COMMENT
LOWsink_test.go1// Copyright (c) 2016 Uber Technologies, Inc.COMMENT
LOWleak_test.go1// Copyright (c) 2021 Uber Technologies, Inc.COMMENT
LOWhttp_handler.go1// Copyright (c) 2016 Uber Technologies, Inc.COMMENT
LOWhttp_handler.go41// {"level":"info"}COMMENT
LOWhttp_handler.go61// curl -X PUT localhost:8080/log/level?level=debugCOMMENT
LOWglobal_test.go1// Copyright (c) 2016 Uber Technologies, Inc.COMMENT
LOWsugar.go1// Copyright (c) 2016 Uber Technologies, Inc.COMMENT
LOWsugar.go41// Unlike the Logger, the SugaredLogger doesn't insist on structured logging.COMMENT
LOWsugar.go81 return &SugaredLogger{base: base}COMMENT
LOWsugar.go101// unsugared.With(COMMENT
LOWsugar.go121// Until that occurs, the logger may retain references to objects inside the fields,COMMENT
LOWencoder_test.go1// Copyright (c) 2016 Uber Technologies, Inc.COMMENT
LOWstacktrace_ext_test.go1// Copyright (c) 2016, 2017 Uber Technologies, Inc.COMMENT
LOWerror_test.go1// Copyright (c) 2017 Uber Technologies, Inc.COMMENT
LOWconfig_test.go1// Copyright (c) 2016 Uber Technologies, Inc.COMMENT
LOWtime_test.go1// Copyright (c) 2016 Uber Technologies, Inc.COMMENT
LOWarray.go1// Copyright (c) 2016 Uber Technologies, Inc.COMMENT
136 more matches not shown…
Fake / Example Data2 hits · 2 pts
SeverityFileLineSnippetContext
LOWlogger_bench_test.go49 Name: "Jane Doe",CODE
LOWbenchmarks/zap_test.go53 Name: "Jane Doe",CODE