AI Slop Code Risk Monitor

aristocratos/btop

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

A monitor of resources

2.9 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for aristocratos/btop, a C++ project with 35,191 GitHub stars. SynthScan examined 52,472 lines of code across 81 source files, recording 137 pattern matches distributed across 7 syntactic categories. The legacy adjusted pattern signal is 2.9 (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.9
Adjusted Signal
2.9
Raw Pattern Score
100%
Time Factor
2026-10-28
Last Push
35.2K
Stars
C++
Language
52.5K
Lines of Code
81
Files
137
Pattern Hits
2026-10-31
Scan Date
0.01
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 13.2/100 · LOW

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

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

PR Review Velocity Impact 13.0/100 · LOW

Which changes need focused human review? 137 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 1MEDIUM 2LOW 134

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 137 distinct pattern matches across 7 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 Block126 hits · 126 pts
SeverityFileLineSnippetContext
LOWCHANGELOG.md1## v1.4.8COMMENT
LOWCHANGELOG.md21COMMENT
LOWCHANGELOG.md41#1445 | fix: remove busy waiting when checking runner thread state | @deckstoseCOMMENT
LOWCHANGELOG.md61#1272 | Skip 'H' and 'HX' suffix in AMD cpu name trimming | @ramdomPTMCOMMENT
LOWCHANGELOG.md81#1306 | Implement feat Process list pausing | @vandabbinCOMMENT
LOWCHANGELOG.md101COMMENT
LOWCHANGELOG.md141f1482fe | Fix process arguments appearing outside proc box by replacing ASCII control codes with blankspace, issue #1080COMMENT
LOWCHANGELOG.md161#1098 | Use XDG_STATE_HOME to save logs | @imwintsCOMMENT
LOWCHANGELOG.md20197d2fb5 | Fixed missing IO graphs in IO mode, issue #867 | @aristocratosCOMMENT
LOWinclude/fmt/ostream.h1// Formatting library for C++ - std::ostream supportCOMMENT
LOWinclude/fmt/ostream.h21#endifCOMMENT
LOWinclude/fmt/format-inl.h1// Formatting library for C++ - implementationCOMMENT
LOWinclude/fmt/format-inl.h21#endifCOMMENT
LOWinclude/fmt/format-inl.h221COMMENT
LOWinclude/fmt/format-inl.h1301 // Compute zi and deltai.COMMENT
LOWinclude/fmt/ranges.h1// Formatting library for C++ - range and tuple supportCOMMENT
LOWinclude/fmt/xchar.h1// Formatting library for C++ - optional wchar_t and exotic character supportCOMMENT
LOWinclude/fmt/core.h1// This file is only provided for compatibility and may be removed in futureCOMMENT
LOWinclude/fmt/chrono.h1// Formatting library for C++ - chrono supportCOMMENT
LOWinclude/fmt/chrono.h21#endifCOMMENT
LOWinclude/fmt/chrono.h221}COMMENT
LOWinclude/fmt/chrono.h241#endifCOMMENT
LOWinclude/fmt/chrono.h541COMMENT
LOWinclude/fmt/os.h1// Formatting library for C++ - optional OS-specific functionalityCOMMENT
LOWinclude/fmt/os.h21# endifCOMMENT
LOWinclude/fmt/os.h41#ifndef FMT_POSIXCOMMENT
LOWinclude/fmt/color.h241 // │23│─┘COMMENT
LOWinclude/fmt/color.h261 // │62│─┬── unusedCOMMENT
LOWinclude/fmt/args.h1// Formatting library for C++ - dynamic argument listsCOMMENT
LOWinclude/fmt/printf.h1// Formatting library for C++ - legacy printf implementationCOMMENT
LOWinclude/fmt/compile.h1// Formatting library for C++ - experimental format string compilationCOMMENT
LOWinclude/fmt/format.h41#include "base.h"COMMENT
LOWinclude/fmt/format.h61# include <bit> // std::bit_castCOMMENT
LOWinclude/fmt/format.h81# define FMT_USE_NONTYPE_TEMPLATE_ARGS 1COMMENT
LOWinclude/fmt/format.h101 defined(__INTEL_RTTI__) || defined(__RTTI)COMMENT
LOWinclude/fmt/format.h121#ifdef FMT_DEPRECATEDCOMMENT
LOWinclude/fmt/format.h141# elseCOMMENT
LOWinclude/fmt/format.h161 using difference_type =COMMENT
LOWinclude/fmt/format.h201# if FMT_HAS_BUILTIN(__builtin_clz) || FMT_GCC_VERSION || FMT_ICC_VERSIONCOMMENT
LOWinclude/fmt/format.h701 !std::is_same<T, wchar_t>::value>;COMMENT
LOWinclude/fmt/format.h3301 write2digits(buffer + number_of_digits_printed, digits);COMMENT
LOWinclude/fmt/std.h1// Formatting library for C++ - formatters for standard library typesCOMMENT
LOWinclude/fmt/std.h21# include <thread>COMMENT
LOWinclude/fmt/std.h41# if FMT_CPLUSPLUS > 201703L && FMT_HAS_INCLUDE(<source_location>)COMMENT
LOWinclude/fmt/std.h61#endifCOMMENT
LOWinclude/fmt/base.h1// Formatting library for C++ - the base API for char/UTF-8COMMENT
LOWinclude/fmt/base.h21#endifCOMMENT
LOWinclude/fmt/base.h41#elseCOMMENT
LOWinclude/fmt/base.h61COMMENT
LOWinclude/fmt/base.h81#elseCOMMENT
LOWinclude/fmt/base.h101// https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66297.COMMENT
LOWinclude/fmt/base.h121#elif FMT_GLIBCXX_RELEASE && FMT_GLIBCXX_RELEASE < 10COMMENT
LOWinclude/fmt/base.h141# define FMT_CONSTEXPR20COMMENT
LOWinclude/fmt/base.h161# define FMT_CATCH(x) if (false)COMMENT
LOWinclude/fmt/base.h181# define FMT_FALLTHROUGH [[clang::fallthrough]]COMMENT
LOWinclude/fmt/base.h201# define FMT_NODISCARDCOMMENT
LOWinclude/fmt/base.h221#elseCOMMENT
LOWinclude/fmt/base.h241# define FMT_ALWAYS_INLINE inline __attribute__((always_inline))COMMENT
LOWinclude/fmt/base.h261#ifndef FMT_EXPORTCOMMENT
LOWinclude/fmt/base.h281#endifCOMMENT
66 more matches not shown…
Synthetic Comment Markers1 hit · 8 pts
SeverityFileLineSnippetContext
HIGHCONTRIBUTING.md15## AI generated codeCOMMENT
Verbosity Indicators3 hits · 4 pts
SeverityFileLineSnippetContext
LOWinclude/fmt/format-inl.h1264 // Step 1: integer promotion & Schubfach multiplier calculation.COMMENT
LOWinclude/fmt/format-inl.h1319 // Step 2: Try larger divisor; remove trailing zeros if necessary.COMMENT
LOWinclude/fmt/format-inl.h1351 // Step 3: Find the significand with the smaller divisor.COMMENT
Structural Annotation Overuse3 hits · 4 pts
SeverityFileLineSnippetContext
LOWinclude/fmt/format-inl.h1264 // Step 1: integer promotion & Schubfach multiplier calculation.COMMENT
LOWinclude/fmt/format-inl.h1319 // Step 2: Try larger divisor; remove trailing zeros if necessary.COMMENT
LOWinclude/fmt/format-inl.h1351 // Step 3: Find the significand with the smaller divisor.COMMENT
AI Slop Vocabulary2 hits · 4 pts
SeverityFileLineSnippetContext
MEDIUMinclude/fmt/format.h3347 // Compilers are not aware of how to leverage the maximum value ofCOMMENT
LOWsrc/linux/intel_gpu_top/intel_chipset.h112/* Exclude chipset #defines, they just add noise */COMMENT
Decorative Section Separators1 hit · 2 pts
SeverityFileLineSnippetContext
MEDIUMsrc/btop.cpp95 {"#000000", "╚═════╝ ╚═╝ ╚═════╝ ╚═╝"},CODE
Slop Phrases1 hit · 2 pts
SeverityFileLineSnippetContext
LOWsrc/linux/intel_gpu_top/drm_mode.h86 * When adding a new stereo mode don't forget to adjust DRM_MODE_FLAGS_3D_MAXCOMMENT