1.5

Adjusted Signal

1.5

Raw Pattern Score

100%

Time Factor

2026-10-31

Last Push

6.0K

Stars

Java

Language

204.7K

Lines of Code

1.2K

Files

121

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 2.8/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 2.3/100 · LOW

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

Agent Over-Engineering Ratio 2.6/100 · LOW

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

PR Review Velocity Impact 7.2/100 · LOW

Which changes need focused human review? 121 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 7HIGH 1MEDIUM 58LOW 55

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 121 distinct pattern matches across 12 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.

Decorative Section Separators43 hits · 101 pts

Severity	File	Line	Snippet	Context
MEDIUM	…nal/superpowers/plans/2026-05-03-btrace-utils-split.md	1050	// ── StringsService ──────────────────────────────────────────────────	COMMENT
MEDIUM	…nal/superpowers/plans/2026-05-03-btrace-utils-split.md	1104	// ── NumbersService ──────────────────────────────────────────────────	COMMENT
MEDIUM	…nal/superpowers/plans/2026-05-03-btrace-utils-split.md	1140	// ── TimeService ─────────────────────────────────────────────────────	COMMENT
MEDIUM	…nal/superpowers/plans/2026-05-03-btrace-utils-split.md	1153	// ── ReferencesService ───────────────────────────────────────────────	COMMENT
MEDIUM	docs/architecture/ExtensionInvokeDynamicBridge.md	75	│ │ // Load extension │─┼──────────────────────────┘	CODE
MEDIUM	.github/workflows/release.yml	74	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	76	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	166	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	168	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	290	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	292	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	436	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	438	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	515	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	517	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	588	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	590	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	638	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	640	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	703	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	705	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	774	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	776	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	814	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	816	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	878	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	880	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	983	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	985	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	1082	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	1084	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	1178	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	1180	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	1218	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	1220	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	1257	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	1259	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	1308	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	1310	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	1386	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	1388	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	1455	# ============================================================	COMMENT
MEDIUM	.github/workflows/release.yml	1457	# ============================================================	COMMENT

Hallucination Indicators7 hits · 95 pts

