Repository Analysis

nicbarker/clay

High performance UI layout library in C.

9.2 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of nicbarker/clay, a C project with 17,597 GitHub stars. SynthScan v2.0 examined 30,653 lines of code across 82 source files, recording 112 pattern matches distributed across 4 syntactic categories. The overall adjusted score of 9.2 places this repository in the Low AI signal 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).

9.2
Adjusted Score
9.2
Raw Score
100%
Time Factor
2026-05-20
Last Push
17.6K
Stars
C
Language
30.7K
Lines of Code
82
Files
112
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 48LOW 64

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 112 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.

Decorative Section Separators48 hits · 213 pts
SeverityFileLineSnippetContext
MEDIUMexamples/GLES3-SDL2-video-demo/CMakeLists.txt6# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-SDL2-video-demo/CMakeLists.txt8# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-SDL2-video-demo/CMakeLists.txt12# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-SDL2-video-demo/CMakeLists.txt14# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-SDL2-video-demo/CMakeLists.txt22# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-SDL2-video-demo/CMakeLists.txt24# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-SDL2-video-demo/CMakeLists.txt34# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-SDL2-video-demo/CMakeLists.txt36# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-SDL2-video-demo/CMakeLists.txt47# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-SDL2-video-demo/CMakeLists.txt49# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-SDL2-video-demo/CMakeLists.txt55# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-SDL2-video-demo/CMakeLists.txt57# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-SDL2-video-demo/CMakeLists.txt65# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-SDL2-video-demo/CMakeLists.txt67# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-SDL2-video-demo/CMakeLists.txt75# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-SDL2-video-demo/CMakeLists.txt77# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-GLFW-video-demo/CMakeLists.txt7# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-GLFW-video-demo/CMakeLists.txt9# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-GLFW-video-demo/CMakeLists.txt13# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-GLFW-video-demo/CMakeLists.txt15# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-GLFW-video-demo/CMakeLists.txt23# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-GLFW-video-demo/CMakeLists.txt25# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-GLFW-video-demo/CMakeLists.txt39# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-GLFW-video-demo/CMakeLists.txt41# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-GLFW-video-demo/CMakeLists.txt53# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-GLFW-video-demo/CMakeLists.txt55# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-GLFW-video-demo/CMakeLists.txt61# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-GLFW-video-demo/CMakeLists.txt63# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-GLFW-video-demo/CMakeLists.txt81# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-GLFW-video-demo/CMakeLists.txt83# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-GLFW-video-demo/CMakeLists.txt90# -------------------------------------------------COMMENT
MEDIUMexamples/GLES3-GLFW-video-demo/CMakeLists.txt92# -------------------------------------------------COMMENT
MEDIUM…/GLES3-SDL2-sidebar-scrolling-container/CMakeLists.txt5# -------------------------------------------------COMMENT
MEDIUM…/GLES3-SDL2-sidebar-scrolling-container/CMakeLists.txt7# -------------------------------------------------COMMENT
MEDIUM…/GLES3-SDL2-sidebar-scrolling-container/CMakeLists.txt11# -------------------------------------------------COMMENT
MEDIUM…/GLES3-SDL2-sidebar-scrolling-container/CMakeLists.txt13# -------------------------------------------------COMMENT
MEDIUM…/GLES3-SDL2-sidebar-scrolling-container/CMakeLists.txt21# -------------------------------------------------COMMENT
MEDIUM…/GLES3-SDL2-sidebar-scrolling-container/CMakeLists.txt23# -------------------------------------------------COMMENT
MEDIUM…/GLES3-SDL2-sidebar-scrolling-container/CMakeLists.txt33# -------------------------------------------------COMMENT
MEDIUM…/GLES3-SDL2-sidebar-scrolling-container/CMakeLists.txt35# -------------------------------------------------COMMENT
MEDIUM…/GLES3-SDL2-sidebar-scrolling-container/CMakeLists.txt46# -------------------------------------------------COMMENT
MEDIUM…/GLES3-SDL2-sidebar-scrolling-container/CMakeLists.txt48# -------------------------------------------------COMMENT
MEDIUM…/GLES3-SDL2-sidebar-scrolling-container/CMakeLists.txt54# -------------------------------------------------COMMENT
MEDIUM…/GLES3-SDL2-sidebar-scrolling-container/CMakeLists.txt56# -------------------------------------------------COMMENT
MEDIUM…/GLES3-SDL2-sidebar-scrolling-container/CMakeLists.txt64# -------------------------------------------------COMMENT
MEDIUM…/GLES3-SDL2-sidebar-scrolling-container/CMakeLists.txt66# -------------------------------------------------COMMENT
MEDIUM…/GLES3-SDL2-sidebar-scrolling-container/CMakeLists.txt74# -------------------------------------------------COMMENT
MEDIUM…/GLES3-SDL2-sidebar-scrolling-container/CMakeLists.txt76# -------------------------------------------------COMMENT
Over-Commented Block42 hits · 42 pts
SeverityFileLineSnippetContext
LOWclay.h21#include <arm_neon.h>COMMENT
LOWclay.h41#endifCOMMENT
LOWclay.h81#define CLAY_SID(label) Clay__HashString(label, 0)COMMENT
LOWclay.h161COMMENT
LOWclay.h181COMMENT
LOWclay.h481COMMENT
LOWclay.h501 // CLAY_POINTER_CAPTURE_MODE_CAPTURE (default) - "Capture" the pointer event and don't allow events like hover and cCOMMENT
LOWclay.h661COMMENT
LOWclay.h801 // CLAY_RENDER_COMMAND_TYPE_BORDER - The renderer should draw a colored border inset into the bounding box.COMMENT
LOWclay.h821typedef CLAY_PACKED_ENUM {COMMENT
LOWclay.h901typedef struct Clay_ErrorData {COMMENT
LOWclay.h921typedef struct {COMMENT
LOWclay.h941CLAY_DLL_EXPORT void Clay_SetPointerState(Clay_Vector2 position, bool pointerDown);COMMENT
LOWclay.h961CLAY_DLL_EXPORT Clay_Vector2 Clay_GetScrollOffset(void);COMMENT
LOWclay.h981// The returned Clay_ElementData contains a `found` bool that will be true if an element with the provided ID was found.COMMENT
LOWclay.h1001// Binds a callback function that Clay will call to determine the dimensions of a given string slice.COMMENT
LOWclay.h1041CLAY_DLL_EXPORT void Clay__OpenTextElement(Clay_String text, Clay_TextElementConfig textConfig);COMMENT
LOWrenderers/GLES3/clay_renderer_gles3.h1#ifndef CLAY_RENDERER_GLES3_HCOMMENT
LOWrenderers/GLES3/clay_renderer_gles3.h821#endifCOMMENT
LOWrenderers/cairo/clay_renderer_cairo.c1// Copyright (c) 2024 Justin Andreas Lacoste (@27justin)COMMENT
LOWrenderers/cairo/clay_renderer_cairo.c21//COMMENT
LOWrenderers/cairo/clay_renderer_cairo.c41void Clay_Cairo_Initialize(cairo_t *cairo);COMMENT
LOWrenderers/raylib/raymath.h61// Function specifiers definitionCOMMENT
LOWrenderers/raylib/raymath.h81COMMENT
LOWrenderers/raylib/raymath.h101COMMENT
LOWrenderers/raylib/raylib.h81* 3. This notice may not be removed or altered from any source distribution.COMMENT
LOWrenderers/raylib/raylib.h101 #endifCOMMENT
LOWrenderers/raylib/raylib.h121 #define PI 3.14159265358979323846fCOMMENT
LOWrenderers/raylib/raylib.h141#ifndef RL_FREECOMMENT
LOWrenderers/raylib/raylib.h161// NOTE: We set some defines with some data types declared by raylibCOMMENT
LOWrenderers/raylib/raylib.h181#define PINK CLITERAL(Color){ 255, 109, 194, 255 } // PinkCOMMENT
LOWrenderers/raylib/raylib.h201#define RAYWHITE CLITERAL(Color){ 245, 245, 245, 255 } // My own White (raylib logo)COMMENT
LOWrenderers/win32_gdi/clay_renderer_gdi.c1#include <Windows.h>COMMENT
LOWrenderers/sokol/sokol_clay.h141#endif /* SOKOL_CLAY_INCLUDED */COMMENT
LOWrenderers/SDL2/clay_renderer_SDL2.c141 indices[indexCount++] = vertexCount - 1; //LTCOMMENT
LOWexamples/sokol-corner-radius/main.c1#include "sokol_app.h"COMMENT
LOW…es/playdate-project-example/clay-video-demo-playdate.c1// This is the video demo with some adjustments so it works on the playdateCOMMENT
LOWexamples/cairo-pdf-rendering/main.c1// Copyright (c) 2024 Justin Andreas Lacoste (@27justin)COMMENT
LOWexamples/win32_gdi/main.c1COMMENT
LOWexamples/sokol-video-demo/main.c1#include "sokol_app.h"COMMENT
LOWexamples/sokol-video-demo/sokol.c1#define SOKOL_IMPLCOMMENT
LOWexamples/sokol-video-demo/sokol.c21#define FONTSTASH_IMPLEMENTATIONCOMMENT
Fake / Example Data21 hits · 26 pts
SeverityFileLineSnippetContext
LOWexamples/shared-layouts/clay-video-demo.c81 documents.documents[1] = (Document){ .title = CLAY_STRING("Lorem Ipsum"), .contents = CLAY_STRING("Lorem ipsum dolorCODE
LOWexamples/shared-layouts/clay-video-demo.c81 documents.documents[1] = (Document){ .title = CLAY_STRING("Lorem Ipsum"), .contents = CLAY_STRING("Lorem ipsum dolorCODE
LOWexamples/raylib-sidebar-scrolling-container/main.c80 CLAY_TEXT(CLAY_STRING("Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor iCODE
LOWexamples/raylib-sidebar-scrolling-container/main.c80 CLAY_TEXT(CLAY_STRING("Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor iCODE
LOWexamples/raylib-sidebar-scrolling-container/main.c104 CLAY_TEXT(CLAY_STRING("Amet cursus sit amet dictum sit amet justo donec. Et malesuada fames ac turpis eCODE
LOWexamples/raylib-sidebar-scrolling-container/main.c104 CLAY_TEXT(CLAY_STRING("Amet cursus sit amet dictum sit amet justo donec. Et malesuada fames ac turpis eCODE
LOWexamples/raylib-multi-context/main.c36 { .title = CLAY_STRING("Lorem Ipsum"), .contents = CLAY_STRING("Lorem ipsum dolor sit amet, consectetur adipCODE
LOWexamples/raylib-multi-context/main.c36 { .title = CLAY_STRING("Lorem Ipsum"), .contents = CLAY_STRING("Lorem ipsum dolor sit amet, consectetur adipCODE
LOW…es/playdate-project-example/clay-video-demo-playdate.c133 .title = CLAY_STRING("Lorem Ipsum"),CODE
LOW…es/playdate-project-example/clay-video-demo-playdate.c136 "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do "CODE
LOW…es/playdate-project-example/clay-video-demo-playdate.c136 "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do "CODE
LOWexamples/GLES3-SDL2-sidebar-scrolling-container/main.c335 CLAY_STRING("Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididuCODE
LOWexamples/GLES3-SDL2-sidebar-scrolling-container/main.c335 CLAY_STRING("Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididuCODE
LOWexamples/GLES3-SDL2-sidebar-scrolling-container/main.c339 CLAY_STRING("Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididuCODE
LOWexamples/GLES3-SDL2-sidebar-scrolling-container/main.c339 CLAY_STRING("Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididuCODE
LOWexamples/GLES3-SDL2-sidebar-scrolling-container/main.c342 CLAY_TEXT(CLAY_STRING("Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor inCODE
LOWexamples/GLES3-SDL2-sidebar-scrolling-container/main.c342 CLAY_TEXT(CLAY_STRING("Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor inCODE
LOWexamples/GLES3-SDL2-sidebar-scrolling-container/main.c376 CLAY_STRING("Amet cursus sit amet dictum sit amet justo donec. Et malesuada fames ac turpis egestas CODE
LOWexamples/GLES3-SDL2-sidebar-scrolling-container/main.c376 CLAY_STRING("Amet cursus sit amet dictum sit amet justo donec. Et malesuada fames ac turpis egestas CODE
LOWexamples/clay-official-website/main.c189Clay_String LOREM_IPSUM_TEXT = CLAY_STRING("Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempCODE
LOWexamples/clay-official-website/main.c189Clay_String LOREM_IPSUM_TEXT = CLAY_STRING("Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempCODE
Hyper-Verbose Identifiers1 hit · 1 pts
SeverityFileLineSnippetContext
LOWexamples/clay-official-website/index.html398 function SetElementBackgroundColorAndRadius(element, cornerRadius, backgroundColor) {CODE