AI Slop Code Risk Monitor

square/okhttp

Name: square/okhttp — Kotlin Code Quality & Security Review | AI Slop Code Risk Monitor
Creator: AI Slop Code Risk Monitor

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

A meticulous HTTP client for the JVM, Android, and GraalVM.

0.2 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for square/okhttp, a Kotlin project with 47,103 GitHub stars. SynthScan examined 167,481 lines of code across 744 source files, recording 20 pattern matches distributed across 2 syntactic categories. The legacy adjusted pattern signal is 0.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.

0.2

Adjusted Signal

0.2

Raw Pattern Score

100%

Time Factor

2026-10-30

Last Push

47.1K

Stars

Kotlin

Language

167.5K

Lines of Code

744

Files

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

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

Hallucinated Dependency & Supply Chain Risk 0.6/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 1.1/100 · LOW

Which changes need focused human review? 20 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 2HIGH 0MEDIUM 0LOW 18

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

Hallucination Indicators2 hits · 20 pts

Severity	File	Line	Snippet	Context
CRITICAL	docs/features/https.md	57	at com.android.org.conscrypt.NativeCrypto.SSL_do_handshake(Native Method)	CODE
CRITICAL	okhttp/src/jvmTest/kotlin/okhttp3/InterceptorTest.kt	709	org.junit.jupiter.api.Assertions.assertTrue(	CODE

Over-Commented Block18 hits · 18 pts

Severity	File	Line	Snippet	Context
LOW	…e/src/main/java/okhttp3/recipes/kt/WiresharkExample.kt	141	override fun publish(record: LogRecord) {	COMMENT
LOW	…p-tls/src/test/java/okhttp3/tls/HeldCertificateTest.kt	261	assertThat(root.certificate.sigAlgName).isEqualTo("SHA256WITHECDSA", ignoreCase = true)	COMMENT
LOW	…p-tls/src/test/java/okhttp3/tls/HeldCertificateTest.kt	321	listOf(GeneralName.iPAddress, "1.1.1.1"),	COMMENT
LOW	.github/workflows/build.yml	421	emulator-boot-timeout: 120	COMMENT
LOW	okhttp/src/jvmTest/kotlin/okhttp3/CallHandshakeTest.kt	121	platform.assumeNotBouncyCastle()	COMMENT
LOW	okhttp/src/jvmTest/kotlin/okhttp3/CallHandshakeTest.kt	161	// TLS_AES_128_GCM_SHA256	COMMENT
LOW	…st/kotlin/okhttp3/internal/tls/HostnameVerifierTest.kt	441	assertThat(verifier.verify("\u82b1\u5b50.foo.com", session)).isFalse()	COMMENT
LOW	…st/kotlin/okhttp3/internal/tls/HostnameVerifierTest.kt	541	// $ cat ./cert.cnf	COMMENT
LOW	…st/kotlin/okhttp3/internal/tls/HostnameVerifierTest.kt	761	}	COMMENT
LOW	…ttp/src/commonJvmAndroid/kotlin/okhttp3/CipherSuite.kt	261	@JvmField val TLS_DHE_DSS_WITH_AES_256_GCM_SHA384 = init("TLS_DHE_DSS_WITH_AES_256_GCM_SHA384", 0x00a3)	COMMENT
LOW	…ttp/src/commonJvmAndroid/kotlin/okhttp3/CipherSuite.kt	281	// @JvmField val TLS_DHE_PSK_WITH_NULL_SHA256 = init("TLS_DHE_PSK_WITH_NULL_SHA256", 0x00b4)	COMMENT
LOW	…ttp/src/commonJvmAndroid/kotlin/okhttp3/CipherSuite.kt	401	// @JvmField val TLS_ECDHE_PSK_WITH_AES_256_CBC_SHA384 = init("TLS_ECDHE_PSK_WITH_AES_256_CBC_SHA384", 0xc038)	COMMENT
LOW	…ttp/src/commonJvmAndroid/kotlin/okhttp3/CipherSuite.kt	421	// @JvmField val TLS_ECDHE_RSA_WITH_ARIA_128_CBC_SHA256 = init("TLS_ECDHE_RSA_WITH_ARIA_128_CBC_SHA256", 0xc04c)	COMMENT
LOW	…ttp/src/commonJvmAndroid/kotlin/okhttp3/CipherSuite.kt	441	// @JvmField val TLS_ECDHE_RSA_WITH_ARIA_128_GCM_SHA256 = init("TLS_ECDHE_RSA_WITH_ARIA_128_GCM_SHA256", 0xc060)	COMMENT
LOW	…ttp/src/commonJvmAndroid/kotlin/okhttp3/CipherSuite.kt	461	// @JvmField val TLS_ECDH_ECDSA_WITH_CAMELLIA_128_CBC_SHA256 = init("TLS_ECDH_ECDSA_WITH_CAMELLIA_128_CBC_SHA256", 0	COMMENT
LOW	…ttp/src/commonJvmAndroid/kotlin/okhttp3/CipherSuite.kt	481	// @JvmField val TLS_ECDH_ECDSA_WITH_CAMELLIA_128_GCM_SHA256 = init("TLS_ECDH_ECDSA_WITH_CAMELLIA_128_GCM_SHA256", 0	COMMENT
LOW	…ttp/src/commonJvmAndroid/kotlin/okhttp3/CipherSuite.kt	501	// @JvmField val TLS_RSA_WITH_AES_128_CCM = init("TLS_RSA_WITH_AES_128_CCM", 0xc09c)	COMMENT
LOW	…n/resources/okhttp3/internal/idna/IdnaMappingTable.txt	1	# IdnaMappingTable.txt	COMMENT