Repository Analysis

Novum/vkQuake

Vulkan Quake port based on QuakeSpasm

3.1 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of Novum/vkQuake, a C project with 2,211 GitHub stars. SynthScan v2.0 examined 290,027 lines of code across 403 source files, recording 1206 pattern matches distributed across 4 syntactic categories. The overall adjusted score of 3.1 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).

3.1
Adjusted Score
3.1
Raw Score
100%
Time Factor
2026-07-14
Last Push
2.2K
Stars
C
Language
290.0K
Lines of Code
403
Files
1.2K
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 1LOW 1205

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 1206 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 Block1199 hits · 879 pts
SeverityFileLineSnippetContext
LOWQuake/q_stdinc.h61#include "msinttypes/stdint.h"COMMENT
LOWQuake/q_stdinc.h161#define PATH_MAX MAXPATHLENCOMMENT
LOWQuake/q_stdinc.h181COMMENT
LOWQuake/q_stdinc.h201#elif defined(__GNUC__) && (__GNUC__ > 4 || (__GNUC__ == 4 && __GNUC_MINOR__ > 3))COMMENT
LOWQuake/q_stdinc.h221#endifCOMMENT
LOWQuake/q_stdinc.h241#endifCOMMENT
LOWQuake/lodepng.h101#define LODEPNG_COMPILE_CRCCOMMENT
LOWQuake/protocol.h21*/COMMENT
LOWQuake/protocol.h41#define PRFL_EDICTSCALE (1 << 5)COMMENT
LOWQuake/protocol.h61#define U_ORIGIN1 (1 << 1)COMMENT
LOWQuake/protocol.h81#define U_MODEL2 (1 << 18) // 1 byte, this is .modelindex & 0xFF00 (second byte)COMMENT
LOWQuake/protocol.h101#define UF_PREDINFO (1u << 6) /*ent is predicted, probably a player*/COMMENT
LOWQuake/protocol.h121#define UF_TRAILEFFECT (1u << 22) /*attaches custom particle trails to entities, woo.*/COMMENT
LOWQuake/protocol.h141#define UFP_WEAPONFRAME_OLD (1u << 7) // no longer used. just a stat now that I rewrote stat deltas.COMMENT
LOWQuake/protocol.h161#define SU_EXTEND1 (1 << 15) // another byte to followCOMMENT
LOWQuake/protocol.h181// spikeCOMMENT
LOWQuake/protocol.h201// spikeCOMMENT
LOWQuake/protocol.h221COMMENT
LOWQuake/protocol.h241#define svc_updatestat 3 // [byte] [long]COMMENT
LOWQuake/protocol.h261#define svc_updatecolors 17 // [byte] [byte]COMMENT
LOWQuake/protocol.h281// johnfitz -- PROTOCOL_FITZQUAKE -- new server messagesCOMMENT
LOWQuake/protocol.h301#define svc_achievement 52 // [string] idCOMMENT
LOWQuake/protocol.h321#define svcdp_entities 57COMMENT
LOWQuake/protocol.h341#define clc_disconnect 2COMMENT
LOWQuake/common.c21*/COMMENT
LOWQuake/bspfile.h21*/COMMENT
LOWQuake/bspfile.h41#define MAX_MAP_MARKSURFACES 65535COMMENT
LOWQuake/bspfile.h81COMMENT
LOWQuake/bspfile.h161#define CONTENTS_SOLID -2COMMENT
LOWQuake/glquake.h41// r_local.h -- private refresh defsCOMMENT
LOWQuake/glquake.h181} vulkan_memory_type_t;COMMENT
LOWQuake/miniz.c3121#define MZ_FOPEN mz_fopenCOMMENT
LOWQuake/miniz.c3141#endifCOMMENT
LOWQuake/miniz.c3161#define MZ_FWRITE fwriteCOMMENT
LOWQuake/miniz.c3181#define MZ_FILE_STAT stat64COMMENT
LOWQuake/miniz.c3201COMMENT
LOWQuake/net.h81// returns 2 if an unreliable message was receivedCOMMENT
LOWQuake/snd_mpg123.c21COMMENT
LOWQuake/quakever.h21#ifndef QUAKEVER_HCOMMENT
LOWQuake/quakever.h41#define VKQUAKE_VERSION 1.35COMMENT
LOWQuake/stb_image_write.h161#ifndef _CRT_NONSTDC_NO_DEPRECATECOMMENT
LOWQuake/stb_image_write.h181#endifCOMMENT
LOWQuake/stb_image_resize.h201#ifdef STB_IMAGE_RESIZE_STATICCOMMENT
LOWQuake/stb_image_resize.h221// * colorspace is linear or sRGB as specified by function nameCOMMENT
LOWQuake/stb_image_resize.h261 STBIR_EDGE_REFLECT = 2,COMMENT
LOWQuake/stb_image_resize.h321//////////////////////////////////////////////////////////////////////////////COMMENT
LOWQuake/stb_image_resize.h361//COMMENT
LOWQuake/stb_image_resize.h381#define STBIR_MALLOC(size, c) ((void)(c), malloc (size))COMMENT
LOWQuake/stb_image_resize.h401#define STBIR__NOTUSED(v) (void)sizeof (v)COMMENT
LOWQuake/stb_image_resize.h421COMMENT
LOWQuake/snd_codec.c21 * with this program; if not, write to the Free Software Foundation, Inc.,COMMENT
LOWQuake/mdfour.c61/* NOTE: This code makes no attempt to be fast!COMMENT
LOWQuake/sv_main.c161// #define UF_UNUSED UF_EXTEND2 /**/COMMENT
LOWQuake/sys_sdl_win.c21COMMENT
LOWQuake/cfgfile.h21COMMENT
LOWQuake/mem.c21COMMENT
LOWQuake/mem.c41#undef snprintfCOMMENT
LOWQuake/net_wins.c41#ifndef IPV6_V6ONLYCOMMENT
LOWQuake/tasks.h81COMMENT
LOWQuake/net_dgrm.c21COMMENT
1139 more matches not shown…
AI Slop Vocabulary2 hits · 4 pts
SeverityFileLineSnippetContext
MEDIUMQuake/mimalloc/prim/osx/alloc-override-zone.c403// it seems less robust than using interpose.COMMENT
LOWWindows/SDL3/include/SDL3/SDL_main_impl.h134 #else /* platforms that use a standard main() and just call SDL_RunApp(), like iOS and 3DS */COMMENT
Slop Phrases3 hits · 4 pts
SeverityFileLineSnippetContext
LOWQuake/pr_ext.c47// one funky way is to allocate a single large buffer and just concatenate it for more tempstring space. don't forget toCOMMENT
LOWQuake/lodepng.c72lodepng source code. Don't forget to remove "static" if you copypaste themCODE
LOWWindows/SDL3/include/SDL3/SDL_process.h39 * Don't forget to call SDL_DestroyProcess() to clean up, whether the processCOMMENT
TODO Padding2 hits · 3 pts
SeverityFileLineSnippetContext
LOWQuake/mimalloc/bitmap.c370 // TODO: implement mi_bchunk_xsetNX instead of setNXCOMMENT
LOWQuake/mimalloc/options.c619// TODO: implement ourselves to reduce dependencies on the C runtimeCOMMENT