Public report of softwaremill/sttp, published 14 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 14 November 2026, 07:37 UTC · Survey ID cd_14468fa4229649148a1e6af6deec1749

softwaremill/sttp

Measured 14 November 2026, 07:37 UTC, at code version 3b20840

Knowledge freshness is not measured: Freshness signal contradicted by repo activity.

CAI score 64out of 100 Adequate
CriticalWeakAdequateStrongExemplary
No change since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A medium codebase: 23,042 lines of product code in 37 projects, tests not counted · Estimated rebuild effort: about 0.3 person-years · Weakest lens: Code Health, 56

Findings by how serious they are

11 critical 172 serious 46 minor

9 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 07:37 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

51of 51 dimensions measured by tools.
194of 229 findings point to an exact file and line, so you can open each one in the code. The other 35 concern the repository as a whole, such as missing documentation.
51dimensions across 6 lenses, read from 23,042 lines of product code in 37 projects.
Chapters

Executive summary

softwaremill/sttp falls short of our standard for production, held back most by its Code Health lens, the quality of the code itself. It scores 64 out of 100 and is rated Adequate, and ten of its 11 critical findings are security problems in the build pipeline.

Code Health, at 56, is the weakest lens and counts most in the score. The best first step is adding automated security scanning, worth about 5 points. Writing log messages as searchable templates would lift Code Health itself, worth about 4 points. Raising Code Health to 70 would lift the score to about 67.

Eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two secrets can leak from the build pipeline, and one set of files in separate parts keeps changing together, which points to a hidden dependency. Pinning each tool to an exact version, limiting each secret to its own step and making the hidden dependencies explicit would close these risks.

The product code is 23,042 lines, about €38,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Code Health 56 · counts for 46%Production Readiness 57 · counts for 25%Security and Compliance 72 · counts for 14%Maturity 84 · counts for 8%Architecture 96 · counts for 4%Performance 100 · counts for 2%

If Code Health rose from 56 to 70, the lowest score rated Strong, the score would rise from 64 to about 67.

Code composition: what the lines of code are
Product code 68%Tests 32%
New since the last survey: 66 findings

