sttp — Watchdog Audit

Executive summary

This system holds an adequate standing with a health score of 68%, representing a manageable asset that carries specific operational risks. While the underlying code is robust, the system’s readiness for production deployment is the primary concern, creating a gap between development quality and operational safety. The value tied up here is moderate, requiring approximately 0.3 person-years or €42,000 to rebuild, indicating that the investment in maintenance is justified but must be directed carefully to protect delivery speed and reliability.

The most significant risk lies in production readiness, which scores only 55%. This lens measures whether the system is safe to operate, including testing, observability, and security controls. A low score here means that defects are more likely to reach users, outages may go unnoticed until they cause damage, and the cost of fixing issues in production will be significantly higher than if caught earlier. This weakness undermines the otherwise strong architectural foundation, exposing the business to unnecessary downtime and support costs.

Conversely, the system demonstrates genuine strength in code health and architecture, scoring 93% and 98% respectively. The codebase is clean, well-structured, and easy to understand, which supports long-term maintainability and reduces the risk of introducing bugs during future changes. This solid foundation means that when improvements are made, they are less likely to cause unintended side effects, preserving the integrity of the business logic.

To address the readiness gap with the highest leverage, the team should add a static analysis security testing step to the continuous integration pipeline. This automated check will catch security regressions before they are merged, ensuring that every release meets a baseline security standard without requiring significant manual effort. Additionally, implementing a draft release process will provide a final gate to stop bad builds from reaching users, adding a critical layer of operational control. These steps offer immediate protection against the most pressing risks while building a more resilient operational posture.

Code Health 93% ★ Exemplary Architecture 98% ★ Exemplary Maturity 73% Strong Readiness 55% Adequate · gated by P3 Security 81% Adequate · gated by D36

How the score is built — each lens's share of the headline Width is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.

Readiness 55% · 47% weightMaturity 73% · 26% weightSecurity 81% · 14% weightCode Health 93% · 8% weightArchitecture 98% · 4% weight

Raise Readiness 55 → 70 (the Healthy floor) ⇒ headline 68 → ~76.

Code composition — where the lines go

Tests 100%

New since the last scan (100+)

125 finding(s) are new versus the previous scan (2026-08-07) — surfaced by this scheduled scan itself, no pull request required. Showing the first 100; the full set is in the report.

