Repository Analysis

LongSoft/UEFITool

UEFI firmware image viewer and editor

2.5 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of LongSoft/UEFITool, a C project with 5,569 GitHub stars. SynthScan v2.0 examined 117,184 lines of code across 292 source files, recording 296 pattern matches distributed across 3 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
5.6K
Stars
C
Language
117.2K
Lines of Code
292
Files
296
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 0LOW 296

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 296 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 Block290 hits · 288 pts
SeverityFileLineSnippetContext
LOWfuzzing/afl_driver.cpp41If 1, close stdout at startup. If 2 close stderr; if 3 close both.COMMENT
LOWfuzzing/afl_driver.cpp61#define LIBFUZZER_NETBSD 0COMMENT
LOWfuzzing/afl_driver.cpp81#define LIBFUZZER_OPENBSD 0COMMENT
LOWUEFITool/uefitool.h21#include <QDropEvent>COMMENT
LOWUEFITool/uefitool.h41COMMENT
LOWUEFITool/QHexView/include/QHexView/qhexview.h1#pragma onceCOMMENT
LOWUEFITool/QHexView/src/qhexview.cpp1#include <QApplication>COMMENT
LOWUEFITool/QHexView/src/model/qhexutils.cpp1#include "QHexView/model/qhexdocument.h"COMMENT
LOWUEFITool/QHexView/src/dialogs/hexfinddialog.cpp1#include <QCheckBox>COMMENT
LOWcommon/treemodel.h21COMMENT
LOWcommon/treemodel.h41#include "basetypes.h"COMMENT
LOWcommon/intel_fit.h21COMMENT
LOWcommon/intel_fit.h41//#define INTEL_FIT_TYPE_INTEL_RESERVED_0E 0x0ECOMMENT
LOWcommon/intel_fit.h81// Version must be 0x0100COMMENT
LOWcommon/intel_fit.h101// One MTRR base/limit pair is used to map Startup ACM, soCOMMENT
LOWcommon/intel_fit.h141//COMMENT
LOWcommon/ustring.h21#elseCOMMENT
LOWcommon/nvram.h41 UINT16 Size; // Size of the entry including headerCOMMENT
LOWcommon/nvram.h61#define NVRAM_NVAR_ENTRY_EXT_AUTH_WRITE 0x10COMMENT
LOWcommon/nvram.h141COMMENT
LOWcommon/nvram.h221// Apple System Flags storeCOMMENT
LOWcommon/nvram.h241//COMMENT
LOWcommon/nvram.h281COMMENT
LOWcommon/ffs.h141COMMENT
LOWcommon/ffs.h161#define EFI_FVB_ALIGNMENT_4 0x00020000COMMENT
LOWcommon/ffs.h181#define EFI_FVB2_WRITE_ENABLED_CAP 0x00000010COMMENT
LOWcommon/ffs.h201#define EFI_FVB2_ALIGNMENT_256 0x00080000COMMENT
LOWcommon/ffs.h301// Standard data checksum, used if FFS_ATTRIB_CHECKSUM is clearCOMMENT
LOWcommon/ffs.h321#define EFI_FV_FILETYPE_MM_CORE_STANDALONE 0x0FCOMMENT
LOWcommon/ffs.h341COMMENT
LOWcommon/ffs.h401// File section typesCOMMENT
LOWcommon/ffs.h521#define EFI_DEP_OPCODE_SIZE 1COMMENT
LOWcommon/ffs.h541#define EFI_DEP_END 0x08COMMENT
LOWcommon/ffs.h601 UINT32 UmaCacheable : 1;COMMENT
LOWcommon/ffs.h621#define BPDT_ENTRY_TYPE_UFS_GPP_LUN 13COMMENT
LOWcommon/ffs.h641#define BPDT_ENTRY_TYPE_ISIF 33COMMENT
LOWcommon/ffs.h721#define CPD_EXT_TYPE_INIT_SCRIPT 1COMMENT
LOWcommon/ffs.h741#define CPD_EXT_TYPE_SECURE_TOKEN 21COMMENT
LOWcommon/ffs.h981 UINT8 NamespaceIdC;COMMENT
LOWcommon/descriptor.h21#pragma pack(push,1)COMMENT
LOWcommon/descriptor.h341 // PLATFORM_STONEYRIDGE 15h (60-6fh) 10220B00hCOMMENT
LOWcommon/basetypes.h21// TODO: improveCOMMENT
LOWcommon/basetypes.h41#define U_UNKNOWN_FFS 18COMMENT
LOWcommon/basetypes.h61#define U_INVALID_CAPSULE 38COMMENT
LOWcommon/basetypes.h101typedef size_t UINTN;COMMENT
LOWcommon/basetypes.h121#define OUTCOMMENT
LOWcommon/basetypes.h141#define COMPRESSION_ALGORITHM_BROTLI 10COMMENT
LOWcommon/basetypes.h161COMMENT
LOWcommon/basetypes.h201#define ALIGN4(Value) (((Value)+3) & ~3)COMMENT
LOWcommon/basetypes.h221#define TCG_HASH_ALGORITHM_ID_SHA384 0x000CCOMMENT
LOWcommon/peimage.h21COMMENT
LOWcommon/peimage.h41#define EFI_IMAGE_FILE_MACHINE_ARMNT 0x01c4 // ARMv7 (or higher) Thumb mode onlyCOMMENT
LOWcommon/peimage.h101// Size of EFI_IMAGE_FILE_HEADER.COMMENT
LOWcommon/peimage.h121//COMMENT
LOWcommon/peimage.h141COMMENT
LOWcommon/peimage.h261#define EFI_IMAGE_SUBSYSTEM_WINDOWS_GUI 2COMMENT
LOWcommon/peimage.h301#define EFI_IMAGE_SCN_CNT_UNINITIALIZED_DATA 0x00000080COMMENT
LOWcommon/peimage.h321#define EFI_IMAGE_SCN_MEM_READ 0x40000000COMMENT
LOWcommon/peimage.h341#define EFI_IMAGE_SYM_TYPE_VOID 1 // no valid typeCOMMENT
LOWcommon/peimage.h361#define EFI_IMAGE_SYM_DTYPE_POINTER 1COMMENT
230 more matches not shown…
Verbosity Indicators3 hits · 4 pts
SeverityFileLineSnippetContext
LOWcommon/kaitai/kaitaistream.cpp1124 // Step 1: convert encoding name to codepage numberCOMMENT
LOWcommon/kaitai/kaitaistream.cpp1144 // Step 2: convert bytes to UTF-16 ("wide char") stringCOMMENT
LOWcommon/kaitai/kaitaistream.cpp1198 // Step 3: convert UTF-16 string to UTF-8 stringCOMMENT
Structural Annotation Overuse3 hits · 4 pts
SeverityFileLineSnippetContext
LOWcommon/kaitai/kaitaistream.cpp1124 // Step 1: convert encoding name to codepage numberCOMMENT
LOWcommon/kaitai/kaitaistream.cpp1144 // Step 2: convert bytes to UTF-16 ("wide char") stringCOMMENT
LOWcommon/kaitai/kaitaistream.cpp1198 // Step 3: convert UTF-16 string to UTF-8 stringCOMMENT