AI Slop Code Risk Monitor

Immediate-Mode-UI/Nuklear

SlopCodeMonitor badge for Immediate-Mode-UI/Nuklear Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

A single-header ANSI C immediate mode cross-platform GUI library

2.4 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for Immediate-Mode-UI/Nuklear, a C project with 11,480 GitHub stars. SynthScan examined 90,484 lines of code across 143 source files, recording 232 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 2.4 (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.4
Adjusted Signal
2.4
Raw Pattern Score
100%
Time Factor
2026-10-31
Last Push
11.5K
Stars
C
Language
90.5K
Lines of Code
143
Files
232
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 10.9/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 229 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? 3 finding(s).

PR Review Velocity Impact 12.3/100 · LOW

Which changes need focused human review? 232 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 3LOW 229

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 232 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 Block227 hits · 207 pts
SeverityFileLineSnippetContext
LOWdemo/xcb_cairo/nuklear_xcb.h81COMMENT
LOWdemo/xcb_cairo/nuklear_xcb.h101#endif /* NK_XCB_FPS */COMMENT
LOWdemo/xcb_cairo/main.c1/* nuklear - v1.32.0 - public domain */COMMENT
LOWdemo/xcb_cairo/main.c41/*#define INCLUDE_ALL */COMMENT
LOWdemo/xcb_cairo/main.c61#ifdef INCLUDE_CALCULATORCOMMENT
LOWdemo/sdl_opengl2/main.c1/* nuklear - 1.32.0 - public domain */COMMENT
LOWdemo/sdl_opengl2/main.c41#define INCLUDE_OVERVIEWCOMMENT
LOWdemo/sdl_opengl2/main.c61 #include "../../demo/common/canvas.c"COMMENT
LOWdemo/sdl_opengl3/main.c1/* nuklear - 1.32.0 - public domain */COMMENT
LOWdemo/sdl_opengl3/main.c41/*#define INCLUDE_ALL */COMMENT
LOWdemo/sdl_opengl3/main.c61#ifdef INCLUDE_CALCULATORCOMMENT
LOWdemo/d3d11/nuklear_d3d11_vertex_shader.h1#if 0COMMENT
LOWdemo/d3d11/nuklear_d3d11_vertex_shader.h21// TEXCOORD 0 xy 2 NONE float xy COMMENT
LOWdemo/d3d11/nuklear_d3d11_pixel_shader.h1#if 0COMMENT
LOWdemo/d3d11/nuklear_d3d11_pixel_shader.h21//COMMENT
LOWdemo/d3d11/main.c1/* nuklear - 1.32.0 - public domain */COMMENT
LOWdemo/d3d11/main.c41/*#define INCLUDE_CONFIGURATOR */COMMENT
LOWdemo/sdl_opengles2/main.c1/* nuklear - 1.40.8 - public domain */COMMENT
LOWdemo/sdl_opengles2/main.c41 * done with this library. To try out an example uncomment the defines */COMMENT
LOWdemo/sdl_opengles2/main.c61#endifCOMMENT
LOWdemo/sfml_opengl3/main.cpp1/* nuklear - v1.32.0 - public domain */COMMENT
LOWdemo/sfml_opengl3/main.cpp41/*#define INCLUDE_CALCULATOR */COMMENT
LOWdemo/sfml_opengl3/main.cpp61#endifCOMMENT
LOWdemo/sdl_renderer/main.c1/* nuklear - 1.32.0 - public domain */COMMENT
LOWdemo/sdl_renderer/main.c41/*#define INCLUDE_CONFIGURATOR */COMMENT
LOWdemo/gdi_native_nuklear/main.c1#include <windows.h>COMMENT
LOWdemo/sfml_opengl2/main.cpp1/* nuklear - v1.32.0 - public domain */COMMENT
LOWdemo/sfml_opengl2/main.cpp41#define INCLUDE_OVERVIEWCOMMENT
LOWdemo/sfml_opengl2/main.cpp61 #include "../../demo/common/canvas.c"COMMENT
LOWdemo/sdl3_opengl3/main.c1/* nuklear - 1.32.0 - public domain */COMMENT
LOWdemo/sdl3_opengl3/main.c41/*#define INCLUDE_ALL */COMMENT
LOWdemo/sdl3_opengl3/main.c61#ifdef INCLUDE_CALCULATORCOMMENT
LOWdemo/gdi/main.c1/* nuklear - 1.32.0 - public domain */COMMENT
LOWdemo/gdi/main.c41 #define INCLUDE_CONFIGURATORCOMMENT
LOWdemo/common/filebrowser/stb_image.h121COMMENT
LOWdemo/common/filebrowser/stb_image.h141// // ... x = width, y = height, n = # 8-bit components per pixel ...COMMENT
LOWdemo/common/filebrowser/stb_image.h161// output otherwise. E.g. if you set desired_channels to 4, you will alwaysCOMMENT
LOWdemo/common/filebrowser/stb_image.h181// Paletted PNG, BMP, GIF, and PIC images are automatically depalettized.COMMENT
LOWdemo/common/filebrowser/stb_image.h201// which defaults to 2**24 = 16777216 pixels. Due to the above memory limit,COMMENT
LOWdemo/common/filebrowser/stb_image.h221// PhilosophyCOMMENT
LOWdemo/common/filebrowser/stb_image.h241//COMMENT
LOWdemo/common/filebrowser/stb_image.h261//COMMENT
LOWdemo/common/filebrowser/stb_image.h281// interface; if you attempt to load an HDR file, it will be automatically remappedCOMMENT
LOWdemo/common/filebrowser/stb_image.h301// stbi_ldr_to_hdr_gamma(2.2f);COMMENT
LOWdemo/common/filebrowser/stb_image.h321// says there's premultiplied data (currently only happens in iPhone images,COMMENT
LOWdemo/common/filebrowser/stb_image.h341//COMMENT
LOWdemo/common/filebrowser/stb_image.h381 STBI_rgb_alpha = 4COMMENT
LOWdemo/common/filebrowser/stb_image.h541//COMMENT
LOWdemo/common/filebrowser/stb_image.h561 #define STBI_NO_PSDCOMMENT
LOWdemo/common/filebrowser/stb_image.h581#define STBI_NO_ZLIBCOMMENT
LOWdemo/common/filebrowser/stb_image.h601#define STBI_ASSERT(x) assert(x)COMMENT
LOWdemo/common/filebrowser/stb_image.h621#ifndef STBI_NO_THREAD_LOCALSCOMMENT
LOWdemo/common/filebrowser/stb_image.h661#ifdef _MSC_VERCOMMENT
LOWdemo/common/filebrowser/stb_image.h681#define STBI_REALLOC(p,newsz) realloc(p,newsz)COMMENT
LOWdemo/common/filebrowser/stb_image.h701// exposed in GCC/Clang is, sadly, not really suited for one-file libs.COMMENT
LOWdemo/common/filebrowser/stb_image.h761COMMENT
LOWdemo/common/filebrowser/stb_image.h781#include <arm_neon.h>COMMENT
LOWdemo/common/filebrowser/stb_image.h981#endifCOMMENT
LOWdemo/common/filebrowser/stb_image.h1081 return a >= SHRT_MIN / b;COMMENT
LOWdemo/common/filebrowser/stb_image.h1141COMMENT
167 more matches not shown…
Decorative Section Separators3 hits · 9 pts
SeverityFileLineSnippetContext
MEDIUMsrc/build.py80# ==========COMMENT
MEDIUMsrc/build.py95# ----------COMMENT
MEDIUMsrc/build.py131# -------------------------COMMENT
Slop Phrases1 hit · 2 pts
SeverityFileLineSnippetContext
LOWsrc/nuklear_vertex.c234 * and don't forget to specify the new element size in your drawingCOMMENT
Deep Nesting1 hit · 1 pts
SeverityFileLineSnippetContext
LOWsrc/build.py33CODE