Home / isocpp / CppCoreGuidelines
AI Slop Code Risk Monitor

isocpp/CppCoreGuidelines

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

The C++ Core Guidelines are a set of tried-and-true guidelines, rules, and best practices about coding in C++

1.8 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for isocpp/CppCoreGuidelines, a CSS project with 45,397 GitHub stars. SynthScan examined 31,861 lines of code across 23 source files, recording 79 pattern matches distributed across 6 syntactic categories. The legacy adjusted pattern signal is 1.8 (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.8
Adjusted Signal
1.8
Raw Pattern Score
100%
Time Factor
2026-10-26
Last Push
45.4K
Stars
CSS
Language
31.9K
Lines of Code
23
Files
79
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 8.0/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.6/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 12.5/100 · LOW

Which changes need focused human review? 79 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 3LOW 76

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 79 distinct pattern matches across 6 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 Block32 hits · 26 pts
SeverityFileLineSnippetContext
LOWCppCoreGuidelines.md9161COMMENT
LOWCppCoreGuidelines.md19721* use case-sensitivity for the header identifier, matching how the header is defined by the standard, specification, impCOMMENT
LOWscripts/python/md-split.py141 result.reverse()COMMENT
LOWscripts/python/cpplint.py1#!/usr/bin/env pythonCOMMENT
LOWscripts/python/cpplint.py2461 # triggered by namespace size only, which works most of the time.COMMENT
LOWscripts/python/cpplint.py2521 # - _ClassInfo: a class or struct.COMMENT
LOWscripts/python/cpplint.py2961 # TODO(unknown): Could it be expanded safely to arbitrary references,COMMENT
LOWscripts/python/cpplint.py3341 # namespace body. In other words, don't issue blank line warningsCOMMENT
LOWscripts/python/cpplint.py3381 # simple heuristic here: If the line is indented 4 spaces; and we have aCOMMENT
LOWscripts/python/cpplint.py3481 # You should always have whitespace around binary operators.COMMENT
LOWscripts/python/cpplint.py3521 # not otherwise (particularly, not when used as streams)COMMENT
LOWscripts/python/cpplint.py3601 """COMMENT
LOWscripts/python/cpplint.py3701 error: The function to call with any errors found.COMMENT
LOWscripts/python/cpplint.py3721 # LOG(INFO) << type{} << " ...";COMMENT
LOWscripts/python/cpplint.py3801 Currently the only thing checked here is blank line before protected/private.COMMENT
LOWscripts/python/cpplint.py4001 linenum: The number of the line to check.COMMENT
LOWscripts/python/cpplint.py4021 # if (...) else {};COMMENT
LOWscripts/python/cpplint.py4041 # {};COMMENT
LOWscripts/python/cpplint.py4061 # warn, specifically:COMMENT
LOWscripts/python/cpplint.py4361 if rhs.find('&&') > -1 or rhs.find('||') > -1:COMMENT
LOWscripts/python/cpplint.py4461 # Don't want to use "raw" either, because we don't want to check inside C++11COMMENT
LOWscripts/python/cpplint.py4721 'Do not include .' + extension + ' files from other packages')COMMENT
LOWscripts/python/cpplint.py4801 position += 1COMMENT
LOWscripts/python/cpplint.py4901 # int operator&(const X& x) { return 42; } // unary operator&COMMENT
LOWscripts/python/cpplint.py5021 r'((?:|static +)(?:|const +))(?::*std::)?string( +const)? +'COMMENT
LOWscripts/python/cpplint.py5141 if remove_function_body:COMMENT
LOWscripts/python/cpplint.py5201 # of these forms:COMMENT
LOWscripts/python/cpplint.py5241 # Check for non-const references in function parameters. A single '&' mayCOMMENT
LOWscripts/python/cpplint.py5321 # Parameterless conversion functions, such as bool(), are allowed as they areCOMMENT
LOWscripts/python/cpplint.py5381 CheckCStyleCast(filename, clean_lines, linenum, 'reinterpret_cast',COMMENT
LOWscripts/python/cpplint.py5721 # For Emacs's flymake.COMMENT
LOWscripts/python/cpplint.py6261 if filename != '-' and file_extension not in GetAllExtensions():COMMENT
Deep Nesting31 hits · 16 pts
SeverityFileLineSnippetContext
LOWscripts/python/md-split.py17CODE
LOWscripts/python/cpplint.py683CODE
LOWscripts/python/cpplint.py1355CODE
LOWscripts/python/cpplint.py1383CODE
LOWscripts/python/cpplint.py1458CODE
LOWscripts/python/cpplint.py1689CODE
LOWscripts/python/cpplint.py1811CODE
LOWscripts/python/cpplint.py2089CODE
LOWscripts/python/cpplint.py2888CODE
LOWscripts/python/cpplint.py3157CODE
LOWscripts/python/cpplint.py3228CODE
LOWscripts/python/cpplint.py3312CODE
LOWscripts/python/cpplint.py3440CODE
LOWscripts/python/cpplint.py3798CODE
LOWscripts/python/cpplint.py3876CODE
LOWscripts/python/cpplint.py4143CODE
LOWscripts/python/cpplint.py4270CODE
LOWscripts/python/cpplint.py4420CODE
LOWscripts/python/cpplint.py4753CODE
LOWscripts/python/cpplint.py5169CODE
LOWscripts/python/cpplint.py5308CODE
LOWscripts/python/cpplint.py5657CODE
LOWscripts/python/cpplint.py6106CODE
LOWscripts/python/cpplint.py6313CODE
LOWscripts/python/cpplint.py6414CODE
LOWscripts/python/cpplint.py910CODE
LOWscripts/python/cpplint.py1077CODE
LOWscripts/python/cpplint.py1264CODE
LOWscripts/python/cpplint.py1622CODE
LOWscripts/python/cpplint.py2633CODE
LOWscripts/python/cpplint.py2690CODE
AI Slop Vocabulary2 hits · 4 pts
SeverityFileLineSnippetContext
MEDIUMscripts/python/cpplint_wrap.py1## wraps local cpplint to produce verbose output without code harnessCOMMENT
LOWscripts/python/cpplint.py2680 # Here we can just use a shallow copy since we are the lastCOMMENT
Unused Imports4 hits · 4 pts
SeverityFileLineSnippetContext
LOWscripts/python/md-split.py6CODE
LOWscripts/python/md-split.py6CODE
LOWscripts/python/md-split.py6CODE
LOWscripts/python/md-split.py9CODE
Self-Referential Comments2 hits · 4 pts
SeverityFileLineSnippetContext
MEDIUMscripts/python/cpplint.py1107 # Create a testcase for each fileCOMMENT
MEDIUMscripts/python/cpplint.py5696 # The following function is just a speed up, no semantics are changed.STRING
Redundant / Tautological Comments8 hits · 3 pts
SeverityFileLineSnippetContext
LOWscripts/python/cpplint.py2614 # Check if token is an unmatched '<'.COMMENT
LOWscripts/python/cpplint.py3240 # Check if the // may be in quotes. If so, ignore itSTRING
LOWscripts/python/cpplint.py4226 # Check if the body is emptySTRING
LOWscripts/python/cpplint.py4507 # Check if the line is a header guard.STRING
LOWscripts/python/cpplint.py4886 # Check if people are using the verboten C basic types. The only exceptionSTRING
LOWscripts/python/cpplint.py4898 # Check if some verboten operator overloading is going onSTRING
LOWscripts/python/cpplint.py5079 # Check if some verboten C functions are being used.STRING
LOWscripts/python/cpplint.py5839 # Set end_col to check whole lines after we are done with theSTRING