AI Slop Code Risk Monitor

KDE/heaptrack

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

A heap memory profiler for Linux

2.4 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for KDE/heaptrack, a C++ project with 4,190 GitHub stars. SynthScan examined 31,250 lines of code across 150 source files, recording 93 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 2.4 (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.4
Adjusted Signal
2.4
Raw Pattern Score
100%
Time Factor
2026-10-13
Last Push
4.2K
Stars
C++
Language
31.2K
Lines of Code
150
Files
93
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 10.5/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.8/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 14.1/100 · LOW

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

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 93 distinct pattern matches across 4 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 Block87 hits · 66 pts
SeverityFileLineSnippetContext
LOWtests/manual/perf-heaptrack.py1#COMMENT
LOWtests/benchmarks/bench_tree.cpp1/*COMMENT
LOW3rdparty/doctest.h1/*COMMENT
LOW3rdparty/doctest.h21//COMMENT
LOW3rdparty/doctest.h41// which uses the Boost Software License - Version 1.0COMMENT
LOW3rdparty/doctest.h61#define DOCTEST_TOSTR(x) DOCTEST_TOSTR_IMPL(x)COMMENT
LOW3rdparty/doctest.h81#endifCOMMENT
LOW3rdparty/doctest.h101#define DOCTEST_ICC DOCTEST_COMPILER(__INTEL_COMPILER / 100, __INTEL_COMPILER % 100, 0)COMMENT
LOW3rdparty/doctest.h121#if DOCTEST_CLANG && !DOCTEST_ICCCOMMENT
LOW3rdparty/doctest.h141 DOCTEST_GCC_SUPPRESS_WARNING_PUSH DOCTEST_GCC_SUPPRESS_WARNING(w)COMMENT
LOW3rdparty/doctest.h261// general compiler feature support table: https://en.cppreference.com/w/cpp/compiler_supportCOMMENT
LOW3rdparty/doctest.h281#define DOCTEST_CONFIG_WINDOWS_SEHCOMMENT
LOW3rdparty/doctest.h301COMMENT
LOW3rdparty/doctest.h321#if DOCTEST_MSVCCOMMENT
LOW3rdparty/doctest.h341#endif // DOCTEST_CONFIG_IMPLEMENTATION_IN_DLLCOMMENT
LOW3rdparty/doctest.h361#define DOCTEST_UNUSEDCOMMENT
LOW3rdparty/doctest.h381#endif // DOCTEST_NORETURNCOMMENT
LOW3rdparty/doctest.h401#ifndef DOCTEST_NO_SANITIZE_INTEGERCOMMENT
LOW3rdparty/doctest.h421#define DOCTEST_DEFINE_INTERFACE(name) \COMMENT
LOW3rdparty/doctest.h441#define DOCTEST_PLATFORM_MACCOMMENT
LOW3rdparty/doctest.h461#ifndef DOCTEST_BREAK_INTO_DEBUGGERCOMMENT
LOW3rdparty/doctest.h481#define DOCTEST_BREAK_INTO_DEBUGGER() __debugbreak()COMMENT
LOW3rdparty/doctest.h501// which case we don't want to forward declare stuff from std - for reference:COMMENT
LOW3rdparty/doctest.h561#include <type_traits>COMMENT
LOW3rdparty/doctest.h581// Idea taken from this lecture about the string implementation of facebook/folly - fbstringCOMMENT
LOW3rdparty/doctest.h1361 const DOCTEST_REF_WRAP(R) rhs) {COMMENT
LOW3rdparty/doctest.h1481 DOCTEST_RELATIONAL_OP(ne, !=)COMMENT
LOW3rdparty/doctest.h2121COMMENT
LOW3rdparty/doctest.h2441 #__VA_ARGS__, __VA_ARGS__)COMMENT
LOW3rdparty/doctest.h2461#define DOCTEST_WARN_EQ(...) DOCTEST_BINARY_ASSERT(DT_WARN_EQ, eq, __VA_ARGS__)COMMENT
LOW3rdparty/doctest.h2541#define DOCTEST_CHECK_THROWS_WITH(expr, ...) DOCTEST_ASSERT_THROWS_WITH(expr, #expr, DT_CHECK_THROWS_WITH, __VA_ARGS__)COMMENT
LOW3rdparty/doctest.h2561#define DOCTEST_WARN_THROWS_WITH_AS_MESSAGE(expr, with, ex, ...) DOCTEST_FUNC_SCOPE_BEGIN { DOCTEST_INFO(__VA_ARGS__); DCOMMENT
LOW3rdparty/doctest.h2621COMMENT
LOW3rdparty/doctest.h2641#define DOCTEST_ADD_FAIL_CHECK_AT(file, line, ...) (static_cast<void>(0))COMMENT
LOW3rdparty/doctest.h2681#define DOCTEST_REQUIRE_EQ(...) [&] { return doctest::detail::eq(__VA_ARGS__); }()COMMENT
LOW3rdparty/doctest.h2701#define DOCTEST_CHECK_UNARY_FALSE(...) [&] { return !(__VA_ARGS__); }()COMMENT
LOW3rdparty/doctest.h2721#define DOCTEST_CHECK_THROWS(...) [&] { try { __VA_ARGS__; return false; } catch (...) { return true; } }()COMMENT
LOW3rdparty/doctest.h2741COMMENT
LOW3rdparty/doctest.h2761#define DOCTEST_WARN_NE(...) DOCTEST_FUNC_EMPTYCOMMENT
LOW3rdparty/doctest.h2781#define DOCTEST_CHECK_UNARY_FALSE(...) DOCTEST_FUNC_EMPTYCOMMENT
LOW3rdparty/doctest.h2801COMMENT
LOW3rdparty/doctest.h2821COMMENT
LOW3rdparty/doctest.h2841#undef DOCTEST_REQUIRE_LECOMMENT
LOW3rdparty/doctest.h2861#define DOCTEST_CHECK_THROWS(...) DOCTEST_EXCEPTION_EMPTY_FUNCCOMMENT
LOW3rdparty/doctest.h2881#define DOCTEST_REQUIRE_THROWS_AS_MESSAGE(expr, ex, ...) DOCTEST_EXCEPTION_EMPTY_FUNCCOMMENT
LOW3rdparty/doctest.h2901#define DOCTEST_FAST_REQUIRE_NE DOCTEST_REQUIRE_NECOMMENT
LOW3rdparty/doctest.h2921COMMENT
LOW3rdparty/doctest.h2941COMMENT
LOW3rdparty/doctest.h2961#define ADD_FAIL_CHECK_AT(file, line, ...) DOCTEST_ADD_FAIL_CHECK_AT(file, line, __VA_ARGS__)COMMENT
LOW3rdparty/doctest.h2981#define CHECK_NOTHROW(...) DOCTEST_CHECK_NOTHROW(__VA_ARGS__)COMMENT
LOW3rdparty/doctest.h3001#define CHECK_THROWS_WITH_MESSAGE(expr, with, ...) DOCTEST_CHECK_THROWS_WITH_MESSAGE(expr, with, __VA_ARGS__)COMMENT
LOW3rdparty/doctest.h3021COMMENT
LOW3rdparty/doctest.h3041#define CHECK_UNARY(...) DOCTEST_CHECK_UNARY(__VA_ARGS__)COMMENT
LOW3rdparty/doctest.h3061#define FAST_CHECK_GE(...) DOCTEST_FAST_CHECK_GE(__VA_ARGS__)COMMENT
LOW3rdparty/doctest.h3161#endif // __BORLANDC__COMMENT
LOW3rdparty/doctest.h3181#define DOCTEST_LOCK_MUTEX(name) std::lock_guard<std::mutex> DOCTEST_ANONYMOUS(DOCTEST_ANON_LOCK_)(name);COMMENT
LOW3rdparty/doctest.h3201#include <sys/sysctl.h>COMMENT
LOW3rdparty/doctest.h3221#endifCOMMENT
LOW3rdparty/doctest.h3241COMMENT
LOW3rdparty/doctest.h3261#define DOCTEST_MULTI_LANE_ATOMICS_THREAD_LANES 32COMMENT
27 more matches not shown…
Unused Imports3 hits · 3 pts
SeverityFileLineSnippetContext
LOWtests/manual/perf-heaptrack.py17CODE
LOWtests/manual/perf-heaptrack.py19CODE
LOWtests/manual/perf-heaptrack.py23CODE
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMsrc/analyze/accumulatedtracedata.cpp564// replace by std::identity once we can leverage C++20COMMENT
Fake / Example Data2 hits · 2 pts
SeverityFileLineSnippetContext
LOW3rdparty/robin-map/README.md255 map.insert({employee(1, "John Doe"), 2001});CODE
LOW3rdparty/robin-map/README.md256 map.insert({employee(2, "Jane Doe"), 2002});CODE