Repository Analysis

cilium/pwru

Packet, where are you? -- eBPF-based Linux kernel networking debugger

3.5 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of cilium/pwru, a C project with 3,783 GitHub stars. SynthScan v2.0 examined 104,617 lines of code across 240 source files, recording 317 pattern matches distributed across 3 syntactic categories. The overall adjusted score of 3.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).

3.5
Adjusted Score
3.5
Raw Score
100%
Time Factor
2026-07-13
Last Push
3.8K
Stars
C
Language
104.6K
Lines of Code
240
Files
317
Pattern Hits
2026-07-14
Scan Date
0.05
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 12MEDIUM 0LOW 305

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 317 distinct pattern matches across 3 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 Block305 hits · 274 pts
SeverityFileLineSnippetContext
LOWbpf/kprobe_pwru.c1// SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)COMMENT
LOWbpf/headers/vmlinux.h1#if defined(__TARGET_ARCH_x86)COMMENT
LOWbpf/headers/bpf/bpf_endian.h41 *COMMENT
LOWbpf/headers/bpf/bpf_endian.h61# define __bpf_constant_be64_to_cpu(x) ___bpf_swab64(x)COMMENT
LOWbpf/headers/bpf/bpf_ipv6.h1#include "vmlinux.h"COMMENT
LOWbpf/headers/bpf/bpf_core_read.h361#define ___last6(a, b, c, d, e, x) xCOMMENT
LOWbpf/headers/bpf/bpf_core_read.h381#define ___arrow3(a, b, c) a->b->cCOMMENT
LOWbpf/headers/bpf/bpf_core_read.h401#define ___rd_p2(fn, ...) ___rd_p1(fn, ___nolast(__VA_ARGS__)) ___rd_last(fn, __VA_ARGS__)COMMENT
LOWbpf/headers/bpf/bpf_helpers.h181};COMMENT
LOWbpf/headers/bpf/bpf_helpers.h201})COMMENT
LOWbpf/headers/bpf/bpf_helpers.h221#ifndef ___bpf_nargCOMMENT
LOWbpf/headers/bpf/bpf_tracing.h1/* SPDX-License-Identifier: (LGPL-2.1 OR BSD-2-Clause) */COMMENT
LOWbpf/headers/bpf/bpf_tracing.h21 #define bpf_target_mipsCOMMENT
LOWbpf/headers/bpf/bpf_tracing.h41#if defined(__x86_64__)COMMENT
LOWbpf/headers/bpf/bpf_tracing.h61 #define bpf_target_definedCOMMENT
LOWbpf/headers/bpf/bpf_tracing.h81/*COMMENT
LOWbpf/headers/bpf/bpf_tracing.h101#define __PT_PARM5_SYSCALL_REG __PT_PARM5_REGCOMMENT
LOWbpf/headers/bpf/bpf_tracing.h121#define __PT_PARM3_SYSCALL_REG edxCOMMENT
LOWbpf/headers/bpf/bpf_tracing.h141#define __PT_PARM1_SYSCALL_REG __PT_PARM1_REGCOMMENT
LOWbpf/headers/bpf/bpf_tracing.h161 * https://github.com/IBM/s390x-abi/releases/download/v1.6/lzsabi_s390x.pdfCOMMENT
LOWbpf/headers/bpf/bpf_tracing.h181#define __PT_PARM6_SYSCALL_REG gprs[7]COMMENT
LOWbpf/headers/bpf/bpf_tracing.h201#define __PT_PARM4_REG uregs[3]COMMENT
LOWbpf/headers/bpf/bpf_tracing.h221 */COMMENT
LOWbpf/headers/bpf/bpf_tracing.h241#define __PT_PARM4_SYSCALL_REG __PT_PARM4_REGCOMMENT
LOWbpf/headers/bpf/bpf_tracing.h261#define __PT_PARM1_REG regs[4]COMMENT
LOWbpf/headers/bpf/bpf_tracing.h281#define __PT_IP_REG cp0_epcCOMMENT
LOWbpf/headers/bpf/bpf_tracing.h301#define __PT_PARM1_SYSCALL_REG orig_gpr3COMMENT
LOWbpf/headers/bpf/bpf_tracing.h321 */COMMENT
LOWbpf/headers/bpf/bpf_tracing.h361#define __PT_PARM2_REG a1COMMENT
LOWbpf/headers/bpf/bpf_tracing.h381#define __PT_RC_REG a0COMMENT
LOWbpf/headers/bpf/bpf_tracing.h401#define __PT_PARM8_REG scratch.r7COMMENT
LOWbpf/headers/bpf/bpf_tracing.h421 * https://docs.kernel.org/loongarch/introduction.htmlCOMMENT
LOWbpf/headers/bpf/bpf_tracing.h441#define __PT_PARM4_SYSCALL_REG __PT_PARM4_REGCOMMENT
LOWbpf/headers/bpf/bpf_tracing.h461COMMENT
LOWbpf/headers/bpf/bpf_tracing.h481/*COMMENT
LOWbpf/headers/bpf/bpf_tracing.h501#define PT_REGS_FP(x) (__PT_REGS_CAST(x)->__PT_FP_REG)COMMENT
LOWbpf/headers/bpf/bpf_tracing.h521COMMENT
LOWbpf/headers/bpf/bpf_tracing.h541#define PT_REGS_PARM1_CORE_SYSCALL(x) BPF_CORE_READ(__PT_REGS_CAST(x), __PT_PARM1_SYSCALL_REG)COMMENT
LOWbpf/headers/bpf/bpf_tracing.h561#define PT_REGS_PARM6_CORE_SYSCALL(x) BPF_CORE_READ(__PT_REGS_CAST(x), __PT_PARM6_SYSCALL_REG)COMMENT
LOWbpf/headers/bpf/bpf_tracing.h581#define PT_REGS_SP(x) ({ _Pragma(__BPF_TARGET_MISSING); 0l; })COMMENT
LOWbpf/headers/bpf/bpf_tracing.h601#define PT_REGS_PARM1_SYSCALL(x) ({ _Pragma(__BPF_TARGET_MISSING); 0l; })COMMENT
LOWbpf/headers/bpf/bpf_tracing.h621 * struct pt_regs containing syscall arguments and suitable for passing toCOMMENT
LOWbpf/headers/bpf/bpf_tracing.h641COMMENT
LOWbpf/headers/bpf/bpf_tracing.h701 __builtin_choose_expr(sizeof(t) == 16, 2, \COMMENT
LOWbpf/headers/bpf/bpf_tracing.h721 __builtin_choose_expr(sizeof(t) == 2, ({ union { __u16 z[1]; t x; } ___t = { .z = {ctx[n]} }; ___t.x; }), \COMMENT
LOWbpf/headers/bpf/bpf_tracing.h741COMMENT
LOWbpf/headers/bpf/bpf_tracing.h861#define ___bpf_syscall_args7(x, args...) ___bpf_syscall_args6(args), (unsigned long long)PT_REGS_PARM7_SYSCALL(regs)COMMENT
LOWlibpcap/build_matrix.sh1#!/bin/sh -eCOMMENT
LOWlibpcap/savefile.c41#include <errno.h>COMMENT
LOWlibpcap/sf-pcapng.c21 * sf-pcapng.c - pcapng-file-format-specific code from savefile.cCOMMENT
LOWlibpcap/sf-pcapng.c121};COMMENT
LOWlibpcap/pcap-dos.c1/*COMMENT
LOWlibpcap/pcap-dos.c21 #include "msdos/pm_drvr/bios32.h"COMMENT
LOWlibpcap/pcap-dos.c41#include "msdos/pktdrvr.h"COMMENT
LOWlibpcap/nlpid.h21/*COMMENT
LOWlibpcap/nlpid.h41#define ISIS_L1_LAN_IIH 15COMMENT
LOWlibpcap/pcap-sita.c21 *COMMENT
LOWlibpcap/sf-pcap.c41#include <errno.h>COMMENT
LOWlibpcap/CMakeLists.txt21# WE KNOW WHAT WE'RE DOING, WE'RE DOING EVERYTHING THE WAY THAT NEWERCOMMENT
LOWlibpcap/CMakeLists.txt41# infiniband/verbs.h for the reason.COMMENT
245 more matches not shown…
Synthetic Comment Markers6 hits · 68 pts
SeverityFileLineSnippetContext
HIGHlibpcap/pcap-common.c607 * FlexRay automotive bus - http://www.flexray.com/ - as requestedCOMMENT
HIGHlibpcap/pcap-common.c614 * transport - https://www.mostcooperation.com/ - as requestedCOMMENT
HIGHlibpcap/pcap-common.c621 * http://www.lin-subbus.org/ - as requested by Hannes KaelberCOMMENT
HIGHlibpcap/pcap/dlt.h933 * FlexRay automotive bus - http://www.flexray.com/ - as requestedCOMMENT
HIGHlibpcap/pcap/dlt.h940 * transport - https://www.mostcooperation.com/ - as requestedCOMMENT
HIGHlibpcap/pcap/dlt.h947 * http://www.lin-subbus.org/ - as requested by Hannes KaelberCOMMENT
Cross-Language Confusion6 hits · 30 pts
SeverityFileLineSnippetContext
HIGHlibpcap/testprogs/visopts.py65 var leftsvg = null;CODE
HIGHlibpcap/testprogs/visopts.py66 var rightsvg = null;CODE
HIGHlibpcap/testprogs/visopts.py121 if (doc == null) {CODE
HIGHlibpcap/testprogs/visopts.py134 if (doc == null) {CODE
HIGHlibpcap/testprogs/visopts.py150 leftsvg = null;CODE
HIGHlibpcap/testprogs/visopts.py159 rightsvg = null;CODE