Repository Analysis

Immediate-Mode-UI/Nuklear

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

2.4 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of Immediate-Mode-UI/Nuklear, a C project with 11,258 GitHub stars. SynthScan v2.0 examined 89,143 lines of code across 139 source files, recording 229 pattern matches distributed across 4 syntactic categories. The overall adjusted score of 2.4 places this repository in the Likely human-written band.

The scanner applied 160+ deterministic lexical heuristics, multi-line block detectors, abstract syntax tree depth profilers, and a cross-file Jaccard similarity matrix to construct a statistically normalised synthetic code estimate. All matches are individually weighted by severity coefficient and contextual multiplier before summation, and the resulting headline score is temporally discounted to account for the repository's development history relative to the commercial emergence of large language model coding tooling (November 2022 onward).

2.4
Adjusted Score
2.4
Raw Score
100%
Time Factor
2026-07-08
Last Push
11.3K
Stars
C
Language
89.1K
Lines of Code
139
Files
229
Pattern Hits
2026-07-14
Scan Date
0.00
HC Hit Rate

What These Metrics Mean

Adjusted Score
Primary synthetic code indicator. Raw score normalised per 1,000 lines of code and multiplied by the temporal discount factor. This is the definitive comparative metric — use it to rank repositories by AI authorship density.
Raw Score
The unmodified sum of all severity-weighted, context-multiplied pattern match scores before temporal discounting. Reflects the absolute signal strength independent of when the repository was last active.
Time Factor
The temporal discount multiplier (0–100%) applied to the raw score. Repositories last updated before ChatGPT's launch (Nov 2022) receive a 5% factor. Full signal is only assigned to repositories active in the post-adoption era (Jan 2024+).
Pattern Hits
Total count of individual pattern matches across all files and categories. A high hit count with a low score may indicate a very large codebase with isolated AI snippets; a low count with a high score indicates dense, concentrated AI signatures.
HC Hit Rate
High+Critical pattern hits per file, averaged across the repository. This orthogonal signal catches repositories where a few files are densely packed with high-severity AI tells — a strong indicator even when the normalised score appears moderate due to codebase size.
Lines of Code / Files
Total lines and files analysed. The scanner examines 94 file extensions. These denominators are used to normalise the score, enabling fair comparison between repositories of vastly different sizes.

Score History

This chart maps the temporal evolution of the adjusted synthetic code score across successive scan runs. An upward trajectory indicates ongoing incorporation of AI-generated code or expanding LLM-assisted scaffolding; a stable or declining trajectory may reflect active human refactoring, code removal, or the adoption of stricter authorship policies. The dashed secondary line (right axis) independently tracks total raw pattern hit count, which can diverge from the normalised score when codebase size changes significantly between scans.

Severity Breakdown

Classifies detected patterns by their diagnostic confidence and structural impact. CRITICAL patterns (coefficient 10) represent definitive synthetic signatures — hallucinated imports, explicit LLM attribution metadata — virtually never produced by human authors. HIGH (5) indicates strong structural tells such as cross-file repetition or cross-linguistic idioms. MEDIUM (2) covers recognisable conversational padding and AI-specific vocabulary. LOW (1) captures subtle indicators like tautological comments and generic boilerplate that require density to carry independent signal.

CRITICAL 0HIGH 0MEDIUM 3LOW 226

Directory Score Breakdown

This horizontal bar chart decomposes the repository's raw synthetic code score by top-level directory, allowing you to pinpoint precisely which modules or components carry the highest AI authorship density. Directories with disproportionately high scores relative to their size warrant targeted manual review: concentrated AI signatures often trace back to mass-generated configuration layers, auto-ported test suites, LLM-scaffolded boilerplate classes, or entire subsystems authored under heavy copilot assistance. Use this view to prioritise your human code-review effort.

Pattern Findings

The scanner identified 229 distinct pattern matches across 4 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a statistically significant AI authorship indicator. 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 diagnostic confidence level (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — comment-context matches receive a ×1.5 weight because LLMs systematically over-annotate. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier as dense clusters constitute far stronger evidence of synthetic authorship than isolated hits.

Over-Commented Block224 hits · 204 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/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
LOWdemo/common/filebrowser/stb_image.h1161COMMENT
LOWdemo/common/filebrowser/stb_image.h1721{COMMENT
LOWdemo/common/filebrowser/stb_image.h1901 if (z > 255) z = 255;COMMENT
164 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