AI Slop Code Risk Monitor

CalcProgrammer1/OpenRGB

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

Open source RGB lighting control that doesn't depend on manufacturer software. Supports Windows, Linux, MacOS. Mirror of https://gitlab.com/CalcProgrammer1/OpenRGB. Releases can be found on GitLab.

1.6 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for CalcProgrammer1/OpenRGB, a C++ project with 4,644 GitHub stars. SynthScan examined 547,511 lines of code across 2188 source files, recording 1004 pattern matches distributed across 5 syntactic categories. The legacy adjusted pattern signal is 1.6 (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.6
Adjusted Signal
1.6
Raw Pattern Score
100%
Time Factor
2026-10-30
Last Push
4.6K
Stars
C++
Language
547.5K
Lines of Code
2.2K
Files
1.0K
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 7.5/100 · LOW

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

Which changes need focused human review? 1004 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 2MEDIUM 12LOW 990

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 1004 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 Block989 hits · 800 pts
SeverityFileLineSnippetContext
LOWfilesystem.h21#define STD_FILESYSTEM_FOUNDCOMMENT
LOWNetworkServer.h21#include <queue>COMMENT
LOWColors.h21#define COLOR_DARKCYAN 0x008b8bCOMMENT
LOWColors.h41#define COLOR_DARKSLATEBLUE 0x483d8bCOMMENT
LOWColors.h61#define COLOR_PURPLE 0x800080COMMENT
LOWColors.h81#define COLOR_DARKGRAY 0xa9a9a9COMMENT
LOWColors.h101#define COLOR_THISTLE 0xd8bfd8COMMENT
LOWColors.h121#define COLOR_BEIGE 0xf5f5dcCOMMENT
LOWColors.h141#define COLOR_LIGHTPINK 0xffb6c1COMMENT
LOWNetworkClient.cpp21#ifdef _WIN32COMMENT
LOWNetworkServer.cpp21#include <sys/ioctl.h>COMMENT
LOWcli.cpp1/*---------------------------------------------------------*\COMMENT
LOW.gitlab-ci.yml1#-----------------------------------------------------------#COMMENT
LOWDetectionManager.h521#elseCOMMENT
LOWDetectionManager.h541#define REGISTER_HID_DETECTOR_DISABLED(name, func, vid, pid) static HIDDeviceDeteCOMMENT
LOWDetectionManager.h561#define REGISTER_HID_DETECTOR_PU_ONLY_DISABLED(name, func, page, usage) static HIDDeviceDeteCOMMENT
LOWDetectionManager.h581#define REGISTER_HID_WRAPPED_DETECTOR_PU_DISABLED(name, func, vid, pid, page, usage) static HIDWrappedDevCOMMENT
LOWDetectionManager.h601#define REGISTER_DYNAMIC_I2C_PCI_DETECTOR(name, func, ven, dev, subven, subdev, addr) I2CPCIDeviceDetectorCOMMENT
LOWResourceManager.cpp21#include "cli.h"COMMENT
LOWLogManager.cpp1/*---------------------------------------------------------*\COMMENT
LOWLogManager.h181#define LOG_VERBOSE(...) LogAppend(LL_VERBOSE, __VA_ARGS__)COMMENT
LOWAutoStart/AutoStart.h41#endifCOMMENT
LOWi2c_smbus/i2c_smbus.h61COMMENT
LOWi2c_smbus/MacOS/i2c_smbus_nct6775.h21#define SMBHSTADD (5 + nct6775_smba)COMMENT
LOWi2c_smbus/MacOS/i2c_smbus_i801.cpp161 // {COMMENT
LOWi2c_smbus/MacOS/i2c_smbus_i801.cpp241 // priv->data = &data->block[1];COMMENT
LOWi2c_smbus/MacOS/i2c_smbus_i801.cpp401 // status = inb_p(SMBAUXSTS(priv)) & SMBAUXSTS_CRCE;COMMENT
LOWi2c_smbus/MacOS/i2c_smbus_i801.cpp421 int status;COMMENT
LOWi2c_smbus/MacOS/i2c_smbus_i801.h21#define SMBHSTSTS (0 + i801_smba)COMMENT
LOWi2c_smbus/MacOS/i2c_smbus_i801.h41#define SMBAUXCTL_CRC BIT(0)COMMENT
LOWi2c_smbus/MacOS/i2c_smbus_i801.h61#define SMBHSTCNT_PEC_EN BIT(7) /* ICH3 and later */COMMENT
LOWi2c_smbus/MacOS/i2c_smbus_piix4.h21#define SMBHSTCMD (3 + piix4_smba)COMMENT
LOWpci_ids/pci_ids.h21#define AMD_FCH_SMBUS_DEV 0x790BCOMMENT
LOWpci_ids/pci_ids.h41#define AMD_NAVI23_DEV1 0x73EFCOMMENT
LOWpci_ids/pci_ids.h61#define INTEL_RAPTOR_LAKE_SMBUS_DEV 0x7A23COMMENT
LOWpci_ids/pci_ids.h81#define NVIDIA_RTX2060S_DEV 0x1F47COMMENT
LOWpci_ids/pci_ids.h101#define NVIDIA_RTX3060TI_LHR_DEV 0x2489COMMENT
LOWpci_ids/pci_ids.h121#define NVIDIA_RTX4070TIS_AD102_DEV 0x2689COMMENT
LOWpci_ids/pci_ids.h141#define NVIDIA_RTX2080_FE_SUB_DEV 0x12A6COMMENT
LOWpci_ids/pci_ids.h161#define ASROCK_SUB_VEN 0x1849COMMENT
LOWpci_ids/pci_ids.h181#define ASUS_ROG_STRIX_GTX1050TI_4G_GAMING 0x8611COMMENT
LOWpci_ids/pci_ids.h201#define ASUS_ROG_STRIX_GTX1650S_OC 0x874FCOMMENT
LOWpci_ids/pci_ids.h221#define ASUS_ROG_STRIX_RTX2070S_O8G_GAMING_8729 0x8729COMMENT
LOWpci_ids/pci_ids.h241#define ASUS_TUF_RTX_3060_O12G_V2_GAMING 0x8865COMMENT
LOWpci_ids/pci_ids.h261#define ASUS_KO_RTX_3070_O8G_GAMING_V1 0x87BECOMMENT
LOWpci_ids/pci_ids.h281#define ASUS_TUF_RTX_3080_O10G_V2_GAMING_8822 0x8822COMMENT
LOWpci_ids/pci_ids.h301#define ASUS_TUF_RTX_3090TI_24G_GAMING 0x8875COMMENT
LOWpci_ids/pci_ids.h321#define ASUS_TUF_RTX_4070TI_SUPER_O16G_GAMING 0x8957COMMENT
LOWpci_ids/pci_ids.h341#define ASUS_ROG_STRIX_RTX_4080S_16G_GAMING_WHITE 0x8969COMMENT
LOWpci_ids/pci_ids.h361#define ASUS_TUF_RTX_5060_O8G_GAMING 0x8A1ACOMMENT
LOWpci_ids/pci_ids.h381#define ASUS_ROG_MATRIX_PLATINUM_RTX_5090_P32G 0x8A61COMMENT
LOWpci_ids/pci_ids.h401#define ASUS_ROG_STRIX_RX_6600XT_O8G_GAMING 0x05D1COMMENT
LOWpci_ids/pci_ids.h421#define ASUS_TUF_RX_7900GRE_O16G_GAMING 0x050CCOMMENT
LOWpci_ids/pci_ids.h441#define COLORFUL_IGAME_RTX_3080_ADVANCED_OC_10G 0x1401COMMENT
LOWpci_ids/pci_ids.h461#define COLORFUL_IGAME_RTX_5060TI_ULTRAW_DUO_OC 0x1531COMMENT
LOWpci_ids/pci_ids.h481#define EVGA_GTX1080TI_FTW3_HYBRID_SUB_DEV 0x6698COMMENT
LOWpci_ids/pci_ids.h501#define EVGA_RTX2080S_FTW3_ULTRA_SUB_DEV 0x3287COMMENT
LOWpci_ids/pci_ids.h521#define EVGA_RTX3070_FTW3_ULTRA_LHR_ALT_SUB_DEV 0x4467COMMENT
LOWpci_ids/pci_ids.h541#define EVGA_RTX3080_FTW3_ULTRA_HYBRID_LHR_SUB_DEV 0x4898COMMENT
LOWpci_ids/pci_ids.h561#define EVGA_RTX3090_FTW3_ULTRA_V2_SUB_DEV 0x3982COMMENT
929 more matches not shown…
Self-Referential Comments10 hits · 30 pts
SeverityFileLineSnippetContext
MEDIUM.gitlab-ci.yml6# This file is part of the OpenRGB project #COMMENT
MEDIUMdependencies/mbedtls-3.2.1/include/psa/crypto_extra.h1300 * -# Initialize the operation object with one of the methods described in theCOMMENT
MEDIUMdependencies/mbedtls-3.2.1/include/psa/crypto.h948 * -# Initialize the operation object with one of the methods described in theCOMMENT
MEDIUMdependencies/mbedtls-3.2.1/include/psa/crypto.h1311 * -# Initialize the operation object with one of the methods described in theCOMMENT
MEDIUMdependencies/mbedtls-3.2.1/include/psa/crypto.h1371 * -# Initialize the operation object with one of the methods described in theCOMMENT
MEDIUMdependencies/mbedtls-3.2.1/include/psa/crypto.h1720 * -# Initialize the operation object with one of the methods described in theCOMMENT
MEDIUMdependencies/mbedtls-3.2.1/include/psa/crypto.h1783 * -# Initialize the operation object with one of the methods described in theCOMMENT
MEDIUMdependencies/mbedtls-3.2.1/include/psa/crypto.h2238 * -# Initialize the operation object with one of the methods described in theCOMMENT
MEDIUMdependencies/mbedtls-3.2.1/include/psa/crypto.h2308 * -# Initialize the operation object with one of the methods described in theCOMMENT
MEDIUMscripts/build-msi.sh86# Create the Wix XML file #COMMENT
Synthetic Comment Markers2 hits · 15 pts
SeverityFileLineSnippetContext
HIGHdependencies/display-library/include/adl_structures.h3764///\brief Structure Containing All Generic LED configuration for user requested LED pattern. The driver will apply the cCOMMENT
HIGHdependencies/display-library/include/adl_structures.h3781///\brief Structure Containing All custom grid pattern LED configuration for user requested LED grid pattern. The driverCOMMENT
AI Slop Vocabulary2 hits · 4 pts
SeverityFileLineSnippetContext
MEDIUM…trollers/LogitechController/LogitechProtocolCommon.cpp83 get_connected_devices.feature_command = 0x02; //0x02 Connection State register. Essentially asking for CODE
MEDIUM…trollers/LogitechController/LogitechProtocolCommon.cpp420 get_connected_devices.feature_command = 0x02; //0x02 Connection State register. Essentially asking for coCODE
Redundant / Tautological Comments1 hit · 2 pts
SeverityFileLineSnippetContext
LOWscripts/build-msi.sh87# Set IFS to the empty string to allow arbitrary spacing #COMMENT