AI Slop Code Risk Monitor

tporadowski/redis

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

Native port of Redis for Windows. Redis is an in-memory database that persists on disk. The data model is key-value, but many different kind of values are supported: Strings, Lists, Sets, Sorted Sets, Hashes, Streams, HyperLogLogs. This repository contains unofficial port of Redis to Windows.

1.8 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for tporadowski/redis, a C project with 10,290 GitHub stars. SynthScan examined 217,093 lines of code across 651 source files, recording 375 pattern matches distributed across 8 syntactic categories. The legacy adjusted pattern signal is 1.8 (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.8
Adjusted Signal
1.8
Raw Pattern Score
100%
Time Factor
2026-10-08
Last Push
10.3K
Stars
C
Language
217.1K
Lines of Code
651
Files
375
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 8.2/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.4/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 8.6/100 · LOW

Which changes need focused human review? 375 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 3MEDIUM 1LOW 371

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 375 distinct pattern matches across 8 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 Block363 hits · 358 pts
SeverityFileLineSnippetContext
LOWutils/install_server.sh1#!/bin/shCOMMENT
LOWutils/install_server.sh21# OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OFCOMMENT
LOWutils/install_server.sh161REDISPORT=\"$REDIS_PORT\"\n\nCOMMENT
LOWutils/install_server.sh201PIDFILE=$PIDFILECOMMENT
LOWutils/hyperloglog/hll-gnuplot-graph.rb1# hll-err.rb - Copyright (C) 2014 Salvatore SanfilippoCOMMENT
LOWdeps/jemalloc-5.2.1/msvc/test_threads/test_threads.cpp1// jemalloc C++ threaded testCOMMENT
LOWdeps/jemalloc-5.2.1/test/unit/arena_reset_prof.c1#include "test/jemalloc_test.h"COMMENT
LOWdeps/jemalloc-5.2.1/test/include/test/SFMT-params2281.h41#define SL2 1COMMENT
LOWdeps/jemalloc-5.2.1/test/include/test/SFMT-params2281.h61 #define ALTI_SL2_PERM \COMMENT
LOWdeps/jemalloc-5.2.1/test/include/test/SFMT-params.h101COMMENT
LOWdeps/jemalloc-5.2.1/test/include/test/SFMT-params.h121 #include "test/SFMT-params216091.h"COMMENT
LOWdeps/jemalloc-5.2.1/test/include/test/SFMT-params1279.h41#define SL2 3COMMENT
LOWdeps/jemalloc-5.2.1/test/include/test/SFMT-params1279.h61 #define ALTI_SL2_PERM \COMMENT
LOW…ps/jemalloc-5.2.1/test/include/test/SFMT-params44497.h41#define SL2 3COMMENT
LOW…ps/jemalloc-5.2.1/test/include/test/SFMT-params44497.h61 #define ALTI_SL2_PERM \COMMENT
LOWdeps/jemalloc-5.2.1/test/include/test/test.h21 !=, "p", __VA_ARGS__)COMMENT
LOWdeps/jemalloc-5.2.1/test/include/test/test.h41#define assert_x_gt(a, b, ...) assert_cmp(int, a, b, >, <=, "#x", __VA_ARGS__)COMMENT
LOWdeps/jemalloc-5.2.1/test/include/test/SFMT-params4253.h41#define SL2 1COMMENT
LOWdeps/jemalloc-5.2.1/test/include/test/SFMT-params4253.h61 #define ALTI_SL2_PERM \COMMENT
LOW…ps/jemalloc-5.2.1/test/include/test/SFMT-params11213.h41#define SL2 3COMMENT
LOW…ps/jemalloc-5.2.1/test/include/test/SFMT-params11213.h61 #define ALTI_SL2_PERM \COMMENT
LOW…ps/jemalloc-5.2.1/test/include/test/SFMT-params86243.h41#define SL2 7COMMENT
LOW…ps/jemalloc-5.2.1/test/include/test/SFMT-params86243.h61 #define ALTI_SL2_PERM \COMMENT
LOW…s/jemalloc-5.2.1/test/include/test/SFMT-params132049.h41#define SL2 1COMMENT
LOW…s/jemalloc-5.2.1/test/include/test/SFMT-params132049.h61 #define ALTI_SL2_PERM \COMMENT
LOW…s/jemalloc-5.2.1/test/include/test/SFMT-params216091.h41#define SL2 3COMMENT
LOW…s/jemalloc-5.2.1/test/include/test/SFMT-params216091.h61 #define ALTI_SL2_PERM \COMMENT
LOW…ps/jemalloc-5.2.1/test/include/test/SFMT-params19937.h41#define SL2 1COMMENT
LOW…ps/jemalloc-5.2.1/test/include/test/SFMT-params19937.h61 #define ALTI_SL2_PERM \COMMENT
LOWdeps/jemalloc-5.2.1/test/include/test/SFMT-params607.h41#define SL2 3COMMENT
LOWdeps/jemalloc-5.2.1/test/include/test/SFMT-params607.h61 #define ALTI_SL2_PERM \COMMENT
LOWdeps/jemalloc-5.2.1/test/src/math.c1#define MATH_C_COMMENT
LOWdeps/jemalloc-5.2.1/test/src/SFMT.c41 * @author Makoto Matsumoto (Hiroshima University)COMMENT
LOWdeps/jemalloc-5.2.1/include/jemalloc/jemalloc_mangle.h1/*COMMENT
LOWdeps/jemalloc-5.2.1/include/jemalloc/jemalloc_mangle.h21# define malloc_message je_malloc_messageCOMMENT
LOWdeps/jemalloc-5.2.1/include/jemalloc/jemalloc_mangle.h41 */COMMENT
LOWdeps/jemalloc-5.2.1/include/jemalloc/jemalloc_mangle.h61# undef je_sallocxCOMMENT
LOWdeps/jemalloc-5.2.1/include/jemalloc/jemalloc.h61#ifndef JEMALLOC_NO_RENAMECOMMENT
LOWdeps/jemalloc-5.2.1/include/jemalloc/jemalloc.h81# define je_sdallocx je_sdallocxCOMMENT
LOWdeps/jemalloc-5.2.1/include/jemalloc/jemalloc.h141# define JEMALLOC_CXX_THROWCOMMENT
LOWdeps/jemalloc-5.2.1/include/jemalloc/jemalloc.h161# elseCOMMENT
LOWdeps/jemalloc-5.2.1/include/jemalloc/jemalloc.h181# ifndef JEMALLOC_EXPORTCOMMENT
LOWdeps/jemalloc-5.2.1/include/jemalloc/jemalloc.h201#elseCOMMENT
LOWdeps/jemalloc-5.2.1/include/jemalloc/jemalloc.h381# define mallctlbymib je_mallctlbymibCOMMENT
LOWdeps/jemalloc-5.2.1/include/jemalloc/jemalloc.h401 * public jemalloc API if JEMALLOC_NO_DEMANGLE is defined. This is primarilyCOMMENT
LOWdeps/jemalloc-5.2.1/include/jemalloc/jemalloc.h421# undef je_nallocxCOMMENT
LOWdeps/jemalloc-5.2.1/include/jemalloc/jemalloc_defs.h41# ifdef _WIN64COMMENT
LOW…/jemalloc-5.2.1/include/jemalloc/jemalloc_mangle_jet.h1/*COMMENT
LOW…/jemalloc-5.2.1/include/jemalloc/jemalloc_mangle_jet.h21# define malloc_message jet_malloc_messageCOMMENT
LOW…/jemalloc-5.2.1/include/jemalloc/jemalloc_mangle_jet.h41 */COMMENT
LOW…/jemalloc-5.2.1/include/jemalloc/jemalloc_mangle_jet.h61# undef jet_sallocxCOMMENT
LOWdeps/jemalloc-5.2.1/include/jemalloc/jemalloc_rename.h1/*COMMENT
LOWdeps/jemalloc-5.2.1/include/jemalloc/jemalloc_rename.h21# define je_nallocx je_nallocxCOMMENT
LOWdeps/jemalloc-5.2.1/include/jemalloc/jemalloc_macros.h1#include <stdlib.h>COMMENT
LOWdeps/jemalloc-5.2.1/include/jemalloc/jemalloc_macros.h61# define JEMALLOC_ATTR(s)COMMENT
LOWdeps/jemalloc-5.2.1/include/jemalloc/jemalloc_macros.h81# define JEMALLOC_RESTRICT_RETURN __declspec(restrict)COMMENT
LOWdeps/jemalloc-5.2.1/include/jemalloc/jemalloc_macros.h101# define JEMALLOC_FORMAT_ARG(i) JEMALLOC_ATTR(__format_arg__(3))COMMENT
LOWdeps/jemalloc-5.2.1/include/jemalloc/jemalloc_macros.h121# define JEMALLOC_ALLOC_SIZE2(s1, s2)COMMENT
LOW…loc-5.2.1/include/jemalloc/internal/public_namespace.h1#define je_aligned_alloc JEMALLOC_N(aligned_alloc)COMMENT
LOW…-5.2.1/include/jemalloc/internal/private_unnamespace.h1#undef a0dallocCOMMENT
303 more matches not shown…
Cross-Language Confusion3 hits · 15 pts
SeverityFileLineSnippetContext
HIGHdeps/jemalloc-5.2.1/scripts/gen_run_tests.py109 \$@ >> run_test.log 2>&1 || abortCODE
HIGHdeps/jemalloc-5.2.1/scripts/gen_run_tests.py117%(config_line)s >> run_test.log 2>&1 || abortCODE
HIGHdeps/jemalloc-5.2.1/scripts/gen_travis.py15 - scripts/gen_travis.py > travis_script && diff .travis.yml travis_scriptCODE
Verbosity Indicators3 hits · 4 pts
SeverityFileLineSnippetContext
LOWsrc/t_stream.c2326 /* We need to check if the minimum idle time requestedCOMMENT
LOWsrc/networking.c2193 /* We need to check if the soft limit is reached continuously for theCOMMENT
LOWsrc/scripting.c294 /* We need to check if it is an array, an error, or a status reply.COMMENT
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMutils/redis-copy.rb7# for the more-robust redis-copy gem.COMMENT
Redundant / Tautological Comments2 hits · 3 pts
SeverityFileLineSnippetContext
LOWutils/lru/test-lru.rb74# Check if evicted keys respect LRUCOMMENT
LOWsrc/module.c1413 * ## Return valueCOMMENT
Slop Phrases1 hit · 2 pts
SeverityFileLineSnippetContext
LOWutils/redis-sha1.rb8# If you hack this code make sure to sort keys and set elements as this areCOMMENT
Hyper-Verbose Identifiers1 hit · 2 pts
SeverityFileLineSnippetContext
LOWsrc/server.c951 * the function clientsCronTrackExpansiveClients(). */COMMENT
Fake / Example Data1 hit · 1 pts
SeverityFileLineSnippetContext
LOWsrc/rdb.c1469 return createStringObject("module-dummy-value",18);CODE