Repository Analysis

raspberrypi/pico-sdk

20.2 Moderate AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of raspberrypi/pico-sdk, a C project with 4,923 GitHub stars. SynthScan v2.0 examined 304,138 lines of code across 940 source files, recording 9211 pattern matches distributed across 11 syntactic categories. The overall adjusted score of 20.2 places this repository in the Moderate AI signal 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).

20.2
Adjusted Score
20.2
Raw Score
100%
Time Factor
2026-08-09
Last Push
4.9K
Stars
C
Language
304.1K
Lines of Code
940
Files
9.2K
Pattern Hits
2026-08-09
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 16LOW 9195

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 9211 distinct pattern matches across 11 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 Block9136 hits · 6046 pts
SeverityFileLineSnippetContext
LOWtools/build_all_headers.py1#!/usr/bin/env python3COMMENT
LOWtools/check_all_groups.py1#!/usr/bin/env python3COMMENT
LOWtools/CMakeLists.txt361#COMMENT
LOWtools/CMakeLists.txt421# \brief\ Set the UF2 family to use when creating the UF2.COMMENT
LOWtools/CMakeLists.txt481# \brief_nodesc\ Embed a partition table in the binaryCOMMENT
LOWtools/CMakeLists.txt501# and sign the encrypted binary.COMMENT
LOWtools/check_source_files_in_bazel_build.py1#!/usr/bin/env python3COMMENT
LOWtools/compare_build_systems.py1#!/usr/bin/env python3COMMENT
LOWtools/check_board_header.py1#!/usr/bin/env python3COMMENT
LOWtools/extract_cmake_functions.py1#!/usr/bin/env python3COMMENT
LOWtools/check_doxygen_groups.py1#!/usr/bin/env python3COMMENT
LOWtools/extract_cmake_configs.py1#!/usr/bin/env python3COMMENT
LOWtools/extract_build_defines.py1#!/usr/bin/env python3COMMENT
LOWtools/extract_configs.py1#!/usr/bin/env python3COMMENT
LOWtools/pioasm/pio_enums.h21#endifCOMMENT
LOWtools/pioasm/pio_types.h1/*COMMENT
LOWtools/pioasm/gen/parser.hpp1// A Bison parser, made by GNU Bison 3.7.2.COMMENT
LOWtools/pioasm/gen/parser.hpp21// part or all of the Bison parser skeleton and distribute that workCOMMENT
LOWtools/pioasm/gen/parser.hpp41// DO NOT RELY ON FEATURES THAT ARE NOT DOCUMENTED in the manual,COMMENT
LOWtools/pioasm/gen/parser.hpp61# include <cstdlib> // std::abortCOMMENT
LOWtools/pioasm/gen/parser.hpp81# define YY_MOVECOMMENT
LOWtools/pioasm/gen/parser.hpp101# define YY_CONSTEXPRCOMMENT
LOWtools/pioasm/gen/parser.hpp121# define YY_ATTRIBUTE_UNUSED __attribute__ ((__unused__))COMMENT
LOWtools/pioasm/gen/parser.hpp141 _Pragma ("GCC diagnostic pop")COMMENT
LOWtools/pioasm/gen/parser.hpp161# define YY_IGNORE_USELESS_CAST_BEGINCOMMENT
LOWtools/pioasm/gen/parser.hpp421 // valueCOMMENT
LOWtools/pioasm/gen/parser.hpp2841 const symbol_type& yyla_;COMMENT
LOWtools/pioasm/gen/parser.hpp2901 // Tables.COMMENT
LOWtools/pioasm/gen/parser.hpp3141 stack_type yystack_;COMMENT
LOWtools/pioasm/gen/lexer.cpp861 *COMMENT
LOWtools/pioasm/gen/location.h1// A Bison parser, made by GNU Bison 3.7.2.COMMENT
LOWtools/pioasm/gen/location.h21// part or all of the Bison parser skeleton and distribute that workCOMMENT
LOWtools/pioasm/gen/location.h41# include <iostream>COMMENT
LOWtools/pioasm/gen/parser.cpp1// A Bison parser, made by GNU Bison 3.7.2.COMMENT
LOWtools/pioasm/gen/parser.cpp21// part or all of the Bison parser skeleton and distribute that workCOMMENT
LOWtools/pioasm/gen/parser.cpp41#include "parser.hpp"COMMENT
LOWtools/pioasm/gen/parser.cpp61# define YY_(msgid) msgidCOMMENT
LOWtools/pioasm/gen/parser.cpp121 yy_stack_print_ (); \COMMENT
LOWtest/CMakeLists.txt41 # Can be used to force failure even when the test prints the success stringCOMMENT
LOWtest/pico_low_power_test/low_power_test_common.h1#ifndef LOW_POWER_TEST_COMMON_HCOMMENT
LOWtest/pico_low_power_test/low_power_test_common.h41#endifCOMMENT
LOWtest/pico_low_power_test/external_sleep_timer.c1/**COMMENT
LOWtest/pico_time_test/pico_time_test.c1/**COMMENT
LOWtest/pico_time_test/pico_time_test.c21// Include sys/types.h before inttypes.h to work around issue withCOMMENT
LOWtest/pico_float_test/pico_float_test.c1//===-- aeabi_cfcmpeq.c - Test __aeabi_cfcmpeq ----------------------------===//COMMENT
LOWtest/pico_float_test/pico_float_test.c21// certain versions of GCC and newlib which causes omission of PRIx64COMMENT
LOWtest/pico_float_test/pico_float_test.c341#define allowed_range(a) (fabsf(a) / FRAC)COMMENT
LOWtest/pico_float_test/pico_float_test.c361#endifCOMMENT
LOWtest/pico_float_test/double_benchmark.c1#include <stdio.h>COMMENT
LOWtest/pico_float_test/double_benchmark.c161#elseCOMMENT
LOWtest/pico_float_test/double_benchmark.c1221#endifCOMMENT
LOWtest/pico_float_test/custom_float_funcs_test.c1#include <stdio.h>COMMENT
LOWtest/pico_float_test/pico_double_test.c1//===-- aeabi_cdcmpeq.c - Test __aeabi_cdcmpeq ----------------------------===//COMMENT
LOWtest/pico_float_test/pico_double_test.c321double __real_pow(double, double);COMMENT
LOWtest/pico_float_test/custom_double_funcs_test.c1#include <stdio.h>COMMENT
LOWtest/pico_float_test/float_benchmark.c1#include <stdio.h>COMMENT
LOWtest/pico_float_test/float_benchmark.c161#elseCOMMENT
LOWtest/pico_float_test/float_benchmark.c1161 printf("PICO VFP ===\n");COMMENT
LOWtest/pico_float_test/pico_float_test_hazard3.c141 // inf * nan = same nanCOMMENT
LOWtest/pico_float_test/llvm/call_apsr.h1//todo check licenseCOMMENT
9076 more matches not shown…
Decorative Section Separators12 hits · 36 pts
SeverityFileLineSnippetContext
MEDIUMtools/check_extern_c_guards.py58# ---------------------------------------------------------------------------COMMENT
MEDIUMtools/check_extern_c_guards.py60# ---------------------------------------------------------------------------COMMENT
MEDIUMtools/check_extern_c_guards.py86# ---------------------------------------------------------------------------COMMENT
MEDIUMtools/check_extern_c_guards.py88# ---------------------------------------------------------------------------COMMENT
MEDIUMtools/check_extern_c_guards.py202# ---------------------------------------------------------------------------COMMENT
MEDIUMtools/check_extern_c_guards.py204# ---------------------------------------------------------------------------COMMENT
MEDIUMtools/check_extern_c_guards.py254# ---------------------------------------------------------------------------COMMENT
MEDIUMtools/check_extern_c_guards.py256# ---------------------------------------------------------------------------COMMENT
MEDIUMtools/check_extern_c_guards.py289# ---------------------------------------------------------------------------COMMENT
MEDIUMtools/check_extern_c_guards.py291# ---------------------------------------------------------------------------COMMENT
MEDIUMtools/check_extern_c_guards.py363# ---------------------------------------------------------------------------COMMENT
MEDIUMtools/check_extern_c_guards.py365# ---------------------------------------------------------------------------COMMENT
Deep Nesting18 hits · 18 pts
SeverityFileLineSnippetContext
LOWtools/copro_dis.py38CODE
LOWtools/check_float_test_names.py156CODE
LOWtools/check_float_test_names.py178CODE
LOWtools/check_float_test_names.py249CODE
LOWtools/check_extern_c_guards.py120CODE
LOWtools/check_extern_c_guards.py440CODE
LOWtools/compare_build_systems.py209CODE
LOWtools/compare_build_systems.py239CODE
LOWtools/memmap_include_tree.py233CODE
LOWtools/check_board_header.py89CODE
LOWtools/extract_cmake_functions.py103CODE
LOWtools/extract_cmake_functions.py152CODE
LOWtools/extract_cmake_configs.py71CODE
LOWtools/extract_build_defines.py69CODE
LOWtools/run_test_matrix.py80CODE
LOWtools/extract_configs.py76CODE
LOWtools/extract_configs.py102CODE
LOWsrc/rp2_common/pico_lwip/tools/makefsdata.py88CODE
Example Usage Blocks10 hits · 15 pts
SeverityFileLineSnippetContext
LOWtools/build_all_headers.py12# Usage:COMMENT
LOWtools/check_all_groups.py11# Usage:COMMENT
LOWtools/check_source_files_in_bazel_build.py11# Usage:COMMENT
LOWtools/compare_build_systems.py11# Usage:COMMENT
LOWtools/check_board_header.py10# Usage:COMMENT
LOWtools/extract_cmake_functions.py12# Usage:COMMENT
LOWtools/check_doxygen_groups.py10# Usage:COMMENT
LOWtools/extract_cmake_configs.py12# Usage:COMMENT
LOWtools/extract_build_defines.py12# Usage:COMMENT
LOWtools/extract_configs.py12# Usage:COMMENT
Hyper-Verbose Identifiers12 hits · 12 pts
SeverityFileLineSnippetContext
LOWtools/check_all_groups.py45def get_group_from_config_attrs(attr_str):CODE
LOWtools/check_source_files_in_bazel_build.py93def check_bazel_build_for_files(CODE
LOWtools/check_source_files_in_bazel_build.py151def git_ls_files_by_extension(file_suffixes: Iterable[str]) -> Iterable[Path]:CODE
LOWtools/check_source_files_in_bazel_build.py173def check_sources_in_bazel_build(picotool_dir) -> int:CODE
LOWtools/memmap_include_tree.py74def _indent_default_excludes_body(text: str) -> str:CODE
LOWtools/memmap_include_tree.py143def validate_explicit_platform(sdk_root: Path, platform: str) -> str | None:CODE
LOWtools/memmap_include_tree.py300def fold_docstring_for_argparse(doc: str) -> str:CODE
LOWtools/memmap_include_tree.py310def collect_unresolved_include_paths(CODE
LOWtools/memmap_include_tree.py323def format_memmap_annotate_status_line(tag: str, msg: str) -> str:CODE
LOWtools/extract_cmake_configs.py232def build_mismatch_exception_message(name, thing, config_obj1, value1, config_obj2, value2):CODE
LOWtools/extract_build_defines.py229def build_mismatch_exception_message(name, thing, config_obj1, value1, config_obj2, value2):CODE
LOWtools/extract_configs.py339def build_mismatch_exception_message(name, thing, config_obj1, value1, config_obj2, value2):CODE
Excessive Try-Catch Wrapping7 hits · 9 pts
SeverityFileLineSnippetContext
LOWtools/check_extern_c_guards.py138 except Exception as exc:CODE
LOWtools/check_extern_c_guards.py184 except Exception as exc:CODE
MEDIUMtools/check_extern_c_guards.py270 print("Error: not inside a git repository.", file=sys.stderr)CODE
LOWtools/run_test_matrix.py197 except Exception as e:CODE
LOWtools/run_test_matrix.py226 except Exception as e:CODE
MEDIUMtools/run_test_matrix.py227 print(f"Error reading output file: {e}")CODE
LOWtools/run_test_matrix.py240 except Exception as e:CODE
Unused Imports8 hits · 8 pts
SeverityFileLineSnippetContext
LOWtools/memmap_annotate.py22CODE
LOWtools/memmap_include_tree.py25CODE
LOWtools/bazel_buildifier_lint_check.py12CODE
LOWtools/bazel_buildifier_lint_check.py13CODE
LOWtools/bazel_buildifier_lint_check.py17CODE
LOWtools/bazel_build.py9CODE
LOWtools/bazel_build.py13CODE
LOW…ithub/workflows/scripts/generate_multi_gcc_workflow.py4CODE
AI Slop Vocabulary2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMsrc/rp2350/hardware_regs/include/hardware/regs/rp_ap.h650// manager and the switched-core. Essentially that is everythjingCOMMENT
MEDIUMsrc/rp2_common/pico_stdlib/stdlib.c18 // this is mostly for backwards compatibility - stdio_uart_init is a bit more nuanced, and usually likely to be presCOMMENT
Modern Structural Boilerplate4 hits · 4 pts
SeverityFileLineSnippetContext
LOWtools/extract_cmake_functions.py32logger = logging.getLogger(__name__)CODE
LOWtools/extract_cmake_configs.py34logger = logging.getLogger(__name__)CODE
LOWtools/extract_build_defines.py34logger = logging.getLogger(__name__)CODE
LOWtools/extract_configs.py34logger = logging.getLogger(__name__)CODE
Slop Phrases1 hit · 2 pts
SeverityFileLineSnippetContext
LOWsrc/rp2_common/pico_multicore/multicore.c200 // entry is the initial program counter (PC) (don't forget to set the thumb bit!)COMMENT
Structural Annotation Overuse1 hit · 2 pts
SeverityFileLineSnippetContext
LOWsrc/rp2_common/pico_bootrom/include/pico/bootrom.h76// NOTE: This function does not validate the buffer for NS access. This must be validated beforeCOMMENT