Repository Analysis

mattn/go-sqlite3

sqlite3 driver for go using database/sql

3.2 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of mattn/go-sqlite3, a C project with 9,176 GitHub stars. SynthScan v2.0 examined 30,839 lines of code across 92 source files, recording 100 pattern matches distributed across 1 syntactic category. The overall adjusted score of 3.2 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.2
Adjusted Score
3.2
Raw Score
100%
Time Factor
2026-07-13
Last Push
9.2K
Stars
C
Language
30.8K
Lines of Code
92
Files
100
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

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 0MEDIUM 0LOW 100

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 100 distinct pattern matches across 1 syntactic category. 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 Block100 hits · 100 pts
SeverityFileLineSnippetContext
LOWsqlite3_context.go1// Copyright (C) 2019 Yasuhiro Matsumoto <mattn.jp@gmail.com>.COMMENT
LOWsqlite3_opt_unlock_notify.c1// Copyright (C) 2018 Yasuhiro Matsumoto <mattn.jp@gmail.com>.COMMENT
LOWsqlite3_trace.go1// Copyright (C) 2019 Yasuhiro Matsumoto <mattn.jp@gmail.com>.COMMENT
LOWsqlite3_opt_allow_uri_authority.go1// Copyright (C) 2019 Yasuhiro Matsumoto <mattn.jp@gmail.com>.COMMENT
LOWsqlite3_stmt_cache_test.go1// Copyright (C) 2019 Yasuhiro Matsumoto <mattn.jp@gmail.com>.COMMENT
LOWcallback.go1// Copyright (C) 2019 Yasuhiro Matsumoto <mattn.jp@gmail.com>.COMMENT
LOWsqlite3_libsqlite3.go1// Copyright (C) 2019 Yasuhiro Matsumoto <mattn.jp@gmail.com>.COMMENT
LOWsqlite3_opt_icu.go1// Copyright (C) 2019 Yasuhiro Matsumoto <mattn.jp@gmail.com>.COMMENT
LOWsqlite3-binding.h81#ifndef SQLITE_APICALLCOMMENT
LOWsqlite3-binding.h461#define SQLITE_IOERR 10 /* Some kind of disk I/O error occurred */COMMENT
LOWsqlite3-binding.h501#define SQLITE_ERROR_MISSING_COLLSEQ (SQLITE_ERROR | (1<<8))COMMENT
LOWsqlite3-binding.h521#define SQLITE_IOERR_LOCK (SQLITE_IOERR | (15<<8))COMMENT
LOWsqlite3-binding.h541#define SQLITE_IOERR_BADKEY (SQLITE_IOERR | (35<<8))COMMENT
LOWsqlite3-binding.h561#define SQLITE_READONLY_CANTINIT (SQLITE_READONLY | (5<<8))COMMENT
LOWsqlite3-binding.h601** [sqlite3_open_v2()] has historically been a no-op and might become anCOMMENT
LOWsqlite3-binding.h1241** options are used to enable it.COMMENT
LOWsqlite3-binding.h1261#define SQLITE_FCNTL_TRACE 19COMMENT
LOWsqlite3-binding.h2221#define SQLITE_CONFIG_PAGECACHE 7 /* void*, int sz, int N */COMMENT
LOWsqlite3-binding.h2701#define SQLITE_DBCONFIG_LOOKASIDE 1001 /* void* int int */COMMENT
LOWsqlite3-binding.h3501** the access attempt or NULL if this access attempt is directly fromCOMMENT
LOWsqlite3-binding.h3521#define SQLITE_DROP_VIEW 17 /* View Name NULL */COMMENT
LOWsqlite3-binding.h4401** [[SQLITE_LIMIT_TRIGGER_DEPTH]] ^(<dt>SQLITE_LIMIT_TRIGGER_DEPTH</dt>COMMENT
LOWsqlite3-binding.h8581** prepared to accommodate additional static mutexes.COMMENT
LOWsqlite3-binding.h8681** These constants are the valid operation code parameters usedCOMMENT
LOWsqlite3-binding.h8701#define SQLITE_TESTCTRL_JSON_SELFCHECK 14COMMENT
LOWsqlite3-binding.h9201#define SQLITE_DBSTATUS_LOOKASIDE_HIT 4COMMENT
LOWsqlite3-binding.h11341*/COMMENT
LOWsqlite3-binding.h14341*************************************************************************/COMMENT
LOWsqlite3_opt_foreign_keys.go1// Copyright (C) 2019 Yasuhiro Matsumoto <mattn.jp@gmail.com>.COMMENT
LOWsqlite3_windows.go1// Copyright (C) 2019 Yasuhiro Matsumoto <mattn.jp@gmail.com>.COMMENT
LOWsqlite3_other.go1// Copyright (C) 2019 Yasuhiro Matsumoto <mattn.jp@gmail.com>.COMMENT
LOWsqlite3_opt_unlock_notify.go1// Copyright (C) 2019 Yasuhiro Matsumoto <mattn.jp@gmail.com>.COMMENT
LOWsqlite3_usleep_windows.go1// Copyright (C) 2018 G.J.R. Timmer <gjr.timmer@gmail.com>.COMMENT
LOWsqlite3_opt_secure_delete_fast.go1// Copyright (C) 2019 Yasuhiro Matsumoto <mattn.jp@gmail.com>.COMMENT
LOWsqlite3_opt_vacuum_full.go1// Copyright (C) 2019 Yasuhiro Matsumoto <mattn.jp@gmail.com>.COMMENT
LOWsqlite3_opt_preupdate_omit.go1// Copyright (C) 2019 G.J.R. Timmer <gjr.timmer@gmail.com>.COMMENT
LOWsqlite3_opt_secure_delete.go1// Copyright (C) 2019 Yasuhiro Matsumoto <mattn.jp@gmail.com>.COMMENT
LOWsqlite3_load_extension.go1// Copyright (C) 2019 Yasuhiro Matsumoto <mattn.jp@gmail.com>.COMMENT
LOWsqlite3_opt_app_armor.go1// Copyright (C) 2019 Yasuhiro Matsumoto <mattn.jp@gmail.com>.COMMENT
LOWsqlite3_opt_stat4.go1// Copyright (C) 2019 Yasuhiro Matsumoto <mattn.jp@gmail.com>.COMMENT
LOWsqlite3ext.h401** (part of the main SQLite library - not an extension) so thatCOMMENT
LOWsqlite3ext.h421#define sqlite3_bind_text16 sqlite3_api->bind_text16COMMENT
LOWsqlite3ext.h441#define sqlite3_column_name16 sqlite3_api->column_name16COMMENT
LOWsqlite3ext.h461#define sqlite3_declare_vtab sqlite3_api->declare_vtabCOMMENT
LOWsqlite3ext.h481#define sqlite3_libversion sqlite3_api->libversionCOMMENT
LOWsqlite3ext.h501#define sqlite3_result_null sqlite3_api->result_nullCOMMENT
LOWsqlite3ext.h521#define sqlite3_value_blob sqlite3_api->value_blobCOMMENT
LOWsqlite3ext.h541#define sqlite3_blob_close sqlite3_api->blob_closeCOMMENT
LOWsqlite3ext.h561#define sqlite3_vfs_register sqlite3_api->vfs_registerCOMMENT
LOWsqlite3ext.h581#define sqlite3_create_function_v2 sqlite3_api->create_function_v2COMMENT
LOWsqlite3ext.h601#define sqlite3_db_readonly sqlite3_api->db_readonlyCOMMENT
LOWsqlite3ext.h621#define sqlite3_reset_auto_extension sqlite3_api->reset_auto_extensionCOMMENT
LOWsqlite3ext.h641#define sqlite3_expanded_sql sqlite3_api->expanded_sqlCOMMENT
LOWsqlite3ext.h661#define sqlite3_str_vappendf sqlite3_api->str_vappendfCOMMENT
LOWsqlite3ext.h681#define sqlite3_filename_database sqlite3_api->filename_databaseCOMMENT
LOWsqlite3ext.h701#define sqlite3_vtab_in_next sqlite3_api->vtab_in_nextCOMMENT
LOWsqlite3ext.h721#define sqlite3_db_status64 sqlite3_api->db_status64COMMENT
LOWsqlite3ext.h741# define SQLITE_EXTENSION_INIT3 /*no-op*/COMMENT
LOWsqlite3_func_crypt.go1// Copyright (C) 2018 G.J.R. Timmer <gjr.timmer@gmail.com>.COMMENT
LOWsqlite3_func_crypt.go21// function through the use of the RegisterFunc on the connection.COMMENT
40 more matches not shown…