Repository Analysis

abseil/abseil-cpp

Abseil Common Libraries (C++)

16.6 Moderate AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of abseil/abseil-cpp, a C++ project with 17,970 GitHub stars. SynthScan v2.0 examined 114,746 lines of code across 440 source files, recording 1988 pattern matches distributed across 5 syntactic categories. The overall adjusted score of 16.6 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).

16.6
Adjusted Score
16.6
Raw Score
100%
Time Factor
2026-07-14
Last Push
18.0K
Stars
C++
Language
114.7K
Lines of Code
440
Files
2.0K
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 12LOW 1976

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 1988 distinct pattern matches across 5 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 Block1964 hits · 1850 pts
SeverityFileLineSnippetContext
LOWCMakeLists.txt1#COMMENT
LOWcreate_lts.py1#!/usr/bin/env python3COMMENT
LOWCMake/install_test_project/CMakeLists.txt1#COMMENT
LOWCMake/install_test_project/test.sh1#!/bin/bashCOMMENT
LOWci/linux_gcc-latest_libstdcxx_bazel.sh1#!/bin/bashCOMMENT
LOWci/macos_xcode_bazel.sh1#!/bin/bashCOMMENT
LOWci/linux_clang-latest_libstdcxx_bazel.sh1#!/bin/bashCOMMENT
LOWci/linux_docker_containers.sh1# Copyright 2019 The Abseil Authors.COMMENT
LOWci/absl_alternate_options.h1// Copyright 2019 The Abseil Authors.COMMENT
LOWci/absl_alternate_options.h21#define ABSL_CI_ABSL_ALTERNATE_OPTIONS_H_COMMENT
LOWci/linux_arm_clang-latest_libcxx_bazel.sh1#!/bin/bashCOMMENT
LOWci/linux_gcc_alpine_cmake.sh1#!/bin/bashCOMMENT
LOWci/linux_clang-latest_libcxx_asan_bazel.sh1#!/bin/bashCOMMENT
LOWci/macos_xcode_cmake.sh1#!/bin/bashCOMMENT
LOWci/cmake_install_test.sh1#!/bin/bashCOMMENT
LOWci/linux_gcc-latest_libstdcxx_cmake.sh1#!/bin/bashCOMMENT
LOWci/linux_clang-latest_libcxx_tsan_bazel.sh1#!/bin/bashCOMMENT
LOWci/linux_gcc-floor_libstdcxx_bazel.sh1#!/bin/bashCOMMENT
LOWci/cmake_common.sh1# Copyright 2020 The Abseil Authors.COMMENT
LOWci/linux_clang-latest_libcxx_bazel.sh1#!/bin/bashCOMMENT
LOWabsl/CMakeLists.txt1#COMMENT
LOWabsl/strings/has_ostream_operator.h1// Copyright 2023 The Abseil AuthorsCOMMENT
LOWabsl/strings/numbers.h1// Copyright 2017 The Abseil Authors.COMMENT
LOWabsl/strings/numbers.h21// which automatically detect and convert most number values appropriately.COMMENT
LOWabsl/strings/numbers.h41#include <type_traits>COMMENT
LOWabsl/strings/numbers.h61// integer type (optionally preceded by a `+` or `-`). If any errors areCOMMENT
LOWabsl/strings/numbers.h81// Converts the given string (optionally followed or preceded by ASCIICOMMENT
LOWabsl/strings/numbers.h181// Helper function used to implement absl::HighPrecision().COMMENT
LOWabsl/strings/CMakeLists.txt1#COMMENT
LOWabsl/strings/cord_analysis.h1// Copyright 2021 The Abseil AuthorsCOMMENT
LOWabsl/strings/cord_analysis.h21#include "absl/base/config.h"COMMENT
LOWabsl/strings/cord_analysis.h41// cord.append(some_other_cord);COMMENT
LOWabsl/strings/cord_test_helpers.h1//COMMENT
LOWabsl/strings/cord_test_helpers.h81COMMENT
LOWabsl/strings/str_format.h1//COMMENT
LOWabsl/strings/str_format.h21// `printf()` string formatting routines within the `<cstdio>` standard libraryCOMMENT
LOWabsl/strings/str_format.h41//COMMENT
LOWabsl/strings/str_format.h61//COMMENT
LOWabsl/strings/str_format.h81#include "absl/base/attributes.h"COMMENT
LOWabsl/strings/str_format.h121 str_format_internal::UntypedFormatSpecImpl spec_;COMMENT
LOWabsl/strings/str_format.h141// conversions, which denote the number of characters written by a formattingCOMMENT
LOWabsl/strings/str_format.h161 friend struct str_format_internal::FormatCountCaptureHelper;COMMENT
LOWabsl/strings/str_format.h181//COMMENT
LOWabsl/strings/str_format.h201// absl::ParsedFormat<'s', 'd'> formatString("Welcome to %s, Number %d!");COMMENT
LOWabsl/strings/str_format.h221// * `p` for pointer address valuesCOMMENT
LOWabsl/strings/str_format.h241// "%s", "C" -> "C"COMMENT
LOWabsl/strings/str_format.h261// (instead of 1 or 0 for booleans formatted using d). `const char*` is notCOMMENT
LOWabsl/strings/str_format.h281// Clang. On MSVC, these checks are performed at runtime instead.COMMENT
LOWabsl/strings/str_format.h301// absl::ParsedFormat<'s', 'd'> format_string("Welcome to %s, Number %d!");COMMENT
LOWabsl/strings/str_format.h321// // Extended format supports multiple conversion characters per argument,COMMENT
LOWabsl/strings/str_format.h341COMMENT
LOWabsl/strings/str_format.h361// EXPECT_EQ("Welcome to The Village, Number 6!", s);COMMENT
LOWabsl/strings/str_format.h381// std::cout << StrAppendFormat(&orig, "%12.6f", 3.14);COMMENT
LOWabsl/strings/str_format.h401template <typename... Args>COMMENT
LOWabsl/strings/str_format.h421//COMMENT
LOWabsl/strings/str_format.h441//COMMENT
LOWabsl/strings/str_format.h461//COMMENT
LOWabsl/strings/str_format.h481// -----------------------------------------------------------------------------COMMENT
LOWabsl/strings/str_format.h521// appended to it.COMMENT
LOWabsl/strings/str_format.h541// `FormatUntyped()`. You may construct `FormatArg` by passingCOMMENT
1904 more matches not shown…
AI Slop Vocabulary12 hits · 36 pts
SeverityFileLineSnippetContext
MEDIUMabsl/debugging/stacktrace.h27// Note: stack traces in Abseil that do not utilize a symbolizer will result inCOMMENT
MEDIUMabsl/meta/type_traits.h564// If it ever becomes possible to detect [[gsl::Owner]], we should leverage it:COMMENT
MEDIUMabsl/meta/type_traits.h607// If it ever becomes possible to detect [[gsl::Pointer]], we should leverageCOMMENT
MEDIUMabsl/meta/type_traits.h632// we should change the implementation to leverage that.COMMENT
MEDIUMabsl/log/scoped_mock_log.h57// // Simple robust setup, ignores unexpected logs.COMMENT
MEDIUMabsl/log/check.h29// compromise. It is also more robust and portable to deliberately terminateCOMMENT
MEDIUMabsl/log/absl_check.h27// compromise. It is also more robust and portable to deliberately terminateCOMMENT
MEDIUMabsl/random/bernoulli_distribution.h161 // greater than or equal to 1, the same would be true for `p`. Certainly `p`COMMENT
MEDIUMabsl/random/internal/nanobenchmark.h19// prediction hit rates. Uses a robust estimator to summarize the measurements.COMMENT
MEDIUMabsl/random/internal/nanobenchmark.h45// which is more robust to outliers and skewed data than the mean or median.COMMENT
MEDIUMabsl/base/options.h39// Diamond dependency problems can be avoided if all packages utilize the sameCOMMENT
MEDIUMabsl/base/internal/poison.h48 // Non-optimized builds may use more robust implementation. Note that we can'tCOMMENT
Example Usage Blocks8 hits · 12 pts
SeverityFileLineSnippetContext
LOWabsl/strings/resize_and_overwrite.h31// Example usage:COMMENT
LOWabsl/strings/internal/generic_printer.h46// Example usage:COMMENT
LOWabsl/strings/internal/generic_printer.h85// Example usage:COMMENT
LOWabsl/synchronization/mutex.h180 // Example usage:COMMENT
LOWabsl/hash/internal/hash.h171// Example usage:COMMENT
LOWabsl/debugging/internal/vdso_support.h30// Example usage:COMMENT
LOWabsl/meta/internal/requires.h30// Example usage:COMMENT
LOWabsl/base/internal/raw_logging.h39// Usage example:COMMENT
Structural Annotation Overuse3 hits · 4 pts
SeverityFileLineSnippetContext
LOWabsl/status/status.h532 // NOTE: This function should only be called when converting to an associatedCOMMENT
LOWabsl/status/status.h623 // NOTE: This function does nothing if the Status is ok.COMMENT
LOWabsl/status/status_builder.h597 // NOTE: This function is `static` to prevent escaping the `this` pointer. WeCOMMENT
Fake / Example Data1 hit · 1 pts
SeverityFileLineSnippetContext
LOWabsl/functional/any_invocable_test.h148 char dummy_data[absl::internal_any_invocable::kStorageSize + 1] = {};CODE