Repository Analysis

libuv/libuv

Cross-platform asynchronous I/O

2.5 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of libuv/libuv, a C project with 26,996 GitHub stars. SynthScan v2.0 examined 116,464 lines of code across 390 source files, recording 399 pattern matches distributed across 4 syntactic categories. The overall adjusted score of 2.5 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.5
Adjusted Score
2.5
Raw Score
100%
Time Factor
2026-07-13
Last Push
27.0K
Stars
C
Language
116.5K
Lines of Code
390
Files
399
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 398

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 399 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 Block396 hits · 288 pts
SeverityFileLineSnippetContext
LOWautogen.sh1#!/bin/shCOMMENT
LOWtest/run-tests.c21COMMENT
LOWtest/task.h21COMMENT
LOWtest/task.h41# pragma clang diagnostic ignored "-Wc99-extensions"COMMENT
LOWtest/task.h61COMMENT
LOWtest/task.h221#define ASSERT_UINT64_LT(a, b) ASSERT_BASE(a, <, b, uint64_t, PRIu64)COMMENT
LOWtest/task.h421#if defined(__MSYS__)COMMENT
LOWtest/runner-win.c21COMMENT
LOWtest/test-pipe-getsockname.c21COMMENT
LOWtest/runner-unix.c21COMMENT
LOWtest/test-tty-escape-sequence-processing.c21COMMENT
LOWtest/test-tty-escape-sequence-processing.c41#define FOREGROUND_YELLOW (FOREGROUND_RED | FOREGROUND_GREEN)COMMENT
LOWtest/test-tty-escape-sequence-processing.c61#define F_YELLOW 33COMMENT
LOWtest/test-fs.c21COMMENT
LOWtest/test-fs.c41# ifndef REPARSE_DATA_BUFFER_HEADER_SIZECOMMENT
LOWtest/test-spawn.c21 */COMMENT
LOWtest/test-poll.c21COMMENT
LOWtest/test-tcp-writealot.c21COMMENT
LOWtest/test-tty.c21COMMENT
LOWtest/test-sizeof.c21COMMENT
LOWtest/test-sizeof.c41# define SIZEOF_UV_POLL_T 160COMMENT
LOWtest/test-sizeof.c61# define SIZEOF_UV_BUF_T 16COMMENT
LOWtest/test-sizeof.c81# define SIZEOF_UV_SEM_T 16COMMENT
LOWtest/test-sizeof.c101# define SIZEOF_UV_IDLE_T 120COMMENT
LOWtest/test-sizeof.c121# define SIZEOF_UV_TIMESPEC_T 16COMMENT
LOWtest/test-sizeof.c141# define SIZEOF_UV_BARRIER_T 32COMMENT
LOWtest/test-sizeof.c161# define SIZEOF_UV_FS_POLL_T 52COMMENT
LOWtest/test-sizeof.c181# define SIZEOF_UV_RUSAGE_T 128COMMENT
LOWtest/test-sizeof.c201# define SIZEOF_UV_LOOP_T 452COMMENT
LOWtest/test-sizeof.c221# define SIZEOF_UV_CONNECT_T 48COMMENT
LOWtest/test-sizeof.c241# define SIZEOF_UV_GROUP_T 12COMMENT
LOWtest/test-sizeof.c261COMMENT
LOWtest/test-sizeof.c281# define SIZEOF_UV_SHUTDOWN_T 80COMMENT
LOWtest/test-sizeof.c301# define SIZEOF_UV_DIRENT_T 16COMMENT
LOWtest/test-sizeof.c321# define SIZEOF_UV_HANDLE_T 48COMMENT
LOWtest/test-sizeof.c341# define SIZEOF_UV_FS_T 292COMMENT
LOWtest/test-sizeof.c361# define SIZEOF_UV_INTERFACE_ADDRESS_T 72COMMENT
LOWtest/test-sizeof.c381# define SIZEOF_UV_PIPE_T 264COMMENT
LOWtest/test-sizeof.c401# define SIZEOF_UV_RANDOM_T 144COMMENT
LOWtest/test-sizeof.c421# define SIZEOF_UV_MUTEX_T 48COMMENT
LOWtest/test-sizeof.c441# define SIZEOF_UV_PREPARE_T 120COMMENT
LOWtest/test-sizeof.c461# define SIZEOF_UV_STAT_T 160COMMENT
LOWtest/test-sizeof.c481# define SIZEOF_UV_ONCE_T 4COMMENT
LOWtest/test-sizeof.c501# define SIZEOF_UV_PROCESS_T 68COMMENT
LOWtest/test-sizeof.c521# define SIZEOF_UV_TIMEVAL_T 8COMMENT
LOWtest/test-sizeof.c541COMMENT
LOWtest/test-sizeof.c561# define SIZEOF_UV_IDLE_T 120COMMENT
LOWtest/test-sizeof.c581# define SIZEOF_UV_TIMESPEC_T 16COMMENT
LOWtest/test-sizeof.c601# define SIZEOF_UV_BARRIER_T 8COMMENT
LOWtest/test-sizeof.c621# define SIZEOF_UV_POLL_T 168COMMENT
LOWtest/test-sizeof.c641# define SIZEOF_UV_BUF_T 16COMMENT
LOWtest/test-sizeof.c661# define SIZEOF_UV_REQ_T 32COMMENT
LOWtest/test-sizeof.c681# define SIZEOF_UV_UDP_SEND_T 216COMMENT
LOWtest/test-sizeof.c701# define SIZEOF_UV_CPU_INFO_T 48COMMENT
LOWtest/test-sizeof.c721# define SIZEOF_UV_UDP_T 424COMMENT
LOWtest/test-sizeof.c741# define SIZEOF_UV_GETADDRINFO_T 216COMMENT
LOWtest/test-sizeof.c761# define SIZEOF_UV_UTSNAME_T 1024COMMENT
LOWtest/test-sizeof.c781# define SIZEOF_UV_TIMER_T 96COMMENT
LOWtest/test-sizeof.c801# define SIZEOF_UV_LIB_T 8COMMENT
LOWtest/test-sizeof.c821# define SIZEOF_UV_SEM_T 4COMMENT
336 more matches not shown…
Self-Referential Comments1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMdocs/src/conf.py6# This file is execfile()d with the current directory set to itsCOMMENT
Excessive Try-Catch Wrapping1 hit · 1 pts
SeverityFileLineSnippetContext
LOWdocs/src/conf.py35 except Exception:CODE
Unused Imports1 hit · 1 pts
SeverityFileLineSnippetContext
LOWdocs/src/sphinx-plugins/manpage.py13CODE