Repository Analysis

skeeto/w64devkit

Portable C and C++ Development Kit for x64 (and x86) Windows

3.9 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of skeeto/w64devkit, a C++ project with 4,619 GitHub stars. SynthScan v2.0 examined 20,311 lines of code across 23 source files, recording 53 pattern matches distributed across 5 syntactic categories. The overall adjusted score of 3.9 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.9
Adjusted Score
3.9
Raw Score
100%
Time Factor
2026-07-11
Last Push
4.6K
Stars
C++
Language
20.3K
Lines of Code
23
Files
53
Pattern Hits
2026-07-14
Scan Date
0.04
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

Longitudinal tracking requires multiple scan runs. Once this repository is re-scanned after new commits land, this chart will visualise how the synthetic code signal evolves over time — enabling you to detect whether AI authorship is growing, stabilising, or being actively corrected by human engineers.

No multi-scan history yet — run the scanner again to build trend data.

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 1MEDIUM 9LOW 43

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 53 distinct pattern matches across 5 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 Separators9 hits · 27 pts
SeverityFileLineSnippetContext
MEDIUMsrc/quilt.cpp2621// ── Patch parsing data structures ──────────────────────────────────────COMMENT
MEDIUMsrc/quilt.cpp2643// ── Path stripping ─────────────────────────────────────────────────────COMMENT
MEDIUMsrc/quilt.cpp2682// ── Unified diff parser ────────────────────────────────────────────────COMMENT
MEDIUMsrc/quilt.cpp2866// ── Line-based file representation ─────────────────────────────────────COMMENT
MEDIUMsrc/quilt.cpp2912// ── Hunk matching ──────────────────────────────────────────────────────COMMENT
MEDIUMsrc/quilt.cpp3068// ── Hunk application ───────────────────────────────────────────────────COMMENT
MEDIUMsrc/quilt.cpp3157// ── Merge conflict markers ─────────────────────────────────────────────COMMENT
MEDIUMsrc/quilt.cpp3300// ── Reject file generation ─────────────────────────────────────────────COMMENT
MEDIUMsrc/quilt.cpp3342// ── Main patch engine ──────────────────────────────────────────────────COMMENT
Over-Commented Block25 hits · 24 pts
SeverityFileLineSnippetContext
LOWcontrib/libgc.c1#if 0COMMENT
LOWcontrib/libgc.c41#define ALL_INTERIOR_POINTERSCOMMENT
LOWcontrib/libgc.c61#include "mallocx.c"COMMENT
LOWcontrib/libregex.c1#if 0COMMENT
LOWcontrib/libregex.c101#define MATCH_LIMIT_DEPTH MATCH_LIMITCOMMENT
LOWcontrib/libregex.c121COMMENT
LOWcontrib/gobuild/bootstrap-go-toolchain.sh1#!/bin/shCOMMENT
LOWsrc/pkg-config.c1// u-config: a small, simple, portable pkg-config cloneCOMMENT
LOWsrc/pkg-config.c2261// field splitting semantics identical to CommandLineToArgvW, includingCOMMENT
LOWsrc/pkg-config.c2861 b32 *err = &ctx->handles[fd].err;COMMENT
LOWsrc/recycle.c1// recycle: send files and folders to the recycle bin without confirmationCOMMENT
LOWsrc/debugbreak.c1// debugbreak - raise a breakpoint exception in all Win32 debuggeesCOMMENT
LOWsrc/rexxd.c1// rexxd: replacement xxd (for w64devkit)COMMENT
LOWsrc/rexxd.c21// * "xxd -r" autodetects input "-c" configurationCOMMENT
LOWsrc/rexxd.c1741#if NO_PLATFORMCOMMENT
LOWsrc/peports.c1// PE export/import table listingCOMMENT
LOWsrc/peports.c21// given arbitrary, untrusted input, its interpretation of PE data mayCOMMENT
LOWsrc/peports.c521 s8 idata = loadrva(map, idataoff, esc);COMMENT
LOWsrc/quilt.cpp1// quilt.cpp — single-file amalgamation (Windows platform)COMMENT
LOWsrc/quilt.cpp1501 final_argv.push_back(const_cast<char *>(s.c_str()));COMMENT
LOWsrc/quilt.cpp8821// Win32 platform implementation for quilt.COMMENT
LOWsrc/w64devkit.c1// Tiny, standalone launcher for w64devkitCOMMENT
LOWsrc/alias.c1// Well-behaved command line aliases for w64devkitCOMMENT
LOWsrc/sign-and-pack.sh1#!/bin/shCOMMENT
LOWsrc/uuidgen.c1// uuidgen: drop-in replacement for Microsoft uuidgen, for widlCOMMENT
Verbosity Indicators9 hits · 11 pts
SeverityFileLineSnippetContext
LOWsrc/quilt.cpp1779 // Step 1: Match common prefix and suffix.COMMENT
LOWsrc/quilt.cpp1801 // Step 2: Find unique common lines in the interior.COMMENT
LOWsrc/quilt.cpp1833 // Step 3: LIS of new_idx values via patience sorting.COMMENT
LOWsrc/quilt.cpp1898 // Step 4: Recurse on gaps between anchors.COMMENT
LOWsrc/quilt.cpp1988 // Step 1: Match common prefix and suffix.COMMENT
LOWsrc/quilt.cpp2030 // Step 2: Build histogram of old interior lines.COMMENT
LOWsrc/quilt.cpp2050 // Step 3: Scan new interior lines to find the best contiguous matching block.COMMENT
LOWsrc/quilt.cpp2116 // Step 4: If no block found, fall back to Myers (minimal).COMMENT
LOWsrc/quilt.cpp2137 // Step 5: Recurse on regions before and after the matching block.COMMENT
Structural Annotation Overuse9 hits · 10 pts
SeverityFileLineSnippetContext
LOWsrc/quilt.cpp1779 // Step 1: Match common prefix and suffix.COMMENT
LOWsrc/quilt.cpp1801 // Step 2: Find unique common lines in the interior.COMMENT
LOWsrc/quilt.cpp1833 // Step 3: LIS of new_idx values via patience sorting.COMMENT
LOWsrc/quilt.cpp1898 // Step 4: Recurse on gaps between anchors.COMMENT
LOWsrc/quilt.cpp1988 // Step 1: Match common prefix and suffix.COMMENT
LOWsrc/quilt.cpp2030 // Step 2: Build histogram of old interior lines.COMMENT
LOWsrc/quilt.cpp2050 // Step 3: Scan new interior lines to find the best contiguous matching block.COMMENT
LOWsrc/quilt.cpp2116 // Step 4: If no block found, fall back to Myers (minimal).COMMENT
LOWsrc/quilt.cpp2137 // Step 5: Recurse on regions before and after the matching block.COMMENT
Synthetic Comment Markers1 hit · 8 pts
SeverityFileLineSnippetContext
HIGHsrc/rexxd.c1458 // NOTE: Prints the name exactly as requested, no filteringCOMMENT