D1 · AbstractBackendStub.adjustResponseBody (cyclomatic 29) core/src/main/scala/sttp/client4/testing/AbstractBackendStub.scala
D1 · BodyFromAkka.webSocketAndFlow (cyclomatic 16) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala
D1 · Slf4jLogger.apply (cyclomatic 16) logging/slf4j/src/main/scala/sttp/client4/logging/slf4j/Slf4jLogger.scala
D1 · BodyFromPekko.webSocketAndFlow (cyclomatic 16) pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyFromPekko.scala
D2 · BodyFromAkka.webSocketAndFlow (cognitive 31) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala
D2 · BodyFromPekko.webSocketAndFlow (cognitive 31) pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyFromPekko.scala
D2 · ZioWebSockets.compilePipe (cognitive 27) effects/zio/src/main/scala/sttp/client4/impl/zio/ZioWebSockets.scala
D2 · ZioWebSockets.compilePipe (cognitive 27) effects/zio1/src/main/scala/sttp/client4/impl/zio/ZioWebSockets.scala
D2 · Otel4sMetricsBackend.metricsListener (cognitive 21) observability/otel4s-metrics-backend/src/main/scala/sttp/client4/opentelemetry/otel4s/Otel4sMetricsBackend.scala
D2 · MetricsRequestListener.captureResponseMetrics (cognitive 21) observability/otel4s-metrics-backend/src/main/scala/sttp/client4/opentelemetry/otel4s/Otel4sMetricsBackend.scala
D2 · AbstractBackendStub.adjustResponseBody (cognitive 20) core/src/main/scala/sttp/client4/testing/AbstractBackendStub.scala
D2 · GZIPCompressingInputStream.read (cognitive 19) core/src/main/scalajvm/sttp/client4/compression/GZIPCompressingInputStream.scala
D3 · MethodTooLong: HttpServer.paramsToString testing/server/src/main/scala/sttp/client4/testing/server/HttpServer.scala
D3 · TooManyMethods: PartialRequestBuilder core/src/main/scala/sttp/client4/requestBuilder.scala
D3 · TooManyMethods: SttpApi core/src/main/scala/sttp/client4/SttpApi.scala
D4 · Near-duplicate member pair (59 shared lines) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala
D4 · Near-duplicate member pair (38 shared lines) effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala
D4 · Near-duplicate member pair (37 shared lines) effects/fs2-ce2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala
D4 · Near-duplicate member pair (36 shared lines) effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala
D4 · Near-duplicate member pair (27 shared lines) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala
D4 · Near-duplicate member pair (24 shared lines) core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala
D4 · Near-duplicate member pair (23 shared lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyToAkka.scala
D4 · Members sharing a duplicated core (4 members, 50+ identical tokens) json/play-json/src/main/scala/sttp/client4/playJson/SttpPlayJsonApi.scala
D4 · Duplicated block (40 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala
D4 · Duplicated block (32–33 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala
D4 · Duplicated block (29 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpClient.scala
D4 · Duplicated block (25 lines × 2) effects/fs2-ce2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala
D4 · Duplicated block (18 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala
D4 · Duplicated block (18 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/ToAkka.scala
D4 · Duplicated block (17 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala
D4 · Duplicated block (17 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala
D4 · Duplicated block (16 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala
D4 · Duplicated block (16 lines × 2) effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala
D4 · Duplicated block (15 lines × 2) effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala
D4 · Duplicated block (12–15 lines × 2) effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala
D4 · Duplicated block (15 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala
D4 · Duplicated block (14 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala
D4 · Duplicated block (12–13 lines × 2) core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala
D4 · Duplicated block (13 lines × 2) effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala
D4 · Duplicated block (13 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala
D4 · Duplicated block (12 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/ToAkka.scala
D4 · Duplicated block (12 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala
D4 · Duplicated block (11 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala
D4 · Duplicated block (10 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala
D4 · Duplicated block (10 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpClient.scala
D4 · Duplicated block (10 lines × 2) effects/zio/src/main/scala/sttp/client4/impl/zio/ZioWebSockets.scala
D4 · Duplicated block (10 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala
D4 · Duplicated block (7–9 lines × 2) core/src/main/scalajs/sttp/client4/WebSocketImpl.scala
D4 · Duplicated block (9 lines × 2) effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/fs2Decompressors.scala
D4 · Duplicated block (9 lines × 2) effects/zio/src/main/scala/sttp/client4/impl/zio/ExtendedEnvBackend.scala
D4 · Duplicated block (9 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala
D4 · Duplicated block (8 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyToAkka.scala
D4 · Duplicated block (8 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyToAkka.scala
D4 · Duplicated block (8 lines × 2) effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala
D4 · Duplicated block (8 lines × 2) effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala
D4 · Duplicated block (8 lines × 2) effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala
D4 · Duplicated block (7 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyToAkka.scala
D4 · Duplicated block (7 lines × 2) armeria-backend/fs2-ce2/src/main/scala/sttp/client4/armeria/fs2/ArmeriaFs2Backend.scala
D4 · Duplicated block (7 lines × 2) core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala
D4 · Duplicated block (4–7 lines × 3) core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala
D4 · Duplicated block (7 lines × 2) effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala
D4 · Duplicated block (7 lines × 2) effects/zio/src/main/scalajs/sttp/client4/impl/zio/FetchZioBackend.scala
D4 · Duplicated block (7 lines × 2) observability/otel4s-metrics-backend/src/main/scala/sttp/client4/opentelemetry/otel4s/Otel4sMetricsBackend.scala
D4 · Duplicated block (6 lines × 4) json/play-json/src/main/scala/sttp/client4/playJson/SttpPlayJsonApi.scala
D4 · Duplicated block (6 lines × 2) core/src/main/scalajvm/sttp/client4/compression/defaultCompressors.scala
D4 · Duplicated block (6 lines × 2) effects/zio1/src/main/scala/sttp/client4/impl/zio/SttpClientStubbingBase.scala
D4 · Duplicated block (6 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala
D4 · Duplicated block (6 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala
D4 · Duplicated block (5 lines × 3) core/src/main/scalajs/sttp/client4/SttpClientExceptionExtensions.scala
D4 · Duplicated block (5 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/FromAkka.scala
D4 · Duplicated block (5 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/Util.scala
D4 · Duplicated block (5 lines × 2) core/src/main/scalajvm/sttp/client4/httpclient/HttpClientAsyncBackend.scala
D4 · Duplicated block (5 lines × 2) effects/fs2-ce2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala
D4 · Duplicated block (5 lines × 2) effects/zio/src/main/scala/sttp/client4/impl/zio/ExtendedEnvBackend.scala
D4 · Duplicated block (5 lines × 2) json/zio-json/src/main/scalajvm/sttp/client4/ziojson/SttpZioJsonApiExtensions.scala
D4 · Duplicated block (27 lines × 3) armeria-backend/zio/src/main/scala/sttp/client4/armeria/zio/package.scala
D4 · Duplicated block (28 lines × 2) armeria-backend/zio1/src/main/scala/sttp/client4/armeria/zio/zio.scala
D4 · Duplicated block (20 lines × 2) core/src/main/scalajvm/sttp/client4/internal/SttpFileExtensions.scala
D4 · Duplicated block (45 lines × 2) effects/cats-ce2/src/main/scala/sttp/client4/impl/cats/implicits.scala
D4 · Duplicated block (10 lines × 2) effects/cats/src/main/scalajvm/sttp/client4/httpclient/cats/CatsSimpleQueue.scala
D4 · Duplicated block (63 lines × 2) effects/zio/src/main/scalajs/sttp/client4/impl/zio/package.scala
D4 · Duplicated block (16 lines × 2) effects/zio/src/main/scalajvm/sttp/client4/impl/zio/package.scala
D4 · Duplicated block (40 lines × 2) http4s-backend/src/main/scalajvm/sttp/client4/http4s/Http4sBackend.scala
D4 · Duplicated block (7 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala
D4 · Duplicated block (12 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala
D4 · Duplicated block (9 lines × 2) armeria-backend/cats-ce2/src/main/scala/sttp/client4/armeria/cats/ArmeriaCatsBackend.scala
D4 · Duplicated block (5 lines × 2) effects/cats/src/main/scalajvm/sttp/client4/httpclient/cats/HttpClientCatsBackend.scala
D4 · Duplicated block (9 lines × 2) effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2ServerSentEvents.scala
D4 · Duplicated block (6 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala
D4 · Duplicated block (7 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala
D4 · Duplicated block (6 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala
D4 · Duplicated block (9 lines × 2) core/src/main/scalajvm/sttp/client4/SttpClientExceptionExtensions.scala
D4 · Duplicated block (6 lines × 2) core/src/main/scalajvm/sttp/client4/SttpClientExceptionExtensions.scala
D4 · Duplicated block (7 lines × 2) effects/fs2-ce2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala
D4 · Duplicated block (6 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala
D4 · Duplicated block (5 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala
D6 · Low cohesion: HttpClientBackend (LCOM4 4) core/src/main/scalajvm/sttp/client4/httpclient/HttpClientBackend.scala
D6 · Low cohesion: OpenTelemetryMetricsListener (LCOM4 4) observability/opentelemetry-backend/src/main/scala/sttp/client4/opentelemetry/OpenTelemetryMetricsBackend.scala
D6 · Low cohesion: HttpServer (LCOM4 4) testing/server/src/main/scala/sttp/client4/testing/server/HttpServer.scala
D17 · TodoComment akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala

A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.

Rebuild cost & value ~ Modeled — €14,000–€70,000

Cost to rebuild	€14,000–€70,000 (0.1–0.4 person-years (233–739 h), ~1 engineer)
Domain complexity	Standard — harder problems cost more per line
Quality factor	1.0× (at 68% quality) — the last 20% of quality is most of the work
Size & shape	Medium · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)

This codebase represents roughly ~0.3 person-years of build effort (about ~€42,000 to rebuild). Its weakest lens is Readiness at 55% — the part of that asset most exposed by the findings below.

How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.0) — standard service × a 1.0× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source · effort from total production LoC as straight-line logic (the tier split is a C#-only syntax walk), a conservative lower bound. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).

Top priorities

The highest-leverage moves; the full ranked list is in the Roadmap below.

Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.

+13.0 pts · Medium effort · Security & performance tooling

Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.

+13.0 pts · Medium effort · Deployment & Rollback

Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.

+4.3 pts · Medium effort · Documentation (README)

Diagnosis — what's actually going on

Value concentrated against a weak lens · Medium · Value at risk

This is a Medium asset (~0.3 person-years to rebuild), and its weakest lens is Readiness at 55%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.

Evidence: valuation: Medium, ~0.3 person-years rebuild (22,813 LoC) · weakest lens: Readiness 55%

→ Direct remediation budget at Readiness first — highest risk-reduction per euro on an asset this size.

Highest-leverage move · Medium · Leverage

Of everything flagged, the best return on effort is: Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. The rest can wait behind it.

Evidence: priority ranking: top of 5 ranked by impact/effort

→ Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.

Architecture — module dependency matrix

Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)

104 modules, 214 dependencies. 3 dependency cycles across 22 modules, marked above the diagonal.

Showing the 40 most-connected modules; 64 more are not drawn.

Module dependency matrix. The row depends on the column; the number is how many type pairs create the dependency. A cell above the diagonal is part of a dependency cycle.
depends on →	1 BackendOptions	2 curl.internal	3 internal.CryptoMd5	4 internal.ws	5 ResponseException	6 internal	7 monad	8 circe	9 json4s	10 wrappers	11 logging	12 testing	13 sttp.client4	14 caching	15 compression	16 curl.AbstractCurlBackend	17 fetch	18 impl.zio.AbstractClientStubbing	19 listener	23 impl.cats	26 impl.zio	27 internal.httpclient	28 opentelemetry	30 armeria.zio	34 armeria	35 httpclient
1 BackendOptions
2 curl.internal
3 internal.CryptoMd5
4 internal.ws
5 ResponseException													2
6 internal				1									9
7 monad													2
8 circe					1								3
9 json4s					1								3
10 wrappers							2						21
11 logging										1			6
12 testing										1			24
13 sttp.client4	1					6		1	1	1	2	2
14 caching										1			4
15 compression													3
16 curl.AbstractCurlBackend		1											1
17 fetch				1		3							6
18 impl.zio.AbstractClientStubbing												5	6											3
19 listener										1			4
20 curl		4				1							8			1
21 examples.wrapper										4			8	1
22 finagle													5		1			1
23 impl.cats						2	1						8				1
24 impl.fs2				1		1							8		3		1
25 impl.monix				1		1							1				1
26 impl.zio				1		1						3	12		5		1	1
27 internal.httpclient						1							6		1											1
28 opentelemetry										1			13						1
29 opentelemetry.otel4s.Otel4sMetricsBackend													2						1
30 armeria.zio												1	2		1			2			1				2
31 impl.scalaz							1						8							4
32 okhttp				5									16									1
33 prometheus			1										9						1				3
34 armeria	1		1			1							8		1									1
35 httpclient			1	5		2							15									9		1
36 impl			1										5											1
37 httpclient.cats				2		1																4				1
38 httpclient.fs2				1		1							3									5				1
39 httpclient.monix				1		1							1		2							5				1
40 httpclient.zio				1		1						1	5		2			2			1	5		1		1

Dependency, pointing down the layeringAbove the diagonal — part of a cycleThe module itself

At a glance — Code Health · 93% · Exemplary ·

The Good

D1 · Scala Cyclomatic Complexity 9.0 D2 · Scala Cognitive Complexity 8.6 D3 · Scala God Classes 9.4 D4 · Scala Code Duplication 8.5 D17 · Scala Explicit Debt 9.9

At a glance — Architecture · 98% · Exemplary ·

The Good

D6 · Scala Cohesion (LCOM4) 9.2 D7 · Scala Architectural Integrity 10.0 D35 · Scala Change Coupling 10.0 AX10 · Repo Code composition 10.0

At a glance — Maturity · 73% · Strong ·

The Good

D15 · Scala Churn × Complexity Hotspots 10.0 D16 · Scala Bus Factor 9.4 D19 · Scala Documentation Quality 10.0 D20 · Scala ADR Quality 7.9 D21 · Scala Naming Consistency 10.0 D25 · Scala ADR Conformance 10.0 M1 · Repo Documentation (README) 7.3 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 10.0

The Ugly

M2 · Repo Architecture documentation 4.0

At a glance — Readiness · 55% · Adequate · gated by P3 ·

The Good

D13 · Scala Secret Scanning 10.0 D14 · Scala License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P6 · Repo Release Hygiene 10.0

The Bad

P4 · Repo Deployment & Rollback 5.0

The Ugly

P3 · Repo Security & performance tooling 0.0

At a glance — Security · 81% · Adequate · gated by D36 ·

The Good

D28 · Scala Secrets (history) 10.0 D30 · Scala Dependency Vulnerabilities 10.0 D43 · Scala Malicious Dependencies 10.0 D44 · Scala Platform End-of-Life 10.0

The Bad

D29 · Scala Static Analysis (SAST) 6.4

The Ugly

D36 · Scala Supply-chain Provenance & Signing 2.5

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP category	Findings	Severity
A03:2021 — Injection	12	High / Critical

Roadmap

First, integrate automated security scanning into the CI pipeline to block regressions before they land. Second, implement a manual approval gate for releases to prevent faulty builds from reaching users. Third, update the root README with a high-level architecture overview and expand the ADR log to eight entries, ensuring all significant decisions include documented trade-offs.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do this	Helps	Effort	Dimension
Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.	+13.0 pts	Medium	Security & performance tooling
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.	+13.0 pts	Medium	Deployment & Rollback
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.	+4.3 pts	Medium	Documentation (README)
Grow the ADR log (currently 4) — reach 8 to raise the maturity tier; document significant decisions as they're made.	+4.3 pts	Medium	Architecture documentation
Resolve the 1 No consequences/trade-offs section (e.g. loss of validation for… finding(s) in ADR Quality — start with 0002-http-model-conventions.md.	+1.7 pts	Low	ADR Quality
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2).	+0.5 pts	Low	Static Analysis (SAST)
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor.	+0.4 pts	Low	Bus Factor
Resolve the 1 Off-boarding risk finding(s) in Bus Factor.	+0.4 pts	Low	Bus Factor

File quality

Per-file score 0–10 — a quality signature. Of 55 files carrying findings, judged against the Production bar: 2% slop · 38% mixed · 60% near-clean.

File	Score	Band	Worst signal
REDACTED	1.3	Slop	Static Analysis (SAST): High: REDACTED
akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala	5.2	Mixed	Change Coupling: Boundary-crossing change coupling: AkkaHttpBackend.scala ↔ Http4sBackendBase.scala
akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala	6.0	Mixed	Explicit Debt: TodoComment
pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyFromPekko.scala	6.0	Mixed	Explicit Debt: TodoComment
core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala	6.0	Mixed	Explicit Debt: TodoComment
core/src/test/scala/sttp/client4/testing/streaming/StreamingTest.scala	6.5	Mixed	Explicit Debt: TodoComment
testing/server/src/main/scala/sttp/client4/testing/server/HttpServer.scala	7.0	Mixed	God Classes: MethodTooLong: HttpServer.paramsToString
http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala	7.0	Mixed	Code Duplication: Near-duplicate member pair (59 shared lines)
effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala	7.1	Mixed	Code Duplication: Near-duplicate member pair (38 shared lines)
effects/fs2-ce2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala	7.2	Mixed	Code Duplication: Near-duplicate member pair (37 shared lines)
effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala	7.2	Mixed	Code Duplication: Near-duplicate member pair (36 shared lines)
akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyToAkka.scala	7.2	Mixed	Code Duplication: Near-duplicate member pair (23 shared lines)
REDACTED	7.2	Mixed	Static Analysis (SAST): High: REDACTED
core/src/main/scala/sttp/client4/monad/MapEffect.scala	7.3	Mixed	Explicit Debt: TodoComment
observability/otel4s-metrics-backend/src/main/scala/sttp/client4/opentelemetry/otel4s/Otel4sMetricsBackend.scala	7.4	Mixed	Cognitive Complexity: Otel4sMetricsBackend.metricsListener (cognitive 21)
core/src/main/scala/sttp/client4/testing/AbstractBackendStub.scala	7.8	Mixed	Cyclomatic Complexity: AbstractBackendStub.adjustResponseBody (cyclomatic 29)
effects/zio/src/main/scala/sttp/client4/impl/zio/ZioWebSockets.scala	7.8	Mixed	Cognitive Complexity: ZioWebSockets.compilePipe (cognitive 27)
json/play-json/src/main/scala/sttp/client4/playJson/SttpPlayJsonApi.scala	7.8	Mixed	Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens)
akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpClient.scala	7.8	Mixed	Code Duplication: Duplicated block (29 lines × 2)
akka-http-backend/src/main/scala/sttp/client4/akkahttp/ToAkka.scala	7.8	Mixed	Code Duplication: Duplicated block (18 lines × 2)

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 11

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 117

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 7

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 44

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 26 of 31 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 5 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 31 dimensions across the health lenses

D1D2D3D4D6D7D13D14D15D16D17D19D20D21D25D28D29D30D35D36D43D44AX10M1M2M3M4P1P3P4P6

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions

Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 126 of 135 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

Method	Backs	Version	Evaluator
Roslyn static analysis	Complexity, cohesion, coupling, dead code, API surface, layering	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a0e3c8-7e74-719b-9083-67bef1d2dc63.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.scala) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) and this repository declares an sbt build (repository root, 206 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D12 Dependency Hygiene — evaluation did not complete — Dependency Hygiene not included (check did not complete) — excluded from the score.
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares an sbt build (build.sbt), but the licence verdict published here was taken over its Python distribution dependencies. Nothing was read about its sbt dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
D34 Knowledge Freshness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. File-level freshness contradicts repo activity: 60 commits in the last 90 days, yet 102 of 140 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
AX3 Project dependency cycles — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over which project references which. That is a language-neutral question, but the project-reference graph is collected from MSBuild .csproj, Gradle and Maven builds only, and this repository commits none — so there was no graph to read, and re-running the same commit reads the same nothing. Its modules are declared as: sbt subprojects (build.sbt). A reader for that graph is the collector this check is missing. That is a COLLECTOR gap in this analyzer — no change to the scan image closes it — and not a finding that the repository is free of what this check looks for.
AX4 Dependency direction — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the direction each project reference points. That is a language-neutral question, but the project-reference graph is collected from MSBuild .csproj, Gradle and Maven builds only, and this repository commits none — so there was no graph to read, and re-running the same commit reads the same nothing. Its modules are declared as: sbt subprojects (build.sbt). A reader for that graph is the collector this check is missing. That is a COLLECTOR gap in this analyzer — no change to the scan image closes it — and not a finding that the repository is free of what this check looks for.
AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AX8 Test isolation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over which projects are test projects, and what they reference. That is a language-neutral question, but the project-reference graph is collected from MSBuild .csproj, Gradle and Maven builds only, and this repository commits none — so there was no graph to read, and re-running the same commit reads the same nothing. Its modules are declared as: sbt subprojects (build.sbt). A reader for that graph is the collector this check is missing. That is a COLLECTOR gap in this analyzer — no change to the scan image closes it — and not a finding that the repository is free of what this check looks for.
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, or a Dockerfile. None was found, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
ED5 Idempotency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds retry-prone mutations by walking the repository's declared types, and NONE was loaded on this run, so it had nothing to look at. That is a limit of the analyzer's reach — it reads .NET projects — not a finding that this repository has no command handlers or message consumers.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X14 Bypassable address classification — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X20 Mistyped argument guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X21 Side-effecting pattern guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X26 Unsynchronised callback handoff — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X27 Collection changed while being enumerated — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X28 Index access outside its own emptiness guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X29 Per-element action decided by a fixed element — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X30 Support guard that admits what it rejects — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X32 Type resolved by simple name across every loaded assembly — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D25 ADR Conformance: ADR conformance is the LLM-scored fraction of sampled code that follows recorded decisions — it checks the decisions that were written down and the slices it sampled, not unrecorded rules or the whole tree.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (5): D19, D20, D21, D25, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity9.0 / 10Strong✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.0 / 10 · rule-coverage 100% · ceiling Prevented

4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was AbstractBackendStub.adjustResponseBody at 29. A further 6 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being BodyToAkka.apply at 21 — they are counted neither in the figure above nor in this dimension's score. 6 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyToAkka.scala (BodyToAkka.apply at 21), pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyToPekko.scala (BodyToPekko.apply at 21), core/src/main/scalajvm/sttp/client4/SttpClientExceptionExtensions.scala (SttpClientExceptionExtensions.defaultExceptionToSttpClientException at 20), core/src/main/scala/sttp/client4/internal/BodyFromResponseAs.scala (BodyFromResponseAs.doApply at 18), core/src/main/scalanative/sttp/client4/SttpClientExceptionExtensions.scala (SttpClientExceptionExtensions.defaultExceptionToSttpClientException at 18), and 1 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

AbstractBackendStub.adjustResponseBody (cyclomatic 29)core/src/main/scala/sttp/client4/testing/AbstractBackendStub.scala:160

BodyFromAkka.webSocketAndFlow (cyclomatic 16)akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala:127

Slf4jLogger.apply (cyclomatic 16)logging/slf4j/src/main/scala/sttp/client4/logging/slf4j/Slf4jLogger.scala:20

BodyFromPekko.webSocketAndFlow (cyclomatic 16)pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyFromPekko.scala:128

What to do

Resolve the 1 AbstractBackendStub.adjustResponseBody (cyclomatic 29) finding(s) in Cyclomatic Complexity — start with AbstractBackendStub.scala. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 BodyFromAkka.webSocketAndFlow (cyclomatic 16) finding(s) in Cyclomatic Complexity — start with BodyFromAkka.scala. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Slf4jLogger.apply (cyclomatic 16) finding(s) in Cyclomatic Complexity — start with Slf4jLogger.scala. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D2 · Cognitive Complexity8.6 / 10Strong✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

Maturity: Documented → Verified → Prevented · effective 8.6 / 10 · rule-coverage 100% · ceiling Prevented

8 method(s) exceeded the cognitive complexity threshold of 15; the worst was BodyFromAkka.webSocketAndFlow at 31.

ZioWebSockets.compilePipe (cognitive 27) · ×2effects/zio/src/main/scala/sttp/client4/impl/zio/ZioWebSockets.scala:8

BodyFromAkka.webSocketAndFlow (cognitive 31)akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala:127

BodyFromPekko.webSocketAndFlow (cognitive 31)pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyFromPekko.scala:128

Otel4sMetricsBackend.metricsListener (cognitive 21)observability/otel4s-metrics-backend/src/main/scala/sttp/client4/opentelemetry/otel4s/Otel4sMetricsBackend.scala:63

MetricsRequestListener.captureResponseMetrics (cognitive 21)observability/otel4s-metrics-backend/src/main/scala/sttp/client4/opentelemetry/otel4s/Otel4sMetricsBackend.scala:159

+ 2 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Resolve the 2 ZioWebSockets.compilePipe (cognitive 27) finding(s) in Cognitive Complexity — start with ZioWebSockets.scala (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 BodyFromAkka.webSocketAndFlow (cognitive 31) finding(s) in Cognitive Complexity — start with BodyFromAkka.scala. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 BodyFromPekko.webSocketAndFlow (cognitive 31) finding(s) in Cognitive Complexity — start with BodyFromPekko.scala. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D3 · God Classes9.4 / 10Stronggated by 3 serious findings✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.4 / 10 · rule-coverage 100% · ceiling Prevented

3 god class(es) detected.

TooManyMethods: PartialRequestBuilder · ×2core/src/main/scala/sttp/client4/requestBuilder.scala:34

MethodTooLong: HttpServer.paramsToStringtesting/server/src/main/scala/sttp/client4/testing/server/HttpServer.scala:48

What to do

Resolve the 2 TooManyMethods finding(s) in God Classes — start with requestBuilder.scala, SttpApi.scala. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 MethodTooLong finding(s) in God Classes — start with HttpServer.scala. — One of this dimension's main actionable groups (1 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D4 · Code Duplication8.5 / 10Strong✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

Maturity: Documented → Verified → Prevented · effective 8.5 / 10 · rule-coverage 100% · ceiling Verified

73 duplicated block group(s) detected. A further 8 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.

Duplicated block (7 lines × 2) · ×9akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyToAkka.scala:28

Duplicated block (6 lines × 2) · ×8core/src/main/scalajvm/sttp/client4/compression/defaultCompressors.scala:16

Duplicated block (5 lines × 2) · ×8akka-http-backend/src/main/scala/sttp/client4/akkahttp/FromAkka.scala:13

Duplicated block (9 lines × 2) · ×6effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/fs2Decompressors.scala:25

Duplicated block (10 lines × 2) · ×5akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala:155

+ 32 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Resolve the 9 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with BodyToAkka.scala, ArmeriaFs2Backend.scala, AbstractCurlBackend.scala. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 8 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with Http4sBackendBase.scala (4), defaultCompressors.scala, SttpClientStubbingBase.scala. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 8 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with FromAkka.scala, Util.scala, HttpClientAsyncBackend.scala. — One of this dimension's main actionable groups (8 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D6 · Cohesion (LCOM4)9.2 / 10Stronggated by 3 serious findings✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 9.2 / 10 · rule-coverage 100% · ceiling Verified

3 of 45 classes have LCOM4 above 3.

Low cohesion: HttpClientBackend (LCOM4 4) · ×3core/src/main/scalajvm/sttp/client4/httpclient/HttpClientBackend.scala:41

What to do

Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with HttpClientBackend.scala, OpenTelemetryMetricsBackend.scala, HttpServer.scala. — One of this dimension's main actionable groups (3 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D7 · Architectural Integrity10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the code respects its intended layering / architecture rules.

Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

All 3 mechanizable ADR(s) are enforced: 3 by analyzers, 0 by tests. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).

✓ On the Gold path — maintain.

Detailed fixes: d7_recommendation.md.

Do you agree with this assessment?

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

Do you agree with this assessment?

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 42 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 5 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (37 reached that way). Requirements it states ONLY under an extra, a PEP 735 dependency group, a Poetry dev group or a dev-named requirements file are excluded: pip does not install any of them for a consumer. ★ This repository commits no dependency lockfile that this pass reads, so each licence is the one PyPI publishes for the distribution's CURRENT release rather than for a pinned version. 10 of them publish no licence on PyPI this pass can read; that is missing data, not a violation, and none of them is charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's Python distribution dependencies and nothing else. The repository also declares an sbt build (build.sbt), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

Do you agree with this assessment?

D16 · Bus Factor9.4 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

Maturity: Documented → Verified → Prevented · effective 9.4 / 10 · rule-coverage 100% · ceiling Documented

8 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is build.sbt. Counted over 140 of the 322 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Off-boarding risk: anonymized user #1

Further sole-owners (lower concentration)

✓ On the Gold path — maintain.

Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D17 · Explicit Debt9.9 / 10Stronggated by 13 serious findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Prevented

13 deducted task-comment markers across 22813 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

TodoComment · ×13akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala:44

What to do

Resolve the 13 TodoComment finding(s) in Explicit Debt — start with StreamingTest.scala (5), MapEffect.scala (2), BodyFromAkka.scala. — One of this dimension's main actionable groups (13 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D19 · Documentation QualityExemplary◐ Sampled · advisory

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Exemplary / 10 · rule-coverage 100% · ceiling Documented

The repository's root README and a dedicated docs directory are both excellent: the root README is an ideal overview of sttp client (what it does, supported Scala versions, platforms, quickstart with scala-cli), while the architecture/Docs markdown files cover every documented project tier. The README itself is well written for its role as an overview document; it states what the repository is for and gives a runnable example, then links out to detailed docs on goals, how it works, migration from sttp-client3, quickstart with sbt/ammonite/scala-cli, community support, sponsors, and commercial sponsorship. The architecture/Docs set is complete and well-structured. The documentation is comprehensive and well-structured: it contains 61 documents (including a README for each of the 12 repositories under docs/), covering backend implementations for Akka, cats-effect, Finagle, fs2, Http4s, Monix, Pekko, Scalaz, and the start-stop guide. Each document is well-organized with an overview, context, decision, what we gain, what we lose, usage examples (fenced shell blocks), and a notes section; it also includes architecture/Docs markdown files for design topics that are not repository-level documentation.

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

Do you agree with this assessment?

D20 · ADR QualityStrong◐ Sampled · advisory

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

Maturity: Documented → Verified → Prevented · effective Strong / 10 · rule-coverage 100% · ceiling Documented

Evaluated 4 ADR(s) individually; mean quality 7.9/10 (mixed — many ADRs miss context or consequences). 1 flagged with a specific gap.

No consequences/trade-offs section (e.g. loss of validation for unsafeApply) are present and the body is clippeddocs/adr/0002-http-model-conventions.md

What to do

Resolve the 1 No consequences/trade-offs section (e.g. loss of validation for… finding(s) in ADR Quality — start with 0002-http-model-conventions.md. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Exemplary / 10 · rule-coverage 100% · ceiling Verified

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

Do you agree with this assessment?

D25 · ADR ConformanceExemplary◐ Sampled · advisory

What it measures: Whether the code actually follows the decisions recorded in the project's ADRs.

Method: Judged by language model at low temperature against ADRs plus a deterministic structural code summary; findings linked to repo-rooted ADR paths for traceability. Advisory.

Maturity: Documented → Verified → Prevented · effective Exemplary / 10 · rule-coverage 100% · ceiling Verified

1 conform / 0 violate across 4 ADRs.

✓ On the Gold path — maintain.

Detailed fixes: d25_recommendation.md.

Do you agree with this assessment?

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

Do you agree with this assessment?

D29 · Static Analysis (SAST)6.4 / 10Adequate✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

Maturity: Documented → Verified → Prevented · effective 6.4 / 10 · rule-coverage 100% · ceiling Documented

12 finding(s): 0 critical, 10 high, 2 medium, 0 low. 8 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 5 file(s) — `effects/ox/src/main/scala/sttp/client4/impl/ox/ws/OxWebSockets.scala`, `examples/src/main/scala/sttp/client4/examples/errors/httpErrorHandlingJson.scala`, `examples/src/main/scala/sttp/client4/examples/observability/metricsWrapperPekkoHttp.scala`, `examples/src/main/scala/sttp/client4/examples/wrapper/retryingBackend.scala`, `examples/src/main/scala/sttp/client4/examples/ws/wsOxExample.scala` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED

What to do

Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
No action in Static Analysis (SAST) — all 4 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (4 issue-level, 0 of them charged here).
No action in Static Analysis (SAST) — all 4 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (4 issue-level, 0 of them charged here).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D30 · Dependency Vulnerabilities10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir/Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex, Go, Java and Kotlin via Maven/Gradle, npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No known-vulnerable dependencies in any ecosystem this repository declares.

✓ On the Gold path — maintain.

Detailed fixes: d30_recommendation.md.

Do you agree with this assessment?

D35 · Change Coupling10.0 / 10Adequategated by 1 critical finding✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: AkkaHttpBackend.scala↔Http4sBackendBase.scala 50%

Boundary-crossing change coupling: AkkaHttpBackend.scala ↔ Http4sBackendBase.scalaakka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala

What to do

Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with AkkaHttpBackend.scala. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

Maturity: Documented → Verified → Prevented · effective 2.5 / 10 · rule-coverage 100% · ceiling Documented

1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED

What to do

Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Do you agree with this assessment?

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 5 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

What to do

The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.

Do you agree with this assessment?

M1 · Documentation (README)7.3 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.

Do you agree with this assessment?

M2 · Architecture documentation4.0 / 10Weak✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

What to do

Grow the ADR log (currently 4) — reach 8 to raise the maturity tier; document significant decisions as they're made.

Do you agree with this assessment?

M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

Do you agree with this assessment?

M4 · Documentation accuracy10.0 / 10Exemplary◐ Sampled · advisory

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

Do you agree with this assessment?

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

Do you agree with this assessment?

P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 6915 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

What to do

Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.

What to do

Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.

Do you agree with this assessment?

P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

Do you agree with this assessment?

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

Lens	Score	Rating	Impact
Code Health	93%	Exemplary	Solid.
Architecture	98%	Exemplary	Strongest area.
Maturity	73%	Strong	Solid.
Readiness	55%	Adequate — gated by P3	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	81%	Adequate — gated by D36	Capped at Fair by a Critical contributor — resolve it before relying on this lens.

Not evidenced — 4 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control

Not included — 80 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
AX3 Project dependency cycles — not assessed — project cycles and dependency direction are computed over a project-reference graph that was not loaded for this repository, because the repository commits no project file of a kind this check models. This is a gap in the analyzer, not a finding about this repository
AX4 Dependency direction — not assessed — project cycles and dependency direction are computed over a project-reference graph that was not loaded for this repository, because the repository commits no project file of a kind this check models. This is a gap in the analyzer, not a finding about this repository
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — not assessed — test isolation is computed from a project graph (which projects are test projects, and what they reference) that was not loaded for this repository, because the repository commits no project file of a kind this check models. This is a gap in the analyzer, not a finding about this repository
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — ~10521 lines of test source are present (.scala) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — the .scala suite was found but not re-run
D12 Dependency Hygiene — Dependency Hygiene not included (check did not complete)
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — Production source is present (.java, .scala) but bounded contexts are resolved over the C#/VB project set, which exposed none, so context scope could not be assessed. Not scored — this is a gap in the analyzer, not a verdict about this repository. Declaring the codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed — see the recommendation on this dimension for where. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D27 Navigability — symbol resolution incomplete — navigability not assessed
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D5 Coupling — Inter-project coupling could not be assessed — no analyzable project graph was found for this repository. Not scored: a gap in the analyzer's reach, not a verdict about this repository. (Coupling here is Martin afferent/efferent/instability plus reference cycles across a project-reference graph, read today from .NET project files; other ecosystems' module graphs are not read yet.)
D8 Code Coverage — Coverage not included — suite not readable by the collector
D9 Test Distribution — Test source is present (.scala) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 96 value object(s); 1 domain event(s)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — This check finds retry-prone mutations (command handlers and message/event consumers) by walking the repository's declared types, and none was loaded here, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C# syntax, and none was loaded for this repository. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P2 Observability — Observability was not assessed: this check reads a source model that does not carry this repository's product — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of a logging idiom this check recognises is NOT evidence that this repo lacks structured logging (it may log through its own ecosystem's logger). This is a gap in the analyzer, not a finding about this repository.
P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
P8 Schema migrations — not assessed — schema-migration practice is read from a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF2 Allocation hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X20 Mistyped argument guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X23 Unguarded diagnostic materialisation — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X27 Collection changed while being enumerated — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X28 Index access outside its own emptiness guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 11 finding(s)

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED

D35 · Change Coupling · Boundary-crossing change coupling · ×1

Boundary-crossing change coupling: AkkaHttpBackend.scala ↔ Http4sBackendBase.scala akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala — `akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala` (context akka-http-backend) and `http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala` (context http4s-backend) sit in DIFFERENT parts of the tree yet change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `371b40f0` Add an option to limit the response length for JVM backends (#2410) (at that commit the file was still `http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala`); `08bb1664` Used tags for auto decompresion disabling (at that commit the files were still `akka-http-backend/src/main/scala/sttp/client3/akkahttp/AkkaHttpBackend.scala` and `http4s-backend/src/main/scala/sttp/client3/http4s/Http4sBackend.scala`); `2c5c5b55` Restore old version (at that commit the files were still `akka-http-backend/src/main/scala/sttp/client3/akkahttp/AkkaHttpBackend.scala` and `http4s-backend/src/main/scala/sttp/client3/http4s/Http4sBackend.scala`) — run `git show` on any of them.

Serious — 117 finding(s)

D17 · Explicit Debt · TodoComment · ×13

TodoComment akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala:44 — // todo: Replace with HttpResponse#discardEntityBytes() once https://github.com/akka/akka-http/issues/1459 is resolved
TodoComment pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyFromPekko.scala:45 — // todo: Replace with HttpResponse#discardEntityBytes() once https://github.com/akka/akka-http/issues/1459 is resolved
TodoComment armeria-backend/zio/src/test/scala/sttp/client4/armeria/zio/ArmeriaZioStreamingTest.scala:35 — // TODO: consider if viaFunction is what we want — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/src/main/scala/sttp/client4/monad/MapEffect.scala:46 — // TODO: an even more dumbed-down version of the slightly more type-safe version below, which is needed due to a — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/src/main/scala/sttp/client4/monad/MapEffect.scala:47 — // TODO: bug in Dotty: https://github.com/lampepfl/dotty/issues/9533
TodoComment core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:508 — // todo: assign to monad object — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/src/test/scala/sttp/client4/testing/streaming/StreamingTest.scala:120 — // TODO: for some reason these explicit types are needed in Dotty — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/src/test/scala/sttp/client4/testing/streaming/StreamingTest.scala:136 — // TODO: for some reason these explicit types are needed in Dotty — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/src/test/scala/sttp/client4/testing/streaming/StreamingTest.scala:157 — // TODO: for some reason these explicit types are needed in Dotty — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/src/test/scala/sttp/client4/testing/streaming/StreamingTest.scala:173 — // TODO: for some reason these explicit types are needed in Dotty — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/src/test/scala/sttp/client4/testing/streaming/StreamingTest.scala:206 — // // TODO: for some reason these explicit types are needed in Dotty — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/src/test/scalajvm/sttp/client4/testing/AsyncRetries.scala:10 — // TODO: on GH Actions some tests sometimes timeout. For lack of a better solution, retrying them, but this needs proper fixing one day. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/src/test/scalanative/sttp/client4/testing/SyncHttpTestExtensions.scala:65 — // TODO: it will return empty value becasue there is a bug in scala native — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.

D4 · Code Duplication · Duplicated block (7 lines × 2) · ×9

Duplicated block (7 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyToAkka.scala:28 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyToAkka.scala:28-34 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyToPekko.scala:29-35 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) armeria-backend/fs2-ce2/src/main/scala/sttp/client4/armeria/fs2/ArmeriaFs2Backend.scala:24 — armeria-backend/fs2-ce2/src/main/scala/sttp/client4/armeria/fs2/ArmeriaFs2Backend.scala:24-30 | armeria-backend/fs2/src/main/scala/sttp/client4/armeria/fs2/ArmeriaFs2Backend.scala:27-33 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `armeria-backend/fs2-ce2/src/main/scala/sttp/client4/armeria/fs2/ArmeriaFs2Backend.scala:24` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:147 — core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:147-153 | core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:239-245 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala:47 — effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala:47-53 | effects/fs2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala:46-52 — before extracting anything, compare `effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala` and `effects/fs2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala:47` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) effects/zio/src/main/scalajs/sttp/client4/impl/zio/FetchZioBackend.scala:58 — effects/zio/src/main/scalajs/sttp/client4/impl/zio/FetchZioBackend.scala:58-64 | effects/zio1/src/main/scalajs/sttp/client4/impl/zio/FetchZioBackend.scala:63-69 — before extracting anything, compare `effects/zio/src/main/scalajs/sttp/client4/impl/zio/FetchZioBackend.scala` and `effects/zio1/src/main/scalajs/sttp/client4/impl/zio/FetchZioBackend.scala` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `effects/zio/src/main/scalajs/sttp/client4/impl/zio/FetchZioBackend.scala:58` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 2) observability/otel4s-metrics-backend/src/main/scala/sttp/client4/opentelemetry/otel4s/Otel4sMetricsBackend.scala:174 — observability/otel4s-metrics-backend/src/main/scala/sttp/client4/opentelemetry/otel4s/Otel4sMetricsBackend.scala:174-180 | observability/otel4s-metrics-backend/src/main/scala/sttp/client4/opentelemetry/otel4s/Otel4sMetricsBackend.scala:199-205 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `observability/otel4s-metrics-backend/src/main/scala/sttp/client4/opentelemetry/otel4s/Otel4sMetricsBackend.scala:206` calls `maybe` and `observability/otel4s-metrics-backend/src/main/scala/sttp/client4/opentelemetry/otel4s/Otel4sMetricsBackend.scala:181` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala:92 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala:92-98 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/PekkoHttpBackend.scala:110-116 — before extracting anything, compare `akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala` and `pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/PekkoHttpBackend.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala:210 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala:210-216 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyFromPekko.scala:211-217 — before extracting anything, compare `akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala` and `pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyFromPekko.scala` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note first that the copies are not typed on the same thing: `ByteString` names `akka.util.ByteString` in one and `pekko.util.ByteString` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (7 lines × 2) effects/fs2-ce2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala:37 — effects/fs2-ce2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala:37-43 | effects/fs2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala:37-43 — before extracting anything, compare `effects/fs2-ce2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala` and `effects/fs2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (6 lines × 2) · ×8

Duplicated block (6 lines × 2) core/src/main/scalajvm/sttp/client4/compression/defaultCompressors.scala:16 — core/src/main/scalajvm/sttp/client4/compression/defaultCompressors.scala:16-21 | core/src/main/scalajvm/sttp/client4/compression/defaultCompressors.scala:45-50 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/scalajvm/sttp/client4/compression/defaultCompressors.scala:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) effects/zio1/src/main/scala/sttp/client4/impl/zio/SttpClientStubbingBase.scala:97 — effects/zio1/src/main/scala/sttp/client4/impl/zio/SttpClientStubbingBase.scala:97-102 | effects/zio1/src/main/scala/sttp/client4/impl/zio/SttpClientStubbingBase.scala:116-121 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `effects/zio1/src/main/scala/sttp/client4/impl/zio/SttpClientStubbingBase.scala:97` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:230 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:230-235 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:225-230 — before extracting anything, compare `http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala` and `http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 149 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:230` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:247 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:247-252 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:242-247 — before extracting anything, compare `http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala` and `http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 149 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:247` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:142 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:142-147 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:138-143 — before extracting anything, compare `http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala` and `http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 149 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala:202 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala:202-207 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyFromPekko.scala:203-208 — before extracting anything, compare `akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala` and `pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyFromPekko.scala` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note first that the copies are not typed on the same thing: `ByteString` names `akka.util.ByteString` in one and `pekko.util.ByteString` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 2) core/src/main/scalajvm/sttp/client4/SttpClientExceptionExtensions.scala:23 — core/src/main/scalajvm/sttp/client4/SttpClientExceptionExtensions.scala:23-28 | core/src/main/scalanative/sttp/client4/SttpClientExceptionExtensions.scala:20-25 — before extracting anything, compare `core/src/main/scalajvm/sttp/client4/SttpClientExceptionExtensions.scala` and `core/src/main/scalanative/sttp/client4/SttpClientExceptionExtensions.scala` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/scalajvm/sttp/client4/SttpClientExceptionExtensions.scala:23` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:278 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:278-283 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:273-278 — before extracting anything, compare `http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala` and `http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 149 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (5 lines × 2) · ×8

Duplicated block (5 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/FromAkka.scala:13 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/FromAkka.scala:13-17 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/FromPekko.scala:14-18 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `akka-http-backend/src/main/scala/sttp/client4/akkahttp/FromAkka.scala:13` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/Util.scala:16 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/Util.scala:16-20 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/Util.scala:17-21 — before extracting anything, compare `akka-http-backend/src/main/scala/sttp/client4/akkahttp/Util.scala` and `pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/Util.scala` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `akka-http-backend/src/main/scala/sttp/client4/akkahttp/Util.scala:16` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) core/src/main/scalajvm/sttp/client4/httpclient/HttpClientAsyncBackend.scala:180 — core/src/main/scalajvm/sttp/client4/httpclient/HttpClientAsyncBackend.scala:180-187 | core/src/main/scalajvm/sttp/client4/httpclient/HttpClientSyncBackend.scala:118-122 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/scalajvm/sttp/client4/httpclient/HttpClientAsyncBackend.scala:180` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) effects/fs2-ce2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala:28 — effects/fs2-ce2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala:28-32 | effects/fs2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala:28-32 — before extracting anything, compare `effects/fs2-ce2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala` and `effects/fs2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `effects/fs2-ce2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala:28` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) effects/zio/src/main/scala/sttp/client4/impl/zio/ExtendedEnvBackend.scala:14 — effects/zio/src/main/scala/sttp/client4/impl/zio/ExtendedEnvBackend.scala:14-18 | effects/zio1/src/main/scala/sttp/client4/impl/zio/ExtendedEnvBackend.scala:14-18 — before extracting anything, compare `effects/zio/src/main/scala/sttp/client4/impl/zio/ExtendedEnvBackend.scala` and `effects/zio1/src/main/scala/sttp/client4/impl/zio/ExtendedEnvBackend.scala` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `effects/zio/src/main/scala/sttp/client4/impl/zio/ExtendedEnvBackend.scala:14` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) json/zio-json/src/main/scalajvm/sttp/client4/ziojson/SttpZioJsonApiExtensions.scala:22 — json/zio-json/src/main/scalajvm/sttp/client4/ziojson/SttpZioJsonApiExtensions.scala:22-26 | json/zio1-json/src/main/scalajvm/sttp/client4/ziojson/SttpZioJsonApiExtensions.scala:23-27 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `json/zio-json/src/main/scalajvm/sttp/client4/ziojson/SttpZioJsonApiExtensions.scala:22` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) effects/cats/src/main/scalajvm/sttp/client4/httpclient/cats/HttpClientCatsBackend.scala:140 — effects/cats/src/main/scalajvm/sttp/client4/httpclient/cats/HttpClientCatsBackend.scala:140-144 | effects/fs2/src/main/scalajvm/sttp/client4/httpclient/fs2/HttpClientFs2Backend.scala:179-183 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:223 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:223-227 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:218-222 — before extracting anything, compare `http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala` and `http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 149 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:223` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (9 lines × 2) · ×6

Duplicated block (9 lines × 2) effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/fs2Decompressors.scala:25 — effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/fs2Decompressors.scala:25-33 | effects/fs2/src/main/scala/sttp/client4/impl/fs2/fs2Decompressors.scala:22-30 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/fs2Decompressors.scala:25` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) effects/zio/src/main/scala/sttp/client4/impl/zio/ExtendedEnvBackend.scala:20 — effects/zio/src/main/scala/sttp/client4/impl/zio/ExtendedEnvBackend.scala:20-28 | effects/zio1/src/main/scala/sttp/client4/impl/zio/ExtendedEnvBackend.scala:20-28 — before extracting anything, compare `effects/zio/src/main/scala/sttp/client4/impl/zio/ExtendedEnvBackend.scala` and `effects/zio1/src/main/scala/sttp/client4/impl/zio/ExtendedEnvBackend.scala` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `effects/zio/src/main/scala/sttp/client4/impl/zio/ExtendedEnvBackend.scala:20` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:191 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:191-199 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:186-194 — before extracting anything, compare `http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala` and `http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 149 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:191` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) armeria-backend/cats-ce2/src/main/scala/sttp/client4/armeria/cats/ArmeriaCatsBackend.scala:23 — armeria-backend/cats-ce2/src/main/scala/sttp/client4/armeria/cats/ArmeriaCatsBackend.scala:23-31 | armeria-backend/cats/src/main/scala/sttp/client4/armeria/cats/ArmeriaCatsBackend.scala:22-30 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2ServerSentEvents.scala:7 — effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2ServerSentEvents.scala:7-15 | effects/fs2/src/main/scala/sttp/client4/impl/fs2/Fs2ServerSentEvents.scala:7-15 — before extracting anything, compare `effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2ServerSentEvents.scala` and `effects/fs2/src/main/scala/sttp/client4/impl/fs2/Fs2ServerSentEvents.scala` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) core/src/main/scalajvm/sttp/client4/SttpClientExceptionExtensions.scala:13 — core/src/main/scalajvm/sttp/client4/SttpClientExceptionExtensions.scala:13-21 | core/src/main/scalanative/sttp/client4/SttpClientExceptionExtensions.scala:11-19 — before extracting anything, compare `core/src/main/scalajvm/sttp/client4/SttpClientExceptionExtensions.scala` and `core/src/main/scalanative/sttp/client4/SttpClientExceptionExtensions.scala` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/scalajvm/sttp/client4/SttpClientExceptionExtensions.scala:13` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/src/main/scalajvm/sttp/client4/SttpClientExceptionExtensions.scala:22` calls `Some`, `TimeoutException` and `core/src/main/scalanative/sttp/client4/SttpClientExceptionExtensions.scala:20` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (10 lines × 2) · ×5

Duplicated block (10 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala:155 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala:155-164 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/PekkoHttpBackend.scala:173-182 — before extracting anything, compare `akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala` and `pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/PekkoHttpBackend.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `ByteString` names `akka.util.ByteString` in one and `org.apache.pekko.util.ByteString` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (10 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpClient.scala:67 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpClient.scala:67-76 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/PekkoHttpClient.scala:68-77 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `Flow` names `akka.stream.scaladsl.Flow` in one and `pekko.stream.scaladsl.Flow` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (10 lines × 2) effects/zio/src/main/scala/sttp/client4/impl/zio/ZioWebSockets.scala:58 — effects/zio/src/main/scala/sttp/client4/impl/zio/ZioWebSockets.scala:58-67 | effects/zio1/src/main/scala/sttp/client4/impl/zio/ZioWebSockets.scala:58-67 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `effects/zio/src/main/scala/sttp/client4/impl/zio/ZioWebSockets.scala:58` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:78 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:78-87 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:80-89 — before extracting anything, compare `http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala` and `http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 149 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:78` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 2) effects/cats/src/main/scalajvm/sttp/client4/httpclient/cats/CatsSimpleQueue.scala:13 — effects/cats/src/main/scalajvm/sttp/client4/httpclient/cats/CatsSimpleQueue.scala:13-22 | effects/fs2/src/main/scalajvm/sttp/client4/impl/fs2/Fs2SimpleQueue.scala:13-22 — before extracting anything, compare `effects/cats/src/main/scalajvm/sttp/client4/httpclient/cats/CatsSimpleQueue.scala` and `effects/fs2/src/main/scalajvm/sttp/client4/impl/fs2/Fs2SimpleQueue.scala` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (8 lines × 2) · ×5

Duplicated block (8 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyToAkka.scala:38 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyToAkka.scala:38-45 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyToPekko.scala:39-46 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyToAkka.scala:38` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyToAkka.scala:60 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyToAkka.scala:60-67 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyToPekko.scala:61-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyToAkka.scala:60` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala:28 — effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala:28-35 | effects/fs2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala:27-34 — before extracting anything, compare `effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala` and `effects/fs2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala:28` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala:37 — effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala:37-44 | effects/fs2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala:36-43 — before extracting anything, compare `effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala` and `effects/fs2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala:37` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala:31 — effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala:31-38 | effects/zio1/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala:33-40 — before extracting anything, compare `effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala` and `effects/zio1/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala:31` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (16 lines × 2) · ×3

Duplicated block (16 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala:103 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala:103-118 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/PekkoHttpBackend.scala:121-136 — before extracting anything, compare `akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala` and `pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/PekkoHttpBackend.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala:65 — effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala:65-80 | effects/zio1/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala:90-105 — before extracting anything, compare `effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala` and `effects/zio1/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala:65` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) effects/zio/src/main/scalajvm/sttp/client4/impl/zio/package.scala:10 — effects/zio/src/main/scalajvm/sttp/client4/impl/zio/package.scala:10-25 | effects/zio1/src/main/scala/sttp/client4/impl/zio/package.scala:10-25 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `effects/zio/src/main/scalajvm/sttp/client4/impl/zio/package.scala:10` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.

D4 · Code Duplication · Duplicated block (12 lines × 2) · ×3

Duplicated block (12 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/ToAkka.scala:40 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/ToAkka.scala:40-51 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/ToPekko.scala:41-52 — before extracting anything, compare `akka-http-backend/src/main/scala/sttp/client4/akkahttp/ToAkka.scala` and `pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/ToPekko.scala` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:128 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:128-139 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:124-135 — before extracting anything, compare `http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala` and `http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 149 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala:306 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala:306-317 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/PekkoHttpBackend.scala:324-335 — before extracting anything, compare `akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala` and `pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/PekkoHttpBackend.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D6 · Cohesion (LCOM4) · Low cohesion · ×3

Low cohesion: HttpClientBackend (LCOM4 4) core/src/main/scalajvm/sttp/client4/httpclient/HttpClientBackend.scala:41 — HttpClientBackend's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: OpenTelemetryMetricsListener (LCOM4 4) observability/opentelemetry-backend/src/main/scala/sttp/client4/opentelemetry/OpenTelemetryMetricsBackend.scala:89 — OpenTelemetryMetricsListener's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: HttpServer (LCOM4 4) testing/server/src/main/scala/sttp/client4/testing/server/HttpServer.scala:38 — HttpServer's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.

D2 · Cognitive Complexity · ZioWebSockets.compilePipe (cognitive 27) · ×2

ZioWebSockets.compilePipe (cognitive 27) effects/zio/src/main/scala/sttp/client4/impl/zio/ZioWebSockets.scala:8 — ZioWebSockets.compilePipe has cognitive complexity 27 (threshold 15). Drivers by points: match/switch 5 (15 pts), if/else 4 (6 pts), loops 3 (6 pts) (nesting depth added 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ZioWebSockets.compilePipe (cognitive 27) effects/zio1/src/main/scala/sttp/client4/impl/zio/ZioWebSockets.scala:8 — ZioWebSockets.compilePipe has cognitive complexity 27 (threshold 15). Drivers by points: match/switch 5 (15 pts), if/else 4 (6 pts), loops 3 (6 pts) (nesting depth added 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D3 · God Classes · TooManyMethods · ×2

TooManyMethods: PartialRequestBuilder core/src/main/scala/sttp/client4/requestBuilder.scala:34 — TooManyMethods — 63 methods. The bar is 30 methods; this is 33 over it, 2.10× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: SttpApi core/src/main/scala/sttp/client4/SttpApi.scala:16 — TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.

D4 · Code Duplication · Duplicated block (40 lines × 2) · ×2

Duplicated block (40 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala:150 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala:150-189 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyFromPekko.scala:151-190 — before extracting anything, compare `akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala` and `pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyFromPekko.scala` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala:150` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (40 lines × 2) http4s-backend/src/main/scalajvm/sttp/client4/http4s/Http4sBackend.scala:23 — http4s-backend/src/main/scalajvm/sttp/client4/http4s/Http4sBackend.scala:23-82 | http4s-backend/src/main/scalanative/sttp/client4/http4s/Http4sBackend.scala:23-62 — before extracting anything, compare `http4s-backend/src/main/scalajvm/sttp/client4/http4s/Http4sBackend.scala` and `http4s-backend/src/main/scalanative/sttp/client4/http4s/Http4sBackend.scala` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (18 lines × 2) · ×2

Duplicated block (18 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala:93 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala:93-110 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyFromPekko.scala:94-111 — before extracting anything, compare `akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala` and `pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyFromPekko.scala` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala:93` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/ToAkka.scala:20 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/ToAkka.scala:20-37 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/ToPekko.scala:21-38 — before extracting anything, compare `akka-http-backend/src/main/scala/sttp/client4/akkahttp/ToAkka.scala` and `pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/ToPekko.scala` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `ParsingResult` names `akka.http.scaladsl.model.HttpHeader.ParsingResult` in one and `pekko.http.scaladsl.model.HttpHeader.ParsingResult` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.

D4 · Code Duplication · Duplicated block (17 lines × 2) · ×2

Duplicated block (17 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala:131 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala:131-147 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyFromPekko.scala:132-148 — before extracting anything, compare `akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala` and `pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyFromPekko.scala` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala:131` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:92 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:92-108 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:93-109 — before extracting anything, compare `http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala` and `http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 149 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (15 lines × 2) · ×2

Duplicated block (15 lines × 2) effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala:54 — effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala:54-68 | effects/fs2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala:53-67 — before extracting anything, compare `effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala` and `effects/fs2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala:54` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:258 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:258-272 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:253-267 — before extracting anything, compare `http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala` and `http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 149 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:258` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (13 lines × 2) · ×2

Duplicated block (13 lines × 2) effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala:76 — effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala:76-88 | effects/fs2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala:75-87 — before extracting anything, compare `effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala` and `effects/fs2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:173 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:173-185 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:168-180 — before extracting anything, compare `http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala` and `http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 149 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D1 · Cyclomatic Complexity · AbstractBackendStub.adjustResponseBody (cyclomatic 29) · ×1

AbstractBackendStub.adjustResponseBody (cyclomatic 29) core/src/main/scala/sttp/client4/testing/AbstractBackendStub.scala:160 — AbstractBackendStub.adjustResponseBody has cyclomatic complexity 29 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · BodyFromAkka.webSocketAndFlow (cyclomatic 16) · ×1

BodyFromAkka.webSocketAndFlow (cyclomatic 16) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala:127 — BodyFromAkka.webSocketAndFlow has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · Slf4jLogger.apply (cyclomatic 16) · ×1

Slf4jLogger.apply (cyclomatic 16) logging/slf4j/src/main/scala/sttp/client4/logging/slf4j/Slf4jLogger.scala:20 — Slf4jLogger.apply has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · BodyFromPekko.webSocketAndFlow (cyclomatic 16) · ×1

BodyFromPekko.webSocketAndFlow (cyclomatic 16) pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyFromPekko.scala:128 — BodyFromPekko.webSocketAndFlow has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D2 · Cognitive Complexity · BodyFromAkka.webSocketAndFlow (cognitive 31) · ×1

BodyFromAkka.webSocketAndFlow (cognitive 31) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala:127 — BodyFromAkka.webSocketAndFlow has cognitive complexity 31 (threshold 15). Drivers by points: match/switch 5 (18 pts), if/else 4 (10 pts), loops 2 (3 pts) (nesting depth added 20). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · BodyFromPekko.webSocketAndFlow (cognitive 31) · ×1

BodyFromPekko.webSocketAndFlow (cognitive 31) pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyFromPekko.scala:128 — BodyFromPekko.webSocketAndFlow has cognitive complexity 31 (threshold 15). Drivers by points: match/switch 5 (18 pts), if/else 4 (10 pts), loops 2 (3 pts) (nesting depth added 20). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · Otel4sMetricsBackend.metricsListener (cognitive 21) · ×1

Otel4sMetricsBackend.metricsListener (cognitive 21) observability/otel4s-metrics-backend/src/main/scala/sttp/client4/opentelemetry/otel4s/Otel4sMetricsBackend.scala:63 — Otel4sMetricsBackend.metricsListener has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: one other method here (MetricsRequestListener.captureResponseMetrics) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.

D2 · Cognitive Complexity · MetricsRequestListener.captureResponseMetrics (cognitive 21) · ×1

MetricsRequestListener.captureResponseMetrics (cognitive 21) observability/otel4s-metrics-backend/src/main/scala/sttp/client4/opentelemetry/otel4s/Otel4sMetricsBackend.scala:159 — MetricsRequestListener.captureResponseMetrics has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: one other method here (Otel4sMetricsBackend.metricsListener) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.

D2 · Cognitive Complexity · AbstractBackendStub.adjustResponseBody (cognitive 20) · ×1

AbstractBackendStub.adjustResponseBody (cognitive 20) core/src/main/scala/sttp/client4/testing/AbstractBackendStub.scala:160 — AbstractBackendStub.adjustResponseBody has cognitive complexity 20 (threshold 15). Drivers by points: match/switch 8 (14 pts), if/else 6 (nesting depth added 6). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · GZIPCompressingInputStream.read (cognitive 19) · ×1

GZIPCompressingInputStream.read (cognitive 19) core/src/main/scalajvm/sttp/client4/compression/GZIPCompressingInputStream.scala:54 — GZIPCompressingInputStream.read has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (18 pts), match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D20 · ADR Quality · No consequences/trade-offs section (e.g. loss of validation for unsafeApply) are present and the body is clipped · ×1

No consequences/trade-offs section (e.g. loss of validation for unsafeApply) are present and the body is clipped docs/adr/0002-http-model-conventions.md

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D3 · God Classes · MethodTooLong · ×1

MethodTooLong: HttpServer.paramsToString testing/server/src/main/scala/sttp/client4/testing/server/HttpServer.scala:48 — MethodTooLong — paramsToString runs 319 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 219 over it, 3.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D4 · Code Duplication · Near-duplicate member pair (59 shared lines) · ×1

Near-duplicate member pair (59 shared lines) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:42 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:42-125 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:43-121 — These two members are variants of one another: 59 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Near-duplicate member pair (38 shared lines) · ×1

Near-duplicate member pair (38 shared lines) effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala:28 — effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala:28-68 | effects/fs2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala:27-67 — These two members are variants of one another: 38 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Near-duplicate member pair (37 shared lines) · ×1

Near-duplicate member pair (37 shared lines) effects/fs2-ce2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala:27 — effects/fs2-ce2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala:27-69 | effects/fs2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala:27-69 — These two members are variants of one another: 37 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Near-duplicate member pair (36 shared lines) · ×1

Near-duplicate member pair (36 shared lines) effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala:31 — effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala:31-80 | effects/zio1/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala:33-105 — These two members are variants of one another: 36 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Near-duplicate member pair (27 shared lines) · ×1

Near-duplicate member pair (27 shared lines) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:230 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:230-272 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:225-267 — These two members are variants of one another: 27 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Near-duplicate member pair (24 shared lines) · ×1

Near-duplicate member pair (24 shared lines) core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:146 — core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:146-184 | core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:238-359 — These two members are variants of one another: 24 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Near-duplicate member pair (23 shared lines) · ×1

Near-duplicate member pair (23 shared lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyToAkka.scala:27 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyToAkka.scala:27-81 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyToPekko.scala:28-82 — These two members are variants of one another: 23 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1

Members sharing a duplicated core (4 members, 50+ identical tokens) json/play-json/src/main/scala/sttp/client4/playJson/SttpPlayJsonApi.scala:49 — json/play-json/src/main/scala/sttp/client4/playJson/SttpPlayJsonApi.scala:49-55 | json/upickle/src/main/scala/sttp/client4/upicklejson/SttpUpickleApi.scala:48-54 | json/zio-json/src/main/scala/sttp/client4/ziojson/SttpZioJsonApi.scala:51-57 | json/zio1-json/src/main/scala/sttp/client4/ziojson/SttpZioJsonApi.scala:51-57 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.

D4 · Code Duplication · Duplicated block (32–33 lines × 2) · ×1

Duplicated block (32–33 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:42 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:42-73 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:43-75 — before extracting anything, compare `http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala` and `http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 149 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:42` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (29 lines × 2) · ×1

Duplicated block (29 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpClient.scala:35 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpClient.scala:35-63 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/PekkoHttpClient.scala:36-64 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `Flow` names `akka.stream.scaladsl.Flow` in one and `pekko.stream.scaladsl.Flow` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.

D4 · Code Duplication · Duplicated block (25 lines × 2) · ×1

Duplicated block (25 lines × 2) effects/fs2-ce2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala:45 — effects/fs2-ce2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala:45-69 | effects/fs2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala:45-69 — before extracting anything, compare `effects/fs2-ce2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala` and `effects/fs2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `effects/fs2-ce2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala:45` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (12–15 lines × 2) · ×1

Duplicated block (12–15 lines × 2) effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala:43 — effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala:43-54 | effects/zio1/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala:50-64 — before extracting anything, compare `effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala` and `effects/zio1/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala:43` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (14 lines × 2) · ×1

Duplicated block (14 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala:112 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala:112-125 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyFromPekko.scala:113-126 — before extracting anything, compare `akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala` and `pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyFromPekko.scala` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala:112` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×1

Duplicated block (12–13 lines × 2) core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:172 — core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:172-184 | core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:332-343 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:172` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (11 lines × 2) · ×1

Duplicated block (11 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:152 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:152-162 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:147-157 — before extracting anything, compare `http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala` and `http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 149 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:152` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (7–9 lines × 2) · ×1

Duplicated block (7–9 lines × 2) core/src/main/scalajs/sttp/client4/WebSocketImpl.scala:25 — core/src/main/scalajs/sttp/client4/WebSocketImpl.scala:25-31 | core/src/main/scalajvm/sttp/client4/internal/httpclient/WebSocketImpl.scala:27-35 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/scalajs/sttp/client4/WebSocketImpl.scala:25` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.

D4 · Code Duplication · Duplicated block (4–7 lines × 3) · ×1

Duplicated block (4–7 lines × 3) core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:160 — core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:160-163 | core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:322-328 | core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:347-353 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (6 lines × 4) · ×1

Duplicated block (6 lines × 4) json/play-json/src/main/scala/sttp/client4/playJson/SttpPlayJsonApi.scala:50 — json/play-json/src/main/scala/sttp/client4/playJson/SttpPlayJsonApi.scala:50-55 | json/upickle/src/main/scala/sttp/client4/upicklejson/SttpUpickleApi.scala:49-54 | json/zio-json/src/main/scala/sttp/client4/ziojson/SttpZioJsonApi.scala:52-57 | json/zio1-json/src/main/scala/sttp/client4/ziojson/SttpZioJsonApi.scala:52-57 — before extracting anything, compare `json/zio-json/src/main/scala/sttp/client4/ziojson/SttpZioJsonApi.scala` and `json/zio1-json/src/main/scala/sttp/client4/ziojson/SttpZioJsonApi.scala` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `json/play-json/src/main/scala/sttp/client4/playJson/SttpPlayJsonApi.scala:50` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (5 lines × 3) · ×1

Duplicated block (5 lines × 3) core/src/main/scalajs/sttp/client4/SttpClientExceptionExtensions.scala:20 — core/src/main/scalajs/sttp/client4/SttpClientExceptionExtensions.scala:20-24 | core/src/main/scalajvm/sttp/client4/SttpClientExceptionExtensions.scala:30-34 | core/src/main/scalanative/sttp/client4/SttpClientExceptionExtensions.scala:26-30 — before extracting anything, compare `core/src/main/scalajs/sttp/client4/SttpClientExceptionExtensions.scala` and `core/src/main/scalajvm/sttp/client4/SttpClientExceptionExtensions.scala` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/scalajs/sttp/client4/SttpClientExceptionExtensions.scala:20` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `core/src/main/scalajvm/sttp/client4/SttpClientExceptionExtensions.scala:27` calls `Some`, `ReadException` and `core/src/main/scalanative/sttp/client4/SttpClientExceptionExtensions.scala:23` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (27 lines × 3) · ×1

Duplicated block (27 lines × 3) armeria-backend/zio/src/main/scala/sttp/client4/armeria/zio/package.scala:25 — armeria-backend/zio/src/main/scala/sttp/client4/armeria/zio/package.scala:25-51 | effects/zio/src/main/scalajs/sttp/client4/impl/zio/package.scala:12-107 | effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/package.scala:25-87 — before extracting anything, compare `armeria-backend/zio/src/main/scala/sttp/client4/armeria/zio/package.scala` and `effects/zio/src/main/scalajs/sttp/client4/impl/zio/package.scala` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `effects/zio/src/main/scalajs/sttp/client4/impl/zio/package.scala:12` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.

D4 · Code Duplication · Duplicated block (28 lines × 2) · ×1

Duplicated block (28 lines × 2) armeria-backend/zio1/src/main/scala/sttp/client4/armeria/zio/zio.scala:38 — armeria-backend/zio1/src/main/scala/sttp/client4/armeria/zio/zio.scala:38-65 | effects/zio1/src/main/scalajvm/sttp/client4/httpclient/zio/package.scala:36-63 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `armeria-backend/zio1/src/main/scala/sttp/client4/armeria/zio/zio.scala:38` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1

Duplicated block (20 lines × 2) core/src/main/scalajvm/sttp/client4/internal/SttpFileExtensions.scala:13 — core/src/main/scalajvm/sttp/client4/internal/SttpFileExtensions.scala:13-32 | core/src/main/scalanative/sttp/client4/internal/SttpFileExtensions.scala:12-31 — before extracting anything, compare `core/src/main/scalajvm/sttp/client4/internal/SttpFileExtensions.scala` and `core/src/main/scalanative/sttp/client4/internal/SttpFileExtensions.scala` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/scalajvm/sttp/client4/internal/SttpFileExtensions.scala:13` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.

D4 · Code Duplication · Duplicated block (45 lines × 2) · ×1

Duplicated block (45 lines × 2) effects/cats-ce2/src/main/scala/sttp/client4/impl/cats/implicits.scala:14 — effects/cats-ce2/src/main/scala/sttp/client4/impl/cats/implicits.scala:14-58 | effects/cats/src/main/scala/sttp/client4/impl/cats/implicits.scala:14-58 — before extracting anything, compare `effects/cats-ce2/src/main/scala/sttp/client4/impl/cats/implicits.scala` and `effects/cats/src/main/scala/sttp/client4/impl/cats/implicits.scala` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `effects/cats-ce2/src/main/scala/sttp/client4/impl/cats/implicits.scala:14` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.

D4 · Code Duplication · Duplicated block (63 lines × 2) · ×1

Duplicated block (63 lines × 2) effects/zio/src/main/scalajs/sttp/client4/impl/zio/package.scala:12 — effects/zio/src/main/scalajs/sttp/client4/impl/zio/package.scala:12-107 | effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/package.scala:25-87 — before extracting anything, compare `effects/zio/src/main/scalajs/sttp/client4/impl/zio/package.scala` and `effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/package.scala` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `effects/zio/src/main/scalajs/sttp/client4/impl/zio/package.scala:12` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.

Minor — 7 finding(s)

D16 · Bus Factor · Off-boarding risk · ×1

Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 4 significant file(s) lose their only recent owner: armeria-backend/monix/src/main/scala/sttp/client4/armeria/monix/ArmeriaMonixBackend.scala, armeria-backend/fs2-ce2/src/main/scala/sttp/client4/armeria/fs2/ArmeriaFs2Backend.scala, armeria-backend/cats-ce2/src/main/scala/sttp/client4/armeria/cats/ArmeriaCatsBackend.scala, armeria-backend/cats/src/main/scala/sttp/client4/armeria/cats/ArmeriaCatsBackend.scala. Pair on, review, or document these before any departure.

D16 · Bus Factor · Further sole-owners (lower concentration) · ×1

Further sole-owners (lower concentration) — 3 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (8 single-owned of 140 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 140 of the 322 production source files in this repository met that bar). They are anonymized user #2 (2 file(s)), anonymized user #3 (1 file(s)), anonymized user #4 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

P3 · Security & performance tooling · No SAST · ×1

No SAST — No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 6915 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

P4 · Deployment & Rollback · No release approval gate · ×1

No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b877eaf7758340ed92ef9d95cb3effff/history.json --exit-code 0 --source .	0	artifacts/raw/gitleaks-history.json
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b877eaf7758340ed92ef9d95cb3effff/tree.json --exit-code 0 --source .	0	artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	12	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	osv-scanner	—	osv-scanner --format json --recursive .	0	artifacts/raw/osv-scanner.json
D31 · IaC & Container Security	trivy	—	trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.	0	—
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.	0	—
D37 · Vulnerability-disclosure Policy	disclosure	—	disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.	0	—
D40 · Network Egress Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.	0	—
D43 · Malicious Dependencies	osv-scanner	—	osv-scanner --format json --recursive .	0	artifacts/raw/osv-scanner.json

Run 01a0e3c8-7e74-719b-9083-67bef1d2dc63 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Softwaremill/sttp

Findings by grade

This survey was produced by

Executive summary

Top priorities

Diagnosis — what's actually going on

Architecture — module dependency matrix

At a glance — Code Health · 93% · Exemplary ·

At a glance — Architecture · 98% · Exemplary ·

At a glance — Maturity · 73% · Strong ·

At a glance — Readiness · 55% · Adequate · gated by P3 ·

At a glance — Security · 81% · Adequate · gated by D36 ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts