AI Slop Code RIsk Monitor

memtest86plus/memtest86plus

Official repo for Memtest86+

6.1 Moderate pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for memtest86plus/memtest86plus, a C project with 1,815 GitHub stars. SynthScan examined 45,335 lines of code across 175 source files, recording 325 pattern matches distributed across 1 syntactic category. The legacy adjusted pattern signal is 6.1 (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.

6.1
Adjusted Signal
6.1
Raw Pattern Score
100%
Time Factor
2026-10-11
Last Push
1.8K
Stars
C
Language
45.3K
Lines of Code
175
Files
325
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 26.4/100 · MEDIUM

Can maintainers explain intent, assumptions, and trade-offs? 325 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 30.1/100 · MEDIUM

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

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 325 distinct pattern matches across 1 syntactic category. 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 Block325 hits · 278 pts
SeverityFileLineSnippetContext
LOWapp/display.c1// SPDX-License-Identifier: GPL-2.0COMMENT
LOWapp/display.c21#include "temperature.h"COMMENT
LOWapp/badram.c1// SPDX-License-Identifier: GPL-2.0COMMENT
LOWapp/badram.c21// - Combine new faulty addresses with it whenever possible;COMMENT
LOWapp/badram.c41COMMENT
LOWapp/version.h1#define MT_VERSION "9.00"COMMENT
LOWapp/reports.c1// SPDX-License-Identifier: GPL-2.0COMMENT
LOWapp/reports.c21#include "display.h"COMMENT
LOWapp/reports.c41#define POP_W 38COMMENT
LOWapp/main.c1// SPDX-License-Identifier: GPL-2.0COMMENT
LOWapp/main.c21#include "acpi.h"COMMENT
LOWapp/main.c41#include "timers.h"COMMENT
LOWapp/main.c61#ifndef TRACE_BARRIERSCOMMENT
LOWapp/error.c1// SPDX-License-Identifier: GPL-2.0COMMENT
LOWapp/error.c21#include "config.h"COMMENT
LOWapp/config.c1// SPDX-License-Identifier: GPL-2.0COMMENT
LOWapp/config.c21#include "hwctrl.h"COMMENT
LOWapp/config.c41COMMENT
LOWapp/config.c61#define POP_LM (POP_C + 3) // Left marginCOMMENT
LOWapp/loongarch/interrupt.c1// SPDX-License-Identifier: GPL-2.0COMMENT
LOWapp/loongarch/interrupt.c21#define INT_IP0 2COMMENT
LOWapp/loongarch/interrupt.c41#define EXC_PPI 7COMMENT
LOWapp/x86/interrupt.c1// SPDX-License-Identifier: GPL-2.0COMMENT
LOWapp/x86/interrupt.c21COMMENT
LOWapp/x86/interrupt.c41#define INT_DEVNA 7COMMENT
LOWapp/aarch64/interrupt.c1// SPDX-License-Identifier: GPL-2.0COMMENT
LOWboot/efisetup.c1// SPDX-License-Identifier: GPL-2.0-onlyCOMMENT
LOWboot/efisetup.c661 }COMMENT
LOWboot/peimage.h1// SPDX-License-Identifier: GPL-2.0COMMENT
LOWboot/peimage.h21#define IMAGE_FILE_REMOVABLE_RUN_FROM_SWAP 0x0400COMMENT
LOWboot/peimage.h41#define IMAGE_SCN_CNT_UNINITIALIZED_DATA 0x00000080 /* Section contains uninitialized data. */COMMENT
LOWboot/peimage.h61#define IMAGE_SCN_ALIGN_64BYTES 0x00700000COMMENT
LOWboot/peimage.h81#define IMAGE_SCN_MEM_SHARED 0x10000000 /* Section is shareable. */COMMENT
LOWboot/peimage.h101#define IMAGE_FILE_MACHINE_M68K 0x268COMMENT
LOWboot/peimage.h121#define IMAGE_SUBSYSTEM_NATIVE 1COMMENT
LOWboot/peimage.h141#define IMAGE_DIRECTORY_ENTRY_RESOURCE 2COMMENT
LOWboot/peimage.h281#define PEP64AOUTSZ 240COMMENT
LOWboot/sbat_csv.h1// SPDX-License-Identifier: GPL-2.0COMMENT
LOWboot/macros.h21#define __must_be_array(a) BUILD_BUG_ON_ZERO(__same_type((a), &(a)[0]))COMMENT
LOWboot/efi.h41#define EFI_ALLOCATE_MAX_ADDRESS 1COMMENT
LOWboot/efi.h61/**COMMENT
LOWtests/test_helper.c1// SPDX-License-Identifier: GPL-2.0COMMENT
LOWtests/mov_inv_rng.c1// SPDX-License-Identifier: GPL-2.0COMMENT
LOWtests/mov_inv_rng.c21// The check passes regenerate the sequence instead of storing it: xorshiftCOMMENT
LOWtests/mov_inv_walk1.c1// SPDX-License-Identifier: GPL-2.0COMMENT
LOWtests/own_addr.c1// SPDX-License-Identifier: GPL-2.0COMMENT
LOWtests/rowhammer.c1// SPDX-License-Identifier: GPL-2.0COMMENT
LOWtests/rowhammer.c21// not observable (e.g. under virtualisation).COMMENT
LOWtests/rowhammer.c41COMMENT
LOWtests/modulo_n.c1// SPDX-License-Identifier: GPL-2.0COMMENT
LOWtests/bus_stress.c1// SPDX-License-Identifier: GPL-2.0COMMENT
LOWtests/bus_stress.c21// verified; without SIMD support (i586, LoongArch) the fills use cachedCOMMENT
LOWtests/tests.c1// SPDX-License-Identifier: GPL-2.0COMMENT
LOWtests/tests.c21#include "tsc.h"COMMENT
LOWtests/block_move.c1// SPDX-License-Identifier: GPL-2.0COMMENT
LOWtests/vec_prsg.c1// SPDX-License-Identifier: GPL-2.0COMMENT
LOWtests/addr_walk1.c1// SPDX-License-Identifier: GPL-2.0COMMENT
LOWtests/mov_inv_fixed.c1// SPDX-License-Identifier: GPL-2.0COMMENT
LOWtests/bit_fade.c1// SPDX-License-Identifier: GPL-2.0COMMENT
LOWtests/bit_fade.c21// Released under version 2 of the Gnu Public License.COMMENT
265 more matches not shown…