AI Slop Code RIsk Monitor

abseil/abseil-cpp

Abseil Common Libraries (C++)

16.7 Elevated pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for abseil/abseil-cpp, a C++ project with 18,158 GitHub stars. SynthScan examined 116,129 lines of code across 440 source files, recording 2024 pattern matches distributed across 5 syntactic categories. The legacy adjusted pattern signal is 16.7 (Elevated pattern signal); it is not an authorship estimate.

Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.

16.7
Adjusted Signal
16.7
Raw Pattern Score
100%
Time Factor
2026-10-11
Last Push
18.2K
Stars
C++
Language
116.1K
Lines of Code
440
Files
2.0K
Pattern Hits
2026-10-12
Scan Date
0.00
HC Hit Rate

Risk Review · v3

Use each vector to guide manual verification of the underlying findings.

Cognitive Ownership Risk 56.6/100 · HIGH

Can maintainers explain intent, assumptions, and trade-offs? 2023 finding(s).

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

Are imports declared and package/API names verified? 1 finding(s).

Agent Over-Engineering Ratio 0.0/100 · LOW

Are wrappers, guards, and repeated structures necessary? 0 finding(s).

PR Review Velocity Impact 58.6/100 · HIGH

Which changes need focused human review? 2024 finding(s).

What These Metrics Mean

Adjusted Signal
Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score
Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor
A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits
Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate
High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files
Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.

Severity Breakdown

Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.

CRITICAL 0HIGH 0MEDIUM 12LOW 2012

Directory Score Breakdown

This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.

Pattern Findings

The scanner identified 2024 distinct pattern matches across 5 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. 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 configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.

Over-Commented Block2000 hits · 1884 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 "absl/numeric/bits.h"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.h21#include <cstdint>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// // specified via a combination of `FormatConversionCharSet` enums.COMMENT
LOWabsl/strings/str_format.h341// used in most cases where you need type-safe conversion of types intoCOMMENT
LOWabsl/strings/str_format.h401}COMMENT
LOWabsl/strings/str_format.h421}COMMENT
LOWabsl/strings/str_format.h441 {str_format_internal::FormatArgImpl(args)...});COMMENT
LOWabsl/strings/str_format.h461// "The capital of Mongolia is %s", s);COMMENT
LOWabsl/strings/str_format.h481//COMMENT
LOWabsl/strings/str_format.h501COMMENT
LOWabsl/strings/str_format.h541COMMENT
LOWabsl/strings/str_format.h561// Example:COMMENT
1940 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.h503// If it ever becomes possible to detect [[gsl::Owner]], we should leverage it:COMMENT
MEDIUMabsl/meta/type_traits.h573// If it ever becomes possible to detect [[gsl::Pointer]], we should leverageCOMMENT
MEDIUMabsl/meta/type_traits.h629// 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.h87// Example usage:COMMENT
LOWabsl/synchronization/mutex.h180 // Example usage:COMMENT
LOWabsl/hash/internal/hash.h169// 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.h40// Usage example:COMMENT
Structural Annotation Overuse3 hits · 4 pts
SeverityFileLineSnippetContext
LOWabsl/status/status.h544 // NOTE: This function should only be called when converting to an associatedCOMMENT
LOWabsl/status/status.h647 // 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.h147 char dummy_data[absl::internal_any_invocable::kStorageSize + 1] = {};CODE