AI Slop Code Risk Monitor

tindy2013/subconverter

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

Utility to convert between various subscription format

2.9 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for tindy2013/subconverter, a C++ project with 17,110 GitHub stars. SynthScan examined 70,636 lines of code across 160 source files, recording 307 pattern matches distributed across 4 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-07-09
Last Push
17.1K
Stars
C++
Language
70.6K
Lines of Code
160
Files
307
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 13.5/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 306 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? 1 finding(s).

PR Review Velocity Impact 19.6/100 · LOW

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

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 307 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 Block304 hits · 201 pts
SeverityFileLineSnippetContext
LOWinclude/httplib.h1//COMMENT
LOWinclude/httplib.h21#ifndef CPPHTTPLIB_KEEPALIVE_MAX_COUNTCOMMENT
LOWinclude/httplib.h41#ifndef CPPHTTPLIB_WRITE_TIMEOUT_SECONDCOMMENT
LOWinclude/httplib.h61#ifndef CPPHTTPLIB_REQUEST_URI_MAX_LENGTHCOMMENT
LOWinclude/httplib.h81#ifndef CPPHTTPLIB_FORM_URL_ENCODED_PAYLOAD_MAX_LENGTHCOMMENT
LOWinclude/httplib.h101 : 0))COMMENT
LOWinclude/httplib.h121#ifndef _CRT_SECURE_NO_WARNINGSCOMMENT
LOWinclude/httplib.h141#endif // _MSC_VERCOMMENT
LOWinclude/httplib.h161#endifCOMMENT
LOWinclude/httplib.h181#define NI_MAXHOST 1025COMMENT
LOWinclude/httplib.h201COMMENT
LOWinclude/httplib.h221#include <iostream>COMMENT
LOWinclude/httplib.h241// these are defined in wincrypt.h and it breaks compilation if BoringSSL isCOMMENT
LOWinclude/httplib.h261#include <openssl/evp.h>COMMENT
LOWinclude/jpcre2.hpp41 * manually. In this case you will have to define `PCRE2_CODE_UNIT_WIDTH` before including `pcre2.h`.COMMENT
LOWinclude/jpcre2.hpp61//previous inclusion of pcre2.h will be respected and we won't try to include it twice.COMMENT
LOWinclude/jpcre2.hpp81 #define JPCRE2_USE_MINIMUM_CXX_17 1COMMENT
LOWinclude/jpcre2.hpp301 mcontext, replacement, rlength, outputbuffer, outlengthptr);COMMENT
LOWinclude/jpcre2.hpp361 //~ static Pcre2Type<8>::JitStack *jit_stack_create(PCRE2_SIZE startsize, PCRE2_SIZE maxsize,COMMENT
LOWinclude/jpcre2.hpp421 PCRE2_SIZE rlength,COMMENT
LOWinclude/jpcre2.hpp481 //~ Pcre2Type<16>::JitCallback callback_function,COMMENT
LOWinclude/jpcre2.hpp601 static int set_newline(Pcre2Type<32>::CompileContext *ccontext, uint32_t value){COMMENT
LOWinclude/jpcre2.hpp621 //~ }COMMENT
LOWinclude/jpcre2.hpp981 ///@param jo pointer to JPCRE2 match option that will be modified.COMMENT
LOWinclude/jpcre2.hpp1001 ///@param x whether to add or remove the modifers.COMMENT
LOWinclude/jpcre2.hpp1201//specializationCOMMENT
LOWinclude/jpcre2.hpp1221///If you want to be specific, then here's the rule:COMMENT
LOWinclude/jpcre2.hpp1241#elseCOMMENT
LOWinclude/jpcre2.hpp1261 #ifdef JPCRE2_USE_MINIMUM_CXX_11COMMENT
LOWinclude/jpcre2.hpp1321 ///@overloadCOMMENT
LOWinclude/jpcre2.hpp1501COMMENT
LOWinclude/jpcre2.hpp1521 deepMove(rm);COMMENT
LOWinclude/jpcre2.hpp1601 ///@see RegexReplace::getSubject()COMMENT
LOWinclude/jpcre2.hpp1701 return vec_ntn;COMMENT
LOWinclude/jpcre2.hpp1721 vec_num = v;COMMENT
LOWinclude/jpcre2.hpp1861 ///Set the match context.COMMENT
LOWinclude/jpcre2.hpp1881 ///User will be responsible for freeing the memory of the match data block.COMMENT
LOWinclude/jpcre2.hpp1901 /// You can get the message with RegexMatch::getErrorMessage() function.COMMENT
LOWinclude/jpcre2.hpp1921 jpcre2_match_opts = x ? jpcre2_match_opts | opt : jpcre2_match_opts & ~opt;COMMENT
LOWinclude/jpcre2.hpp1941 /// @see Regex::addModifier()COMMENT
LOWinclude/jpcre2.hpp1981 ///If you are using lambda function with capture, you must use the `std::function` approach.COMMENT
LOWinclude/jpcre2.hpp2001 /// //Examples with lambda (>=C++11)COMMENT
LOWinclude/jpcre2.hpp2021 ///This class does not allow object instantiation.COMMENT
LOWinclude/jpcre2.hpp2041 ///a MatchEvaluator object with its default constructor:COMMENT
LOWinclude/jpcre2.hpp2061 #endifCOMMENT
LOWinclude/jpcre2.hpp2081 ///COMMENT
LOWinclude/jpcre2.hpp2101 /// In such cases, previous Match data can not be used to perform a new replacment operation with this second callbaCOMMENT
LOWinclude/jpcre2.hpp2121 /// //In above, nreplace() populates jp::NumSub and jp::MapNtn with match data.COMMENT
LOWinclude/jpcre2.hpp2161 typename MatchEvaluatorCallback<void*, MapNas const &, void*>::Callback callback2;COMMENT
LOWinclude/jpcre2.hpp2281 /// .nreplace();COMMENT
LOWinclude/jpcre2.hpp2441COMMENT
LOWinclude/jpcre2.hpp2461 callback1 = mef;COMMENT
LOWinclude/jpcre2.hpp2481 ///@param mef Callback function.COMMENT
LOWinclude/jpcre2.hpp2501 ///```cppCOMMENT
LOWinclude/jpcre2.hpp2521 ///```cppCOMMENT
LOWinclude/jpcre2.hpp2541 ///@overloadCOMMENT
LOWinclude/jpcre2.hpp2561 return *this;COMMENT
LOWinclude/jpcre2.hpp2581 callback6 = mef;COMMENT
LOWinclude/jpcre2.hpp2761 ///If buffer size proves to be enough to fit the resultant stringCOMMENT
LOWinclude/jpcre2.hpp2841 ///It uses the `MatchEvaluatorCallback` function that was set with a constructor or `MatchEvaluator::setCallbackCOMMENT
244 more matches not shown…
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMinclude/jpcre2.hpp2179 // Also, this approach proved to be more readable and robust.COMMENT
Excessive Try-Catch Wrapping1 hit · 1 pts
SeverityFileLineSnippetContext
LOWscripts/update_rules.py84 except Exception as e:CODE
Deep Nesting1 hit · 1 pts
SeverityFileLineSnippetContext
LOWscripts/update_rules.py45CODE