AI Slop Code Risk Monitor

async-profiler/async-profiler

SlopCodeMonitor badge for async-profiler/async-profiler Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

Sampling CPU and HEAP profiler for Java featuring AsyncGetCallTrace + perf_events

1.2 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for async-profiler/async-profiler, a C++ project with 9,181 GitHub stars. SynthScan examined 53,837 lines of code across 366 source files, recording 62 pattern matches distributed across 2 syntactic categories. The legacy adjusted pattern signal is 1.2 (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.2
Adjusted Signal
1.2
Raw Pattern Score
100%
Time Factor
2026-10-27
Last Push
9.2K
Stars
C++
Language
53.8K
Lines of Code
366
Files
62
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 5.6/100 · LOW

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

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

PR Review Velocity Impact 5.6/100 · LOW

Which changes need focused human review? 62 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 0LOW 62

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 62 distinct pattern matches across 2 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 Block50 hits · 50 pts
SeverityFileLineSnippetContext
LOWtest/native/testRunner.hpp101 } \COMMENT
LOWtest/test/nonjava/non_java_app.cpp1/*COMMENT
LOWtest/test/nativemem/profile_with_dlopen.c1/*COMMENT
LOW.assets/html/flamegraph.html21 dl.hotkeys > dt {float: left; clear: left; width: 158px; margin-right: 4px; text-align: right}COMMENT
LOWsrc/ctimer_linux.cpp1/*COMMENT
LOWsrc/instrument.cpp1/*COMMENT
LOWsrc/stackFrame_x64.cpp141 // JDK 17+COMMENT
LOWsrc/symbols_linux.cpp1/*COMMENT
LOWsrc/symbols_linux.cpp21#include <link.h>COMMENT
LOWsrc/symbols_linux.cpp181# define R_ABS64 R_X86_64_64COMMENT
LOWsrc/asprof.h1/*COMMENT
LOWsrc/asprof.h41// This API is UNSTABLE and might change or be removed in the next version of async-profiler.COMMENT
LOWsrc/asprof.h61//COMMENT
LOWsrc/asprof.h81COMMENT
LOWsrc/arguments.cpp1/*COMMENT
LOWsrc/profiler.cpp1/*COMMENT
LOWsrc/profiler.cpp21#include "mallocTracer.h"COMMENT
LOWsrc/rustDemangle.h41 // Contains the part after the mangled name that is to be outputted,COMMENT
LOWsrc/rustDemangle.h61/// This function is `O(n)` in the length of the input + *output* [$], but the demangled output of demangling a symbol cCOMMENT
LOWsrc/mallocTracer.cpp1/*COMMENT
LOWsrc/wallClock.cpp1/*COMMENT
LOWsrc/os_linux.cpp1/*COMMENT
LOWsrc/os_linux.cpp21#include <sys/sendfile.h>COMMENT
LOWsrc/safeAccess.cpp1/*COMMENT
LOWsrc/perfEvents_linux.cpp1/*COMMENT
LOWsrc/perfEvents_linux.cpp21#include <sys/syscall.h>COMMENT
LOWsrc/os_macos.cpp1/*COMMENT
LOWsrc/stackFrame_aarch64.cpp1/*COMMENT
LOWsrc/stackFrame_aarch64.cpp181 // Check if there is such an instruction anywhere betweenCOMMENT
LOWsrc/stackFrame_aarch64.cpp221 pc = ((uintptr_t*)sp)[-1];COMMENT
LOWsrc/stackFrame_aarch64.cpp241 //COMMENT
LOWsrc/rustDemangle.cpp1/*COMMENT
LOWsrc/j9StackTraces.cpp1/*COMMENT
LOWsrc/symbols_macos.cpp1/*COMMENT
LOWsrc/flightRecorder.cpp1/*COMMENT
LOWsrc/flightRecorder.cpp21#include "jfrMetadata.h"COMMENT
LOWsrc/hooks.cpp1/*COMMENT
LOWsrc/frameName.h1/*COMMENT
LOWsrc/profiler.h1/*COMMENT
LOWsrc/vmEntry.cpp1/*COMMENT
LOWsrc/fdtransferClient_linux.cpp1/*COMMENT
LOWsrc/arch.h1/*COMMENT
LOWsrc/arch.h181#endifCOMMENT
LOWsrc/res/flame.html21 dl.hotkeys > dt {float: left; clear: left; width: 158px; margin-right: 4px; text-align: right}COMMENT
LOWsrc/jattach/jattach_hotspot.c1/*COMMENT
LOWsrc/jattach/psutil.c1/*COMMENT
LOWsrc/jattach/jattach_openj9.c1/*COMMENT
LOWsrc/jattach/psutil.h21void get_tmp_path(int pid);COMMENT
LOWsrc/main/fdtransferServer_linux.cpp1/*COMMENT
LOWsrc/main/main.cpp1/*COMMENT
Hyper-Verbose Identifiers12 hits · 12 pts
SeverityFileLineSnippetContext
LOWsrc/res/heatmap.html1978 function prepareFramesReversedDiff(from, to, baseFrom, baseTo) {CODE
LOWsrc/res/heatmap.html2513 function prepareTheOnlyChunksReversed(ctx) {CODE
LOWsrc/res/heatmap.html2584 function prepareBaseTheOnlyChunksReversed(ctx) {CODE
LOWsrc/res/heatmap.html2767 function prepareDirectSamplesReversed(ctx) {CODE
LOWsrc/res/heatmap.html2812 function prepareDirectSamplesReversedDiff(ctx) {CODE
LOWsrc/res/heatmap.html2895 function prepareBaseDirectSamplesReversed(ctx) {CODE
LOWsrc/res/heatmap.html3090 function splitTheOnlyChunksReversed(ctx) {CODE
LOWsrc/res/heatmap.html3148 function splitBaseTheOnlyChunksReversed(ctx) {CODE
LOWsrc/res/heatmap.html3329 function splitDirectSamplesReversed(ctx) {CODE
LOWsrc/res/heatmap.html3374 function splitDirectSamplesReversedDiff(ctx) {CODE
LOWsrc/res/heatmap.html3474 function splitBaseDirectSamplesReversed(ctx) {CODE
LOWsrc/res/heatmap.html3548 function cleanupMethodBuffersReversed(ctx) {CODE