AI Slop Code Risk Monitor

nats-io/nats-server

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

High-Performance server for NATS.io, the cloud and edge native messaging system.

1.0 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for nats-io/nats-server, a Go project with 20,973 GitHub stars. SynthScan examined 488,724 lines of code across 307 source files, recording 375 pattern matches distributed across 7 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-30
Last Push
21.0K
Stars
Go
Language
488.7K
Lines of Code
307
Files
375
Pattern Hits
2026-10-31
Scan Date
0.04
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.6/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 373 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.0/100 · LOW

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

PR Review Velocity Impact 4.4/100 · LOW

Which changes need focused human review? 375 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 12MEDIUM 3LOW 360

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 375 distinct pattern matches across 7 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 Block344 hits · 344 pts
SeverityFileLineSnippetContext
LOWmain.go1// Copyright 2012-2026 The NATS AuthorsCOMMENT
LOWlogger/log.go1// Copyright 2012-2025 The NATS AuthorsCOMMENT
LOWlogger/log_test.go1// Copyright 2012-2026 The NATS AuthorsCOMMENT
LOWlogger/syslog.go1// Copyright 2012-2025 The NATS AuthorsCOMMENT
LOWlogger/syslog_test.go1// Copyright 2012-2025 The NATS AuthorsCOMMENT
LOWlogger/syslog_windows.go1// Copyright 2012-2025 The NATS AuthorsCOMMENT
LOWlogger/syslog_windows_test.go1// Copyright 2012-2025 The NATS AuthorsCOMMENT
LOWtest/pedantic_test.go1// Copyright 2012-2019 The NATS AuthorsCOMMENT
LOWtest/verbose_test.go1// Copyright 2012-2018 The NATS AuthorsCOMMENT
LOWtest/auth_test.go1// Copyright 2012-2024 The NATS AuthorsCOMMENT
LOWtest/cluster_test.go1// Copyright 2013-2026 The NATS AuthorsCOMMENT
LOWtest/services_test.go1// Copyright 2020-2025 The NATS AuthorsCOMMENT
LOWtest/fanout_test.go1// Copyright 2018-2025 The NATS AuthorsCOMMENT
LOWtest/test.go1// Copyright 2012-2026 The NATS AuthorsCOMMENT
LOWtest/accounts_cycles_test.go1// Copyright 2020-2026 The NATS AuthorsCOMMENT
LOWtest/operator_test.go1// Copyright 2018-2025 The NATS AuthorsCOMMENT
LOWtest/routes_test.go1// Copyright 2012-2025 The NATS AuthorsCOMMENT
LOWtest/test_test.go1// Copyright 2016-2025 The NATS AuthorsCOMMENT
LOWtest/service_latency_test.go1// Copyright 2019-2026 The NATS AuthorsCOMMENT
LOWtest/new_routes_test.go1// Copyright 2018-2026 The NATS AuthorsCOMMENT
LOWtest/new_routes_test.go2121COMMENT
LOWtest/monitor_test.go1// Copyright 2012-2024 The NATS AuthorsCOMMENT
LOWtest/port_test.go1// Copyright 2014-2019 The NATS AuthorsCOMMENT
LOWtest/ports_test.go1// Copyright 2018-2024 The NATS AuthorsCOMMENT
LOWtest/route_discovery_test.go1// Copyright 2015-2024 The NATS AuthorsCOMMENT
LOWtest/proto_test.go1// Copyright 2012-2024 The NATS AuthorsCOMMENT
LOWtest/ping_test.go1// Copyright 2012-2025 The NATS AuthorsCOMMENT
LOWtest/ocsp_test.go1// Copyright 2021-2026 The NATS AuthorsCOMMENT
LOWtest/system_services_test.go1// Copyright 2019-2026 The NATS AuthorsCOMMENT
LOWtest/cluster_tls_test.go1// Copyright 2013-2025 The NATS AuthorsCOMMENT
LOWtest/gateway_test.go1// Copyright 2018-2026 The NATS AuthorsCOMMENT
LOWtest/opts_test.go1// Copyright 2015-2025 The NATS AuthorsCOMMENT
LOWtest/client_auth_test.go1// Copyright 2016-2025 The NATS AuthorsCOMMENT
LOWtest/bench_test.go1// Copyright 2012-2026 The NATS AuthorsCOMMENT
LOWtest/pid_test.go1// Copyright 2012-2025 The NATS AuthorsCOMMENT
LOWtest/tls_test.go1// Copyright 2015-2026 The NATS AuthorsCOMMENT
LOWtest/tls_test.go1361 err errorCOMMENT
LOWtest/leafnode_test.go1// Copyright 2019-2026 The NATS AuthorsCOMMENT
LOWtest/client_cluster_test.go1// Copyright 2013-2026 The NATS AuthorsCOMMENT
LOWtest/gosrv_test.go1// Copyright 2012-2025 The NATS AuthorsCOMMENT
LOWtest/user_authorization_test.go1// Copyright 2016-2025 The NATS AuthorsCOMMENT
LOWtest/maxpayload_test.go1// Copyright 2015-2026 The NATS AuthorsCOMMENT
LOWtest/norace_test.go1// Copyright 2019-2025 The NATS AuthorsCOMMENT
LOWtest/ocsp_peer_test.go1// Copyright 2023-2025 The NATS AuthorsCOMMENT
LOWinternal/antithesis/noop.go1// Copyright 2022-2024 The NATS AuthorsCOMMENT
LOWinternal/antithesis/test_assert.go1// Copyright 2022-2024 The NATS AuthorsCOMMENT
LOWinternal/antithesis/test_assert.go21 "fmt"COMMENT
LOWinternal/antithesis/test_assert.go61 // Always print the stack traceCOMMENT
LOWinternal/testhelper/logging.go1// Copyright 2019-2025 The NATS AuthorsCOMMENT
LOWinternal/ocsp/ocsp.go1// Copyright 2019-2024 The NATS AuthorsCOMMENT
LOWserver/norace_2_test.go1// Copyright 2018-2026 The NATS AuthorsCOMMENT
LOWserver/reload.go1// Copyright 2017-2026 The NATS AuthorsCOMMENT
LOWserver/reload.go1301// The `co` compression options are applied to the given leaf connection `c`.COMMENT
LOWserver/jetstream_cluster.go1// Copyright 2020-2026 The NATS AuthorsCOMMENT
LOWserver/jetstream_cluster.go41)COMMENT
LOWserver/jetstream_cluster.go81 // that have a local consumer the meta layer doesn't know about (yet).COMMENT
LOWserver/jetstream_cluster.go201 // Excluded peers are evacuated and can't be added to this group as part of the metaCOMMENT
LOWserver/log.go1// Copyright 2012-2026 The NATS AuthorsCOMMENT
LOWserver/accounts.go1// Copyright 2018-2026 The NATS AuthorsCOMMENT
LOWserver/accounts.go201// Reply subjects are normally unique per request, so the overwhelming majorityCOMMENT
284 more matches not shown…
Synthetic Comment Markers12 hits · 90 pts
SeverityFileLineSnippetContext
HIGHserver/jetstream_cluster.go6251 // Report the config as requested, the stream can still be running at its origin.COMMENT
HIGHserver/jetstream_cluster.go6897 // Report the config as requested, the stream can still be running at its origin.COMMENT
HIGHserver/jetstream_cluster.go6980 // Report the config as requested, the stream can still be running at its origin.COMMENT
HIGHserver/jetstream_cluster.go14309 // Report the config as requested, the stream can still be running at its origin.COMMENT
HIGHserver/monitor.go3196 // Report the config as requested, the stream can still be running at its origin.COMMENT
HIGHserver/events.go3234 // Reload the server config, as requested.COMMENT
HIGHserver/jetstream_api.go2188 // Report the config as requested, the stream can still be running at its origin.COMMENT
HIGHserver/jetstream_cluster_3_test.go12889// The running config is at its origin, while the config as requested is the target.COMMENT
HIGHserver/jetstream_cluster_3_test.go12900 // Placement/retention as requested by the user.COMMENT
HIGHserver/jetstream_cluster_3_test.go12973 // Must be reported as requested, i.e. reverting back to the target.COMMENT
HIGHserver/jetstream_cluster_3_test.go13182 // The update response must report the config as requested.COMMENT
HIGHserver/jetstream_cluster_3_test.go13212 // But stream info, stream list and jsz must all report the config as requested.COMMENT
Verbosity Indicators11 hits · 16 pts
SeverityFileLineSnippetContext
LOWserver/reload.go471 // If the mode is "s2_auto", we need to check if there is reallyCOMMENT
LOWserver/reload.go1317 // If the mode is "s2_auto", we need to check if there is reallyCOMMENT
LOWserver/jetstream_cluster.go2786 // If we're not recovering, we need to check if we have any left-over streams or consumers that aren'tCOMMENT
LOWserver/auth_callout_test.go4442 // Step 1: Inject zombie connections into FOO account.COMMENT
LOWserver/auth_callout_test.go4454 // Step 2: Connect legitimate clients. FOO has max_connections: 5.COMMENT
LOWserver/route.go1810 // We need to check if this route is "no_pool" in which case weCOMMENT
LOWserver/client.go5872 // We need to check if this is a request that has a stamped client information header.COMMENT
LOWserver/consumer.go6758 // We need to check if the pending items left are still valid.COMMENT
LOWserver/leafnode.go2966 // If we are a spoke, we need to check if we are allowed to send this subscription over to the hub.COMMENT
LOWserver/jetstream_cluster_3_test.go4762 // we need to check if it restored from the snapshot properlyCOMMENT
LOWserver/raft.go5142 // This is us. We need to check if we can become the leader.COMMENT
AI Slop Vocabulary3 hits · 9 pts
SeverityFileLineSnippetContext
MEDIUMserver/mqtt.go5069// TODO: would prefer a more robust and performant way of checking theCOMMENT
MEDIUMserver/jetstream_leafnode_test.go2086 // Pointer-equality on *subscription is timing-robust:COMMENT
MEDIUMserver/avl/seqset.go152// This will more effectively utilize space versus self selecting.COMMENT
Structural Annotation Overuse2 hits · 3 pts
SeverityFileLineSnippetContext
LOWserver/auth_callout_test.go4442 // Step 1: Inject zombie connections into FOO account.COMMENT
LOWserver/auth_callout_test.go4454 // Step 2: Connect legitimate clients. FOO has max_connections: 5.COMMENT
Fake / Example Data2 hits · 2 pts
SeverityFileLineSnippetContext
LOWserver/util_test.go169 {"nats://foo:bar@example.org", "nats://foo:xxxxx@example.org"},CODE
LOWserver/util_test.go170 {"nats://foo@example.org", "nats://foo@example.org"},CODE
Redundant / Tautological Comments1 hit · 2 pts
SeverityFileLineSnippetContext
LOWserver/monitor_test.go5942 # Set this to make sure that it does not impact secure monitoringCOMMENT