These 66 critical or serious findings weren't in the previous survey, on 26 October 2026.

  • Code Duplication · Near-duplicate member pair (65 shared lines) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala
  • Code Duplication · Edited copy of a member (68 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala
  • Code Duplication · Edited copy of a member (41 corresponding lines) effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala
  • Code Duplication · Edited copy of a member (21 corresponding lines) core/src/main/scalajvm/sttp/client4/SttpClientExceptionExtensions.scala
  • Code Duplication · Edited copy of a member (37 corresponding lines) effects/zio/src/main/scala/sttp/client4/impl/zio/ZioWebSockets.scala
  • Code Duplication · Edited copy of a member (33 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala
  • Code Duplication · Edited copy of a member (26 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala
  • Code Duplication · Edited copy of a member (15 corresponding lines) effects/zio/src/main/scala/sttp/client4/impl/zio/ExtendedEnvBackend.scala
  • Code Duplication · Edited copy of a member (12 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/FromAkka.scala
  • Code Duplication · Edited copy of a member (15 corresponding lines) core/src/main/scalajvm/sttp/client4/compression/defaultCompressors.scala
  • Code Duplication · Edited copy of a member (16 corresponding lines) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala
  • Code Duplication · Edited copy of a member (27 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala
  • Code Duplication · Edited copy of a member (16 corresponding lines) effects/fs2-ce2/src/main/scalajvm/sttp/client4/httpclient/fs2/HttpClientFs2Backend.scala
  • Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) effects/monix/src/main/scalajs/sttp/client4/impl/monix/FetchMonixBackend.scala
  • Code Duplication · Edited copy of a member (13 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyToAkka.scala
  • Code Duplication · Edited copy of a member (12 corresponding lines) effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/fs2Decompressors.scala
  • Code Duplication · Edited copy of a member (8 corresponding lines) effects/zio1/src/main/scala/sttp/client4/impl/zio/SttpClientStubbingBase.scala
  • Code Duplication · Edited copy of a member (21 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/ToAkka.scala
  • Code Duplication · Edited copy of a member (9 corresponding lines) json/zio-json/src/main/scalajvm/sttp/client4/ziojson/SttpZioJsonApiExtensions.scala
  • Code Duplication · Edited copy of a member (10 corresponding lines) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala
  • Code Duplication · Edited copy of a member (16 corresponding lines) core/src/main/scalajs/sttp/client4/WebSocketImpl.scala
  • Code Duplication · Edited copy of a member (12 corresponding lines) core/src/main/scala/sttp/client4/testing/package.scala
  • Code Duplication · Edited copy of a member (16 corresponding lines) core/src/main/scalajvm/sttp/client4/httpclient/HttpClientBackend.scala
  • Code Duplication · Edited copy of a member (6 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaCompressor.scala
  • Code Duplication · Edited copy of a member (7 corresponding lines) core/src/main/scalajvm/sttp/client4/internal/httpclient/BodyFromHttpClient.scala
  • Code Duplication · Edited copy of a member (11 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala
  • Code Duplication · Edited copy of a member (9 corresponding lines) armeria-backend/fs2-ce2/src/main/scala/sttp/client4/armeria/fs2/ArmeriaFs2Backend.scala
  • Code Duplication · Edited copy of a member (13 corresponding lines) effects/zio/src/main/scala/sttp/client4/impl/zio/ZioWebSockets.scala
  • Code Duplication · Edited copy of a member (7 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/FromAkka.scala
  • Code Duplication · Edited copy of a member (4 corresponding lines) effects/zio/src/main/scalajvm/sttp/client4/impl/zio/zioDecompressors.scala
  • Code Duplication · Edited copy of a member (9 corresponding lines) armeria-backend/zio/src/main/scala/sttp/client4/armeria/zio/ArmeriaZioBackend.scala
  • Code Duplication · Edited copy of a member (15 corresponding lines) core/src/main/scala/sttp/client4/internal/package.scala
  • Code Duplication · Edited copy of a member (7 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala
  • Code Duplication · Edited copy of a member (4 corresponding lines) armeria-backend/fs2-ce2/src/main/scala/sttp/client4/armeria/fs2/ArmeriaFs2Backend.scala
  • Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) json/circe/src/main/scala/sttp/client4/circe/SttpCirceApi.scala
  • Code Duplication · Edited copies of one member (4 members, 4+ corresponding lines) armeria-backend/cats/src/main/scala/sttp/client4/armeria/cats/ArmeriaCatsBackend.scala
  • Code Duplication · Edited copy of a member (10 corresponding lines) observability/prometheus-backend/src/main/scala/sttp/client4/prometheus/PrometheusBackend.scala
  • Code Duplication · Edited copy of a member (7 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala
  • Code Duplication · Edited copy of a member (16 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala
  • Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) armeria-backend/src/main/scala/sttp/client4/armeria/future/ArmeriaFutureBackend.scala
  • Code Duplication · Edited copy of a member (11 corresponding lines) effects/cats/src/main/scalajvm/sttp/client4/httpclient/cats/HttpClientCatsBackend.scala
  • Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) armeria-backend/fs2/src/main/scala/sttp/client4/armeria/fs2/ArmeriaFs2Backend.scala
  • Code Duplication · Edited copy of a member (4 corresponding lines) armeria-backend/zio/src/main/scala/sttp/client4/armeria/zio/ArmeriaZioBackend.scala
  • Code Duplication · Edited copy of a member (5 corresponding lines) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala
  • Code Duplication · Edited copy of a member (4 corresponding lines) armeria-backend/zio1/src/main/scala/sttp/client4/armeria/zio/ArmeriaZioBackend.scala
  • Code Duplication · Edited copy of a member (5 corresponding lines) effects/zio/src/main/scalajs/sttp/client4/impl/zio/FetchZioBackend.scala
  • Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) armeria-backend/monix/src/main/scala/sttp/client4/armeria/monix/ArmeriaMonixBackend.scala
  • Code Duplication · Edited copies of one member (4 members, 4+ corresponding lines) core/src/main/scala/sttp/client4/SttpWebSocketStreamApi.scala
  • Code Duplication · Edited copy of a member (5 corresponding lines) effects/cats-ce2/src/main/scalajs/sttp/client4/impl/cats/FetchCatsBackend.scala
  • Code Duplication · Edited copy of a member (4 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/ToAkka.scala
  • Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) effects/cats-ce2/src/main/scalajs/sttp/client4/impl/cats/FetchCatsBackend.scala
  • Code Duplication · Edited copy of a member (6 corresponding lines) observability/opentelemetry-backend/src/main/scala/sttp/client4/opentelemetry/OpenTelemetryMetricsBackend.scala
  • Code Duplication · Edited copy of a member (4 corresponding lines) effects/fs2/src/main/scalajvm/sttp/client4/httpclient/fs2/HttpClientFs2Backend.scala
  • Code Duplication · Edited copy of a member (10 corresponding lines) effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/HttpClientZioBackend.scala
  • Code Duplication · Edited copy of a member (5 corresponding lines) armeria-backend/zio/src/main/scala/sttp/client4/armeria/zio/ArmeriaZioBackend.scala
  • Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) effects/monix/src/main/scalajs/sttp/client4/impl/monix/FetchMonixBackend.scala
  • Code Duplication · Edited copies of one member (3 members, 1+ corresponding lines) armeria-backend/cats-ce2/src/main/scala/sttp/client4/armeria/cats/ArmeriaCatsBackend.scala
  • Code Duplication · Edited copy of a member (9 corresponding lines) effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/HttpClientZioBackend.scala
  • Code Duplication · Edited copy of a member (6 corresponding lines) observability/otel4s-metrics-backend/src/main/scala/sttp/client4/opentelemetry/otel4s/Otel4sMetricsBackend.scala
  • Code Duplication · Edited copy of a member (1 corresponding lines) core/src/main/scala/sttp/client4/SttpApi.scala
  • Code Duplication · Edited copy of a member (3 corresponding lines) effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/HttpClientZioBackend.scala
  • Code Duplication · Duplicated block (38–39 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala
  • Code Duplication · Duplicated block (10–13 lines × 2) core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala
  • Code Duplication · Duplicated block (6 lines × 2) core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala
  • Code Duplication · Duplicated block (7 lines × 2) core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala
  • Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) examples-ce2/src/main/scala/sttp/client4/examples/WebSocketMonix.scala

We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 13 findings

These 13 critical or serious findings were in the previous survey, on 26 October 2026, and are gone from this one.

  • Code Duplication · Near-duplicate member pair (59 shared lines) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala
  • Code Duplication · Near-duplicate member pair (38 shared lines) effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala
  • Code Duplication · Near-duplicate member pair (24 shared lines) core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala
  • Code Duplication · Duplicated block (32–33 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala
  • Code Duplication · Duplicated block (15 lines × 2) effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala
  • Code Duplication · Duplicated block (8 lines × 2) effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala
  • Code Duplication · Duplicated block (7 lines × 2) armeria-backend/fs2-ce2/src/main/scala/sttp/client4/armeria/fs2/ArmeriaFs2Backend.scala
  • Code Duplication · Duplicated block (7 lines × 2) core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala
  • Code Duplication · Duplicated block (4–7 lines × 3) core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala
  • Code Duplication · Duplicated block (6 lines × 2) effects/zio1/src/main/scala/sttp/client4/impl/zio/SttpClientStubbingBase.scala
  • Code Duplication · Duplicated block (6 lines × 2) core/src/main/scalajvm/sttp/client4/SttpClientExceptionExtensions.scala
  • Explicit Debt · TodoComment core/src/test/scalanative/sttp/client4/testing/SyncHttpTestExtensions.scala
  • Explicit Debt · TodoComment armeria-backend/zio/src/test/scala/sttp/client4/armeria/zio/ArmeriaZioStreamingTest.scala
Rebuild cost: about €38,000 · Estimate
Cost to rebuild€13,000 to €64,000, for 213 to 675 hours of work, about 0.3 person-years for one engineer
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.9 at a score of 64. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 23,042 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
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.
Raises the score by about 5 points · Medium effort · Security & performance tooling
2
Interpolated log message defeats structured logging
Raises the score by about 4 points · Medium effort · Structured logging
3
On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`.
Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
Raises the score by about 4 points · Medium effort · Nullable reference types

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €38,000 to build again, about 0.3 person-years of work. Its weakest lens is Code Health, at 56 (Adequate). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
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. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch akkaHttpBackend akkaHttpBackend armeriaBackend armeriaBackend cachingBackend cachingBackend core core cachingBackend->core jsoniter jsoniter cachingBackend->jsoniter circe circe circe->core json4s json4s json4s->core jsonCommon jsonCommon jsonCommon->core jsoniter->core openTelemetryBackend openTelemetryBackend openTelemetryBackend->core openTelemetryTracingZioBackend openTelemetryTracingZioBackend openTelemetryTracingZioBackend->core play29Json play29Json play29Json->core playJson playJson playJson->core prometheusBackend prometheusBackend prometheusBackend->core scribeBackend scribeBackend scribeBackend->core slf4jBackend slf4jBackend slf4jBackend->core sprayJson sprayJson sprayJson->core tethysJson tethysJson tethysJson->core upickle upickle upickle->core zio1Json zio1Json zio1Json->core zioJson zioJson zioJson->core __more__ +17 more projects

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

91 modules, with 170 dependencies between them. 2 loops run through 10 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 51 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 BackendOptions2 curl.internal3 internal.ws4 monad5 ws6 internal7 wrappers8 logging9 testing10 sttp.client411 ResponseException12 caching13 compression14 curl15 curl.AbstractCurlBackend16 fetch17 listener18 okhttp19 akkahttp20 armeria21 circe22 curl.cats23 curl.zio24 impl.cats25 impl.fs226 impl.monix27 impl.zio28 internal.httpclient29 okhttp.monix30 opentelemetry31 prometheus32 armeria.cats33 armeria.future34 armeria.scalaz35 armeria.zio36 httpclient37 httpclient.cats38 httpclient.fs239 httpclient.monix40 httpclient.zio
1 BackendOptions
2 curl.internal
3 internal.ws
4 monad2
5 ws3
6 internal129
7 wrappers221
8 logging16
9 testing124
10 sttp.client4115122
11 ResponseException2
12 caching14
13 compression3
14 curl418
15 curl.AbstractCurlBackend11
16 fetch136
17 listener14
18 okhttp516
19 akkahttp126
20 armeria1181
21 circe31
22 curl.cats11
23 curl.zio11
24 impl.cats1281
25 impl.fs211831
26 impl.monix1111
27 impl.zio1131251
28 internal.httpclient1611
29 okhttp.monix113
30 opentelemetry1131
31 prometheus91
32 armeria.cats12
33 armeria.future12
34 armeria.scalaz12
35 armeria.zio12121
36 httpclient52159
37 httpclient.cats2141
38 httpclient.fs211351
39 httpclient.monix111251
40 httpclient.zio11152151
Uses a module listed above itPart of a loopThe module itself
1 BackendOptions2 curl.internal3 internal.ws4 monad5 ws6 internal7 wrappers8 logging9 testing10 sttp.client411 ResponseException12 caching13 compression14 curl15 curl.AbstractCurlBackend16 fetch17 listener18 okhttp19 akkahttp20 armeria21 circe22 curl.cats23 curl.zio24 impl.cats25 impl.fs226 impl.monix27 impl.zio28 internal.httpclient29 okhttp.monix30 opentelemetry31 prometheus32 armeria.cats33 armeria.future34 armeria.scalaz35 armeria.zio36 httpclient37 httpclient.cats38 httpclient.fs239 httpclient.monix40 httpclient.zioBackendOptions1curl.internal2internal.ws3monad4ws5internal6wrappers7logging8testing9sttp.client410ResponseException11caching12compression13curl14curl.AbstractCurlBackend15fetch16listener17okhttp18akkahttp19armeria20circe21curl.cats22curl.zio23impl.cats24impl.fs225impl.monix26impl.zio27internal.httpclient28okhttp.monix29opentelemetry30prometheus31armeria.cats32armeria.future33armeria.scalaz34armeria.zio35httpclient36httpclient.cats37httpclient.fs238httpclient.monix39httpclient.zio402312922116124115122214341811136145161261181311111128111831111111312511611113113191121212121215215921411135111125111152151+51 more modules (most-connected shown)

At a glance — Code Health · 56% · Adequate · gated by X4, X5 ·

At a glance — Architecture · 96% · Exemplary ·

At a glance — Maturity · 84% · Strong ·

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

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

At a glance — Performance · 100% · Exemplary ·

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 categoryFindingsSeverity
A05:2025 — Injection12High / Critical
A03:2025 — Software Supply Chain Failures6Medium

Roadmap

Top priorities: 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; Interpolated log message defeats structured logging; On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.

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

Do thisHelpsEffortDimension
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.+5.1 ptsMediumSecurity & performance tooling
Interpolated log message defeats structured logging+4.1 ptsMediumStructured logging
On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.+4.1 ptsMediumNullable reference types
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.+2.4 ptsMediumDeployment & Rollback
Resolve the 4 ADR has no Consequences section finding(s) in ADR Quality — start with 0001-extract-stream-from-http4s.md, 0002-http-model-conventions.md, 0003-separate-backend-types.md.+1.1 ptsLowADR Quality
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2).+0.5 ptsLowStatic Analysis (SAST)
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.+0.4 ptsLowSupply-chain Provenance & Signing
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED.+0.4 ptsLowSupply-chain Provenance & Signing

File quality

Per-file score 0–10 — a quality signature. Of 76 files carrying findings, judged against the Production bar: 1% slop · 50% mixed · 49% near-clean.

FileScoreBandWorst signal
REDACTED0.7SlopStatic Analysis (SAST): High: REDACTED
akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala5.0MixedChange Coupling: Boundary-crossing change coupling: AkkaHttpBackend.scala ↔ Http4sBackendBase.scala
akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala6.0MixedExplicit Debt: TodoComment
pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyFromPekko.scala6.0MixedExplicit Debt: TodoComment
core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala6.0MixedExplicit Debt: TodoComment
core/src/test/scala/sttp/client4/testing/streaming/StreamingTest.scala6.5MixedExplicit Debt: TodoComment
testing/server/src/main/scala/sttp/client4/testing/server/HttpServer.scala7.0MixedGod Classes: MethodTooLong: HttpServer.paramsToString
http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala7.0MixedCode Duplication: Near-duplicate member pair (65 shared lines)
core/src/main/scalajvm/sttp/client4/httpclient/HttpClientBackend.scala7.0MixedCode Duplication: Edited copy of a member (16 corresponding lines)
observability/opentelemetry-backend/src/main/scala/sttp/client4/opentelemetry/OpenTelemetryMetricsBackend.scala7.0MixedCode Duplication: Edited copy of a member (6 corresponding lines)
akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyToAkka.scala7.1MixedCode Duplication: Near-duplicate member pair (33 shared lines)
effects/zio/src/main/scala/sttp/client4/impl/zio/ZioWebSockets.scala7.2MixedCognitive Complexity: ZioWebSockets.compilePipe (cognitive 27)
observability/otel4s-metrics-backend/src/main/scala/sttp/client4/opentelemetry/otel4s/Otel4sMetricsBackend.scala7.2MixedCognitive Complexity: Otel4sMetricsBackend.metricsListener (cognitive 21)
effects/fs2-ce2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala7.2MixedCode Duplication: Near-duplicate member pair (39 shared lines)
effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/ZioBodyFromHttpClient.scala7.2MixedCode Duplication: Near-duplicate member pair (36 shared lines)
effects/fs2-ce2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala7.2MixedCode Duplication: Edited copy of a member (41 corresponding lines)
akka-http-backend/src/main/scala/sttp/client4/akkahttp/ToAkka.scala7.2MixedCode Duplication: Edited copy of a member (21 corresponding lines)
REDACTED7.2MixedStatic Analysis (SAST): High: REDACTED
core/src/main/scala/sttp/client4/monad/MapEffect.scala7.3MixedExplicit Debt: TodoComment
effects/zio/src/main/scala/sttp/client4/impl/zio/ExtendedEnvBackend.scala7.4MixedCode Duplication: Edited copy of a member (15 corresponding lines)

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 — 172

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 — 46

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

Could not be resolved — 9

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

This survey 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. All 51 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.

Every figure here is one of two 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. 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.

What we checked — 51 dimensions across the health lenses
D1D2D3D4D5D6D7D12D13D14D15D16D17D20D28D29D30D35D36D43D44AX10AX2AX3AX4AX6AX8GD1IC1M1M2M3P1P2P3P4P6PF3X1X12X16X18X21X23X24X25X26X27X3X4X5

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
  1. 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, 194 of 229 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.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1d8fd-7e94-750b-a60f-43c39e6adb1a.

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 — We 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.
  • D11 Test Reliability — not measured this run — We 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.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we 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 a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its sbt dependencies. Nothing was read about its Python 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 — We 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: it declares a published package (project/plugins.sbt), but 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.
  • D24 Comment Value — not measured this run — We 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's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • D26 Project Cohesion — not measured this run — We 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. `(repository root)` (23042 LoC, 574 module-visible types across 107 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
  • D27 Navigability — not measured this run — We 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We 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. `effects/ox/src/main/scala/sttp/client4/impl/ox/ws/OxWebSockets.scala` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • D34 Knowledge Freshness — not measured this run — We 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: 84 commits in the last 90 days, yet 105 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.
  • C1 Data Protection — not measured this run — We 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 — We 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.

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

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do 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.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • 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.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • 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.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • 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.
  • 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.

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/scalanative/sttp/client4/SttpClientExceptionExtensions.scala (SttpClientExceptionExtensions.defaultExceptionToSttpClientException at 19), core/src/main/scala/sttp/client4/internal/BodyFromResponseAs.scala (BodyFromResponseAs.doApply 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

  1. Bring the 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with AbstractBackendStub.adjustResponseBody (cyclomatic 29), BodyFromAkka.webSocketAndFlow (cyclomatic 16), Slf4jLogger.apply (cyclomatic 16). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 9.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

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

  1. Bring the 8 bodies over 15 down to 15 or less in Cognitive Complexity — start with BodyFromAkka.webSocketAndFlow (cognitive 31), BodyFromPekko.webSocketAndFlow (cognitive 31), ZioWebSockets.compilePipe (cognitive 27). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 8 together lifts Cognitive Complexity from 8.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

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

  1. 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).
  2. Resolve the 1 MethodTooLong finding(s) in God Classes — start with HttpServer.scala. — One of this dimension's main actionable groups (1 warning-level).

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

D4 · Code Duplication5.4 / 10Adequate✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

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

68 duplicated block group(s) detected. 11.4 % of the production lines (2,635 of 23,042) are in a reported copy. A further 67 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 1 of the 135 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.

Duplicated block (7 lines × 2) · ×8akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyToAkka.scala:28
Duplicated block (6 lines × 2) · ×7core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:171
Edited copy of a member (4 corresponding lines) · ×6effects/zio/src/main/scalajvm/sttp/client4/impl/zio/zioDecompressors.scala:18
Edited copies of one member (3 members, 3+ corresponding lines) · ×6armeria-backend/src/main/scala/sttp/client4/armeria/future/ArmeriaFutureBackend.scala:37
Duplicated block (10 lines × 2) · ×6akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala:155

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

What to do

  1. Resolve the 8 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with Fs2BodyFromHttpClient.scala (2), BodyToAkka.scala, FetchZioBackend.scala. — One of this dimension's main actionable groups (8 warning-level).
  2. Resolve the 7 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with Http4sBackendBase.scala (3), AbstractCurlBackend.scala, FromAkka.scala. — One of this dimension's main actionable groups (7 warning-level).
  3. Resolve the 6 Edited copy of a member (4 corresponding lines) finding(s) in Code Duplication — start with ArmeriaZioBackend.scala (2), zioDecompressors.scala, ArmeriaFs2Backend.scala. — One of this dimension's main actionable groups (6 warning-level).

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

D5 · Coupling9.8 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

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

37 production modules (sbt), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 1 module(s) off the main sequence, with abstractness counted on 36 of the 37 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

Off the main sequence: core

What to do

  1. Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).

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

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 44 classes have LCOM4 above 3.

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

What to do

  1. 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).

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

D7 · Architectural Integrity6.0 / 10Adequate✓ 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 6.0 / 10 · rule-coverage 100% · ceiling Prevented

No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).

Detailed fixes: d7_recommendation.md.

D12 · Dependency Hygiene8.7 8.5 / 10Strong✓ Tool-verified

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

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

26 outdated direct sbt declarations. 69 of 71 direct declarations were graded against Maven Central (2 not published there, which is what a private Nexus or Artifactory artifact looks like, 0 declaring a version range rather than an exact version). An sbt declaration names an EXACT version, so the remedy is an edit to the build file — there is no lockfile refresh that would move it. Test-, Provided- and it-scoped declarations are excluded, because a consumer of this project never receives them. A version held in a Scala val is read only when the val is one string literal: sbt is a program rather than a manifest, and evaluating a computed version would invent the measurement rather than take it. Whether any artifact is DEPRECATED or ABANDONED is not graded and cannot be — Maven Central publishes no such marker, and release age does not stand in for one: the most widely depended-upon libraries are routinely the stalest, being finished rather than abandoned. Known CVEs in this dependency graph are D30's question.

Outdated: ch.megard:akka-http-cors_2.13 · ×26

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

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.

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 69 declared sbt dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the production coordinates this repository's 5 sbt build file(s) (REDACTED and project/*.scala) declare with a literal version, directly or through a string-literal val — `%%` resolved to the Scala binary suffix Central publishes under, test-scoped declarations excluded — the same declaration-site closure this analysis reads for dependency currency. sbt has no lockfile a checkout carries, so this is deliberately NOT the transitive closure. A further 2 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's sbt dependencies and nothing else. The repository also declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), 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.

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.

D16 · Bus Factor9.6 / 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.6 / 10 · rule-coverage 100% · ceiling Documented

6 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is REDACTED. Counted over 140 of the 325 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.

D17 · Explicit Debt9.9 / 10Stronggated by 11 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

11 deducted task-comment markers across 23042 LoC (0.0/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 · ×11pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyFromPekko.scala:45

What to do

  1. Resolve the 11 TodoComment finding(s) in Explicit Debt — start with StreamingTest.scala (5), MapEffect.scala (2), BodyFromPekko.scala. — One of this dimension's main actionable groups (11 warning-level).

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

D20 · ADR Quality6.0 / 10Adequate✓ Tool-verified

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

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

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

4 of 4 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.

ADR has no Consequences section · ×4docs/adr/0001-extract-stream-from-http4s.md:1detected by adr-integrity

What to do

  1. Resolve the 4 ADR has no Consequences section finding(s) in ADR Quality — start with 0001-extract-stream-from-http4s.md, 0002-http-model-conventions.md, 0003-separate-backend-types.md. — One of this dimension's main actionable groups (4 recommendation-level).

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

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.

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
REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. 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).
  2. 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).
  3. 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.

D30 · Dependency Vulnerabilities9.8 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via 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 (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), 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. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

1 finding(s): 0 critical, 0 high, 1 medium, 0 low.

REDACTED

What to do

  1. Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

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:1

What to do

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

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
REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
  3. 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.

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. Reported 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. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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.

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 Rust toolchain pin, 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.

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.

AX2 · Stateful singletons10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue in this repository's Scala: methods whose whole body is still `???` or a "not implemented" throw where nothing overrides them, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

IC1 · Incompleteness & stubs10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Scala: methods whose body is `???` or only throws a "not implemented" error, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. — okhttp-backend/src/test/scala/sttp/client4/okhttp/OkHttpSyncDigestAuthProxyManualTest.scala:11

What to do

  • Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
M1 · Documentation (README)7.3 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

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

M2 · Architecture documentation8.0 / 10Strong✓ 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.

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

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

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

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.

P2 · Observability9.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

What to do

  • Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
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 2 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. — REDACTED:3

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

PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X18 · Disposal-pattern correctness4.3 / 10Weak✓ Tool-verified

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

  • `Source.fromFile(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.mkString` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(Source.fromFile(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`. (×2) — finagle-backend/src/main/scala/sttp/client4/finagle/FinagleBackend.scala:94, finagle-backend/src/main/scala/sttp/client4/finagle/FinagleBackend.scala:127

What to do

  • Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for` comprehension or `foreach` leaves the mutable collection it is walking alone — an `ArrayBuffer` or `ListBuffer` counts its changes and its iterator checks the count, an `ArrayDeque` (and `mutable.Queue`/`mutable.Stack`) is walked by index up to its starting length, and a `java.util` collection walked through `asScala` is fail-fast, so a body that adds to or removes from the very collection the loop is walking makes a later step throw `ConcurrentModificationException` (`IndexOutOfBoundsException` for a deque) and the remaining elements are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

X3 · Exception handling10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

X4 · Structured logging2.0 / 10Critical✓ Tool-verified

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

  • `debug` at line 56 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — caching/src/main/scala/sttp/client4/caching/CachingBackend.scala:56
  • `warn` at line 59 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — caching/src/main/scala/sttp/client4/caching/CachingBackend.scala:59
  • `debug` at line 65 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — caching/src/main/scala/sttp/client4/caching/CachingBackend.scala:65
  • `debug` at line 82 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — caching/src/main/scala/sttp/client4/caching/CachingBackend.scala:82

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types2.0 / 10Critical✓ Tool-verified

Other · Code Health — Whether Scala's null is held to the type system and not undermined by assertions — a file compiled with `-Yexplicit-nulls` is one where `String` excludes null and `String | Null` admits it, a file under WartRemover's `Null` wart or Scalafix's `DisableSyntax.noNulls` is one whose code cannot write `null` and must say `Option`, and each `.nn`, `import scala.language.unsafeNulls` or null-lint suppression is the author overruling that.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • No build over this repository's 314 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.

What to do

  • On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.

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.

LensScoreRatingImpact
Code Health56%Adequate — gated by X4, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture96%ExemplarySolid.
Maturity84%StrongSolid.
Readiness57%Adequate — gated by P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security72%Adequate — gated by D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100%ExemplaryStrongest area.
Unscored — 1 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 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.

  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 62 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.
  • AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Scala imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • 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
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
  • 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.
  • C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
  • C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
  • D10 Test Quality — ~10601 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
  • 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.
  • D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
  • D21 Naming Consistency — N/A — too few peers to establish a naming convention (5654 declarations, no unit with a dominant convention).
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. 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 — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
  • D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • 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) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • 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.
  • 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.
  • D8 Code Coverage — Coverage not included — suite not readable by the collector
  • 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): 63 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • M4 Documentation accuracy — Not applicable: the 55 current-state document(s) make no claim of a kind M4 checks.
  • 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'.
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • S1 Web-Security Posture — No web surface: 315 Scala file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository builds on an HTTP-server library (akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpClient.scala:7 — `akka.http.scaladsl.server`) but serves no HTTP of its own: its production source starts no server (no `newServerAt`/`bindAndHandle`, server builder, `Server.serve`, `Http.serve`, tapir server interpreter or Netty HTTP pipeline), declares no application one runs (no Play application, servlet, cask `MainRoutes`, `HttpApp` or twitter-server), so it is a library whose server controls belong to the application that serves it — HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library. If this codebase starts serving HTTP, the dimension reactivates automatically.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — no C# was loaded; this repository's Scala and Java were read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter; a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
  • X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • 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:1 — `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 — 172 finding(s)
D17 · Explicit Debt · TodoComment · ×11
  • 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 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 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/scala/sttp/client4/testing/streaming/StreamingTest.scala:139 — // 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:155 — // 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:176 — // 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:192 — // 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:225 — // // 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/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:526 — // 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/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
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×8
  • 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 — before extracting anything, compare `akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyToAkka.scala` and `pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyToPekko.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 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) 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) core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:166 — core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:166-172 | core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:261-267 — 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/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala:27 — effects/fs2-ce2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala:27-33 | effects/fs2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala:27-33 — 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 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/fs2-ce2/src/main/scalajvm/sttp/client4/httpclient/fs2/Fs2BodyFromHttpClient.scala:27` 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) 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 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.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×7
  • Duplicated block (6 lines × 2) core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:171 — core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:171-176 | core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:214-219 — 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:171` 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:239 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:239-244 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:238-243 — 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 166 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:239` 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) akka-http-backend/src/main/scala/sttp/client4/akkahttp/FromAkka.scala:12 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/FromAkka.scala:12-17 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/FromPekko.scala:13-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. 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 (6 lines × 2) json/zio-json/src/main/scalajvm/sttp/client4/ziojson/SttpZioJsonApiExtensions.scala:20 — json/zio-json/src/main/scalajvm/sttp/client4/ziojson/SttpZioJsonApiExtensions.scala:20-25 | json/zio1-json/src/main/scalajvm/sttp/client4/ziojson/SttpZioJsonApiExtensions.scala:22-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: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 (6 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:151 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:151-156 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:151-156 — 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 166 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) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:287 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:287-292 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:286-291 — 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 166 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 · Edited copy of a member (4 corresponding lines) · ×6
  • Edited copy of a member (4 corresponding lines) effects/zio/src/main/scalajvm/sttp/client4/impl/zio/zioDecompressors.scala:18 — effects/zio/src/main/scalajvm/sttp/client4/impl/zio/zioDecompressors.scala:18-21 | effects/zio1/src/main/scalajvm/sttp/client4/httpclient/zio/zioDecompressors.scala:18-21 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) armeria-backend/fs2-ce2/src/main/scala/sttp/client4/armeria/fs2/ArmeriaFs2Backend.scala:41 — armeria-backend/fs2-ce2/src/main/scala/sttp/client4/armeria/fs2/ArmeriaFs2Backend.scala:41-44 | effects/fs2-ce2/src/main/scalajvm/sttp/client4/httpclient/fs2/HttpClientFs2Backend.scala:113-116 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) armeria-backend/zio/src/main/scala/sttp/client4/armeria/zio/ArmeriaZioBackend.scala:46 — armeria-backend/zio/src/main/scala/sttp/client4/armeria/zio/ArmeriaZioBackend.scala:46-49 | effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/HttpClientZioBackend.scala:83-86 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) armeria-backend/zio1/src/main/scala/sttp/client4/armeria/zio/ArmeriaZioBackend.scala:41 — armeria-backend/zio1/src/main/scala/sttp/client4/armeria/zio/ArmeriaZioBackend.scala:41-44 | effects/zio1/src/main/scalajvm/sttp/client4/httpclient/zio/HttpClientZioBackend.scala:78-81 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/ToAkka.scala:12 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/ToAkka.scala:12-15 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/ToPekko.scala:13-16 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) effects/fs2/src/main/scalajvm/sttp/client4/httpclient/fs2/HttpClientFs2Backend.scala:127 — effects/fs2/src/main/scalajvm/sttp/client4/httpclient/fs2/HttpClientFs2Backend.scala:127-130 | http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:303-306 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) · ×6
  • Edited copies of one member (3 members, 3+ corresponding lines) armeria-backend/src/main/scala/sttp/client4/armeria/future/ArmeriaFutureBackend.scala:37 — armeria-backend/src/main/scala/sttp/client4/armeria/future/ArmeriaFutureBackend.scala:37-39 | core/src/main/scalajvm/sttp/client4/httpclient/HttpClientFutureBackend.scala:90-92 | okhttp-backend/src/main/scala/sttp/client4/okhttp/OkHttpFutureBackend.scala:47-49 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 3+ corresponding lines) armeria-backend/fs2/src/main/scala/sttp/client4/armeria/fs2/ArmeriaFs2Backend.scala:84 — armeria-backend/fs2/src/main/scala/sttp/client4/armeria/fs2/ArmeriaFs2Backend.scala:84-86 | effects/cats/src/main/scalajvm/sttp/client4/httpclient/cats/HttpClientCatsBackend.scala:152-160 | effects/fs2/src/main/scalajvm/sttp/client4/httpclient/fs2/HttpClientFs2Backend.scala:181-188 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 3+ corresponding lines) armeria-backend/monix/src/main/scala/sttp/client4/armeria/monix/ArmeriaMonixBackend.scala:39 — armeria-backend/monix/src/main/scala/sttp/client4/armeria/monix/ArmeriaMonixBackend.scala:39-41 | effects/monix/src/main/scalajvm/sttp/client4/httpclient/monix/HttpClientMonixBackend.scala:94-96 | okhttp-backend/monix/src/main/scala/sttp/client4/okhttp/monix/OkHttpMonixBackend.scala:106-108 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 3+ corresponding lines) effects/cats-ce2/src/main/scalajs/sttp/client4/impl/cats/FetchCatsBackend.scala:36 — effects/cats-ce2/src/main/scalajs/sttp/client4/impl/cats/FetchCatsBackend.scala:36-38 | effects/cats/src/main/scalajs/sttp/client4/impl/cats/FetchCatsBackend.scala:36-38 | effects/fs2/src/main/scalajs/sttp.client4.impl.fs2/FetchFs2Backend.scala:100-104 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 3+ corresponding lines) effects/monix/src/main/scalajs/sttp/client4/impl/monix/FetchMonixBackend.scala:72 — effects/monix/src/main/scalajs/sttp/client4/impl/monix/FetchMonixBackend.scala:72-74 | effects/zio/src/main/scalajs/sttp/client4/impl/zio/FetchZioBackend.scala:74-76 | effects/zio1/src/main/scalajs/sttp/client4/impl/zio/FetchZioBackend.scala:79-81 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 3+ corresponding lines) examples-ce2/src/main/scala/sttp/client4/examples/WebSocketMonix.scala:17 — examples-ce2/src/main/scala/sttp/client4/examples/WebSocketMonix.scala:17-21 | examples/src/main/scala/sttp/client4/examples/testing/WebSocketTesting.scala:21-25 | examples/src/main/scala/sttp/client4/examples/ws/WebSocketZio.scala:16-18 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×6
  • 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:84 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:84-93 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:86-95 — 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 166 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:84` 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/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-34 | effects/fs2/src/main/scala/sttp/client4/impl/fs2/fs2Decompressors.scala:22-31 — 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 (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 · Edited copy of a member (16 corresponding lines) · ×5
  • Edited copy of a member (16 corresponding lines) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:161 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:161-176 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:160-175 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) effects/fs2-ce2/src/main/scalajvm/sttp/client4/httpclient/fs2/HttpClientFs2Backend.scala:123 — effects/fs2-ce2/src/main/scalajvm/sttp/client4/httpclient/fs2/HttpClientFs2Backend.scala:123-138 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:294-309 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) core/src/main/scalajs/sttp/client4/WebSocketImpl.scala:20 — core/src/main/scalajs/sttp/client4/WebSocketImpl.scala:20-36 | core/src/main/scalajvm/sttp/client4/internal/httpclient/WebSocketImpl.scala:25-40 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) core/src/main/scalajvm/sttp/client4/httpclient/HttpClientBackend.scala:205 — core/src/main/scalajvm/sttp/client4/httpclient/HttpClientBackend.scala:205-221 | okhttp-backend/src/main/scala/sttp/client4/okhttp/OkHttpBackend.scala:149-164 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala:241 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala:241-256 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/PekkoHttpBackend.scala:259-274 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×5
  • 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:137 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:137-148 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:137-148 — 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 166 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) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:197 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:197-208 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:196-207 — 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 166 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 (12 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-49 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyToPekko.scala:39-50 — before extracting anything, compare `akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyToAkka.scala` and `pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyToPekko.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 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/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. 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 (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.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×4
  • Edited copy of a member (9 corresponding lines) json/zio-json/src/main/scalajvm/sttp/client4/ziojson/SttpZioJsonApiExtensions.scala:17 — json/zio-json/src/main/scalajvm/sttp/client4/ziojson/SttpZioJsonApiExtensions.scala:17-25 | json/zio1-json/src/main/scalajvm/sttp/client4/ziojson/SttpZioJsonApiExtensions.scala:19-27 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) 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-32 | armeria-backend/fs2/src/main/scala/sttp/client4/armeria/fs2/ArmeriaFs2Backend.scala:27-37 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) armeria-backend/zio/src/main/scala/sttp/client4/armeria/zio/ArmeriaZioBackend.scala:27 — armeria-backend/zio/src/main/scala/sttp/client4/armeria/zio/ArmeriaZioBackend.scala:27-35 | armeria-backend/zio1/src/main/scala/sttp/client4/armeria/zio/ArmeriaZioBackend.scala:28-36 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/HttpClientZioBackend.scala:191 — effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/HttpClientZioBackend.scala:191-199 | effects/zio1/src/main/scalajvm/sttp/client4/httpclient/zio/HttpClientZioBackend.scala:189-197 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×4
  • Edited copy of a member (7 corresponding lines) core/src/main/scalajvm/sttp/client4/internal/httpclient/BodyFromHttpClient.scala:25 — core/src/main/scalajvm/sttp/client4/internal/httpclient/BodyFromHttpClient.scala:25-31 | okhttp-backend/src/main/scala/sttp/client4/okhttp/BodyFromOkHttp.scala:22-28 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/FromAkka.scala:11 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/FromAkka.scala:11-17 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/FromPekko.scala:12-18 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala:183 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala:183-189 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/PekkoHttpBackend.scala:201-207 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala:171 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala:171-177 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/PekkoHttpBackend.scala:189-195 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×4
  • Edited copy of a member (5 corresponding lines) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:221 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:221-225 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:213-217 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) effects/zio/src/main/scalajs/sttp/client4/impl/zio/FetchZioBackend.scala:35 — effects/zio/src/main/scalajs/sttp/client4/impl/zio/FetchZioBackend.scala:35-39 | effects/zio1/src/main/scalajs/sttp/client4/impl/zio/FetchZioBackend.scala:40-44 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) effects/cats-ce2/src/main/scalajs/sttp/client4/impl/cats/FetchCatsBackend.scala:22 — effects/cats-ce2/src/main/scalajs/sttp/client4/impl/cats/FetchCatsBackend.scala:22-26 | effects/cats/src/main/scalajs/sttp/client4/impl/cats/FetchCatsBackend.scala:22-26 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) armeria-backend/zio/src/main/scala/sttp/client4/armeria/zio/ArmeriaZioBackend.scala:70 — armeria-backend/zio/src/main/scala/sttp/client4/armeria/zio/ArmeriaZioBackend.scala:70-74 | armeria-backend/zio1/src/main/scala/sttp/client4/armeria/zio/ArmeriaZioBackend.scala:65-69 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×4
  • 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) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:266 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:266-281 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:265-280 — 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 166 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:266` 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 (9 lines × 2) · ×4
  • 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) 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:12-20 — before extracting anything, compare `core/src/main/scalajvm/sttp/client4/SttpClientExceptionExtensions.scala` and `core/src/main/scalanative/sttp/client4/SttpClientExceptionExtensions.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. 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:21` 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 (5 lines × 2) · ×4
  • 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/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) 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:168-172 — 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:232 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:232-236 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:231-235 — 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 166 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:232` 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 · Edited copy of a member (15 corresponding lines) · ×3
  • Edited copy of a member (15 corresponding lines) effects/zio/src/main/scala/sttp/client4/impl/zio/ExtendedEnvBackend.scala:14 — effects/zio/src/main/scala/sttp/client4/impl/zio/ExtendedEnvBackend.scala:14-28 | effects/zio1/src/main/scala/sttp/client4/impl/zio/ExtendedEnvBackend.scala:14-28 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) core/src/main/scalajvm/sttp/client4/compression/defaultCompressors.scala:16 — core/src/main/scalajvm/sttp/client4/compression/defaultCompressors.scala:16-30 | core/src/main/scalajvm/sttp/client4/compression/defaultCompressors.scala:45-59 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) core/src/main/scala/sttp/client4/internal/package.scala:19 — core/src/main/scala/sttp/client4/internal/package.scala:19-33 | testing/server/src/main/scala/sttp/client4/testing/server/HttpServer.scala:622-636 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×3
  • Edited copy of a member (12 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/FromAkka.scala:20 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/FromAkka.scala:20-31 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/FromPekko.scala:21-33 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) 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-36 | effects/fs2/src/main/scala/sttp/client4/impl/fs2/fs2Decompressors.scala:22-33 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) core/src/main/scala/sttp/client4/testing/package.scala:12 — core/src/main/scala/sttp/client4/testing/package.scala:12-23 | core/src/main/scala/sttp/client4/testing/package.scala:29-40 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×3
  • Edited copy of a member (10 corresponding lines) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:227 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:227-236 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:226-235 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) observability/prometheus-backend/src/main/scala/sttp/client4/prometheus/PrometheusBackend.scala:89 — observability/prometheus-backend/src/main/scala/sttp/client4/prometheus/PrometheusBackend.scala:89-98 | observability/prometheus-backend/src/main/scala/sttp/client4/prometheus/PrometheusBackend.scala:107-116 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/HttpClientZioBackend.scala:156 — effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/HttpClientZioBackend.scala:156-165 | effects/zio1/src/main/scalajvm/sttp/client4/httpclient/zio/HttpClientZioBackend.scala:154-163 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×3
  • Edited copy of a member (6 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaCompressor.scala:16 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaCompressor.scala:16-21 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/PekkoCompressor.scala:16-21 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) observability/opentelemetry-backend/src/main/scala/sttp/client4/opentelemetry/OpenTelemetryMetricsBackend.scala:188 — observability/opentelemetry-backend/src/main/scala/sttp/client4/opentelemetry/OpenTelemetryMetricsBackend.scala:188-193 | observability/prometheus-backend/src/main/scala/sttp/client4/prometheus/PrometheusBackend.scala:282-287 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) observability/otel4s-metrics-backend/src/main/scala/sttp/client4/opentelemetry/otel4s/Otel4sMetricsBackend.scala:218 — observability/otel4s-metrics-backend/src/main/scala/sttp/client4/opentelemetry/otel4s/Otel4sMetricsBackend.scala:218-223 | observability/otel4s-tracing-backend/src/main/scala/sttp/client4/opentelemetry/otel4s/Otel4sTracingDefaults.scala:94-99 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×3
  • 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:98 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:98-114 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:99-115 — 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 166 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 (17 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-44 | effects/fs2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala:27-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 3 separate duplicated blocks between them, totalling at least 52 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.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×3
  • 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 3 separate duplicated blocks between them, totalling at least 52 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:182 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:182-194 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:181-193 — 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 166 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:249 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:249-261 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:248-260 — 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 166 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:249` 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.
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 (REDACTED) 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 (REDACTED) 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 · Edited copy of a member (21 corresponding lines) · ×2
  • Edited copy of a member (21 corresponding lines) core/src/main/scalajvm/sttp/client4/SttpClientExceptionExtensions.scala:13 — core/src/main/scalajvm/sttp/client4/SttpClientExceptionExtensions.scala:13-34 | core/src/main/scalanative/sttp/client4/SttpClientExceptionExtensions.scala:12-32 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/ToAkka.scala:17 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/ToAkka.scala:17-37 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/ToPekko.scala:18-38 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×2
  • Edited copy of a member (13 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyToAkka.scala:87 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyToAkka.scala:87-99 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyToPekko.scala:88-100 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) effects/zio/src/main/scala/sttp/client4/impl/zio/ZioWebSockets.scala:58 — effects/zio/src/main/scala/sttp/client4/impl/zio/ZioWebSockets.scala:58-70 | effects/zio1/src/main/scala/sttp/client4/impl/zio/ZioWebSockets.scala:58-72 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×2
  • Edited copy of a member (11 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala:53 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala:53-63 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/PekkoHttpBackend.scala:69-79 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) effects/cats/src/main/scalajvm/sttp/client4/httpclient/cats/HttpClientCatsBackend.scala:123 — effects/cats/src/main/scalajvm/sttp/client4/httpclient/cats/HttpClientCatsBackend.scala:123-133 | effects/fs2/src/main/scalajvm/sttp/client4/httpclient/fs2/HttpClientFs2Backend.scala:150-160 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 4+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 4+ corresponding lines) armeria-backend/cats/src/main/scala/sttp/client4/armeria/cats/ArmeriaCatsBackend.scala:36 — armeria-backend/cats/src/main/scala/sttp/client4/armeria/cats/ArmeriaCatsBackend.scala:36-39 | armeria-backend/fs2/src/main/scala/sttp/client4/armeria/fs2/ArmeriaFs2Backend.scala:55-58 | effects/cats/src/main/scalajvm/sttp/client4/httpclient/cats/HttpClientCatsBackend.scala:88-91 | effects/fs2/src/main/scalajvm/sttp/client4/httpclient/fs2/HttpClientFs2Backend.scala:111-114 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 4+ corresponding lines) core/src/main/scala/sttp/client4/SttpWebSocketStreamApi.scala:70 — core/src/main/scala/sttp/client4/SttpWebSocketStreamApi.scala:70-73 | core/src/main/scalajs/sttp/client4/SttpExtensions.scala:31-36 | core/src/main/scalajvm/sttp/client4/SttpExtensions.scala:75-80 | core/src/main/scalanative/sttp/client4/SttpExtensions.scala:52-57 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
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 (14 lines × 2) · ×2
  • 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.
  • Duplicated block (14 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-73 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyToPekko.scala:61-74 — before extracting anything, compare `akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyToAkka.scala` and `pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyToPekko.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 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/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. 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.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×2
  • 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.
  • Duplicated block (8 lines × 2) core/src/main/scalajvm/sttp/client4/compression/defaultCompressors.scala:16 — core/src/main/scalajvm/sttp/client4/compression/defaultCompressors.scala:16-23 | core/src/main/scalajvm/sttp/client4/compression/defaultCompressors.scala:45-52 — 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.
X18 · Disposal-pattern correctness · Disposable created and abandoned in the function that made it · ×2
  • Disposable created and abandoned in the function that made it finagle-backend/src/main/scala/sttp/client4/finagle/FinagleBackend.scala:94 — `Source.fromFile(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.mkString` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(Source.fromFile(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`.
  • Disposable created and abandoned in the function that made it finagle-backend/src/main/scala/sttp/client4/finagle/FinagleBackend.scala:127 — `Source.fromFile(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.mkString` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(Source.fromFile(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`.
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.
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 327 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 227 over it, 3.27× 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.
D30 · Dependency Vulnerabilities · Medium CVE · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member pair (65 shared lines) · ×1
  • Near-duplicate member pair (65 shared lines) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:42 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:42-134 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:43-134 — These two members are variants of one another: 65 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 (39 shared lines) · ×1
  • Near-duplicate member pair (39 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: 39 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 (35 shared lines) · ×1
  • Near-duplicate member pair (35 shared lines) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:239 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:239-281 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:238-280 — These two members are variants of one another: 35 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 (33 shared lines) · ×1
  • Near-duplicate member pair (33 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: 33 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 · Edited copy of a member (68 corresponding lines) · ×1
  • Edited copy of a member (68 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala:130 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala:130-197 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyFromPekko.scala:131-198 — These two members are one piece of code written twice and then edited apart: 68 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (41 corresponding lines) · ×1
  • Edited copy of a member (41 corresponding 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 one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (37 corresponding lines) · ×1
  • Edited copy of a member (37 corresponding lines) effects/zio/src/main/scala/sttp/client4/impl/zio/ZioWebSockets.scala:12 — effects/zio/src/main/scala/sttp/client4/impl/zio/ZioWebSockets.scala:12-48 | effects/zio1/src/main/scala/sttp/client4/impl/zio/ZioWebSockets.scala:12-48 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (33 corresponding lines) · ×1
  • Edited copy of a member (33 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala:93 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/BodyFromAkka.scala:93-125 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/BodyFromPekko.scala:94-126 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (26 corresponding lines) · ×1
  • Edited copy of a member (26 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala:65 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala:65-90 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/PekkoHttpBackend.scala:81-108 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (27 corresponding lines) · ×1
  • Edited copy of a member (27 corresponding lines) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala:126 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpBackend.scala:126-152 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/PekkoHttpBackend.scala:144-170 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 16+ corresponding lines) effects/monix/src/main/scalajs/sttp/client4/impl/monix/FetchMonixBackend.scala:48 — effects/monix/src/main/scalajs/sttp/client4/impl/monix/FetchMonixBackend.scala:48-64 | effects/zio/src/main/scalajs/sttp/client4/impl/zio/FetchZioBackend.scala:51-66 | effects/zio1/src/main/scalajs/sttp/client4/impl/zio/FetchZioBackend.scala:56-71 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×1
  • Edited copy of a member (8 corresponding lines) effects/zio1/src/main/scala/sttp/client4/impl/zio/SttpClientStubbingBase.scala:95 — effects/zio1/src/main/scala/sttp/client4/impl/zio/SttpClientStubbingBase.scala:95-102 | effects/zio1/src/main/scala/sttp/client4/impl/zio/SttpClientStubbingBase.scala:112-121 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 7+ corresponding lines) json/circe/src/main/scala/sttp/client4/circe/SttpCirceApi.scala:53 — json/circe/src/main/scala/sttp/client4/circe/SttpCirceApi.scala:53-59 | json/json4s/src/main/scala/sttp/client4/json4s/SttpJson4sApi.scala:62-70 | json/spray-json/src/main/scala/sttp/client4/sprayJson/SttpSprayJsonApi.scala:47-55 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 1+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 1+ corresponding lines) armeria-backend/cats-ce2/src/main/scala/sttp/client4/armeria/cats/ArmeriaCatsBackend.scala:55 — armeria-backend/cats-ce2/src/main/scala/sttp/client4/armeria/cats/ArmeriaCatsBackend.scala:55-55 | armeria-backend/cats/src/main/scala/sttp/client4/armeria/cats/ArmeriaCatsBackend.scala:54-54 | armeria-backend/fs2-ce2/src/main/scala/sttp/client4/armeria/fs2/ArmeriaFs2Backend.scala:61-61 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (1 corresponding lines) · ×1
  • Edited copy of a member (1 corresponding lines) core/src/main/scala/sttp/client4/SttpApi.scala:357 — core/src/main/scala/sttp/client4/SttpApi.scala:357-357 | core/src/main/scala/sttp/client4/SttpWebSocketStreamApi.scala:59-61 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (3 corresponding lines) · ×1
  • Edited copy of a member (3 corresponding lines) effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/HttpClientZioBackend.scala:182 — effects/zio/src/main/scalajvm/sttp/client4/httpclient/zio/HttpClientZioBackend.scala:182-184 | effects/zio1/src/main/scalajvm/sttp/client4/httpclient/zio/HttpClientZioBackend.scala:180-182 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (40 lines × 2) · ×1
  • 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.
D4 · Code Duplication · Duplicated block (38–39 lines × 2) · ×1
  • Duplicated block (38–39 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:42 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:42-79 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:43-81 — 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 166 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 (27 lines × 2) · ×1
  • Duplicated block (27 lines × 2) akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpClient.scala:37 — akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpClient.scala:37-63 | pekko-http-backend/src/main/scala/sttp/client4/pekkohttp/PekkoHttpClient.scala:38-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. Read the line range as the matched WINDOW rather than a finished unit: at `akka-http-backend/src/main/scala/sttp/client4/akkahttp/AkkaHttpClient.scala:37` 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. 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 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/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 (22 lines × 2) · ×1
  • Duplicated block (22 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-68 | effects/fs2/src/main/scala/sttp/client4/impl/fs2/Fs2WebSockets.scala:46-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 3 separate duplicated blocks between them, totalling at least 52 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.
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 (12–13 lines × 2) · ×1
  • Duplicated block (12–13 lines × 2) core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:188 — core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:188-200 | core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:351-362 — 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:188` 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 (10–13 lines × 2) · ×1
  • Duplicated block (10–13 lines × 2) core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:414 — core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:414-426 | core/src/main/scalanative/sttp/client4/curl/AbstractCurlBackend.scala:702-711 — 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.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×1
  • Duplicated block (11 lines × 2) http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:161 — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:161-171 | http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala:160-170 — 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 166 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:161` 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 (7 lines × 4) · ×1
  • Duplicated block (7 lines × 4) 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 — 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.
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:28-32 — 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.
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.
D4 · Code Duplication · Duplicated block (44 lines × 2) · ×1
  • Duplicated block (44 lines × 2) http4s-backend/src/main/scalajvm/sttp/client4/http4s/Http4sBackend.scala:23 — http4s-backend/src/main/scalajvm/sttp/client4/http4s/Http4sBackend.scala:23-90 | http4s-backend/src/main/scalanative/sttp/client4/http4s/Http4sBackend.scala:23-66 — 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.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: core — core: abstractness 0.20, instability 0.00, distance 0.80 — zone of pain — concrete and depended on by 17 project(s), so it's rigid to change.
Minor — 20 finding(s)
D20 · ADR Quality · ADR has no Consequences section · ×4
  • ADR has no Consequences section docs/adr/0001-extract-stream-from-http4s.md:1 — docs/adr/0001-extract-stream-from-http4s.md has no Consequences section (a heading such as `## Consequences`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Consequences section docs/adr/0002-http-model-conventions.md:1 — docs/adr/0002-http-model-conventions.md has no Consequences section (a heading such as `## Consequences`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Consequences section docs/adr/0003-separate-backend-types.md:1 — docs/adr/0003-separate-backend-types.md has no Consequences section (a heading such as `## Consequences`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Consequences section docs/adr/0004-separate-request-types.md:1 — docs/adr/0004-separate-request-types.md has no Consequences section (a heading such as `## Consequences`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
X4 · Structured logging · Interpolated log message defeats structured logging · ×4
  • Interpolated log message defeats structured logging caching/src/main/scala/sttp/client4/caching/CachingBackend.scala:56 — `debug` at line 56 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
  • Interpolated log message defeats structured logging caching/src/main/scala/sttp/client4/caching/CachingBackend.scala:59 — `warn` at line 59 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
  • Interpolated log message defeats structured logging caching/src/main/scala/sttp/client4/caching/CachingBackend.scala:65 — `debug` at line 65 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
  • Interpolated log message defeats structured logging caching/src/main/scala/sttp/client4/caching/CachingBackend.scala:82 — `debug` at line 82 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
X10 · Duplicated predicate · Duplicated predicate · ×3
  • Duplicated predicate core/src/main/scalajs/sttp/client4/SttpClientExceptionExtensions.scala:21 — `e.getCause != null && e.getCause.isInstanceOf[Exception]` appears character-identically in 3 files — core/src/main/scalajs/sttp/client4/SttpClientExceptionExtensions.scala, core/src/main/scalajvm/sttp/client4/SttpClientExceptionExtensions.scala, core/src/main/scalanative/sttp/client4/SttpClientExceptionExtensions.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala:232 — `hr.status.equals(Status.NoContent) || isEmptyBody` appears character-identically in 2 files — http4s-backend/src/main/scala/sttp/client4/http4s/Http4sBackendBase.scala, http4s-ce2-backend/src/main/scala/sttp/client4/http4s/Http4sBackend.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate core/src/main/scalajvm/sttp/client4/httpclient/HttpClientAsyncBackend.scala:184 — `subprotocol != null && subprotocol.nonEmpty` appears character-identically in 2 files — core/src/main/scalajvm/sttp/client4/httpclient/HttpClientAsyncBackend.scala, core/src/main/scalajvm/sttp/client4/httpclient/HttpClientSyncBackend.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 5 significant file(s) lose their only recent owner: finagle-backend/src/main/scala/sttp/client4/finagle/FinagleBackend.scala, core/src/main/scalanative/sttp/client4/curl/internal/CurlCode.scala, effects/zio1/src/main/scala/sttp/client4/impl/zio/SttpClientStubbingBase.scala, core/src/main/scalanative/sttp/client4/curl/CurlMultiInputStream.scala, core/src/main/scala/sttp/client4/internal/package.scala. Pair on, review, or document these before any departure.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 1 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 (6 single-owned of 140 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 140 of the 325 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: REDACTED.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
IC1 · Incompleteness & stubs · Disabled test · ×1
  • Disabled test okhttp-backend/src/test/scala/sttp/client4/okhttp/OkHttpSyncDigestAuthProxyManualTest.scala:11 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:3 — 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 2 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.
X5 · Nullable reference types · Scala's null is not held to the type system everywhere · ×1
  • Scala's null is not held to the type system everywhere — No build over this repository's 314 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
Minor — 26 finding(s)
D12 · Dependency Hygiene · Outdated · ×26
  • Outdated: ch.megard:akka-http-cors_2.13 — `ch.megard %% akka-http-cors_2.13` is declared at 1.2.0 in REDACTED, but 1.3.1 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.2.0 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: ch.qos.logback:logback-classic — `ch.qos.logback %% logback-classic` is declared at 1.5.14 in REDACTED, but 1.6.6 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.5.14 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: co.fs2:fs2-core_2.13 — `co.fs2 %% fs2-core_2.13` is declared at 2.5.13 in REDACTED, but 3.14.0 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.5.13 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: co.fs2:fs2-io_2.13 — `co.fs2 %% fs2-io_2.13` is declared at 2.5.13 in REDACTED, but 3.14.0 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.5.13 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: co.fs2:fs2-reactive-streams_2.13 — `co.fs2 %% fs2-reactive-streams_2.13` is declared at 2.5.13 in REDACTED, but 3.14.0 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.5.13 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.lihaoyi:os-lib_2.13 — `com.lihaoyi %% os-lib_2.13` is declared at 0.11.4 in REDACTED, but 0.11.10 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 0.11.4 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.outr:scribe_2.13 — `com.outr %% scribe_2.13` is declared at 3.15.2 in REDACTED, but 3.19.1 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 3.15.2 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.typesafe.akka:akka-http_2.13 — `com.typesafe.akka %% akka-http_2.13` is declared at 10.2.10 in REDACTED, but 10.5.3 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 10.2.10 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.typesafe.akka:akka-stream_2.13 — `com.typesafe.akka %% akka-stream_2.13` is declared at 2.6.20 in REDACTED, but 2.8.8 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.6.20 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: dev.zio:zio-interop-reactivestreams_2.13 — `dev.zio %% zio-interop-reactivestreams_2.13` is declared at 1.3.12 in REDACTED, but 2.0.2 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.3.12 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: dev.zio:zio-json_2.13 — `dev.zio %% zio-json_2.13` is declared at 1.0.0 in REDACTED, but 1.1.2 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.0.0 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: dev.zio:zio-nio_2.13 — `dev.zio %% zio-nio_2.13` is declared at 1.0.0-RC12 in REDACTED, but 2.0.2 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.0.0-RC12 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: dev.zio:zio-streams_2.13 — `dev.zio %% zio-streams_2.13` is declared at 1.0.18 in REDACTED, but 2.1.27 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.0.18 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: dev.zio:zio_2.13 — `dev.zio %% zio_2.13` is declared at 1.0.18 in REDACTED, but 2.1.27 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.0.18 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: io.github.cquiroz:scala-java-time_2.13 — `io.github.cquiroz %% scala-java-time_2.13` is declared at 2.6.0 in REDACTED, but 2.10.0 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.6.0 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: io.monix:monix_2.13 — `io.monix %% monix_2.13` is declared at 3.4.1 in REDACTED, but 3.5.2 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 3.4.1 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: io.opentelemetry:opentelemetry-api — `io.opentelemetry %% opentelemetry-api` is declared at 1.67.0 in REDACTED, but 1.68.0 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.67.0 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: io.opentelemetry:opentelemetry-exporter-otlp — `io.opentelemetry %% opentelemetry-exporter-otlp` is declared at 1.67.0 in REDACTED, but 1.68.0 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.67.0 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: io.opentelemetry:opentelemetry-sdk-extension-autoconfigure — `io.opentelemetry %% opentelemetry-sdk-extension-autoconfigure` is declared at 1.67.0 in REDACTED, but 1.68.0 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.67.0 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: org.apache.pekko:pekko-http_2.13 — `org.apache.pekko %% pekko-http_2.13` is declared at 1.4.2 in REDACTED, but 2.0.0 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.4.2 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: org.apache.pekko:pekko-stream_2.13 — `org.apache.pekko %% pekko-stream_2.13` is declared at 1.7.1 in REDACTED, but 2.0.0 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.7.1 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: org.http4s:http4s-blaze-client_2.13 — `org.http4s %% http4s-blaze-client_2.13` is declared at 0.23.18 in REDACTED, but 1.0-4-a7fc4a9 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 0.23.18 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: org.http4s:http4s-client_2.13 — `org.http4s %% http4s-client_2.13` is declared at 0.22.15 in REDACTED, but 1.0-4-a7fc4a9 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 0.22.15 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: org.http4s:http4s-ember-client_2.13 — `org.http4s %% http4s-ember-client_2.13` is declared at 0.23.38 in REDACTED, but 1.0-4-a7fc4a9 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 0.23.38 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: org.slf4j:slf4j-api — `org.slf4j %% slf4j-api` is declared at 1.7.36 in REDACTED, but 2.0.20 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.7.36 until the declaration is edited — there is no lockfile refresh that would move it.
  • + 1 more in this group — see findings.md.

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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9d7102358498482ab2e82b2c6b441c94/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9d7102358498482ab2e82b2c6b441c94/tree.json --exit-code 0 --source .0artifacts/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/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude core/src/test/js .12artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-a1ea8d775f144f2d9dde6be5785e8b321artifacts/raw/osv-scanner.json
D31 · IaC & Container Securitytrivy—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. semgrep could not parse 1 file(s) — `effects/ox/src/main/scala/sttp/client4/impl/ox/ws/OxWebSockets.scala` — so the PII/GDPR sweep did not cover them at all.0—
D37 · Vulnerability-disclosure Policydisclosure—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 Confinementruntime-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 Confinementruntime-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 Enforcementruntime-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 Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-a1ea8d775f144f2d9dde6be5785e8b320artifacts/raw/osv-scanner.json

Run 01a1d8fd-7e94-750b-a60f-43c39e6adb1a · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md