AI Slop Code Risk Monitor

p2r3/bareiron

Name: p2r3/bareiron — C Code Quality & Security Review | AI Slop Code Risk Monitor
Creator: AI Slop Code Risk Monitor

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

Minimalist Minecraft server for memory-restrictive embedded systems

2.8 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for p2r3/bareiron, a C project with 4,432 GitHub stars. SynthScan examined 7,057 lines of code across 28 source files, recording 20 pattern matches distributed across 1 syntactic category. The legacy adjusted pattern signal is 2.8 (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.8

Adjusted Signal

2.8

Raw Pattern Score

100%

Time Factor

2026-08-22

Last Push

4.4K

Stars

Language

7.1K

Lines of Code

Files

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 13.2/100 · LOW

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

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

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 20 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 Block20 hits · 20 pts

Severity	File	Line	Snippet	Context
LOW	include/globals.h	1	#ifndef H_GLOBALS	COMMENT
LOW	include/globals.h	21	// How many players to keep in memory, NOT the amount of concurrent players	COMMENT
LOW	include/globals.h	41	#define TICKS_PER_SECOND ((float)1000000 / TIME_BETWEEN_TICKS)	COMMENT
LOW	include/globals.h	61	// Size of every major biome in multiples of CHUNK_SIZE	COMMENT
LOW	include/globals.h	81	// When targeting ESP-IDF, LittleFS is used to manage flash reads and	COMMENT
LOW	include/globals.h	101	// timing out. Default is 15s, which leaves 5s to prevent starving other	COMMENT
LOW	include/globals.h	121	// broadcast based on the amount of players, reducing overhead for higher	COMMENT
LOW	include/globals.h	141	// If defined, enables the item pickup animation when mining a block/	COMMENT
LOW	include/globals.h	221	uint8_t inventory_count[41];	COMMENT
LOW	include/tools.h	41	uint64_t splitmix64 (uint64_t state);	COMMENT
LOW	include/serialize.h	1	#ifndef SERIALIZE_H	COMMENT
LOW	src/tools.c	1	#include <stdio.h>	COMMENT
LOW	src/tools.c	21	#endif	COMMENT
LOW	src/serialize.c	1	#include "globals.h"	COMMENT
LOW	src/packets.c	1	#include <stdio.h>	COMMENT
LOW	src/main.c	1	#include <stdio.h>	COMMENT
LOW	src/main.c	21	#include <sys/types.h>	COMMENT
LOW	src/procedures.c	1	#include <stdio.h>	COMMENT
LOW	src/varnum.c	1	#include <stdint.h>	COMMENT
LOW	src/globals.c	1	#include <stdio.h>	COMMENT