AI Slop Code Risk Monitor

cameron314/concurrentqueue

SlopCodeMonitor badge for cameron314/concurrentqueue Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).
8.8 Moderate pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for cameron314/concurrentqueue. SynthScan examined 330,334 lines of code across 1647 source files, recording 3310 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 8.8 (Moderate 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.

8.8
Adjusted Signal
8.8
Raw Pattern Score
100%
Time Factor
—
Last Push
—
Stars
—
Language
330.3K
Lines of Code
1.6K
Files
3.3K
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 35.7/100 · MEDIUM

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

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

PR Review Velocity Impact 39.5/100 · MEDIUM

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

Run additional scans to build a history of the legacy pattern signal. Score changes are not a measure of AI adoption or code quality.

No multi-scan history yet — run the scanner again to build trend data.

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 3LOW 3307

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 3310 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 Block3307 hits · 2914 pts
SeverityFileLineSnippetContext
LOWlightweightsemaphore.h1// Provides an efficient implementation of a semaphore (LightweightSemaphore).COMMENT
LOWlightweightsemaphore.h21// namespace with thousands of generic names or adding a .cpp for nothing.COMMENT
LOWlightweightsemaphore.h41#endifCOMMENT
LOWlightweightsemaphore.h61//COMMENT
LOWblockingconcurrentqueue.h1// Provides an efficient blocking version of moodycamel::ConcurrentQueue.COMMENT
LOWconcurrentqueue.h1// Provides a C++11 implementation of a multi-producer, multi-consumer lock-free queue.COMMENT
LOWconcurrentqueue.h21// EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFCOMMENT
LOWconcurrentqueue.h41#ifdef MCDBGQ_USE_RELACYCOMMENT
LOWconcurrentqueue.h61// We'll override the default trait malloc ourselves without a macro.COMMENT
LOWconcurrentqueue.h141} }COMMENT
LOWconcurrentqueue.h161COMMENT
LOWconcurrentqueue.h181#endifCOMMENT
LOWconcurrentqueue.h201#define MOODYCAMEL_NOEXCEPT_CTOR(type, valueType, expr) trueCOMMENT
LOWconcurrentqueue.h221#ifdef MCDBGQ_USE_RELACYCOMMENT
LOWconcurrentqueue.h261#elseCOMMENT
LOWconcurrentqueue.h321COMMENT
LOWconcurrentqueue.h341 // whether the queue is lock-free with a 64-int type depends on the whetherCOMMENT
LOWconcurrentqueue.h361 static const size_t EXPLICIT_INITIAL_INDEX_SIZE = 32;COMMENT
LOWconcurrentqueue.h381 // internal queue.COMMENT
LOWconcurrentqueue.h401 static const bool RECYCLE_ALLOCATED_BLOCKS = false;COMMENT
LOWconcurrentqueue.h1061 }COMMENT
LOWconcurrentqueue.h1121 // Fails if not enough room to enqueue (or implicit production isCOMMENT
LOWconcurrentqueue.h1321 COMMENT
LOWconcurrentqueue.h2001 // Note that I believe a compiler (signal) fence here would be sufficient due to the nature of fetch_add (allCOMMENT
LOWconcurrentqueue.h2021 if ((details::likely)(details::circular_less_than<index_t>(myDequeueCount - overcommit, tail))) {COMMENT
LOWtests/corealgos.h1// ©2014 Cameron DesrochersCOMMENT
LOWtests/corealgos.h101// Use a nice trick from this answer: http://stackoverflow.com/a/8438730/21475COMMENT
LOWtests/relacy/relacy/test/foo.cpp1#include "stdafx.h"COMMENT
LOWtests/relacy/relacy/test/stdafx.h1#ifndef STDAFX_HCOMMENT
LOWtests/relacy/relacy/test/main.cpp1#include "stdafx.h"COMMENT
LOWtests/relacy/relacy/test/main.cpp321 //assert(VAR(data) != 2);COMMENT
LOWtests/relacy/relacy/test/main.cpp341 //p.collect_history = true;COMMENT
LOWtests/relacy/relacy/test/main.cpp361COMMENT
LOWtests/relacy/relacy/test/ntest/stdafx.h1#ifndef STDAFX_HCOMMENT
LOWtests/relacy/relacy/example/smr/stdafx.h1#pragma onceCOMMENT
LOWtests/relacy/relacy/example/ws_deque/stdafx.h1#pragma onceCOMMENT
LOWtests/relacy/relacy/example/mpmc/stdafx.h1#pragma onceCOMMENT
LOWtests/relacy/relacy/example/mpmc/mpmc.cpp1#include "stdafx.h"COMMENT
LOWtests/relacy/relacy/example/mpmc/stdafx.cpp1// stdafx.cpp : source file that includes just the standard includesCOMMENT
LOWtests/relacy/relacy/example/peterson/stdafx.h1#pragma onceCOMMENT
LOWtests/relacy/relacy/example/ws_deque2/stdafx.cpp1// stdafx.cpp : source file that includes just the standard includesCOMMENT
LOWtests/relacy/relacy/example/condvar/stdafx.h1#pragma onceCOMMENT
LOWtests/relacy/relacy/example/ref_counting/stdafx.h1#pragma onceCOMMENT
LOWtests/relacy/relacy/example/examples/stdafx.h1#pragma onceCOMMENT
LOW…ts/relacy/relacy/example/mutex_business_logic/stdafx.h1#pragma onceCOMMENT
LOWtests/relacy/relacy/example/stack/stdafx.h1#pragma onceCOMMENT
LOWtests/relacy/relacy/example/eventcount/stdafx.h1#pragma onceCOMMENT
LOWtests/relacy/relacy/example/eventcount/eventcount.cpp1#include "stdafx.h"COMMENT
LOWtests/relacy/relacy/example/eventcount/stdafx.cpp1// stdafx.cpp : source file that includes just the standard includesCOMMENT
LOW…ts/relacy/relacy/example/tbb_eventcount/eventcount.cpp1#include "stdafx.h"COMMENT
LOWtests/relacy/relacy/example/tbb_eventcount/stdafx.cpp1// stdafx.cpp : source file that includes just the standard includesCOMMENT
LOWtests/relacy/relacy/relacy/relacy.hpp21#include "atomic_fence.hpp"COMMENT
LOWtests/relacy/relacy/relacy/relacy.hpp41#define memory_order_relaxed mo_relaxed, $COMMENT
LOWtests/relacy/relacy/relacy/relacy.hpp61#define free(p) rl::rl_free((p), $)COMMENT
LOWtests/relacy/relacy/relacy/relacy_std.hpp21#define atomic std_atomicCOMMENT
LOWtests/relacy/relacy/relacy/relacy_std.hpp61 using rl::atomic_ushort;COMMENT
LOWtests/relacy/relacy/relacy/pch.hpp21# undef _FORTIFY_SOURCECOMMENT
LOWtests/relacy/relacy/relacy/pch.hpp41#include <iterator>COMMENT
LOWtests/relacy/relacy/relacy/pch.hpp61# include <process.h>COMMENT
LOWtests/relacy/relacy/relacy/context_base.hpp21#include "test_params.hpp"COMMENT
3247 more matches not shown…
Decorative Section Separators2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMbenchmarks/dlib/logger/logger_config_file.h53 # -----------------------------------------------COMMENT
MEDIUMbenchmarks/dlib/logger/logger_config_file.h55 # -----------------------------------------------COMMENT
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMbenchmarks/tbb/task_stream.h36//! Essentially, this is just a pair of a queue and a mutex to protect the queue.COMMENT