AI Slop Code Risk Monitor

timescale/timescaledb

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

A time-series database for high-performance real-time analytics packaged as a Postgres extension

1.5 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for timescale/timescaledb, a C project with 23,777 GitHub stars. SynthScan examined 332,633 lines of code across 1449 source files, recording 406 pattern matches distributed across 15 syntactic categories. The legacy adjusted pattern signal is 1.5 (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.

1.5
Adjusted Signal
1.5
Raw Pattern Score
100%
Time Factor
2026-10-31
Last Push
23.8K
Stars
C
Language
332.6K
Lines of Code
1.4K
Files
406
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 6.3/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 389 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.9/100 · LOW

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

PR Review Velocity Impact 6.9/100 · LOW

Which changes need focused human review? 406 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 6MEDIUM 21LOW 379

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 406 distinct pattern matches across 15 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 Block331 hits · 331 pts
SeverityFileLineSnippetContext
LOWtest/pg_regress.sh1#!/usr/bin/env bashCOMMENT
LOWtest/runner_isolation.sh1#!/usr/bin/env bashCOMMENT
LOWtest/pg_prove.sh1#!/usr/bin/env bashCOMMENT
LOWtest/t/001_replication_telemetry.pl1# This file and its contents are licensed under the Timescale License.COMMENT
LOWtest/t/002_compressed_chunk_apache.pl1# This file and its contents are licensed under the Apache License 2.0.COMMENT
LOWtest/src/test_with_clause_parser.c1/*COMMENT
LOWtest/src/test_utils.c1/*COMMENT
LOWtest/src/loader/init.c1/*COMMENT
LOWtest/src/telemetry/test_telemetry.c1/*COMMENT
LOWtest/src/bgw/log.c1/*COMMENT
LOWtest/src/bgw/timer_mock.c1/*COMMENT
LOWtest/src/bgw/test_job_refresh.c1/*COMMENT
LOWtest/src/bgw/scheduler_mock.c1/*COMMENT
LOWtest/src/bgw/scheduler_mock.c21#include <utils/guc.h>COMMENT
LOWtest/src/bgw/params.c1/*COMMENT
LOWtsl/test/t/006_granular_refresh_restart.pl1# This file and its contents are licensed under the Timescale License.COMMENT
LOWtsl/test/t/007_custom_toaster.pl1# This file and its contents are licensed under the Timescale License.COMMENT
LOWtsl/test/src/decompress_arithmetic_test_impl.c1/*COMMENT
LOWtsl/test/src/decompress_arithmetic_test_impl.c281COMMENT
LOWtsl/test/src/compression_sql_test.c61 */COMMENT
LOWtsl/test/src/compression_sql_test.c81#define ALGO AICCOMMENT
LOWtsl/test/src/compression_sql_test.c101#define CTYPE pg_uuid_tCOMMENT
LOWtsl/test/src/compression_unit_test.c1/*COMMENT
LOWtsl/test/src/compression_unit_test.c21#include <utils/typcache.h>COMMENT
LOWtsl/src/chunkwise_agg.c1/*COMMENT
LOWtsl/src/process_utility.c1/*COMMENT
LOWtsl/src/process_utility.c21#include "bgw_policy/policies_v2.h"COMMENT
LOWtsl/src/chunk_merge.c1/*COMMENT
LOWtsl/src/chunk_merge.c21#include <executor/spi.h>COMMENT
LOWtsl/src/chunk_merge.c41#include "chunk.h"COMMENT
LOWtsl/src/init.c1/*COMMENT
LOWtsl/src/init.c21#include "compression/algorithms/array.h"COMMENT
LOWtsl/src/init.c41#include "continuous_aggs/utils.h"COMMENT
LOWtsl/src/chunk.c1/*COMMENT
LOWtsl/src/chunk.c21#include <nodes/nodes.h>COMMENT
LOWtsl/src/chunk_split.c1/*COMMENT
LOWtsl/src/chunk_split.c21#include <utils/syscache.h>COMMENT
LOWtsl/src/reorder.c21#include <access/transam.h>COMMENT
LOWtsl/src/reorder.c41#include <storage/bufmgr.h>COMMENT
LOWtsl/src/chunk_api.c1/*COMMENT
LOWtsl/src/chunk_api.c21#include <funcapi.h>COMMENT
LOWtsl/src/planner.c1/*COMMENT
LOWtsl/src/continuous_aggs/materialize.c1/*COMMENT
LOWtsl/src/continuous_aggs/insert.c1/*COMMENT
LOWtsl/src/continuous_aggs/add_column.c1/*COMMENT
LOWtsl/src/continuous_aggs/add_column.c21#include <utils/rel.h>COMMENT
LOWtsl/src/continuous_aggs/invalidation.c1/*COMMENT
LOWtsl/src/continuous_aggs/invalidation.c21#include <scanner.h>COMMENT
LOWtsl/src/continuous_aggs/rewrite_with_caggs.c1/*COMMENT
LOWtsl/src/continuous_aggs/create.c21#include <access/sysattr.h>COMMENT
LOWtsl/src/continuous_aggs/create.c41#include <optimizer/clauses.h>COMMENT
LOWtsl/src/continuous_aggs/create.c61#include <utils/ruleutils.h>COMMENT
LOWtsl/src/continuous_aggs/refresh.c1/*COMMENT
LOWtsl/src/continuous_aggs/refresh.c21#include <utils/snapmgr.h>COMMENT
LOWtsl/src/continuous_aggs/utils.c1/*COMMENT
LOWtsl/src/continuous_aggs/common.h1/*COMMENT
LOWtsl/src/continuous_aggs/common.h21#include <nodes/pg_list.h>COMMENT
LOWtsl/src/continuous_aggs/tenant_tracker.c181#include <storage/lwlock.h>COMMENT
LOWtsl/src/continuous_aggs/finalize.h1/*COMMENT
LOWtsl/src/continuous_aggs/invalidation_threshold.c1/*COMMENT
271 more matches not shown…
Decorative Section Separators12 hits · 36 pts
SeverityFileLineSnippetContext
MEDIUMtsl/test/t/006_granular_refresh_restart.pl38# ===========================================================================COMMENT
MEDIUMtsl/test/t/006_granular_refresh_restart.pl40# ===========================================================================COMMENT
MEDIUMtsl/test/t/006_granular_refresh_restart.pl150# ===========================================================================COMMENT
MEDIUMtsl/test/t/006_granular_refresh_restart.pl152# ===========================================================================COMMENT
MEDIUMtsl/test/t/006_granular_refresh_restart.pl182# ===========================================================================COMMENT
MEDIUMtsl/test/t/006_granular_refresh_restart.pl185# ===========================================================================COMMENT
MEDIUMtsl/test/t/006_granular_refresh_restart.pl296# ===========================================================================COMMENT
MEDIUMtsl/test/t/006_granular_refresh_restart.pl305# ===========================================================================COMMENT
MEDIUM.github/workflows/release_feature_freeze_ceremony.yaml122 # -------------------------------------------------------COMMENT
MEDIUM.github/workflows/release_feature_freeze_ceremony.yaml126 # -------------------------------------------------------COMMENT
MEDIUM.github/workflows/release_feature_freeze_ceremony.yaml173 # -------------------------------------------------------COMMENT
MEDIUM.github/workflows/release_feature_freeze_ceremony.yaml177 # -------------------------------------------------------COMMENT
Structural Annotation Overuse23 hits · 34 pts
SeverityFileLineSnippetContext
LOWREADME.md35### Step 1: Start TimescaleDBCOMMENT
LOWREADME.md72### Step 2: Connect to TimescaleDBCOMMENT
LOWREADME.md96### Step 3: Create Your First HypertableCOMMENT
LOWREADME.md123### Step 4: Insert Sample DataCOMMENT
LOWREADME.md167### Step 5: Run Your First Analytical QueriesCOMMENT
LOWREADME.md252#### Step 1: Create the Continuous AggregateCOMMENT
LOWREADME.md272#### Step 2: Add a Refresh PolicyCOMMENT
LOWREADME.md290#### Step 3: Query the Continuous AggregateCOMMENT
LOWdocs/getting-started/nyc-taxi/README.md21### Step 1: Start TimescaleDBCOMMENT
LOWdocs/getting-started/nyc-taxi/README.md58### Step 2: Connect to TimescaleDBCOMMENT
LOWdocs/getting-started/nyc-taxi/README.md82### Step 3: Create the SchemaCOMMENT
LOWdocs/getting-started/nyc-taxi/README.md128### Step 4: Load Sample DataCOMMENT
LOWdocs/getting-started/nyc-taxi/README.md199### Step 5: Run Sample QueriesCOMMENT
LOWdocs/getting-started/financial-ticks/README.md54### Step 1: Start TimescaleDBCOMMENT
LOWdocs/getting-started/financial-ticks/README.md91### Step 2: Connect to TimescaleDBCOMMENT
LOWdocs/getting-started/financial-ticks/README.md114### Step 3: Create the SchemaCOMMENT
LOWdocs/getting-started/financial-ticks/README.md139### Step 4: Load Sample Data into TimescaleDBCOMMENT
LOWdocs/getting-started/financial-ticks/README.md156### Step 5: Run Sample QueriesCOMMENT
LOWdocs/getting-started/events-uuidv7/README.md20### Step 1: Start TimescaleDBCOMMENT
LOWdocs/getting-started/events-uuidv7/README.md57### Step 2: Connect to TimescaleDBCOMMENT
LOWdocs/getting-started/events-uuidv7/README.md81### Step 3: Create the SchemaCOMMENT
LOWdocs/getting-started/events-uuidv7/README.md122### Step 4: Load Sample DataCOMMENT
LOWdocs/getting-started/events-uuidv7/README.md193### Step 5: Run Sample QueriesCOMMENT
Self-Referential Comments7 hits · 21 pts
SeverityFileLineSnippetContext
MEDIUMscripts/label-released.py61# Create the label if neededCOMMENT
MEDIUMscripts/upload_ci_stats.sh74# Create the job record.COMMENT
MEDIUMscripts/test_update_smoke.sh136# Create a 1.7.5 version UpgradeCOMMENT
MEDIUMscripts/backport.py573 # Create the backport PR.COMMENT
MEDIUM.github/workflows/libfuzzer.yaml242 # Create the fuzzing functionsCOMMENT
MEDIUM.github/workflows/sanitizer-build-and-test.yaml112 # Create a directory for sanitizer logs. This directory is referenced byCOMMENT
MEDIUM.github/workflows/llm-fuzzer.yaml134 # Create a directory for sanitizer logs. This directory is referenced byCOMMENT
Cross-File Repetition3 hits · 15 pts
SeverityFileLineSnippetContext
HIGHscripts/label-released.py0a simple function to use requests.post to make the graphql api call.STRING
HIGHscripts/backport.py0a simple function to use requests.post to make the graphql api call.STRING
HIGHscripts/check_changelog_format.py0a simple function to use requests.post to make the graphql api call.STRING
Synthetic Comment Markers2 hits · 12 pts
SeverityFileLineSnippetContext
HIGHtsl/src/compression/algorithms/fastlanes/README.md126Compared to the C++ implementation, where the kernel is auto-generated code and C++ templates or the RustCODE
HIGHscripts/check_license.sh9# - test/sql/dump which contains auto-generated codeCOMMENT
Slop Phrases4 hits · 8 pts
SeverityFileLineSnippetContext
MEDIUMtest/pg_prove.sh10# Note that you can also use regular expressions to run multipleCOMMENT
LOWtsl/src/import/access/heap/heapam.c291 * If heaptup is a private copy, release it. Don't forget to copy t_selfCOMMENT
LOWscripts/upload_ci_stats.sh17# don't forget to append the needed migration code below.COMMENT
LOWscripts/upload_ci_stats.sh17# don't forget to append the needed migration code below.COMMENT
Redundant / Tautological Comments7 hits · 8 pts
SeverityFileLineSnippetContext
LOWtsl/test/t/002_logrepl_decomp_marker.pl17# Set max_process_workers to 0 before starting the node. wal_level has to beCOMMENT
LOWscripts/delete_released_change_logs.sh3# Check if both old_version and new_version have been providedCOMMENT
LOWscripts/check_changelog_format.py66# Check if a line matches any of the specified patternsSTRING
LOWscripts/check_changelog_format.py98 # Check if the file existsSTRING
LOWscripts/check_changelog_format.py106 # Read the file and check non-empty linesSTRING
LOW.github/gh_matrix_builder.py341 # Check if we need to check for the flaky tests. Determine which test filesCOMMENT
LOW.github/workflows/changelog-check.yaml8 # Check if the PR creates a separate file with changelog entry in theCOMMENT
Deep Nesting6 hits · 6 pts
SeverityFileLineSnippetContext
LOWscripts/test_memory_spikes.py60CODE
LOWscripts/check_updates.py18CODE
LOWscripts/check_updates.py60CODE
LOWscripts/check_updates.py97CODE
LOWscripts/check_changelog_format.py82CODE
LOWscripts/githooks/commit_msg.py23CODE
Empty Error Handlers1 hit · 5 pts
SeverityFileLineSnippetContext
HIGHscripts/check_changelog_format.py129except github.UnknownObjectException:CODE
Verbosity Indicators3 hits · 4 pts
SeverityFileLineSnippetContext
LOWtsl/src/continuous_aggs/refresh.c1620 * In order to don't produce unnecessary batches we need to check if the start and end of theCOMMENT
LOWtsl/src/compression/recompress.c896 * compressed. But we need to check if there are any uncompressed tuples in theCOMMENT
LOWsrc/process_utility.c1857 * If it is a "GRANT/REVOKE ON ALL TABLES IN SCHEMA" operation then we need to check ifCOMMENT
Hyper-Verbose Identifiers4 hits · 4 pts
SeverityFileLineSnippetContext
LOWscripts/backport.py217def should_backport_by_labels(number, title, labels):CODE
LOWscripts/backport.py242def should_backport_by_milestone(number, title, milestone):CODE
LOWscripts/githooks/commit_msg.py59 def check_subject_body_separtor(self):CODE
LOWscripts/githooks/commit_msg.py70 def check_subject_capitalized(self):CODE
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUM.github/workflows/pgspot.yaml1# Test our extension sql scripts are following security best practicesCOMMENT
Example Usage Blocks1 hit · 2 pts
SeverityFileLineSnippetContext
LOWscripts/test_update_smoke.sh8# Usage:COMMENT
Excessive Try-Catch Wrapping1 hit · 1 pts
SeverityFileLineSnippetContext
LOWscripts/check_updates.py219 except Exception: # pylint: disable=broad-exceptCODE