Executive summary
zio/zio-http falls short of our standard for production, held back most by its Accessibility lens, the interface's usability with a keyboard or assistive technology. It scores 48 out of 100 and is rated Weak, and 141 of its 162 critical findings are security problems.
Accessibility, at 42, is the weakest lens, level with Security and Compliance, and counts most in the score. The best first step is restoring certificate checks, worth about 5 points. Fixing focus, motion and contrast would lift Accessibility itself, also worth about 5. Raising Accessibility to 70 would lift the score to about 53.
124 pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Seven secrets can leak from the build pipeline, and ten form fields can't be read by a screen reader. Pinning each tool to an exact version, limiting each secret to its own step and labelling the form fields would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the four passwords or keys in the code's history and the password or key in the code need replacing, with the old ones switched off. The six parts of the code nobody has worked on for a long time need someone to learn and document them before anyone changes them.
The product code is 70,957 lines, about €110,000 to rebuild.
If Accessibility rose from 42 to 70, the lowest score rated Strong, the score would rise from 48 to about 53.
New since the last survey: 43 findings
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-basic-auth/src/main/resources/basic-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-basic-auth/src/main/resources/basic-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-basic-auth/src/main/resources/basic-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-basic-auth/src/main/resources/basic-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-basic-auth/src/main/resources/basic-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-basic-auth/src/main/resources/basic-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-basic-auth/src/main/resources/basic-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-digest-auth/src/main/resources/digest-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-digest-auth/src/main/resources/digest-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-digest-auth/src/main/resources/digest-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-token-auth/src/main/resources/jwt-bearer-token-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-token-auth/src/main/resources/jwt-bearer-token-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-token-auth/src/main/resources/jwt-bearer-token-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-token-auth/src/main/resources/jwt-bearer-token-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-token-auth/src/main/resources/jwt-bearer-token-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-token-auth/src/main/resources/jwt-bearer-token-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-token-auth/src/main/resources/jwt-bearer-token-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-token-auth/src/main/resources/jwt-bearer-token-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-oauth-bearer-token-auth/src/main/resources/oauth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-oauth-bearer-token-auth/src/main/resources/oauth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-oauth-bearer-token-auth/src/main/resources/oauth-client.html
Fixed since the last survey: 9 findings
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-basic-auth/src/main/resources/basic-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-digest-auth/src/main/resources/digest-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-token-auth/src/main/resources/jwt-bearer-token-auth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-oauth-bearer-token-auth/src/main/resources/oauth-client.html
- Visual & motion safety · Animation without a prefers-reduced-motion guard zio-http-example-opaque-bearer-token-auth/src/main/resources/opaque-bearer-token-auth-client.html
Rebuild cost: about €110,000 · Estimate
| Cost to rebuild | €36,000 to €180,000, for 599 to 1,902 hours of work, about 0.7 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Standard, 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.7 at a score of 48. 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. |
| Size | Medium: 70,957 lines of product code |
| What it is not | Not 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. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 gen.smithy.Smithy.SimpleShapes | 2 Header.Vary | 3 URL | 4 endpoint.cli.HttpOptions | 5 gen.grpc.Protobuf | 6 gen.scala.Code.Collection | 7 gen.scala.Code.ScalaType | 8 codec.PathCodec | 9 gen.smithy | 10 gen.smithy.SmithyTrait | 11 ErrorResponseConfig.ErrorFormat | 12 internal | 13 codec.HttpCodec | 14 codec.internal | 15 codec | 16 endpoint | 17 endpoint.cli | 18 endpoint.cli.Retriever | 19 gen.scala.Code | 20 gen.scala.Code.CodecType | 21 endpoint.openapi.JsonSchema | 22 gen.openapi | 23 template | 24 template2.Dom | 25 template2 | 26 datastar.Attributes | 27 datastar.Attributes.OnIntervalModifier | 28 Cookie | 29 Header | 30 Header.AcceptLanguage | 31 Body | 32 ZClient | 33 datastar | 34 endpoint.openapi.OpenAPIGen | 35 Handler | 36 endpoint.openapi | 37 netty | 38 endpoint.openapi.OpenAPI | 39 zio.http | 40 codec.internal.EncoderDecoder |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 gen.smithy.Smithy.SimpleShapes | ||||||||||||||||||||||||||||||||||||||||
| 2 Header.Vary | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 3 URL | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 4 endpoint.cli.HttpOptions | 1 | 1 | 10 | 11 | 8 | |||||||||||||||||||||||||||||||||||
| 5 gen.grpc.Protobuf | 2 | 4 | ||||||||||||||||||||||||||||||||||||||
| 6 gen.scala.Code.Collection | 8 | 2 | ||||||||||||||||||||||||||||||||||||||
| 7 gen.scala.Code.ScalaType | 4 | |||||||||||||||||||||||||||||||||||||||
| 8 codec.PathCodec | 1 | 2 | 1 | 7 | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 9 gen.smithy | 5 | 1 | 1 | 4 | 1 | 1 | 1 | 13 | ||||||||||||||||||||||||||||||||
| 10 gen.smithy.SmithyTrait | 2 | 62 | 13 | |||||||||||||||||||||||||||||||||||||
| 11 ErrorResponseConfig.ErrorFormat | 3 | |||||||||||||||||||||||||||||||||||||||
| 12 internal | 4 | 4 | 7 | 2 | 2 | 4 | 1 | 2 | 2 | 1 | 29 | 5 | 5 | 6 | 3 | 12 | ||||||||||||||||||||||||
| 13 codec.HttpCodec | 3 | 1 | 1 | 1 | 1 | 17 | 1 | 11 | 5 | 2 | ||||||||||||||||||||||||||||||
| 14 codec.internal | 1 | 4 | 2 | 1 | 2 | 5 | 1 | 2 | 1 | 3 | ||||||||||||||||||||||||||||||
| 15 codec | 4 | 1 | 4 | 1 | 5 | 9 | 1 | 3 | 1 | 1 | 2 | 1 | 30 | 4 | 69 | 4 | 1 | 4 | ||||||||||||||||||||||
| 16 endpoint | 1 | 1 | 1 | 1 | 1 | 9 | 3 | 2 | 2 | 2 | 6 | |||||||||||||||||||||||||||||
| 17 endpoint.cli | 1 | 1 | 3 | 2 | 2 | 1 | 1 | 8 | 1 | 1 | 1 | |||||||||||||||||||||||||||||
| 18 endpoint.cli.Retriever | 1 | 2 | 3 | 2 | 3 | |||||||||||||||||||||||||||||||||||
| 19 gen.scala.Code | 10 | 1 | 6 | 1 | 17 | 1 | ||||||||||||||||||||||||||||||||||
| 20 gen.scala.Code.CodecType | 13 | |||||||||||||||||||||||||||||||||||||||
| 21 endpoint.openapi.JsonSchema | 1 | 2 | 1 | 2 | 1 | 1 | 14 | 30 | ||||||||||||||||||||||||||||||||
| 22 gen.openapi | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 23 template | 1 | 3 | 7 | |||||||||||||||||||||||||||||||||||||
| 24 template2.Dom | 1 | 1 | 1 | 12 | 5 | 13 | ||||||||||||||||||||||||||||||||||
| 25 template2 | 1 | 1 | 1 | 1 | 17 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 26 datastar.Attributes | 41 | 1 | 12 | 7 | ||||||||||||||||||||||||||||||||||||
| 27 datastar.Attributes.OnIntervalModifier | 5 | 4 | ||||||||||||||||||||||||||||||||||||||
| 28 Cookie | 1 | 4 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 29 Header | 2 | 2 | 78 | 3 | 1 | 3 | 5 | 38 | 2 | 2 | 1 | 1 | 2 | |||||||||||||||||||||||||||
| 30 Header.AcceptLanguage | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 31 Body | 10 | 9 | 2 | 1 | 23 | 9 | 2 | |||||||||||||||||||||||||||||||||
| 32 ZClient | 2 | 3 | 3 | 2 | 2 | 2 | 2 | 1 | 5 | 1 | 1 | 15 | ||||||||||||||||||||||||||||
| 33 datastar | 2 | 2 | 16 | 3 | 1 | 3 | 15 | 5 | 2 | 1 | 4 | |||||||||||||||||||||||||||||
| 34 endpoint.openapi.OpenAPIGen | 2 | 1 | 2 | 2 | 2 | 2 | 4 | 1 | 4 | 1 | 2 | 1 | ||||||||||||||||||||||||||||
| 35 Handler | 2 | 8 | 2 | 1 | 6 | 1 | 1 | 2 | 1 | 2 | 4 | 1 | 11 | |||||||||||||||||||||||||||
| 36 endpoint.openapi | 3 | 1 | 1 | 3 | 1 | 2 | 1 | 3 | 1 | 5 | 1 | 12 | 2 | 2 | 1 | 2 | 2 | 7 | 2 | |||||||||||||||||||||
| 37 netty | 1 | 3 | 1 | 7 | 1 | 16 | 3 | 1 | 3 | 3 | 1 | 7 | ||||||||||||||||||||||||||||
| 38 endpoint.openapi.OpenAPI | 2 | 3 | 12 | 2 | 1 | 14 | 28 | 2 | 2 | 1 | 5 | |||||||||||||||||||||||||||||
| 39 zio.http | 10 | 12 | 15 | 17 | 8 | 8 | 16 | 5 | 1 | 9 | 7 | 8 | 75 | 3 | 4 | 5 | 6 | 35 | 6 | 28 | 1 | 2 | 3 | 2 | 2 | 6 | ||||||||||||||
| 40 codec.internal.EncoderDecoder | 3 | 4 | 3 | 1 | 1 | 4 | 5 | 3 | 1 | 2 | 6 |
2→20 Header.Vary uses gen.scala.Code.CodecType part of a loop✕
- Connections
- 1 pair of types, where a type in Header.Vary uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.Header.Vary.Headers→zio.http.gen.scala.Code.CodecType.String
- Direction
- Header.Vary uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break Header.Vary, while a change to Header.Vary can't break gen.scala.Code.CodecType.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
2→29 Header.Vary uses Header part of a loop✕
- Connections
- 2 pairs of types, where a type in Header.Vary uses a type in Header.
- The types involved
zio.http.Header.Vary.Headers→zio.http.Header.Varyzio.http.Header.Vary.Star→zio.http.Header.Vary
- Direction
- Header.Vary uses Header, so a change to Header can break Header.Vary, while a change to Header.Vary can't break Header.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→20 URL uses gen.scala.Code.CodecType part of a loop✕
- Connections
- 3 pairs of types, where a type in URL uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.URL.Err→zio.http.gen.scala.Code.CodecType.Stringzio.http.URL.Fragment→zio.http.gen.scala.Code.CodecType.Stringzio.http.URL.Location→zio.http.gen.scala.Code.CodecType.Boolean
- Direction
- URL uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break URL, while a change to URL can't break gen.scala.Code.CodecType.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→29 URL uses Header part of a loop✕
- Connections
- 1 pair of types, where a type in URL uses a type in Header.
- The types involved
zio.http.URL.Location→zio.http.Header.Location
- Direction
- URL uses Header, so a change to Header can break URL, while a change to URL can't break Header.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→10 endpoint.cli.HttpOptions uses gen.smithy.SmithyTrait part of a loop✕
- Connections
- 1 pair of types, where a type in endpoint.cli.HttpOptions uses a type in gen.smithy.SmithyTrait.
- The types involved
zio.http.endpoint.cli.HttpOptions.Body→zio.http.gen.smithy.SmithyTrait.MediaType
- Direction
- endpoint.cli.HttpOptions uses gen.smithy.SmithyTrait, so a change to gen.smithy.SmithyTrait can break endpoint.cli.HttpOptions, while a change to endpoint.cli.HttpOptions can't break gen.smithy.SmithyTrait.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→11 endpoint.cli.HttpOptions uses ErrorResponseConfig.ErrorFormat part of a loop✕
- Connections
- 1 pair of types, where a type in endpoint.cli.HttpOptions uses a type in ErrorResponseConfig.ErrorFormat.
- The types involved
zio.http.endpoint.cli.HttpOptions.Body→zio.http.ErrorResponseConfig.ErrorFormat.Json
- Direction
- endpoint.cli.HttpOptions uses ErrorResponseConfig.ErrorFormat, so a change to ErrorResponseConfig.ErrorFormat can break endpoint.cli.HttpOptions, while a change to endpoint.cli.HttpOptions can't break ErrorResponseConfig.ErrorFormat.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→15 endpoint.cli.HttpOptions uses codec part of a loop✕
- Connections
- 10 pairs of types, where a type in endpoint.cli.HttpOptions uses a type in codec.
- The types involved
zio.http.endpoint.cli.HttpOptions.Body→zio.http.codec.Doczio.http.endpoint.cli.HttpOptions.Header→zio.http.codec.Doczio.http.endpoint.cli.HttpOptions.Header→zio.http.codec.TextCodeczio.http.endpoint.cli.HttpOptions.HeaderConstant→zio.http.codec.Doczio.http.endpoint.cli.HttpOptions.HeaderOptions→zio.http.codec.Doczio.http.endpoint.cli.HttpOptions.Path→zio.http.codec.Doczio.http.endpoint.cli.HttpOptions.Path→zio.http.codec.PathCodeczio.http.endpoint.cli.HttpOptions.Query→zio.http.codec.Doczio.http.endpoint.cli.HttpOptions.QueryConstant→zio.http.codec.Doczio.http.endpoint.cli.HttpOptions.URLOptions→zio.http.codec.Doc
- Direction
- endpoint.cli.HttpOptions uses codec, so a change to codec can break endpoint.cli.HttpOptions, while a change to endpoint.cli.HttpOptions can't break codec.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→17 endpoint.cli.HttpOptions uses endpoint.cli part of a loop✕
- Connections
- 11 pairs of types, where a type in endpoint.cli.HttpOptions uses a type in endpoint.cli.
- The types involved
zio.http.endpoint.cli.HttpOptions.Body→zio.http.endpoint.cli.CliRequestzio.http.endpoint.cli.HttpOptions.Body→zio.http.endpoint.cli.HttpOptionszio.http.endpoint.cli.HttpOptions.Body→zio.http.endpoint.cli.Retrieverzio.http.endpoint.cli.HttpOptions.Constant→zio.http.endpoint.cli.HttpOptionszio.http.endpoint.cli.HttpOptions.Header→zio.http.endpoint.cli.CliRequestzio.http.endpoint.cli.HttpOptions.HeaderConstant→zio.http.endpoint.cli.CliRequestzio.http.endpoint.cli.HttpOptions.HeaderOptions→zio.http.endpoint.cli.HttpOptionszio.http.endpoint.cli.HttpOptions.Path→zio.http.endpoint.cli.CliRequestzio.http.endpoint.cli.HttpOptions.Query→zio.http.endpoint.cli.CliRequestzio.http.endpoint.cli.HttpOptions.QueryConstant→zio.http.endpoint.cli.CliRequestzio.http.endpoint.cli.HttpOptions.URLOptions→zio.http.endpoint.cli.HttpOptions
- Direction
- endpoint.cli.HttpOptions uses endpoint.cli, so a change to endpoint.cli can break endpoint.cli.HttpOptions, while a change to endpoint.cli.HttpOptions can't break endpoint.cli.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→20 endpoint.cli.HttpOptions uses gen.scala.Code.CodecType part of a loop✕
- Connections
- 8 pairs of types, where a type in endpoint.cli.HttpOptions uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.endpoint.cli.HttpOptions.Body→zio.http.gen.scala.Code.CodecType.Booleanzio.http.endpoint.cli.HttpOptions.Body→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.cli.HttpOptions.Header→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.cli.HttpOptions.HeaderConstant→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.cli.HttpOptions.Path→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.cli.HttpOptions.Query→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.cli.HttpOptions.QueryConstant→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.cli.HttpOptions.URLOptions→zio.http.gen.scala.Code.CodecType.String
- Direction
- endpoint.cli.HttpOptions uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break endpoint.cli.HttpOptions, while a change to endpoint.cli.HttpOptions can't break gen.scala.Code.CodecType.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→1 gen.grpc.Protobuf uses gen.smithy.Smithy.SimpleShapes✕
- Connections
- 2 pairs of types, where a type in gen.grpc.Protobuf uses a type in gen.smithy.Smithy.SimpleShapes.
- The types involved
zio.http.gen.grpc.Protobuf.File→zio.http.gen.smithy.Smithy.SimpleShapes.Listzio.http.gen.grpc.Protobuf.Service→zio.http.gen.smithy.Smithy.SimpleShapes.List
- Direction
- gen.grpc.Protobuf uses gen.smithy.Smithy.SimpleShapes, so a change to gen.smithy.Smithy.SimpleShapes can break gen.grpc.Protobuf, while a change to gen.grpc.Protobuf can't break gen.smithy.Smithy.SimpleShapes.
- Position
- Below the diagonal: gen.grpc.Protobuf uses a module listed above it, which is the healthy direction.
5→20 gen.grpc.Protobuf uses gen.scala.Code.CodecType part of a loop✕
- Connections
- 4 pairs of types, where a type in gen.grpc.Protobuf uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.gen.grpc.Protobuf.File→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.grpc.Protobuf.Method→zio.http.gen.scala.Code.CodecType.Booleanzio.http.gen.grpc.Protobuf.Method→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.grpc.Protobuf.Service→zio.http.gen.scala.Code.CodecType.String
- Direction
- gen.grpc.Protobuf uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break gen.grpc.Protobuf, while a change to gen.grpc.Protobuf can't break gen.scala.Code.CodecType.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→19 gen.scala.Code.Collection uses gen.scala.Code part of a loop✕
- Connections
- 8 pairs of types, where a type in gen.scala.Code.Collection uses a type in gen.scala.Code.
- The types involved
zio.http.gen.scala.Code.Collection.Map→zio.http.gen.scala.Code.Collectionzio.http.gen.scala.Code.Collection.Map→zio.http.gen.scala.Code.ScalaTypezio.http.gen.scala.Code.Collection.Opt→zio.http.gen.scala.Code.Collectionzio.http.gen.scala.Code.Collection.Opt→zio.http.gen.scala.Code.ScalaTypezio.http.gen.scala.Code.Collection.Seq→zio.http.gen.scala.Code.Collectionzio.http.gen.scala.Code.Collection.Seq→zio.http.gen.scala.Code.ScalaTypezio.http.gen.scala.Code.Collection.Set→zio.http.gen.scala.Code.Collectionzio.http.gen.scala.Code.Collection.Set→zio.http.gen.scala.Code.ScalaType
- Direction
- gen.scala.Code.Collection uses gen.scala.Code, so a change to gen.scala.Code can break gen.scala.Code.Collection, while a change to gen.scala.Code.Collection can't break gen.scala.Code.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→20 gen.scala.Code.Collection uses gen.scala.Code.CodecType part of a loop✕
- Connections
- 2 pairs of types, where a type in gen.scala.Code.Collection uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.gen.scala.Code.Collection.Seq→zio.http.gen.scala.Code.CodecType.Booleanzio.http.gen.scala.Code.Collection.Set→zio.http.gen.scala.Code.CodecType.Boolean
- Direction
- gen.scala.Code.Collection uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break gen.scala.Code.Collection, while a change to gen.scala.Code.Collection can't break gen.scala.Code.CodecType.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→19 gen.scala.Code.ScalaType uses gen.scala.Code part of a loop✕
- Connections
- 4 pairs of types, where a type in gen.scala.Code.ScalaType uses a type in gen.scala.Code.
- The types involved
zio.http.gen.scala.Code.ScalaType.Inferred→zio.http.gen.scala.Code.ScalaTypezio.http.gen.scala.Code.ScalaType.JsonAST→zio.http.gen.scala.Code.ScalaTypezio.http.gen.scala.Code.ScalaType.Or→zio.http.gen.scala.Code.ScalaTypezio.http.gen.scala.Code.ScalaType.Unit→zio.http.gen.scala.Code.ScalaType
- Direction
- gen.scala.Code.ScalaType uses gen.scala.Code, so a change to gen.scala.Code can break gen.scala.Code.ScalaType, while a change to gen.scala.Code.ScalaType can't break gen.scala.Code.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→4 codec.PathCodec uses endpoint.cli.HttpOptions✕
- Connections
- 1 pair of types, where a type in codec.PathCodec uses a type in endpoint.cli.HttpOptions.
- The types involved
zio.http.codec.PathCodec.SegmentSubtree→zio.http.endpoint.cli.HttpOptions.Path
- Direction
- codec.PathCodec uses endpoint.cli.HttpOptions, so a change to endpoint.cli.HttpOptions can break codec.PathCodec, while a change to codec.PathCodec can't break endpoint.cli.HttpOptions.
- Position
- Below the diagonal: codec.PathCodec uses a module listed above it, which is the healthy direction.
8→6 codec.PathCodec uses gen.scala.Code.Collection✕
- Connections
- 2 pairs of types, where a type in codec.PathCodec uses a type in gen.scala.Code.Collection.
- The types involved
zio.http.codec.PathCodec.SegmentSubtree→zio.http.gen.scala.Code.Collection.Mapzio.http.codec.PathCodec.SegmentSubtree→zio.http.gen.scala.Code.Collection.Set
- Direction
- codec.PathCodec uses gen.scala.Code.Collection, so a change to gen.scala.Code.Collection can break codec.PathCodec, while a change to codec.PathCodec can't break gen.scala.Code.Collection.
- Position
- Below the diagonal: codec.PathCodec uses a module listed above it, which is the healthy direction.
8→7 codec.PathCodec uses gen.scala.Code.ScalaType✕
- Connections
- 1 pair of types, where a type in codec.PathCodec uses a type in gen.scala.Code.ScalaType.
- The types involved
zio.http.codec.PathCodec.Fallback→zio.http.gen.scala.Code.ScalaType.Unit
- Direction
- codec.PathCodec uses gen.scala.Code.ScalaType, so a change to gen.scala.Code.ScalaType can break codec.PathCodec, while a change to codec.PathCodec can't break gen.scala.Code.ScalaType.
- Position
- Below the diagonal: codec.PathCodec uses a module listed above it, which is the healthy direction.
8→15 codec.PathCodec uses codec part of a loop✕
- Connections
- 7 pairs of types, where a type in codec.PathCodec uses a type in codec.
- The types involved
zio.http.codec.PathCodec.Annotated→zio.http.codec.PathCodeczio.http.codec.PathCodec.Concat→zio.http.codec.PathCodeczio.http.codec.PathCodec.Fallback→zio.http.codec.PathCodeczio.http.codec.PathCodec.Segment→zio.http.codec.PathCodeczio.http.codec.PathCodec.Segment→zio.http.codec.SegmentCodeczio.http.codec.PathCodec.SegmentSubtree→zio.http.codec.SegmentCodeczio.http.codec.PathCodec.TransformOrFail→zio.http.codec.PathCodec
- Direction
- codec.PathCodec uses codec, so a change to codec can break codec.PathCodec, while a change to codec.PathCodec can't break codec.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→20 codec.PathCodec uses gen.scala.Code.CodecType part of a loop✕
- Connections
- 4 pairs of types, where a type in codec.PathCodec uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.codec.PathCodec.Annotated→zio.http.gen.scala.Code.CodecType.Booleanzio.http.codec.PathCodec.Annotated→zio.http.gen.scala.Code.CodecType.Intzio.http.codec.PathCodec.SegmentSubtree→zio.http.gen.scala.Code.CodecType.Intzio.http.codec.PathCodec.SegmentSubtree→zio.http.gen.scala.Code.CodecType.String
- Direction
- codec.PathCodec uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break codec.PathCodec, while a change to codec.PathCodec can't break gen.scala.Code.CodecType.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→28 codec.PathCodec uses Cookie part of a loop✕
- Connections
- 1 pair of types, where a type in codec.PathCodec uses a type in Cookie.
- The types involved
zio.http.codec.PathCodec.SegmentSubtree→zio.http.Cookie.Response
- Direction
- codec.PathCodec uses Cookie, so a change to Cookie can break codec.PathCodec, while a change to codec.PathCodec can't break Cookie.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→30 codec.PathCodec uses Header.AcceptLanguage part of a loop✕
- Connections
- 1 pair of types, where a type in codec.PathCodec uses a type in Header.AcceptLanguage.
- The types involved
zio.http.codec.PathCodec.Annotated→zio.http.Header.AcceptLanguage.Any
- Direction
- codec.PathCodec uses Header.AcceptLanguage, so a change to Header.AcceptLanguage can break codec.PathCodec, while a change to codec.PathCodec can't break Header.AcceptLanguage.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→1 gen.smithy uses gen.smithy.Smithy.SimpleShapes✕
- Connections
- 5 pairs of types, where a type in gen.smithy uses a type in gen.smithy.Smithy.SimpleShapes.
- The types involved
zio.http.gen.smithy.Member→zio.http.gen.smithy.Smithy.SimpleShapes.Listzio.http.gen.smithy.Shape→zio.http.gen.smithy.Smithy.SimpleShapes.Listzio.http.gen.smithy.SmithyCodecs→zio.http.gen.smithy.Smithy.SimpleShapes.BigDecimalzio.http.gen.smithy.SmithyEndpointGen→zio.http.gen.smithy.Smithy.SimpleShapes.Listzio.http.gen.smithy.SmithyModel→zio.http.gen.smithy.Smithy.SimpleShapes.List
- Direction
- gen.smithy uses gen.smithy.Smithy.SimpleShapes, so a change to gen.smithy.Smithy.SimpleShapes can break gen.smithy, while a change to gen.smithy can't break gen.smithy.Smithy.SimpleShapes.
- Position
- Below the diagonal: gen.smithy uses a module listed above it, which is the healthy direction.
9→4 gen.smithy uses endpoint.cli.HttpOptions✕
- Connections
- 1 pair of types, where a type in gen.smithy uses a type in endpoint.cli.HttpOptions.
- The types involved
zio.http.gen.smithy.SmithyEndpointGen→zio.http.endpoint.cli.HttpOptions.Path
- Direction
- gen.smithy uses endpoint.cli.HttpOptions, so a change to endpoint.cli.HttpOptions can break gen.smithy, while a change to gen.smithy can't break endpoint.cli.HttpOptions.
- Position
- Below the diagonal: gen.smithy uses a module listed above it, which is the healthy direction.
9→5 gen.smithy uses gen.grpc.Protobuf✕
- Connections
- 1 pair of types, where a type in gen.smithy uses a type in gen.grpc.Protobuf.
- The types involved
zio.http.gen.smithy.Smithy→zio.http.gen.grpc.Protobuf.Service
- Direction
- gen.smithy uses gen.grpc.Protobuf, so a change to gen.grpc.Protobuf can break gen.smithy, while a change to gen.smithy can't break gen.grpc.Protobuf.
- Position
- Below the diagonal: gen.smithy uses a module listed above it, which is the healthy direction.
9→6 gen.smithy uses gen.scala.Code.Collection✕
- Connections
- 4 pairs of types, where a type in gen.smithy uses a type in gen.scala.Code.Collection.
- The types involved
zio.http.gen.smithy.Smithy→zio.http.gen.scala.Code.Collection.Mapzio.http.gen.smithy.SmithyConfig→zio.http.gen.scala.Code.Collection.Mapzio.http.gen.smithy.SmithyModel→zio.http.gen.scala.Code.Collection.Mapzio.http.gen.smithy.SmithyValidation→zio.http.gen.scala.Code.Collection.Set
- Direction
- gen.smithy uses gen.scala.Code.Collection, so a change to gen.scala.Code.Collection can break gen.smithy, while a change to gen.smithy can't break gen.scala.Code.Collection.
- Position
- Below the diagonal: gen.smithy uses a module listed above it, which is the healthy direction.
9→7 gen.smithy uses gen.scala.Code.ScalaType✕
- Connections
- 1 pair of types, where a type in gen.smithy uses a type in gen.scala.Code.ScalaType.
- The types involved
zio.http.gen.smithy.SmithyCodecs→zio.http.gen.scala.Code.ScalaType.Unit
- Direction
- gen.smithy uses gen.scala.Code.ScalaType, so a change to gen.scala.Code.ScalaType can break gen.smithy, while a change to gen.smithy can't break gen.scala.Code.ScalaType.
- Position
- Below the diagonal: gen.smithy uses a module listed above it, which is the healthy direction.
9→15 gen.smithy uses codec part of a loop✕
- Connections
- 1 pair of types, where a type in gen.smithy uses a type in codec.
- The types involved
zio.http.gen.smithy.SmithyCodecs→zio.http.codec.RichTextCodec
- Direction
- gen.smithy uses codec, so a change to codec can break gen.smithy, while a change to gen.smithy can't break codec.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→19 gen.smithy uses gen.scala.Code part of a loop✕
- Connections
- 1 pair of types, where a type in gen.smithy uses a type in gen.scala.Code.
- The types involved
zio.http.gen.smithy.SmithyEndpointGen→zio.http.gen.scala.Code.Files
- Direction
- gen.smithy uses gen.scala.Code, so a change to gen.scala.Code can break gen.smithy, while a change to gen.smithy can't break gen.scala.Code.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→20 gen.smithy uses gen.scala.Code.CodecType part of a loop✕
- Connections
- 13 pairs of types, where a type in gen.smithy uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.gen.smithy.Member→zio.http.gen.scala.Code.CodecType.Booleanzio.http.gen.smithy.Member→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.smithy.ShapeId→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.smithy.Smithy→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.smithy.SmithyCodecs→zio.http.gen.scala.Code.CodecType.Longzio.http.gen.smithy.SmithyCodecs→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.smithy.SmithyConfig→zio.http.gen.scala.Code.CodecType.Booleanzio.http.gen.smithy.SmithyConfig→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.smithy.SmithyEndpointGen→zio.http.gen.scala.Code.CodecType.Booleanzio.http.gen.smithy.SmithyEndpointGen→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.smithy.SmithyModel→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.smithy.SmithyParser→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.smithy.SmithyValidation→zio.http.gen.scala.Code.CodecType.String
- Direction
- gen.smithy uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break gen.smithy, while a change to gen.smithy can't break gen.scala.Code.CodecType.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→1 gen.smithy.SmithyTrait uses gen.smithy.Smithy.SimpleShapes✕
- Connections
- 2 pairs of types, where a type in gen.smithy.SmithyTrait uses a type in gen.smithy.Smithy.SimpleShapes.
- The types involved
zio.http.gen.smithy.SmithyTrait.Auth→zio.http.gen.smithy.Smithy.SimpleShapes.Listzio.http.gen.smithy.SmithyTrait.Range→zio.http.gen.smithy.Smithy.SimpleShapes.BigDecimal
- Direction
- gen.smithy.SmithyTrait uses gen.smithy.Smithy.SimpleShapes, so a change to gen.smithy.Smithy.SimpleShapes can break gen.smithy.SmithyTrait, while a change to gen.smithy.SmithyTrait can't break gen.smithy.Smithy.SimpleShapes.
- Position
- Below the diagonal: gen.smithy.SmithyTrait uses a module listed above it, which is the healthy direction.
10→9 gen.smithy.SmithyTrait uses gen.smithy✕
- Connections
- 62 pairs of types, where a type in gen.smithy.SmithyTrait uses a type in gen.smithy. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
zio.http.gen.smithy.SmithyTrait.Auth→zio.http.gen.smithy.ShapeIdzio.http.gen.smithy.SmithyTrait.Auth→zio.http.gen.smithy.SmithyTraitzio.http.gen.smithy.SmithyTrait.Default→zio.http.gen.smithy.NodeValuezio.http.gen.smithy.SmithyTrait.Default→zio.http.gen.smithy.ShapeIdzio.http.gen.smithy.SmithyTrait.Default→zio.http.gen.smithy.SmithyTraitzio.http.gen.smithy.SmithyTrait.Documentation→zio.http.gen.smithy.ShapeIdzio.http.gen.smithy.SmithyTrait.Documentation→zio.http.gen.smithy.SmithyTraitzio.http.gen.smithy.SmithyTrait.Error→zio.http.gen.smithy.ShapeIdzio.http.gen.smithy.SmithyTrait.Error→zio.http.gen.smithy.SmithyTraitzio.http.gen.smithy.SmithyTrait.ErrorMessage→zio.http.gen.smithy.ShapeIdzio.http.gen.smithy.SmithyTrait.ErrorMessage→zio.http.gen.smithy.SmithyTraitzio.http.gen.smithy.SmithyTrait.EventStream→zio.http.gen.smithy.ShapeIdzio.http.gen.smithy.SmithyTrait.EventStream→zio.http.gen.smithy.SmithyTraitzio.http.gen.smithy.SmithyTrait.Generic→zio.http.gen.smithy.NodeValuezio.http.gen.smithy.SmithyTrait.Generic→zio.http.gen.smithy.ShapeIdzio.http.gen.smithy.SmithyTrait.Generic→zio.http.gen.smithy.SmithyTraitzio.http.gen.smithy.SmithyTrait.Http→zio.http.gen.smithy.ShapeIdzio.http.gen.smithy.SmithyTrait.Http→zio.http.gen.smithy.SmithyTraitzio.http.gen.smithy.SmithyTrait.HttpApiKeyAuth→zio.http.gen.smithy.ShapeIdzio.http.gen.smithy.SmithyTrait.HttpApiKeyAuth→zio.http.gen.smithy.SmithyTraitzio.http.gen.smithy.SmithyTrait.HttpBasicAuth→zio.http.gen.smithy.ShapeIdzio.http.gen.smithy.SmithyTrait.HttpBasicAuth→zio.http.gen.smithy.SmithyTraitzio.http.gen.smithy.SmithyTrait.HttpBearerAuth→zio.http.gen.smithy.ShapeIdzio.http.gen.smithy.SmithyTrait.HttpBearerAuth→zio.http.gen.smithy.SmithyTraitzio.http.gen.smithy.SmithyTrait.HttpDigestAuth→zio.http.gen.smithy.ShapeId
- Direction
- gen.smithy.SmithyTrait uses gen.smithy, so a change to gen.smithy can break gen.smithy.SmithyTrait, while a change to gen.smithy.SmithyTrait can't break gen.smithy.
- Position
- Below the diagonal: gen.smithy.SmithyTrait uses a module listed above it, which is the healthy direction.
10→20 gen.smithy.SmithyTrait uses gen.scala.Code.CodecType part of a loop✕
- Connections
- 13 pairs of types, where a type in gen.smithy.SmithyTrait uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.gen.smithy.SmithyTrait.Documentation→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.smithy.SmithyTrait.ErrorMessage→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.smithy.SmithyTrait.Http→zio.http.gen.scala.Code.CodecType.Intzio.http.gen.smithy.SmithyTrait.Http→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.smithy.SmithyTrait.HttpError→zio.http.gen.scala.Code.CodecType.Intzio.http.gen.smithy.SmithyTrait.HttpHeader→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.smithy.SmithyTrait.HttpPrefixHeaders→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.smithy.SmithyTrait.HttpQuery→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.smithy.SmithyTrait.JsonName→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.smithy.SmithyTrait.Length→zio.http.gen.scala.Code.CodecType.Longzio.http.gen.smithy.SmithyTrait.MediaType→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.smithy.SmithyTrait.Pattern→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.smithy.SmithyTrait.TimestampFormat→zio.http.gen.scala.Code.CodecType.String
- Direction
- gen.smithy.SmithyTrait uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break gen.smithy.SmithyTrait, while a change to gen.smithy.SmithyTrait can't break gen.scala.Code.CodecType.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→10 ErrorResponseConfig.ErrorFormat uses gen.smithy.SmithyTrait✕
- Connections
- 3 pairs of types, where a type in ErrorResponseConfig.ErrorFormat uses a type in gen.smithy.SmithyTrait.
- The types involved
zio.http.ErrorResponseConfig.ErrorFormat.Html→zio.http.gen.smithy.SmithyTrait.MediaTypezio.http.ErrorResponseConfig.ErrorFormat.Json→zio.http.gen.smithy.SmithyTrait.MediaTypezio.http.ErrorResponseConfig.ErrorFormat.Text→zio.http.gen.smithy.SmithyTrait.MediaType
- Direction
- ErrorResponseConfig.ErrorFormat uses gen.smithy.SmithyTrait, so a change to gen.smithy.SmithyTrait can break ErrorResponseConfig.ErrorFormat, while a change to ErrorResponseConfig.ErrorFormat can't break gen.smithy.SmithyTrait.
- Position
- Below the diagonal: ErrorResponseConfig.ErrorFormat uses a module listed above it, which is the healthy direction.
12→1 internal uses gen.smithy.Smithy.SimpleShapes✕
- Connections
- 4 pairs of types, where a type in internal uses a type in gen.smithy.Smithy.SimpleShapes.
- The types involved
zio.http.internal.FetchBody→zio.http.gen.smithy.Smithy.SimpleShapes.Bytezio.http.internal.FetchBodyBatched→zio.http.gen.smithy.Smithy.SimpleShapes.Bytezio.http.internal.FetchBodyInternal→zio.http.gen.smithy.Smithy.SimpleShapes.Bytezio.http.internal.FormAST→zio.http.gen.smithy.Smithy.SimpleShapes.Byte
- Direction
- internal uses gen.smithy.Smithy.SimpleShapes, so a change to gen.smithy.Smithy.SimpleShapes can break internal, while a change to internal can't break gen.smithy.Smithy.SimpleShapes.
- Position
- Below the diagonal: internal uses a module listed above it, which is the healthy direction.
12→2 internal uses Header.Vary✕
- Connections
- 4 pairs of types, where a type in internal uses a type in Header.Vary.
- The types involved
zio.http.internal.FetchDriver→zio.http.Header.Vary.Headerszio.http.internal.FetchDriverBatched→zio.http.Header.Vary.Headerszio.http.internal.HeaderGetters→zio.http.Header.Vary.Headerszio.http.internal.HeaderModifier→zio.http.Header.Vary.Headers
- Direction
- internal uses Header.Vary, so a change to Header.Vary can break internal, while a change to internal can't break Header.Vary.
- Position
- Below the diagonal: internal uses a module listed above it, which is the healthy direction.
12→4 internal uses endpoint.cli.HttpOptions✕
- Connections
- 7 pairs of types, where a type in internal uses a type in endpoint.cli.HttpOptions.
- The types involved
zio.http.internal.FetchBody→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.internal.FetchBodyBatched→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.internal.FetchBodyInternal→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.internal.FetchDriver→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.internal.FetchDriverBatched→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.internal.HeaderChecks→zio.http.endpoint.cli.HttpOptions.Headerzio.http.internal.HeaderModifier→zio.http.endpoint.cli.HttpOptions.Header
- Direction
- internal uses endpoint.cli.HttpOptions, so a change to endpoint.cli.HttpOptions can break internal, while a change to internal can't break endpoint.cli.HttpOptions.
- Position
- Below the diagonal: internal uses a module listed above it, which is the healthy direction.
12→5 internal uses gen.grpc.Protobuf✕
- Connections
- 2 pairs of types, where a type in internal uses a type in gen.grpc.Protobuf.
- The types involved
zio.http.internal.FetchDriver→zio.http.gen.grpc.Protobuf.Methodzio.http.internal.FetchDriverBatched→zio.http.gen.grpc.Protobuf.Method
- Direction
- internal uses gen.grpc.Protobuf, so a change to gen.grpc.Protobuf can break internal, while a change to internal can't break gen.grpc.Protobuf.
- Position
- Below the diagonal: internal uses a module listed above it, which is the healthy direction.
12→6 internal uses gen.scala.Code.Collection✕
- Connections
- 2 pairs of types, where a type in internal uses a type in gen.scala.Code.Collection.
- The types involved
zio.http.internal.HeaderModifier→zio.http.gen.scala.Code.Collection.Setzio.http.internal.QueryModifier→zio.http.gen.scala.Code.Collection.Map
- Direction
- internal uses gen.scala.Code.Collection, so a change to gen.scala.Code.Collection can break internal, while a change to internal can't break gen.scala.Code.Collection.
- Position
- Below the diagonal: internal uses a module listed above it, which is the healthy direction.
12→7 internal uses gen.scala.Code.ScalaType✕
- Connections
- 4 pairs of types, where a type in internal uses a type in gen.scala.Code.ScalaType.
- The types involved
zio.http.internal.ByteArrayOutputStreamPool→zio.http.gen.scala.Code.ScalaType.Unitzio.http.internal.FormState→zio.http.gen.scala.Code.ScalaType.Unitzio.http.internal.QueryParamEncoding→zio.http.gen.scala.Code.ScalaType.Unitzio.http.internal.StringBuilderPool→zio.http.gen.scala.Code.ScalaType.Unit
- Direction
- internal uses gen.scala.Code.ScalaType, so a change to gen.scala.Code.ScalaType can break internal, while a change to internal can't break gen.scala.Code.ScalaType.
- Position
- Below the diagonal: internal uses a module listed above it, which is the healthy direction.
12→10 internal uses gen.smithy.SmithyTrait✕
- Connections
- 1 pair of types, where a type in internal uses a type in gen.smithy.SmithyTrait.
- The types involved
zio.http.internal.HeaderChecks→zio.http.gen.smithy.SmithyTrait.MediaType
- Direction
- internal uses gen.smithy.SmithyTrait, so a change to gen.smithy.SmithyTrait can break internal, while a change to internal can't break gen.smithy.SmithyTrait.
- Position
- Below the diagonal: internal uses a module listed above it, which is the healthy direction.
12→15 internal uses codec part of a loop✕
- Connections
- 2 pairs of types, where a type in internal uses a type in codec.
- The types involved
zio.http.internal.ErrorConstructor→zio.http.codec.HttpCodecErrorzio.http.internal.QueryGetters→zio.http.codec.TextCodec
- Direction
- internal uses codec, so a change to codec can break internal, while a change to internal can't break codec.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→18 internal uses endpoint.cli.Retriever part of a loop✕
- Connections
- 2 pairs of types, where a type in internal uses a type in endpoint.cli.Retriever.
- The types involved
zio.http.internal.FetchDriver→zio.http.endpoint.cli.Retriever.URLzio.http.internal.FetchDriverBatched→zio.http.endpoint.cli.Retriever.URL
- Direction
- internal uses endpoint.cli.Retriever, so a change to endpoint.cli.Retriever can break internal, while a change to internal can't break endpoint.cli.Retriever.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→19 internal uses gen.scala.Code part of a loop✕
- Connections
- 1 pair of types, where a type in internal uses a type in gen.scala.Code.
- The types involved
zio.http.internal.StringSchemaCodec→zio.http.gen.scala.Code.Collection
- Direction
- internal uses gen.scala.Code, so a change to gen.scala.Code can break internal, while a change to internal can't break gen.scala.Code.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→20 internal uses gen.scala.Code.CodecType part of a loop✕
- Connections
- 29 pairs of types, where a type in internal uses a type in gen.scala.Code.CodecType. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
zio.http.internal.CharSequenceExtensions→zio.http.gen.scala.Code.CodecType.Booleanzio.http.internal.CharSequenceExtensions→zio.http.gen.scala.Code.CodecType.Intzio.http.internal.CookieEncoding→zio.http.gen.scala.Code.CodecType.Booleanzio.http.internal.CookieEncoding→zio.http.gen.scala.Code.CodecType.Stringzio.http.internal.DateEncoding→zio.http.gen.scala.Code.CodecType.Booleanzio.http.internal.DateEncoding→zio.http.gen.scala.Code.CodecType.Stringzio.http.internal.ErrorConstructor→zio.http.gen.scala.Code.CodecType.Intzio.http.internal.ErrorConstructor→zio.http.gen.scala.Code.CodecType.Stringzio.http.internal.FetchBody→zio.http.gen.scala.Code.CodecType.Booleanzio.http.internal.FetchBody→zio.http.gen.scala.Code.CodecType.Longzio.http.internal.FetchBodyBatched→zio.http.gen.scala.Code.CodecType.Booleanzio.http.internal.FetchBodyBatched→zio.http.gen.scala.Code.CodecType.Longzio.http.internal.FetchBodyInternal→zio.http.gen.scala.Code.CodecType.Booleanzio.http.internal.FetchBodyInternal→zio.http.gen.scala.Code.CodecType.Longzio.http.internal.FormAST→zio.http.gen.scala.Code.CodecType.Booleanzio.http.internal.HeaderChecks→zio.http.gen.scala.Code.CodecType.Booleanzio.http.internal.HeaderGetters→zio.http.gen.scala.Code.CodecType.Stringzio.http.internal.HeaderModifier→zio.http.gen.scala.Code.CodecType.Stringzio.http.internal.OutputEncoder→zio.http.gen.scala.Code.CodecType.Stringzio.http.internal.QueryChecks→zio.http.gen.scala.Code.CodecType.Booleanzio.http.internal.QueryChecks→zio.http.gen.scala.Code.CodecType.Intzio.http.internal.QueryGetters→zio.http.gen.scala.Code.CodecType.Stringzio.http.internal.QueryModifier→zio.http.gen.scala.Code.CodecType.Stringzio.http.internal.QueryParamEncoding→zio.http.gen.scala.Code.CodecType.Booleanzio.http.internal.QueryParamEncoding→zio.http.gen.scala.Code.CodecType.Int
- Direction
- internal uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break internal, while a change to internal can't break gen.scala.Code.CodecType.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→28 internal uses Cookie part of a loop✕
- Connections
- 5 pairs of types, where a type in internal uses a type in Cookie.
- The types involved
zio.http.internal.CookieEncoding→zio.http.Cookie.Requestzio.http.internal.CookieEncoding→zio.http.Cookie.Responsezio.http.internal.FetchBodyInternal→zio.http.Cookie.Responsezio.http.internal.FetchDriver→zio.http.Cookie.Responsezio.http.internal.FetchDriverBatched→zio.http.Cookie.Response
- Direction
- internal uses Cookie, so a change to Cookie can break internal, while a change to internal can't break Cookie.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→29 internal uses Header part of a loop✕
- Connections
- 5 pairs of types, where a type in internal uses a type in Header.
- The types involved
zio.http.internal.FetchBodyBatched→zio.http.Header.ContentLengthzio.http.internal.FetchBodyInternal→zio.http.Header.ContentLengthzio.http.internal.HeaderChecks→zio.http.Header.HeaderTypezio.http.internal.HeaderGetters→zio.http.Header.HeaderTypezio.http.internal.HeaderModifier→zio.http.Header.HeaderType
- Direction
- internal uses Header, so a change to Header can break internal, while a change to internal can't break Header.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→30 internal uses Header.AcceptLanguage part of a loop✕
- Connections
- 6 pairs of types, where a type in internal uses a type in Header.AcceptLanguage.
- The types involved
zio.http.internal.FetchBody→zio.http.Header.AcceptLanguage.Anyzio.http.internal.FetchBodyBatched→zio.http.Header.AcceptLanguage.Anyzio.http.internal.FetchBodyInternal→zio.http.Header.AcceptLanguage.Anyzio.http.internal.FetchDriver→zio.http.Header.AcceptLanguage.Anyzio.http.internal.FetchDriverBatched→zio.http.Header.AcceptLanguage.Anyzio.http.internal.StringSchemaCodec→zio.http.Header.AcceptLanguage.Any
- Direction
- internal uses Header.AcceptLanguage, so a change to Header.AcceptLanguage can break internal, while a change to internal can't break Header.AcceptLanguage.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→31 internal uses Body part of a loop✕
- Connections
- 3 pairs of types, where a type in internal uses a type in Body.
- The types involved
zio.http.internal.FetchBody→zio.http.Body.ContentTypezio.http.internal.FetchBodyBatched→zio.http.Body.ContentTypezio.http.internal.FetchBodyInternal→zio.http.Body.ContentType
- Direction
- internal uses Body, so a change to Body can break internal, while a change to internal can't break Body.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→39 internal uses zio.http part of a loop✕
- Connections
- 12 pairs of types, where a type in internal uses a type in zio.http.
- The types involved
zio.http.internal.FetchDriver→zio.http.ClientSSLConfigzio.http.internal.FetchDriver→zio.http.Driverzio.http.internal.FetchDriver→zio.http.Proxyzio.http.internal.FetchDriver→zio.http.WebSocketAppzio.http.internal.FetchDriverBatched→zio.http.ClientSSLConfigzio.http.internal.FetchDriverBatched→zio.http.Driverzio.http.internal.FetchDriverBatched→zio.http.Proxyzio.http.internal.FetchDriverBatched→zio.http.WebSocketAppzio.http.internal.QueryGetters→zio.http.QueryParamszio.http.internal.QueryGetters→zio.http.QueryParamsErrorzio.http.internal.QueryModifier→zio.http.QueryParamszio.http.internal.QueryParamEncoding→zio.http.QueryParams
- Direction
- internal uses zio.http, so a change to zio.http can break internal, while a change to internal can't break zio.http.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→4 codec.HttpCodec uses endpoint.cli.HttpOptions✕
- Connections
- 3 pairs of types, where a type in codec.HttpCodec uses a type in endpoint.cli.HttpOptions.
- The types involved
zio.http.codec.HttpCodec.Header→zio.http.endpoint.cli.HttpOptions.Headerzio.http.codec.HttpCodec.Path→zio.http.endpoint.cli.HttpOptions.Pathzio.http.codec.HttpCodec.Query→zio.http.endpoint.cli.HttpOptions.Query
- Direction
- codec.HttpCodec uses endpoint.cli.HttpOptions, so a change to endpoint.cli.HttpOptions can break codec.HttpCodec, while a change to codec.HttpCodec can't break endpoint.cli.HttpOptions.
- Position
- Below the diagonal: codec.HttpCodec uses a module listed above it, which is the healthy direction.
13→5 codec.HttpCodec uses gen.grpc.Protobuf✕
- Connections
- 1 pair of types, where a type in codec.HttpCodec uses a type in gen.grpc.Protobuf.
- The types involved
zio.http.codec.HttpCodec.Method→zio.http.gen.grpc.Protobuf.Method
- Direction
- codec.HttpCodec uses gen.grpc.Protobuf, so a change to gen.grpc.Protobuf can break codec.HttpCodec, while a change to codec.HttpCodec can't break gen.grpc.Protobuf.
- Position
- Below the diagonal: codec.HttpCodec uses a module listed above it, which is the healthy direction.
13→6 codec.HttpCodec uses gen.scala.Code.Collection✕
- Connections
- 1 pair of types, where a type in codec.HttpCodec uses a type in gen.scala.Code.Collection.
- The types involved
zio.http.codec.HttpCodec.Annotated→zio.http.gen.scala.Code.Collection.Map
- Direction
- codec.HttpCodec uses gen.scala.Code.Collection, so a change to gen.scala.Code.Collection can break codec.HttpCodec, while a change to codec.HttpCodec can't break gen.scala.Code.Collection.
- Position
- Below the diagonal: codec.HttpCodec uses a module listed above it, which is the healthy direction.
13→7 codec.HttpCodec uses gen.scala.Code.ScalaType✕
- Connections
- 1 pair of types, where a type in codec.HttpCodec uses a type in gen.scala.Code.ScalaType.
- The types involved
zio.http.codec.HttpCodec.Enumeration→zio.http.gen.scala.Code.ScalaType.Unit
- Direction
- codec.HttpCodec uses gen.scala.Code.ScalaType, so a change to gen.scala.Code.ScalaType can break codec.HttpCodec, while a change to codec.HttpCodec can't break gen.scala.Code.ScalaType.
- Position
- Below the diagonal: codec.HttpCodec uses a module listed above it, which is the healthy direction.
13→12 codec.HttpCodec uses internal✕
- Connections
- 1 pair of types, where a type in codec.HttpCodec uses a type in internal.
- The types involved
zio.http.codec.HttpCodec.Query→zio.http.internal.StringSchemaCodec
- Direction
- codec.HttpCodec uses internal, so a change to internal can break codec.HttpCodec, while a change to codec.HttpCodec can't break internal.
- Position
- Below the diagonal: codec.HttpCodec uses a module listed above it, which is the healthy direction.
13→15 codec.HttpCodec uses codec part of a loop✕
- Connections
- 17 pairs of types, where a type in codec.HttpCodec uses a type in codec.
- The types involved
zio.http.codec.HttpCodec.Annotated→zio.http.codec.HttpCodeczio.http.codec.HttpCodec.Atom→zio.http.codec.HttpCodeczio.http.codec.HttpCodec.Combine→zio.http.codec.HttpCodeczio.http.codec.HttpCodec.Content→zio.http.codec.HttpCodeczio.http.codec.HttpCodec.Content→zio.http.codec.HttpContentCodeczio.http.codec.HttpCodec.ContentStream→zio.http.codec.HttpContentCodeczio.http.codec.HttpCodec.Empty→zio.http.codec.HttpCodeczio.http.codec.HttpCodec.Enumeration→zio.http.codec.HttpCodeczio.http.codec.HttpCodec.Fallback→zio.http.codec.Alternatorzio.http.codec.HttpCodec.Fallback→zio.http.codec.HttpCodeczio.http.codec.HttpCodec.Halt→zio.http.codec.HttpCodeczio.http.codec.HttpCodec.Header→zio.http.codec.HttpCodeczio.http.codec.HttpCodec.Method→zio.http.codec.SimpleCodeczio.http.codec.HttpCodec.Path→zio.http.codec.PathCodeczio.http.codec.HttpCodec.Query→zio.http.codec.HttpCodeczio.http.codec.HttpCodec.Status→zio.http.codec.SimpleCodeczio.http.codec.HttpCodec.TransformOrFail→zio.http.codec.HttpCodec
- Direction
- codec.HttpCodec uses codec, so a change to codec can break codec.HttpCodec, while a change to codec.HttpCodec can't break codec.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→18 codec.HttpCodec uses endpoint.cli.Retriever part of a loop✕
- Connections
- 1 pair of types, where a type in codec.HttpCodec uses a type in endpoint.cli.Retriever.
- The types involved
zio.http.codec.HttpCodec.Content→zio.http.endpoint.cli.Retriever.Content
- Direction
- codec.HttpCodec uses endpoint.cli.Retriever, so a change to endpoint.cli.Retriever can break codec.HttpCodec, while a change to codec.HttpCodec can't break endpoint.cli.Retriever.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→20 codec.HttpCodec uses gen.scala.Code.CodecType part of a loop✕
- Connections
- 11 pairs of types, where a type in codec.HttpCodec uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.codec.HttpCodec.Annotated→zio.http.gen.scala.Code.CodecType.Stringzio.http.codec.HttpCodec.Atom→zio.http.gen.scala.Code.CodecType.Intzio.http.codec.HttpCodec.Content→zio.http.gen.scala.Code.CodecType.Intzio.http.codec.HttpCodec.Content→zio.http.gen.scala.Code.CodecType.Stringzio.http.codec.HttpCodec.ContentStream→zio.http.gen.scala.Code.CodecType.Intzio.http.codec.HttpCodec.ContentStream→zio.http.gen.scala.Code.CodecType.Stringzio.http.codec.HttpCodec.Header→zio.http.gen.scala.Code.CodecType.Intzio.http.codec.HttpCodec.Method→zio.http.gen.scala.Code.CodecType.Intzio.http.codec.HttpCodec.Path→zio.http.gen.scala.Code.CodecType.Intzio.http.codec.HttpCodec.Query→zio.http.gen.scala.Code.CodecType.Intzio.http.codec.HttpCodec.Status→zio.http.gen.scala.Code.CodecType.Int
- Direction
- codec.HttpCodec uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break codec.HttpCodec, while a change to codec.HttpCodec can't break gen.scala.Code.CodecType.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→30 codec.HttpCodec uses Header.AcceptLanguage part of a loop✕
- Connections
- 5 pairs of types, where a type in codec.HttpCodec uses a type in Header.AcceptLanguage.
- The types involved
zio.http.codec.HttpCodec.Header→zio.http.Header.AcceptLanguage.Anyzio.http.codec.HttpCodec.Method→zio.http.Header.AcceptLanguage.Anyzio.http.codec.HttpCodec.Path→zio.http.Header.AcceptLanguage.Anyzio.http.codec.HttpCodec.Query→zio.http.Header.AcceptLanguage.Anyzio.http.codec.HttpCodec.Status→zio.http.Header.AcceptLanguage.Any
- Direction
- codec.HttpCodec uses Header.AcceptLanguage, so a change to Header.AcceptLanguage can break codec.HttpCodec, while a change to codec.HttpCodec can't break Header.AcceptLanguage.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→39 codec.HttpCodec uses zio.http part of a loop✕
- Connections
- 2 pairs of types, where a type in codec.HttpCodec uses a type in zio.http.
- The types involved
zio.http.codec.HttpCodec.Query→zio.http.QueryParamszio.http.codec.HttpCodec.Status→zio.http.Status
- Direction
- codec.HttpCodec uses zio.http, so a change to zio.http can break codec.HttpCodec, while a change to codec.HttpCodec can't break zio.http.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→2 codec.internal uses Header.Vary✕
- Connections
- 1 pair of types, where a type in codec.internal uses a type in Header.Vary.
- The types involved
zio.http.codec.internal.EncoderDecoder→zio.http.Header.Vary.Headers
- Direction
- codec.internal uses Header.Vary, so a change to Header.Vary can break codec.internal, while a change to codec.internal can't break Header.Vary.
- Position
- Below the diagonal: codec.internal uses a module listed above it, which is the healthy direction.
14→4 codec.internal uses endpoint.cli.HttpOptions✕
- Connections
- 4 pairs of types, where a type in codec.internal uses a type in endpoint.cli.HttpOptions.
- The types involved
zio.http.codec.internal.AtomizedCodecs→zio.http.endpoint.cli.HttpOptions.Headerzio.http.codec.internal.AtomizedCodecs→zio.http.endpoint.cli.HttpOptions.Queryzio.http.codec.internal.BodyCodec→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.codec.internal.EncoderDecoder→zio.http.endpoint.cli.HttpOptions.Body
- Direction
- codec.internal uses endpoint.cli.HttpOptions, so a change to endpoint.cli.HttpOptions can break codec.internal, while a change to codec.internal can't break endpoint.cli.HttpOptions.
- Position
- Below the diagonal: codec.internal uses a module listed above it, which is the healthy direction.
14→5 codec.internal uses gen.grpc.Protobuf✕
- Connections
- 2 pairs of types, where a type in codec.internal uses a type in gen.grpc.Protobuf.
- The types involved
zio.http.codec.internal.AtomizedCodecs→zio.http.gen.grpc.Protobuf.Methodzio.http.codec.internal.EncoderDecoder→zio.http.gen.grpc.Protobuf.Method
- Direction
- codec.internal uses gen.grpc.Protobuf, so a change to gen.grpc.Protobuf can break codec.internal, while a change to codec.internal can't break gen.grpc.Protobuf.
- Position
- Below the diagonal: codec.internal uses a module listed above it, which is the healthy direction.
14→10 codec.internal uses gen.smithy.SmithyTrait✕
- Connections
- 1 pair of types, where a type in codec.internal uses a type in gen.smithy.SmithyTrait.
- The types involved
zio.http.codec.internal.BodyCodec→zio.http.gen.smithy.SmithyTrait.MediaType
- Direction
- codec.internal uses gen.smithy.SmithyTrait, so a change to gen.smithy.SmithyTrait can break codec.internal, while a change to codec.internal can't break gen.smithy.SmithyTrait.
- Position
- Below the diagonal: codec.internal uses a module listed above it, which is the healthy direction.
14→13 codec.internal uses codec.HttpCodec✕
- Connections
- 2 pairs of types, where a type in codec.internal uses a type in codec.HttpCodec.
- The types involved
zio.http.codec.internal.Atomized→zio.http.codec.HttpCodec.AtomTagzio.http.codec.internal.AtomizedCodecs→zio.http.codec.HttpCodec.Atom
- Direction
- codec.internal uses codec.HttpCodec, so a change to codec.HttpCodec can break codec.internal, while a change to codec.internal can't break codec.HttpCodec.
- Position
- Below the diagonal: codec.internal uses a module listed above it, which is the healthy direction.
14→15 codec.internal uses codec part of a loop✕
- Connections
- 5 pairs of types, where a type in codec.internal uses a type in codec.
- The types involved
zio.http.codec.internal.AtomizedCodecs→zio.http.codec.PathCodeczio.http.codec.internal.AtomizedCodecs→zio.http.codec.SimpleCodeczio.http.codec.internal.BodyCodec→zio.http.codec.CodecConfigzio.http.codec.internal.EncoderDecoder→zio.http.codec.CodecConfigzio.http.codec.internal.Mechanic→zio.http.codec.HttpCodec
- Direction
- codec.internal uses codec, so a change to codec can break codec.internal, while a change to codec.internal can't break codec.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→18 codec.internal uses endpoint.cli.Retriever part of a loop✕
- Connections
- 1 pair of types, where a type in codec.internal uses a type in endpoint.cli.Retriever.
- The types involved
zio.http.codec.internal.EncoderDecoder→zio.http.endpoint.cli.Retriever.URL
- Direction
- codec.internal uses endpoint.cli.Retriever, so a change to endpoint.cli.Retriever can break codec.internal, while a change to codec.internal can't break endpoint.cli.Retriever.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→20 codec.internal uses gen.scala.Code.CodecType part of a loop✕
- Connections
- 2 pairs of types, where a type in codec.internal uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.codec.internal.BodyCodec→zio.http.gen.scala.Code.CodecType.Stringzio.http.codec.internal.Mechanic→zio.http.gen.scala.Code.CodecType.Int
- Direction
- codec.internal uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break codec.internal, while a change to codec.internal can't break gen.scala.Code.CodecType.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→30 codec.internal uses Header.AcceptLanguage part of a loop✕
- Connections
- 1 pair of types, where a type in codec.internal uses a type in Header.AcceptLanguage.
- The types involved
zio.http.codec.internal.BodyCodec→zio.http.Header.AcceptLanguage.Any
- Direction
- codec.internal uses Header.AcceptLanguage, so a change to Header.AcceptLanguage can break codec.internal, while a change to codec.internal can't break Header.AcceptLanguage.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→39 codec.internal uses zio.http part of a loop✕
- Connections
- 3 pairs of types, where a type in codec.internal uses a type in zio.http.
- The types involved
zio.http.codec.internal.AtomizedCodecs→zio.http.Statuszio.http.codec.internal.BodyCodec→zio.http.FormFieldzio.http.codec.internal.EncoderDecoder→zio.http.Status
- Direction
- codec.internal uses zio.http, so a change to zio.http can break codec.internal, while a change to codec.internal can't break zio.http.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→1 codec uses gen.smithy.Smithy.SimpleShapes✕
- Connections
- 4 pairs of types, where a type in codec uses a type in gen.smithy.Smithy.SimpleShapes.
- The types involved
zio.http.codec.ContentCodecs→zio.http.gen.smithy.Smithy.SimpleShapes.Bytezio.http.codec.Doc→zio.http.gen.smithy.Smithy.SimpleShapes.Listzio.http.codec.DocWriter→zio.http.gen.smithy.Smithy.SimpleShapes.Listzio.http.codec.PathCodec→zio.http.gen.smithy.Smithy.SimpleShapes.List
- Direction
- codec uses gen.smithy.Smithy.SimpleShapes, so a change to gen.smithy.Smithy.SimpleShapes can break codec, while a change to codec can't break gen.smithy.Smithy.SimpleShapes.
- Position
- Below the diagonal: codec uses a module listed above it, which is the healthy direction.
15→3 codec uses URL✕
- Connections
- 1 pair of types, where a type in codec uses a type in URL.
- The types involved
zio.http.codec.PathCodec→zio.http.URL.Err
- Direction
- codec uses URL, so a change to URL can break codec, while a change to codec can't break URL.
- Position
- Below the diagonal: codec uses a module listed above it, which is the healthy direction.
15→4 codec uses endpoint.cli.HttpOptions✕
- Connections
- 4 pairs of types, where a type in codec uses a type in endpoint.cli.HttpOptions.
- The types involved
zio.http.codec.HttpCodec→zio.http.endpoint.cli.HttpOptions.Queryzio.http.codec.HttpContentCodec→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.codec.PathCodec→zio.http.endpoint.cli.HttpOptions.Pathzio.http.codec.SegmentCodec→zio.http.endpoint.cli.HttpOptions.Path
- Direction
- codec uses endpoint.cli.HttpOptions, so a change to endpoint.cli.HttpOptions can break codec, while a change to codec can't break endpoint.cli.HttpOptions.
- Position
- Below the diagonal: codec uses a module listed above it, which is the healthy direction.
15→5 codec uses gen.grpc.Protobuf✕
- Connections
- 1 pair of types, where a type in codec uses a type in gen.grpc.Protobuf.
- The types involved
zio.http.codec.MethodCodecs→zio.http.gen.grpc.Protobuf.Method
- Direction
- codec uses gen.grpc.Protobuf, so a change to gen.grpc.Protobuf can break codec, while a change to codec can't break gen.grpc.Protobuf.
- Position
- Below the diagonal: codec uses a module listed above it, which is the healthy direction.
15→6 codec uses gen.scala.Code.Collection✕
- Connections
- 5 pairs of types, where a type in codec uses a type in gen.scala.Code.Collection.
- The types involved
zio.http.codec.Doc→zio.http.gen.scala.Code.Collection.Seqzio.http.codec.HttpCodec→zio.http.gen.scala.Code.Collection.Mapzio.http.codec.HttpCodec→zio.http.gen.scala.Code.Collection.Setzio.http.codec.PathCodec→zio.http.gen.scala.Code.Collection.Optzio.http.codec.PathCodec→zio.http.gen.scala.Code.Collection.Set
- Direction
- codec uses gen.scala.Code.Collection, so a change to gen.scala.Code.Collection can break codec, while a change to codec can't break gen.scala.Code.Collection.
- Position
- Below the diagonal: codec uses a module listed above it, which is the healthy direction.
15→7 codec uses gen.scala.Code.ScalaType✕
- Connections
- 9 pairs of types, where a type in codec uses a type in gen.scala.Code.ScalaType.
- The types involved
zio.http.codec.CombinerLowPriority1→zio.http.gen.scala.Code.ScalaType.Unitzio.http.codec.DocWriter→zio.http.gen.scala.Code.ScalaType.Unitzio.http.codec.HttpCodec→zio.http.gen.scala.Code.ScalaType.Unitzio.http.codec.MethodCodecs→zio.http.gen.scala.Code.ScalaType.Unitzio.http.codec.PathCodec→zio.http.gen.scala.Code.ScalaType.Unitzio.http.codec.PathCodecPlatformSpecific→zio.http.gen.scala.Code.ScalaType.Unitzio.http.codec.RichTextCodec→zio.http.gen.scala.Code.ScalaType.Unitzio.http.codec.SegmentCodec→zio.http.gen.scala.Code.ScalaType.Unitzio.http.codec.StatusCodecs→zio.http.gen.scala.Code.ScalaType.Unit
- Direction
- codec uses gen.scala.Code.ScalaType, so a change to gen.scala.Code.ScalaType can break codec, while a change to codec can't break gen.scala.Code.ScalaType.
- Position
- Below the diagonal: codec uses a module listed above it, which is the healthy direction.
15→8 codec uses codec.PathCodec✕
- Connections
- 1 pair of types, where a type in codec uses a type in codec.PathCodec.
- The types involved
zio.http.codec.PathCodec→zio.http.codec.PathCodec.MetaData
- Direction
- codec uses codec.PathCodec, so a change to codec.PathCodec can break codec, while a change to codec can't break codec.PathCodec.
- Position
- Below the diagonal: codec uses a module listed above it, which is the healthy direction.
15→10 codec uses gen.smithy.SmithyTrait✕
- Connections
- 3 pairs of types, where a type in codec uses a type in gen.smithy.SmithyTrait.
- The types involved
zio.http.codec.ContentCodecs→zio.http.gen.smithy.SmithyTrait.MediaTypezio.http.codec.HeaderCodecs→zio.http.gen.smithy.SmithyTrait.Rangezio.http.codec.HttpContentCodec→zio.http.gen.smithy.SmithyTrait.MediaType
- Direction
- codec uses gen.smithy.SmithyTrait, so a change to gen.smithy.SmithyTrait can break codec, while a change to codec can't break gen.smithy.SmithyTrait.
- Position
- Below the diagonal: codec uses a module listed above it, which is the healthy direction.
15→11 codec uses ErrorResponseConfig.ErrorFormat✕
- Connections
- 1 pair of types, where a type in codec uses a type in ErrorResponseConfig.ErrorFormat.
- The types involved
zio.http.codec.Doc→zio.http.ErrorResponseConfig.ErrorFormat.Html
- Direction
- codec uses ErrorResponseConfig.ErrorFormat, so a change to ErrorResponseConfig.ErrorFormat can break codec, while a change to codec can't break ErrorResponseConfig.ErrorFormat.
- Position
- Below the diagonal: codec uses a module listed above it, which is the healthy direction.
15→12 codec uses internal✕
- Connections
- 1 pair of types, where a type in codec uses a type in internal.
- The types involved
zio.http.codec.HttpContentCodec→zio.http.internal.HeaderOps
- Direction
- codec uses internal, so a change to internal can break codec, while a change to codec can't break internal.
- Position
- Below the diagonal: codec uses a module listed above it, which is the healthy direction.
15→13 codec uses codec.HttpCodec✕
- Connections
- 2 pairs of types, where a type in codec uses a type in codec.HttpCodec.
- The types involved
zio.http.codec.HttpCodec→zio.http.codec.HttpCodec.Metadatazio.http.codec.PathCodec→zio.http.codec.HttpCodec.Fallback
- Direction
- codec uses codec.HttpCodec, so a change to codec.HttpCodec can break codec, while a change to codec can't break codec.HttpCodec.
- Position
- Below the diagonal: codec uses a module listed above it, which is the healthy direction.
15→14 codec uses codec.internal✕
- Connections
- 1 pair of types, where a type in codec uses a type in codec.internal.
- The types involved
zio.http.codec.HttpCodec→zio.http.codec.internal.EncoderDecoder
- Direction
- codec uses codec.internal, so a change to codec.internal can break codec, while a change to codec can't break codec.internal.
- Position
- Below the diagonal: codec uses a module listed above it, which is the healthy direction.
15→20 codec uses gen.scala.Code.CodecType part of a loop✕
- Connections
- 30 pairs of types, where a type in codec uses a type in gen.scala.Code.CodecType. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
zio.http.codec.Alternator→zio.http.gen.scala.Code.CodecType.Booleanzio.http.codec.CodecConfig→zio.http.gen.scala.Code.CodecType.Booleanzio.http.codec.ContentCodecs→zio.http.gen.scala.Code.CodecType.Stringzio.http.codec.Doc→zio.http.gen.scala.Code.CodecType.Booleanzio.http.codec.Doc→zio.http.gen.scala.Code.CodecType.Intzio.http.codec.Doc→zio.http.gen.scala.Code.CodecType.Stringzio.http.codec.DocWriter→zio.http.gen.scala.Code.CodecType.Intzio.http.codec.DocWriter→zio.http.gen.scala.Code.CodecType.Stringzio.http.codec.HeaderCodecs→zio.http.gen.scala.Code.CodecType.Stringzio.http.codec.HttpCodec→zio.http.gen.scala.Code.CodecType.Booleanzio.http.codec.HttpCodec→zio.http.gen.scala.Code.CodecType.Stringzio.http.codec.HttpCodecError→zio.http.gen.scala.Code.CodecType.Stringzio.http.codec.HttpContentCodec→zio.http.gen.scala.Code.CodecType.Stringzio.http.codec.PathCodec→zio.http.gen.scala.Code.CodecType.Booleanzio.http.codec.PathCodec→zio.http.gen.scala.Code.CodecType.Intzio.http.codec.PathCodec→zio.http.gen.scala.Code.CodecType.Stringzio.http.codec.PathCodecPlatformSpecific→zio.http.gen.scala.Code.CodecType.Intzio.http.codec.PathCodecPlatformSpecific→zio.http.gen.scala.Code.CodecType.Longzio.http.codec.PathCodecPlatformSpecific→zio.http.gen.scala.Code.CodecType.Stringzio.http.codec.QueryCodecs→zio.http.gen.scala.Code.CodecType.Stringzio.http.codec.RichTextCodec→zio.http.gen.scala.Code.CodecType.Stringzio.http.codec.SegmentCodec→zio.http.gen.scala.Code.CodecType.Booleanzio.http.codec.SegmentCodec→zio.http.gen.scala.Code.CodecType.Intzio.http.codec.SegmentCodec→zio.http.gen.scala.Code.CodecType.Stringzio.http.codec.SimpleCodec→zio.http.gen.scala.Code.CodecType.Boolean
- Direction
- codec uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break codec, while a change to codec can't break gen.scala.Code.CodecType.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→28 codec uses Cookie part of a loop✕
- Connections
- 4 pairs of types, where a type in codec uses a type in Cookie.
- The types involved
zio.http.codec.HttpCodec→zio.http.Cookie.Requestzio.http.codec.HttpCodec→zio.http.Cookie.Responsezio.http.codec.HttpContentCodec→zio.http.Cookie.Requestzio.http.codec.HttpContentCodec→zio.http.Cookie.Response
- Direction
- codec uses Cookie, so a change to Cookie can break codec, while a change to codec can't break Cookie.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→29 codec uses Header part of a loop✕
- Connections
- 69 pairs of types, where a type in codec uses a type in Header. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
zio.http.codec.HeaderCodecs→zio.http.Header.Acceptzio.http.codec.HeaderCodecs→zio.http.Header.AcceptEncodingzio.http.codec.HeaderCodecs→zio.http.Header.AcceptLanguagezio.http.codec.HeaderCodecs→zio.http.Header.AcceptPatchzio.http.codec.HeaderCodecs→zio.http.Header.AcceptRangeszio.http.codec.HeaderCodecs→zio.http.Header.AccessControlAllowCredentialszio.http.codec.HeaderCodecs→zio.http.Header.AccessControlAllowHeaderszio.http.codec.HeaderCodecs→zio.http.Header.AccessControlAllowMethodszio.http.codec.HeaderCodecs→zio.http.Header.AccessControlAllowOriginzio.http.codec.HeaderCodecs→zio.http.Header.AccessControlExposeHeaderszio.http.codec.HeaderCodecs→zio.http.Header.AccessControlMaxAgezio.http.codec.HeaderCodecs→zio.http.Header.AccessControlRequestHeaderszio.http.codec.HeaderCodecs→zio.http.Header.AccessControlRequestMethodzio.http.codec.HeaderCodecs→zio.http.Header.Agezio.http.codec.HeaderCodecs→zio.http.Header.Authorizationzio.http.codec.HeaderCodecs→zio.http.Header.CacheControlzio.http.codec.HeaderCodecs→zio.http.Header.ClearSiteDatazio.http.codec.HeaderCodecs→zio.http.Header.Connectionzio.http.codec.HeaderCodecs→zio.http.Header.ContentBasezio.http.codec.HeaderCodecs→zio.http.Header.ContentDispositionzio.http.codec.HeaderCodecs→zio.http.Header.ContentEncodingzio.http.codec.HeaderCodecs→zio.http.Header.ContentLanguagezio.http.codec.HeaderCodecs→zio.http.Header.ContentLengthzio.http.codec.HeaderCodecs→zio.http.Header.ContentLocationzio.http.codec.HeaderCodecs→zio.http.Header.ContentMd5
- Direction
- codec uses Header, so a change to Header can break codec, while a change to codec can't break Header.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→30 codec uses Header.AcceptLanguage part of a loop✕
- Connections
- 4 pairs of types, where a type in codec uses a type in Header.AcceptLanguage.
- The types involved
zio.http.codec.ContentCodecs→zio.http.Header.AcceptLanguage.Anyzio.http.codec.PathCodec→zio.http.Header.AcceptLanguage.Anyzio.http.codec.SegmentCodec→zio.http.Header.AcceptLanguage.Anyzio.http.codec.TextCodec→zio.http.Header.AcceptLanguage.Any
- Direction
- codec uses Header.AcceptLanguage, so a change to Header.AcceptLanguage can break codec, while a change to codec can't break Header.AcceptLanguage.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→31 codec uses Body part of a loop✕
- Connections
- 1 pair of types, where a type in codec uses a type in Body.
- The types involved
zio.http.codec.HeaderCodecs→zio.http.Body.ContentType
- Direction
- codec uses Body, so a change to Body can break codec, while a change to codec can't break Body.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→39 codec uses zio.http part of a loop✕
- Connections
- 4 pairs of types, where a type in codec uses a type in zio.http.
- The types involved
zio.http.codec.HeaderCodecs→zio.http.Cookiezio.http.codec.HttpCodec→zio.http.Statuszio.http.codec.PathCodec→zio.http.Routeszio.http.codec.StatusCodecs→zio.http.Status
- Direction
- codec uses zio.http, so a change to zio.http can break codec, while a change to codec can't break zio.http.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→1 endpoint uses gen.smithy.Smithy.SimpleShapes✕
- Connections
- 1 pair of types, where a type in endpoint uses a type in gen.smithy.Smithy.SimpleShapes.
- The types involved
zio.http.endpoint.Endpoint→zio.http.gen.smithy.Smithy.SimpleShapes.List
- Direction
- endpoint uses gen.smithy.Smithy.SimpleShapes, so a change to gen.smithy.Smithy.SimpleShapes can break endpoint, while a change to endpoint can't break gen.smithy.Smithy.SimpleShapes.
- Position
- Below the diagonal: endpoint uses a module listed above it, which is the healthy direction.
16→3 endpoint uses URL✕
- Connections
- 1 pair of types, where a type in endpoint uses a type in URL.
- The types involved
zio.http.endpoint.Endpoint→zio.http.URL.Err
- Direction
- endpoint uses URL, so a change to URL can break endpoint, while a change to endpoint can't break URL.
- Position
- Below the diagonal: endpoint uses a module listed above it, which is the healthy direction.
16→4 endpoint uses endpoint.cli.HttpOptions✕
- Connections
- 1 pair of types, where a type in endpoint uses a type in endpoint.cli.HttpOptions.
- The types involved
zio.http.endpoint.EndpointExecutor→zio.http.endpoint.cli.HttpOptions.Body
- Direction
- endpoint uses endpoint.cli.HttpOptions, so a change to endpoint.cli.HttpOptions can break endpoint, while a change to endpoint can't break endpoint.cli.HttpOptions.
- Position
- Below the diagonal: endpoint uses a module listed above it, which is the healthy direction.
16→6 endpoint uses gen.scala.Code.Collection✕
- Connections
- 1 pair of types, where a type in endpoint uses a type in gen.scala.Code.Collection.
- The types involved
zio.http.endpoint.Endpoint→zio.http.gen.scala.Code.Collection.Map
- Direction
- endpoint uses gen.scala.Code.Collection, so a change to gen.scala.Code.Collection can break endpoint, while a change to endpoint can't break gen.scala.Code.Collection.
- Position
- Below the diagonal: endpoint uses a module listed above it, which is the healthy direction.
16→10 endpoint uses gen.smithy.SmithyTrait✕
- Connections
- 1 pair of types, where a type in endpoint uses a type in gen.smithy.SmithyTrait.
- The types involved
zio.http.endpoint.Endpoint→zio.http.gen.smithy.SmithyTrait.MediaType
- Direction
- endpoint uses gen.smithy.SmithyTrait, so a change to gen.smithy.SmithyTrait can break endpoint, while a change to endpoint can't break gen.smithy.SmithyTrait.
- Position
- Below the diagonal: endpoint uses a module listed above it, which is the healthy direction.
16→15 endpoint uses codec✕
- Connections
- 9 pairs of types, where a type in endpoint uses a type in codec.
- The types involved
zio.http.endpoint.AuthType→zio.http.codec.HttpCodeczio.http.endpoint.Endpoint→zio.http.codec.Alternatorzio.http.endpoint.Endpoint→zio.http.codec.Combinerzio.http.endpoint.Endpoint→zio.http.codec.Doczio.http.endpoint.Endpoint→zio.http.codec.HeaderCodeczio.http.endpoint.Endpoint→zio.http.codec.HttpCodeczio.http.endpoint.Endpoint→zio.http.codec.HttpCodecErrorzio.http.endpoint.Endpoint→zio.http.codec.QueryCodeczio.http.endpoint.EndpointExecutor→zio.http.codec.Combiner
- Direction
- endpoint uses codec, so a change to codec can break endpoint, while a change to endpoint can't break codec.
- Position
- Below the diagonal: endpoint uses a module listed above it, which is the healthy direction.
16→18 endpoint uses endpoint.cli.Retriever part of a loop✕
- Connections
- 3 pairs of types, where a type in endpoint uses a type in endpoint.cli.Retriever.
- The types involved
zio.http.endpoint.Endpoint→zio.http.endpoint.cli.Retriever.URLzio.http.endpoint.EndpointLocator→zio.http.endpoint.cli.Retriever.URLzio.http.endpoint.EndpointPlatformSpecific→zio.http.endpoint.cli.Retriever.URL
- Direction
- endpoint uses endpoint.cli.Retriever, so a change to endpoint.cli.Retriever can break endpoint, while a change to endpoint can't break endpoint.cli.Retriever.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→20 endpoint uses gen.scala.Code.CodecType part of a loop✕
- Connections
- 2 pairs of types, where a type in endpoint uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.endpoint.Endpoint→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.EndpointNotFound→zio.http.gen.scala.Code.CodecType.String
- Direction
- endpoint uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break endpoint, while a change to endpoint can't break gen.scala.Code.CodecType.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→28 endpoint uses Cookie part of a loop✕
- Connections
- 2 pairs of types, where a type in endpoint uses a type in Cookie.
- The types involved
zio.http.endpoint.Endpoint→zio.http.Cookie.Requestzio.http.endpoint.EndpointExecutor→zio.http.Cookie.Response
- Direction
- endpoint uses Cookie, so a change to Cookie can break endpoint, while a change to endpoint can't break Cookie.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→30 endpoint uses Header.AcceptLanguage part of a loop✕
- Connections
- 2 pairs of types, where a type in endpoint uses a type in Header.AcceptLanguage.
- The types involved
zio.http.endpoint.Endpoint→zio.http.Header.AcceptLanguage.Anyzio.http.endpoint.EndpointExecutor→zio.http.Header.AcceptLanguage.Any
- Direction
- endpoint uses Header.AcceptLanguage, so a change to Header.AcceptLanguage can break endpoint, while a change to endpoint can't break Header.AcceptLanguage.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→39 endpoint uses zio.http part of a loop✕
- Connections
- 6 pairs of types, where a type in endpoint uses a type in zio.http.
- The types involved
zio.http.endpoint.AuthType→zio.http.Statuszio.http.endpoint.Endpoint→zio.http.Handlerzio.http.endpoint.Endpoint→zio.http.Routezio.http.endpoint.Endpoint→zio.http.RoutePatternzio.http.endpoint.Endpoint→zio.http.Statuszio.http.endpoint.EndpointExecutor→zio.http.ZClient
- Direction
- endpoint uses zio.http, so a change to zio.http can break endpoint, while a change to endpoint can't break zio.http.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→1 endpoint.cli uses gen.smithy.Smithy.SimpleShapes✕
- Connections
- 1 pair of types, where a type in endpoint.cli uses a type in gen.smithy.Smithy.SimpleShapes.
- The types involved
zio.http.endpoint.cli.CliEndpoint→zio.http.gen.smithy.Smithy.SimpleShapes.List
- Direction
- endpoint.cli uses gen.smithy.Smithy.SimpleShapes, so a change to gen.smithy.Smithy.SimpleShapes can break endpoint.cli, while a change to endpoint.cli can't break gen.smithy.Smithy.SimpleShapes.
- Position
- Below the diagonal: endpoint.cli uses a module listed above it, which is the healthy direction.
17→2 endpoint.cli uses Header.Vary✕
- Connections
- 1 pair of types, where a type in endpoint.cli uses a type in Header.Vary.
- The types involved
zio.http.endpoint.cli.CliRequest→zio.http.Header.Vary.Headers
- Direction
- endpoint.cli uses Header.Vary, so a change to Header.Vary can break endpoint.cli, while a change to endpoint.cli can't break Header.Vary.
- Position
- Below the diagonal: endpoint.cli uses a module listed above it, which is the healthy direction.
17→4 endpoint.cli uses endpoint.cli.HttpOptions✕
- Connections
- 3 pairs of types, where a type in endpoint.cli uses a type in endpoint.cli.HttpOptions.
- The types involved
zio.http.endpoint.cli.CliEndpoint→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.endpoint.cli.CliEndpoint→zio.http.endpoint.cli.HttpOptions.HeaderOptionszio.http.endpoint.cli.CliEndpoint→zio.http.endpoint.cli.HttpOptions.URLOptions
- Direction
- endpoint.cli uses endpoint.cli.HttpOptions, so a change to endpoint.cli.HttpOptions can break endpoint.cli, while a change to endpoint.cli can't break endpoint.cli.HttpOptions.
- Position
- Below the diagonal: endpoint.cli uses a module listed above it, which is the healthy direction.
17→5 endpoint.cli uses gen.grpc.Protobuf✕
- Connections
- 2 pairs of types, where a type in endpoint.cli uses a type in gen.grpc.Protobuf.
- The types involved
zio.http.endpoint.cli.CliEndpoint→zio.http.gen.grpc.Protobuf.Methodzio.http.endpoint.cli.CliRequest→zio.http.gen.grpc.Protobuf.Method
- Direction
- endpoint.cli uses gen.grpc.Protobuf, so a change to gen.grpc.Protobuf can break endpoint.cli, while a change to endpoint.cli can't break gen.grpc.Protobuf.
- Position
- Below the diagonal: endpoint.cli uses a module listed above it, which is the healthy direction.
17→15 endpoint.cli uses codec✕
- Connections
- 2 pairs of types, where a type in endpoint.cli uses a type in codec.
- The types involved
zio.http.endpoint.cli.CliEndpoint→zio.http.codec.Doczio.http.endpoint.cli.HttpOptions→zio.http.codec.Doc
- Direction
- endpoint.cli uses codec, so a change to codec can break endpoint.cli, while a change to endpoint.cli can't break codec.
- Position
- Below the diagonal: endpoint.cli uses a module listed above it, which is the healthy direction.
17→16 endpoint.cli uses endpoint✕
- Connections
- 1 pair of types, where a type in endpoint.cli uses a type in endpoint.
- The types involved
zio.http.endpoint.cli.HttpCommand→zio.http.endpoint.Endpoint
- Direction
- endpoint.cli uses endpoint, so a change to endpoint can break endpoint.cli, while a change to endpoint.cli can't break endpoint.
- Position
- Below the diagonal: endpoint.cli uses a module listed above it, which is the healthy direction.
17→18 endpoint.cli uses endpoint.cli.Retriever part of a loop✕
- Connections
- 1 pair of types, where a type in endpoint.cli uses a type in endpoint.cli.Retriever.
- The types involved
zio.http.endpoint.cli.CliRequest→zio.http.endpoint.cli.Retriever.URL
- Direction
- endpoint.cli uses endpoint.cli.Retriever, so a change to endpoint.cli.Retriever can break endpoint.cli, while a change to endpoint.cli can't break endpoint.cli.Retriever.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→20 endpoint.cli uses gen.scala.Code.CodecType part of a loop✕
- Connections
- 8 pairs of types, where a type in endpoint.cli uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.endpoint.cli.CliEndpoint→zio.http.gen.scala.Code.CodecType.Booleanzio.http.endpoint.cli.CliEndpoint→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.cli.CliRequest→zio.http.gen.scala.Code.CodecType.Booleanzio.http.endpoint.cli.CliRequest→zio.http.gen.scala.Code.CodecType.Intzio.http.endpoint.cli.CliRequest→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.cli.HttpCommand→zio.http.gen.scala.Code.CodecType.Booleanzio.http.endpoint.cli.HttpCommand→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.cli.HttpOptions→zio.http.gen.scala.Code.CodecType.String
- Direction
- endpoint.cli uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break endpoint.cli, while a change to endpoint.cli can't break gen.scala.Code.CodecType.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→28 endpoint.cli uses Cookie part of a loop✕
- Connections
- 1 pair of types, where a type in endpoint.cli uses a type in Cookie.
- The types involved
zio.http.endpoint.cli.CliRequest→zio.http.Cookie.Request
- Direction
- endpoint.cli uses Cookie, so a change to Cookie can break endpoint.cli, while a change to endpoint.cli can't break Cookie.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→30 endpoint.cli uses Header.AcceptLanguage part of a loop✕
- Connections
- 1 pair of types, where a type in endpoint.cli uses a type in Header.AcceptLanguage.
- The types involved
zio.http.endpoint.cli.CliZLayerClient→zio.http.Header.AcceptLanguage.Any
- Direction
- endpoint.cli uses Header.AcceptLanguage, so a change to Header.AcceptLanguage can break endpoint.cli, while a change to endpoint.cli can't break Header.AcceptLanguage.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→39 endpoint.cli uses zio.http part of a loop✕
- Connections
- 1 pair of types, where a type in endpoint.cli uses a type in zio.http.
- The types involved
zio.http.endpoint.cli.Retriever→zio.http.FormField
- Direction
- endpoint.cli uses zio.http, so a change to zio.http can break endpoint.cli, while a change to endpoint.cli can't break zio.http.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→4 endpoint.cli.Retriever uses endpoint.cli.HttpOptions✕
- Connections
- 1 pair of types, where a type in endpoint.cli.Retriever uses a type in endpoint.cli.HttpOptions.
- The types involved
zio.http.endpoint.cli.Retriever.File→zio.http.endpoint.cli.HttpOptions.Path
- Direction
- endpoint.cli.Retriever uses endpoint.cli.HttpOptions, so a change to endpoint.cli.HttpOptions can break endpoint.cli.Retriever, while a change to endpoint.cli.Retriever can't break endpoint.cli.HttpOptions.
- Position
- Below the diagonal: endpoint.cli.Retriever uses a module listed above it, which is the healthy direction.
18→10 endpoint.cli.Retriever uses gen.smithy.SmithyTrait✕
- Connections
- 2 pairs of types, where a type in endpoint.cli.Retriever uses a type in gen.smithy.SmithyTrait.
- The types involved
zio.http.endpoint.cli.Retriever.File→zio.http.gen.smithy.SmithyTrait.MediaTypezio.http.endpoint.cli.Retriever.URL→zio.http.gen.smithy.SmithyTrait.MediaType
- Direction
- endpoint.cli.Retriever uses gen.smithy.SmithyTrait, so a change to gen.smithy.SmithyTrait can break endpoint.cli.Retriever, while a change to endpoint.cli.Retriever can't break gen.smithy.SmithyTrait.
- Position
- Below the diagonal: endpoint.cli.Retriever uses a module listed above it, which is the healthy direction.
18→17 endpoint.cli.Retriever uses endpoint.cli✕
- Connections
- 3 pairs of types, where a type in endpoint.cli.Retriever uses a type in endpoint.cli.
- The types involved
zio.http.endpoint.cli.Retriever.Content→zio.http.endpoint.cli.Retrieverzio.http.endpoint.cli.Retriever.File→zio.http.endpoint.cli.Retrieverzio.http.endpoint.cli.Retriever.URL→zio.http.endpoint.cli.Retriever
- Direction
- endpoint.cli.Retriever uses endpoint.cli, so a change to endpoint.cli can break endpoint.cli.Retriever, while a change to endpoint.cli.Retriever can't break endpoint.cli.
- Position
- Below the diagonal: endpoint.cli.Retriever uses a module listed above it, which is the healthy direction.
18→20 endpoint.cli.Retriever uses gen.scala.Code.CodecType part of a loop✕
- Connections
- 2 pairs of types, where a type in endpoint.cli.Retriever uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.endpoint.cli.Retriever.File→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.cli.Retriever.URL→zio.http.gen.scala.Code.CodecType.String
- Direction
- endpoint.cli.Retriever uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break endpoint.cli.Retriever, while a change to endpoint.cli.Retriever can't break gen.scala.Code.CodecType.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→39 endpoint.cli.Retriever uses zio.http part of a loop✕
- Connections
- 3 pairs of types, where a type in endpoint.cli.Retriever uses a type in zio.http.
- The types involved
zio.http.endpoint.cli.Retriever.Content→zio.http.FormFieldzio.http.endpoint.cli.Retriever.File→zio.http.FormFieldzio.http.endpoint.cli.Retriever.URL→zio.http.FormField
- Direction
- endpoint.cli.Retriever uses zio.http, so a change to zio.http can break endpoint.cli.Retriever, while a change to endpoint.cli.Retriever can't break zio.http.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→1 gen.scala.Code uses gen.smithy.Smithy.SimpleShapes✕
- Connections
- 10 pairs of types, where a type in gen.scala.Code uses a type in gen.smithy.Smithy.SimpleShapes.
- The types involved
zio.http.gen.scala.Code.Annotation→zio.http.gen.smithy.Smithy.SimpleShapes.Listzio.http.gen.scala.Code.CaseClass→zio.http.gen.smithy.Smithy.SimpleShapes.Listzio.http.gen.scala.Code.EndpointCode→zio.http.gen.smithy.Smithy.SimpleShapes.Listzio.http.gen.scala.Code.Enum→zio.http.gen.smithy.Smithy.SimpleShapes.Listzio.http.gen.scala.Code.Field→zio.http.gen.smithy.Smithy.SimpleShapes.Listzio.http.gen.scala.Code.File→zio.http.gen.smithy.Smithy.SimpleShapes.Listzio.http.gen.scala.Code.Files→zio.http.gen.smithy.Smithy.SimpleShapes.Listzio.http.gen.scala.Code.HeadersCode→zio.http.gen.smithy.Smithy.SimpleShapes.Listzio.http.gen.scala.Code.Object→zio.http.gen.smithy.Smithy.SimpleShapes.Listzio.http.gen.scala.Code.PathPatternCode→zio.http.gen.smithy.Smithy.SimpleShapes.List
- Direction
- gen.scala.Code uses gen.smithy.Smithy.SimpleShapes, so a change to gen.smithy.Smithy.SimpleShapes can break gen.scala.Code, while a change to gen.scala.Code can't break gen.smithy.Smithy.SimpleShapes.
- Position
- Below the diagonal: gen.scala.Code uses a module listed above it, which is the healthy direction.
19→5 gen.scala.Code uses gen.grpc.Protobuf✕
- Connections
- 1 pair of types, where a type in gen.scala.Code uses a type in gen.grpc.Protobuf.
- The types involved
zio.http.gen.scala.Code.EndpointCode→zio.http.gen.grpc.Protobuf.Method
- Direction
- gen.scala.Code uses gen.grpc.Protobuf, so a change to gen.grpc.Protobuf can break gen.scala.Code, while a change to gen.scala.Code can't break gen.grpc.Protobuf.
- Position
- Below the diagonal: gen.scala.Code uses a module listed above it, which is the healthy direction.
19→6 gen.scala.Code uses gen.scala.Code.Collection✕
- Connections
- 6 pairs of types, where a type in gen.scala.Code uses a type in gen.scala.Code.Collection.
- The types involved
zio.http.gen.scala.Code.EndpointCode→zio.http.gen.scala.Code.Collection.Setzio.http.gen.scala.Code.Object→zio.http.gen.scala.Code.Collection.Mapzio.http.gen.scala.Code.ScalaType→zio.http.gen.scala.Code.Collection.Mapzio.http.gen.scala.Code.ScalaType→zio.http.gen.scala.Code.Collection.Optzio.http.gen.scala.Code.ScalaType→zio.http.gen.scala.Code.Collection.Seqzio.http.gen.scala.Code.ScalaType→zio.http.gen.scala.Code.Collection.Set
- Direction
- gen.scala.Code uses gen.scala.Code.Collection, so a change to gen.scala.Code.Collection can break gen.scala.Code, while a change to gen.scala.Code can't break gen.scala.Code.Collection.
- Position
- Below the diagonal: gen.scala.Code uses a module listed above it, which is the healthy direction.
19→18 gen.scala.Code uses endpoint.cli.Retriever✕
- Connections
- 1 pair of types, where a type in gen.scala.Code uses a type in endpoint.cli.Retriever.
- The types involved
zio.http.gen.scala.Code.Files→zio.http.endpoint.cli.Retriever.File
- Direction
- gen.scala.Code uses endpoint.cli.Retriever, so a change to endpoint.cli.Retriever can break gen.scala.Code, while a change to gen.scala.Code can't break endpoint.cli.Retriever.
- Position
- Below the diagonal: gen.scala.Code uses a module listed above it, which is the healthy direction.
19→20 gen.scala.Code uses gen.scala.Code.CodecType part of a loop✕
- Connections
- 17 pairs of types, where a type in gen.scala.Code uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.gen.scala.Code.Annotation→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.scala.Code.AuthTypeCode→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.scala.Code.CaseClass→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.scala.Code.Enum→zio.http.gen.scala.Code.CodecType.Booleanzio.http.gen.scala.Code.Enum→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.scala.Code.Field→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.scala.Code.File→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.scala.Code.HeaderCode→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.scala.Code.InCode→zio.http.gen.scala.Code.CodecType.Booleanzio.http.gen.scala.Code.InCode→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.scala.Code.Object→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.scala.Code.OutCode→zio.http.gen.scala.Code.CodecType.Booleanzio.http.gen.scala.Code.OutCode→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.scala.Code.PathSegmentCode→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.scala.Code.QueryParamCode→zio.http.gen.scala.Code.CodecType.Stringzio.http.gen.scala.Code.ScalaType→zio.http.gen.scala.Code.CodecType.Booleanzio.http.gen.scala.Code.TypeRef→zio.http.gen.scala.Code.CodecType.String
- Direction
- gen.scala.Code uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break gen.scala.Code, while a change to gen.scala.Code can't break gen.scala.Code.CodecType.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→39 gen.scala.Code uses zio.http part of a loop✕
- Connections
- 1 pair of types, where a type in gen.scala.Code uses a type in zio.http.
- The types involved
zio.http.gen.scala.Code.OutCode→zio.http.Status
- Direction
- gen.scala.Code uses zio.http, so a change to zio.http can break gen.scala.Code, while a change to gen.scala.Code can't break zio.http.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→19 gen.scala.Code.CodecType uses gen.scala.Code✕
- Connections
- 13 pairs of types, where a type in gen.scala.Code.CodecType uses a type in gen.scala.Code.
- The types involved
zio.http.gen.scala.Code.CodecType.Aliased→zio.http.gen.scala.Code.CodecTypezio.http.gen.scala.Code.CodecType.Boolean→zio.http.gen.scala.Code.CodecTypezio.http.gen.scala.Code.CodecType.Duration→zio.http.gen.scala.Code.CodecTypezio.http.gen.scala.Code.CodecType.Instant→zio.http.gen.scala.Code.CodecTypezio.http.gen.scala.Code.CodecType.Int→zio.http.gen.scala.Code.CodecTypezio.http.gen.scala.Code.CodecType.Literal→zio.http.gen.scala.Code.CodecTypezio.http.gen.scala.Code.CodecType.LocalDate→zio.http.gen.scala.Code.CodecTypezio.http.gen.scala.Code.CodecType.LocalTime→zio.http.gen.scala.Code.CodecTypezio.http.gen.scala.Code.CodecType.Long→zio.http.gen.scala.Code.CodecTypezio.http.gen.scala.Code.CodecType.SeqOf→zio.http.gen.scala.Code.CodecTypezio.http.gen.scala.Code.CodecType.SetOf→zio.http.gen.scala.Code.CodecTypezio.http.gen.scala.Code.CodecType.String→zio.http.gen.scala.Code.CodecTypezio.http.gen.scala.Code.CodecType.UUID→zio.http.gen.scala.Code.CodecType
- Direction
- gen.scala.Code.CodecType uses gen.scala.Code, so a change to gen.scala.Code can break gen.scala.Code.CodecType, while a change to gen.scala.Code.CodecType can't break gen.scala.Code.
- Position
- Below the diagonal: gen.scala.Code.CodecType uses a module listed above it, which is the healthy direction.
21→1 endpoint.openapi.JsonSchema uses gen.smithy.Smithy.SimpleShapes✕
- Connections
- 1 pair of types, where a type in endpoint.openapi.JsonSchema uses a type in gen.smithy.Smithy.SimpleShapes.
- The types involved
zio.http.endpoint.openapi.JsonSchema.Number→zio.http.gen.smithy.Smithy.SimpleShapes.Double
- Direction
- endpoint.openapi.JsonSchema uses gen.smithy.Smithy.SimpleShapes, so a change to gen.smithy.Smithy.SimpleShapes can break endpoint.openapi.JsonSchema, while a change to endpoint.openapi.JsonSchema can't break gen.smithy.Smithy.SimpleShapes.
- Position
- Below the diagonal: endpoint.openapi.JsonSchema uses a module listed above it, which is the healthy direction.
21→6 endpoint.openapi.JsonSchema uses gen.scala.Code.Collection✕
- Connections
- 2 pairs of types, where a type in endpoint.openapi.JsonSchema uses a type in gen.scala.Code.Collection.
- The types involved
zio.http.endpoint.openapi.JsonSchema.JsonSchemaRoot→zio.http.gen.scala.Code.Collection.Mapzio.http.endpoint.openapi.JsonSchema.Object→zio.http.gen.scala.Code.Collection.Map
- Direction
- endpoint.openapi.JsonSchema uses gen.scala.Code.Collection, so a change to gen.scala.Code.Collection can break endpoint.openapi.JsonSchema, while a change to endpoint.openapi.JsonSchema can't break gen.scala.Code.Collection.
- Position
- Below the diagonal: endpoint.openapi.JsonSchema uses a module listed above it, which is the healthy direction.
21→8 endpoint.openapi.JsonSchema uses codec.PathCodec✕
- Connections
- 1 pair of types, where a type in endpoint.openapi.JsonSchema uses a type in codec.PathCodec.
- The types involved
zio.http.endpoint.openapi.JsonSchema.AnnotatedSchema→zio.http.codec.PathCodec.MetaData
- Direction
- endpoint.openapi.JsonSchema uses codec.PathCodec, so a change to codec.PathCodec can break endpoint.openapi.JsonSchema, while a change to endpoint.openapi.JsonSchema can't break codec.PathCodec.
- Position
- Below the diagonal: endpoint.openapi.JsonSchema uses a module listed above it, which is the healthy direction.
21→10 endpoint.openapi.JsonSchema uses gen.smithy.SmithyTrait✕
- Connections
- 2 pairs of types, where a type in endpoint.openapi.JsonSchema uses a type in gen.smithy.SmithyTrait.
- The types involved
zio.http.endpoint.openapi.JsonSchema.Object→zio.http.gen.smithy.SmithyTrait.Patternzio.http.endpoint.openapi.JsonSchema.String→zio.http.gen.smithy.SmithyTrait.Pattern
- Direction
- endpoint.openapi.JsonSchema uses gen.smithy.SmithyTrait, so a change to gen.smithy.SmithyTrait can break endpoint.openapi.JsonSchema, while a change to endpoint.openapi.JsonSchema can't break gen.smithy.SmithyTrait.
- Position
- Below the diagonal: endpoint.openapi.JsonSchema uses a module listed above it, which is the healthy direction.
21→11 endpoint.openapi.JsonSchema uses ErrorResponseConfig.ErrorFormat✕
- Connections
- 1 pair of types, where a type in endpoint.openapi.JsonSchema uses a type in ErrorResponseConfig.ErrorFormat.
- The types involved
zio.http.endpoint.openapi.JsonSchema.EnumValue→zio.http.ErrorResponseConfig.ErrorFormat.Json
- Direction
- endpoint.openapi.JsonSchema uses ErrorResponseConfig.ErrorFormat, so a change to ErrorResponseConfig.ErrorFormat can break endpoint.openapi.JsonSchema, while a change to endpoint.openapi.JsonSchema can't break ErrorResponseConfig.ErrorFormat.
- Position
- Below the diagonal: endpoint.openapi.JsonSchema uses a module listed above it, which is the healthy direction.
21→19 endpoint.openapi.JsonSchema uses gen.scala.Code✕
- Connections
- 1 pair of types, where a type in endpoint.openapi.JsonSchema uses a type in gen.scala.Code.
- The types involved
zio.http.endpoint.openapi.JsonSchema.Object→zio.http.gen.scala.Code.Object
- Direction
- endpoint.openapi.JsonSchema uses gen.scala.Code, so a change to gen.scala.Code can break endpoint.openapi.JsonSchema, while a change to endpoint.openapi.JsonSchema can't break gen.scala.Code.
- Position
- Below the diagonal: endpoint.openapi.JsonSchema uses a module listed above it, which is the healthy direction.
21→20 endpoint.openapi.JsonSchema uses gen.scala.Code.CodecType✕
- Connections
- 14 pairs of types, where a type in endpoint.openapi.JsonSchema uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.endpoint.openapi.JsonSchema.ArrayType→zio.http.gen.scala.Code.CodecType.Booleanzio.http.endpoint.openapi.JsonSchema.ArrayType→zio.http.gen.scala.Code.CodecType.Intzio.http.endpoint.openapi.JsonSchema.Integer→zio.http.gen.scala.Code.CodecType.Booleanzio.http.endpoint.openapi.JsonSchema.Integer→zio.http.gen.scala.Code.CodecType.Longzio.http.endpoint.openapi.JsonSchema.JsonSchemaRoot→zio.http.gen.scala.Code.CodecType.Intzio.http.endpoint.openapi.JsonSchema.JsonSchemaRoot→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.JsonSchema.Number→zio.http.gen.scala.Code.CodecType.Booleanzio.http.endpoint.openapi.JsonSchema.Object→zio.http.gen.scala.Code.CodecType.Booleanzio.http.endpoint.openapi.JsonSchema.Object→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.JsonSchema.Pattern→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.JsonSchema.RefSchema→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.JsonSchema.SchemaSpec→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.JsonSchema.String→zio.http.gen.scala.Code.CodecType.Intzio.http.endpoint.openapi.JsonSchema.StringFormat→zio.http.gen.scala.Code.CodecType.String
- Direction
- endpoint.openapi.JsonSchema uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break endpoint.openapi.JsonSchema, while a change to endpoint.openapi.JsonSchema can't break gen.scala.Code.CodecType.
- Position
- Below the diagonal: endpoint.openapi.JsonSchema uses a module listed above it, which is the healthy direction.
21→36 endpoint.openapi.JsonSchema uses endpoint.openapi part of a loop✕
- Connections
- 30 pairs of types, where a type in endpoint.openapi.JsonSchema uses a type in endpoint.openapi. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
zio.http.endpoint.openapi.JsonSchema.AllOfSchema→zio.http.endpoint.openapi.JsonSchemazio.http.endpoint.openapi.JsonSchema.AllOfSchema→zio.http.endpoint.openapi.SerializableJsonSchemazio.http.endpoint.openapi.JsonSchema.AnnotatedSchema→zio.http.endpoint.openapi.JsonSchemazio.http.endpoint.openapi.JsonSchema.AnnotatedSchema→zio.http.endpoint.openapi.SerializableJsonSchemazio.http.endpoint.openapi.JsonSchema.AnyJson→zio.http.endpoint.openapi.JsonSchemazio.http.endpoint.openapi.JsonSchema.AnyJson→zio.http.endpoint.openapi.SerializableJsonSchemazio.http.endpoint.openapi.JsonSchema.AnyOfSchema→zio.http.endpoint.openapi.JsonSchemazio.http.endpoint.openapi.JsonSchema.AnyOfSchema→zio.http.endpoint.openapi.SerializableJsonSchemazio.http.endpoint.openapi.JsonSchema.ArrayType→zio.http.endpoint.openapi.JsonSchemazio.http.endpoint.openapi.JsonSchema.ArrayType→zio.http.endpoint.openapi.SerializableJsonSchemazio.http.endpoint.openapi.JsonSchema.Boolean→zio.http.endpoint.openapi.JsonSchemazio.http.endpoint.openapi.JsonSchema.Boolean→zio.http.endpoint.openapi.SerializableJsonSchemazio.http.endpoint.openapi.JsonSchema.Enum→zio.http.endpoint.openapi.JsonSchemazio.http.endpoint.openapi.JsonSchema.Enum→zio.http.endpoint.openapi.SerializableJsonSchemazio.http.endpoint.openapi.JsonSchema.Integer→zio.http.endpoint.openapi.JsonSchemazio.http.endpoint.openapi.JsonSchema.Integer→zio.http.endpoint.openapi.SerializableJsonSchemazio.http.endpoint.openapi.JsonSchema.JsonSchemaRoot→zio.http.endpoint.openapi.JsonSchemazio.http.endpoint.openapi.JsonSchema.JsonSchemaRoot→zio.http.endpoint.openapi.SerializableJsonSchemazio.http.endpoint.openapi.JsonSchema.Null→zio.http.endpoint.openapi.JsonSchemazio.http.endpoint.openapi.JsonSchema.Null→zio.http.endpoint.openapi.SerializableJsonSchemazio.http.endpoint.openapi.JsonSchema.Number→zio.http.endpoint.openapi.JsonSchemazio.http.endpoint.openapi.JsonSchema.Number→zio.http.endpoint.openapi.SerializableJsonSchemazio.http.endpoint.openapi.JsonSchema.Object→zio.http.endpoint.openapi.JsonSchemazio.http.endpoint.openapi.JsonSchema.Object→zio.http.endpoint.openapi.SerializableJsonSchemazio.http.endpoint.openapi.JsonSchema.OneOfSchema→zio.http.endpoint.openapi.JsonSchema
- Direction
- endpoint.openapi.JsonSchema uses endpoint.openapi, so a change to endpoint.openapi can break endpoint.openapi.JsonSchema, while a change to endpoint.openapi.JsonSchema can't break endpoint.openapi.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→6 gen.openapi uses gen.scala.Code.Collection✕
- Connections
- 1 pair of types, where a type in gen.openapi uses a type in gen.scala.Code.Collection.
- The types involved
zio.http.gen.openapi.Config→zio.http.gen.scala.Code.Collection.Map
- Direction
- gen.openapi uses gen.scala.Code.Collection, so a change to gen.scala.Code.Collection can break gen.openapi, while a change to gen.openapi can't break gen.scala.Code.Collection.
- Position
- Below the diagonal: gen.openapi uses a module listed above it, which is the healthy direction.
22→19 gen.openapi uses gen.scala.Code✕
- Connections
- 1 pair of types, where a type in gen.openapi uses a type in gen.scala.Code.
- The types involved
zio.http.gen.openapi.EndpointGen→zio.http.gen.scala.Code.Files
- Direction
- gen.openapi uses gen.scala.Code, so a change to gen.scala.Code can break gen.openapi, while a change to gen.openapi can't break gen.scala.Code.
- Position
- Below the diagonal: gen.openapi uses a module listed above it, which is the healthy direction.
22→20 gen.openapi uses gen.scala.Code.CodecType✕
- Connections
- 2 pairs of types, where a type in gen.openapi uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.gen.openapi.Config→zio.http.gen.scala.Code.CodecType.Booleanzio.http.gen.openapi.Config→zio.http.gen.scala.Code.CodecType.String
- Direction
- gen.openapi uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break gen.openapi, while a change to gen.openapi can't break gen.scala.Code.CodecType.
- Position
- Below the diagonal: gen.openapi uses a module listed above it, which is the healthy direction.
23→6 template uses gen.scala.Code.Collection✕
- Connections
- 1 pair of types, where a type in template uses a type in gen.scala.Code.Collection.
- The types involved
zio.http.template.Element→zio.http.gen.scala.Code.Collection.Set
- Direction
- template uses gen.scala.Code.Collection, so a change to gen.scala.Code.Collection can break template, while a change to template can't break gen.scala.Code.Collection.
- Position
- Below the diagonal: template uses a module listed above it, which is the healthy direction.
23→11 template uses ErrorResponseConfig.ErrorFormat✕
- Connections
- 3 pairs of types, where a type in template uses a type in ErrorResponseConfig.ErrorFormat.
- The types involved
zio.http.template.Attributes→zio.http.ErrorResponseConfig.ErrorFormat.Htmlzio.http.template.Html→zio.http.ErrorResponseConfig.ErrorFormat.Htmlzio.http.template.Template→zio.http.ErrorResponseConfig.ErrorFormat.Html
- Direction
- template uses ErrorResponseConfig.ErrorFormat, so a change to ErrorResponseConfig.ErrorFormat can break template, while a change to template can't break ErrorResponseConfig.ErrorFormat.
- Position
- Below the diagonal: template uses a module listed above it, which is the healthy direction.
23→20 template uses gen.scala.Code.CodecType✕
- Connections
- 7 pairs of types, where a type in template uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.template.Attributes→zio.http.gen.scala.Code.CodecType.Stringzio.http.template.Dom→zio.http.gen.scala.Code.CodecType.Booleanzio.http.template.Dom→zio.http.gen.scala.Code.CodecType.Intzio.http.template.Element→zio.http.gen.scala.Code.CodecType.Booleanzio.http.template.EncodingState→zio.http.gen.scala.Code.CodecType.Stringzio.http.template.Html→zio.http.gen.scala.Code.CodecType.Intzio.http.template.IsAttributeValue→zio.http.gen.scala.Code.CodecType.String
- Direction
- template uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break template, while a change to template can't break gen.scala.Code.CodecType.
- Position
- Below the diagonal: template uses a module listed above it, which is the healthy direction.
24→1 template2.Dom uses gen.smithy.Smithy.SimpleShapes✕
- Connections
- 1 pair of types, where a type in template2.Dom uses a type in gen.smithy.Smithy.SimpleShapes.
- The types involved
zio.http.template2.Dom.PartialAttribute→zio.http.gen.smithy.Smithy.SimpleShapes.Double
- Direction
- template2.Dom uses gen.smithy.Smithy.SimpleShapes, so a change to gen.smithy.Smithy.SimpleShapes can break template2.Dom, while a change to template2.Dom can't break gen.smithy.Smithy.SimpleShapes.
- Position
- Below the diagonal: template2.Dom uses a module listed above it, which is the healthy direction.
24→3 template2.Dom uses URL✕
- Connections
- 1 pair of types, where a type in template2.Dom uses a type in URL.
- The types involved
zio.http.template2.Dom.Fragment→zio.http.URL.Fragment
- Direction
- template2.Dom uses URL, so a change to URL can break template2.Dom, while a change to template2.Dom can't break URL.
- Position
- Below the diagonal: template2.Dom uses a module listed above it, which is the healthy direction.
24→6 template2.Dom uses gen.scala.Code.Collection✕
- Connections
- 1 pair of types, where a type in template2.Dom uses a type in gen.scala.Code.Collection.
- The types involved
zio.http.template2.Dom.Element→zio.http.gen.scala.Code.Collection.Map
- Direction
- template2.Dom uses gen.scala.Code.Collection, so a change to gen.scala.Code.Collection can break template2.Dom, while a change to template2.Dom can't break gen.scala.Code.Collection.
- Position
- Below the diagonal: template2.Dom uses a module listed above it, which is the healthy direction.
24→20 template2.Dom uses gen.scala.Code.CodecType✕
- Connections
- 12 pairs of types, where a type in template2.Dom uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.template2.Dom.Attribute→zio.http.gen.scala.Code.CodecType.Stringzio.http.template2.Dom.BooleanAttribute→zio.http.gen.scala.Code.CodecType.Booleanzio.http.template2.Dom.BooleanAttribute→zio.http.gen.scala.Code.CodecType.Stringzio.http.template2.Dom.CompleteAttribute→zio.http.gen.scala.Code.CodecType.Stringzio.http.template2.Dom.Element→zio.http.gen.scala.Code.CodecType.Booleanzio.http.template2.Dom.Element→zio.http.gen.scala.Code.CodecType.Stringzio.http.template2.Dom.PartialAttribute→zio.http.gen.scala.Code.CodecType.Booleanzio.http.template2.Dom.PartialAttribute→zio.http.gen.scala.Code.CodecType.Intzio.http.template2.Dom.PartialAttribute→zio.http.gen.scala.Code.CodecType.Stringzio.http.template2.Dom.PartialMultiAttribute→zio.http.gen.scala.Code.CodecType.Stringzio.http.template2.Dom.RawHtml→zio.http.gen.scala.Code.CodecType.Stringzio.http.template2.Dom.Text→zio.http.gen.scala.Code.CodecType.String
- Direction
- template2.Dom uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break template2.Dom, while a change to template2.Dom can't break gen.scala.Code.CodecType.
- Position
- Below the diagonal: template2.Dom uses a module listed above it, which is the healthy direction.
24→23 template2.Dom uses template✕
- Connections
- 5 pairs of types, where a type in template2.Dom uses a type in template.
- The types involved
zio.http.template2.Dom.Element→zio.http.template.Domzio.http.template2.Dom.Empty→zio.http.template.Domzio.http.template2.Dom.Fragment→zio.http.template.Domzio.http.template2.Dom.RawHtml→zio.http.template.Domzio.http.template2.Dom.Text→zio.http.template.Dom
- Direction
- template2.Dom uses template, so a change to template can break template2.Dom, while a change to template2.Dom can't break template.
- Position
- Below the diagonal: template2.Dom uses a module listed above it, which is the healthy direction.
24→25 template2.Dom uses template2 part of a loop✕
- Connections
- 13 pairs of types, where a type in template2.Dom uses a type in template2.
- The types involved
zio.http.template2.Dom.Attribute→zio.http.template2.Modifierzio.http.template2.Dom.CompleteAttribute→zio.http.template2.CssSelectablezio.http.template2.Dom.CompleteAttribute→zio.http.template2.CssSelectorzio.http.template2.Dom.Element→zio.http.template2.CssSelectablezio.http.template2.Dom.Element→zio.http.template2.CssSelectorzio.http.template2.Dom.Element→zio.http.template2.Modifierzio.http.template2.Dom.Element→zio.http.template2.RenderStatezio.http.template2.Dom.Empty→zio.http.template2.RenderStatezio.http.template2.Dom.Fragment→zio.http.template2.RenderStatezio.http.template2.Dom.PartialAttribute→zio.http.template2.Jszio.http.template2.Dom.PartialMultiAttribute→zio.http.template2.AttributeSeparatorzio.http.template2.Dom.RawHtml→zio.http.template2.RenderStatezio.http.template2.Dom.Text→zio.http.template2.RenderState
- Direction
- template2.Dom uses template2, so a change to template2 can break template2.Dom, while a change to template2.Dom can't break template2.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→1 template2 uses gen.smithy.Smithy.SimpleShapes✕
- Connections
- 1 pair of types, where a type in template2 uses a type in gen.smithy.Smithy.SimpleShapes.
- The types involved
zio.http.template2.Dom→zio.http.gen.smithy.Smithy.SimpleShapes.List
- Direction
- template2 uses gen.smithy.Smithy.SimpleShapes, so a change to gen.smithy.Smithy.SimpleShapes can break template2, while a change to template2 can't break gen.smithy.Smithy.SimpleShapes.
- Position
- Below the diagonal: template2 uses a module listed above it, which is the healthy direction.
25→3 template2 uses URL✕
- Connections
- 1 pair of types, where a type in template2 uses a type in URL.
- The types involved
zio.http.template2.HtmlElements→zio.http.URL.Fragment
- Direction
- template2 uses URL, so a change to URL can break template2, while a change to template2 can't break URL.
- Position
- Below the diagonal: template2 uses a module listed above it, which is the healthy direction.
25→6 template2 uses gen.scala.Code.Collection✕
- Connections
- 1 pair of types, where a type in template2 uses a type in gen.scala.Code.Collection.
- The types involved
zio.http.template2.JsInterpolatorMacros→zio.http.gen.scala.Code.Collection.Seq
- Direction
- template2 uses gen.scala.Code.Collection, so a change to gen.scala.Code.Collection can break template2, while a change to template2 can't break gen.scala.Code.Collection.
- Position
- Below the diagonal: template2 uses a module listed above it, which is the healthy direction.
25→11 template2 uses ErrorResponseConfig.ErrorFormat✕
- Connections
- 1 pair of types, where a type in template2 uses a type in ErrorResponseConfig.ErrorFormat.
- The types involved
zio.http.template2.HtmlElements→zio.http.ErrorResponseConfig.ErrorFormat.Text
- Direction
- template2 uses ErrorResponseConfig.ErrorFormat, so a change to ErrorResponseConfig.ErrorFormat can break template2, while a change to template2 can't break ErrorResponseConfig.ErrorFormat.
- Position
- Below the diagonal: template2 uses a module listed above it, which is the healthy direction.
25→20 template2 uses gen.scala.Code.CodecType✕
- Connections
- 17 pairs of types, where a type in template2 uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.template2.AttributeSeparator→zio.http.gen.scala.Code.CodecType.Stringzio.http.template2.Css→zio.http.gen.scala.Code.CodecType.Stringzio.http.template2.CssInterpolatorMacros→zio.http.gen.scala.Code.CodecType.Booleanzio.http.template2.CssInterpolatorMacros→zio.http.gen.scala.Code.CodecType.Stringzio.http.template2.CssSelectable→zio.http.gen.scala.Code.CodecType.Intzio.http.template2.CssSelectable→zio.http.gen.scala.Code.CodecType.Stringzio.http.template2.CssSelector→zio.http.gen.scala.Code.CodecType.Stringzio.http.template2.Dom→zio.http.gen.scala.Code.CodecType.Booleanzio.http.template2.Dom→zio.http.gen.scala.Code.CodecType.Stringzio.http.template2.HtmlAttributes→zio.http.gen.scala.Code.CodecType.Stringzio.http.template2.HtmlElements→zio.http.gen.scala.Code.CodecType.Stringzio.http.template2.JSInterpolatorMacros→zio.http.gen.scala.Code.CodecType.Booleanzio.http.template2.JSInterpolatorMacros→zio.http.gen.scala.Code.CodecType.Stringzio.http.template2.Js→zio.http.gen.scala.Code.CodecType.Stringzio.http.template2.JsInterpolatorMacros→zio.http.gen.scala.Code.CodecType.Booleanzio.http.template2.JsInterpolatorMacros→zio.http.gen.scala.Code.CodecType.Stringzio.http.template2.RenderState→zio.http.gen.scala.Code.CodecType.String
- Direction
- template2 uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break template2, while a change to template2 can't break gen.scala.Code.CodecType.
- Position
- Below the diagonal: template2 uses a module listed above it, which is the healthy direction.
25→23 template2 uses template✕
- Connections
- 2 pairs of types, where a type in template2 uses a type in template.
- The types involved
zio.http.template2.Dom→zio.http.template.Domzio.http.template2.HtmlElements→zio.http.template.Dom
- Direction
- template2 uses template, so a change to template can break template2, while a change to template2 can't break template.
- Position
- Below the diagonal: template2 uses a module listed above it, which is the healthy direction.
25→24 template2 uses template2.Dom✕
- Connections
- 2 pairs of types, where a type in template2 uses a type in template2.Dom.
- The types involved
zio.http.template2.HtmlAttributes→zio.http.template2.Dom.PartialMultiAttributezio.http.template2.HtmlElements→zio.http.template2.Dom.RawHtml
- Direction
- template2 uses template2.Dom, so a change to template2.Dom can break template2, while a change to template2 can't break template2.Dom.
- Position
- Below the diagonal: template2 uses a module listed above it, which is the healthy direction.
25→30 template2 uses Header.AcceptLanguage part of a loop✕
- Connections
- 1 pair of types, where a type in template2 uses a type in Header.AcceptLanguage.
- The types involved
zio.http.template2.JsInterpolatorMacros→zio.http.Header.AcceptLanguage.Any
- Direction
- template2 uses Header.AcceptLanguage, so a change to Header.AcceptLanguage can break template2, while a change to template2 can't break Header.AcceptLanguage.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→20 datastar.Attributes uses gen.scala.Code.CodecType✕
- Connections
- 41 pairs of types, where a type in datastar.Attributes uses a type in gen.scala.Code.CodecType. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
zio.http.datastar.Attributes.BindModifier→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.Attributes.CaseModifier→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.Attributes.DataBind→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.Attributes.DataClass→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.Attributes.DataIndicatorAttr→zio.http.gen.scala.Code.CodecType.Booleanzio.http.datastar.Attributes.DataIndicatorAttr→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.Attributes.DataInit→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.Attributes.DataJsonSignals→zio.http.gen.scala.Code.CodecType.Booleanzio.http.datastar.Attributes.DataJsonSignals→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.Attributes.DataOn→zio.http.gen.scala.Code.CodecType.Booleanzio.http.datastar.Attributes.DataOn→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.Attributes.DataOnIntersect→zio.http.gen.scala.Code.CodecType.Booleanzio.http.datastar.Attributes.DataOnIntersect→zio.http.gen.scala.Code.CodecType.Intzio.http.datastar.Attributes.DataOnIntersect→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.Attributes.DataOnInterval→zio.http.gen.scala.Code.CodecType.Booleanzio.http.datastar.Attributes.DataOnInterval→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.Attributes.DataOnLoad→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.Attributes.DataOnSignalPatch→zio.http.gen.scala.Code.CodecType.Booleanzio.http.datastar.Attributes.DataOnSignalPatch→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.Attributes.DataRef→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.Attributes.DatastarAttribute→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.Attributes.EventModifier→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.Attributes.InitModifier→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.Attributes.IntersectModifier→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.Attributes.LoadModifier→zio.http.gen.scala.Code.CodecType.String
- Direction
- datastar.Attributes uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break datastar.Attributes, while a change to datastar.Attributes can't break gen.scala.Code.CodecType.
- Position
- Below the diagonal: datastar.Attributes uses a module listed above it, which is the healthy direction.
26→24 datastar.Attributes uses template2.Dom✕
- Connections
- 1 pair of types, where a type in datastar.Attributes uses a type in template2.Dom.
- The types involved
zio.http.datastar.Attributes.DataClass→zio.http.template2.Dom.CompleteAttribute
- Direction
- datastar.Attributes uses template2.Dom, so a change to template2.Dom can break datastar.Attributes, while a change to datastar.Attributes can't break template2.Dom.
- Position
- Below the diagonal: datastar.Attributes uses a module listed above it, which is the healthy direction.
26→25 datastar.Attributes uses template2✕
- Connections
- 12 pairs of types, where a type in datastar.Attributes uses a type in template2.
- The types involved
zio.http.datastar.Attributes.DataClass→zio.http.template2.Jszio.http.datastar.Attributes.DataInit→zio.http.template2.Jszio.http.datastar.Attributes.DataJsonSignals→zio.http.template2.Jszio.http.datastar.Attributes.DataOn→zio.http.template2.Jszio.http.datastar.Attributes.DataOnIntersect→zio.http.template2.Jszio.http.datastar.Attributes.DataOnInterval→zio.http.template2.Jszio.http.datastar.Attributes.DataOnLoad→zio.http.template2.Jszio.http.datastar.Attributes.DataOnSignalPatch→zio.http.template2.Jszio.http.datastar.Attributes.DatastarAttribute→zio.http.template2.Jszio.http.datastar.Attributes.PartialSignalsAttr→zio.http.template2.Jszio.http.datastar.Attributes.SignalAttr→zio.http.template2.Jszio.http.datastar.Attributes.SignalsAttr→zio.http.template2.Js
- Direction
- datastar.Attributes uses template2, so a change to template2 can break datastar.Attributes, while a change to datastar.Attributes can't break template2.
- Position
- Below the diagonal: datastar.Attributes uses a module listed above it, which is the healthy direction.
26→27 datastar.Attributes uses datastar.Attributes.OnIntervalModifier part of a loop✕
- Connections
- 7 pairs of types, where a type in datastar.Attributes uses a type in datastar.Attributes.OnIntervalModifier.
- The types involved
zio.http.datastar.Attributes.DataInit→zio.http.datastar.Attributes.OnIntervalModifier.Durationzio.http.datastar.Attributes.DataOn→zio.http.datastar.Attributes.OnIntervalModifier.Durationzio.http.datastar.Attributes.DataOnIntersect→zio.http.datastar.Attributes.OnIntervalModifier.Durationzio.http.datastar.Attributes.DataOnInterval→zio.http.datastar.Attributes.OnIntervalModifier.Durationzio.http.datastar.Attributes.DataOnLoad→zio.http.datastar.Attributes.OnIntervalModifier.Durationzio.http.datastar.Attributes.DataOnSignalPatch→zio.http.datastar.Attributes.OnIntervalModifier.Durationzio.http.datastar.Attributes.PartialDataOn→zio.http.datastar.Attributes.OnIntervalModifier.Duration
- Direction
- datastar.Attributes uses datastar.Attributes.OnIntervalModifier, so a change to datastar.Attributes.OnIntervalModifier can break datastar.Attributes, while a change to datastar.Attributes can't break datastar.Attributes.OnIntervalModifier.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→20 datastar.Attributes.OnIntervalModifier uses gen.scala.Code.CodecType✕
- Connections
- 5 pairs of types, where a type in datastar.Attributes.OnIntervalModifier uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.datastar.Attributes.OnIntervalModifier.And→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.Attributes.OnIntervalModifier.Duration→zio.http.gen.scala.Code.CodecType.Booleanzio.http.datastar.Attributes.OnIntervalModifier.Duration→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.Attributes.OnIntervalModifier.None→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.Attributes.OnIntervalModifier.ViewTransition→zio.http.gen.scala.Code.CodecType.String
- Direction
- datastar.Attributes.OnIntervalModifier uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break datastar.Attributes.OnIntervalModifier, while a change to datastar.Attributes.OnIntervalModifier can't break gen.scala.Code.CodecType.
- Position
- Below the diagonal: datastar.Attributes.OnIntervalModifier uses a module listed above it, which is the healthy direction.
27→26 datastar.Attributes.OnIntervalModifier uses datastar.Attributes✕
- Connections
- 4 pairs of types, where a type in datastar.Attributes.OnIntervalModifier uses a type in datastar.Attributes.
- The types involved
zio.http.datastar.Attributes.OnIntervalModifier.And→zio.http.datastar.Attributes.OnIntervalModifierzio.http.datastar.Attributes.OnIntervalModifier.Duration→zio.http.datastar.Attributes.OnIntervalModifierzio.http.datastar.Attributes.OnIntervalModifier.None→zio.http.datastar.Attributes.OnIntervalModifierzio.http.datastar.Attributes.OnIntervalModifier.ViewTransition→zio.http.datastar.Attributes.OnIntervalModifier
- Direction
- datastar.Attributes.OnIntervalModifier uses datastar.Attributes, so a change to datastar.Attributes can break datastar.Attributes.OnIntervalModifier, while a change to datastar.Attributes.OnIntervalModifier can't break datastar.Attributes.
- Position
- Below the diagonal: datastar.Attributes.OnIntervalModifier uses a module listed above it, which is the healthy direction.
28→4 Cookie uses endpoint.cli.HttpOptions✕
- Connections
- 1 pair of types, where a type in Cookie uses a type in endpoint.cli.HttpOptions.
- The types involved
zio.http.Cookie.Response→zio.http.endpoint.cli.HttpOptions.Path
- Direction
- Cookie uses endpoint.cli.HttpOptions, so a change to endpoint.cli.HttpOptions can break Cookie, while a change to Cookie can't break endpoint.cli.HttpOptions.
- Position
- Below the diagonal: Cookie uses a module listed above it, which is the healthy direction.
28→20 Cookie uses gen.scala.Code.CodecType✕
- Connections
- 4 pairs of types, where a type in Cookie uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.Cookie.Request→zio.http.gen.scala.Code.CodecType.Booleanzio.http.Cookie.Request→zio.http.gen.scala.Code.CodecType.Stringzio.http.Cookie.Response→zio.http.gen.scala.Code.CodecType.Booleanzio.http.Cookie.Response→zio.http.gen.scala.Code.CodecType.String
- Direction
- Cookie uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break Cookie, while a change to Cookie can't break gen.scala.Code.CodecType.
- Position
- Below the diagonal: Cookie uses a module listed above it, which is the healthy direction.
28→27 Cookie uses datastar.Attributes.OnIntervalModifier✕
- Connections
- 1 pair of types, where a type in Cookie uses a type in datastar.Attributes.OnIntervalModifier.
- The types involved
zio.http.Cookie.Response→zio.http.datastar.Attributes.OnIntervalModifier.Duration
- Direction
- Cookie uses datastar.Attributes.OnIntervalModifier, so a change to datastar.Attributes.OnIntervalModifier can break Cookie, while a change to Cookie can't break datastar.Attributes.OnIntervalModifier.
- Position
- Below the diagonal: Cookie uses a module listed above it, which is the healthy direction.
28→39 Cookie uses zio.http part of a loop✕
- Connections
- 2 pairs of types, where a type in Cookie uses a type in zio.http.
- The types involved
zio.http.Cookie.Request→zio.http.Cookiezio.http.Cookie.Response→zio.http.Cookie
- Direction
- Cookie uses zio.http, so a change to zio.http can break Cookie, while a change to Cookie can't break zio.http.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→1 Header uses gen.smithy.Smithy.SimpleShapes✕
- Connections
- 2 pairs of types, where a type in Header uses a type in gen.smithy.Smithy.SimpleShapes.
- The types involved
zio.http.Header.Forwarded→zio.http.gen.smithy.Smithy.SimpleShapes.Listzio.http.Header.UserAgent→zio.http.gen.smithy.Smithy.SimpleShapes.List
- Direction
- Header uses gen.smithy.Smithy.SimpleShapes, so a change to gen.smithy.Smithy.SimpleShapes can break Header, while a change to Header can't break gen.smithy.Smithy.SimpleShapes.
- Position
- Below the diagonal: Header uses a module listed above it, which is the healthy direction.
29→2 Header uses Header.Vary✕
- Connections
- 2 pairs of types, where a type in Header uses a type in Header.Vary.
- The types involved
zio.http.Header.HeaderType→zio.http.Header.Vary.Headerszio.http.Header.HeaderTypeBase→zio.http.Header.Vary.Headers
- Direction
- Header uses Header.Vary, so a change to Header.Vary can break Header, while a change to Header can't break Header.Vary.
- Position
- Below the diagonal: Header uses a module listed above it, which is the healthy direction.
29→4 Header uses endpoint.cli.HttpOptions✕
- Connections
- 78 pairs of types, where a type in Header uses a type in endpoint.cli.HttpOptions. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
zio.http.Header.Accept→zio.http.endpoint.cli.HttpOptions.Headerzio.http.Header.AcceptEncoding→zio.http.endpoint.cli.HttpOptions.Headerzio.http.Header.AcceptLanguage→zio.http.endpoint.cli.HttpOptions.Headerzio.http.Header.AcceptPatch→zio.http.endpoint.cli.HttpOptions.Headerzio.http.Header.AcceptRanges→zio.http.endpoint.cli.HttpOptions.Headerzio.http.Header.AccessControlAllowCredentials→zio.http.endpoint.cli.HttpOptions.Headerzio.http.Header.AccessControlAllowHeaders→zio.http.endpoint.cli.HttpOptions.Headerzio.http.Header.AccessControlAllowMethods→zio.http.endpoint.cli.HttpOptions.Headerzio.http.Header.AccessControlAllowOrigin→zio.http.endpoint.cli.HttpOptions.Headerzio.http.Header.AccessControlExposeHeaders→zio.http.endpoint.cli.HttpOptions.Headerzio.http.Header.AccessControlMaxAge→zio.http.endpoint.cli.HttpOptions.Headerzio.http.Header.AccessControlRequestHeaders→zio.http.endpoint.cli.HttpOptions.Headerzio.http.Header.AccessControlRequestMethod→zio.http.endpoint.cli.HttpOptions.Headerzio.http.Header.Age→zio.http.endpoint.cli.HttpOptions.Headerzio.http.Header.Allow→zio.http.endpoint.cli.HttpOptions.Headerzio.http.Header.Authorization→zio.http.endpoint.cli.HttpOptions.Headerzio.http.Header.CacheControl→zio.http.endpoint.cli.HttpOptions.Headerzio.http.Header.ClearSiteData→zio.http.endpoint.cli.HttpOptions.Headerzio.http.Header.Connection→zio.http.endpoint.cli.HttpOptions.Headerzio.http.Header.ContentBase→zio.http.endpoint.cli.HttpOptions.Headerzio.http.Header.ContentDisposition→zio.http.endpoint.cli.HttpOptions.Headerzio.http.Header.ContentEncoding→zio.http.endpoint.cli.HttpOptions.Headerzio.http.Header.ContentLanguage→zio.http.endpoint.cli.HttpOptions.Headerzio.http.Header.ContentLength→zio.http.endpoint.cli.HttpOptions.Headerzio.http.Header.ContentLocation→zio.http.endpoint.cli.HttpOptions.Header
- Direction
- Header uses endpoint.cli.HttpOptions, so a change to endpoint.cli.HttpOptions can break Header, while a change to Header can't break endpoint.cli.HttpOptions.
- Position
- Below the diagonal: Header uses a module listed above it, which is the healthy direction.
29→5 Header uses gen.grpc.Protobuf✕
- Connections
- 3 pairs of types, where a type in Header uses a type in gen.grpc.Protobuf.
- The types involved
zio.http.Header.AccessControlAllowMethods→zio.http.gen.grpc.Protobuf.Methodzio.http.Header.AccessControlRequestMethod→zio.http.gen.grpc.Protobuf.Methodzio.http.Header.Allow→zio.http.gen.grpc.Protobuf.Method
- Direction
- Header uses gen.grpc.Protobuf, so a change to gen.grpc.Protobuf can break Header, while a change to Header can't break gen.grpc.Protobuf.
- Position
- Below the diagonal: Header uses a module listed above it, which is the healthy direction.
29→6 Header uses gen.scala.Code.Collection✕
- Connections
- 1 pair of types, where a type in Header uses a type in gen.scala.Code.Collection.
- The types involved
zio.http.Header.Link→zio.http.gen.scala.Code.Collection.Map
- Direction
- Header uses gen.scala.Code.Collection, so a change to gen.scala.Code.Collection can break Header, while a change to Header can't break gen.scala.Code.Collection.
- Position
- Below the diagonal: Header uses a module listed above it, which is the healthy direction.
29→10 Header uses gen.smithy.SmithyTrait✕
- Connections
- 3 pairs of types, where a type in Header uses a type in gen.smithy.SmithyTrait.
- The types involved
zio.http.Header.AcceptPatch→zio.http.gen.smithy.SmithyTrait.MediaTypezio.http.Header.ContentType→zio.http.gen.smithy.SmithyTrait.MediaTypezio.http.Header.Range→zio.http.gen.smithy.SmithyTrait.Range
- Direction
- Header uses gen.smithy.SmithyTrait, so a change to gen.smithy.SmithyTrait can break Header, while a change to Header can't break gen.smithy.SmithyTrait.
- Position
- Below the diagonal: Header uses a module listed above it, which is the healthy direction.
29→18 Header uses endpoint.cli.Retriever✕
- Connections
- 5 pairs of types, where a type in Header uses a type in endpoint.cli.Retriever.
- The types involved
zio.http.Header.Link→zio.http.endpoint.cli.Retriever.URLzio.http.Header.Location→zio.http.endpoint.cli.Retriever.URLzio.http.Header.Referer→zio.http.endpoint.cli.Retriever.URLzio.http.Header.SecWebSocketLocation→zio.http.endpoint.cli.Retriever.URLzio.http.Header.SecWebSocketOrigin→zio.http.endpoint.cli.Retriever.URL
- Direction
- Header uses endpoint.cli.Retriever, so a change to endpoint.cli.Retriever can break Header, while a change to Header can't break endpoint.cli.Retriever.
- Position
- Below the diagonal: Header uses a module listed above it, which is the healthy direction.
29→20 Header uses gen.scala.Code.CodecType✕
- Connections
- 38 pairs of types, where a type in Header uses a type in gen.scala.Code.CodecType. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
zio.http.Header.AcceptEncoding→zio.http.gen.scala.Code.CodecType.Stringzio.http.Header.AcceptRanges→zio.http.gen.scala.Code.CodecType.Stringzio.http.Header.AccessControlAllowMethods→zio.http.gen.scala.Code.CodecType.Booleanzio.http.Header.AccessControlRequestHeaders→zio.http.gen.scala.Code.CodecType.Stringzio.http.Header.AuthenticationScheme→zio.http.gen.scala.Code.CodecType.Stringzio.http.Header.CacheControl→zio.http.gen.scala.Code.CodecType.Stringzio.http.Header.Connection→zio.http.gen.scala.Code.CodecType.Stringzio.http.Header.ContentEncoding→zio.http.gen.scala.Code.CodecType.Stringzio.http.Header.ContentLength→zio.http.gen.scala.Code.CodecType.Longzio.http.Header.ContentMd5→zio.http.gen.scala.Code.CodecType.Stringzio.http.Header.ContentRange→zio.http.gen.scala.Code.CodecType.Intzio.http.Header.ContentRange→zio.http.gen.scala.Code.CodecType.Stringzio.http.Header.ContentType→zio.http.gen.scala.Code.CodecType.Stringzio.http.Header.Custom→zio.http.gen.scala.Code.CodecType.Booleanzio.http.Header.Custom→zio.http.gen.scala.Code.CodecType.Intzio.http.Header.Custom→zio.http.gen.scala.Code.CodecType.Stringzio.http.Header.Expect→zio.http.gen.scala.Code.CodecType.Stringzio.http.Header.Forwarded→zio.http.gen.scala.Code.CodecType.Stringzio.http.Header.From→zio.http.gen.scala.Code.CodecType.Stringzio.http.Header.HeaderType→zio.http.gen.scala.Code.CodecType.Stringzio.http.Header.HeaderTypeBase→zio.http.gen.scala.Code.CodecType.Stringzio.http.Header.Host→zio.http.gen.scala.Code.CodecType.Intzio.http.Header.Host→zio.http.gen.scala.Code.CodecType.Stringzio.http.Header.Link→zio.http.gen.scala.Code.CodecType.Stringzio.http.Header.MaxForwards→zio.http.gen.scala.Code.CodecType.Int
- Direction
- Header uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break Header, while a change to Header can't break gen.scala.Code.CodecType.
- Position
- Below the diagonal: Header uses a module listed above it, which is the healthy direction.
29→27 Header uses datastar.Attributes.OnIntervalModifier✕
- Connections
- 2 pairs of types, where a type in Header uses a type in datastar.Attributes.OnIntervalModifier.
- The types involved
zio.http.Header.AccessControlMaxAge→zio.http.datastar.Attributes.OnIntervalModifier.Durationzio.http.Header.Age→zio.http.datastar.Attributes.OnIntervalModifier.Duration
- Direction
- Header uses datastar.Attributes.OnIntervalModifier, so a change to datastar.Attributes.OnIntervalModifier can break Header, while a change to Header can't break datastar.Attributes.OnIntervalModifier.
- Position
- Below the diagonal: Header uses a module listed above it, which is the healthy direction.
29→28 Header uses Cookie✕
- Connections
- 2 pairs of types, where a type in Header uses a type in Cookie.
- The types involved
zio.http.Header.Cookie→zio.http.Cookie.Requestzio.http.Header.SetCookie→zio.http.Cookie.Response
- Direction
- Header uses Cookie, so a change to Cookie can break Header, while a change to Header can't break Cookie.
- Position
- Below the diagonal: Header uses a module listed above it, which is the healthy direction.
29→30 Header uses Header.AcceptLanguage part of a loop✕
- Connections
- 1 pair of types, where a type in Header uses a type in Header.AcceptLanguage.
- The types involved
zio.http.Header.Custom→zio.http.Header.AcceptLanguage.Any
- Direction
- Header uses Header.AcceptLanguage, so a change to Header.AcceptLanguage can break Header, while a change to Header can't break Header.AcceptLanguage.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→31 Header uses Body part of a loop✕
- Connections
- 1 pair of types, where a type in Header uses a type in Body.
- The types involved
zio.http.Header.ContentType→zio.http.Body.ContentType
- Direction
- Header uses Body, so a change to Body can break Header, while a change to Header can't break Body.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→39 Header uses zio.http part of a loop✕
- Connections
- 2 pairs of types, where a type in Header uses a type in zio.http.
- The types involved
zio.http.Header.ContentType→zio.http.Boundaryzio.http.Header.Cookie→zio.http.Cookie
- Direction
- Header uses zio.http, so a change to zio.http can break Header, while a change to Header can't break zio.http.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→1 Header.AcceptLanguage uses gen.smithy.Smithy.SimpleShapes✕
- Connections
- 1 pair of types, where a type in Header.AcceptLanguage uses a type in gen.smithy.Smithy.SimpleShapes.
- The types involved
zio.http.Header.AcceptLanguage.Single→zio.http.gen.smithy.Smithy.SimpleShapes.Double
- Direction
- Header.AcceptLanguage uses gen.smithy.Smithy.SimpleShapes, so a change to gen.smithy.Smithy.SimpleShapes can break Header.AcceptLanguage, while a change to Header.AcceptLanguage can't break gen.smithy.Smithy.SimpleShapes.
- Position
- Below the diagonal: Header.AcceptLanguage uses a module listed above it, which is the healthy direction.
30→20 Header.AcceptLanguage uses gen.scala.Code.CodecType✕
- Connections
- 1 pair of types, where a type in Header.AcceptLanguage uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.Header.AcceptLanguage.Single→zio.http.gen.scala.Code.CodecType.String
- Direction
- Header.AcceptLanguage uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break Header.AcceptLanguage, while a change to Header.AcceptLanguage can't break gen.scala.Code.CodecType.
- Position
- Below the diagonal: Header.AcceptLanguage uses a module listed above it, which is the healthy direction.
30→29 Header.AcceptLanguage uses Header✕
- Connections
- 3 pairs of types, where a type in Header.AcceptLanguage uses a type in Header.
- The types involved
zio.http.Header.AcceptLanguage.Any→zio.http.Header.AcceptLanguagezio.http.Header.AcceptLanguage.Multiple→zio.http.Header.AcceptLanguagezio.http.Header.AcceptLanguage.Single→zio.http.Header.AcceptLanguage
- Direction
- Header.AcceptLanguage uses Header, so a change to Header can break Header.AcceptLanguage, while a change to Header.AcceptLanguage can't break Header.
- Position
- Below the diagonal: Header.AcceptLanguage uses a module listed above it, which is the healthy direction.
31→1 Body uses gen.smithy.Smithy.SimpleShapes✕
- Connections
- 10 pairs of types, where a type in Body uses a type in gen.smithy.Smithy.SimpleShapes.
- The types involved
zio.http.Body.ArrayBody→zio.http.gen.smithy.Smithy.SimpleShapes.Bytezio.http.Body.ByteRange→zio.http.gen.smithy.Smithy.SimpleShapes.Bytezio.http.Body.ChunkBody→zio.http.gen.smithy.Smithy.SimpleShapes.Bytezio.http.Body.EmptyBody→zio.http.gen.smithy.Smithy.SimpleShapes.Bytezio.http.Body.ErrorBody→zio.http.gen.smithy.Smithy.SimpleShapes.Bytezio.http.Body.FileBody→zio.http.gen.smithy.Smithy.SimpleShapes.Bytezio.http.Body.StreamBody→zio.http.gen.smithy.Smithy.SimpleShapes.Bytezio.http.Body.StringBody→zio.http.gen.smithy.Smithy.SimpleShapes.Bytezio.http.Body.UnsafeBytes→zio.http.gen.smithy.Smithy.SimpleShapes.Bytezio.http.Body.WebsocketBody→zio.http.gen.smithy.Smithy.SimpleShapes.Byte
- Direction
- Body uses gen.smithy.Smithy.SimpleShapes, so a change to gen.smithy.Smithy.SimpleShapes can break Body, while a change to Body can't break gen.smithy.Smithy.SimpleShapes.
- Position
- Below the diagonal: Body uses a module listed above it, which is the healthy direction.
31→4 Body uses endpoint.cli.HttpOptions✕
- Connections
- 9 pairs of types, where a type in Body uses a type in endpoint.cli.HttpOptions.
- The types involved
zio.http.Body.ArrayBody→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.Body.ChunkBody→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.Body.EmptyBody→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.Body.ErrorBody→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.Body.FileBody→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.Body.StreamBody→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.Body.StringBody→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.Body.UnsafeBytes→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.Body.WebsocketBody→zio.http.endpoint.cli.HttpOptions.Body
- Direction
- Body uses endpoint.cli.HttpOptions, so a change to endpoint.cli.HttpOptions can break Body, while a change to Body can't break endpoint.cli.HttpOptions.
- Position
- Below the diagonal: Body uses a module listed above it, which is the healthy direction.
31→10 Body uses gen.smithy.SmithyTrait✕
- Connections
- 2 pairs of types, where a type in Body uses a type in gen.smithy.SmithyTrait.
- The types involved
zio.http.Body.ByteRange→zio.http.gen.smithy.SmithyTrait.MediaTypezio.http.Body.ContentType→zio.http.gen.smithy.SmithyTrait.MediaType
- Direction
- Body uses gen.smithy.SmithyTrait, so a change to gen.smithy.SmithyTrait can break Body, while a change to Body can't break gen.smithy.SmithyTrait.
- Position
- Below the diagonal: Body uses a module listed above it, which is the healthy direction.
31→18 Body uses endpoint.cli.Retriever✕
- Connections
- 1 pair of types, where a type in Body uses a type in endpoint.cli.Retriever.
- The types involved
zio.http.Body.FileBody→zio.http.endpoint.cli.Retriever.File
- Direction
- Body uses endpoint.cli.Retriever, so a change to endpoint.cli.Retriever can break Body, while a change to Body can't break endpoint.cli.Retriever.
- Position
- Below the diagonal: Body uses a module listed above it, which is the healthy direction.
31→20 Body uses gen.scala.Code.CodecType✕
- Connections
- 23 pairs of types, where a type in Body uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.Body.ArrayBody→zio.http.gen.scala.Code.CodecType.Booleanzio.http.Body.ArrayBody→zio.http.gen.scala.Code.CodecType.Longzio.http.Body.ArrayBody→zio.http.gen.scala.Code.CodecType.Stringzio.http.Body.ByteRange→zio.http.gen.scala.Code.CodecType.Longzio.http.Body.ChunkBody→zio.http.gen.scala.Code.CodecType.Booleanzio.http.Body.ChunkBody→zio.http.gen.scala.Code.CodecType.Longzio.http.Body.ChunkBody→zio.http.gen.scala.Code.CodecType.Stringzio.http.Body.EmptyBody→zio.http.gen.scala.Code.CodecType.Booleanzio.http.Body.EmptyBody→zio.http.gen.scala.Code.CodecType.Longzio.http.Body.EmptyBody→zio.http.gen.scala.Code.CodecType.Stringzio.http.Body.ErrorBody→zio.http.gen.scala.Code.CodecType.Booleanzio.http.Body.ErrorBody→zio.http.gen.scala.Code.CodecType.Longzio.http.Body.ErrorBody→zio.http.gen.scala.Code.CodecType.Stringzio.http.Body.FileBody→zio.http.gen.scala.Code.CodecType.Booleanzio.http.Body.FileBody→zio.http.gen.scala.Code.CodecType.Intzio.http.Body.FileBody→zio.http.gen.scala.Code.CodecType.Longzio.http.Body.StreamBody→zio.http.gen.scala.Code.CodecType.Booleanzio.http.Body.StreamBody→zio.http.gen.scala.Code.CodecType.Longzio.http.Body.StringBody→zio.http.gen.scala.Code.CodecType.Booleanzio.http.Body.StringBody→zio.http.gen.scala.Code.CodecType.Longzio.http.Body.StringBody→zio.http.gen.scala.Code.CodecType.Stringzio.http.Body.WebsocketBody→zio.http.gen.scala.Code.CodecType.Booleanzio.http.Body.WebsocketBody→zio.http.gen.scala.Code.CodecType.Long
- Direction
- Body uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break Body, while a change to Body can't break gen.scala.Code.CodecType.
- Position
- Below the diagonal: Body uses a module listed above it, which is the healthy direction.
31→30 Body uses Header.AcceptLanguage✕
- Connections
- 9 pairs of types, where a type in Body uses a type in Header.AcceptLanguage.
- The types involved
zio.http.Body.ArrayBody→zio.http.Header.AcceptLanguage.Anyzio.http.Body.ByteRange→zio.http.Header.AcceptLanguage.Anyzio.http.Body.ChunkBody→zio.http.Header.AcceptLanguage.Anyzio.http.Body.EmptyBody→zio.http.Header.AcceptLanguage.Anyzio.http.Body.ErrorBody→zio.http.Header.AcceptLanguage.Anyzio.http.Body.FileBody→zio.http.Header.AcceptLanguage.Anyzio.http.Body.StreamBody→zio.http.Header.AcceptLanguage.Anyzio.http.Body.StringBody→zio.http.Header.AcceptLanguage.Anyzio.http.Body.WebsocketBody→zio.http.Header.AcceptLanguage.Any
- Direction
- Body uses Header.AcceptLanguage, so a change to Header.AcceptLanguage can break Body, while a change to Body can't break Header.AcceptLanguage.
- Position
- Below the diagonal: Body uses a module listed above it, which is the healthy direction.
31→39 Body uses zio.http part of a loop✕
- Connections
- 2 pairs of types, where a type in Body uses a type in zio.http.
- The types involved
zio.http.Body.ContentType→zio.http.Boundaryzio.http.Body.WebsocketBody→zio.http.WebSocketApp
- Direction
- Body uses zio.http, so a change to zio.http can break Body, while a change to Body can't break zio.http.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→2 ZClient uses Header.Vary✕
- Connections
- 2 pairs of types, where a type in ZClient uses a type in Header.Vary.
- The types involved
zio.http.ZClient.Driver→zio.http.Header.Vary.Headerszio.http.ZClient.DriverLive→zio.http.Header.Vary.Headers
- Direction
- ZClient uses Header.Vary, so a change to Header.Vary can break ZClient, while a change to ZClient can't break Header.Vary.
- Position
- Below the diagonal: ZClient uses a module listed above it, which is the healthy direction.
32→3 ZClient uses URL✕
- Connections
- 3 pairs of types, where a type in ZClient uses a type in URL.
- The types involved
zio.http.ZClient.BodyDecoder→zio.http.URL.Errzio.http.ZClient.BodyEncoder→zio.http.URL.Errzio.http.ZClient.Driver→zio.http.URL.Err
- Direction
- ZClient uses URL, so a change to URL can break ZClient, while a change to ZClient can't break URL.
- Position
- Below the diagonal: ZClient uses a module listed above it, which is the healthy direction.
32→4 ZClient uses endpoint.cli.HttpOptions✕
- Connections
- 3 pairs of types, where a type in ZClient uses a type in endpoint.cli.HttpOptions.
- The types involved
zio.http.ZClient.BodyEncoder→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.ZClient.Driver→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.ZClient.DriverLive→zio.http.endpoint.cli.HttpOptions.Body
- Direction
- ZClient uses endpoint.cli.HttpOptions, so a change to endpoint.cli.HttpOptions can break ZClient, while a change to ZClient can't break endpoint.cli.HttpOptions.
- Position
- Below the diagonal: ZClient uses a module listed above it, which is the healthy direction.
32→5 ZClient uses gen.grpc.Protobuf✕
- Connections
- 2 pairs of types, where a type in ZClient uses a type in gen.grpc.Protobuf.
- The types involved
zio.http.ZClient.Driver→zio.http.gen.grpc.Protobuf.Methodzio.http.ZClient.DriverLive→zio.http.gen.grpc.Protobuf.Method
- Direction
- ZClient uses gen.grpc.Protobuf, so a change to gen.grpc.Protobuf can break ZClient, while a change to ZClient can't break gen.grpc.Protobuf.
- Position
- Below the diagonal: ZClient uses a module listed above it, which is the healthy direction.
32→18 ZClient uses endpoint.cli.Retriever✕
- Connections
- 2 pairs of types, where a type in ZClient uses a type in endpoint.cli.Retriever.
- The types involved
zio.http.ZClient.Driver→zio.http.endpoint.cli.Retriever.URLzio.http.ZClient.DriverLive→zio.http.endpoint.cli.Retriever.URL
- Direction
- ZClient uses endpoint.cli.Retriever, so a change to endpoint.cli.Retriever can break ZClient, while a change to ZClient can't break endpoint.cli.Retriever.
- Position
- Below the diagonal: ZClient uses a module listed above it, which is the healthy direction.
32→20 ZClient uses gen.scala.Code.CodecType✕
- Connections
- 2 pairs of types, where a type in ZClient uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.ZClient.Config→zio.http.gen.scala.Code.CodecType.Booleanzio.http.ZClient.Config→zio.http.gen.scala.Code.CodecType.Int
- Direction
- ZClient uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break ZClient, while a change to ZClient can't break gen.scala.Code.CodecType.
- Position
- Below the diagonal: ZClient uses a module listed above it, which is the healthy direction.
32→22 ZClient uses gen.openapi✕
- Connections
- 2 pairs of types, where a type in ZClient uses a type in gen.openapi.
- The types involved
zio.http.ZClient.Config→zio.http.gen.openapi.Configzio.http.ZClient.DriverLive→zio.http.gen.openapi.Config
- Direction
- ZClient uses gen.openapi, so a change to gen.openapi can break ZClient, while a change to ZClient can't break gen.openapi.
- Position
- Below the diagonal: ZClient uses a module listed above it, which is the healthy direction.
32→27 ZClient uses datastar.Attributes.OnIntervalModifier✕
- Connections
- 1 pair of types, where a type in ZClient uses a type in datastar.Attributes.OnIntervalModifier.
- The types involved
zio.http.ZClient.Config→zio.http.datastar.Attributes.OnIntervalModifier.Duration
- Direction
- ZClient uses datastar.Attributes.OnIntervalModifier, so a change to datastar.Attributes.OnIntervalModifier can break ZClient, while a change to ZClient can't break datastar.Attributes.OnIntervalModifier.
- Position
- Below the diagonal: ZClient uses a module listed above it, which is the healthy direction.
32→28 ZClient uses Cookie✕
- Connections
- 5 pairs of types, where a type in ZClient uses a type in Cookie.
- The types involved
zio.http.ZClient.BodyDecoder→zio.http.Cookie.Responsezio.http.ZClient.Driver→zio.http.Cookie.Requestzio.http.ZClient.Driver→zio.http.Cookie.Responsezio.http.ZClient.DriverLive→zio.http.Cookie.Requestzio.http.ZClient.DriverLive→zio.http.Cookie.Response
- Direction
- ZClient uses Cookie, so a change to Cookie can break ZClient, while a change to ZClient can't break Cookie.
- Position
- Below the diagonal: ZClient uses a module listed above it, which is the healthy direction.
32→29 ZClient uses Header✕
- Connections
- 1 pair of types, where a type in ZClient uses a type in Header.
- The types involved
zio.http.ZClient.DriverLive→zio.http.Header.Connection
- Direction
- ZClient uses Header, so a change to Header can break ZClient, while a change to ZClient can't break Header.
- Position
- Below the diagonal: ZClient uses a module listed above it, which is the healthy direction.
32→30 ZClient uses Header.AcceptLanguage✕
- Connections
- 1 pair of types, where a type in ZClient uses a type in Header.AcceptLanguage.
- The types involved
zio.http.ZClient.Driver→zio.http.Header.AcceptLanguage.Any
- Direction
- ZClient uses Header.AcceptLanguage, so a change to Header.AcceptLanguage can break ZClient, while a change to ZClient can't break Header.AcceptLanguage.
- Position
- Below the diagonal: ZClient uses a module listed above it, which is the healthy direction.
32→39 ZClient uses zio.http part of a loop✕
- Connections
- 15 pairs of types, where a type in ZClient uses a type in zio.http.
- The types involved
zio.http.ZClient.Config→zio.http.ClientSSLConfigzio.http.ZClient.Config→zio.http.ConnectionPoolConfigzio.http.ZClient.Config→zio.http.Decompressionzio.http.ZClient.Config→zio.http.Proxyzio.http.ZClient.Config→zio.http.WebSocketConfigzio.http.ZClient.Driver→zio.http.ClientSSLConfigzio.http.ZClient.Driver→zio.http.Driverzio.http.ZClient.Driver→zio.http.Proxyzio.http.ZClient.Driver→zio.http.WebSocketAppzio.http.ZClient.DriverLive→zio.http.ClientDriverzio.http.ZClient.DriverLive→zio.http.ClientSSLConfigzio.http.ZClient.DriverLive→zio.http.ConnectionPoolzio.http.ZClient.DriverLive→zio.http.Driverzio.http.ZClient.DriverLive→zio.http.Proxyzio.http.ZClient.DriverLive→zio.http.WebSocketApp
- Direction
- ZClient uses zio.http, so a change to zio.http can break ZClient, while a change to ZClient can't break zio.http.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→6 datastar uses gen.scala.Code.Collection✕
- Connections
- 2 pairs of types, where a type in datastar uses a type in gen.scala.Code.Collection.
- The types involved
zio.http.datastar.DatastarPackageBase→zio.http.gen.scala.Code.Collection.Seqzio.http.datastar.ExecuteScriptOptions→zio.http.gen.scala.Code.Collection.Seq
- Direction
- datastar uses gen.scala.Code.Collection, so a change to gen.scala.Code.Collection can break datastar, while a change to datastar can't break gen.scala.Code.Collection.
- Position
- Below the diagonal: datastar uses a module listed above it, which is the healthy direction.
33→7 datastar uses gen.scala.Code.ScalaType✕
- Connections
- 2 pairs of types, where a type in datastar uses a type in gen.scala.Code.ScalaType.
- The types involved
zio.http.datastar.DatastarPackageBase→zio.http.gen.scala.Code.ScalaType.Unitzio.http.datastar.ServerSentEventGenerator→zio.http.gen.scala.Code.ScalaType.Unit
- Direction
- datastar uses gen.scala.Code.ScalaType, so a change to gen.scala.Code.ScalaType can break datastar, while a change to datastar can't break gen.scala.Code.ScalaType.
- Position
- Below the diagonal: datastar uses a module listed above it, which is the healthy direction.
33→20 datastar uses gen.scala.Code.CodecType✕
- Connections
- 16 pairs of types, where a type in datastar uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.datastar.Attributes→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.Datastar→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.DatastarEvent→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.DatastarPackageBase→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.DispatchEventOptions→zio.http.gen.scala.Code.CodecType.Booleanzio.http.datastar.DispatchEventOptions→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.ElementPatchMode→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.EventType→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.ExecuteScriptOptions→zio.http.gen.scala.Code.CodecType.Booleanzio.http.datastar.ExecuteScriptOptions→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.PatchElementOptions→zio.http.gen.scala.Code.CodecType.Booleanzio.http.datastar.PatchElementOptions→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.PatchSignalOptions→zio.http.gen.scala.Code.CodecType.Booleanzio.http.datastar.PatchSignalOptions→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.ServerSentEventGenerator→zio.http.gen.scala.Code.CodecType.Stringzio.http.datastar.aliased→zio.http.gen.scala.Code.CodecType.String
- Direction
- datastar uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break datastar, while a change to datastar can't break gen.scala.Code.CodecType.
- Position
- Below the diagonal: datastar uses a module listed above it, which is the healthy direction.
33→23 datastar uses template✕
- Connections
- 3 pairs of types, where a type in datastar uses a type in template.
- The types involved
zio.http.datastar.Attributes→zio.http.template.Domzio.http.datastar.DatastarPackageBase→zio.http.template.Domzio.http.datastar.ServerSentEventGenerator→zio.http.template.Dom
- Direction
- datastar uses template, so a change to template can break datastar, while a change to datastar can't break template.
- Position
- Below the diagonal: datastar uses a module listed above it, which is the healthy direction.
33→24 datastar uses template2.Dom✕
- Connections
- 1 pair of types, where a type in datastar uses a type in template2.Dom.
- The types involved
zio.http.datastar.Attributes→zio.http.template2.Dom.PartialMultiAttribute
- Direction
- datastar uses template2.Dom, so a change to template2.Dom can break datastar, while a change to datastar can't break template2.Dom.
- Position
- Below the diagonal: datastar uses a module listed above it, which is the healthy direction.
33→25 datastar uses template2✕
- Connections
- 3 pairs of types, where a type in datastar uses a type in template2.
- The types involved
zio.http.datastar.DispatchEventOptions→zio.http.template2.CssSelectorzio.http.datastar.PatchElementOptions→zio.http.template2.CssSelectorzio.http.datastar.ServerSentEventGenerator→zio.http.template2.Js
- Direction
- datastar uses template2, so a change to template2 can break datastar, while a change to datastar can't break template2.
- Position
- Below the diagonal: datastar uses a module listed above it, which is the healthy direction.
33→26 datastar uses datastar.Attributes✕
- Connections
- 15 pairs of types, where a type in datastar uses a type in datastar.Attributes.
- The types involved
zio.http.datastar.Attributes→zio.http.datastar.Attributes.CaseModifierzio.http.datastar.Attributes→zio.http.datastar.Attributes.DataClasszio.http.datastar.Attributes→zio.http.datastar.Attributes.DataInitzio.http.datastar.Attributes→zio.http.datastar.Attributes.DataJsonSignalszio.http.datastar.Attributes→zio.http.datastar.Attributes.DataOnIntersectzio.http.datastar.Attributes→zio.http.datastar.Attributes.DataOnIntervalzio.http.datastar.Attributes→zio.http.datastar.Attributes.DataOnLoadzio.http.datastar.Attributes→zio.http.datastar.Attributes.DataOnSignalPatchzio.http.datastar.Attributes→zio.http.datastar.Attributes.DatastarAttributezio.http.datastar.Attributes→zio.http.datastar.Attributes.PartialDataBindzio.http.datastar.Attributes→zio.http.datastar.Attributes.PartialDataIndicatorzio.http.datastar.Attributes→zio.http.datastar.Attributes.PartialDataOnzio.http.datastar.Attributes→zio.http.datastar.Attributes.PartialDataRefzio.http.datastar.Attributes→zio.http.datastar.Attributes.PartialSignalAttrzio.http.datastar.Attributes→zio.http.datastar.Attributes.PartialSignalsAttr
- Direction
- datastar uses datastar.Attributes, so a change to datastar.Attributes can break datastar, while a change to datastar can't break datastar.Attributes.
- Position
- Below the diagonal: datastar uses a module listed above it, which is the healthy direction.
33→27 datastar uses datastar.Attributes.OnIntervalModifier✕
- Connections
- 5 pairs of types, where a type in datastar uses a type in datastar.Attributes.OnIntervalModifier.
- The types involved
zio.http.datastar.DispatchEventOptions→zio.http.datastar.Attributes.OnIntervalModifier.Durationzio.http.datastar.ExecuteScriptOptions→zio.http.datastar.Attributes.OnIntervalModifier.Durationzio.http.datastar.PatchElementOptions→zio.http.datastar.Attributes.OnIntervalModifier.Durationzio.http.datastar.PatchSignalOptions→zio.http.datastar.Attributes.OnIntervalModifier.Durationzio.http.datastar.ServerSentEventGenerator→zio.http.datastar.Attributes.OnIntervalModifier.Duration
- Direction
- datastar uses datastar.Attributes.OnIntervalModifier, so a change to datastar.Attributes.OnIntervalModifier can break datastar, while a change to datastar can't break datastar.Attributes.OnIntervalModifier.
- Position
- Below the diagonal: datastar uses a module listed above it, which is the healthy direction.
33→28 datastar uses Cookie✕
- Connections
- 2 pairs of types, where a type in datastar uses a type in Cookie.
- The types involved
zio.http.datastar.DatastarPackageBase→zio.http.Cookie.Requestzio.http.datastar.DatastarPackageBase→zio.http.Cookie.Response
- Direction
- datastar uses Cookie, so a change to Cookie can break datastar, while a change to datastar can't break Cookie.
- Position
- Below the diagonal: datastar uses a module listed above it, which is the healthy direction.
33→30 datastar uses Header.AcceptLanguage✕
- Connections
- 1 pair of types, where a type in datastar uses a type in Header.AcceptLanguage.
- The types involved
zio.http.datastar.DatastarPackageBase→zio.http.Header.AcceptLanguage.Any
- Direction
- datastar uses Header.AcceptLanguage, so a change to Header.AcceptLanguage can break datastar, while a change to datastar can't break Header.AcceptLanguage.
- Position
- Below the diagonal: datastar uses a module listed above it, which is the healthy direction.
33→39 datastar uses zio.http part of a loop✕
- Connections
- 4 pairs of types, where a type in datastar uses a type in zio.http.
- The types involved
zio.http.datastar.Datastar→zio.http.ServerSentEventzio.http.datastar.DatastarEvent→zio.http.ServerSentEventzio.http.datastar.DatastarPackageBase→zio.http.Handlerzio.http.datastar.DatastarPackageBase→zio.http.ServerSentEvent
- Direction
- datastar uses zio.http, so a change to zio.http can break datastar, while a change to datastar can't break zio.http.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
34→4 endpoint.openapi.OpenAPIGen uses endpoint.cli.HttpOptions✕
- Connections
- 2 pairs of types, where a type in endpoint.openapi.OpenAPIGen uses a type in endpoint.cli.HttpOptions.
- The types involved
zio.http.endpoint.openapi.OpenAPIGen.AtomizedMetaCodecs→zio.http.endpoint.cli.HttpOptions.Headerzio.http.endpoint.openapi.OpenAPIGen.AtomizedMetaCodecs→zio.http.endpoint.cli.HttpOptions.Query
- Direction
- endpoint.openapi.OpenAPIGen uses endpoint.cli.HttpOptions, so a change to endpoint.cli.HttpOptions can break endpoint.openapi.OpenAPIGen, while a change to endpoint.openapi.OpenAPIGen can't break endpoint.cli.HttpOptions.
- Position
- Below the diagonal: endpoint.openapi.OpenAPIGen uses a module listed above it, which is the healthy direction.
34→5 endpoint.openapi.OpenAPIGen uses gen.grpc.Protobuf✕
- Connections
- 1 pair of types, where a type in endpoint.openapi.OpenAPIGen uses a type in gen.grpc.Protobuf.
- The types involved
zio.http.endpoint.openapi.OpenAPIGen.AtomizedMetaCodecs→zio.http.gen.grpc.Protobuf.Method
- Direction
- endpoint.openapi.OpenAPIGen uses gen.grpc.Protobuf, so a change to gen.grpc.Protobuf can break endpoint.openapi.OpenAPIGen, while a change to endpoint.openapi.OpenAPIGen can't break gen.grpc.Protobuf.
- Position
- Below the diagonal: endpoint.openapi.OpenAPIGen uses a module listed above it, which is the healthy direction.
34→6 endpoint.openapi.OpenAPIGen uses gen.scala.Code.Collection✕
- Connections
- 2 pairs of types, where a type in endpoint.openapi.OpenAPIGen uses a type in gen.scala.Code.Collection.
- The types involved
zio.http.endpoint.openapi.OpenAPIGen.AtomizedMetaCodecs→zio.http.gen.scala.Code.Collection.Mapzio.http.endpoint.openapi.OpenAPIGen.MetaCodec→zio.http.gen.scala.Code.Collection.Map
- Direction
- endpoint.openapi.OpenAPIGen uses gen.scala.Code.Collection, so a change to gen.scala.Code.Collection can break endpoint.openapi.OpenAPIGen, while a change to endpoint.openapi.OpenAPIGen can't break gen.scala.Code.Collection.
- Position
- Below the diagonal: endpoint.openapi.OpenAPIGen uses a module listed above it, which is the healthy direction.
34→7 endpoint.openapi.OpenAPIGen uses gen.scala.Code.ScalaType✕
- Connections
- 2 pairs of types, where a type in endpoint.openapi.OpenAPIGen uses a type in gen.scala.Code.ScalaType.
- The types involved
zio.http.endpoint.openapi.OpenAPIGen.AtomizedMetaCodecs→zio.http.gen.scala.Code.ScalaType.Orzio.http.endpoint.openapi.OpenAPIGen.MetaCodec→zio.http.gen.scala.Code.ScalaType.Or
- Direction
- endpoint.openapi.OpenAPIGen uses gen.scala.Code.ScalaType, so a change to gen.scala.Code.ScalaType can break endpoint.openapi.OpenAPIGen, while a change to endpoint.openapi.OpenAPIGen can't break gen.scala.Code.ScalaType.
- Position
- Below the diagonal: endpoint.openapi.OpenAPIGen uses a module listed above it, which is the healthy direction.
34→10 endpoint.openapi.OpenAPIGen uses gen.smithy.SmithyTrait✕
- Connections
- 2 pairs of types, where a type in endpoint.openapi.OpenAPIGen uses a type in gen.smithy.SmithyTrait.
- The types involved
zio.http.endpoint.openapi.OpenAPIGen.AtomizedMetaCodecs→zio.http.gen.smithy.SmithyTrait.MediaTypezio.http.endpoint.openapi.OpenAPIGen.MetaCodec→zio.http.gen.smithy.SmithyTrait.MediaType
- Direction
- endpoint.openapi.OpenAPIGen uses gen.smithy.SmithyTrait, so a change to gen.smithy.SmithyTrait can break endpoint.openapi.OpenAPIGen, while a change to endpoint.openapi.OpenAPIGen can't break gen.smithy.SmithyTrait.
- Position
- Below the diagonal: endpoint.openapi.OpenAPIGen uses a module listed above it, which is the healthy direction.
34→13 endpoint.openapi.OpenAPIGen uses codec.HttpCodec✕
- Connections
- 2 pairs of types, where a type in endpoint.openapi.OpenAPIGen uses a type in codec.HttpCodec.
- The types involved
zio.http.endpoint.openapi.OpenAPIGen.AtomizedMetaCodecs→zio.http.codec.HttpCodec.Atomzio.http.endpoint.openapi.OpenAPIGen.MetaCodec→zio.http.codec.HttpCodec.Metadata
- Direction
- endpoint.openapi.OpenAPIGen uses codec.HttpCodec, so a change to codec.HttpCodec can break endpoint.openapi.OpenAPIGen, while a change to endpoint.openapi.OpenAPIGen can't break codec.HttpCodec.
- Position
- Below the diagonal: endpoint.openapi.OpenAPIGen uses a module listed above it, which is the healthy direction.
34→15 endpoint.openapi.OpenAPIGen uses codec✕
- Connections
- 4 pairs of types, where a type in endpoint.openapi.OpenAPIGen uses a type in codec.
- The types involved
zio.http.endpoint.openapi.OpenAPIGen.AtomizedMetaCodecs→zio.http.codec.Doczio.http.endpoint.openapi.OpenAPIGen.AtomizedMetaCodecs→zio.http.codec.SegmentCodeczio.http.endpoint.openapi.OpenAPIGen.AtomizedMetaCodecs→zio.http.codec.SimpleCodeczio.http.endpoint.openapi.OpenAPIGen.MetaCodec→zio.http.codec.Doc
- Direction
- endpoint.openapi.OpenAPIGen uses codec, so a change to codec can break endpoint.openapi.OpenAPIGen, while a change to endpoint.openapi.OpenAPIGen can't break codec.
- Position
- Below the diagonal: endpoint.openapi.OpenAPIGen uses a module listed above it, which is the healthy direction.
34→18 endpoint.openapi.OpenAPIGen uses endpoint.cli.Retriever✕
- Connections
- 1 pair of types, where a type in endpoint.openapi.OpenAPIGen uses a type in endpoint.cli.Retriever.
- The types involved
zio.http.endpoint.openapi.OpenAPIGen.AtomizedMetaCodecs→zio.http.endpoint.cli.Retriever.Content
- Direction
- endpoint.openapi.OpenAPIGen uses endpoint.cli.Retriever, so a change to endpoint.cli.Retriever can break endpoint.openapi.OpenAPIGen, while a change to endpoint.openapi.OpenAPIGen can't break endpoint.cli.Retriever.
- Position
- Below the diagonal: endpoint.openapi.OpenAPIGen uses a module listed above it, which is the healthy direction.
34→20 endpoint.openapi.OpenAPIGen uses gen.scala.Code.CodecType✕
- Connections
- 4 pairs of types, where a type in endpoint.openapi.OpenAPIGen uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.endpoint.openapi.OpenAPIGen.AtomizedMetaCodecs→zio.http.gen.scala.Code.CodecType.Booleanzio.http.endpoint.openapi.OpenAPIGen.AtomizedMetaCodecs→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.OpenAPIGen.MetaCodec→zio.http.gen.scala.Code.CodecType.Booleanzio.http.endpoint.openapi.OpenAPIGen.MetaCodec→zio.http.gen.scala.Code.CodecType.String
- Direction
- endpoint.openapi.OpenAPIGen uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break endpoint.openapi.OpenAPIGen, while a change to endpoint.openapi.OpenAPIGen can't break gen.scala.Code.CodecType.
- Position
- Below the diagonal: endpoint.openapi.OpenAPIGen uses a module listed above it, which is the healthy direction.
34→30 endpoint.openapi.OpenAPIGen uses Header.AcceptLanguage✕
- Connections
- 1 pair of types, where a type in endpoint.openapi.OpenAPIGen uses a type in Header.AcceptLanguage.
- The types involved
zio.http.endpoint.openapi.OpenAPIGen.MetaCodec→zio.http.Header.AcceptLanguage.Any
- Direction
- endpoint.openapi.OpenAPIGen uses Header.AcceptLanguage, so a change to Header.AcceptLanguage can break endpoint.openapi.OpenAPIGen, while a change to endpoint.openapi.OpenAPIGen can't break Header.AcceptLanguage.
- Position
- Below the diagonal: endpoint.openapi.OpenAPIGen uses a module listed above it, which is the healthy direction.
34→38 endpoint.openapi.OpenAPIGen uses endpoint.openapi.OpenAPI part of a loop✕
- Connections
- 2 pairs of types, where a type in endpoint.openapi.OpenAPIGen uses a type in endpoint.openapi.OpenAPI.
- The types involved
zio.http.endpoint.openapi.OpenAPIGen.AtomizedMetaCodecs→zio.http.endpoint.openapi.OpenAPI.Examplezio.http.endpoint.openapi.OpenAPIGen.MetaCodec→zio.http.endpoint.openapi.OpenAPI.Example
- Direction
- endpoint.openapi.OpenAPIGen uses endpoint.openapi.OpenAPI, so a change to endpoint.openapi.OpenAPI can break endpoint.openapi.OpenAPIGen, while a change to endpoint.openapi.OpenAPIGen can't break endpoint.openapi.OpenAPI.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
34→39 endpoint.openapi.OpenAPIGen uses zio.http part of a loop✕
- Connections
- 1 pair of types, where a type in endpoint.openapi.OpenAPIGen uses a type in zio.http.
- The types involved
zio.http.endpoint.openapi.OpenAPIGen.AtomizedMetaCodecs→zio.http.Status
- Direction
- endpoint.openapi.OpenAPIGen uses zio.http, so a change to zio.http can break endpoint.openapi.OpenAPIGen, while a change to endpoint.openapi.OpenAPIGen can't break zio.http.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
35→2 Handler uses Header.Vary✕
- Connections
- 2 pairs of types, where a type in Handler uses a type in Header.Vary.
- The types involved
zio.http.Handler.RequestHandlerSyntax→zio.http.Header.Vary.Headerszio.http.Handler.ResponseOutputSyntax→zio.http.Header.Vary.Headers
- Direction
- Handler uses Header.Vary, so a change to Header.Vary can break Handler, while a change to Handler can't break Header.Vary.
- Position
- Below the diagonal: Handler uses a module listed above it, which is the healthy direction.
35→3 Handler uses URL✕
- Connections
- 8 pairs of types, where a type in Handler uses a type in URL.
- The types involved
zio.http.Handler.ContraFlatMap→zio.http.URL.Errzio.http.Handler.FromFunctionEither→zio.http.URL.Errzio.http.Handler.FromFunctionExit→zio.http.URL.Errzio.http.Handler.FromFunctionHandler→zio.http.URL.Errzio.http.Handler.FromFunctionZIO→zio.http.URL.Errzio.http.Handler.RequestHandlerSyntax→zio.http.URL.Errzio.http.Handler.ResponseOutputSyntax→zio.http.URL.Errzio.http.Handler.ScopedPartiallyApplied→zio.http.URL.Err
- Direction
- Handler uses URL, so a change to URL can break Handler, while a change to Handler can't break URL.
- Position
- Below the diagonal: Handler uses a module listed above it, which is the healthy direction.
35→4 Handler uses endpoint.cli.HttpOptions✕
- Connections
- 2 pairs of types, where a type in Handler uses a type in endpoint.cli.HttpOptions.
- The types involved
zio.http.Handler.RequestHandlerSyntax→zio.http.endpoint.cli.HttpOptions.Pathzio.http.Handler.ResponseOutputSyntax→zio.http.endpoint.cli.HttpOptions.Body
- Direction
- Handler uses endpoint.cli.HttpOptions, so a change to endpoint.cli.HttpOptions can break Handler, while a change to Handler can't break endpoint.cli.HttpOptions.
- Position
- Below the diagonal: Handler uses a module listed above it, which is the healthy direction.
35→5 Handler uses gen.grpc.Protobuf✕
- Connections
- 1 pair of types, where a type in Handler uses a type in gen.grpc.Protobuf.
- The types involved
zio.http.Handler.RequestHandlerSyntax→zio.http.gen.grpc.Protobuf.Method
- Direction
- Handler uses gen.grpc.Protobuf, so a change to gen.grpc.Protobuf can break Handler, while a change to Handler can't break gen.grpc.Protobuf.
- Position
- Below the diagonal: Handler uses a module listed above it, which is the healthy direction.
35→7 Handler uses gen.scala.Code.ScalaType✕
- Connections
- 6 pairs of types, where a type in Handler uses a type in gen.scala.Code.ScalaType.
- The types involved
zio.http.Handler.FromFunction→zio.http.gen.scala.Code.ScalaType.Unitzio.http.Handler.FromFunctionEither→zio.http.gen.scala.Code.ScalaType.Unitzio.http.Handler.FromFunctionExit→zio.http.gen.scala.Code.ScalaType.Unitzio.http.Handler.FromFunctionHandler→zio.http.gen.scala.Code.ScalaType.Unitzio.http.Handler.FromFunctionZIO→zio.http.gen.scala.Code.ScalaType.Unitzio.http.Handler.ParamExtractorBuilder→zio.http.gen.scala.Code.ScalaType.Unit
- Direction
- Handler uses gen.scala.Code.ScalaType, so a change to gen.scala.Code.ScalaType can break Handler, while a change to Handler can't break gen.scala.Code.ScalaType.
- Position
- Below the diagonal: Handler uses a module listed above it, which is the healthy direction.
35→12 Handler uses internal✕
- Connections
- 1 pair of types, where a type in Handler uses a type in internal.
- The types involved
zio.http.Handler.RequestHandlerSyntax→zio.http.internal.HeaderModifier
- Direction
- Handler uses internal, so a change to internal can break Handler, while a change to Handler can't break internal.
- Position
- Below the diagonal: Handler uses a module listed above it, which is the healthy direction.
35→18 Handler uses endpoint.cli.Retriever✕
- Connections
- 1 pair of types, where a type in Handler uses a type in endpoint.cli.Retriever.
- The types involved
zio.http.Handler.RequestHandlerSyntax→zio.http.endpoint.cli.Retriever.URL
- Direction
- Handler uses endpoint.cli.Retriever, so a change to endpoint.cli.Retriever can break Handler, while a change to Handler can't break endpoint.cli.Retriever.
- Position
- Below the diagonal: Handler uses a module listed above it, which is the healthy direction.
35→20 Handler uses gen.scala.Code.CodecType✕
- Connections
- 2 pairs of types, where a type in Handler uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.Handler.ResponseOutputSyntax→zio.http.gen.scala.Code.CodecType.Stringzio.http.Handler.ScopedPartiallyApplied→zio.http.gen.scala.Code.CodecType.Boolean
- Direction
- Handler uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break Handler, while a change to Handler can't break gen.scala.Code.CodecType.
- Position
- Below the diagonal: Handler uses a module listed above it, which is the healthy direction.
35→28 Handler uses Cookie✕
- Connections
- 1 pair of types, where a type in Handler uses a type in Cookie.
- The types involved
zio.http.Handler.ResponseOutputSyntax→zio.http.Cookie.Response
- Direction
- Handler uses Cookie, so a change to Cookie can break Handler, while a change to Handler can't break Cookie.
- Position
- Below the diagonal: Handler uses a module listed above it, which is the healthy direction.
35→29 Handler uses Header✕
- Connections
- 2 pairs of types, where a type in Handler uses a type in Header.
- The types involved
zio.http.Handler.ResponseOutputSyntax→zio.http.Header.ContentLengthzio.http.Handler.ResponseOutputSyntax→zio.http.Header.HeaderType
- Direction
- Handler uses Header, so a change to Header can break Handler, while a change to Handler can't break Header.
- Position
- Below the diagonal: Handler uses a module listed above it, which is the healthy direction.
35→30 Handler uses Header.AcceptLanguage✕
- Connections
- 4 pairs of types, where a type in Handler uses a type in Header.AcceptLanguage.
- The types involved
zio.http.Handler.FromFunction→zio.http.Header.AcceptLanguage.Anyzio.http.Handler.FromFunctionEither→zio.http.Header.AcceptLanguage.Anyzio.http.Handler.FromFunctionExit→zio.http.Header.AcceptLanguage.Anyzio.http.Handler.ParamExtractorBuilder→zio.http.Header.AcceptLanguage.Any
- Direction
- Handler uses Header.AcceptLanguage, so a change to Header.AcceptLanguage can break Handler, while a change to Handler can't break Header.AcceptLanguage.
- Position
- Below the diagonal: Handler uses a module listed above it, which is the healthy direction.
35→31 Handler uses Body✕
- Connections
- 1 pair of types, where a type in Handler uses a type in Body.
- The types involved
zio.http.Handler.ResponseOutputSyntax→zio.http.Body.ContentType
- Direction
- Handler uses Body, so a change to Body can break Handler, while a change to Handler can't break Body.
- Position
- Below the diagonal: Handler uses a module listed above it, which is the healthy direction.
35→39 Handler uses zio.http part of a loop✕
- Connections
- 11 pairs of types, where a type in Handler uses a type in zio.http.
- The types involved
zio.http.Handler.ContraFlatMap→zio.http.Handlerzio.http.Handler.FromFunction→zio.http.Handlerzio.http.Handler.FromFunctionEither→zio.http.Handlerzio.http.Handler.FromFunctionExit→zio.http.Handlerzio.http.Handler.FromFunctionHandler→zio.http.Handlerzio.http.Handler.FromFunctionZIO→zio.http.Handlerzio.http.Handler.ParamExtractorBuilder→zio.http.Handlerzio.http.Handler.RequestHandlerSyntax→zio.http.Statuszio.http.Handler.ResponseOutputSyntax→zio.http.Handlerzio.http.Handler.ResponseOutputSyntax→zio.http.Statuszio.http.Handler.ScopedPartiallyApplied→zio.http.Handler
- Direction
- Handler uses zio.http, so a change to zio.http can break Handler, while a change to Handler can't break zio.http.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
36→1 endpoint.openapi uses gen.smithy.Smithy.SimpleShapes✕
- Connections
- 3 pairs of types, where a type in endpoint.openapi uses a type in gen.smithy.Smithy.SimpleShapes.
- The types involved
zio.http.endpoint.openapi.JsonSchema→zio.http.gen.smithy.Smithy.SimpleShapes.Bytezio.http.endpoint.openapi.OpenAPI→zio.http.gen.smithy.Smithy.SimpleShapes.Listzio.http.endpoint.openapi.SerializableJsonSchema→zio.http.gen.smithy.Smithy.SimpleShapes.Double
- Direction
- endpoint.openapi uses gen.smithy.Smithy.SimpleShapes, so a change to gen.smithy.Smithy.SimpleShapes can break endpoint.openapi, while a change to endpoint.openapi can't break gen.smithy.Smithy.SimpleShapes.
- Position
- Below the diagonal: endpoint.openapi uses a module listed above it, which is the healthy direction.
36→4 endpoint.openapi uses endpoint.cli.HttpOptions✕
- Connections
- 1 pair of types, where a type in endpoint.openapi uses a type in endpoint.cli.HttpOptions.
- The types involved
zio.http.endpoint.openapi.OpenAPI→zio.http.endpoint.cli.HttpOptions.Path
- Direction
- endpoint.openapi uses endpoint.cli.HttpOptions, so a change to endpoint.cli.HttpOptions can break endpoint.openapi, while a change to endpoint.openapi can't break endpoint.cli.HttpOptions.
- Position
- Below the diagonal: endpoint.openapi uses a module listed above it, which is the healthy direction.
36→5 endpoint.openapi uses gen.grpc.Protobuf✕
- Connections
- 1 pair of types, where a type in endpoint.openapi uses a type in gen.grpc.Protobuf.
- The types involved
zio.http.endpoint.openapi.OpenAPIGen→zio.http.gen.grpc.Protobuf.Method
- Direction
- endpoint.openapi uses gen.grpc.Protobuf, so a change to gen.grpc.Protobuf can break endpoint.openapi, while a change to endpoint.openapi can't break gen.grpc.Protobuf.
- Position
- Below the diagonal: endpoint.openapi uses a module listed above it, which is the healthy direction.
36→6 endpoint.openapi uses gen.scala.Code.Collection✕
- Connections
- 3 pairs of types, where a type in endpoint.openapi uses a type in gen.scala.Code.Collection.
- The types involved
zio.http.endpoint.openapi.JsonSchemas→zio.http.gen.scala.Code.Collection.Mapzio.http.endpoint.openapi.OpenAPIGen→zio.http.gen.scala.Code.Collection.Mapzio.http.endpoint.openapi.SerializableJsonSchema→zio.http.gen.scala.Code.Collection.Map
- Direction
- endpoint.openapi uses gen.scala.Code.Collection, so a change to gen.scala.Code.Collection can break endpoint.openapi, while a change to endpoint.openapi can't break gen.scala.Code.Collection.
- Position
- Below the diagonal: endpoint.openapi uses a module listed above it, which is the healthy direction.
36→7 endpoint.openapi uses gen.scala.Code.ScalaType✕
- Connections
- 1 pair of types, where a type in endpoint.openapi uses a type in gen.scala.Code.ScalaType.
- The types involved
zio.http.endpoint.openapi.SwaggerUI→zio.http.gen.scala.Code.ScalaType.Unit
- Direction
- endpoint.openapi uses gen.scala.Code.ScalaType, so a change to gen.scala.Code.ScalaType can break endpoint.openapi, while a change to endpoint.openapi can't break gen.scala.Code.ScalaType.
- Position
- Below the diagonal: endpoint.openapi uses a module listed above it, which is the healthy direction.
36→8 endpoint.openapi uses codec.PathCodec✕
- Connections
- 2 pairs of types, where a type in endpoint.openapi uses a type in codec.PathCodec.
- The types involved
zio.http.endpoint.openapi.JsonSchema→zio.http.codec.PathCodec.MetaDatazio.http.endpoint.openapi.OpenAPIGen→zio.http.codec.PathCodec.MetaData
- Direction
- endpoint.openapi uses codec.PathCodec, so a change to codec.PathCodec can break endpoint.openapi, while a change to endpoint.openapi can't break codec.PathCodec.
- Position
- Below the diagonal: endpoint.openapi uses a module listed above it, which is the healthy direction.
36→10 endpoint.openapi uses gen.smithy.SmithyTrait✕
- Connections
- 1 pair of types, where a type in endpoint.openapi uses a type in gen.smithy.SmithyTrait.
- The types involved
zio.http.endpoint.openapi.OpenAPIGen→zio.http.gen.smithy.SmithyTrait.MediaType
- Direction
- endpoint.openapi uses gen.smithy.SmithyTrait, so a change to gen.smithy.SmithyTrait can break endpoint.openapi, while a change to endpoint.openapi can't break gen.smithy.SmithyTrait.
- Position
- Below the diagonal: endpoint.openapi uses a module listed above it, which is the healthy direction.
36→11 endpoint.openapi uses ErrorResponseConfig.ErrorFormat✕
- Connections
- 3 pairs of types, where a type in endpoint.openapi uses a type in ErrorResponseConfig.ErrorFormat.
- The types involved
zio.http.endpoint.openapi.JsonSchema→zio.http.ErrorResponseConfig.ErrorFormat.Jsonzio.http.endpoint.openapi.OpenAPIGen→zio.http.ErrorResponseConfig.ErrorFormat.Jsonzio.http.endpoint.openapi.SerializableJsonSchema→zio.http.ErrorResponseConfig.ErrorFormat.Json
- Direction
- endpoint.openapi uses ErrorResponseConfig.ErrorFormat, so a change to ErrorResponseConfig.ErrorFormat can break endpoint.openapi, while a change to endpoint.openapi can't break ErrorResponseConfig.ErrorFormat.
- Position
- Below the diagonal: endpoint.openapi uses a module listed above it, which is the healthy direction.
36→13 endpoint.openapi uses codec.HttpCodec✕
- Connections
- 1 pair of types, where a type in endpoint.openapi uses a type in codec.HttpCodec.
- The types involved
zio.http.endpoint.openapi.OpenAPIGen→zio.http.codec.HttpCodec.Metadata
- Direction
- endpoint.openapi uses codec.HttpCodec, so a change to codec.HttpCodec can break endpoint.openapi, while a change to endpoint.openapi can't break codec.HttpCodec.
- Position
- Below the diagonal: endpoint.openapi uses a module listed above it, which is the healthy direction.
36→15 endpoint.openapi uses codec✕
- Connections
- 5 pairs of types, where a type in endpoint.openapi uses a type in codec.
- The types involved
zio.http.endpoint.openapi.OpenAPIGen→zio.http.codec.HttpCodeczio.http.endpoint.openapi.OpenAPIGen→zio.http.codec.PathCodeczio.http.endpoint.openapi.OpenAPIGen→zio.http.codec.SegmentCodeczio.http.endpoint.openapi.OpenAPIGen→zio.http.codec.SimpleCodeczio.http.endpoint.openapi.SwaggerUI→zio.http.codec.PathCodec
- Direction
- endpoint.openapi uses codec, so a change to codec can break endpoint.openapi, while a change to endpoint.openapi can't break codec.
- Position
- Below the diagonal: endpoint.openapi uses a module listed above it, which is the healthy direction.
36→16 endpoint.openapi uses endpoint✕
- Connections
- 1 pair of types, where a type in endpoint.openapi uses a type in endpoint.
- The types involved
zio.http.endpoint.openapi.OpenAPIGen→zio.http.endpoint.Endpoint
- Direction
- endpoint.openapi uses endpoint, so a change to endpoint can break endpoint.openapi, while a change to endpoint.openapi can't break endpoint.
- Position
- Below the diagonal: endpoint.openapi uses a module listed above it, which is the healthy direction.
36→20 endpoint.openapi uses gen.scala.Code.CodecType✕
- Connections
- 12 pairs of types, where a type in endpoint.openapi uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.endpoint.openapi.JsonSchema→zio.http.gen.scala.Code.CodecType.Booleanzio.http.endpoint.openapi.JsonSchema→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.JsonSchemas→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.OpenAPI→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.OpenAPIGen→zio.http.gen.scala.Code.CodecType.Booleanzio.http.endpoint.openapi.OpenAPIGen→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.SerializableJsonSchema→zio.http.gen.scala.Code.CodecType.Booleanzio.http.endpoint.openapi.SerializableJsonSchema→zio.http.gen.scala.Code.CodecType.Intzio.http.endpoint.openapi.SerializableJsonSchema→zio.http.gen.scala.Code.CodecType.Longzio.http.endpoint.openapi.SerializableJsonSchema→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.SwaggerUI→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.TypeOrTypes→zio.http.gen.scala.Code.CodecType.String
- Direction
- endpoint.openapi uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break endpoint.openapi, while a change to endpoint.openapi can't break gen.scala.Code.CodecType.
- Position
- Below the diagonal: endpoint.openapi uses a module listed above it, which is the healthy direction.
36→21 endpoint.openapi uses endpoint.openapi.JsonSchema✕
- Connections
- 2 pairs of types, where a type in endpoint.openapi uses a type in endpoint.openapi.JsonSchema.
- The types involved
zio.http.endpoint.openapi.OpenAPIGen→zio.http.endpoint.openapi.JsonSchema.SchemaRefzio.http.endpoint.openapi.OpenAPIGen→zio.http.endpoint.openapi.JsonSchema.SchemaStyle
- Direction
- endpoint.openapi uses endpoint.openapi.JsonSchema, so a change to endpoint.openapi.JsonSchema can break endpoint.openapi, while a change to endpoint.openapi can't break endpoint.openapi.JsonSchema.
- Position
- Below the diagonal: endpoint.openapi uses a module listed above it, which is the healthy direction.
36→28 endpoint.openapi uses Cookie✕
- Connections
- 2 pairs of types, where a type in endpoint.openapi uses a type in Cookie.
- The types involved
zio.http.endpoint.openapi.OpenAPIGen→zio.http.Cookie.Responsezio.http.endpoint.openapi.SwaggerUI→zio.http.Cookie.Response
- Direction
- endpoint.openapi uses Cookie, so a change to Cookie can break endpoint.openapi, while a change to endpoint.openapi can't break Cookie.
- Position
- Below the diagonal: endpoint.openapi uses a module listed above it, which is the healthy direction.
36→29 endpoint.openapi uses Header✕
- Connections
- 1 pair of types, where a type in endpoint.openapi uses a type in Header.
- The types involved
zio.http.endpoint.openapi.JsonSchema→zio.http.Header.ContentEncoding
- Direction
- endpoint.openapi uses Header, so a change to Header can break endpoint.openapi, while a change to endpoint.openapi can't break Header.
- Position
- Below the diagonal: endpoint.openapi uses a module listed above it, which is the healthy direction.
36→30 endpoint.openapi uses Header.AcceptLanguage✕
- Connections
- 2 pairs of types, where a type in endpoint.openapi uses a type in Header.AcceptLanguage.
- The types involved
zio.http.endpoint.openapi.OpenAPIGen→zio.http.Header.AcceptLanguage.Anyzio.http.endpoint.openapi.SwaggerUI→zio.http.Header.AcceptLanguage.Any
- Direction
- endpoint.openapi uses Header.AcceptLanguage, so a change to Header.AcceptLanguage can break endpoint.openapi, while a change to endpoint.openapi can't break Header.AcceptLanguage.
- Position
- Below the diagonal: endpoint.openapi uses a module listed above it, which is the healthy direction.
36→34 endpoint.openapi uses endpoint.openapi.OpenAPIGen✕
- Connections
- 2 pairs of types, where a type in endpoint.openapi uses a type in endpoint.openapi.OpenAPIGen.
- The types involved
zio.http.endpoint.openapi.OpenAPIGen→zio.http.endpoint.openapi.OpenAPIGen.AtomizedMetaCodecszio.http.endpoint.openapi.OpenAPIGen→zio.http.endpoint.openapi.OpenAPIGen.MetaCodec
- Direction
- endpoint.openapi uses endpoint.openapi.OpenAPIGen, so a change to endpoint.openapi.OpenAPIGen can break endpoint.openapi, while a change to endpoint.openapi can't break endpoint.openapi.OpenAPIGen.
- Position
- Below the diagonal: endpoint.openapi uses a module listed above it, which is the healthy direction.
36→38 endpoint.openapi uses endpoint.openapi.OpenAPI part of a loop✕
- Connections
- 7 pairs of types, where a type in endpoint.openapi uses a type in endpoint.openapi.OpenAPI.
- The types involved
zio.http.endpoint.openapi.OpenAPI→zio.http.endpoint.openapi.OpenAPI.Componentszio.http.endpoint.openapi.OpenAPI→zio.http.endpoint.openapi.OpenAPI.ExternalDoczio.http.endpoint.openapi.OpenAPI→zio.http.endpoint.openapi.OpenAPI.Infozio.http.endpoint.openapi.OpenAPI→zio.http.endpoint.openapi.OpenAPI.PathItemzio.http.endpoint.openapi.OpenAPI→zio.http.endpoint.openapi.OpenAPI.Tagzio.http.endpoint.openapi.OpenAPIGen→zio.http.endpoint.openapi.OpenAPI.ReferenceOrzio.http.endpoint.openapi.OpenAPIGen→zio.http.endpoint.openapi.OpenAPI.StatusOrDefault
- Direction
- endpoint.openapi uses endpoint.openapi.OpenAPI, so a change to endpoint.openapi.OpenAPI can break endpoint.openapi, while a change to endpoint.openapi can't break endpoint.openapi.OpenAPI.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
36→39 endpoint.openapi uses zio.http part of a loop✕
- Connections
- 2 pairs of types, where a type in endpoint.openapi uses a type in zio.http.
- The types involved
zio.http.endpoint.openapi.OpenAPIGen→zio.http.Statuszio.http.endpoint.openapi.SwaggerUI→zio.http.Routes
- Direction
- endpoint.openapi uses zio.http, so a change to zio.http can break endpoint.openapi, while a change to endpoint.openapi can't break zio.http.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
37→1 netty uses gen.smithy.Smithy.SimpleShapes✕
- Connections
- 1 pair of types, where a type in netty uses a type in gen.smithy.Smithy.SimpleShapes.
- The types involved
zio.http.netty.AsyncBodyReader→zio.http.gen.smithy.Smithy.SimpleShapes.Byte
- Direction
- netty uses gen.smithy.Smithy.SimpleShapes, so a change to gen.smithy.Smithy.SimpleShapes can break netty, while a change to netty can't break gen.smithy.Smithy.SimpleShapes.
- Position
- Below the diagonal: netty uses a module listed above it, which is the healthy direction.
37→4 netty uses endpoint.cli.HttpOptions✕
- Connections
- 3 pairs of types, where a type in netty uses a type in endpoint.cli.HttpOptions.
- The types involved
zio.http.netty.BodyExtensions→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.netty.NettyBody→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.netty.NettyBodyWriter→zio.http.endpoint.cli.HttpOptions.Body
- Direction
- netty uses endpoint.cli.HttpOptions, so a change to endpoint.cli.HttpOptions can break netty, while a change to netty can't break endpoint.cli.HttpOptions.
- Position
- Below the diagonal: netty uses a module listed above it, which is the healthy direction.
37→5 netty uses gen.grpc.Protobuf✕
- Connections
- 1 pair of types, where a type in netty uses a type in gen.grpc.Protobuf.
- The types involved
zio.http.netty.NettyResponse→zio.http.gen.grpc.Protobuf.Method
- Direction
- netty uses gen.grpc.Protobuf, so a change to gen.grpc.Protobuf can break netty, while a change to netty can't break gen.grpc.Protobuf.
- Position
- Below the diagonal: netty uses a module listed above it, which is the healthy direction.
37→7 netty uses gen.scala.Code.ScalaType✕
- Connections
- 7 pairs of types, where a type in netty uses a type in gen.scala.Code.ScalaType.
- The types involved
zio.http.netty.AsyncBodyReader→zio.http.gen.scala.Code.ScalaType.Unitzio.http.netty.HybridContentLengthHandler→zio.http.gen.scala.Code.ScalaType.Unitzio.http.netty.NettyBody→zio.http.gen.scala.Code.ScalaType.Unitzio.http.netty.NettyBodyWriter→zio.http.gen.scala.Code.ScalaType.Unitzio.http.netty.NettyChannel→zio.http.gen.scala.Code.ScalaType.Unitzio.http.netty.NettyRuntime→zio.http.gen.scala.Code.ScalaType.Unitzio.http.netty.WebSocketAppHandler→zio.http.gen.scala.Code.ScalaType.Unit
- Direction
- netty uses gen.scala.Code.ScalaType, so a change to gen.scala.Code.ScalaType can break netty, while a change to netty can't break gen.scala.Code.ScalaType.
- Position
- Below the diagonal: netty uses a module listed above it, which is the healthy direction.
37→12 netty uses internal✕
- Connections
- 1 pair of types, where a type in netty uses a type in internal.
- The types involved
zio.http.netty.NettyResponse→zio.http.internal.ChannelState
- Direction
- netty uses internal, so a change to internal can break netty, while a change to netty can't break internal.
- Position
- Below the diagonal: netty uses a module listed above it, which is the healthy direction.
37→20 netty uses gen.scala.Code.CodecType✕
- Connections
- 16 pairs of types, where a type in netty uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.netty.AsyncBodyReader→zio.http.gen.scala.Code.CodecType.Booleanzio.http.netty.AsyncBodyReader→zio.http.gen.scala.Code.CodecType.Intzio.http.netty.NettyBody→zio.http.gen.scala.Code.CodecType.Longzio.http.netty.NettyBodyWriter→zio.http.gen.scala.Code.CodecType.Longzio.http.netty.NettyChannel→zio.http.gen.scala.Code.CodecType.Booleanzio.http.netty.NettyChannel→zio.http.gen.scala.Code.CodecType.Stringzio.http.netty.NettyConfig→zio.http.gen.scala.Code.CodecType.Intzio.http.netty.NettyConfig→zio.http.gen.scala.Code.CodecType.Longzio.http.netty.NettyCookieEncoding→zio.http.gen.scala.Code.CodecType.Booleanzio.http.netty.NettyCookieEncoding→zio.http.gen.scala.Code.CodecType.Stringzio.http.netty.NettyFutureExecutor→zio.http.gen.scala.Code.CodecType.Booleanzio.http.netty.NettyQueryParamEncoding→zio.http.gen.scala.Code.CodecType.Stringzio.http.netty.NettyResponse→zio.http.gen.scala.Code.CodecType.Booleanzio.http.netty.NettyResponse→zio.http.gen.scala.Code.CodecType.Longzio.http.netty.NettyRuntime→zio.http.gen.scala.Code.CodecType.Booleanzio.http.netty.WebSocketChannel→zio.http.gen.scala.Code.CodecType.Boolean
- Direction
- netty uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break netty, while a change to netty can't break gen.scala.Code.CodecType.
- Position
- Below the diagonal: netty uses a module listed above it, which is the healthy direction.
37→22 netty uses gen.openapi✕
- Connections
- 3 pairs of types, where a type in netty uses a type in gen.openapi.
- The types involved
zio.http.netty.EventLoopGroups→zio.http.gen.openapi.Configzio.http.netty.NettyConfig→zio.http.gen.openapi.Configzio.http.netty.server→zio.http.gen.openapi.Config
- Direction
- netty uses gen.openapi, so a change to gen.openapi can break netty, while a change to netty can't break gen.openapi.
- Position
- Below the diagonal: netty uses a module listed above it, which is the healthy direction.
37→27 netty uses datastar.Attributes.OnIntervalModifier✕
- Connections
- 1 pair of types, where a type in netty uses a type in datastar.Attributes.OnIntervalModifier.
- The types involved
zio.http.netty.NettyConfig→zio.http.datastar.Attributes.OnIntervalModifier.Duration
- Direction
- netty uses datastar.Attributes.OnIntervalModifier, so a change to datastar.Attributes.OnIntervalModifier can break netty, while a change to netty can't break datastar.Attributes.OnIntervalModifier.
- Position
- Below the diagonal: netty uses a module listed above it, which is the healthy direction.
37→28 netty uses Cookie✕
- Connections
- 3 pairs of types, where a type in netty uses a type in Cookie.
- The types involved
zio.http.netty.NettyCookieEncoding→zio.http.Cookie.Requestzio.http.netty.NettyCookieEncoding→zio.http.Cookie.Responsezio.http.netty.NettyResponse→zio.http.Cookie.Response
- Direction
- netty uses Cookie, so a change to Cookie can break netty, while a change to netty can't break Cookie.
- Position
- Below the diagonal: netty uses a module listed above it, which is the healthy direction.
37→30 netty uses Header.AcceptLanguage✕
- Connections
- 3 pairs of types, where a type in netty uses a type in Header.AcceptLanguage.
- The types involved
zio.http.netty.BodyExtensions→zio.http.Header.AcceptLanguage.Anyzio.http.netty.HybridContentLengthHandler→zio.http.Header.AcceptLanguage.Anyzio.http.netty.NettyRuntime→zio.http.Header.AcceptLanguage.Any
- Direction
- netty uses Header.AcceptLanguage, so a change to Header.AcceptLanguage can break netty, while a change to netty can't break Header.AcceptLanguage.
- Position
- Below the diagonal: netty uses a module listed above it, which is the healthy direction.
37→31 netty uses Body✕
- Connections
- 1 pair of types, where a type in netty uses a type in Body.
- The types involved
zio.http.netty.NettyBody→zio.http.Body.ContentType
- Direction
- netty uses Body, so a change to Body can break netty, while a change to netty can't break Body.
- Position
- Below the diagonal: netty uses a module listed above it, which is the healthy direction.
37→39 netty uses zio.http part of a loop✕
- Connections
- 7 pairs of types, where a type in netty uses a type in zio.http.
- The types involved
zio.http.netty.NettyProxy→zio.http.Credentialszio.http.netty.NettyQueryParamEncoding→zio.http.QueryParamszio.http.netty.NettyResponse→zio.http.Statuszio.http.netty.WebSocketAppHandler→zio.http.ChannelEventzio.http.netty.WebSocketAppHandler→zio.http.WebSocketFramezio.http.netty.WebSocketChannel→zio.http.WebSocketFramezio.http.netty.server→zio.http.Driver
- Direction
- netty uses zio.http, so a change to zio.http can break netty, while a change to netty can't break zio.http.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
38→1 endpoint.openapi.OpenAPI uses gen.smithy.Smithy.SimpleShapes✕
- Connections
- 2 pairs of types, where a type in endpoint.openapi.OpenAPI uses a type in gen.smithy.Smithy.SimpleShapes.
- The types involved
zio.http.endpoint.openapi.OpenAPI.Operation→zio.http.gen.smithy.Smithy.SimpleShapes.Listzio.http.endpoint.openapi.OpenAPI.PathItem→zio.http.gen.smithy.Smithy.SimpleShapes.List
- Direction
- endpoint.openapi.OpenAPI uses gen.smithy.Smithy.SimpleShapes, so a change to gen.smithy.Smithy.SimpleShapes can break endpoint.openapi.OpenAPI, while a change to endpoint.openapi.OpenAPI can't break gen.smithy.Smithy.SimpleShapes.
- Position
- Below the diagonal: endpoint.openapi.OpenAPI uses a module listed above it, which is the healthy direction.
38→4 endpoint.openapi.OpenAPI uses endpoint.cli.HttpOptions✕
- Connections
- 3 pairs of types, where a type in endpoint.openapi.OpenAPI uses a type in endpoint.cli.HttpOptions.
- The types involved
zio.http.endpoint.openapi.OpenAPI.Components→zio.http.endpoint.cli.HttpOptions.Headerzio.http.endpoint.openapi.OpenAPI.Encoding→zio.http.endpoint.cli.HttpOptions.Headerzio.http.endpoint.openapi.OpenAPI.Response→zio.http.endpoint.cli.HttpOptions.Header
- Direction
- endpoint.openapi.OpenAPI uses endpoint.cli.HttpOptions, so a change to endpoint.cli.HttpOptions can break endpoint.openapi.OpenAPI, while a change to endpoint.openapi.OpenAPI can't break endpoint.cli.HttpOptions.
- Position
- Below the diagonal: endpoint.openapi.OpenAPI uses a module listed above it, which is the healthy direction.
38→6 endpoint.openapi.OpenAPI uses gen.scala.Code.Collection✕
- Connections
- 12 pairs of types, where a type in endpoint.openapi.OpenAPI uses a type in gen.scala.Code.Collection.
- The types involved
zio.http.endpoint.openapi.OpenAPI.Callback→zio.http.gen.scala.Code.Collection.Mapzio.http.endpoint.openapi.OpenAPI.Discriminator→zio.http.gen.scala.Code.Collection.Mapzio.http.endpoint.openapi.OpenAPI.Encoding→zio.http.gen.scala.Code.Collection.Mapzio.http.endpoint.openapi.OpenAPI.Link→zio.http.gen.scala.Code.Collection.Mapzio.http.endpoint.openapi.OpenAPI.MediaType→zio.http.gen.scala.Code.Collection.Mapzio.http.endpoint.openapi.OpenAPI.Operation→zio.http.gen.scala.Code.Collection.Mapzio.http.endpoint.openapi.OpenAPI.Operation→zio.http.gen.scala.Code.Collection.Setzio.http.endpoint.openapi.OpenAPI.Parameter→zio.http.gen.scala.Code.Collection.Mapzio.http.endpoint.openapi.OpenAPI.PathItem→zio.http.gen.scala.Code.Collection.Setzio.http.endpoint.openapi.OpenAPI.RequestBody→zio.http.gen.scala.Code.Collection.Mapzio.http.endpoint.openapi.OpenAPI.Response→zio.http.gen.scala.Code.Collection.Mapzio.http.endpoint.openapi.OpenAPI.Server→zio.http.gen.scala.Code.Collection.Map
- Direction
- endpoint.openapi.OpenAPI uses gen.scala.Code.Collection, so a change to gen.scala.Code.Collection can break endpoint.openapi.OpenAPI, while a change to endpoint.openapi.OpenAPI can't break gen.scala.Code.Collection.
- Position
- Below the diagonal: endpoint.openapi.OpenAPI uses a module listed above it, which is the healthy direction.
38→10 endpoint.openapi.OpenAPI uses gen.smithy.SmithyTrait✕
- Connections
- 2 pairs of types, where a type in endpoint.openapi.OpenAPI uses a type in gen.smithy.SmithyTrait.
- The types involved
zio.http.endpoint.openapi.OpenAPI.RequestBody→zio.http.gen.smithy.SmithyTrait.MediaTypezio.http.endpoint.openapi.OpenAPI.Response→zio.http.gen.smithy.SmithyTrait.MediaType
- Direction
- endpoint.openapi.OpenAPI uses gen.smithy.SmithyTrait, so a change to gen.smithy.SmithyTrait can break endpoint.openapi.OpenAPI, while a change to endpoint.openapi.OpenAPI can't break gen.smithy.SmithyTrait.
- Position
- Below the diagonal: endpoint.openapi.OpenAPI uses a module listed above it, which is the healthy direction.
38→11 endpoint.openapi.OpenAPI uses ErrorResponseConfig.ErrorFormat✕
- Connections
- 1 pair of types, where a type in endpoint.openapi.OpenAPI uses a type in ErrorResponseConfig.ErrorFormat.
- The types involved
zio.http.endpoint.openapi.OpenAPI.Example→zio.http.ErrorResponseConfig.ErrorFormat.Json
- Direction
- endpoint.openapi.OpenAPI uses ErrorResponseConfig.ErrorFormat, so a change to ErrorResponseConfig.ErrorFormat can break endpoint.openapi.OpenAPI, while a change to endpoint.openapi.OpenAPI can't break ErrorResponseConfig.ErrorFormat.
- Position
- Below the diagonal: endpoint.openapi.OpenAPI uses a module listed above it, which is the healthy direction.
38→15 endpoint.openapi.OpenAPI uses codec✕
- Connections
- 14 pairs of types, where a type in endpoint.openapi.OpenAPI uses a type in codec.
- The types involved
zio.http.endpoint.openapi.OpenAPI.Example→zio.http.codec.Doczio.http.endpoint.openapi.OpenAPI.ExternalDoc→zio.http.codec.Doczio.http.endpoint.openapi.OpenAPI.Header→zio.http.codec.Doczio.http.endpoint.openapi.OpenAPI.Info→zio.http.codec.Doczio.http.endpoint.openapi.OpenAPI.Link→zio.http.codec.Doczio.http.endpoint.openapi.OpenAPI.Operation→zio.http.codec.Doczio.http.endpoint.openapi.OpenAPI.Parameter→zio.http.codec.Doczio.http.endpoint.openapi.OpenAPI.PathItem→zio.http.codec.Doczio.http.endpoint.openapi.OpenAPI.RequestBody→zio.http.codec.Doczio.http.endpoint.openapi.OpenAPI.Response→zio.http.codec.Doczio.http.endpoint.openapi.OpenAPI.SecurityScheme→zio.http.codec.Doczio.http.endpoint.openapi.OpenAPI.Server→zio.http.codec.Doczio.http.endpoint.openapi.OpenAPI.ServerVariable→zio.http.codec.Doczio.http.endpoint.openapi.OpenAPI.Tag→zio.http.codec.Doc
- Direction
- endpoint.openapi.OpenAPI uses codec, so a change to codec can break endpoint.openapi.OpenAPI, while a change to endpoint.openapi.OpenAPI can't break codec.
- Position
- Below the diagonal: endpoint.openapi.OpenAPI uses a module listed above it, which is the healthy direction.
38→20 endpoint.openapi.OpenAPI uses gen.scala.Code.CodecType✕
- Connections
- 28 pairs of types, where a type in endpoint.openapi.OpenAPI uses a type in gen.scala.Code.CodecType. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
zio.http.endpoint.openapi.OpenAPI.Callback→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.OpenAPI.Contact→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.OpenAPI.Discriminator→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.OpenAPI.Encoding→zio.http.gen.scala.Code.CodecType.Booleanzio.http.endpoint.openapi.OpenAPI.Encoding→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.OpenAPI.Example→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.OpenAPI.Header→zio.http.gen.scala.Code.CodecType.Booleanzio.http.endpoint.openapi.OpenAPI.Info→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.OpenAPI.Key→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.OpenAPI.License→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.OpenAPI.Link→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.OpenAPI.MediaType→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.OpenAPI.Operation→zio.http.gen.scala.Code.CodecType.Booleanzio.http.endpoint.openapi.OpenAPI.Operation→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.OpenAPI.Parameter→zio.http.gen.scala.Code.CodecType.Booleanzio.http.endpoint.openapi.OpenAPI.Parameter→zio.http.gen.scala.Code.CodecType.Intzio.http.endpoint.openapi.OpenAPI.Parameter→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.OpenAPI.Path→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.OpenAPI.PathItem→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.OpenAPI.RequestBody→zio.http.gen.scala.Code.CodecType.Booleanzio.http.endpoint.openapi.OpenAPI.RequestBody→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.OpenAPI.Response→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.OpenAPI.Server→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.OpenAPI.ServerVariable→zio.http.gen.scala.Code.CodecType.Stringzio.http.endpoint.openapi.OpenAPI.StatusOrDefault→zio.http.gen.scala.Code.CodecType.String
- Direction
- endpoint.openapi.OpenAPI uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break endpoint.openapi.OpenAPI, while a change to endpoint.openapi.OpenAPI can't break gen.scala.Code.CodecType.
- Position
- Below the diagonal: endpoint.openapi.OpenAPI uses a module listed above it, which is the healthy direction.
38→28 endpoint.openapi.OpenAPI uses Cookie✕
- Connections
- 2 pairs of types, where a type in endpoint.openapi.OpenAPI uses a type in Cookie.
- The types involved
zio.http.endpoint.openapi.OpenAPI.Components→zio.http.Cookie.Responsezio.http.endpoint.openapi.OpenAPI.Operation→zio.http.Cookie.Response
- Direction
- endpoint.openapi.OpenAPI uses Cookie, so a change to Cookie can break endpoint.openapi.OpenAPI, while a change to endpoint.openapi.OpenAPI can't break Cookie.
- Position
- Below the diagonal: endpoint.openapi.OpenAPI uses a module listed above it, which is the healthy direction.
38→29 endpoint.openapi.OpenAPI uses Header✕
- Connections
- 2 pairs of types, where a type in endpoint.openapi.OpenAPI uses a type in Header.
- The types involved
zio.http.endpoint.openapi.OpenAPI.Components→zio.http.Header.Linkzio.http.endpoint.openapi.OpenAPI.Response→zio.http.Header.Link
- Direction
- endpoint.openapi.OpenAPI uses Header, so a change to Header can break endpoint.openapi.OpenAPI, while a change to endpoint.openapi.OpenAPI can't break Header.
- Position
- Below the diagonal: endpoint.openapi.OpenAPI uses a module listed above it, which is the healthy direction.
38→30 endpoint.openapi.OpenAPI uses Header.AcceptLanguage✕
- Connections
- 1 pair of types, where a type in endpoint.openapi.OpenAPI uses a type in Header.AcceptLanguage.
- The types involved
zio.http.endpoint.openapi.OpenAPI.Parameter→zio.http.Header.AcceptLanguage.Any
- Direction
- endpoint.openapi.OpenAPI uses Header.AcceptLanguage, so a change to Header.AcceptLanguage can break endpoint.openapi.OpenAPI, while a change to endpoint.openapi.OpenAPI can't break Header.AcceptLanguage.
- Position
- Below the diagonal: endpoint.openapi.OpenAPI uses a module listed above it, which is the healthy direction.
38→36 endpoint.openapi.OpenAPI uses endpoint.openapi✕
- Connections
- 5 pairs of types, where a type in endpoint.openapi.OpenAPI uses a type in endpoint.openapi.
- The types involved
zio.http.endpoint.openapi.OpenAPI.Components→zio.http.endpoint.openapi.JsonSchemazio.http.endpoint.openapi.OpenAPI.Header→zio.http.endpoint.openapi.JsonSchemazio.http.endpoint.openapi.OpenAPI.MediaType→zio.http.endpoint.openapi.JsonSchemazio.http.endpoint.openapi.OpenAPI.Parameter→zio.http.endpoint.openapi.JsonSchemazio.http.endpoint.openapi.OpenAPI.ReferenceOr→zio.http.endpoint.openapi.JsonSchema
- Direction
- endpoint.openapi.OpenAPI uses endpoint.openapi, so a change to endpoint.openapi can break endpoint.openapi.OpenAPI, while a change to endpoint.openapi.OpenAPI can't break endpoint.openapi.
- Position
- Below the diagonal: endpoint.openapi.OpenAPI uses a module listed above it, which is the healthy direction.
39→1 zio.http uses gen.smithy.Smithy.SimpleShapes✕
- Connections
- 10 pairs of types, where a type in zio.http uses a type in gen.smithy.Smithy.SimpleShapes.
- The types involved
zio.http.Body→zio.http.gen.smithy.Smithy.SimpleShapes.Bytezio.http.Boundary→zio.http.gen.smithy.Smithy.SimpleShapes.Bytezio.http.Form→zio.http.gen.smithy.Smithy.SimpleShapes.Bytezio.http.FormField→zio.http.gen.smithy.Smithy.SimpleShapes.Bytezio.http.MediaType→zio.http.gen.smithy.Smithy.SimpleShapes.Listzio.http.MediaTypes→zio.http.gen.smithy.Smithy.SimpleShapes.Listzio.http.QueryParams→zio.http.gen.smithy.Smithy.SimpleShapes.Listzio.http.RoutePattern→zio.http.gen.smithy.Smithy.SimpleShapes.Listzio.http.RoutesOverview→zio.http.gen.smithy.Smithy.SimpleShapes.Listzio.http.StreamingForm→zio.http.gen.smithy.Smithy.SimpleShapes.Byte
- Direction
- zio.http uses gen.smithy.Smithy.SimpleShapes, so a change to gen.smithy.Smithy.SimpleShapes can break zio.http, while a change to zio.http can't break gen.smithy.Smithy.SimpleShapes.
- Position
- Below the diagonal: zio.http uses a module listed above it, which is the healthy direction.
39→2 zio.http uses Header.Vary✕
- Connections
- 12 pairs of types, where a type in zio.http uses a type in Header.Vary.
- The types involved
zio.http.Boundary→zio.http.Header.Vary.Headerszio.http.Handler→zio.http.Header.Vary.Headerszio.http.HandlerAspect→zio.http.Header.Vary.Headerszio.http.HandlerAspects→zio.http.Header.Vary.Headerszio.http.Headers→zio.http.Header.Vary.Headerszio.http.Proxy→zio.http.Header.Vary.Headerszio.http.Request→zio.http.Header.Vary.Headerszio.http.Response→zio.http.Header.Vary.Headerszio.http.Routes→zio.http.Header.Vary.Headerszio.http.TestClient→zio.http.Header.Vary.Headerszio.http.WebSocketApp→zio.http.Header.Vary.Headerszio.http.ZClient→zio.http.Header.Vary.Headers
- Direction
- zio.http uses Header.Vary, so a change to Header.Vary can break zio.http, while a change to zio.http can't break Header.Vary.
- Position
- Below the diagonal: zio.http uses a module listed above it, which is the healthy direction.
39→3 zio.http uses URL✕
- Connections
- 15 pairs of types, where a type in zio.http uses a type in URL.
- The types involved
zio.http.CanServe→zio.http.URL.Errzio.http.Channel→zio.http.URL.Errzio.http.Handler→zio.http.URL.Errzio.http.HandlerAspect→zio.http.URL.Errzio.http.Middleware→zio.http.URL.Errzio.http.ProtocolStack→zio.http.URL.Errzio.http.Route→zio.http.URL.Errzio.http.RoutePattern→zio.http.URL.Errzio.http.Routes→zio.http.URL.Errzio.http.TestChannel→zio.http.URL.Errzio.http.ToHandler→zio.http.URL.Errzio.http.URL→zio.http.URL.Fragmentzio.http.WithContext→zio.http.URL.Errzio.http.ZClient→zio.http.URL.Errzio.http.ZClientAspect→zio.http.URL.Err
- Direction
- zio.http uses URL, so a change to URL can break zio.http, while a change to zio.http can't break URL.
- Position
- Below the diagonal: zio.http uses a module listed above it, which is the healthy direction.
39→4 zio.http uses endpoint.cli.HttpOptions✕
- Connections
- 17 pairs of types, where a type in zio.http uses a type in endpoint.cli.HttpOptions.
- The types involved
zio.http.Body→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.Cookie→zio.http.endpoint.cli.HttpOptions.Pathzio.http.Handler→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.Handler→zio.http.endpoint.cli.HttpOptions.Pathzio.http.HandlerAspects→zio.http.endpoint.cli.HttpOptions.Pathzio.http.Headers→zio.http.endpoint.cli.HttpOptions.Headerzio.http.Path→zio.http.endpoint.cli.HttpOptions.Pathzio.http.Request→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.Request→zio.http.endpoint.cli.HttpOptions.Pathzio.http.Response→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.RoutePattern→zio.http.endpoint.cli.HttpOptions.Pathzio.http.Routes→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.Routes→zio.http.endpoint.cli.HttpOptions.Pathzio.http.TestClient→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.URL→zio.http.endpoint.cli.HttpOptions.Pathzio.http.ZClient→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.ZClient→zio.http.endpoint.cli.HttpOptions.Path
- Direction
- zio.http uses endpoint.cli.HttpOptions, so a change to endpoint.cli.HttpOptions can break zio.http, while a change to zio.http can't break endpoint.cli.HttpOptions.
- Position
- Below the diagonal: zio.http uses a module listed above it, which is the healthy direction.
39→5 zio.http uses gen.grpc.Protobuf✕
- Connections
- 8 pairs of types, where a type in zio.http uses a type in gen.grpc.Protobuf.
- The types involved
zio.http.Handler→zio.http.gen.grpc.Protobuf.Methodzio.http.HandlerAspects→zio.http.gen.grpc.Protobuf.Methodzio.http.Method→zio.http.gen.grpc.Protobuf.Methodzio.http.Request→zio.http.gen.grpc.Protobuf.Methodzio.http.RoutePattern→zio.http.gen.grpc.Protobuf.Methodzio.http.Routes→zio.http.gen.grpc.Protobuf.Methodzio.http.TestClient→zio.http.gen.grpc.Protobuf.Methodzio.http.ZClient→zio.http.gen.grpc.Protobuf.Method
- Direction
- zio.http uses gen.grpc.Protobuf, so a change to gen.grpc.Protobuf can break zio.http, while a change to zio.http can't break gen.grpc.Protobuf.
- Position
- Below the diagonal: zio.http uses a module listed above it, which is the healthy direction.
39→6 zio.http uses gen.scala.Code.Collection✕
- Connections
- 8 pairs of types, where a type in zio.http uses a type in gen.scala.Code.Collection.
- The types involved
zio.http.Form→zio.http.gen.scala.Code.Collection.Mapzio.http.HandlerAspects→zio.http.gen.scala.Code.Collection.Setzio.http.MediaType→zio.http.gen.scala.Code.Collection.Mapzio.http.QueryParams→zio.http.gen.scala.Code.Collection.Mapzio.http.QueryParams→zio.http.gen.scala.Code.Collection.Seqzio.http.RequestStore→zio.http.gen.scala.Code.Collection.Mapzio.http.RoutesOverview→zio.http.gen.scala.Code.Collection.Seqzio.http.SSLConfig→zio.http.gen.scala.Code.Collection.Seq
- Direction
- zio.http uses gen.scala.Code.Collection, so a change to gen.scala.Code.Collection can break zio.http, while a change to zio.http can't break gen.scala.Code.Collection.
- Position
- Below the diagonal: zio.http uses a module listed above it, which is the healthy direction.
39→7 zio.http uses gen.scala.Code.ScalaType✕
- Connections
- 16 pairs of types, where a type in zio.http uses a type in gen.scala.Code.ScalaType.
- The types involved
zio.http.Channel→zio.http.gen.scala.Code.ScalaType.Unitzio.http.ConnectionPool→zio.http.gen.scala.Code.ScalaType.Unitzio.http.DateEncodingBenchmark→zio.http.gen.scala.Code.ScalaType.Unitzio.http.Driver→zio.http.gen.scala.Code.ScalaType.Unitzio.http.Handler→zio.http.gen.scala.Code.ScalaType.Unitzio.http.HandlerAspect→zio.http.gen.scala.Code.ScalaType.Unitzio.http.HandlerAspects→zio.http.gen.scala.Code.ScalaType.Unitzio.http.QueryEncodingBenchmark→zio.http.gen.scala.Code.ScalaType.Unitzio.http.RequestStore→zio.http.gen.scala.Code.ScalaType.Unitzio.http.Route→zio.http.gen.scala.Code.ScalaType.Unitzio.http.RoutePattern→zio.http.gen.scala.Code.ScalaType.Unitzio.http.Routes→zio.http.gen.scala.Code.ScalaType.Unitzio.http.Server→zio.http.gen.scala.Code.ScalaType.Unitzio.http.TestChannel→zio.http.gen.scala.Code.ScalaType.Unitzio.http.TestClient→zio.http.gen.scala.Code.ScalaType.Unitzio.http.TestServer→zio.http.gen.scala.Code.ScalaType.Unit
- Direction
- zio.http uses gen.scala.Code.ScalaType, so a change to gen.scala.Code.ScalaType can break zio.http, while a change to zio.http can't break gen.scala.Code.ScalaType.
- Position
- Below the diagonal: zio.http uses a module listed above it, which is the healthy direction.
39→10 zio.http uses gen.smithy.SmithyTrait✕
- Connections
- 5 pairs of types, where a type in zio.http uses a type in gen.smithy.SmithyTrait.
- The types involved
zio.http.Body→zio.http.gen.smithy.SmithyTrait.MediaTypezio.http.FormField→zio.http.gen.smithy.SmithyTrait.MediaTypezio.http.MediaType→zio.http.gen.smithy.SmithyTrait.MediaTypezio.http.MediaTypes→zio.http.gen.smithy.SmithyTrait.MediaTypezio.http.Response→zio.http.gen.smithy.SmithyTrait.MediaType
- Direction
- zio.http uses gen.smithy.SmithyTrait, so a change to gen.smithy.SmithyTrait can break zio.http, while a change to zio.http can't break gen.smithy.SmithyTrait.
- Position
- Below the diagonal: zio.http uses a module listed above it, which is the healthy direction.
39→11 zio.http uses ErrorResponseConfig.ErrorFormat✕
- Connections
- 1 pair of types, where a type in zio.http uses a type in ErrorResponseConfig.ErrorFormat.
- The types involved
zio.http.Flash→zio.http.ErrorResponseConfig.ErrorFormat.Html
- Direction
- zio.http uses ErrorResponseConfig.ErrorFormat, so a change to ErrorResponseConfig.ErrorFormat can break zio.http, while a change to zio.http can't break ErrorResponseConfig.ErrorFormat.
- Position
- Below the diagonal: zio.http uses a module listed above it, which is the healthy direction.
39→12 zio.http uses internal✕
- Connections
- 9 pairs of types, where a type in zio.http uses a type in internal.
- The types involved
zio.http.ClientDriver→zio.http.internal.ChannelStatezio.http.HandlerAspects→zio.http.internal.HeaderModifierzio.http.Headers→zio.http.internal.HeaderOpszio.http.QueryParams→zio.http.internal.QueryOpszio.http.Request→zio.http.internal.HeaderOpszio.http.Request→zio.http.internal.QueryOpszio.http.Response→zio.http.internal.HeaderOpszio.http.URL→zio.http.internal.QueryOpszio.http.ZClient→zio.http.internal.HeaderOps
- Direction
- zio.http uses internal, so a change to internal can break zio.http, while a change to zio.http can't break internal.
- Position
- Below the diagonal: zio.http uses a module listed above it, which is the healthy direction.
39→15 zio.http uses codec✕
- Connections
- 7 pairs of types, where a type in zio.http uses a type in codec.
- The types involved
zio.http.Method→zio.http.codec.PathCodeczio.http.Route→zio.http.codec.PathCodeczio.http.RoutePattern→zio.http.codec.Combinerzio.http.RoutePattern→zio.http.codec.Doczio.http.RoutePattern→zio.http.codec.HttpCodeczio.http.RoutePattern→zio.http.codec.PathCodeczio.http.Routes→zio.http.codec.PathCodec
- Direction
- zio.http uses codec, so a change to codec can break zio.http, while a change to zio.http can't break codec.
- Position
- Below the diagonal: zio.http uses a module listed above it, which is the healthy direction.
39→18 zio.http uses endpoint.cli.Retriever✕
- Connections
- 8 pairs of types, where a type in zio.http uses a type in endpoint.cli.Retriever.
- The types involved
zio.http.HandlerAspects→zio.http.endpoint.cli.Retriever.URLzio.http.Proxy→zio.http.endpoint.cli.Retriever.URLzio.http.Request→zio.http.endpoint.cli.Retriever.URLzio.http.TestClient→zio.http.endpoint.cli.Retriever.URLzio.http.URL→zio.http.endpoint.cli.Retriever.URLzio.http.UrlInterpolatorMacro→zio.http.endpoint.cli.Retriever.URLzio.http.WebSocketApp→zio.http.endpoint.cli.Retriever.URLzio.http.ZClient→zio.http.endpoint.cli.Retriever.URL
- Direction
- zio.http uses endpoint.cli.Retriever, so a change to endpoint.cli.Retriever can break zio.http, while a change to zio.http can't break endpoint.cli.Retriever.
- Position
- Below the diagonal: zio.http uses a module listed above it, which is the healthy direction.
39→20 zio.http uses gen.scala.Code.CodecType✕
- Connections
- 75 pairs of types, where a type in zio.http uses a type in gen.scala.Code.CodecType. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
zio.http.Body→zio.http.gen.scala.Code.CodecType.Booleanzio.http.Body→zio.http.gen.scala.Code.CodecType.Longzio.http.Body→zio.http.gen.scala.Code.CodecType.Stringzio.http.Boundary→zio.http.gen.scala.Code.CodecType.Booleanzio.http.Boundary→zio.http.gen.scala.Code.CodecType.Stringzio.http.ClientDriver→zio.http.gen.scala.Code.CodecType.Booleanzio.http.ClientDriver→zio.http.gen.scala.Code.CodecType.Longzio.http.ConnectionPool→zio.http.gen.scala.Code.CodecType.Booleanzio.http.ConnectionPool→zio.http.gen.scala.Code.CodecType.Intzio.http.Cookie→zio.http.gen.scala.Code.CodecType.Booleanzio.http.Cookie→zio.http.gen.scala.Code.CodecType.Stringzio.http.Credentials→zio.http.gen.scala.Code.CodecType.Stringzio.http.Decompression→zio.http.gen.scala.Code.CodecType.Booleanzio.http.DnsResolver→zio.http.gen.scala.Code.CodecType.Stringzio.http.ErrorResponseConfig→zio.http.gen.scala.Code.CodecType.Booleanzio.http.ErrorResponseConfig→zio.http.gen.scala.Code.CodecType.Intzio.http.Form→zio.http.gen.scala.Code.CodecType.Stringzio.http.FormDecodingError→zio.http.gen.scala.Code.CodecType.Stringzio.http.FormField→zio.http.gen.scala.Code.CodecType.Stringzio.http.HandlerAspects→zio.http.gen.scala.Code.CodecType.Booleanzio.http.HandlerAspects→zio.http.gen.scala.Code.CodecType.Stringzio.http.HandlerPlatformSpecific→zio.http.gen.scala.Code.CodecType.Stringzio.http.Header→zio.http.gen.scala.Code.CodecType.Stringzio.http.Headers→zio.http.gen.scala.Code.CodecType.Booleanzio.http.Headers→zio.http.gen.scala.Code.CodecType.String
- Direction
- zio.http uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break zio.http, while a change to zio.http can't break gen.scala.Code.CodecType.
- Position
- Below the diagonal: zio.http uses a module listed above it, which is the healthy direction.
39→22 zio.http uses gen.openapi✕
- Connections
- 3 pairs of types, where a type in zio.http uses a type in gen.openapi.
- The types involved
zio.http.DriverPlatformSpecific→zio.http.gen.openapi.Configzio.http.ServerPlatformSpecific→zio.http.gen.openapi.Configzio.http.ZClientPlatformSpecific→zio.http.gen.openapi.Config
- Direction
- zio.http uses gen.openapi, so a change to gen.openapi can break zio.http, while a change to zio.http can't break gen.openapi.
- Position
- Below the diagonal: zio.http uses a module listed above it, which is the healthy direction.
39→23 zio.http uses template✕
- Connections
- 4 pairs of types, where a type in zio.http uses a type in template.
- The types involved
zio.http.LowPriorityTemplateImplicits→zio.http.template.Domzio.http.RoutesOverview→zio.http.template.Domzio.http.template→zio.http.template.Elementszio.http.template2→zio.http.template.Dom
- Direction
- zio.http uses template, so a change to template can break zio.http, while a change to zio.http can't break template.
- Position
- Below the diagonal: zio.http uses a module listed above it, which is the healthy direction.
39→25 zio.http uses template2✕
- Connections
- 5 pairs of types, where a type in zio.http uses a type in template2.
- The types involved
zio.http.template2→zio.http.template2.CssInterpolatorzio.http.template2→zio.http.template2.HtmlAttributeszio.http.template2→zio.http.template2.HtmlElementszio.http.template2→zio.http.template2.JsInterpolatorzio.http.template2→zio.http.template2.Modifier
- Direction
- zio.http uses template2, so a change to template2 can break zio.http, while a change to zio.http can't break template2.
- Position
- Below the diagonal: zio.http uses a module listed above it, which is the healthy direction.
39→27 zio.http uses datastar.Attributes.OnIntervalModifier✕
- Connections
- 6 pairs of types, where a type in zio.http uses a type in datastar.Attributes.OnIntervalModifier.
- The types involved
zio.http.ConnectionPool→zio.http.datastar.Attributes.OnIntervalModifier.Durationzio.http.Cookie→zio.http.datastar.Attributes.OnIntervalModifier.Durationzio.http.Handler→zio.http.datastar.Attributes.OnIntervalModifier.Durationzio.http.Routes→zio.http.datastar.Attributes.OnIntervalModifier.Durationzio.http.ServerSentEvent→zio.http.datastar.Attributes.OnIntervalModifier.Durationzio.http.WebSocketConfig→zio.http.datastar.Attributes.OnIntervalModifier.Duration
- Direction
- zio.http uses datastar.Attributes.OnIntervalModifier, so a change to datastar.Attributes.OnIntervalModifier can break zio.http, while a change to zio.http can't break datastar.Attributes.OnIntervalModifier.
- Position
- Below the diagonal: zio.http uses a module listed above it, which is the healthy direction.
39→28 zio.http uses Cookie✕
- Connections
- 35 pairs of types, where a type in zio.http uses a type in Cookie. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
zio.http.CanServe→zio.http.Cookie.Responsezio.http.ClientDriver→zio.http.Cookie.Requestzio.http.ClientDriver→zio.http.Cookie.Responsezio.http.Cookie→zio.http.Cookie.Requestzio.http.Cookie→zio.http.Cookie.Responsezio.http.Cookie→zio.http.Cookie.SameSitezio.http.Driver→zio.http.Cookie.Responsezio.http.Handler→zio.http.Cookie.Requestzio.http.Handler→zio.http.Cookie.Responsezio.http.HandlerAspect→zio.http.Cookie.Requestzio.http.HandlerAspect→zio.http.Cookie.Responsezio.http.HandlerAspects→zio.http.Cookie.Requestzio.http.HandlerAspects→zio.http.Cookie.Responsezio.http.HandlerConstructorLowPriorityImplicits1→zio.http.Cookie.Responsezio.http.HandlerConstructorLowPriorityImplicits4→zio.http.Cookie.Responsezio.http.HandlerPlatformSpecific→zio.http.Cookie.Responsezio.http.Request→zio.http.Cookie.Requestzio.http.RequestHandlerInput→zio.http.Cookie.Requestzio.http.RequestStore→zio.http.Cookie.Requestzio.http.Response→zio.http.Cookie.Responsezio.http.Route→zio.http.Cookie.Requestzio.http.Route→zio.http.Cookie.Responsezio.http.RoutePattern→zio.http.Cookie.Requestzio.http.RoutePattern→zio.http.Cookie.Responsezio.http.Routes→zio.http.Cookie.Request
- Direction
- zio.http uses Cookie, so a change to Cookie can break zio.http, while a change to zio.http can't break Cookie.
- Position
- Below the diagonal: zio.http uses a module listed above it, which is the healthy direction.
39→29 zio.http uses Header✕
- Connections
- 6 pairs of types, where a type in zio.http uses a type in Header.
- The types involved
zio.http.ClientDriver→zio.http.Header.Connectionzio.http.ConnectionPool→zio.http.Header.Connectionzio.http.Handler→zio.http.Header.HeaderTypezio.http.HandlerAspects→zio.http.Header.HeaderTypeBasezio.http.Headers→zio.http.Header.HeaderTypezio.http.URL→zio.http.Header.Location
- Direction
- zio.http uses Header, so a change to Header can break zio.http, while a change to zio.http can't break Header.
- Position
- Below the diagonal: zio.http uses a module listed above it, which is the healthy direction.
39→30 zio.http uses Header.AcceptLanguage✕
- Connections
- 28 pairs of types, where a type in zio.http uses a type in Header.AcceptLanguage. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
zio.http.Body→zio.http.Header.AcceptLanguage.Anyzio.http.ConnectionPool→zio.http.Header.AcceptLanguage.Anyzio.http.DnsResolver→zio.http.Header.AcceptLanguage.Anyzio.http.Form→zio.http.Header.AcceptLanguage.Anyzio.http.FormField→zio.http.Header.AcceptLanguage.Anyzio.http.Handler→zio.http.Header.AcceptLanguage.Anyzio.http.HandlerAspect→zio.http.Header.AcceptLanguage.Anyzio.http.HandlerAspects→zio.http.Header.AcceptLanguage.Anyzio.http.HandlerConstructorLowPriorityImplicits1→zio.http.Header.AcceptLanguage.Anyzio.http.HandlerConstructorLowPriorityImplicits3→zio.http.Header.AcceptLanguage.Anyzio.http.HandlerConstructorLowPriorityImplicits4→zio.http.Header.AcceptLanguage.Anyzio.http.HandlerPlatformSpecific→zio.http.Header.AcceptLanguage.Anyzio.http.Path→zio.http.Header.AcceptLanguage.Anyzio.http.ProtocolStack→zio.http.Header.AcceptLanguage.Anyzio.http.QueryParams→zio.http.Header.AcceptLanguage.Anyzio.http.Request→zio.http.Header.AcceptLanguage.Anyzio.http.RequestStore→zio.http.Header.AcceptLanguage.Anyzio.http.Response→zio.http.Header.AcceptLanguage.Anyzio.http.Route→zio.http.Header.AcceptLanguage.Anyzio.http.Routes→zio.http.Header.AcceptLanguage.Anyzio.http.Status→zio.http.Header.AcceptLanguage.Anyzio.http.StreamingForm→zio.http.Header.AcceptLanguage.Anyzio.http.TestClient→zio.http.Header.AcceptLanguage.Anyzio.http.TestServer→zio.http.Header.AcceptLanguage.Anyzio.http.URL→zio.http.Header.AcceptLanguage.Any
- Direction
- zio.http uses Header.AcceptLanguage, so a change to Header.AcceptLanguage can break zio.http, while a change to zio.http can't break Header.AcceptLanguage.
- Position
- Below the diagonal: zio.http uses a module listed above it, which is the healthy direction.
39→31 zio.http uses Body✕
- Connections
- 1 pair of types, where a type in zio.http uses a type in Body.
- The types involved
zio.http.Body→zio.http.Body.ContentType
- Direction
- zio.http uses Body, so a change to Body can break zio.http, while a change to zio.http can't break Body.
- Position
- Below the diagonal: zio.http uses a module listed above it, which is the healthy direction.
39→32 zio.http uses ZClient✕
- Connections
- 2 pairs of types, where a type in zio.http uses a type in ZClient.
- The types involved
zio.http.ZClient→zio.http.ZClient.BodyDecoderzio.http.ZClient→zio.http.ZClient.BodyEncoder
- Direction
- zio.http uses ZClient, so a change to ZClient can break zio.http, while a change to zio.http can't break ZClient.
- Position
- Below the diagonal: zio.http uses a module listed above it, which is the healthy direction.
39→33 zio.http uses datastar✕
- Connections
- 3 pairs of types, where a type in zio.http uses a type in datastar.
- The types involved
zio.http.datastar→zio.http.datastar.DatastarPackageBasezio.http.htmx→zio.http.datastar.Attributeszio.http.template→zio.http.datastar.Attributes
- Direction
- zio.http uses datastar, so a change to datastar can break zio.http, while a change to zio.http can't break datastar.
- Position
- Below the diagonal: zio.http uses a module listed above it, which is the healthy direction.
39→35 zio.http uses Handler✕
- Connections
- 2 pairs of types, where a type in zio.http uses a type in Handler.
- The types involved
zio.http.Handler→zio.http.Handler.ContraFlatMapzio.http.Handler→zio.http.Handler.IsRequest
- Direction
- zio.http uses Handler, so a change to Handler can break zio.http, while a change to zio.http can't break Handler.
- Position
- Below the diagonal: zio.http uses a module listed above it, which is the healthy direction.
39→37 zio.http uses netty✕
- Connections
- 2 pairs of types, where a type in zio.http uses a type in netty.
- The types involved
zio.http.TestChannel→zio.http.netty.WebSocketChannelzio.http.WebSocketApp→zio.http.netty.WebSocketChannel
- Direction
- zio.http uses netty, so a change to netty can break zio.http, while a change to zio.http can't break netty.
- Position
- Below the diagonal: zio.http uses a module listed above it, which is the healthy direction.
39→38 zio.http uses endpoint.openapi.OpenAPI✕
- Connections
- 6 pairs of types, where a type in zio.http uses a type in endpoint.openapi.OpenAPI.
- The types involved
zio.http.Handler→zio.http.endpoint.openapi.OpenAPI.Tagzio.http.RequestStore→zio.http.endpoint.openapi.OpenAPI.Tagzio.http.Routes→zio.http.endpoint.openapi.OpenAPI.Tagzio.http.WithContextConstructorLowPriorityImplicits1→zio.http.endpoint.openapi.OpenAPI.Tagzio.http.WithContextConstructorLowPriorityImplicits2→zio.http.endpoint.openapi.OpenAPI.Tagzio.http.WithContextConstructorLowPriorityImplicits3→zio.http.endpoint.openapi.OpenAPI.Tag
- Direction
- zio.http uses endpoint.openapi.OpenAPI, so a change to endpoint.openapi.OpenAPI can break zio.http, while a change to zio.http can't break endpoint.openapi.OpenAPI.
- Position
- Below the diagonal: zio.http uses a module listed above it, which is the healthy direction.
40→2 codec.internal.EncoderDecoder uses Header.Vary✕
- Connections
- 3 pairs of types, where a type in codec.internal.EncoderDecoder uses a type in Header.Vary.
- The types involved
zio.http.codec.internal.EncoderDecoder.Multiple→zio.http.Header.Vary.Headerszio.http.codec.internal.EncoderDecoder.Single→zio.http.Header.Vary.Headerszio.http.codec.internal.EncoderDecoder.Undefined→zio.http.Header.Vary.Headers
- Direction
- codec.internal.EncoderDecoder uses Header.Vary, so a change to Header.Vary can break codec.internal.EncoderDecoder, while a change to codec.internal.EncoderDecoder can't break Header.Vary.
- Position
- Below the diagonal: codec.internal.EncoderDecoder uses a module listed above it, which is the healthy direction.
40→4 codec.internal.EncoderDecoder uses endpoint.cli.HttpOptions✕
- Connections
- 4 pairs of types, where a type in codec.internal.EncoderDecoder uses a type in endpoint.cli.HttpOptions.
- The types involved
zio.http.codec.internal.EncoderDecoder.Multiple→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.codec.internal.EncoderDecoder.Single→zio.http.endpoint.cli.HttpOptions.Bodyzio.http.codec.internal.EncoderDecoder.Single→zio.http.endpoint.cli.HttpOptions.Pathzio.http.codec.internal.EncoderDecoder.Undefined→zio.http.endpoint.cli.HttpOptions.Body
- Direction
- codec.internal.EncoderDecoder uses endpoint.cli.HttpOptions, so a change to endpoint.cli.HttpOptions can break codec.internal.EncoderDecoder, while a change to codec.internal.EncoderDecoder can't break endpoint.cli.HttpOptions.
- Position
- Below the diagonal: codec.internal.EncoderDecoder uses a module listed above it, which is the healthy direction.
40→5 codec.internal.EncoderDecoder uses gen.grpc.Protobuf✕
- Connections
- 3 pairs of types, where a type in codec.internal.EncoderDecoder uses a type in gen.grpc.Protobuf.
- The types involved
zio.http.codec.internal.EncoderDecoder.Multiple→zio.http.gen.grpc.Protobuf.Methodzio.http.codec.internal.EncoderDecoder.Single→zio.http.gen.grpc.Protobuf.Methodzio.http.codec.internal.EncoderDecoder.Undefined→zio.http.gen.grpc.Protobuf.Method
- Direction
- codec.internal.EncoderDecoder uses gen.grpc.Protobuf, so a change to gen.grpc.Protobuf can break codec.internal.EncoderDecoder, while a change to codec.internal.EncoderDecoder can't break gen.grpc.Protobuf.
- Position
- Below the diagonal: codec.internal.EncoderDecoder uses a module listed above it, which is the healthy direction.
40→7 codec.internal.EncoderDecoder uses gen.scala.Code.ScalaType✕
- Connections
- 1 pair of types, where a type in codec.internal.EncoderDecoder uses a type in gen.scala.Code.ScalaType.
- The types involved
zio.http.codec.internal.EncoderDecoder.Single→zio.http.gen.scala.Code.ScalaType.Unit
- Direction
- codec.internal.EncoderDecoder uses gen.scala.Code.ScalaType, so a change to gen.scala.Code.ScalaType can break codec.internal.EncoderDecoder, while a change to codec.internal.EncoderDecoder can't break gen.scala.Code.ScalaType.
- Position
- Below the diagonal: codec.internal.EncoderDecoder uses a module listed above it, which is the healthy direction.
40→10 codec.internal.EncoderDecoder uses gen.smithy.SmithyTrait✕
- Connections
- 1 pair of types, where a type in codec.internal.EncoderDecoder uses a type in gen.smithy.SmithyTrait.
- The types involved
zio.http.codec.internal.EncoderDecoder.Single→zio.http.gen.smithy.SmithyTrait.MediaType
- Direction
- codec.internal.EncoderDecoder uses gen.smithy.SmithyTrait, so a change to gen.smithy.SmithyTrait can break codec.internal.EncoderDecoder, while a change to codec.internal.EncoderDecoder can't break gen.smithy.SmithyTrait.
- Position
- Below the diagonal: codec.internal.EncoderDecoder uses a module listed above it, which is the healthy direction.
40→14 codec.internal.EncoderDecoder uses codec.internal✕
- Connections
- 4 pairs of types, where a type in codec.internal.EncoderDecoder uses a type in codec.internal.
- The types involved
zio.http.codec.internal.EncoderDecoder.Multiple→zio.http.codec.internal.EncoderDecoderzio.http.codec.internal.EncoderDecoder.Single→zio.http.codec.internal.AtomizedCodecszio.http.codec.internal.EncoderDecoder.Single→zio.http.codec.internal.EncoderDecoderzio.http.codec.internal.EncoderDecoder.Undefined→zio.http.codec.internal.EncoderDecoder
- Direction
- codec.internal.EncoderDecoder uses codec.internal, so a change to codec.internal can break codec.internal.EncoderDecoder, while a change to codec.internal.EncoderDecoder can't break codec.internal.
- Position
- Below the diagonal: codec.internal.EncoderDecoder uses a module listed above it, which is the healthy direction.
40→15 codec.internal.EncoderDecoder uses codec✕
- Connections
- 5 pairs of types, where a type in codec.internal.EncoderDecoder uses a type in codec.
- The types involved
zio.http.codec.internal.EncoderDecoder.Multiple→zio.http.codec.CodecConfigzio.http.codec.internal.EncoderDecoder.Single→zio.http.codec.CodecConfigzio.http.codec.internal.EncoderDecoder.Single→zio.http.codec.HttpCodeczio.http.codec.internal.EncoderDecoder.Single→zio.http.codec.SimpleCodeczio.http.codec.internal.EncoderDecoder.Undefined→zio.http.codec.CodecConfig
- Direction
- codec.internal.EncoderDecoder uses codec, so a change to codec can break codec.internal.EncoderDecoder, while a change to codec.internal.EncoderDecoder can't break codec.
- Position
- Below the diagonal: codec.internal.EncoderDecoder uses a module listed above it, which is the healthy direction.
40→18 codec.internal.EncoderDecoder uses endpoint.cli.Retriever✕
- Connections
- 3 pairs of types, where a type in codec.internal.EncoderDecoder uses a type in endpoint.cli.Retriever.
- The types involved
zio.http.codec.internal.EncoderDecoder.Multiple→zio.http.endpoint.cli.Retriever.URLzio.http.codec.internal.EncoderDecoder.Single→zio.http.endpoint.cli.Retriever.URLzio.http.codec.internal.EncoderDecoder.Undefined→zio.http.endpoint.cli.Retriever.URL
- Direction
- codec.internal.EncoderDecoder uses endpoint.cli.Retriever, so a change to endpoint.cli.Retriever can break codec.internal.EncoderDecoder, while a change to codec.internal.EncoderDecoder can't break endpoint.cli.Retriever.
- Position
- Below the diagonal: codec.internal.EncoderDecoder uses a module listed above it, which is the healthy direction.
40→20 codec.internal.EncoderDecoder uses gen.scala.Code.CodecType✕
- Connections
- 1 pair of types, where a type in codec.internal.EncoderDecoder uses a type in gen.scala.Code.CodecType.
- The types involved
zio.http.codec.internal.EncoderDecoder.Single→zio.http.gen.scala.Code.CodecType.Boolean
- Direction
- codec.internal.EncoderDecoder uses gen.scala.Code.CodecType, so a change to gen.scala.Code.CodecType can break codec.internal.EncoderDecoder, while a change to codec.internal.EncoderDecoder can't break gen.scala.Code.CodecType.
- Position
- Below the diagonal: codec.internal.EncoderDecoder uses a module listed above it, which is the healthy direction.
40→30 codec.internal.EncoderDecoder uses Header.AcceptLanguage✕
- Connections
- 2 pairs of types, where a type in codec.internal.EncoderDecoder uses a type in Header.AcceptLanguage.
- The types involved
zio.http.codec.internal.EncoderDecoder.Single→zio.http.Header.AcceptLanguage.Anyzio.http.codec.internal.EncoderDecoder.Undefined→zio.http.Header.AcceptLanguage.Any
- Direction
- codec.internal.EncoderDecoder uses Header.AcceptLanguage, so a change to Header.AcceptLanguage can break codec.internal.EncoderDecoder, while a change to codec.internal.EncoderDecoder can't break Header.AcceptLanguage.
- Position
- Below the diagonal: codec.internal.EncoderDecoder uses a module listed above it, which is the healthy direction.
40→39 codec.internal.EncoderDecoder uses zio.http✕
- Connections
- 6 pairs of types, where a type in codec.internal.EncoderDecoder uses a type in zio.http.
- The types involved
zio.http.codec.internal.EncoderDecoder.Multiple→zio.http.Statuszio.http.codec.internal.EncoderDecoder.Single→zio.http.Formzio.http.codec.internal.EncoderDecoder.Single→zio.http.QueryParamszio.http.codec.internal.EncoderDecoder.Single→zio.http.Statuszio.http.codec.internal.EncoderDecoder.Single→zio.http.StreamingFormzio.http.codec.internal.EncoderDecoder.Undefined→zio.http.Status
- Direction
- codec.internal.EncoderDecoder uses zio.http, so a change to zio.http can break codec.internal.EncoderDecoder, while a change to codec.internal.EncoderDecoder can't break zio.http.
- Position
- Below the diagonal: codec.internal.EncoderDecoder uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 134 | High / Critical |
| A02:2025 — Security Misconfiguration | 14 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 8 | Medium |
| A07:2025 — Authentication Failures | 6 | High / Critical |
Roadmap
First, eliminate insecure TLS configurations by removing empty trust managers and hostname verifiers, ensuring all connections use proper certificate validation. Next, improve visual and motion safety by maintaining visible focus styles, respecting reduced-motion preferences, and fixing low-contrast colors. Then, enforce accessibility standards by integrating automated a11y checks into the test suite and CI pipeline to prevent regressions. Finally, correct page structure issues such as missing language attributes and landmarks, and resolve static analysis findings related to secret exposure in configuration files.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Stop accepting every TLS certificate: delete the trust manager whose `checkServerTrusted` is empty, the `HostnameVerifier` that returns `true`, `InsecureTrustManagerFactory` / `NoopHostnameVerifier` and `acceptAnyCertificate`, and trust a self-signed or private server by giving the client a trust store holding its CA — never by switching verification off. | +5.4 pts | Medium | Web-Security Posture |
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +4.6 pts | Medium | Visual & motion safety |
| Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2), REDACTED. | +1.8 pts | Low | Static Analysis (SAST) |
| Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge. | +2.4 pts | Medium | A11y enforcement |
| Resolve the 4 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED, REDACTED. | +1.1 pts | Low | Secrets (history) |
| Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. | +1.0 pts | Low | REDACTED Scanning |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.0 pts | Low | ADR Quality |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +1.8 pts | Medium | Page structure |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.1 | Slop | Secrets (history): REDACTED: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| zio-http-gen/src/main/scala/zio/http/gen/openapi/EndpointGen.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| zio-http/shared/src/main/scala/zio/http/internal/DateEncoding.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| zio-http/shared/src/main/scala/zio/http/endpoint/openapi/OpenAPIGen.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| zio-http/shared/src/main/scala/zio/http/endpoint/openapi/JsonSchema.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| zio-http/shared/src/main/scala/zio/http/endpoint/Endpoint.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| zio-http/shared/src/main/scala/zio/http/endpoint/http/HttpGen.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| zio-http/shared/src/main/scala/zio/http/StreamingForm.scala | 6.0 | Mixed | Explicit Debt: FixmeComment |
| zio-http/shared/src/main/scala/zio/http/Response.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| zio-http/shared/src/main/scala/zio/http/codec/HttpCodec.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| zio-http/shared/src/main/scala/zio/http/endpoint/openapi/OpenAPI.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| zio-http/shared/src/main/scala/zio/http/multipart/mixed/MultipartMixed.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| zio-http/jvm/src/test/scala/zio/http/endpoint/QueryParameterSpec.scala | 6.9 | Mixed | Explicit Debt: TodoComment |
How the grades work
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.
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.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 70 of 70 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 70 dimensions across the health lenses
- 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, 638 of 680 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a coverage step in CI (`scoverage`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.scala), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) and this repository declares an sbt build (repository root, 358 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D19 Documentation Quality — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `zio-http/shared/src/main/scala-3/zio/http/HandlerVersionSpecific.scala`, `zio-http/shared/src/main/scala-3/zio/http/RoutesCompanionVersionSpecific.scala`, `zio-http/shared/src/main/scala-3/zio/http/endpoint/extensions.scala`, `REDACTED` 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.
- D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
- AC6 Visual & motion safety — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 21 further occurrence(s) are not listed individually; the score already reflects all 61.
- AX2 Stateful singletons — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection singletons in C#, Spring/JSR-330/CDI singletons in Java and Kotlin, module state in Python request handlers, handler state in Go and Swift, Play controllers, Cask routes, Scalatra servlets, Finatra controllers, Akka/Pekko HTTP routes and JSR-330 singletons in Scala, Rails, Sinatra, Grape, Roda and Hanami handlers and Rack apps in Ruby, and module state in F# request handlers (Giraffe, Saturn, Falco, Oxpecker and Suave handlers and ASP.NET Core controllers) only, and this repository's product is written in Scala (Tapir) and Scala (ZIO HTTP) and Scala (http4s), which was left unread, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — -------------------- ERROR: failed to solve: hseeberger/scala-sbt:11.0.12_1.5.5_2.13.6: failed to resolve source metadata for docker.io/hseeberger/scala-sbt:11.0.12_1.5.5_2.13.6: failed to do request: Head "https://registry-1.docker.io/v2/hseeberger/scala-sbt/manifests/11.0.12_1.5.5_2.13.6": Forbidden; runtime evidence skipped.
- C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- 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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- 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 REDACTED Scanning: REDACTED 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").
- 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 is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- 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.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- 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.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- 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 Complexity
49 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SmithyParser.parseModel at 144. A further 26 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 CodeGen.renderHeader at 80 — they are counted neither in the figure above nor in this dimension's score. 7 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: zio-http/shared/src/main/scala/zio/http/Status.scala (Status.fromInt at 57), zio-http-cli/src/main/scala/zio/http/endpoint/cli/HttpOptions.scala (Body.fromSchema at 52), zio-http/shared/src/main/scala/zio/http/codec/HttpCodec.scala (Enumeration.f22 at 23), zio-http/jvm/src/main/scala/zio/http/netty/client/ClientSSLConverter.scala (ClientSSLConverter.buildNettySslContextBuilder at 21), zio-http-stomp/src/main/scala/zio/http/stomp/StompCommand.scala (StompCommand.fromString at 17), and 2 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.
What to do
- Bring the 1 body over 120 down to 120 or less in Cyclomatic Complexity — start with SmithyParser.parseModel (cyclomatic 144). — Refactoring it lifts Cyclomatic Complexity from 5.6 to about 5.8/10.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
81 method(s) exceeded the cognitive complexity threshold of 15; the worst was SmithyParser.parseModel at 329.
What to do
- Bring the 3 bodies over 120 down to 120 or less in Cognitive Complexity — start with SmithyParser.parseModel (cognitive 329), TextBinaryCodec.fromSchema (cognitive 138), StreamingForm.streamFormFields (cognitive 128). — 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 3 together lifts Cognitive Complexity from 4.8 to about 5.8/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
30 god class(es) detected.
What to do
- Resolve the 15 FileTooLong finding(s) in God Classes — start with REDACTED, HttpCodec.scala, Endpoint.scala. — One of this dimension's main actionable groups (15 warning-level).
- Resolve the 10 TooManyMethods finding(s) in God Classes — start with Handler.scala (2), DatastarEvent.scala, HandlerAspect.scala. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 5 MethodTooLong finding(s) in God Classes — start with StringSchemaCodec.scala (2), Endpoint.scala (2), ZClientAspect.scala. — One of this dimension's main actionable groups (5 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
111 duplicated block group(s) detected. A further 9 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 18 of the 120 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.
What to do
- Resolve the 11 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with WithContext.scala (3), EndpointGen.scala, CodeGen.scala. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 7 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with EndpointGen.scala, CssInterpolatorMacros.scala, ConnectionPoolConfig.scala. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 5 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with PathCodecPlatformSpecific.scala, Middleware.scala, URL.scala. — One of this dimension's main actionable groups (5 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
13 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 11 of the 13 (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).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
2 of 19 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with ProbeContentTypeBenchmark.scala, UtilBenchmark.scala. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
2529 test methods: 2515 unit, 14 integration, 0 BDD, 0 e2e. The Scala suite contributes 2529 test case(s) across 276 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
D12 · Dependency Hygiene
24 outdated direct sbt declarations. 40 of 42 direct declarations were graded against Maven Central (0 not published there, which is what a private Nexus or Artifactory artifact looks like, 2 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.
What to do
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · REDACTED Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D15 · Churn × Complexity Hotspots
Top hotspots: zio-http/jvm/src/main/scala/zio/http/netty/client/ClientSSLConverter.scala (3×21=63)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with ClientSSLConverter.scala. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
18 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is zio-http-datastar-sdk/src/main/scala/zio/http/datastar/Attributes.scala. Counted over 199 of the 455 production source files in this repository: 255 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.
D17 · Explicit Debt
40 deducted task-comment markers across 70957 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 38 TodoComment finding(s) in Explicit Debt — start with JsonSchema.scala (4), EndpointGen.scala (3), REDACTED (3). — One of this dimension's main actionable groups (38 warning-level).
- Resolve the 2 FixmeComment finding(s) in Explicit Debt — start with StreamingForm.scala, ScalaSettings.scala. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 2 build units (npm, sbt) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
4 finding(s): 0 critical, 4 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 4 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
134 finding(s): 0 critical, 134 high, 0 medium, 0 low. 124 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 4 file(s) — `zio-http/shared/src/main/scala-3/zio/http/HandlerVersionSpecific.scala`, `zio-http/shared/src/main/scala-3/zio/http/RoutesCompanionVersionSpecific.scala`, `zio-http/shared/src/main/scala-3/zio/http/endpoint/extensions.scala`, `REDACTED` — 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 3 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.
What to do
- Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 124 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 (124 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D31 · IaC & Container Security
14 finding(s): 0 critical, 1 high, 2 medium, 11 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 11 Low IaC finding(s) in IaC & Container Security — start with REDACTED (11). — One of this dimension's main actionable groups (11 recommendation-level).
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
62 of 200 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is zio-http/shared/src/main/scala/zio/http/codec/Combiner.scala. Counted over 200 of the 455 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 56 Orphaned file finding(s) in Knowledge Freshness — start with Attributes.scala (2), UrlInterpolator.scala (2), SSLConfig.scala. — One of this dimension's main actionable groups (56 recommendation-level).
- Resolve the 6 Orphaned knowledge finding(s) in Knowledge Freshness — start with Combiner.scala, HandlerAspect.scala, RichTextCodec.scala. — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: NettyResponse.scala↔ServerInboundHandler.scala 58%; NettyBodyWriter.scala↔NettyResponseEncoder.scala 50%
What to do
- Resolve the 2 Change coupling finding(s) in Change Coupling — start with NettyResponse.scala, NettyBodyWriter.scala. — One of this dimension's main actionable groups (2 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
AC2 · Forms & labels
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×10) — zio-http-example-basic-auth/src/main/resources/basic-auth-client-simple.html:6, zio-http-example-basic-auth/src/main/resources/basic-auth-client-simple.html:7, zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client-simple.html:16, …
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×5) — zio-http-example-basic-auth/src/main/resources/basic-auth-client-simple.html:2, zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client-simple.html:2, zio-http-example-digest-auth/src/main/resources/digest-auth-client-simple.html:2, …
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×13) — zio-http-example-basic-auth/src/main/resources/basic-auth-client-simple.html:2, zio-http-example-basic-auth/src/main/resources/basic-auth-client.html:2, zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client-simple.html:2, …
- Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×3) — zio-http-example-digest-auth/src/main/resources/digest-auth-client-simple.html:31, zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token-simple.html:38, zio-http-example-jwt-bearer-token-auth/src/main/resources/jwt-bearer-token-auth-client-simple.html:33
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC6 · Visual & motion safety
- `.container` moves (`animation: slideIn 0.6s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×6) — zio-http-example-basic-auth/src/main/resources/basic-auth-client.html:34, zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client.html:46, zio-http-example-digest-auth/src/main/resources/digest-auth-client.html:34, …
- `.user-card::before` moves (`transition: left 0.5s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×4) — zio-http-example-basic-auth/src/main/resources/basic-auth-client.html:134, zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client.html:202, zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html:228, …
- `.user-card.active::after` moves (`animation: checkIn 0.3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×4) — zio-http-example-basic-auth/src/main/resources/basic-auth-client.html:169, zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client.html:237, zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html:263, …
- `.btn::before` moves (`transition: left 0.5s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×5) — zio-http-example-basic-auth/src/main/resources/basic-auth-client.html:293, zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client.html:353, zio-http-example-digest-auth/src/main/resources/digest-auth-client.html:218, …
- `.response.show` moves (`animation: fadeIn 0.5s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×4) — zio-http-example-basic-auth/src/main/resources/basic-auth-client.html:361, zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client.html:417, zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html:531, …
- `.spinner` moves (`animation: spin 1s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×3) — zio-http-example-basic-auth/src/main/resources/basic-auth-client.html:408, zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client.html:459, zio-http-example-jwt-bearer-token-auth/src/main/resources/jwt-bearer-token-auth-client.html:514
- `.transaction-details.visible` moves (`animation: fadeIn 0.5s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×5) — zio-http-example-basic-auth/src/main/resources/basic-auth-client.html:424, zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client.html:470, zio-http-example-digest-auth/src/main/resources/digest-auth-client.html:322, …
- `.token-timer.active` moves (`animation: fadeIn 0.5s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html:120, zio-http-example-oauth-bearer-token-auth/src/main/resources/oauth-client.html:120
- `.timer-display.warning` moves (`animation: pulse 1s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html:157, zio-http-example-oauth-bearer-token-auth/src/main/resources/oauth-client.html:157
- `.timer-progress-bar` moves (`transition: width 0.3s ease, background 0.3s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html:189
- `.jwt-decoded.show` moves (`animation: fadeIn 0.5s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html:338, zio-http-example-jwt-bearer-token-auth/src/main/resources/jwt-bearer-token-auth-client.html:261
- `.status-indicator.connected` moves (`animation: pulse 2s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html:572
- `.auto-refresh-icon` moves (`animation: spin 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html:603
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 13 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
AX8 · Test isolation
GD1 · Unfinished & placeholder code
- `saveResponse` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — zio-http-cli/src/main/scala/zio/http/endpoint/cli/HttpCliApp.scala:88
What to do
- Finish or delete the members whose body is still `???` or a "not implemented" throw where nothing overrides them, and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
- `saveResponse` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — zio-http-cli/src/main/scala/zio/http/endpoint/cli/HttpCliApp.scala:88
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×6) — zio-http-cli/src/test/scala/zio/http/endpoint/cli/CliSpec.scala:152, zio-http-gen/src/test/scala/zio/http/gen/scala/OpenAPICodeGenSpec.scala:119, zio-http/jvm/src/test/scala/zio/http/ClientSpec.scala:108, …
- A bare `// scalastyle:off`, `// scalafix:off` or `@nowarn` (or Wartremover's `warts.All`) switches every rule or warning off — hidden debt. Suppress the specific rule on the specific line, with a justification, instead. — zio-http/shared/src/main/scala/zio/http/endpoint/EndpointLocator.scala:43
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
- 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)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 9 of 12 project(s) that lack one — worth up to 1.5 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- No logging call was found in the 451 JVM, JavaScript/TypeScript production file(s) this check read across 10 module(s). Each was searched for its ecosystem's logging libraries (JVM: SLF4J, Log4j2, java.util.logging, Logback, kotlin-logging, scala-logging; JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Adopt SLF4J (with a Logback or Log4j2 JSON encoder) and log at meaningful points in the modules you run.
- 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 tooling
What to do
- Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
- Dependabot is configured but does not watch `npm` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- 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 Hygiene
PF1 · Benchmark discipline
- A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — zio-http-benchmarks/src/main/scala-2.13/zio/http/benchmarks/EndpointBenchmark.scala
What to do
- Run JMH with the GC profiler (`-prof gc`, or addProfiler(GCProfiler.class)) so allocation rate regressions are visible, not just time.
PF2 · Allocation hygiene
What to do
- Raise allocation-aware density on the hot paths — currently 27 use(s) across 72,883 production line(s) (~0.4/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
- Scala: on hot paths, make small wrappers value classes (extends AnyVal), @specialized generic code over primitives, use primitive collections, and presize builders.
PF3 · Async & latency hygiene
- `requestHttp` is async and calls unsafeRunSync — a blocking call inside async code stalls the execution-context thread, and every future or fiber scheduled on it for as long as it runs. — zio-http/jvm/src/main/scala/zio/http/netty/client/NettyClientDriver.scala:62
What to do
- Scala: compose the Future or effect (map/flatMap, a for-comprehension) instead of Await.result or unsafeRunSync, and wrap unavoidable blocking calls in blocking { } (Future), IO.blocking or ZIO.attemptBlocking.
S1 · Web-Security Posture
- `InsecureTrustManagerFactory.INSTANCE` is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the override so the JVM's default trust manager and hostname check apply — that is what `SSLContext.getDefault`, Netty's `SslContextBuilder.forClient()`, sttp, Play WS and ssl-config use when nothing is set. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: load its CA into a `KeyStore` and build a `TrustManagerFactory` from it (ssl-config: `trustManager.stores`), which keeps the chain and hostname checks on. — zio-http/jvm/src/main/scala/zio/http/netty/client/ClientSSLConverter.scala:86
- `https://cdnjs.cloudflare.com/ajax/libs/crypto-js/4.2.0/crypto-js.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 2 such include(s) across the repository's markup. — zio-http-example-digest-auth/src/main/resources/digest-auth-client-simple.html:46
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `netlify.toml` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — netlify.toml:1
What to do
- Stop accepting every TLS certificate: delete the trust manager whose `checkServerTrusted` is empty, the `HostnameVerifier` that returns `true`, `InsecureTrustManagerFactory` / `NoopHostnameVerifier` and `acceptAnyCertificate`, and trust a self-signed or private server by giving the client a trust store holding its CA — never by switching verification off.
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
- Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- `case NonFatal(_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — REDACTED:4174, zio-http/shared/src/main/scala/zio/http/URL.scala:384
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- No build over this repository's 265 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.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 63% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 73% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 60% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 60% | Adequate — gated by P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 42% | Weak — gated by D29, D36, S1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 42% | Weak — gated by AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 76% | Strong | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 8 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
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 48 check(s) not relevant to this codebase
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — Not applicable: 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.
- AX2 Stateful singletons — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — -------------------- ERROR: failed to solve: hseeberger/scala-sbt:11.0.12_1.5.5_2.13.6: failed to resolve source metadata for docker.io/hseeberger/scala-sbt:11.0.12_1.5.5_2.13.6: failed to do request: Head "https://registry-1.docker.io/v2/hseeberger/scala-sbt/manifests/11.0.12_1.5.5_2.13.6": Forbidden; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- 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 — ~47961 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
- D14 License Compliance — Not scored — this repository's 42 pinned sbt dependency coordinate(s) were read from its 20 sbt build file(s), but Maven Central could not be asked for the licence of 1 of them (HTTP 403 Forbidden from https://repo1.maven.org/maven2/org/scoverage/sbt-scoverage/${ScoverageVersion}/sbt-scoverage-${ScoverageVersion}.pom), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
- 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 — D19 reads .NET projects as units only; 2 folder(s) declared by package.json were not judged for an overview, an example or the map.
- D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, Python, Scala, html not measured.
- 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+ projects each declaring an entity of their own. 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# and Visual Basic comments only — this repository's production source is .py, .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- 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.
- D32 Data Compliance (PII/GDPR) — 4 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (3 signals for this style, 2 needed — the count is met but a required primary signal is absent): 1141 value object(s); 16 domain event(s); its domain events are published by services or handlers — no domain entity raises one; a Domain/Aggregates/ValueObjects layer; a domain structure with no aggregate, domain event or strongly-typed id in it: a CRUD / clean-architecture model, measured but not claimed as DDD; a top-level zio-http-example/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
- 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 81 current-state document(s) make no claim of a kind M4 checks. 15 claim(s) of kinds M4 does not check were not checked (path 5, command argument 3, environment variable 7); M4 checks only links and versions.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript, Python 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 — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's Scala and Python 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 Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
- 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.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Scala was read, and it logs through none that an interpolated message defeats: scala-logging takes an `s"…"` message apart into SLF4J's pattern and arguments at compile time, and log4s, grizzled-slf4j, Play's Logger, Akka's LoggingAdapter, sbt's Logger and Spark's Logging take one finished message (as log4net does in C#). Calls made straight through SLF4J (`org.slf4j.Logger`) would be judged.
- 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)
Critical — 162 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <input> without a programmatic label zio-http-example-basic-auth/src/main/resources/basic-auth-client-simple.html:6
- <input> without a programmatic label zio-http-example-basic-auth/src/main/resources/basic-auth-client-simple.html:7
- <input> without a programmatic label zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client-simple.html:16
- <input> without a programmatic label zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client-simple.html:17
- <input> without a programmatic label zio-http-example-digest-auth/src/main/resources/digest-auth-client-simple.html:32
- <input> without a programmatic label zio-http-example-digest-auth/src/main/resources/digest-auth-client-simple.html:33
- <input> without a programmatic label zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token-simple.html:39
- <input> without a programmatic label zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token-simple.html:40
- <input> without a programmatic label zio-http-example-jwt-bearer-token-auth/src/main/resources/jwt-bearer-token-auth-client-simple.html:19
- <input> without a programmatic label zio-http-example-jwt-bearer-token-auth/src/main/resources/jwt-bearer-token-auth-client-simple.html:20
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge zio-http/shared/src/main/scala/zio/http/codec/Combiner.scala:1
- Orphaned knowledge zio-http/shared/src/main/scala/zio/http/HandlerAspect.scala:1
- Orphaned knowledge zio-http/shared/src/main/scala/zio/http/codec/RichTextCodec.scala:1
- Orphaned knowledge zio-http-benchmarks/src/main/scala-2.13/zio/http/benchmarks/EndpointBenchmark.scala:1
- Orphaned knowledge zio-http/shared/src/main/scala/zio/http/ZClientAspect.scala:1
- Orphaned knowledge zio-http/shared/src/main/scala/zio/http/ToHandler.scala:1
- <html> without a lang zio-http-example-basic-auth/src/main/resources/basic-auth-client-simple.html:2
- <html> without a lang zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client-simple.html:2
- <html> without a lang zio-http-example-digest-auth/src/main/resources/digest-auth-client-simple.html:2
- <html> without a lang zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token-simple.html:2
- <html> without a lang zio-http-example-jwt-bearer-token-auth/src/main/resources/jwt-bearer-token-auth-client-simple.html:2
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TLS certificate validation disabled zio-http/jvm/src/main/scala/zio/http/netty/client/ClientSSLConverter.scala:86
Serious — 399 finding(s)
- Animation without a prefers-reduced-motion guard zio-http-example-basic-auth/src/main/resources/basic-auth-client.html:34
- Animation without a prefers-reduced-motion guard zio-http-example-basic-auth/src/main/resources/basic-auth-client.html:134
- Animation without a prefers-reduced-motion guard zio-http-example-basic-auth/src/main/resources/basic-auth-client.html:169
- Animation without a prefers-reduced-motion guard zio-http-example-basic-auth/src/main/resources/basic-auth-client.html:293
- Animation without a prefers-reduced-motion guard zio-http-example-basic-auth/src/main/resources/basic-auth-client.html:361
- Animation without a prefers-reduced-motion guard zio-http-example-basic-auth/src/main/resources/basic-auth-client.html:408
- Animation without a prefers-reduced-motion guard zio-http-example-basic-auth/src/main/resources/basic-auth-client.html:424
- Animation without a prefers-reduced-motion guard zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client.html:46
- Animation without a prefers-reduced-motion guard zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client.html:202
- Animation without a prefers-reduced-motion guard zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client.html:237
- Animation without a prefers-reduced-motion guard zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client.html:353
- Animation without a prefers-reduced-motion guard zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client.html:417
- Animation without a prefers-reduced-motion guard zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client.html:459
- Animation without a prefers-reduced-motion guard zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client.html:470
- Animation without a prefers-reduced-motion guard zio-http-example-digest-auth/src/main/resources/digest-auth-client.html:34
- Animation without a prefers-reduced-motion guard zio-http-example-digest-auth/src/main/resources/digest-auth-client.html:218
- Animation without a prefers-reduced-motion guard zio-http-example-digest-auth/src/main/resources/digest-auth-client.html:322
- Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html:34
- Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html:120
- Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html:157
- Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html:189
- Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html:228
- Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html:263
- Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html:338
- Animation without a prefers-reduced-motion guard zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html:475
- TodoComment zio-http-gen/src/main/scala/zio/http/gen/openapi/EndpointGen.scala:410
- TodoComment zio-http-gen/src/main/scala/zio/http/gen/openapi/EndpointGen.scala:471
- TodoComment zio-http-cli/src/test/scala/zio/http/endpoint/cli/CliSpec.scala:152
- TodoComment zio-http-cli/src/test/scala/zio/http/endpoint/cli/EndpointGen.scala:81
- TodoComment zio-http-cli/src/main/scala/zio/http/endpoint/cli/HttpOptions.scala:113
- TodoComment REDACTED:2262
- TodoComment REDACTED:2272
- TodoComment REDACTED:2275
- TodoComment zio-http/shared/src/main/scala/zio/http/ProtocolStack.scala:79
- TodoComment zio-http/shared/src/main/scala/zio/http/ProtocolStack.scala:99
- TodoComment zio-http/shared/src/main/scala/zio/http/Response.scala:288
- TodoComment zio-http/shared/src/main/scala/zio/http/multipart/mixed/MultipartMixed.scala:128
- TodoComment zio-http/shared/src/main/scala/zio/http/internal/DateEncoding.scala:97
- TodoComment zio-http/shared/src/main/scala/zio/http/endpoint/Endpoint.scala:461
- TodoComment zio-http/shared/src/main/scala/zio/http/endpoint/openapi/JsonSchema.scala:879
- TodoComment zio-http/shared/src/main/scala/zio/http/endpoint/openapi/JsonSchema.scala:1421
- TodoComment zio-http/shared/src/main/scala/zio/http/endpoint/openapi/JsonSchema.scala:1631
- TodoComment zio-http/shared/src/main/scala/zio/http/endpoint/openapi/JsonSchema.scala:1670
- TodoComment zio-http/shared/src/main/scala/zio/http/endpoint/openapi/OpenAPI.scala:505
- TodoComment zio-http/shared/src/main/scala/zio/http/endpoint/openapi/OpenAPI.scala:1205
- TodoComment zio-http/shared/src/main/scala/zio/http/endpoint/openapi/OpenAPIGen.scala:954
- TodoComment zio-http/shared/src/main/scala/zio/http/endpoint/openapi/OpenAPIGen.scala:1251
- TodoComment zio-http/shared/src/main/scala/zio/http/endpoint/http/HttpFile.scala:47
- TodoComment zio-http/shared/src/main/scala/zio/http/endpoint/http/HttpGen.scala:76
- TodoComment zio-http/shared/src/main/scala/zio/http/endpoint/http/HttpGen.scala:83
- FileTooLong: REDACTED REDACTED
- FileTooLong: codec/HttpCodec.scala zio-http/shared/src/main/scala/zio/http/codec/HttpCodec.scala
- FileTooLong: endpoint/Endpoint.scala zio-http/shared/src/main/scala/zio/http/endpoint/Endpoint.scala
- FileTooLong: openapi/JsonSchema.scala zio-http/shared/src/main/scala/zio/http/endpoint/openapi/JsonSchema.scala
- FileTooLong: openapi/EndpointGen.scala zio-http-gen/src/main/scala/zio/http/gen/openapi/EndpointGen.scala
- FileTooLong: openapi/OpenAPIGen.scala zio-http/shared/src/main/scala/zio/http/endpoint/openapi/OpenAPIGen.scala
- FileTooLong: codec/Combiner.scala zio-http/shared/src/main/scala/zio/http/codec/Combiner.scala
- FileTooLong: http/Handler.scala zio-http/shared/src/main/scala/zio/http/Handler.scala
- FileTooLong: datastar/DatastarPackageBase.scala zio-http-datastar-sdk/src/main/scala/zio/http/datastar/DatastarPackageBase.scala
- FileTooLong: smithy/Smithy.scala zio-http-gen/src/main/scala/zio/http/gen/smithy/Smithy.scala
- FileTooLong: codec/PathCodec.scala zio-http/shared/src/main/scala/zio/http/codec/PathCodec.scala
- FileTooLong: openapi/OpenAPI.scala zio-http/shared/src/main/scala/zio/http/endpoint/openapi/OpenAPI.scala
- FileTooLong: internal/StringSchemaCodec.scala zio-http/shared/src/main/scala/zio/http/internal/StringSchemaCodec.scala
- FileTooLong: http/ZClient.scala zio-http/shared/src/main/scala/zio/http/ZClient.scala
- FileTooLong: datastar/Attributes.scala zio-http-datastar-sdk/src/main/scala/zio/http/datastar/Attributes.scala
- Page without a main landmark zio-http-example-basic-auth/src/main/resources/basic-auth-client-simple.html:2
- Page without a main landmark zio-http-example-basic-auth/src/main/resources/basic-auth-client.html:2
- Page without a main landmark zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client-simple.html:2
- Page without a main landmark zio-http-example-cookie-auth/src/main/resources/cookie-based-auth-client.html:2
- Page without a main landmark zio-http-example-digest-auth/src/main/resources/digest-auth-client-simple.html:2
- Page without a main landmark zio-http-example-digest-auth/src/main/resources/digest-auth-client.html:2
- Page without a main landmark zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token-simple.html:2
- Page without a main landmark zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token.html:2
- Page without a main landmark zio-http-example-jwt-bearer-token-auth/src/main/resources/jwt-bearer-token-auth-client-simple.html:2
- Page without a main landmark zio-http-example-jwt-bearer-token-auth/src/main/resources/jwt-bearer-token-auth-client.html:2
- Page without a main landmark zio-http-example-oauth-bearer-token-auth/src/main/resources/oauth-client.html:2
- Page without a main landmark zio-http-example-opaque-bearer-token-auth/src/main/resources/opaque-bearer-token-auth-client.html:2
- Page without a main landmark zio-http-example-webauthn/src/main/resources/webauthn-client.html:2
- Duplicated block (7 lines × 2) zio-http-gen/src/main/scala/zio/http/gen/openapi/EndpointGen.scala:1266
- Duplicated block (7 lines × 2) zio-http-gen/src/main/scala/zio/http/gen/scala/CodeGen.scala:426
- Duplicated block (7 lines × 2) zio-http/jvm/src/main/scala/zio/http/netty/server/ServerInboundHandler.scala:282
- Duplicated block (7 lines × 2) zio-http/shared/src/main/scala/zio/http/Middleware.scala:410
- Duplicated block (7 lines × 2) zio-http/shared/src/main/scala/zio/http/WithContext.scala:111
- Duplicated block (7 lines × 2) zio-http/shared/src/main/scala/zio/http/WithContext.scala:117
- Duplicated block (7 lines × 2) zio-http/shared/src/main/scala/zio/http/WithContext.scala:258
- Duplicated block (7 lines × 2) zio-http/shared/src/main/scala/zio/http/codec/PathCodec.scala:83
- Duplicated block (7 lines × 2) zio-http/shared/src/main/scala/zio/http/internal/StringSchemaCodec.scala:419
- Duplicated block (7 lines × 2) zio-http/shared/src/main/scala/zio/http/template2/Dom.scala:429
- Duplicated block (7 lines × 2) zio-http-example-jwt-bearer-refresh-token-auth/src/main/scala/example/auth/bearer/jwt/refresh/core/JwtTokenService.scala:77
- TooManyMethods: Handler zio-http/shared/src/main/scala/zio/http/Handler.scala:35
- TooManyMethods: DatastarEvent zio-http-datastar-sdk/src/main/scala/zio/http/datastar/DatastarEvent.scala:20
- TooManyMethods: Handler zio-http/shared/src/main/scala/zio/http/Handler.scala:716
- TooManyMethods: HandlerAspects zio-http/shared/src/main/scala/zio/http/HandlerAspect.scala:242
- TooManyMethods: Response zio-http/shared/src/main/scala/zio/http/Response.scala:119
- TooManyMethods: CssSelectable zio-http/shared/src/main/scala/zio/http/template2/CssSelector.scala:7
- TooManyMethods: OpenAPIGen zio-http/shared/src/main/scala/zio/http/endpoint/openapi/OpenAPIGen.scala:26
- TooManyMethods: HttpCodec zio-http/shared/src/main/scala/zio/http/codec/HttpCodec.scala:48
- TooManyMethods: Attributes zio-http-datastar-sdk/src/main/scala/zio/http/datastar/Attributes.scala:13
- TooManyMethods: PathCodec zio-http/shared/src/main/scala/zio/http/codec/PathCodec.scala:39
- Duplicated block (12 lines × 2) zio-http-gen/src/main/scala/zio/http/gen/openapi/EndpointGen.scala:816
- Duplicated block (12 lines × 2) zio-http/shared/src/main/scala-3/zio/http/template2/CssInterpolatorMacros.scala:26
- Duplicated block (12 lines × 2) zio-http/shared/src/main/scala/zio/http/ConnectionPoolConfig.scala:47
- Duplicated block (12 lines × 2) zio-http/shared/src/main/scala/zio/http/HandlerAspect.scala:100
- Duplicated block (12 lines × 2) zio-http/shared/src/main/scala/zio/http/codec/TextCodec.scala:95
- Duplicated block (12 lines × 2) zio-http/shared/src/main/scala/zio/http/internal/StringSchemaCodec.scala:391
- Duplicated block (12 lines × 2) zio-http-example-jwt-bearer-refresh-token-auth/src/main/scala/example/auth/bearer/jwt/refresh/core/JwtTokenService.scala:50
- MethodTooLong: StringSchemaCodec.recordSchema zio-http/shared/src/main/scala/zio/http/internal/StringSchemaCodec.scala:520
- MethodTooLong: StringSchemaCodec.parsePrimitive zio-http/shared/src/main/scala/zio/http/internal/StringSchemaCodec.scala:526
- MethodTooLong: Endpoint.implementEither zio-http/shared/src/main/scala/zio/http/endpoint/Endpoint.scala:314
- MethodTooLong: Endpoint.implementPurely zio-http/shared/src/main/scala/zio/http/endpoint/Endpoint.scala:319
- MethodTooLong: ZClientAspect.requestLogging zio-http/shared/src/main/scala/zio/http/ZClientAspect.scala:184
- Duplicated block (9 lines × 2) zio-http/js/src/main/scala/zio/http/codec/PathCodecPlatformSpecific.scala:5
- Duplicated block (9 lines × 2) zio-http/shared/src/main/scala/zio/http/Middleware.scala:253
- Duplicated block (9 lines × 2) zio-http/shared/src/main/scala/zio/http/URL.scala:313
- Duplicated block (9 lines × 2) zio-http/shared/src/main/scala/zio/http/endpoint/http/HttpGen.scala:181
- Duplicated block (9 lines × 2) zio-http-example-jwt-bearer-refresh-token-auth/src/main/scala/example/auth/bearer/jwt/refresh/core/AuthMiddleware.scala:16
- Members sharing a duplicated core (4 members, 50+ identical tokens) zio-http/shared/src/main/scala/zio/http/Route.scala:92
- Members sharing a duplicated core (4 members, 50+ identical tokens) zio-http/shared/src/main/scala/zio/http/WithContext.scala:105
- Members sharing a duplicated core (4 members, 50+ identical tokens) zio-http/shared/src/main/scala/zio/http/ZClientAspect.scala:122
- Members sharing a duplicated core (4 members, 50+ identical tokens) zio-http/shared/src/main/scala/zio/http/template2/Dom.scala:423
- Duplicated block (13 lines × 2) zio-http/js/src/main/scala/zio/http/codec/PathCodecPlatformSpecific.scala:27
- Duplicated block (13 lines × 2) zio-http/shared/src/main/scala/zio/http/Form.scala:123
- Duplicated block (13 lines × 2) REDACTED:134
- Duplicated block (13 lines × 2) REDACTED:4436
- Duplicated block (11 lines × 2) zio-http/shared/src/main/scala/zio/http/ZClientAspect.scala:169
- Duplicated block (11 lines × 2) zio-http/shared/src/main/scala/zio/http/codec/HttpContentCodec.scala:91
- Duplicated block (11 lines × 2) zio-http/shared/src/main/scala/zio/http/codec/SegmentCodec.scala:402
- Duplicated block (11 lines × 2) zio-http-example-jwt-bearer-refresh-token-auth/src/main/scala/example/auth/bearer/jwt/refresh/AuthenticationClient.scala:51
- Duplicated block (10 lines × 2) REDACTED:3214
- Duplicated block (10 lines × 2) zio-http/shared/src/main/scala/zio/http/WithContext.scala:156
- Duplicated block (10 lines × 2) zio-http/shared/src/main/scala/zio/http/ZClient.scala:446
- Duplicated block (10 lines × 2) zio-http/shared/src/main/scala/zio/http/internal/StringSchemaCodec.scala:172
- Duplicated block (8 lines × 2) zio-http/shared/src/main/scala/zio/http/WithContext.scala:147
- Duplicated block (8 lines × 2) zio-http/shared/src/main/scala/zio/http/internal/StringSchemaCodec.scala:426
- Duplicated block (8 lines × 2) zio-http-benchmarks/src/main/scala/zhttp.benchmarks/ClientBenchmark.scala:56
- Duplicated block (8 lines × 2) zio-http-example-jwt-bearer-refresh-token-auth/src/main/scala/example/auth/bearer/jwt/refresh/core/JwtTokenService.scala:67
- Duplicated block (7–8 lines × 2) zio-http/shared/src/main/scala/zio/http/codec/HttpCodec.scala:1553
- Duplicated block (7–8 lines × 2) zio-http/shared/src/main/scala/zio/http/codec/HttpCodec.scala:1734
- Duplicated block (7–8 lines × 2) zio-http/shared/src/main/scala/zio/http/codec/HttpCodec.scala:1941
- Duplicated block (7–8 lines × 2) zio-http/shared/src/main/scala/zio/http/endpoint/openapi/OpenAPIGen.scala:359
- Duplicated block (6 lines × 2) zio-http/shared/src/main/scala/zio/http/WithContext.scala:111
- Duplicated block (6 lines × 2) zio-http/shared/src/main/scala/zio/http/ZClient.scala:458
- Duplicated block (6 lines × 2) zio-http/shared/src/main/scala/zio/http/Request.scala:113
- Duplicated block (6 lines × 2) zio-http/shared/src/main/scala/zio/http/Route.scala:130
- Heading level jumps from h1 to h3 zio-http-example-digest-auth/src/main/resources/digest-auth-client-simple.html:31
- Heading level jumps from h1 to h3 zio-http-example-jwt-bearer-refresh-token-auth/src/main/resources/jwt-client-with-refresh-token-simple.html:38
- Heading level jumps from h1 to h3 zio-http-example-jwt-bearer-token-auth/src/main/resources/jwt-bearer-token-auth-client-simple.html:33
- Duplicated block (6 lines × 3) zio-http/shared/src/main/scala/zio/http/template2/Dom.scala:428
- Duplicated block (6 lines × 3) zio-http-example-jwt-bearer-refresh-token-auth/src/main/scala/example/auth/bearer/jwt/refresh/core/AuthMiddleware.scala:15
- Duplicated block (6 lines × 3) zio-http-example-jwt-bearer-refresh-token-auth/src/main/scala/example/auth/bearer/jwt/refresh/core/JwtTokenService.scala:86
- Duplicated block (5 lines × 3) zio-http/shared/src/main/scala/zio/http/endpoint/openapi/JsonSchema.scala:1341
- Duplicated block (5 lines × 3) zio-http/shared/src/main/scala/zio/http/endpoint/openapi/OpenAPIGen.scala:1011
- Duplicated block (5 lines × 3) zio-http-example-jwt-bearer-refresh-token-auth/src/main/scala/example/auth/bearer/jwt/refresh/core/JwtTokenService.scala:42
- Duplicated block (5 lines × 2) zio-http/shared/src/main/scala/zio/http/endpoint/openapi/OpenAPIGen.scala:255
- Duplicated block (5 lines × 2) zio-http/shared/src/main/scala/zio/http/internal/StringSchemaCodec.scala:408
- Duplicated block (5 lines × 2) zio-http/shared/src/main/scala/zio/http/endpoint/openapi/OpenAPIGen.scala:998
- FixmeComment zio-http/shared/src/main/scala/zio/http/StreamingForm.scala:143
- FixmeComment project/ScalaSettings.scala:41
- REDACTED
- REDACTED
- Change coupling: NettyResponse.scala ↔ ServerInboundHandler.scala zio-http/jvm/src/main/scala/zio/http/netty/NettyResponse.scala:1
- Change coupling: NettyBodyWriter.scala ↔ NettyResponseEncoder.scala zio-http/jvm/src/main/scala/zio/http/netty/NettyBodyWriter.scala:1
- REDACTED
- REDACTED
- Duplicated block (24 lines × 2) zio-http/shared/src/main/scala/zio/http/Path.scala:325
- Duplicated block (24 lines × 2) zio-http/shared/src/main/scala/zio/http/QueryParams.scala:99
- Duplicated block (19 lines × 2) zio-http/jvm/src/main/scala/zio/http/netty/client/NettyConnectionPool.scala:518
- Duplicated block (19 lines × 2) zio-http-example-jwt-bearer-refresh-token-auth/src/main/scala/example/auth/bearer/jwt/refresh/core/User.scala:26
- Duplicated block (16 lines × 2) zio-http-gen/src/main/scala/zio/http/gen/openapi/EndpointGen.scala:898
- Duplicated block (16 lines × 2) zio-http/shared/src/main/scala/zio/http/codec/Combiner.scala:1344
- Duplicated block (14 lines × 2) zio-http/shared/src/main/scala/zio/http/Middleware.scala:447
- Duplicated block (14 lines × 2) zio-http/shared/src/main/scala/zio/http/ZClientAspect.scala:368
- Duplicated block (10–11 lines × 2) zio-http/shared/src/main/scala/zio/http/codec/PathCodec.scala:335
- Duplicated block (10–11 lines × 2) zio-http-example-jwt-bearer-refresh-token-auth/src/main/scala/example/auth/bearer/jwt/refresh/AuthenticationClient.scala:109
- Duplicated block (5 lines × 4) zio-http/shared/src/main/scala/zio/http/endpoint/openapi/JsonSchema.scala:1309
- Duplicated block (5 lines × 4) zio-http/shared/src/main/scala/zio/http/template2/Dom.scala:425
- Low cohesion: ProbeContentTypeBenchmark (LCOM4 6) zio-http-benchmarks/src/main/scala/zhttp.benchmarks/ProbeContentTypeBenchmark.scala:12
- Low cohesion: UtilBenchmark (LCOM4 4) zio-http-benchmarks/src/main/scala/zhttp.benchmarks/UtilBenchmark.scala:11
- Swallowed exception (caught, then discarded) REDACTED:4174
- Swallowed exception (caught, then discarded) zio-http/shared/src/main/scala/zio/http/URL.scala:384
- Accessibility enforcement below the top rung
- SmithyParser.parseModel (cyclomatic 144) zio-http-gen/src/main/scala/zio/http/gen/smithy/Smithy.scala:432
- TextBinaryCodec.fromSchema (cyclomatic 84) zio-http/shared/src/main/scala/zio/http/codec/TextBinaryCodec.scala:34
- EndpointGen.schemaToField (cyclomatic 79) zio-http-gen/src/main/scala/zio/http/gen/openapi/EndpointGen.scala:1173
- DateEncoding.decodeRFC1123 (cyclomatic 76) zio-http/shared/src/main/scala/zio/http/internal/DateEncoding.scala:93
- OpenAPIGen.gen (cyclomatic 72) zio-http/shared/src/main/scala/zio/http/endpoint/openapi/OpenAPIGen.scala:672
- JsonSchema.fromZSchemaInternal (cyclomatic 70) zio-http/shared/src/main/scala/zio/http/endpoint/openapi/JsonSchema.scala:742
- RichTextCodec.describe (cyclomatic 64) zio-http/shared/src/main/scala/zio/http/codec/RichTextCodec.scala:318
- StringSchemaCodec.parsePrimitive (cyclomatic 60) zio-http/shared/src/main/scala/zio/http/internal/StringSchemaCodec.scala:526
- CodeGen.render (cyclomatic 49) zio-http-gen/src/main/scala/zio/http/gen/scala/CodeGen.scala:42
- EndpointGen.schemaToCode (cyclomatic 46) zio-http-gen/src/main/scala/zio/http/gen/openapi/EndpointGen.scala:803
- JsonSchema.flatten (cyclomatic 40) zio-http/shared/src/main/scala/zio/http/endpoint/openapi/JsonSchema.scala:1289
- SmithyParser.convertTrait (cyclomatic 37) zio-http-gen/src/main/scala/zio/http/gen/smithy/Smithy.scala:951
- PathCodec.decode (cyclomatic 37) zio-http/shared/src/main/scala/zio/http/codec/PathCodec.scala:127
- PathCodec.decodeSubstring (cyclomatic 32) zio-http/shared/src/main/scala/zio/http/codec/PathCodec.scala:295
- Endpoint.implementHandler (cyclomatic 32) zio-http/shared/src/main/scala/zio/http/endpoint/Endpoint.scala:347
- JsonSchema.fromSerializableSchema (cyclomatic 32) zio-http/shared/src/main/scala/zio/http/endpoint/openapi/JsonSchema.scala:274
- EndpointGen.endpoint (cyclomatic 31) zio-http-gen/src/main/scala/zio/http/gen/openapi/EndpointGen.scala:398
- useFullpageScroll.useFullpageScroll (cyclomatic 30) website/src/components/useFullpageScroll.js:16
- HttpGen.bodyVariables (cyclomatic 28) zio-http/shared/src/main/scala/zio/http/endpoint/http/HttpGen.scala:67
- StreamingForm.streamFormFields (cyclomatic 26) zio-http/shared/src/main/scala/zio/http/StreamingForm.scala:50
- Doc.toPlaintext (cyclomatic 26) zio-http/shared/src/main/scala/zio/http/codec/Doc.scala:221
- SegmentSubtree.get (cyclomatic 25) zio-http/shared/src/main/scala/zio/http/codec/PathCodec.scala:835
- JsonSchema.fromZSchemaMultiple (cyclomatic 25) zio-http/shared/src/main/scala/zio/http/endpoint/openapi/JsonSchema.scala:502
- DateEncoding.encodeRFC1123 (cyclomatic 25) zio-http/shared/src/main/scala/zio/http/internal/DateEncoding.scala:38
- StringSchemaCodec.decode (cyclomatic 25) zio-http/shared/src/main/scala/zio/http/internal/StringSchemaCodec.scala:130
- EndpointGen.extractComponents (cyclomatic 24) zio-http-gen/src/main/scala/zio/http/gen/openapi/EndpointGen.scala:75
- Doc.toCommonMark (cyclomatic 24) zio-http/shared/src/main/scala/zio/http/codec/Doc.scala:75
- FormStateBuffer.append (cyclomatic 24) zio-http/shared/src/main/scala/zio/http/internal/FormState.scala:56
- OpenAPIGen.contentAsJsonSchema (cyclomatic 23) zio-http/shared/src/main/scala/zio/http/endpoint/openapi/OpenAPIGen.scala:346
- OpenAPIGen.generateExamples (cyclomatic 22) zio-http/shared/src/main/scala/zio/http/endpoint/openapi/OpenAPIGen.scala:248
- Dom.encode (cyclomatic 22) zio-http/shared/src/main/scala/zio/http/template/Dom.scala:43
- SmithyValidation.validateConstraintTraits (cyclomatic 21) zio-http-gen/src/main/scala/zio/http/gen/smithy/SmithyValidation.scala:392
- Authorization.parseDigest (cyclomatic 21) REDACTED:1349
- QueryParams.normalize (cyclomatic 21) zio-http/shared/src/main/scala/zio/http/QueryParams.scala:90
- SmithyEndpointGen.shapeIdToType (cyclomatic 20) zio-http-gen/src/main/scala/zio/http/gen/smithy/SmithyEndpointGen.scala:662
- CodeGen.renderQueryCodecType (cyclomatic 18) zio-http-gen/src/main/scala/zio/http/gen/scala/CodeGen.scala:410
- Middleware.cors (cyclomatic 18) zio-http/shared/src/main/scala/zio/http/Middleware.scala:81
- PathCodec.indexOfNextCodec (cyclomatic 18) zio-http/shared/src/main/scala/zio/http/codec/PathCodec.scala:408
- RichTextCodec.parse (cyclomatic 18) zio-http/shared/src/main/scala/zio/http/codec/RichTextCodec.scala:610
- UUID.inUUIDUntil (cyclomatic 18) zio-http/shared/src/main/scala/zio/http/codec/SegmentCodec.scala:474
- UrlInterpolatorMacro.url (cyclomatic 17) zio-http/shared/src/main/scala-2/zio/http/UrlInterpolator.scala:30
- ZClientAspect.followRedirects (cyclomatic 17) zio-http/shared/src/main/scala/zio/http/ZClientAspect.scala:331
- CharSequenceExtensions.contains (cyclomatic 17) zio-http/shared/src/main/scala/zio/http/internal/CharSequenceExtensions.scala:81
- DatastarEndpointOps.makeRequest (cyclomatic 16) zio-http-datastar-sdk/src/main/scala/zio/http/datastar/DatastarPackageBase.scala:250
- UrlInterpolatorMacro.url (cyclomatic 16) zio-http/shared/src/main/scala-3/zio/http/UrlInterpolator.scala:31
- Path.removeDotSegments (cyclomatic 16) zio-http/shared/src/main/scala/zio/http/Path.scala:207
- DriverLive.requestAsync (cyclomatic 16) zio-http/shared/src/main/scala/zio/http/ZClient.scala:664
- QueryParamEncoding.decode (cyclomatic 16) zio-http/shared/src/main/scala/zio/http/internal/QueryParamEncoding.scala:26
- StringSchemaCodec.headerFromSchema (cyclomatic 16) zio-http/shared/src/main/scala/zio/http/internal/StringSchemaCodec.scala:351
- Hotspot: zio-http/jvm/src/main/scala/zio/http/netty/client/ClientSSLConverter.scala zio-http/jvm/src/main/scala/zio/http/netty/client/ClientSSLConverter.scala:81
- SmithyParser.parseModel (cognitive 329) zio-http-gen/src/main/scala/zio/http/gen/smithy/Smithy.scala:432
- TextBinaryCodec.fromSchema (cognitive 138) zio-http/shared/src/main/scala/zio/http/codec/TextBinaryCodec.scala:34
- StreamingForm.streamFormFields (cognitive 128) zio-http/shared/src/main/scala/zio/http/StreamingForm.scala:50
- EndpointGen.schemaToField (cognitive 89) zio-http-gen/src/main/scala/zio/http/gen/openapi/EndpointGen.scala:1173
- Authorization.parseDigest (cognitive 82) REDACTED:1349
- PathCodec.decode (cognitive 78) zio-http/shared/src/main/scala/zio/http/codec/PathCodec.scala:127
- PathCodec.decodeSubstring (cognitive 70) zio-http/shared/src/main/scala/zio/http/codec/PathCodec.scala:295
- SegmentSubtree.get (cognitive 64) zio-http/shared/src/main/scala/zio/http/codec/PathCodec.scala:835
- DateEncoding.decodeRFC1123 (cognitive 62) zio-http/shared/src/main/scala/zio/http/internal/DateEncoding.scala:93
- DriverLive.requestAsync (cognitive 60) zio-http/shared/src/main/scala/zio/http/ZClient.scala:664
- OpenAPIGen.gen (cognitive 58) zio-http/shared/src/main/scala/zio/http/endpoint/openapi/OpenAPIGen.scala:672
- CodeGen.render (cognitive 56) zio-http-gen/src/main/scala/zio/http/gen/scala/CodeGen.scala:42
- QueryParams.normalize (cognitive 56) zio-http/shared/src/main/scala/zio/http/QueryParams.scala:90
- StringSchemaCodec.parsePrimitive (cognitive 56) zio-http/shared/src/main/scala/zio/http/internal/StringSchemaCodec.scala:526
- RichTextCodec.describe (cognitive 53) zio-http/shared/src/main/scala/zio/http/codec/RichTextCodec.scala:318
- StringSchemaCodec.decode (cognitive 51) zio-http/shared/src/main/scala/zio/http/internal/StringSchemaCodec.scala:130
- NettyConnectionPool.happyEyeballsConnect (cognitive 48) zio-http/jvm/src/main/scala/zio/http/netty/client/NettyConnectionPool.scala:223
- JsonSchema.fromZSchemaInternal (cognitive 48) zio-http/shared/src/main/scala/zio/http/endpoint/openapi/JsonSchema.scala:742
- CharSequenceExtensions.contains (cognitive 47) zio-http/shared/src/main/scala/zio/http/internal/CharSequenceExtensions.scala:81
- TestClient.socket (cognitive 45) zio-http-testkit/src/main/scala/zio/http/TestClient.scala:161
- EndpointGen.extractComponents (cognitive 44) zio-http-gen/src/main/scala/zio/http/gen/openapi/EndpointGen.scala:75
- SmithyValidation.validateConstraintTraits (cognitive 41) zio-http-gen/src/main/scala/zio/http/gen/smithy/SmithyValidation.scala:392
- EndpointGen.endpoint (cognitive 38) zio-http-gen/src/main/scala/zio/http/gen/openapi/EndpointGen.scala:398
- QueryParamEncoding.decode (cognitive 38) zio-http/shared/src/main/scala/zio/http/internal/QueryParamEncoding.scala:26
- Endpoint.implementHandler (cognitive 36) zio-http/shared/src/main/scala/zio/http/endpoint/Endpoint.scala:347
- Path.removeDotSegments (cognitive 35) zio-http/shared/src/main/scala/zio/http/Path.scala:207
- useFullpageScroll.useFullpageScroll (cognitive 35) website/src/components/useFullpageScroll.js:16
- EndpointGen.schemaToCode (cognitive 34) zio-http-gen/src/main/scala/zio/http/gen/openapi/EndpointGen.scala:803
- ZClientAspect.followRedirects (cognitive 34) zio-http/shared/src/main/scala/zio/http/ZClientAspect.scala:331
- HttpCliApp.fromEndpoints (cognitive 31) zio-http-cli/src/main/scala/zio/http/endpoint/cli/HttpCliApp.scala:43
- Path.decode (cognitive 29) zio-http/shared/src/main/scala/zio/http/Path.scala:324
- Path.decodeRaw (cognitive 29) zio-http/shared/src/main/scala/zio/http/Path.scala:373
- ServerInboundHandler.attemptFullWrite (cognitive 27) zio-http/jvm/src/main/scala/zio/http/netty/server/ServerInboundHandler.scala:180
- URL.decode (cognitive 27) zio-http/shared/src/main/scala/zio/http/URL.scala:299
- FormStateBuffer.append (cognitive 27) zio-http/shared/src/main/scala/zio/http/internal/FormState.scala:56
- Parser.subStream (cognitive 26) zio-http/shared/src/main/scala/zio/http/multipart/mixed/MultipartMixed.scala:139
- PathCodecPlatformSpecific.parseInt (cognitive 25) zio-http/js/src/main/scala/zio/http/codec/PathCodecPlatformSpecific.scala:43
- Link.parse (cognitive 25) REDACTED:3375
- Range.parse (cognitive 25) REDACTED:3640
- URL.decodeOrNull (cognitive 25) zio-http/shared/src/main/scala/zio/http/URL.scala:359
- ZClientAspect.requestLogging (cognitive 25) zio-http/shared/src/main/scala/zio/http/ZClientAspect.scala:184
- CharSequenceExtensions.compare (cognitive 25) zio-http/shared/src/main/scala/zio/http/internal/CharSequenceExtensions.scala:32
- PathCodecPlatformSpecific.parseLong (cognitive 24) zio-http/js/src/main/scala/zio/http/codec/PathCodecPlatformSpecific.scala:4
- URL.resolve (cognitive 24) zio-http/shared/src/main/scala/zio/http/URL.scala:189
- PathCodec.indexOfNextCodec (cognitive 24) zio-http/shared/src/main/scala/zio/http/codec/PathCodec.scala:408
- DatastarEndpointOps.makeRequest (cognitive 23) zio-http-datastar-sdk/src/main/scala/zio/http/datastar/DatastarPackageBase.scala:250
- FileBody.asStream (cognitive 23) zio-http/shared/src/main/scala/zio/http/Body.scala:808
- Middleware.cors (cognitive 23) zio-http/shared/src/main/scala/zio/http/Middleware.scala:81
- JsonSchema.fromSerializableSchema (cognitive 23) zio-http/shared/src/main/scala/zio/http/endpoint/openapi/JsonSchema.scala:274
- JsonSchema.fromZSchemaMultiple (cognitive 23) zio-http/shared/src/main/scala/zio/http/endpoint/openapi/JsonSchema.scala:502
- QueryParamEncoding.encode (cognitive 23) zio-http/shared/src/main/scala/zio/http/internal/QueryParamEncoding.scala:103
- HandlerAspect.apply (cognitive 22) zio-http/shared/src/main/scala/zio/http/HandlerAspect.scala:96
- HandlerAspect.applyHandlerContext (cognitive 22) zio-http/shared/src/main/scala/zio/http/HandlerAspect.scala:118
- HandlerAspect.applyHandler (cognitive 22) zio-http/shared/src/main/scala/zio/http/HandlerAspect.scala:135
- UUID.inUUIDUntil (cognitive 22) zio-http/shared/src/main/scala/zio/http/codec/SegmentCodec.scala:474
- Element.renderElementInternal (cognitive 22) zio-http/shared/src/main/scala/zio/http/template2/Dom.scala:283
- NettyDriver.start (cognitive 21) zio-http/jvm/src/main/scala/zio/http/netty/server/NettyDriver.scala:43
- OpenAPIGen.contentAsJsonSchema (cognitive 21) zio-http/shared/src/main/scala/zio/http/endpoint/openapi/OpenAPIGen.scala:346
- HandlerPlatformSpecific.fromResourceWithURL (cognitive 20) zio-http/jvm/src/main/scala/zio/http/HandlerPlatformSpecific.scala:31
- CachingResolver.refreshOrDropEntries (cognitive 20) zio-http/shared/src/main/scala/zio/http/DnsResolver.scala:131
- Dom.encode (cognitive 19) zio-http/shared/src/main/scala/zio/http/template/Dom.scala:43
- SmithyParser.convertTrait (cognitive 18) zio-http-gen/src/main/scala/zio/http/gen/smithy/Smithy.scala:951
- UrlInterpolatorMacro.url (cognitive 18) zio-http/shared/src/main/scala-2/zio/http/UrlInterpolator.scala:30
- Tree.++ (cognitive 18) zio-http/shared/src/main/scala/zio/http/RoutePattern.scala:193
- Tree.map (cognitive 18) zio-http/shared/src/main/scala/zio/http/RoutePattern.scala:236
- Doc.toPlaintext (cognitive 18) zio-http/shared/src/main/scala/zio/http/codec/Doc.scala:221
- RichTextCodec.parse (cognitive 18) zio-http/shared/src/main/scala/zio/http/codec/RichTextCodec.scala:610
- UUIDCodec.isDefinedAt (cognitive 18) zio-http/shared/src/main/scala/zio/http/codec/TextCodec.scala:163
- CachingResolver.resolve (cognitive 17) zio-http/shared/src/main/scala/zio/http/DnsResolver.scala:79
- DocWriter.append (cognitive 17) zio-http/shared/src/main/scala/zio/http/codec/Doc.scala:497
- OpenAPIGen.generateExamples (cognitive 17) zio-http/shared/src/main/scala/zio/http/endpoint/openapi/OpenAPIGen.scala:248
- OpenAPIGen.schemaByStatusAndMediaType (cognitive 17) zio-http/shared/src/main/scala/zio/http/endpoint/openapi/OpenAPIGen.scala:1126
- CookieEncoding.decodeResponseCookie (cognitive 17) zio-http/shared/src/main/scala/zio/http/internal/CookieEncoding.scala:115
- StringSchemaCodec.encode (cognitive 17) zio-http/shared/src/main/scala/zio/http/internal/StringSchemaCodec.scala:206
- ZClientPlatformSpecific.customized (cognitive 16) zio-http/jvm/src/main/scala/zio/http/ZClientPlatformSpecific.scala:16
- NettyBodyWriter.writeAndFlush (cognitive 16) zio-http/jvm/src/main/scala/zio/http/netty/NettyBodyWriter.scala:37
- Custom.equals (cognitive 16) REDACTED:261
- Response.throwableToMessage (cognitive 16) zio-http/shared/src/main/scala/zio/http/Response.scala:306
- ServerSentEvent.encodeWith (cognitive 16) zio-http/shared/src/main/scala/zio/http/ServerSentEvent.scala:57
- JsonSchema.flatten (cognitive 16) zio-http/shared/src/main/scala/zio/http/endpoint/openapi/JsonSchema.scala:1289
- QueryParamEncoding.decodeComponent (cognitive 16) zio-http/shared/src/main/scala/zio/http/internal/QueryParamEncoding.scala:159
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Near-duplicate member pair (32 shared lines) zio-http/shared/src/main/scala/zio/http/internal/StringSchemaCodec.scala:355
- Edited copy of a member (22 corresponding lines) zio-http/jvm/src/main/scala/zio/http/netty/client/ClientSSLConverter.scala:38
- Members sharing a duplicated core (13 members, 50+ identical tokens) zio-http/shared/src/main/scala/zio/http/codec/HttpCodec.scala:614
- Members sharing a duplicated core (7 members, 50+ identical tokens) zio-http-datastar-sdk/src/main/scala/zio/http/datastar/DatastarPackageBase.scala:569
- Members sharing a duplicated core (5 members, 50+ identical tokens) zio-http/shared/src/main/scala/zio/http/Middleware.scala:202
- Duplicated block (36–49 lines × 4) zio-http/shared/src/main/scala/zio/http/codec/HttpCodec.scala:1511
- Duplicated block (36–37 lines × 2) zio-http-gen/src/main/scala/zio/http/gen/openapi/EndpointGen.scala:485
- Duplicated block (36 lines × 2) zio-http-datastar-sdk/src/main/scala/zio/http/datastar/model/DatastarRequest.scala:80
- Duplicated block (32–35 lines × 4) zio-http/shared/src/main/scala/zio/http/codec/HttpCodec.scala:1113
- Duplicated block (33 lines × 2) zio-http-gen/src/main/scala/zio/http/gen/openapi/EndpointGen.scala:863
- Duplicated block (27 lines × 5) zio-http/shared/src/main/scala/zio/http/codec/HttpCodec.scala:1368
- Duplicated block (21–24 lines × 3) zio-http/shared/src/main/scala/zio/http/codec/HttpCodec.scala:827
- Duplicated block (21–24 lines × 2) zio-http/shared/src/main/scala/zio/http/Middleware.scala:423
- Duplicated block (22 lines × 2) zio-http/shared/src/main/scala/zio/http/HandlerAspect.scala:664
- Duplicated block (12–21 lines × 11) zio-http/shared/src/main/scala/zio/http/codec/HttpCodec.scala:744
- Duplicated block (11–20 lines × 12) zio-http/shared/src/main/scala/zio/http/codec/HttpCodec.scala:676
- Duplicated block (19–20 lines × 2) zio-http/jvm/src/main/scala/zio/http/netty/client/ClientSSLConverter.scala:41
- Duplicated block (16–18 lines × 3) zio-http/shared/src/main/scala-2/zio/http/template2/CssInterpolatorMacros.scala:27
- Duplicated block (18 lines × 2) zio-http-datastar-sdk/src/main/scala/zio/http/datastar/DatastarEvent.scala:233
- Duplicated block (16–17 lines × 2) zio-http/js/src/main/scala/zio/http/internal/FetchDriver.scala:24
- Duplicated block (17 lines × 2) REDACTED:741
- Duplicated block (2–17 lines × 3) zio-http/shared/src/main/scala/zio/http/codec/Combiner.scala:1103
- Duplicated block (15 lines × 3) zio-http/shared/src/main/scala/zio/http/ZClientAspect.scala:132
- Duplicated block (15 lines × 2) zio-http/shared/src/main/scala/zio/http/internal/CookieEncoding.scala:47
- Duplicated block (13–14 lines × 3) zio-http/shared/src/main/scala/zio/http/codec/HttpCodec.scala:619
- Duplicated block (13–14 lines × 2) zio-http/shared/src/main/scala/zio/http/codec/HttpCodec.scala:1913
- Duplicated block (10–13 lines × 3) zio-http/shared/src/main/scala/zio/http/ZClientAspect.scala:122
- Duplicated block (11 lines × 4) zio-http/shared/src/main/scala/zio/http/Route.scala:100
- Duplicated block (11 lines × 3) zio-http-gen/src/main/scala/zio/http/gen/openapi/EndpointGen.scala:1188
- Duplicated block (10 lines × 11) zio-http/shared/src/main/scala/zio/http/codec/HttpCodec.scala:746
- Duplicated block (8–10 lines × 3) zio-http-gen/src/main/scala/zio/http/gen/openapi/EndpointGen.scala:435
- Duplicated block (8–10 lines × 2) zio-http/shared/src/main/scala/zio/http/HandlerAspect.scala:654
- Duplicated block (8–9 lines × 5) zio-http-gen/src/main/scala/zio/http/gen/openapi/EndpointGen.scala:1193
- Duplicated block (8–9 lines × 4) zio-http/shared/src/main/scala/zio/http/ZClientAspect.scala:139
- Duplicated block (9 lines × 3) zio-http/shared/src/main/scala/zio/http/endpoint/Endpoint.scala:908
- Duplicated block (8 lines × 12) zio-http/shared/src/main/scala/zio/http/codec/HttpCodec.scala:679
- Duplicated block (8 lines × 6) zio-http/shared/src/main/scala/zio/http/codec/HttpCodec.scala:1261
- Duplicated block (7 lines × 7) zio-http-datastar-sdk/src/main/scala/zio/http/datastar/DatastarPackageBase.scala:585
- Duplicated block (6 lines × 6) zio-http/shared/src/main/scala/zio/http/codec/HttpCodec.scala:618
- Duplicated block (4–6 lines × 3) zio-http-datastar-sdk/src/main/scala/zio/http/datastar/DatastarEvent.scala:54
- Duplicated block (5 lines × 5) zio-http/shared/src/main/scala/zio/http/Middleware.scala:202
- Duplicated block (37 lines × 2) zio-http-example-jwt-bearer-refresh-token-auth/src/main/scala/example/auth/bearer/jwt/refresh/AuthenticationServer.scala:15
- Duplicated block (12–14 lines × 2) zio-http-example-jwt-bearer-refresh-token-auth/src/main/scala/example/auth/bearer/jwt/refresh/AuthenticationServer.scala:99
- Duplicated block (10–14 lines × 2) zio-http-example-jwt-bearer-refresh-token-auth/src/main/scala/example/auth/bearer/jwt/refresh/core/AuthMiddleware.scala:11
- Duplicated block (9–11 lines × 3) zio-http-example-jwt-bearer-refresh-token-auth/src/main/scala/example/auth/bearer/jwt/refresh/AuthenticationServer.scala:60
- Duplicated block (16 lines × 5) zio-http-example-cookie-auth/src/main/scala/example/auth/session/cookie/core/UserService.scala:24
- Duplicated block (30 lines × 2) zio-http-example/src/main/scala/example/endpoint/EndpointWithMultipleErrorsUsingEither.scala:36
- Duplicated block (8 lines × 3) zio-http-example-cookie-auth/src/main/scala/example/auth/session/cookie/AuthenticationServer.scala:35
- Off the main sequence: zioHttp
- Unfinished stub — body is `???` zio-http-cli/src/main/scala/zio/http/endpoint/cli/HttpCliApp.scala:88
- Unfinished stub — body is ??? / NotImplementedError zio-http-cli/src/main/scala/zio/http/endpoint/cli/HttpCliApp.scala:88
- Coverage collected but not gated
- No structured logging
- Sync-over-async blocking zio-http/jvm/src/main/scala/zio/http/netty/client/NettyClientDriver.scala:62
- Third-party script without Subresource Integrity zio-http-example-digest-auth/src/main/resources/digest-auth-client-simple.html:46
Minor — 95 finding(s)
- Orphaned file zio-http/shared/src/main/scala/zio/http/template/Attributes.scala:1
- Orphaned file zio-http/shared/src/main/scala/zio/http/SSLConfig.scala:1
- Orphaned file zio-http/shared/src/main/scala/zio/http/Flash.scala:1
- Orphaned file zio-http-example/src/main/scala/example/CombinerTypesExample.scala:1
- Orphaned file zio-http/shared/src/main/scala/zio/http/ProtocolStack.scala:1
- Orphaned file zio-http/shared/src/main/scala/zio/http/multipart/mixed/MultipartMixed.scala:1
- Orphaned file zio-http/shared/src/main/scala/zio/http/FormField.scala:1
- Orphaned file zio-http-htmx/src/main/scala/zio/http/htmx/Attributes.scala:1
- Orphaned file zio-http/shared/src/main/scala/zio/http/StreamingForm.scala:1
- Orphaned file zio-http/shared/src/main/scala/zio/http/template/Elements.scala:1
- Orphaned file zio-http/jvm/src/main/scala/zio/http/netty/client/NettyClientDriver.scala:1
- Orphaned file zio-http/shared/src/main/scala/zio/http/Form.scala:1
- Orphaned file zio-http/jvm/src/main/scala/zio/http/netty/NettyConfig.scala:1
- Orphaned file zio-http/shared/src/main/scala/zio/http/codec/StatusCodecs.scala:1
- Orphaned file zio-http/shared/src/main/scala/zio/http/codec/TextCodec.scala:1
- Orphaned file zio-http/jvm/src/main/scala/zio/http/netty/server/NettyDriver.scala:1
- Orphaned file project/ScalaSettings.scala:1
- Orphaned file zio-http/shared/src/main/scala/zio/http/codec/internal/Mechanic.scala:1
- Orphaned file zio-http/shared/src/main/scala/zio/http/internal/FormState.scala:1
- Orphaned file zio-http-tools/src/main/scala/zio/http/tools/GenerateMediaTypes.scala:1
- Orphaned file zio-http/jvm/src/main/scala/zio/http/netty/EventLoopGroups.scala:1
- Orphaned file zio-http/shared/src/main/scala/zio/http/ZCompose.scala:1
- Orphaned file zio-http/jvm/src/main/scala/zio/http/netty/socket/NettySocketProtocol.scala:1
- Orphaned file zio-http/shared/src/main/scala/zio/http/internal/CharSequenceExtensions.scala:1
- Orphaned file zio-http/jvm/src/main/scala/zio/http/netty/server/ServerChannelInitializer.scala:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated predicate website/src/components/OnboardAgentButton/NavbarButton.jsx:13
- Duplicated predicate zio-http/shared/src/main/scala/zio/http/codec/SegmentCodec.scala:483
- Duplicated predicate zio-http/shared/src/main/scala/zio/http/endpoint/http/HttpGen.scala:170
- Duplicated predicate zio-http/shared/src/main/scala/zio/http/codec/SegmentCodec.scala:487
- Duplicated predicate zio-http-gen/src/main/scala/zio/http/gen/openapi/EndpointGen.scala:1326
- Duplicated predicate zio-http-gen/src/main/scala/zio/http/gen/openapi/EndpointGen.scala:1322
- Duplicated predicate zio-http/jvm/src/main/scala/zio/http/netty/NettyQueryParamEncoding.scala:29
- Duplicated predicate zio-http/shared/src/main/scala-2/zio/http/template2/CssInterpolatorMacros.scala:44
- Disabled test zio-http-cli/src/test/scala/zio/http/endpoint/cli/CliSpec.scala:152
- Disabled test zio-http-gen/src/test/scala/zio/http/gen/scala/OpenAPICodeGenSpec.scala:119
- Disabled test zio-http/jvm/src/test/scala/zio/http/ClientSpec.scala:108
- Disabled test zio-http/jvm/src/test/scala/zio/http/ClientStreamingSpec.scala:319
- Disabled test zio-http/jvm/src/test/scala/zio/http/WebSocketSpec.scala:122
- Disabled test zio-http/jvm/src/test/scala/zio/http/netty/client/NettyConnectionPoolSpec.scala:274
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- Blanket warning suppression zio-http/shared/src/main/scala/zio/http/endpoint/EndpointLocator.scala:43
- No ADRs
- No release approval gate
- Benchmarks don't track allocations zio-http-benchmarks/src/main/scala-2.13/zio/http/benchmarks/EndpointBenchmark.scala
- No security response headers detected netlify.toml:1
- Scala's null is not held to the type system everywhere
Minor — 24 finding(s)
- Outdated: com.github.jwt-scala:jwt-core_2.13
- Outdated: com.github.jwt-scala:jwt-zio-json_2.13
- Outdated: com.lihaoyi:unroll-annotation_2.13
- Outdated: com.lihaoyi:unroll-plugin_2.13
- Outdated: com.softwaremill.sttp.tapir:tapir-http4s-server_2.13
- Outdated: com.softwaremill.sttp.tapir:tapir-json-circe_2.13
- Outdated: com.yubico:webauthn-server-attestation
- Outdated: com.yubico:webauthn-server-core
- Outdated: dev.zio:zio-config-magnolia_2.13
- Outdated: dev.zio:zio-config-typesafe_2.13
- Outdated: dev.zio:zio-config_2.13
- Outdated: dev.zio:zio-http_2.13
- Outdated: dev.zio:zio-json-yaml_2.13
- Outdated: dev.zio:zio-metrics-connectors-prometheus_2.13
- Outdated: dev.zio:zio-metrics-connectors_2.13
- Outdated: dev.zio:zio-schema-avro_2.13
- Outdated: dev.zio:zio-schema-json_2.13
- Outdated: dev.zio:zio-schema-msg-pack_2.13
- Outdated: dev.zio:zio-schema-protobuf_2.13
- Outdated: dev.zio:zio-schema-thrift_2.13
- Outdated: dev.zio:zio-schema_2.13
- Outdated: dev.zio:zio-streams_2.13
- Outdated: dev.zio:zio-test_2.13
- Outdated: dev.zio:zio_2.13
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-106789113ea74694bc85dcf474fc22c8/history.json --exit-code 0 --source . | 5 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-106789113ea74694bc85dcf474fc22c8/tree.json --exit-code 0 --source . | 3 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --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 . | 134 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 14 | artifacts/raw/trivy-config.json |
| 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 4 file(s) — `zio-http/shared/src/main/scala-3/zio/http/HandlerVersionSpecific.scala`, `zio-http/shared/src/main/scala-3/zio/http/RoutesCompanionVersionSpecific.scala`, `zio-http/shared/src/main/scala-3/zio/http/endpoint/extensions.scala`, `REDACTED` — so the PII/GDPR sweep did not cover them at all. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |