AI Slop Code Risk Monitor

uber/h3

Name: uber/h3 — C Code Quality & Security Review | AI Slop Code Risk Monitor
Creator: AI Slop Code Risk Monitor

Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

Hexagonal hierarchical geospatial indexing system

0.1 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for uber/h3, a C project with 6,670 GitHub stars. SynthScan examined 275,693 lines of code across 428 source files, recording 36 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 0.1 (Low 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.

0.1

Adjusted Signal

0.1

Raw Pattern Score

100%

Time Factor

2026-10-29

Last Push

6.7K

Stars

Language

275.7K

Lines of Code

428

Files

Pattern Hits

2026-10-31

Scan Date

0.00

HC Hit Rate

Risk Review · Payload v1

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

Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.

Cognitive Ownership Risk 0.7/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 0.7/100 · LOW

Which changes need focused human review? 36 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 1LOW 35

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 36 distinct pattern matches across 3 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 Block34 hits · 34 pts

Severity	File	Line	Snippet	Context
LOW	CMakeLists.txt	1	# Copyright 2017-2022 Uber Technologies, Inc.	COMMENT
LOW	examples/CMakeLists.txt	1	# Copyright 2018 Uber Technologies, Inc.	COMMENT
LOW	examples/edge.c	41	// The edge is 16a2a1072b59ffff	COMMENT
LOW	scripts/update_version.sh	1	#!/usr/bin/env bash	COMMENT
LOW	scripts/binding_functions.sh	1	#!/usr/bin/env bash	COMMENT
LOW	scripts/publish_website.sh	1	#!/bin/sh	COMMENT
LOW	src/apps/filters/h3.c	21		COMMENT
LOW	src/apps/testapps/testCellToBoundaryEdgeCases.c	21	#include "h3api.h"	COMMENT
LOW	src/apps/testapps/testCellToLocalIjExhaustive.c	21	*/	COMMENT
LOW	src/apps/testapps/testGridDistanceExhaustive.c	21		COMMENT
LOW	src/apps/testapps/testCellToLocalIjInternal.c	21		COMMENT
LOW	src/apps/testapps/testCoordIjInternal.c	21		COMMENT
LOW	src/apps/testapps/testCellToLocalIj.c	21		COMMENT
LOW	…apps/testapps/testPolygonToCellsReportedExperimental.c	21	#include "constants.h"	COMMENT
LOW	src/apps/testapps/testGridDistance.c	21		COMMENT
LOW	src/apps/testapps/testGridDistanceInternal.c	21		COMMENT
LOW	src/apps/testapps/testH3Memory.c	21		COMMENT
LOW	src/apps/miscapps/generateBaseCellNeighbors.c	141	// direction from the neighboring base cell to the	COMMENT
LOW	src/apps/applib/include/aflHarness.h	81	#endif // H3_USE_LIBFUZZER	COMMENT
LOW	src/h3lib/include/polygonAlgos.h	21	* included inline in a file that defines the type-specific	COMMENT
LOW	src/h3lib/include/polygonAlgos.h	41	#error "IS_EMPTY must be defined before including this header"	COMMENT
LOW	src/h3lib/include/h3Assert.h	121	#define ALWAYS(X) (X)	COMMENT
LOW	src/h3lib/include/directedEdge.h	21	#define DIRECTEDEDGE_H	COMMENT
LOW	src/h3lib/include/constants.h	81	#define NUM_BASE_CELLS 122	COMMENT
LOW	src/h3lib/include/alloc.h	41	#ifdef __cplusplus	COMMENT
LOW	src/h3lib/lib/algos.c	21		COMMENT
LOW	src/h3lib/lib/algos.c	1001	* @param res The Hexagon resolution (0-15)	COMMENT
LOW	src/h3lib/lib/localij.c	21	*/	COMMENT
LOW	src/h3lib/lib/iterGosper.c	41	* the digit sequence as if it were a hexagon, then skip over the deleted	COMMENT
LOW	src/h3lib/lib/polyfill.c	21		COMMENT
LOW	src/h3lib/lib/polygon.c	21		COMMENT
LOW	src/h3lib/lib/h3Index.c	21		COMMENT
LOW	src/h3lib/lib/linkedGeo.c	581	H3_MEMORY(free)(innerLoops);	COMMENT
LOW	src/h3lib/lib/faceijk.c	21	#include "faceijk.h"	COMMENT

Self-Referential Comments1 hit · 3 pts

Severity	File	Line	Snippet	Context
MEDIUM	scripts/binding_functions.sh	16	# This file is used to extract lists of functions that should be provided	COMMENT

Verbosity Indicators1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	src/h3lib/lib/h3Index.c	1498	// While we are inside a parent pentagon, we need to check if	COMMENT