Severity	File	Line	Snippet	Context
CRITICAL	…test/java/io/btrace/qe/generate/CaseGeneratorTest.java	224	org.junit.jupiter.api.Assertions.assertThrows(	CODE
CRITICAL⚡	…va/io/btrace/instr/BTraceTransformerEarlyExitTest.java	133	org.junit.jupiter.api.Assertions.assertFalse(	CODE
CRITICAL⚡	…va/io/btrace/instr/BTraceTransformerEarlyExitTest.java	136	org.junit.jupiter.api.Assertions.assertFalse(	CODE
CRITICAL⚡	…va/io/btrace/instr/BTraceTransformerEarlyExitTest.java	139	org.junit.jupiter.api.Assertions.assertFalse(	CODE
CRITICAL⚡	…va/io/btrace/instr/BTraceTransformerEarlyExitTest.java	142	org.junit.jupiter.api.Assertions.assertTrue(	CODE
CRITICAL⚡	…va/io/btrace/instr/BTraceTransformerEarlyExitTest.java	145	org.junit.jupiter.api.Assertions.assertTrue(	CODE
CRITICAL	…t/src/main/java/io/btrace/instr/BTraceTransformer.java	210	org.objectweb.asm.util.CheckClassAdapter.verify(	CODE

Structural Annotation Overuse22 hits · 38 pts

Severity	File	Line	Snippet	Context
LOW⚡	docs/Troubleshooting.md	695	// Step 1: Verify attachment	COMMENT
LOW⚡	docs/Troubleshooting.md	701	// Step 2: Verify class matching	COMMENT
LOW⚡	docs/Troubleshooting.md	707	// Step 3: Add specific logic	COMMENT
LOW	docs/GettingStarted.md	154	### Step 1: Prepare a Test Application	COMMENT
LOW	docs/GettingStarted.md	187	### Step 2: Create Your First BTrace Script	COMMENT
LOW	docs/GettingStarted.md	209	### Step 3: Attach BTrace to the Running Application	COMMENT
LOW⚡	docs/OnelinerGuide.md	403	# Step 1: Find which class	COMMENT
LOW⚡	docs/OnelinerGuide.md	406	# Step 2: Focus on specific class	COMMENT
LOW⚡	docs/OnelinerGuide.md	409	# Step 3: Drill into specific method	COMMENT
LOW	docs/tutorials/12-production-safe-attach.md	24	## Step 1 - Start a JVM in prepared mode	COMMENT
LOW	docs/tutorials/12-production-safe-attach.md	51	## Step 2 - Ask the doctor, and read every line	COMMENT
LOW	docs/tutorials/12-production-safe-attach.md	96	## Step 3 - See what "not ready" looks like	COMMENT
LOW	docs/tutorials/12-production-safe-attach.md	135	## Step 4 - Attach with no flags and watch the cost	COMMENT
LOW	docs/tutorials/12-production-safe-attach.md	169	## Step 5 - Leave, and watch the number come back	COMMENT
LOW	docs/tutorials/12-production-safe-attach.md	189	## Step 6 - Clean up	COMMENT
LOW	docs/tutorials/10-whats-new-for-2x-users.md	26	## Step 1 - Start the patient	COMMENT
LOW	docs/tutorials/10-whats-new-for-2x-users.md	42	## Step 2 - Oneliners: no file, no compile	COMMENT
LOW	docs/tutorials/10-whats-new-for-2x-users.md	97	## Step 3 - From oneliner to a flat-DSL script	COMMENT
LOW	docs/tutorials/10-whats-new-for-2x-users.md	131	## Step 4 - Your compiled 2.x probes just work	COMMENT
LOW	docs/tutorials/10-whats-new-for-2x-users.md	161	## Step 5 - Your source scripts need one line	COMMENT
LOW	docs/tutorials/10-whats-new-for-2x-users.md	270	## Step 7 - Run `btrace doctor` before attaching to anything you do not own	COMMENT
LOW	docs/tutorials/10-whats-new-for-2x-users.md	303	## Step 8 - Clean up	COMMENT

Modern AI Meta-Vocabulary10 hits · 29 pts

Severity	File	Line	Snippet	Context
MEDIUM	internal/blog-drafts/b5-write-your-own-extension.md	9	## The scaffold	COMMENT
MEDIUM	internal/plans/2026-09-25-btrace-qe-agent-phase1.md	100	### Task 1: Module scaffold, source sets, and a working no-op `qe` task	COMMENT
MEDIUM	internal/plans/2026-09-25-btrace-qe-agent-phase1.md	3174	### Task 10: `QeMain` orchestration and property forwarding	COMMENT
MEDIUM	…l/superpowers/specs/2026-05-17-extension-tck-design.md	51	TckEngine.java # orchestrates suites, collects TckResult	CODE
MEDIUM	docs/BTraceTutorial.md	1752	#### 12.2 RAG Pipeline Observability (`btrace-rag-quality`)	COMMENT
MEDIUM	docs/BTraceTutorial.md	1785	##### Full example — RAG pipeline with Pinecone and LangChain4j	COMMENT
MEDIUM	docs/tutorials/11-ai-workload-observability.md	1	# Watch Your RAG Pipeline and Your Models	COMMENT
MEDIUM	demos/05-rag-and-inference/run.sh	2	# Demo 05 - RAG and inference observability.	COMMENT
MEDIUM	demos/05-rag-and-inference/run.sh	3	# Attaches to a running RAG answerer and finds retrievals that silently return nothing, using the	COMMENT
MEDIUM	demos/05-rag-and-inference/README.md	1	# Demo 05 - RAG and inference observability	COMMENT

Over-Commented Block15 hits · 14 pts

Severity	File	Line	Snippet	Context
LOW	…ntime/src/main/java/io/btrace/runtime/ProbeAnchor.java	81	* <pre>public final class <internalName> { public <init>() { super(); } }</pre>	COMMENT
LOW	btrace-agent/src/test/btrace/onmethod/NoArgs.java	41		COMMENT
LOW	…ace-agent/src/test/btrace/onmethod/leveled/NoArgs.java	41	}	COMMENT
LOW	…s/superpowers/plans/2026-07-12-checklines-migration.md	321		COMMENT
LOW	…src/main/java/io/btrace/extension/ExtensionLoader.java	81		COMMENT
LOW	…gent-benchmark/src/jmh/java/benchmark/BTraceBench.java	201	// @Benchmark	COMMENT
LOW	…gent-benchmark/src/jmh/java/benchmark/BTraceBench.java	221	//	COMMENT
LOW	scripts/migrate-btrace-script.sh	1	#!/usr/bin/env bash	COMMENT
LOW	scripts/release.sh	1	#!/usr/bin/env bash	COMMENT
LOW	scripts/resolve-sdkman-java.sh	1	#!/usr/bin/env bash	COMMENT
LOW	.github/workflows/release.yml	1	# BTrace Release Workflow	COMMENT
LOW	.github/workflows/codeql-analysis.yml	1	# For most projects, this workflow file will not need changing; you simply need	COMMENT
LOW	.github/workflows/continuous.yml	101	fail-fast: false	COMMENT
LOW	demos/06-ai-assistant/record-session.sh	1	#!/usr/bin/env bash	COMMENT
LOW	demos/lib/common.sh	1	#!/usr/bin/env bash	COMMENT

AI Slop Vocabulary5 hits · 14 pts

Severity	File	Line	Snippet	Context
MEDIUM	btrace-qe/cases/demos/attach-oneliner-smoke.yaml	9	# ${pid} is the launched target's PID, ${port} a free port the harness reserved for it.	COMMENT
MEDIUM	…rc/main/java/io/btrace/qe/report/MarkdownReporter.java	103	"## All cases\n\n\| id \| surface \| resilience \| conformance \| guidance \| harness error \|\n"	CODE
MEDIUM	.github/workflows/v2-protocol-tests.yml	2	# This workflow runs comprehensive tests for the v2 protocol implementation	COMMENT
MEDIUM	.github/workflows/continuous.yml	210	# Resilience and demo-replay harness (btrace-qe): launches real target JVMs with the masked jar,	COMMENT
MEDIUM	.github/workflows/continuous.yml	212	# Lightweight enough for every push; its self tests cover the harness itself.	COMMENT

Redundant / Tautological Comments8 hits · 10 pts

Severity	File	Line	Snippet	Context
LOW	scripts/release.sh	108	# Check if we have an interactive terminal	COMMENT
LOW	scripts/release.sh	115	# Check if fzf is available	COMMENT
LOW	scripts/release.sh	491	# Check if reference exists	COMMENT
LOW	scripts/release.sh	502	# Check if develop is ancestor of source_ref	COMMENT
LOW	scripts/release.sh	541	# Check if tag already exists	COMMENT
LOW	scripts/release.sh	782	# Check if tag already exists	COMMENT
LOW	.github/workflows/release.yml	1026	# Check if this release should skip auto-generated notes	COMMENT
LOW	.github/workflows/release.yml	1329	# Check if milestone exists	COMMENT

Deep Nesting7 hits · 7 pts

Severity	File	Line	Context
LOW	demos/lib/render-chat.py	79	CODE
LOW	demos/lib/render-chat.py	106	CODE
LOW	demos/lib/render-chat.py	263	CODE
LOW	demos/lib/render-chat.py	310	CODE
LOW	demos/lib/render-chat.py	340	CODE
LOW	demos/lib/render-chat.py	681	CODE
LOW	demos/lib/render-replay.py	148	CODE

Empty Error Handlers1 hit · 5 pts

Severity	File	Line	Snippet	Context
HIGH	demos/lib/render-chat.py	87	except Exception:	CODE

Example Usage Blocks1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	scripts/release.sh	8	# Usage:	COMMENT

Excessive Try-Catch Wrapping1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	demos/lib/render-chat.py	87	except Exception:	CODE

Unused Imports1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	demos/lib/render-replay.py	12		CODE

btraceio/btrace

Open-Source Code Quality, Security and Technical Debt Review