1.1

Adjusted Signal

1.1

Raw Pattern Score

100%

Time Factor

2026-10-31

Last Push

5.8K

Stars

Java

Language

401.1K

Lines of Code

2.0K

Files

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

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

Hallucinated Dependency & Supply Chain Risk 4.2/100 · LOW

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

Agent Over-Engineering Ratio 0.4/100 · LOW

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

PR Review Velocity Impact 4.3/100 · LOW

Which changes need focused human review? 82 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 28HIGH 0MEDIUM 9LOW 45

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 82 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.

Hallucination Indicators28 hits · 345 pts

Severity	File	Line	Snippet	Context
CRITICAL	docs/faq.md	13	at io.lettuce.core.internal.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:80)	CODE
CRITICAL	docs/faq.md	76	at io.lettuce.core.internal.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:80)	CODE
CRITICAL⚡	…ettuce/core/dynamic/ReactiveTypeAdaptersUnitTests.java	154	io.reactivex.rxjava3.core.Single<String> foo = io.reactivex.rxjava3.core.Single.just("foo");	CODE
CRITICAL⚡	…ettuce/core/dynamic/ReactiveTypeAdaptersUnitTests.java	161	io.reactivex.rxjava3.core.Single<String> foo = io.reactivex.rxjava3.core.Single.just("foo");	CODE
CRITICAL⚡	…ettuce/core/dynamic/ReactiveTypeAdaptersUnitTests.java	168	io.reactivex.rxjava3.core.Maybe<String> foo = io.reactivex.rxjava3.core.Maybe.just("foo");	CODE
CRITICAL⚡	…ettuce/core/dynamic/ReactiveTypeAdaptersUnitTests.java	175	io.reactivex.rxjava3.core.Maybe<String> foo = io.reactivex.rxjava3.core.Maybe.just("foo");	CODE
CRITICAL⚡	…ettuce/core/dynamic/ReactiveTypeAdaptersUnitTests.java	182	io.reactivex.rxjava3.core.Maybe<String> foo = io.reactivex.rxjava3.core.Maybe.just("foo");	CODE
CRITICAL⚡	…ettuce/core/dynamic/ReactiveTypeAdaptersUnitTests.java	189	io.reactivex.rxjava3.core.Flowable<String> foo = io.reactivex.rxjava3.core.Flowable.just("foo");	CODE
CRITICAL⚡	…ettuce/core/dynamic/ReactiveTypeAdaptersUnitTests.java	196	io.reactivex.rxjava3.core.Flowable<String> foo = io.reactivex.rxjava3.core.Flowable.just("foo");	CODE
CRITICAL⚡	…ettuce/core/dynamic/ReactiveTypeAdaptersUnitTests.java	203	io.reactivex.rxjava3.core.Flowable<String> foo = io.reactivex.rxjava3.core.Flowable.just("foo");	CODE
CRITICAL⚡	…ettuce/core/dynamic/ReactiveTypeAdaptersUnitTests.java	210	io.reactivex.rxjava3.core.Observable<String> foo = io.reactivex.rxjava3.core.Observable.just("foo");	CODE
CRITICAL⚡	…ettuce/core/dynamic/ReactiveTypeAdaptersUnitTests.java	217	io.reactivex.rxjava3.core.Observable<String> foo = io.reactivex.rxjava3.core.Observable.just("foo");	CODE
CRITICAL⚡	…ettuce/core/dynamic/ReactiveTypeAdaptersUnitTests.java	224	io.reactivex.rxjava3.core.Observable<String> foo = io.reactivex.rxjava3.core.Observable.just("foo");	CODE
CRITICAL⚡	…ettuce/core/dynamic/ReactiveTypeAdaptersUnitTests.java	232	io.reactivex.rxjava3.core.Observable<String> foo = io.reactivex.rxjava3.core.Observable.empty();	CODE
CRITICAL⚡	…ettuce/core/dynamic/ReactiveTypeAdaptersUnitTests.java	240	io.reactivex.rxjava3.core.Observable<String> foo = io.reactivex.rxjava3.core.Observable.just("foo");	CODE
CRITICAL	…io/lettuce/core/support/BoundedAsyncPoolUnitTests.java	84	return io.lettuce.core.internal.Futures.failed(new IllegalStateException());	CODE
CRITICAL	…e/api/consistency/CommandBuilderCoverageUnitTests.java	121	if (io.lettuce.core.protocol.RedisCommand.class.isAssignableFrom(method.getReturnType())) {	CODE
CRITICAL	…/api/consistency/DeviationTableStalenessUnitTests.java	258	if (io.lettuce.core.protocol.RedisCommand.class.isAssignableFrom(method.getReturnType())) {	CODE
CRITICAL	src/test/java/io/lettuce/test/TestFutures.java	68	if (!io.lettuce.core.internal.Futures.awaitAll(TIMEOUT, futures.toArray(new Future[0]))) {	CODE
CRITICAL	…ttuce/scenario/MaintenancePushNotificationMonitor.java	152	return io.lettuce.core.codec.StringCodec.UTF8.decodeKey(buffer);	CODE
CRITICAL	src/main/java/io/lettuce/core/KqueueProvider.java	18	return io.lettuce.core.resource.KqueueProvider.isAvailable();	CODE
CRITICAL	src/main/java/io/lettuce/core/ConnectionBuilder.java	292	if (io.lettuce.core.resource.EpollProvider.isAvailable()) {	CODE
CRITICAL	src/main/java/io/lettuce/core/EpollProvider.java	18	return io.lettuce.core.resource.EpollProvider.isAvailable();	CODE
CRITICAL	…java/io/lettuce/core/dynamic/ReactiveTypeAdapters.java	641	return io.reactivex.rxjava3.core.Single.fromPublisher(source);	CODE
CRITICAL	…java/io/lettuce/core/dynamic/ReactiveTypeAdapters.java	655	return io.reactivex.rxjava3.core.Completable.fromPublisher(source);	CODE
CRITICAL	…java/io/lettuce/core/dynamic/ReactiveTypeAdapters.java	669	return io.reactivex.rxjava3.core.Observable.fromPublisher(source);	CODE
CRITICAL	…java/io/lettuce/core/dynamic/ReactiveTypeAdapters.java	795	return io.reactivex.rxjava3.core.Flowable.fromPublisher(source);	CODE
CRITICAL	…java/io/lettuce/core/dynamic/ReactiveTypeAdapters.java	823	return io.reactivex.rxjava3.core.Flowable.fromPublisher(source).singleElement();	CODE

Structural Annotation Overuse22 hits · 42 pts

Severity	File	Line	Snippet	Context
LOW	docs/user-guide/connecting-redis.md	274	### Step 1 - Create a Streaming Credentials Provider	COMMENT
LOW	docs/user-guide/connecting-redis.md	386	### Step 2 - Create a RedisURI with streaming credentials provider	COMMENT
LOW	docs/user-guide/connecting-redis.md	438	#### Step 1 - Add the dependencies	COMMENT
LOW	docs/user-guide/connecting-redis.md	452	### Step 2 - Create Entra ID enabled credentials provider	COMMENT
LOW	docs/user-guide/connecting-redis.md	476	### Step 3 - Enable automatic re-authentication	COMMENT
LOW	docs/user-guide/connecting-redis.md	485	### Step 4 - Connect with Entra ID enabled credentials provider	COMMENT
LOW⚡	…tocol/MaintenanceAwareConnectionWatchdogUnitTests.java	553	// Step 5: Advance clock past expiration (31 seconds)	COMMENT
LOW⚡	…tocol/MaintenanceAwareConnectionWatchdogUnitTests.java	556	// Step 6: New call to same wrappedSupplier should return original address again	COMMENT
LOW⚡	…tocol/MaintenanceAwareConnectionWatchdogUnitTests.java	570	// Step 1: Create wrapped supplier once (same instance used throughout)	COMMENT
LOW⚡	…tocol/MaintenanceAwareConnectionWatchdogUnitTests.java	573	// Step 2: First call should return original address (no rebind set yet)	COMMENT
LOW⚡	…tocol/MaintenanceAwareConnectionWatchdogUnitTests.java	576	// Step 3: Invoke rebind with 30 seconds duration	COMMENT
LOW⚡	…tocol/MaintenanceAwareConnectionWatchdogUnitTests.java	579	// Step 4: New call to same wrappedSupplier should return rebind address	COMMENT
LOW⚡	…tocol/MaintenanceAwareConnectionWatchdogUnitTests.java	582	// Step 5: Advance clock past expiration (31 seconds)	COMMENT
LOW⚡	…tocol/MaintenanceAwareConnectionWatchdogUnitTests.java	585	// Step 6: New call to same wrappedSupplier should return original address again	COMMENT
LOW⚡	…est/java/io/lettuce/scenario/FaultInjectionClient.java	548	// Step 1: Migrate all shards from source node to target node	COMMENT
LOW⚡	…est/java/io/lettuce/scenario/FaultInjectionClient.java	558	// Step 2: Now bind the endpoint to trigger MOVING notification	COMMENT
LOW⚡	…est/java/io/lettuce/scenario/FaultInjectionClient.java	619	// Step 1: Empty the target node first (increased timeout)	COMMENT
LOW⚡	…est/java/io/lettuce/scenario/FaultInjectionClient.java	624	// Step 2: Add delay to let the cluster stabilize, then perform actual migration with longer timeout	COMMENT
LOW	…st/java/io/lettuce/scenario/RedisEnterpriseConfig.java	1158	// Step 1: Restore shard distribution across nodes	COMMENT
LOW	…st/java/io/lettuce/scenario/RedisEnterpriseConfig.java	1225	// Step 2: Restore master/slave roles	COMMENT
LOW	…st/java/io/lettuce/scenario/RedisEnterpriseConfig.java	1257	// Step 3: Restore endpoint bindings	COMMENT
LOW	…st/java/io/lettuce/scenario/RedisEnterpriseConfig.java	1281	// Step 4: Verify final state matches original	COMMENT

Verbosity Indicators17 hits · 34 pts

Severity	File	Line	Snippet	Context
LOW⚡	…tocol/MaintenanceAwareConnectionWatchdogUnitTests.java	553	// Step 5: Advance clock past expiration (31 seconds)	COMMENT
LOW⚡	…tocol/MaintenanceAwareConnectionWatchdogUnitTests.java	556	// Step 6: New call to same wrappedSupplier should return original address again	COMMENT
LOW⚡	…tocol/MaintenanceAwareConnectionWatchdogUnitTests.java	570	// Step 1: Create wrapped supplier once (same instance used throughout)	COMMENT
LOW⚡	…tocol/MaintenanceAwareConnectionWatchdogUnitTests.java	573	// Step 2: First call should return original address (no rebind set yet)	COMMENT
LOW⚡	…tocol/MaintenanceAwareConnectionWatchdogUnitTests.java	576	// Step 3: Invoke rebind with 30 seconds duration	COMMENT
LOW⚡	…tocol/MaintenanceAwareConnectionWatchdogUnitTests.java	579	// Step 4: New call to same wrappedSupplier should return rebind address	COMMENT
LOW⚡	…tocol/MaintenanceAwareConnectionWatchdogUnitTests.java	582	// Step 5: Advance clock past expiration (31 seconds)	COMMENT
LOW⚡	…tocol/MaintenanceAwareConnectionWatchdogUnitTests.java	585	// Step 6: New call to same wrappedSupplier should return original address again	COMMENT
LOW⚡	…est/java/io/lettuce/scenario/FaultInjectionClient.java	548	// Step 1: Migrate all shards from source node to target node	COMMENT
LOW⚡	…est/java/io/lettuce/scenario/FaultInjectionClient.java	558	// Step 2: Now bind the endpoint to trigger MOVING notification	COMMENT
LOW⚡	…est/java/io/lettuce/scenario/FaultInjectionClient.java	619	// Step 1: Empty the target node first (increased timeout)	COMMENT
LOW⚡	…est/java/io/lettuce/scenario/FaultInjectionClient.java	624	// Step 2: Add delay to let the cluster stabilize, then perform actual migration with longer timeout	COMMENT
LOW	…st/java/io/lettuce/scenario/RedisEnterpriseConfig.java	1158	// Step 1: Restore shard distribution across nodes	COMMENT
LOW	…st/java/io/lettuce/scenario/RedisEnterpriseConfig.java	1225	// Step 2: Restore master/slave roles	COMMENT
LOW	…st/java/io/lettuce/scenario/RedisEnterpriseConfig.java	1257	// Step 3: Restore endpoint bindings	COMMENT
LOW	…st/java/io/lettuce/scenario/RedisEnterpriseConfig.java	1281	// Step 4: Verify final state matches original	COMMENT
LOW	…re/failover/AbstractRedisMultiDbConnectionBuilder.java	241	// in both cases we need to check if all failed, and complete the future accordingly.	COMMENT

Decorative Section Separators9 hits · 33 pts

Severity	File	Line	Snippet	Context
MEDIUM	…ttuce/core/commands/StringCommandIntegrationTests.java	558	// ── INCREX ──────────────────────────────────────────	COMMENT
MEDIUM	src/main/java/io/lettuce/core/IncrexArgs.java	29	// ── Static Builder ─────────────────────────────	COMMENT
MEDIUM	src/main/java/io/lettuce/core/IncrexArgs.java	74	// ── Fluent Setters ─────────────────────────────	COMMENT
MEDIUM	src/main/java/io/lettuce/core/IncrexFloatArgs.java	29	// ── Static Builder ─────────────────────────────	COMMENT
MEDIUM	src/main/java/io/lettuce/core/IncrexFloatArgs.java	74	// ── Fluent Setters ─────────────────────────────	COMMENT
MEDIUM⚡	…a/io/lettuce/core/failover/health/HealthCheckImpl.java	247	* T0: Start Check #1 ────────────────────┐	COMMENT
MEDIUM⚡	…a/io/lettuce/core/failover/health/HealthCheckImpl.java	248	* T1: Start Check #2 ──────────┐ │	COMMENT
MEDIUM⚡	…a/io/lettuce/core/failover/health/HealthCheckImpl.java	250	* T3: Check #2 completes ──────┘ │ → status = "Healthy"	COMMENT
MEDIUM⚡	…a/io/lettuce/core/failover/health/HealthCheckImpl.java	251	* T4: Check #1 completes ────────────────┘ → status = "Unhealthy" (STALE!)	COMMENT

Over-Commented Block3 hits · 3 pts

Severity	File	Line	Snippet	Context
LOW	.github/workflows/benchmarks.yml	1	name: Benchmarks	COMMENT
LOW	…e/core/search/RediSearchAggregateIntegrationTests.java	1921	// 3. Filter based on computed values	COMMENT
LOW	…/lettuce/core/commands/BitCommandIntegrationTests.java	441	// Y1 ∨ Y2 ∨ Y3 = all bits 0-7 are set = 11111111	COMMENT

Hyper-Verbose Identifiers2 hits · 2 pts

Severity	File	Line	Snippet	Context
LOW	docs/static/benchmarks/index.html	136	function collectBenchesPerTestCase(entries) {	CODE
LOW	…core/support/http/NettyHttpClientIntegrationTests.java	752	private static class NoResponseHandler extends SimpleChannelInboundHandler<FullHttpRequest> {	CODE

Fake / Example Data1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	…io/lettuce/core/search/RediSearchIntegrationTests.java	683	updateDoc1.put("author", "John Doe");	CODE

redis/lettuce

Open-Source Code Quality, Security and Technical Debt Review