AI Slop Code Risk Monitor

nanocurrency/nano-node

SlopCodeMonitor badge for nanocurrency/nano-node Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).
1.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for nanocurrency/nano-node. SynthScan examined 242,629 lines of code across 1005 source files, recording 405 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 1.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.

1.7
Adjusted Signal
1.7
Raw Pattern Score
100%
Time Factor
—
Last Push
—
Stars
—
Language
242.6K
Lines of Code
1.0K
Files
405
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 8.0/100 · LOW

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

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

PR Review Velocity Impact 8.0/100 · LOW

Which changes need focused human review? 405 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 405

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 405 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 Block399 hits · 395 pts
SeverityFileLineSnippetContext
LOWcrypto/blake2/blake2b-load-avx2-simple.h1#ifndef BLAKE2_AVX2_BLAKE2B_LOAD_AVX2_SIMPLE_HCOMMENT
LOWcrypto/blake2/blake2b-load-avx2-simple.h21#define BLAKE2B_LOAD_MSG_4_2(b0) b0 = _mm256_set_epi64x(m15, m4, m7, m0);COMMENT
LOWcrypto/blake2/blake2b-load-avx2-simple.h41#define BLAKE2B_LOAD_MSG_9_2(b0) b0 = _mm256_set_epi64x(m5, m6, m4, m2);COMMENT
LOWcrypto/blake2/blake2b-load-sse2.h21#define LOAD_MSG_0_4(b0, b1) b0 = _mm_set_epi64x(m11, m9); b1 = _mm_set_epi64x(m15, m13)COMMENT
LOWcrypto/blake2/blake2b-load-sse2.h41#define LOAD_MSG_5_4(b0, b1) b0 = _mm_set_epi64x(m5, m13); b1 = _mm_set_epi64x(m9, m14)COMMENT
LOWcrypto/blake2/blake2b-load-sse2.h61#define LOAD_MSG_10_4(b0, b1) b0 = _mm_set_epi64x(m11, m9); b1 = _mm_set_epi64x(m15, m13)COMMENT
LOWcrypto/blake2/blake2b.c21#include "blake2-impl.h"COMMENT
LOWcrypto/blake2/blake2-config.h21#endifCOMMENT
LOWcrypto/blake2/blake2-config.h41#endifCOMMENT
LOWcrypto/blake2/blake2-config.h61COMMENT
LOWcrypto/blake2/blake2-impl.h21#if !defined(__cplusplus) && (!defined(__STDC_VERSION__) || __STDC_VERSION__ < 199901L)COMMENT
LOWcrypto/ed25519-donna/ed25519-donna-portable-identify.h1/* os */COMMENT
LOWcrypto/ed25519-donna/ed25519-donna-portable-identify.h21#endifCOMMENT
LOWcrypto/ed25519-donna/ed25519-donna-portable-identify.h41#if defined(__clang__)COMMENT
LOWcrypto/ed25519-donna/ed25519-donna-portable-identify.h61 #define CPU_SPARCCOMMENT
LOWcrypto/ed25519-donna/ed25519-donna.h21#endifCOMMENT
LOWcrypto/ed25519-donna/ed25519-donna.h41 #endifCOMMENT
LOWcrypto/ed25519-donna/ed25519-donna.h101 #include "ed25519-donna-64bit-x86.h"COMMENT
LOWcrypto/ed25519-donna/ed25519-donna-portable.h1#include "ed25519-donna-portable-identify.h"COMMENT
LOWcrypto/ed25519-donna/ed25519-donna-portable.h21 #define DONNA_INLINE inline __attribute__((always_inline))COMMENT
LOWcrypto/ed25519-donna/ed25519-donna-portable.h41 #define shl128_pair(out,hi,lo,shift) out = __shiftleft128(lo, hi, shift);COMMENT
LOWcrypto/ed25519-donna/ed25519-donna-portable.h61 #define shr128_pair(out,hi,lo,shift) __asm__ ("shrdq %2,%1,%0" : "+r" (lo) : "r" (hi), "J" (shift)); out = lo;COMMENT
LOWcrypto/ed25519-donna/fuzz/ed25519-donna-sse2.c1#define ED25519_SUFFIX _sse2COMMENT
LOWci/actions/generate_next_git_tag.sh1#!/bin/bashCOMMENT
LOWnano/pch.hpp1#pragma onceCOMMENT
LOWnano/pch.hpp21#include <boost/lexical_cast.hpp>COMMENT
LOWnano/pch.hpp41#include <condition_variable>COMMENT
LOWnano/pch.hpp61#include <set>COMMENT
LOWnano/pch.hpp81#include <fmt/core.h>COMMENT
LOWnano/load_test/entry.cpp1#include <nano/boost/asio/connect.hpp>COMMENT
LOWnano/crypto/blake2/blake2.h1#pragma onceCOMMENT
LOWnano/messages/telemetry.hpp1#pragma onceCOMMENT
LOWnano/messages/deserialize_message.cpp1#include <nano/lib/block_type.hpp>COMMENT
LOWnano/messages/message_visitor.hpp1#pragma onceCOMMENT
LOWnano/messages/message_header.cpp1#include <nano/lib/block_type.hpp>COMMENT
LOWnano/messages/messages.hpp1#pragma onceCOMMENT
LOWnano/crypto_lib/secure_memory.hpp1#include <cstddef>COMMENT
LOWnano/crypto_lib/secure_memory.cpp1#include <nano/crypto_lib/secure_memory.hpp>COMMENT
LOWnano/crypto_lib/secure_memory.cpp21#elif defined(__GNUC__)COMMENT
LOWnano/nano_wallet/entry.cpp1#include <nano/crypto_lib/random_pool.hpp>COMMENT
LOWnano/nano_wallet/entry.cpp21#include <nano/node/node_scope_guard.hpp>COMMENT
LOWnano/core_test/bootstrap_topo_blocks.cpp1#include <nano/lib/blockbuilders.hpp>COMMENT
LOWnano/core_test/bootstrap_topo_scan.cpp1#include <nano/lib/container_info.hpp>COMMENT
LOWnano/core_test/ipc.cpp1#include <nano/lib/ipc_client.hpp>COMMENT
LOWnano/core_test/inproc.cpp1#include <nano/lib/blockbuilders.hpp>COMMENT
LOWnano/core_test/network.cpp1#include <nano/crypto_lib/random_pool.hpp>COMMENT
LOWnano/core_test/network.cpp21#include <nano/test_common/network.hpp>COMMENT
LOWnano/core_test/cementing_set.cpp1#include <nano/lib/blockbuilders.hpp>COMMENT
LOWnano/core_test/backend.cpp1#include <nano/lib/config.hpp>COMMENT
LOWnano/core_test/object_stream.cpp1#include <nano/lib/numbers.hpp>COMMENT
LOWnano/core_test/difficulty.cpp1#include <nano/lib/block_type.hpp>COMMENT
LOWnano/core_test/toml.cpp1#include <nano/lib/config_template.hpp>COMMENT
LOWnano/core_test/toml.cpp21#include <nano/node/local_block_broadcaster.hpp>COMMENT
LOWnano/core_test/ledger.cpp1#include <nano/lib/blockbuilders.hpp>COMMENT
LOWnano/core_test/ledger.cpp21#include <nano/secure/vote.hpp>COMMENT
LOWnano/core_test/deserialize_message.cpp1#include <nano/lib/block_type.hpp>COMMENT
LOWnano/core_test/election.cpp1#include <nano/lib/blockbuilders.hpp>COMMENT
LOWnano/core_test/active_elections.cpp1#include <nano/lib/blockbuilders.hpp>COMMENT
LOWnano/core_test/active_elections.cpp21#include <nano/node/transport/fake.hpp>COMMENT
LOWnano/core_test/ledger_upgrades.cpp1#include <nano/lib/block_sideband.hpp>COMMENT
339 more matches not shown…
Redundant / Tautological Comments4 hits · 6 pts
SeverityFileLineSnippetContext
LOWutil/changelog.py222 # Check if the common ancestor exists in the commit list.COMMENT
LOWci/actions/generate_next_git_tag.sh191# Check if the current commit is included in the last tagCOMMENT
LOWsystest/daemon_interrupt.sh24# Check if the process has stopped using a timeout to avoid infinite waitingCOMMENT
LOWsystest/rpc_stop.sh31# Check if the process has stopped using a timeout to avoid infinite waitingCOMMENT
Deep Nesting2 hits · 2 pts
SeverityFileLineSnippetContext
LOWutil/changelog.py181CODE
LOWutil/changelog.py404CODE