AI Slop Code Risk Monitor

xmrig/xmrig

SlopCodeMonitor badge for xmrig/xmrig Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).
2.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for xmrig/xmrig. SynthScan examined 250,310 lines of code across 868 source files, recording 762 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 2.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.

2.7
Adjusted Signal
2.7
Raw Pattern Score
100%
Time Factor
—
Last Push
—
Stars
—
Language
250.3K
Lines of Code
868
Files
762
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 12.4/100 · LOW

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

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

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 762 distinct pattern matches across 4 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 Block751 hits · 648 pts
SeverityFileLineSnippetContext
LOWsrc/Summary.cpp21#include <uv.h>COMMENT
LOWsrc/version.h1/* XMRigCOMMENT
LOWsrc/version.h21#define APP_VER_MINOR 26COMMENT
LOWsrc/version.h41# elseCOMMENT
LOWsrc/version.h61# define APP_OS "Haiku"COMMENT
LOWsrc/version.h81#ifdef XMRIG_64_BITCOMMENT
LOWsrc/App.cpp21 *COMMENT
LOWsrc/crypto/ghostrider/sph_whirlpool.c3441COMMENT
LOWsrc/crypto/ghostrider/md_helper.c81#endifCOMMENT
LOWsrc/crypto/ghostrider/md_helper.c101#endifCOMMENT
LOWsrc/crypto/ghostrider/sph_hamsi.c101#define SPH_HAMSI_EXPAND_SMALL 4COMMENT
LOWsrc/crypto/ghostrider/sph_hamsi.c461 sc->h[0x9] = c9; \COMMENT
LOWsrc/crypto/ghostrider/sph_hamsi.c481#define s0B m5COMMENT
LOWsrc/crypto/ghostrider/sph_skein.c41COMMENT
LOWsrc/crypto/ghostrider/sph_skein.c61#define M5_0_3 3COMMENT
LOWsrc/crypto/ghostrider/sph_skein.c81#define M5_4_3 2COMMENT
LOWsrc/crypto/ghostrider/sph_skein.c101#define M5_8_3 1COMMENT
LOWsrc/crypto/ghostrider/sph_skein.c121#define M5_12_3 0COMMENT
LOWsrc/crypto/ghostrider/sph_skein.c141#define M5_16_3 4COMMENT
LOWsrc/crypto/ghostrider/sph_skein.c161#define M9_0_3 3COMMENT
LOWsrc/crypto/ghostrider/sph_skein.c181#define M9_2_5 7COMMENT
LOWsrc/crypto/ghostrider/sph_skein.c201#define M9_4_7 2COMMENT
LOWsrc/crypto/ghostrider/sph_skein.c221#define M9_7_0 7COMMENT
LOWsrc/crypto/ghostrider/sph_skein.c241#define M9_9_2 2COMMENT
LOWsrc/crypto/ghostrider/sph_skein.c261#define M9_11_4 6COMMENT
LOWsrc/crypto/ghostrider/sph_skein.c281#define M9_13_6 1COMMENT
LOWsrc/crypto/ghostrider/sph_skein.c301COMMENT
LOWsrc/crypto/ghostrider/sph_skein.c321#define M9_18_1 1COMMENT
LOWsrc/crypto/ghostrider/sph_skein.c341#define M3_4_0 1COMMENT
LOWsrc/crypto/ghostrider/sph_skein.c361#define M3_14_0 2COMMENT
LOWsrc/crypto/ghostrider/sph_jh.c41COMMENT
LOWsrc/crypto/ghostrider/sph_jh.c81 ((SPH_C64(x) << 8) & SPH_C64(0x000000FF00000000)) | \COMMENT
LOWsrc/crypto/ghostrider/sph_simd.c41#endifCOMMENT
LOWsrc/crypto/ghostrider/sph_simd.c381COMMENT
LOWsrc/crypto/ghostrider/sph_simd.c401#define WS_2_3 W_SMALL(20, -128, -64, 233)COMMENT
LOWsrc/crypto/ghostrider/sph_simd.c421 INNER(q[16 * (sb) + 2 * 5 + o1], q[16 * (sb) + 2 * 5 + o2], mm), \COMMENT
LOWsrc/crypto/ghostrider/sph_simd.c441#define WB_2_0 W_BIG(17, -256, -128, 233)COMMENT
LOWsrc/crypto/ghostrider/sph_simd.c461#define PP4_0_0 1COMMENT
LOWsrc/crypto/ghostrider/sph_simd.c481#define PP8_0_7 6COMMENT
LOWsrc/crypto/ghostrider/sph_simd.c501#define PP8_3_0 3COMMENT
LOWsrc/crypto/ghostrider/sph_simd.c521#define PP8_5_2 5COMMENT
LOWsrc/crypto/ghostrider/sph_simd.c701 STEP_ELT(6, w6, fun, s, pp8b); \COMMENT
LOWsrc/crypto/ghostrider/sph_simd.c721#define M3_7_1 2_COMMENT
LOWsrc/crypto/ghostrider/sph_simd.c761COMMENT
LOWsrc/crypto/ghostrider/sph_simd.c961#undef B0COMMENT
LOWsrc/crypto/ghostrider/sph_simd.c981#define B0 (sc->state[ 4])COMMENT
LOWsrc/crypto/ghostrider/sph_simd.c1081#undef B1COMMENT
LOWsrc/crypto/ghostrider/sph_simd.c1101#define A3 state[ 3]COMMENT
LOWsrc/crypto/ghostrider/sph_simd.c1301}COMMENT
LOWsrc/crypto/ghostrider/sph_simd.c1321#undef C2COMMENT
LOWsrc/crypto/ghostrider/sph_simd.c1341#define A2 (sc->state[ 2])COMMENT
LOWsrc/crypto/ghostrider/sph_simd.c1361#define C6 (sc->state[22])COMMENT
LOWsrc/crypto/ghostrider/sph_simd.c1481 sc->state[28], sc->state[29], sc->state[30], sc->state[31],COMMENT
LOWsrc/crypto/ghostrider/sph_simd.c1501#undef B5COMMENT
LOWsrc/crypto/ghostrider/ghostrider.cpp21#include "sph_bmw.h"COMMENT
LOWsrc/crypto/ghostrider/ghostrider.cpp41#include "crypto/cn/CnCtx.h"COMMENT
LOWsrc/crypto/ghostrider/sph_fugue.c521#define READ_STATE_BIG(state)COMMENT
LOWsrc/crypto/ghostrider/sph_fugue.c541#define S17 ((sc)->S[17])COMMENT
LOWsrc/crypto/ghostrider/sph_bmw.c101#endifCOMMENT
LOWsrc/crypto/ghostrider/sph_bmw.c121#define I16_29 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28COMMENT
691 more matches not shown…
Slop Phrases5 hits · 8 pts
SeverityFileLineSnippetContext
LOWsrc/3rdparty/hwloc/include/hwloc/glibc-sched.h26#error Please make sure to include sched.h before including glibc-sched.h, and define _GNU_SOURCE before any inclusion oCOMMENT
LOWsrc/3rdparty/argon2/arch/x86_64/lib/argon2-avx2.c260 /* Don't forget to generate the first block of addresses: */COMMENT
LOWsrc/3rdparty/argon2/arch/x86_64/lib/argon2-avx512f.c245 /* Don't forget to generate the first block of addresses: */COMMENT
LOW…/3rdparty/argon2/arch/x86_64/lib/argon2-template-128.h103 /* Don't forget to generate the first block of addresses: */COMMENT
LOWsrc/3rdparty/argon2/lib/argon2-template-64.h129 /* Don't forget to generate the first block of addresses: */COMMENT
Verbosity Indicators3 hits · 4 pts
SeverityFileLineSnippetContext
LOWsrc/3rdparty/fmt/format-inl.h2166 // Step 1: integer promotion & Schubfach multiplier calculation.COMMENT
LOWsrc/3rdparty/fmt/format-inl.h2212 // Step 2: Try larger divisor; remove trailing zeros if necessaryCOMMENT
LOWsrc/3rdparty/fmt/format-inl.h2248 // Step 3: Find the significand with the smaller divisorCOMMENT
Structural Annotation Overuse3 hits · 4 pts
SeverityFileLineSnippetContext
LOWsrc/3rdparty/fmt/format-inl.h2166 // Step 1: integer promotion & Schubfach multiplier calculation.COMMENT
LOWsrc/3rdparty/fmt/format-inl.h2212 // Step 2: Try larger divisor; remove trailing zeros if necessaryCOMMENT
LOWsrc/3rdparty/fmt/format-inl.h2248 // Step 3: Find the significand with the smaller divisorCOMMENT