AI Slop Code Risk Monitor

sz3/libcimbar

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

Optimized implementation for color-icon-matrix barcodes

2.1 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for sz3/libcimbar, a C++ project with 6,529 GitHub stars. SynthScan examined 130,181 lines of code across 393 source files, recording 303 pattern matches distributed across 5 syntactic categories. The legacy adjusted pattern signal is 2.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.

2.1
Adjusted Signal
2.1
Raw Pattern Score
100%
Time Factor
2026-10-30
Last Push
6.5K
Stars
C++
Language
130.2K
Lines of Code
393
Files
303
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 9.9/100 · LOW

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

Which changes need focused human review? 303 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 302

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 303 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 Block294 hits · 258 pts
SeverityFileLineSnippetContext
LOWtest/catch.hpp21# pragma clang system_headerCOMMENT
LOWtest/catch.hpp41 // Wparentheses have to be suppressed globally.COMMENT
LOWtest/catch.hpp61# if !defined(CATCH_CONFIG_ENABLE_CHRONO_STRINGMAKER)COMMENT
LOWtest/catch.hpp81# define CATCH_PLATFORM_LINUXCOMMENT
LOWtest/catch.hpp101COMMENT
LOWtest/catch.hpp121// In general each macro has a _NO_<feature name> formCOMMENT
LOWtest/catch.hpp141# define CATCH_INTERNAL_START_WARNINGS_SUPPRESSION _Pragma( "GCC diagnostic push" )COMMENT
LOWtest/catch.hpp181# define CATCH_INTERNAL_SUPPRESS_UNUSED_TEMPLATE_WARNINGS \COMMENT
LOWtest/catch.hpp201#endifCOMMENT
LOWtest/catch.hpp221COMMENT
LOWtest/catch.hpp241#if defined(_MSC_VER)COMMENT
LOWtest/catch.hpp261# define CATCH_INTERNAL_START_WARNINGS_SUPPRESSION __pragma( warning(push) )COMMENT
LOWtest/catch.hpp281# define CATCH_INTERNAL_CONFIG_NO_WCHARCOMMENT
LOWtest/catch.hpp301////////////////////////////////////////////////////////////////////////////////COMMENT
LOWtest/catch.hpp321 #endifCOMMENT
LOWtest/catch.hpp341 # include <ciso646>COMMENT
LOWtest/catch.hpp361# define CATCH_CONFIG_POSIX_SIGNALSCOMMENT
LOWtest/catch.hpp381# define CATCH_CONFIG_CPP17_VARIANTCOMMENT
LOWtest/catch.hpp401# define CATCH_CONFIG_POLYFILL_ISNANCOMMENT
LOWtest/catch.hpp421#if !defined(CATCH_INTERNAL_STOP_WARNINGS_SUPPRESSION)COMMENT
LOWtest/catch.hpp441#endifCOMMENT
LOWtest/catch.hpp461#endifCOMMENT
LOWtest/catch.hpp701#define INTERNAL_CATCH_EXPAND_VARGS(...) __VA_ARGS__COMMENT
LOWtest/catch.hpp721COMMENT
LOWtest/catch.hpp741#define INTERNAL_CATCH_STRINGIZE(...) INTERNAL_CATCH_STRINGIZE2(__VA_ARGS__)COMMENT
LOWtest/catch.hpp761#define INTERNAL_CATCH_MAKE_TYPE_LIST2(...) INTERNAL_CATCH_EXPAND_VARGS(decltype(get_wrapper<INTERNAL_CATCH_REMOVE_PARENCOMMENT
LOWtest/catch.hpp901#define INTERNAL_CATCH_NTTP_REG_GEN(TestFunc, ...) INTERNAL_CATCH_VA_NARGS_IMPL( "dummy", __VA_ARGS__, INTERNAL_CATCH_NTCOMMENT
LOWtest/catch.hpp1021 #ifndef CATCH_CONFIG_TRADITIONAL_MSVC_PREPROCESSORCOMMENT
LOWtest/catch.hpp1401 ResultDisposition::Flags resultDisposition;COMMENT
LOWtest/catch.hpp1521 return nil;COMMENT
LOWtest/catch.hpp1861 }COMMENT
LOWtest/catch.hpp2181COMMENT
LOWtest/catch.hpp2681#elseCOMMENT
LOWtest/catch.hpp5061COMMENT
LOWtest/catch.hpp6941COMMENT
LOWtest/catch.hpp7941// start catch_debugger.hCOMMENT
LOWtest/catch.hpp7961 #define CATCH_TRAP() __asm__(".inst 0xd4200000")COMMENT
LOWtest/catch.hpp7981#elif defined(__MINGW32__)COMMENT
LOWtest/catch.hpp8001namespace Catch {COMMENT
LOWtest/catch.hpp8401 }COMMENT
LOWtest/catch.hpp8421#pragma clang diagnostic ignored "-Wexit-time-destructors"COMMENT
LOWtest/catch.hpp8441#define CATCH_CLARA_TEXTFLOW_CONFIG_CONSOLE_WIDTH CATCH_CLARA_CONFIG_CONSOLE_WIDTHCOMMENT
LOWtest/catch.hpp9681#ifdef __clang__COMMENT
LOWtest/catch.hpp10061#endifCOMMENT
LOWtest/catch.hpp10401# include <cassert>COMMENT
LOWtest/catch.hpp10461COMMENT
LOWtest/catch.hpp10881COMMENT
LOWtest/catch.hpp12041 std::string& m_stdoutDest;COMMENT
LOWtest/catch.hpp14341 return className;COMMENT
LOWtest/catch.hpp15001COMMENT
LOWtest/catch.hpp15321#if defined(_MSC_VER)COMMENT
LOWtest/catch.hpp15761#include <cstring>COMMENT
LOWtest/catch.hpp17561#ifdef CLARA_CONFIG_MAIN_NOT_DEFINEDCOMMENT
LOWtest/catch.hpp17581#define CATCH_CHECK( ... ) INTERNAL_CATCH_TEST( "CATCH_CHECK", Catch::ResultDisposition::ContinueOnFailure, __VA_ARGS__ COMMENT
LOWtest/catch.hpp17601#define CATCH_INFO( msg ) INTERNAL_CATCH_INFO( "CATCH_INFO", msg )COMMENT
LOWtest/catch.hpp17621#define CATCH_TEMPLATE_TEST_CASE_METHOD( className, ... ) INTERNAL_CATCH_TEMPLATE_TEST_CASE_METHOD( className, __VA_ARGSCOMMENT
LOWtest/catch.hpp17641#elseCOMMENT
LOWtest/catch.hpp17661#endif // CATCH_CONFIG_ENABLE_BENCHMARKINGCOMMENT
LOWtest/catch.hpp17681#define CHECK_NOFAIL( ... ) INTERNAL_CATCH_TEST( "CHECK_NOFAIL", Catch::ResultDisposition::ContinueOnFailure | Catch::ReCOMMENT
LOWtest/catch.hpp17701COMMENT
234 more matches not shown…
Verbosity Indicators4 hits · 6 pts
SeverityFileLineSnippetContext
LOWtest/catch.hpp12661 // No children have started. We need to check if they _can_COMMENT
LOWsrc/third_party_lib/fmt/format-inl.h1259 // Step 1: integer promotion & Schubfach multiplier calculation.COMMENT
LOWsrc/third_party_lib/fmt/format-inl.h1314 // Step 2: Try larger divisor; remove trailing zeros if necessary.COMMENT
LOWsrc/third_party_lib/fmt/format-inl.h1346 // Step 3: Find the significand with the smaller divisor.COMMENT
Structural Annotation Overuse3 hits · 4 pts
SeverityFileLineSnippetContext
LOWsrc/third_party_lib/fmt/format-inl.h1259 // Step 1: integer promotion & Schubfach multiplier calculation.COMMENT
LOWsrc/third_party_lib/fmt/format-inl.h1314 // Step 2: Try larger divisor; remove trailing zeros if necessary.COMMENT
LOWsrc/third_party_lib/fmt/format-inl.h1346 // Step 3: Find the significand with the smaller divisor.COMMENT
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMsrc/third_party_lib/fmt/format.h3359 // Compilers are not aware of how to leverage the maximum value ofCOMMENT
Unused Imports1 hit · 1 pts
SeverityFileLineSnippetContext
LOWtest/py/test_cimbar_cli.py5CODE