AI Slop Code Risk Monitor

nanomsg/nng

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

nanomsg-next-generation -- light-weight brokerless messaging

3.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for nanomsg/nng, a C project with 4,695 GitHub stars. SynthScan examined 130,862 lines of code across 419 source files, recording 492 pattern matches distributed across 7 syntactic categories. The legacy adjusted pattern signal is 3.7 (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.

3.7
Adjusted Signal
3.7
Raw Pattern Score
100%
Time Factor
2026-10-28
Last Push
4.7K
Stars
C
Language
130.9K
Lines of Code
419
Files
492
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 16.7/100 · LOW

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

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

PR Review Velocity Impact 17.5/100 · LOW

Which changes need focused human review? 492 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 2MEDIUM 1LOW 489

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 492 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 Block480 hits · 467 pts
SeverityFileLineSnippetContext
LOWCMakeLists.txt1#COMMENT
LOWdemo/http_client/CMakeLists.txt1#COMMENT
LOWdemo/http_client/http_client.c1//COMMENT
LOWdemo/http_client/http_client.c21// since this program just exits. In longer running programs or libraries,COMMENT
LOWdemo/reqrep/reqrep.c1//COMMENT
LOWdemo/stream/stream.c1// Copyright 2020 Hugo Lindström <hugolm84@gmail.com>COMMENT
LOWdemo/stream/platform/posix/server.c1// Copyright 2020 Hugo Lindström <hugolm84@gmail.com>COMMENT
LOWdemo/async/CMakeLists.txt1#COMMENT
LOWdemo/async/server.c1// Copyright 2025 Staysail Systems, Inc. <info@staysail.tech>COMMENT
LOWdemo/async/server.c21// To run this program, start the server as async_demo <url> -sCOMMENT
LOWdemo/async/client.c1// Copyright 2025 Staysail Systems, Inc. <info@staysail.tech>COMMENT
LOWdemo/pubsub_forwarder/pubsub_forwarder.c1//COMMENT
LOWdemo/pubsub_forwarder/pubsub_forwarder.c21// - In a third terminal, runCOMMENT
LOWdemo/raw/raw.c1// Copyright 2025 Staysail Systems, Inc. <info@staysail.tech>COMMENT
LOWdemo/raw/raw.c21// For example:COMMENT
LOWdemo/rest/server.c1//COMMENT
LOWdemo/rest/server.c21// The reply is obtained from the server, and sent back to the client viaCOMMENT
LOWdemo/rest/server.c41#include <string.h>COMMENT
LOWinclude/nng/http.h1//COMMENT
LOWinclude/nng/http.h101COMMENT
LOWinclude/nng/http.h121// than the amount requested. (It completes as soon as at least oneCOMMENT
LOWinclude/nng/http.h161COMMENT
LOWinclude/nng/http.h201// headers, and servers (and callbacks on the server) modify response headers.COMMENT
LOWinclude/nng/http.h241//COMMENT
LOWinclude/nng/http.h261typedef void (*nng_http_handler_func)(nng_http *, void *, nng_aio *);COMMENT
LOWinclude/nng/http.h281NNG_DECL nng_err nng_http_handler_alloc_static(COMMENT
LOWinclude/nng/http.h301// method, then the handler is executed regardless of method, and mustCOMMENT
LOWinclude/nng/http.h321COMMENT
LOWinclude/nng/http.h341// from the URL. If a server already exists, then a hold is placed on it, andCOMMENT
LOWinclude/nng/http.h361// nng_http_server_add_handler registers a handler on the server.COMMENT
LOWinclude/nng/http.h381NNG_DECL nng_err nng_http_server_set_tls(nng_http_server *, nng_tls_config *);COMMENT
LOWinclude/nng/http.h401NNG_DECL nng_err nng_http_server_set_error_file(COMMENT
LOWinclude/nng/http.h421COMMENT
LOWinclude/nng/http.h441// nng_http_client_connect establishes a new connection with the serverCOMMENT
LOWinclude/nng/args.h1//COMMENT
LOWinclude/nng/args.h21// This is a header library, and it does not depend on anything else in NNG.COMMENT
LOWinclude/nng/args.h41 int a_val; // Value stored on a good parse (>0)COMMENT
LOWinclude/nng/nng.h1//COMMENT
LOWinclude/nng/nng.h21extern "C" {COMMENT
LOWinclude/nng/nng.h41#if defined(NNG_SHARED_LIB) && defined(NNG_HIDDEN_VISIBILITY)COMMENT
LOWinclude/nng/nng.h61#define NNG_MINOR_VERSION 2COMMENT
LOWinclude/nng/nng.h121// codes. We try hard to match things semantically to one of our standardCOMMENT
LOWinclude/nng/nng.h181// Internal details are opaque.COMMENT
LOWinclude/nng/nng.h321COMMENT
LOWinclude/nng/nng.h361// and starts it listening. It is functionally equivalent to the legacyCOMMENT
LOWinclude/nng/nng.h461// nng_strerror returns a human-readable string associated with the errorCOMMENT
LOWinclude/nng/nng.h481NNG_DECL int nng_sendmsg(nng_socket, nng_msg *, int);COMMENT
LOWinclude/nng/nng.h501NNG_DECL void nng_socket_recv(nng_socket, nng_aio *);COMMENT
LOWinclude/nng/nng.h521// nng_ctx_id returns the numeric id for the context; this will beCOMMENT
LOWinclude/nng/nng.h561// nng_free is used to free memory allocated with nng_alloc. As theCOMMENT
LOWinclude/nng/nng.h581// The meaning of the inputs and the outputs are determined by theCOMMENT
LOWinclude/nng/nng.h601// when this is called.COMMENT
LOWinclude/nng/nng.h621COMMENT
LOWinclude/nng/nng.h661// nng_aio_get_output retrieves the output result at the given index.COMMENT
LOWinclude/nng/nng.h681NNG_DECL nng_err nng_aio_set_iov(nng_aio *, unsigned, const nng_iov *);COMMENT
LOWinclude/nng/nng.h701// for any reason, the cancellation callback should do nothing. TheCOMMENT
LOWinclude/nng/nng.h801// Options.COMMENT
LOWinclude/nng/nng.h821// only available for pipes. This option may return incorrect results ifCOMMENT
LOWinclude/nng/nng.h841// middle boxes thinking the session has gone idle (e.g. keeping NATCOMMENT
LOWinclude/nng/nng.h861// for its peer to accept the connection. The duration must be positive.COMMENT
420 more matches not shown…
Empty Error Handlers2 hits · 10 pts
SeverityFileLineSnippetContext
HIGHsrc/sp/transport/dtls/dtls_soak.py541except (OSError, ValueError):CODE
HIGHsrc/sp/transport/dtls/dtls_soak.py507except subprocess.TimeoutExpired:CODE
Deep Nesting5 hits · 5 pts
SeverityFileLineSnippetContext
LOWcmake/NNGCheckCoverage.py17CODE
LOWsrc/sp/transport/dtls/dtls_soak.py104CODE
LOWsrc/sp/transport/dtls/dtls_soak.py327CODE
LOWsrc/sp/transport/dtls/dtls_soak.py428CODE
LOWsrc/sp/transport/dtls/dtls_interop_test.py16CODE
Example Usage Blocks2 hits · 3 pts
SeverityFileLineSnippetContext
LOWdemo/http_client/http_client.c27// Example usage:COMMENT
LOWdemo/rest/server.c24// Example usage:COMMENT
Slop Phrases1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMdemo/rest/server.c20// NNG REP server (builtin inproc_server, for demonstration purposes only).COMMENT
Hyper-Verbose Identifiers1 hit · 1 pts
SeverityFileLineSnippetContext
LOWdocs/theme/nng-site-header.js76 function addLegacyDocumentationBar() {CODE
Excessive Try-Catch Wrapping1 hit · 1 pts
SeverityFileLineSnippetContext
LOWsrc/sp/transport/dtls/dtls_soak.py491 except Exception as error:CODE