Executive summary
zio/zio-quill falls short of our standard for production, in part because it has pipeline tools referenced by a changeable name. It scores 55 out of 100 and is rated Adequate, and all 63 of its critical findings are security problems.
Security and Compliance, at 46, is the weakest lens and counts most in the score. The best first step for the work it takes is replacing the two exposed passwords or keys and switching the old ones off, worth about 3 points. Stopping the 12 pipeline steps that hand secrets to unpinned tools would lift Security and Compliance itself, worth about 5 points. Raising Security and Compliance to 70 would lift the score to about 60.
Thirty-seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Thirteen secrets can leak from the build pipeline, and eleven settings leave the servers or containers unsafe. Pinning each tool to an exact version, limiting each secret to its own step and correcting the unsafe settings would close these risks. The two passwords or keys in the code need replacing, with the old ones switched off.
The product code is 23,626 lines, about €65,000 to rebuild.
If Security and Compliance rose from 46 to 70, the lowest score rated Strong, the score would rise from 55 to about 60.
New since the last survey: 33 findings
- Code Duplication · Edited copy of a member (70 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala
- Code Duplication · Edited copy of a member (75 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala
- Code Duplication · Edited copy of a member (47 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala
- Code Duplication · Edited copy of a member (30 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala
- Code Duplication · Edited copy of a member (56 corresponding lines) quill-cassandra/src/main/scala/zio/quill/context/cassandra/encoding/UdtEncodingMacro.scala
- Code Duplication · Edited copy of a member (22 corresponding lines) quill-engine/src/main/scala/zio/quill/context/cassandra/CqlIdiom.scala
- Code Duplication · Edited copy of a member (36 corresponding lines) quill-engine/src/main/scala/zio/quill/norm/AdHocReduction.scala
- Code Duplication · Edited copy of a member (14 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala
- Code Duplication · Edited copy of a member (13 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala
- Code Duplication · Edited copy of a member (18 corresponding lines) quill-core/src/main/scala/zio/quill/quotation/TranspileConfigSummoning.scala
- Code Duplication · Edited copy of a member (17 corresponding lines) quill-engine/src/main/scala/zio/quill/norm/RepropagateQuats.scala
- Code Duplication · Edited copy of a member (17 corresponding lines) quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala
- Code Duplication · Edited copy of a member (11 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) quill-engine/src/main/scala/zio/quill/sql/norm/AddDropToNestedOrderBy.scala
- Code Duplication · Edited copy of a member (7 corresponding lines) quill-engine/src/main/scala/zio/quill/quotation/FreeVariables.scala
- Code Duplication · Edited copy of a member (9 corresponding lines) quill-engine/src/main/scala/zio/quill/sql/norm/ExpandNestedQueries.scala
- Code Duplication · Edited copy of a member (19 corresponding lines) quill-codegen-jdbc/src/main/scala/zio/quill/codegen/jdbc/gen/DefaultJdbcSchemaReader.scala
- Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) quill-jdbc/src/main/scala/zio/quill/context/jdbc/JdbcContextVerbExecute.scala
- Code Duplication · Edited copy of a member (7 corresponding lines) quill-engine/src/main/scala/zio/quill/sql/SqlQuery.scala
- Code Duplication · Edited copy of a member (10 corresponding lines) quill-jdbc-zio/src/main/scala-2.12/zio/quill/context/json/PostgresJsonExtensions.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformerWithStack.scala
- Code Duplication · Edited copy of a member (10 corresponding lines) quill-jdbc-zio/src/main/scala-2.12/zio/quill/context/json/PostgresJsonExtensions.scala
- Code Duplication · Edited copy of a member (11 corresponding lines) quill-cassandra-pekko/src/main/scala/zio/quill/CassandraPekkoContext.scala
- Code Duplication · Edited copy of a member (5 corresponding lines) quill-core/src/main/scala/zio/quill/context/mirror/MirrorEncoders.scala
- Code Duplication · Edited copy of a member (7 corresponding lines) quill-core/src/main/scala/zio/quill/AsyncMirrorContext.scala
- Code Duplication · Edited copy of a member (5 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala
- Code Duplication · Edited copy of a member (5 corresponding lines) quill-cassandra-pekko/src/main/scala/zio/quill/CassandraPekkoContext.scala
- Code Duplication · Edited copy of a member (5 corresponding lines) quill-jdbc/src/main/scala/zio/quill/context/jdbc/JdbcContextVerbExecute.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) quill-core/src/main/scala/zio/quill/AsyncMirrorContext.scala
- Code Duplication · Edited copy of a member (4 corresponding lines) quill-engine/src/main/scala/zio/quill/context/cassandra/CqlIdiom.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) quill-core/src/main/scala/zio/quill/context/ContextVerbTranslate.scala
- Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) quill-engine/src/main/scala/zio/quill/MySQLDialect.scala
- Code Duplication · Edited copy of a member (4 corresponding lines) quill-engine/src/main/scala/zio/quill/PostgresDialect.scala
Fixed since the last survey: 5 findings
- Code Duplication · Duplicated block (8–14 lines × 2) quill-engine/src/main/scala/zio/quill/SqliteDialect.scala
- Code Duplication · Duplicated block (8 lines × 2) quill-engine/src/main/scala/zio/quill/idiom/ReifyStatement.scala
- Code Duplication · Duplicated block (5 lines × 2) quill-engine/src/main/scala/zio/quill/OracleDialect.scala
- Code Duplication · Duplicated block (5 lines × 2) quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala
- Code Duplication · Duplicated block (5 lines × 2) quill-engine/src/main/scala/zio/quill/MirrorIdiom.scala
Rebuild cost: about €65,000 · Estimate
| Cost to rebuild | €21,000 to €110,000, for 358 to 1,137 hours of work, about 0.4 person-years for one engineer |
|---|---|
| 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.8 at a score of 55. 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: 23,626 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: which parts of the code depend on which
| uses → | 1 codegen.model | 2 monad | 3 util.Messages | 4 codegen.gen | 5 context.json | 6 context.mirror | 7 dsl | 8 idiom | 9 util | 10 codegen.jdbc.gen | 11 context | 12 idiom.StatementInterpolator | 13 norm | 14 context.orientdb | 15 quotation | 16 quat | 17 ast | 18 context.cassandra | 19 context.sql | 20 context.sql.idiom.SqlIdiom | 21 quat.Quat | 22 context.jdbc | 23 context.sql.idiom | 24 context.qzio | 25 sql.idiom | 26 zio.quill | 27 AsyncMirrorContext | 28 H2ZioJdbcContext | 29 MirrorContext | 30 MirrorSqlDialect | 31 MysqlZioJdbcContext | 32 PostgresDialect | 33 PostgresZioJdbcContext | 34 doobie | 35 jdbczio | 36 quotation.TranspileConfigSummoning | 37 sql.norm | 38 context.spark | 39 context.sql.norm | 40 jdbczio.Quill |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 codegen.model | ||||||||||||||||||||||||||||||||||||||||
| 2 monad | ||||||||||||||||||||||||||||||||||||||||
| 3 util.Messages | ||||||||||||||||||||||||||||||||||||||||
| 4 codegen.gen | 13 | |||||||||||||||||||||||||||||||||||||||
| 5 context.json | 2 | |||||||||||||||||||||||||||||||||||||||
| 6 context.mirror | 2 | |||||||||||||||||||||||||||||||||||||||
| 7 dsl | 1 | 2 | 3 | 7 | ||||||||||||||||||||||||||||||||||||
| 8 idiom | 2 | 1 | 8 | 3 | ||||||||||||||||||||||||||||||||||||
| 9 util | 2 | |||||||||||||||||||||||||||||||||||||||
| 10 codegen.jdbc.gen | 10 | 2 | ||||||||||||||||||||||||||||||||||||||
| 11 context | 2 | 6 | 2 | 3 | 8 | 4 | ||||||||||||||||||||||||||||||||||
| 12 idiom.StatementInterpolator | 5 | |||||||||||||||||||||||||||||||||||||||
| 13 norm | 1 | 2 | 1 | 58 | 2 | |||||||||||||||||||||||||||||||||||
| 14 context.orientdb | 3 | |||||||||||||||||||||||||||||||||||||||
| 15 quotation | 1 | 1 | 1 | 2 | 5 | 73 | ||||||||||||||||||||||||||||||||||
| 16 quat | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 ast | 76 | |||||||||||||||||||||||||||||||||||||||
| 18 context.cassandra | 1 | 4 | 7 | |||||||||||||||||||||||||||||||||||||
| 19 context.sql | 1 | 1 | 12 | 15 | 1 | |||||||||||||||||||||||||||||||||||
| 20 context.sql.idiom.SqlIdiom | 3 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 quat.Quat | 11 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 context.jdbc | 1 | 10 | 1 | 5 | ||||||||||||||||||||||||||||||||||||
| 23 context.sql.idiom | 3 | 1 | 1 | 2 | 3 | 1 | 24 | 8 | 1 | 4 | ||||||||||||||||||||||||||||||
| 24 context.qzio | 13 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 25 sql.idiom | 1 | 2 | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 26 zio.quill | 6 | 1 | 4 | 14 | 1 | 48 | 7 | 10 | 2 | 1 | 46 | 3 | 5 | 4 | 18 | 38 | 13 | 3 | ||||||||||||||||||||||
| 27 AsyncMirrorContext | 1 | 5 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 H2ZioJdbcContext | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 MirrorContext | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 MirrorSqlDialect | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 MysqlZioJdbcContext | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 PostgresDialect | 1 | 1 | 3 | 2 | ||||||||||||||||||||||||||||||||||||
| 33 PostgresZioJdbcContext | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 34 doobie | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 jdbczio | 4 | 1 | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 36 quotation.TranspileConfigSummoning | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 37 sql.norm | 2 | 21 | 11 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 context.spark | 1 | 2 | 1 | 1 | 7 | 4 | 1 | 4 | 2 | |||||||||||||||||||||||||||||||
| 39 context.sql.norm | 3 | 1 | 9 | 6 | 3 | |||||||||||||||||||||||||||||||||||
| 40 jdbczio.Quill | 1 | 7 | 7 | 7 |
4→1 codegen.gen uses codegen.model✕
- Connections
- 13 pairs of types, where a type in codegen.gen uses a type in codegen.model.
- The types involved
zio.quill.codegen.gen.CodeGeneratorComponents→zio.quill.codegen.model.NameParserzio.quill.codegen.gen.CodeGeneratorComponents→zio.quill.codegen.model.PackagingStrategyzio.quill.codegen.gen.CodeGeneratorComponents→zio.quill.codegen.model.RawSchemazio.quill.codegen.gen.CodeGeneratorComponents→zio.quill.codegen.model.UnrecognizedTypeStrategyzio.quill.codegen.gen.EmitterSettings→zio.quill.codegen.model.CodeWrapperzio.quill.codegen.gen.EmitterSettings→zio.quill.codegen.model.TableStereotypezio.quill.codegen.gen.Generator→zio.quill.codegen.model.RawSchemazio.quill.codegen.gen.PackageGen→zio.quill.codegen.model.CodeWrapperzio.quill.codegen.gen.StereotypePackager→zio.quill.codegen.model.CodeWrapperzio.quill.codegen.gen.StereotypePackager→zio.quill.codegen.model.PackageGroupingStrategyzio.quill.codegen.gen.StereotypePackager→zio.quill.codegen.model.PackageNamingStrategyzio.quill.codegen.gen.StereotypePackager→zio.quill.codegen.model.PackagingStrategyzio.quill.codegen.gen.StereotypePackager→zio.quill.codegen.model.TableStereotype
- Direction
- codegen.gen uses codegen.model, so a change to codegen.model can break codegen.gen, while a change to codegen.gen can't break codegen.model.
- Position
- Below the diagonal: codegen.gen uses a module listed above it, which is the healthy direction.
5→26 context.json uses zio.quill part of a loop✕
- Connections
- 2 pairs of types, where a type in context.json uses a type in zio.quill.
- The types involved
zio.quill.context.json.PostgresJsonExtensions→zio.quill.JsonValuezio.quill.context.json.PostgresJsonExtensions→zio.quill.JsonbValue
- Direction
- context.json uses zio.quill, so a change to zio.quill can break context.json, while a change to context.json can't break zio.quill.
- 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→26 context.mirror uses zio.quill part of a loop✕
- Connections
- 2 pairs of types, where a type in context.mirror uses a type in zio.quill.
- The types involved
zio.quill.context.mirror.MirrorDecoders→zio.quill.MappedEncodingzio.quill.context.mirror.MirrorEncoders→zio.quill.MappedEncoding
- Direction
- context.mirror uses zio.quill, so a change to zio.quill can break context.mirror, while a change to context.mirror can't break zio.quill.
- 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→15 dsl uses quotation part of a loop✕
- Connections
- 1 pair of types, where a type in dsl uses a type in quotation.
- The types involved
zio.quill.dsl.QuotationMacro→zio.quill.quotation.Quotation
- Direction
- dsl uses quotation, so a change to quotation can break dsl, while a change to dsl can't break quotation.
- 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→16 dsl uses quat part of a loop✕
- Connections
- 2 pairs of types, where a type in dsl uses a type in quat.
- The types involved
zio.quill.dsl.DynamicQueryDsl→zio.quill.quat.Quatzio.quill.dsl.DynamicQueryDsl→zio.quill.quat.TypeTaggedQuatMaking
- Direction
- dsl uses quat, so a change to quat can break dsl, while a change to dsl can't break quat.
- 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→17 dsl uses ast part of a loop✕
- Connections
- 3 pairs of types, where a type in dsl uses a type in ast.
- The types involved
zio.quill.dsl.DynamicQueryDsl→zio.quill.ast.Astzio.quill.dsl.DynamicQueryDsl→zio.quill.ast.Identzio.quill.dsl.DynamicQueryDsl→zio.quill.ast.Query
- Direction
- dsl uses ast, so a change to ast can break dsl, while a change to dsl can't break ast.
- 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→26 dsl uses zio.quill part of a loop✕
- Connections
- 7 pairs of types, where a type in dsl uses a type in zio.quill.
- The types involved
zio.quill.dsl.DynamicQueryDsl→zio.quill.EntityQueryzio.quill.dsl.DynamicQueryDsl→zio.quill.Quotedzio.quill.dsl.EncodingDsl→zio.quill.MappedEncodingzio.quill.dsl.EncodingDsl→zio.quill.Queryzio.quill.dsl.OrdDsl→zio.quill.Ordzio.quill.dsl.QueryDsl→zio.quill.EntityQueryzio.quill.dsl.QuotationDsl→zio.quill.Quoted
- Direction
- dsl uses zio.quill, so a change to zio.quill can break dsl, while a change to dsl can't break zio.quill.
- 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→11 idiom uses context part of a loop✕
- Connections
- 2 pairs of types, where a type in idiom uses a type in context.
- The types involved
zio.quill.idiom.Idiom→zio.quill.context.ExecutionTypezio.quill.idiom.Idiom→zio.quill.context.IdiomReturningCapability
- Direction
- idiom uses context, so a change to context can break idiom, while a change to idiom can't break context.
- 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→16 idiom uses quat part of a loop✕
- Connections
- 1 pair of types, where a type in idiom uses a type in quat.
- The types involved
zio.quill.idiom.Idiom→zio.quill.quat.Quat
- Direction
- idiom uses quat, so a change to quat can break idiom, while a change to idiom can't break quat.
- 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→17 idiom uses ast part of a loop✕
- Connections
- 8 pairs of types, where a type in idiom uses a type in ast.
- The types involved
zio.quill.idiom.Idiom→zio.quill.ast.Astzio.quill.idiom.QuotationTagToken→zio.quill.ast.QuotationTagzio.quill.idiom.ReifyStatementWithInjectables→zio.quill.ast.Mapzio.quill.idiom.ScalarLiftToken→zio.quill.ast.ScalarLiftzio.quill.idiom.ScalarTagToken→zio.quill.ast.ScalarTagzio.quill.idiom.StatementInterpolator→zio.quill.ast.Externalzio.quill.idiom.StatementInterpolator→zio.quill.ast.Liftzio.quill.idiom.StatementInterpolator→zio.quill.ast.Tag
- Direction
- idiom uses ast, so a change to ast can break idiom, while a change to idiom can't break ast.
- 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→26 idiom uses zio.quill part of a loop✕
- Connections
- 3 pairs of types, where a type in idiom uses a type in zio.quill.
- The types involved
zio.quill.idiom.Idiom→zio.quill.IdiomContextzio.quill.idiom.Idiom→zio.quill.NamingStrategyzio.quill.idiom.LoadNaming→zio.quill.NamingStrategy
- Direction
- idiom uses zio.quill, so a change to zio.quill can break idiom, while a change to idiom can't break zio.quill.
- 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→3 util uses util.Messages✕
- Connections
- 2 pairs of types, where a type in util uses a type in util.Messages.
- The types involved
zio.quill.util.Interpolator→zio.quill.util.Messages.TraceTypezio.quill.util.TraceConfig→zio.quill.util.Messages.TraceType
- Direction
- util uses util.Messages, so a change to util.Messages can break util, while a change to util can't break util.Messages.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
10→1 codegen.jdbc.gen uses codegen.model✕
- Connections
- 10 pairs of types, where a type in codegen.jdbc.gen uses a type in codegen.model.
- The types involved
zio.quill.codegen.jdbc.gen.DefaultJdbcSchemaReader→zio.quill.codegen.model.JdbcColumnMetazio.quill.codegen.jdbc.gen.DefaultJdbcSchemaReader→zio.quill.codegen.model.JdbcTableMetazio.quill.codegen.jdbc.gen.DefaultJdbcSchemaReader→zio.quill.codegen.model.RawSchemazio.quill.codegen.jdbc.gen.JdbcCodeGeneratorComponents→zio.quill.codegen.model.NameParserzio.quill.codegen.jdbc.gen.JdbcCodeGeneratorComponents→zio.quill.codegen.model.NumericPreferencezio.quill.codegen.jdbc.gen.JdbcCodeGeneratorComponents→zio.quill.codegen.model.PackagingStrategyzio.quill.codegen.jdbc.gen.JdbcCodeGeneratorComponents→zio.quill.codegen.model.UnrecognizedTypeStrategyzio.quill.codegen.jdbc.gen.JdbcGenerator→zio.quill.codegen.model.JdbcColumnMetazio.quill.codegen.jdbc.gen.JdbcGenerator→zio.quill.codegen.model.JdbcTableMetazio.quill.codegen.jdbc.gen.JdbcGenerator→zio.quill.codegen.model.RawSchema
- Direction
- codegen.jdbc.gen uses codegen.model, so a change to codegen.model can break codegen.jdbc.gen, while a change to codegen.jdbc.gen can't break codegen.model.
- Position
- Below the diagonal: codegen.jdbc.gen uses a module listed above it, which is the healthy direction.
10→4 codegen.jdbc.gen uses codegen.gen✕
- Connections
- 2 pairs of types, where a type in codegen.jdbc.gen uses a type in codegen.gen.
- The types involved
zio.quill.codegen.jdbc.gen.JdbcCodeGeneratorComponents→zio.quill.codegen.gen.CodeGeneratorComponentszio.quill.codegen.jdbc.gen.JdbcGenerator→zio.quill.codegen.gen.Generator
- Direction
- codegen.jdbc.gen uses codegen.gen, so a change to codegen.gen can break codegen.jdbc.gen, while a change to codegen.jdbc.gen can't break codegen.gen.
- Position
- Below the diagonal: codegen.jdbc.gen uses a module listed above it, which is the healthy direction.
11→7 context uses dsl✕
- Connections
- 2 pairs of types, where a type in context uses a type in dsl.
- The types involved
zio.quill.context.Context→zio.quill.dsl.CoreDslzio.quill.context.ContextVerbPrepare→zio.quill.dsl.CoreDsl
- Direction
- context uses dsl, so a change to dsl can break context, while a change to context can't break dsl.
- Position
- Below the diagonal: context uses a module listed above it, which is the healthy direction.
11→8 context uses idiom✕
- Connections
- 6 pairs of types, where a type in context uses a type in idiom.
- The types involved
zio.quill.context.CanDoBatchedInsert→zio.quill.idiom.Idiomzio.quill.context.CanDoBatchedInsert→zio.quill.idiom.Tokenzio.quill.context.Expand→zio.quill.idiom.Idiomzio.quill.context.Expand→zio.quill.idiom.Statementzio.quill.context.ExpandWithInjectables→zio.quill.idiom.Idiomzio.quill.context.ExpandWithInjectables→zio.quill.idiom.Statement
- Direction
- context uses idiom, so a change to idiom can break context, while a change to context can't break idiom.
- Position
- Below the diagonal: context uses a module listed above it, which is the healthy direction.
11→15 context uses quotation part of a loop✕
- Connections
- 2 pairs of types, where a type in context uses a type in quotation.
- The types involved
zio.quill.context.ActionMacro→zio.quill.quotation.ReifyLiftingszio.quill.context.ContextMacro→zio.quill.quotation.Quotation
- Direction
- context uses quotation, so a change to quotation can break context, while a change to context can't break quotation.
- 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→16 context uses quat part of a loop✕
- Connections
- 3 pairs of types, where a type in context uses a type in quat.
- The types involved
zio.quill.context.ContextMacro→zio.quill.quat.Quatzio.quill.context.ExecutionInfo→zio.quill.quat.Quatzio.quill.context.QueryMacro→zio.quill.quat.Quat
- Direction
- context uses quat, so a change to quat can break context, while a change to context can't break quat.
- 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→17 context uses ast part of a loop✕
- Connections
- 8 pairs of types, where a type in context uses a type in ast.
- The types involved
zio.quill.context.CanDoBatchedInsert→zio.quill.ast.Astzio.quill.context.ContextMacro→zio.quill.ast.Astzio.quill.context.ContextTranslateMacro→zio.quill.ast.ScalarLiftzio.quill.context.ContextTranslateProto→zio.quill.ast.ScalarLiftzio.quill.context.ExecutionInfo→zio.quill.ast.Astzio.quill.context.Expand→zio.quill.ast.Astzio.quill.context.ExpandWithInjectables→zio.quill.ast.Astzio.quill.context.VerifyFreeVariables→zio.quill.ast.Ast
- Direction
- context uses ast, so a change to ast can break context, while a change to context can't break ast.
- 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→26 context uses zio.quill part of a loop✕
- Connections
- 4 pairs of types, where a type in context uses a type in zio.quill.
- The types involved
zio.quill.context.CanDoBatchedInsert→zio.quill.IdiomContextzio.quill.context.Expand→zio.quill.NamingStrategyzio.quill.context.ExpandWithInjectables→zio.quill.NamingStrategyzio.quill.context.ProtoContext→zio.quill.ReturnAction
- Direction
- context uses zio.quill, so a change to zio.quill can break context, while a change to context can't break zio.quill.
- 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→8 idiom.StatementInterpolator uses idiom✕
- Connections
- 5 pairs of types, where a type in idiom.StatementInterpolator uses a type in idiom.
- The types involved
zio.quill.idiom.StatementInterpolator.Impl→zio.quill.idiom.Statementzio.quill.idiom.StatementInterpolator.Impl→zio.quill.idiom.Tokenzio.quill.idiom.StatementInterpolator.TokenImplicit→zio.quill.idiom.Tokenzio.quill.idiom.StatementInterpolator.TokenList→zio.quill.idiom.Statementzio.quill.idiom.StatementInterpolator.Tokenizer→zio.quill.idiom.Token
- Direction
- idiom.StatementInterpolator uses idiom, so a change to idiom can break idiom.StatementInterpolator, while a change to idiom.StatementInterpolator can't break idiom.
- Position
- Below the diagonal: idiom.StatementInterpolator uses a module listed above it, which is the healthy direction.
13→8 norm uses idiom✕
- Connections
- 1 pair of types, where a type in norm uses a type in idiom.
- The types involved
zio.quill.norm.ExpandReturning→zio.quill.idiom.Idiom
- Direction
- norm uses idiom, so a change to idiom can break norm, while a change to norm can't break idiom.
- Position
- Below the diagonal: norm uses a module listed above it, which is the healthy direction.
13→9 norm uses util✕
- Connections
- 2 pairs of types, where a type in norm uses a type in util.
- The types involved
zio.quill.norm.SheathLeafClauses→zio.quill.util.TraceConfigzio.quill.norm.TranspileConfig→zio.quill.util.TraceConfig
- Direction
- norm uses util, so a change to util can break norm, while a change to norm can't break util.
- Position
- Below the diagonal: norm uses a module listed above it, which is the healthy direction.
13→16 norm uses quat part of a loop✕
- Connections
- 1 pair of types, where a type in norm uses a type in quat.
- The types involved
zio.quill.norm.RepropagateQuats→zio.quill.quat.Quat
- Direction
- norm uses quat, so a change to quat can break norm, while a change to norm can't break quat.
- 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→17 norm uses ast part of a loop✕
- Connections
- 58 pairs of types, where a type in norm uses a type in ast. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
zio.quill.norm.AdHocReduction→zio.quill.ast.Queryzio.quill.norm.ApplyMap→zio.quill.ast.Astzio.quill.norm.ApplyMap→zio.quill.ast.Identzio.quill.norm.ApplyMap→zio.quill.ast.Queryzio.quill.norm.ApplyRenamesToProps→zio.quill.ast.Astzio.quill.norm.ApplyRenamesToProps→zio.quill.ast.Propertyzio.quill.norm.ApplyRenamesToProps→zio.quill.ast.StatelessTransformerzio.quill.norm.AttachToEntity→zio.quill.ast.Astzio.quill.norm.AttachToEntity→zio.quill.ast.Identzio.quill.norm.BetaReduction→zio.quill.ast.Assignmentzio.quill.norm.BetaReduction→zio.quill.ast.AssignmentDualzio.quill.norm.BetaReduction→zio.quill.ast.Astzio.quill.norm.BetaReduction→zio.quill.ast.OptionOperationzio.quill.norm.BetaReduction→zio.quill.ast.Queryzio.quill.norm.BetaReduction→zio.quill.ast.StatelessTransformerzio.quill.norm.CompleteRenames→zio.quill.ast.Astzio.quill.norm.CompleteRenames→zio.quill.ast.Identzio.quill.norm.CompleteRenames→zio.quill.ast.Queryzio.quill.norm.CompleteRenames→zio.quill.ast.StatelessTransformerzio.quill.norm.ExpandReturning→zio.quill.ast.ReturningActionzio.quill.norm.FlattenOptionOperation→zio.quill.ast.Astzio.quill.norm.FlattenOptionOperation→zio.quill.ast.Identzio.quill.norm.FlattenOptionOperation→zio.quill.ast.StatelessTransformerzio.quill.norm.Normalize→zio.quill.ast.Actionzio.quill.norm.Normalize→zio.quill.ast.Ast
- Direction
- norm uses ast, so a change to ast can break norm, while a change to norm can't break ast.
- 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→26 norm uses zio.quill part of a loop✕
- Connections
- 2 pairs of types, where a type in norm uses a type in zio.quill.
- The types involved
zio.quill.norm.ExpandReturning→zio.quill.IdiomContextzio.quill.norm.ExpandReturning→zio.quill.NamingStrategy
- Direction
- norm uses zio.quill, so a change to zio.quill can break norm, while a change to norm can't break zio.quill.
- 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→11 context.orientdb uses context✕
- Connections
- 3 pairs of types, where a type in context.orientdb uses a type in context.
- The types involved
zio.quill.context.orientdb.OrientDBContext→zio.quill.context.Contextzio.quill.context.orientdb.OrientDBIdiom→zio.quill.context.CannotReturnzio.quill.context.orientdb.OrientDBSessionContext→zio.quill.context.Context
- Direction
- context.orientdb uses context, so a change to context can break context.orientdb, while a change to context.orientdb can't break context.
- Position
- Below the diagonal: context.orientdb uses a module listed above it, which is the healthy direction.
15→3 quotation uses util.Messages✕
- Connections
- 1 pair of types, where a type in quotation uses a type in util.Messages.
- The types involved
zio.quill.quotation.TranspileConfigSummoning→zio.quill.util.Messages.TraceType
- Direction
- quotation uses util.Messages, so a change to util.Messages can break quotation, while a change to quotation can't break util.Messages.
- Position
- Below the diagonal: quotation uses a module listed above it, which is the healthy direction.
15→7 quotation uses dsl✕
- Connections
- 1 pair of types, where a type in quotation uses a type in dsl.
- The types involved
zio.quill.quotation.Parsing→zio.quill.dsl.ValueComputation
- Direction
- quotation uses dsl, so a change to dsl can break quotation, while a change to quotation can't break dsl.
- Position
- Below the diagonal: quotation uses a module listed above it, which is the healthy direction.
15→11 quotation uses context✕
- Connections
- 1 pair of types, where a type in quotation uses a type in context.
- The types involved
zio.quill.quotation.Parsing→zio.quill.context.ReturningCapability
- Direction
- quotation uses context, so a change to context can break quotation, while a change to quotation can't break context.
- Position
- Below the diagonal: quotation uses a module listed above it, which is the healthy direction.
15→13 quotation uses norm✕
- Connections
- 2 pairs of types, where a type in quotation uses a type in norm.
- The types involved
zio.quill.quotation.TranspileConfigSummoning→zio.quill.norm.OptionalPhasezio.quill.quotation.TranspileConfigSummoning→zio.quill.norm.TranspileConfig
- Direction
- quotation uses norm, so a change to norm can break quotation, while a change to quotation can't break norm.
- Position
- Below the diagonal: quotation uses a module listed above it, which is the healthy direction.
15→16 quotation uses quat part of a loop✕
- Connections
- 5 pairs of types, where a type in quotation uses a type in quat.
- The types involved
zio.quill.quotation.Parsing→zio.quill.quat.Quatzio.quill.quotation.Parsing→zio.quill.quat.QuatMakingzio.quill.quotation.QuatLiftable→zio.quill.quat.Quatzio.quill.quotation.QuatUnliftable→zio.quill.quat.Quatzio.quill.quotation.ReifyLiftings→zio.quill.quat.QuatMaking
- Direction
- quotation uses quat, so a change to quat can break quotation, while a change to quotation can't break quat.
- 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→17 quotation uses ast part of a loop✕
- Connections
- 73 pairs of types, where a type in quotation uses a type in ast. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
zio.quill.quotation.FreeVariables→zio.quill.ast.Actionzio.quill.quotation.FreeVariables→zio.quill.ast.Assignmentzio.quill.quotation.FreeVariables→zio.quill.ast.AssignmentDualzio.quill.quotation.FreeVariables→zio.quill.ast.Astzio.quill.quotation.FreeVariables→zio.quill.ast.Identzio.quill.quotation.FreeVariables→zio.quill.ast.IdentNamezio.quill.quotation.FreeVariables→zio.quill.ast.OptionOperationzio.quill.quotation.FreeVariables→zio.quill.ast.Queryzio.quill.quotation.FreeVariables→zio.quill.ast.StatefulTransformerzio.quill.quotation.IsDynamic→zio.quill.ast.Astzio.quill.quotation.Liftables→zio.quill.ast.Actionzio.quill.quotation.Liftables→zio.quill.ast.AggregationOperatorzio.quill.quotation.Liftables→zio.quill.ast.Assignmentzio.quill.quotation.Liftables→zio.quill.ast.AssignmentDualzio.quill.quotation.Liftables→zio.quill.ast.Astzio.quill.quotation.Liftables→zio.quill.ast.BinaryOperatorzio.quill.quotation.Liftables→zio.quill.ast.ExternalIdentzio.quill.quotation.Liftables→zio.quill.ast.Identzio.quill.quotation.Liftables→zio.quill.ast.IterableOperationzio.quill.quotation.Liftables→zio.quill.ast.JoinTypezio.quill.quotation.Liftables→zio.quill.ast.Liftzio.quill.quotation.Liftables→zio.quill.ast.OptionOperationzio.quill.quotation.Liftables→zio.quill.ast.Orderingzio.quill.quotation.Liftables→zio.quill.ast.Propertyzio.quill.quotation.Liftables→zio.quill.ast.PropertyAlias
- Direction
- quotation uses ast, so a change to ast can break quotation, while a change to quotation can't break ast.
- 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→15 quat uses quotation✕
- Connections
- 1 pair of types, where a type in quat uses a type in quotation.
- The types involved
zio.quill.quat.QuatMakingBase→zio.quill.quotation.MacroUtilUniverse
- Direction
- quat uses quotation, so a change to quotation can break quat, while a change to quat can't break quotation.
- Position
- Below the diagonal: quat uses a module listed above it, which is the healthy direction.
16→17 quat uses ast part of a loop✕
- Connections
- 1 pair of types, where a type in quat uses a type in ast.
- The types involved
zio.quill.quat.QuatNestingHelper→zio.quill.ast.Ast
- Direction
- quat uses ast, so a change to ast can break quat, while a change to quat can't break ast.
- 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→16 ast uses quat✕
- Connections
- 76 pairs of types, where a type in ast uses a type in quat. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
zio.quill.ast.Aggregation→zio.quill.quat.Quatzio.quill.ast.Assignment→zio.quill.quat.Quatzio.quill.ast.AssignmentDual→zio.quill.quat.Quatzio.quill.ast.Ast→zio.quill.quat.Quatzio.quill.ast.BinaryOperation→zio.quill.quat.Quatzio.quill.ast.Block→zio.quill.quat.Quatzio.quill.ast.CaseClass→zio.quill.quat.Quatzio.quill.ast.CaseClassQueryLift→zio.quill.quat.Quatzio.quill.ast.CaseClassValueLift→zio.quill.quat.Quatzio.quill.ast.ConcatMap→zio.quill.quat.Quatzio.quill.ast.Constant→zio.quill.quat.Quatzio.quill.ast.Delete→zio.quill.quat.Quatzio.quill.ast.Distinct→zio.quill.quat.Quatzio.quill.ast.DistinctOn→zio.quill.quat.Quatzio.quill.ast.Drop→zio.quill.quat.Quatzio.quill.ast.Dynamic→zio.quill.quat.Quatzio.quill.ast.Entity→zio.quill.quat.Quatzio.quill.ast.ExternalIdent→zio.quill.quat.Quatzio.quill.ast.Filter→zio.quill.quat.Quatzio.quill.ast.FilterIfDefined→zio.quill.quat.Quatzio.quill.ast.FlatJoin→zio.quill.quat.Quatzio.quill.ast.FlatMap→zio.quill.quat.Quatzio.quill.ast.Foreach→zio.quill.quat.Quatzio.quill.ast.Function→zio.quill.quat.Quatzio.quill.ast.FunctionApply→zio.quill.quat.Quat
- Direction
- ast uses quat, so a change to quat can break ast, while a change to ast can't break quat.
- Position
- Below the diagonal: ast uses a module listed above it, which is the healthy direction.
18→9 context.cassandra uses util✕
- Connections
- 1 pair of types, where a type in context.cassandra uses a type in util.
- The types involved
zio.quill.context.cassandra.CassandraPrepareContext→zio.quill.util.ContextLogger
- Direction
- context.cassandra uses util, so a change to util can break context.cassandra, while a change to context.cassandra can't break util.
- Position
- Below the diagonal: context.cassandra uses a module listed above it, which is the healthy direction.
18→11 context.cassandra uses context✕
- Connections
- 4 pairs of types, where a type in context.cassandra uses a type in context.
- The types involved
zio.quill.context.cassandra.CassandraContext→zio.quill.context.Contextzio.quill.context.cassandra.CassandraPrepareContext→zio.quill.context.ExecutionInfozio.quill.context.cassandra.CassandraRowContext→zio.quill.context.Contextzio.quill.context.cassandra.CqlIdiom→zio.quill.context.CannotReturn
- Direction
- context.cassandra uses context, so a change to context can break context.cassandra, while a change to context.cassandra can't break context.
- Position
- Below the diagonal: context.cassandra uses a module listed above it, which is the healthy direction.
18→17 context.cassandra uses ast✕
- Connections
- 7 pairs of types, where a type in context.cassandra uses a type in ast.
- The types involved
zio.quill.context.cassandra.CqlNormalize→zio.quill.ast.Astzio.quill.context.cassandra.CqlQuery→zio.quill.ast.Astzio.quill.context.cassandra.CqlQuery→zio.quill.ast.Entityzio.quill.context.cassandra.ExpandMappedInfixCassandra→zio.quill.ast.Astzio.quill.context.cassandra.ExpandMappedInfixCassandra→zio.quill.ast.StatelessTransformerzio.quill.context.cassandra.OrderByCriteria→zio.quill.ast.Propertyzio.quill.context.cassandra.OrderByCriteria→zio.quill.ast.PropertyOrdering
- Direction
- context.cassandra uses ast, so a change to ast can break context.cassandra, while a change to context.cassandra can't break ast.
- Position
- Below the diagonal: context.cassandra uses a module listed above it, which is the healthy direction.
19→9 context.sql uses util✕
- Connections
- 1 pair of types, where a type in context.sql uses a type in util.
- The types involved
zio.quill.context.sql.SqlQueryApply→zio.quill.util.Interpolator
- Direction
- context.sql uses util, so a change to util can break context.sql, while a change to context.sql can't break util.
- Position
- Below the diagonal: context.sql uses a module listed above it, which is the healthy direction.
19→11 context.sql uses context✕
- Connections
- 1 pair of types, where a type in context.sql uses a type in context.
- The types involved
zio.quill.context.sql.SqlContext→zio.quill.context.Context
- Direction
- context.sql uses context, so a change to context can break context.sql, while a change to context.sql can't break context.
- Position
- Below the diagonal: context.sql uses a module listed above it, which is the healthy direction.
19→16 context.sql uses quat✕
- Connections
- 12 pairs of types, where a type in context.sql uses a type in quat.
- The types involved
zio.quill.context.sql.CaseClassMake→zio.quill.quat.Quatzio.quill.context.sql.FlatJoinContext→zio.quill.quat.Quatzio.quill.context.sql.FlattenSqlQuery→zio.quill.quat.Quatzio.quill.context.sql.FromContext→zio.quill.quat.Quatzio.quill.context.sql.InfixContext→zio.quill.quat.Quatzio.quill.context.sql.JoinContext→zio.quill.quat.Quatzio.quill.context.sql.QueryContext→zio.quill.quat.Quatzio.quill.context.sql.SetOperationSqlQuery→zio.quill.quat.Quatzio.quill.context.sql.SqlQuery→zio.quill.quat.Quatzio.quill.context.sql.TableContext→zio.quill.quat.Quatzio.quill.context.sql.TopInfixQuery→zio.quill.quat.Quatzio.quill.context.sql.UnaryOperationSqlQuery→zio.quill.quat.Quat
- Direction
- context.sql uses quat, so a change to quat can break context.sql, while a change to context.sql can't break quat.
- Position
- Below the diagonal: context.sql uses a module listed above it, which is the healthy direction.
19→17 context.sql uses ast✕
- Connections
- 15 pairs of types, where a type in context.sql uses a type in ast.
- The types involved
zio.quill.context.sql.CaseClassMake→zio.quill.ast.CaseClasszio.quill.context.sql.FlatJoinContext→zio.quill.ast.Astzio.quill.context.sql.FlatJoinContext→zio.quill.ast.JoinTypezio.quill.context.sql.FlattenSqlQuery→zio.quill.ast.Astzio.quill.context.sql.InfixContext→zio.quill.ast.Infixzio.quill.context.sql.JoinContext→zio.quill.ast.Astzio.quill.context.sql.JoinContext→zio.quill.ast.JoinTypezio.quill.context.sql.OrderByCriteria→zio.quill.ast.Astzio.quill.context.sql.OrderByCriteria→zio.quill.ast.PropertyOrderingzio.quill.context.sql.SelectValue→zio.quill.ast.Astzio.quill.context.sql.SqlQueryApply→zio.quill.ast.Astzio.quill.context.sql.TableContext→zio.quill.ast.Entityzio.quill.context.sql.TakeDropFlatten→zio.quill.ast.Queryzio.quill.context.sql.TopInfixQuery→zio.quill.ast.Infixzio.quill.context.sql.UnaryOperationSqlQuery→zio.quill.ast.UnaryOperator
- Direction
- context.sql uses ast, so a change to ast can break context.sql, while a change to context.sql can't break ast.
- Position
- Below the diagonal: context.sql uses a module listed above it, which is the healthy direction.
19→26 context.sql uses zio.quill part of a loop✕
- Connections
- 1 pair of types, where a type in context.sql uses a type in zio.quill.
- The types involved
zio.quill.context.sql.SelectValue→zio.quill.PseudoAst
- Direction
- context.sql uses zio.quill, so a change to zio.quill can break context.sql, while a change to context.sql can't break zio.quill.
- 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→8 context.sql.idiom.SqlIdiom uses idiom✕
- Connections
- 3 pairs of types, where a type in context.sql.idiom.SqlIdiom uses a type in idiom.
- The types involved
zio.quill.context.sql.idiom.SqlIdiom.FlattenSqlQueryTokenizerHelper→zio.quill.idiom.Statementzio.quill.context.sql.idiom.SqlIdiom.FlattenSqlQueryTokenizerHelper→zio.quill.idiom.Tokenzio.quill.context.sql.idiom.SqlIdiom.InsertUpdateStmt→zio.quill.idiom.Statement
- Direction
- context.sql.idiom.SqlIdiom uses idiom, so a change to idiom can break context.sql.idiom.SqlIdiom, while a change to context.sql.idiom.SqlIdiom can't break idiom.
- Position
- Below the diagonal: context.sql.idiom.SqlIdiom uses a module listed above it, which is the healthy direction.
20→17 context.sql.idiom.SqlIdiom uses ast✕
- Connections
- 2 pairs of types, where a type in context.sql.idiom.SqlIdiom uses a type in ast.
- The types involved
zio.quill.context.sql.idiom.SqlIdiom.TokenizeProperty→zio.quill.ast.Astzio.quill.context.sql.idiom.SqlIdiom.TokenizeProperty→zio.quill.ast.Renameable
- Direction
- context.sql.idiom.SqlIdiom uses ast, so a change to ast can break context.sql.idiom.SqlIdiom, while a change to context.sql.idiom.SqlIdiom can't break ast.
- Position
- Below the diagonal: context.sql.idiom.SqlIdiom uses a module listed above it, which is the healthy direction.
20→26 context.sql.idiom.SqlIdiom uses zio.quill part of a loop✕
- Connections
- 1 pair of types, where a type in context.sql.idiom.SqlIdiom uses a type in zio.quill.
- The types involved
zio.quill.context.sql.idiom.SqlIdiom.TokenizeProperty→zio.quill.NamingStrategy
- Direction
- context.sql.idiom.SqlIdiom uses zio.quill, so a change to zio.quill can break context.sql.idiom.SqlIdiom, while a change to context.sql.idiom.SqlIdiom can't break zio.quill.
- 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.
21→16 quat.Quat uses quat✕
- Connections
- 11 pairs of types, where a type in quat.Quat uses a type in quat.
- The types involved
zio.quill.quat.Quat.Generic→zio.quill.quat.Quatzio.quill.quat.Quat.Is→zio.quill.quat.Quatzio.quill.quat.Quat.IsAbstract→zio.quill.quat.Quatzio.quill.quat.Quat.NoRenames→zio.quill.quat.Quatzio.quill.quat.Quat.NotAbstract→zio.quill.quat.Quatzio.quill.quat.Quat.Null→zio.quill.quat.Quatzio.quill.quat.Quat.Placeholder→zio.quill.quat.Quatzio.quill.quat.Quat.Primitive→zio.quill.quat.Quatzio.quill.quat.Quat.Product→zio.quill.quat.Quatzio.quill.quat.Quat.Tuple→zio.quill.quat.Quatzio.quill.quat.Quat.Unknown→zio.quill.quat.Quat
- Direction
- quat.Quat uses quat, so a change to quat can break quat.Quat, while a change to quat.Quat can't break quat.
- Position
- Below the diagonal: quat.Quat uses a module listed above it, which is the healthy direction.
21→17 quat.Quat uses ast✕
- Connections
- 1 pair of types, where a type in quat.Quat uses a type in ast.
- The types involved
zio.quill.quat.Quat.Is→zio.quill.ast.Ast
- Direction
- quat.Quat uses ast, so a change to ast can break quat.Quat, while a change to quat.Quat can't break ast.
- Position
- Below the diagonal: quat.Quat uses a module listed above it, which is the healthy direction.
22→2 context.jdbc uses monad✕
- Connections
- 1 pair of types, where a type in context.jdbc uses a type in monad.
- The types involved
zio.quill.context.jdbc.JdbcContext→zio.quill.monad.SyncIOMonad
- Direction
- context.jdbc uses monad, so a change to monad can break context.jdbc, while a change to context.jdbc can't break monad.
- Position
- Below the diagonal: context.jdbc uses a module listed above it, which is the healthy direction.
22→11 context.jdbc uses context✕
- Connections
- 10 pairs of types, where a type in context.jdbc uses a type in context.
- The types involved
zio.quill.context.jdbc.JdbcContext→zio.quill.context.ContextVerbTranslatezio.quill.context.jdbc.JdbcContext→zio.quill.context.ExecutionInfozio.quill.context.jdbc.JdbcContext→zio.quill.context.ProtoContextzio.quill.context.jdbc.JdbcContextBase→zio.quill.context.ContextVerbPrepareLambdazio.quill.context.jdbc.JdbcContextTypes→zio.quill.context.Contextzio.quill.context.jdbc.JdbcContextVerbExecute→zio.quill.context.ExecutionInfozio.quill.context.jdbc.JdbcContextVerbPrepare→zio.quill.context.ContextVerbPreparezio.quill.context.jdbc.JdbcContextVerbPrepare→zio.quill.context.ExecutionInfozio.quill.context.jdbc.SqlServerExecuteOverride→zio.quill.context.ExecutionInfozio.quill.context.jdbc.SqliteExecuteOverride→zio.quill.context.ExecutionInfo
- Direction
- context.jdbc uses context, so a change to context can break context.jdbc, while a change to context.jdbc can't break context.
- Position
- Below the diagonal: context.jdbc uses a module listed above it, which is the healthy direction.
22→19 context.jdbc uses context.sql✕
- Connections
- 1 pair of types, where a type in context.jdbc uses a type in context.sql.
- The types involved
zio.quill.context.jdbc.JdbcContextTypes→zio.quill.context.sql.SqlContext
- Direction
- context.jdbc uses context.sql, so a change to context.sql can break context.jdbc, while a change to context.jdbc can't break context.sql.
- Position
- Below the diagonal: context.jdbc uses a module listed above it, which is the healthy direction.
22→26 context.jdbc uses zio.quill part of a loop✕
- Connections
- 5 pairs of types, where a type in context.jdbc uses a type in zio.quill.
- The types involved
zio.quill.context.jdbc.Decoders→zio.quill.MappedEncodingzio.quill.context.jdbc.Encoders→zio.quill.MappedEncodingzio.quill.context.jdbc.JdbcContext→zio.quill.ReturnActionzio.quill.context.jdbc.JdbcContextVerbExecute→zio.quill.ReturnActionzio.quill.context.jdbc.SqlServerExecuteOverride→zio.quill.ReturnAction
- Direction
- context.jdbc uses zio.quill, so a change to zio.quill can break context.jdbc, while a change to context.jdbc can't break zio.quill.
- 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.
23→8 context.sql.idiom uses idiom✕
- Connections
- 3 pairs of types, where a type in context.sql.idiom uses a type in idiom.
- The types involved
zio.quill.context.sql.idiom.SqlIdiom→zio.quill.idiom.Idiomzio.quill.context.sql.idiom.SqlIdiom→zio.quill.idiom.Statementzio.quill.context.sql.idiom.SqlIdiom→zio.quill.idiom.Token
- Direction
- context.sql.idiom uses idiom, so a change to idiom can break context.sql.idiom, while a change to context.sql.idiom can't break idiom.
- Position
- Below the diagonal: context.sql.idiom uses a module listed above it, which is the healthy direction.
23→9 context.sql.idiom uses util✕
- Connections
- 1 pair of types, where a type in context.sql.idiom uses a type in util.
- The types involved
zio.quill.context.sql.idiom.SqlIdiom→zio.quill.util.TraceConfig
- Direction
- context.sql.idiom uses util, so a change to util can break context.sql.idiom, while a change to context.sql.idiom can't break util.
- Position
- Below the diagonal: context.sql.idiom uses a module listed above it, which is the healthy direction.
23→11 context.sql.idiom uses context✕
- Connections
- 1 pair of types, where a type in context.sql.idiom uses a type in context.
- The types involved
zio.quill.context.sql.idiom.SqlIdiom→zio.quill.context.ExecutionType
- Direction
- context.sql.idiom uses context, so a change to context can break context.sql.idiom, while a change to context.sql.idiom can't break context.
- Position
- Below the diagonal: context.sql.idiom uses a module listed above it, which is the healthy direction.
23→12 context.sql.idiom uses idiom.StatementInterpolator✕
- Connections
- 2 pairs of types, where a type in context.sql.idiom uses a type in idiom.StatementInterpolator.
- The types involved
zio.quill.context.sql.idiom.OnConflictSupport→zio.quill.idiom.StatementInterpolator.Tokenizerzio.quill.context.sql.idiom.SqlIdiom→zio.quill.idiom.StatementInterpolator.Tokenizer
- Direction
- context.sql.idiom uses idiom.StatementInterpolator, so a change to idiom.StatementInterpolator can break context.sql.idiom, while a change to context.sql.idiom can't break idiom.StatementInterpolator.
- Position
- Below the diagonal: context.sql.idiom uses a module listed above it, which is the healthy direction.
23→13 context.sql.idiom uses norm✕
- Connections
- 3 pairs of types, where a type in context.sql.idiom uses a type in norm.
- The types involved
zio.quill.context.sql.idiom.SqlIdiom→zio.quill.norm.ConcatBehaviorzio.quill.context.sql.idiom.SqlIdiom→zio.quill.norm.EqualityBehaviorzio.quill.context.sql.idiom.SqlIdiom→zio.quill.norm.ProductAggregationToken
- Direction
- context.sql.idiom uses norm, so a change to norm can break context.sql.idiom, while a change to context.sql.idiom can't break norm.
- Position
- Below the diagonal: context.sql.idiom uses a module listed above it, which is the healthy direction.
23→16 context.sql.idiom uses quat✕
- Connections
- 1 pair of types, where a type in context.sql.idiom uses a type in quat.
- The types involved
zio.quill.context.sql.idiom.SqlIdiom→zio.quill.quat.Quat
- Direction
- context.sql.idiom uses quat, so a change to quat can break context.sql.idiom, while a change to context.sql.idiom can't break quat.
- Position
- Below the diagonal: context.sql.idiom uses a module listed above it, which is the healthy direction.
23→17 context.sql.idiom uses ast✕
- Connections
- 24 pairs of types, where a type in context.sql.idiom uses a type in ast.
- The types involved
zio.quill.context.sql.idiom.Error→zio.quill.ast.Astzio.quill.context.sql.idiom.Error→zio.quill.ast.Identzio.quill.context.sql.idiom.OnConflictSupport→zio.quill.ast.Astzio.quill.context.sql.idiom.OnConflictSupport→zio.quill.ast.OnConflictzio.quill.context.sql.idiom.SqlIdiom→zio.quill.ast.Actionzio.quill.context.sql.idiom.SqlIdiom→zio.quill.ast.AggregationOperatorzio.quill.context.sql.idiom.SqlIdiom→zio.quill.ast.Assignmentzio.quill.context.sql.idiom.SqlIdiom→zio.quill.ast.AssignmentDualzio.quill.context.sql.idiom.SqlIdiom→zio.quill.ast.Astzio.quill.context.sql.idiom.SqlIdiom→zio.quill.ast.BinaryOperatorzio.quill.context.sql.idiom.SqlIdiom→zio.quill.ast.Entityzio.quill.context.sql.idiom.SqlIdiom→zio.quill.ast.ExternalIdentzio.quill.context.sql.idiom.SqlIdiom→zio.quill.ast.Identzio.quill.context.sql.idiom.SqlIdiom→zio.quill.ast.Ifzio.quill.context.sql.idiom.SqlIdiom→zio.quill.ast.Infixzio.quill.context.sql.idiom.SqlIdiom→zio.quill.ast.JoinTypezio.quill.context.sql.idiom.SqlIdiom→zio.quill.ast.Operationzio.quill.context.sql.idiom.SqlIdiom→zio.quill.ast.OptionOperationzio.quill.context.sql.idiom.SqlIdiom→zio.quill.ast.Propertyzio.quill.context.sql.idiom.SqlIdiom→zio.quill.ast.Renameablezio.quill.context.sql.idiom.SqlIdiom→zio.quill.ast.ReturningActionzio.quill.context.sql.idiom.SqlIdiom→zio.quill.ast.UnaryOperatorzio.quill.context.sql.idiom.SqlIdiom→zio.quill.ast.Valuezio.quill.context.sql.idiom.VerifySqlQuery→zio.quill.ast.Ast
- Direction
- context.sql.idiom uses ast, so a change to ast can break context.sql.idiom, while a change to context.sql.idiom can't break ast.
- Position
- Below the diagonal: context.sql.idiom uses a module listed above it, which is the healthy direction.
23→19 context.sql.idiom uses context.sql✕
- Connections
- 8 pairs of types, where a type in context.sql.idiom uses a type in context.sql.
- The types involved
zio.quill.context.sql.idiom.SqlIdiom→zio.quill.context.sql.FromContextzio.quill.context.sql.idiom.SqlIdiom→zio.quill.context.sql.OrderByCriteriazio.quill.context.sql.idiom.SqlIdiom→zio.quill.context.sql.SelectValuezio.quill.context.sql.idiom.SqlIdiom→zio.quill.context.sql.SetOperationzio.quill.context.sql.idiom.SqlIdiom→zio.quill.context.sql.SqlQueryzio.quill.context.sql.idiom.VerifySqlQuery→zio.quill.context.sql.FlattenSqlQueryzio.quill.context.sql.idiom.VerifySqlQuery→zio.quill.context.sql.FromContextzio.quill.context.sql.idiom.VerifySqlQuery→zio.quill.context.sql.SqlQuery
- Direction
- context.sql.idiom uses context.sql, so a change to context.sql can break context.sql.idiom, while a change to context.sql.idiom can't break context.sql.
- Position
- Below the diagonal: context.sql.idiom uses a module listed above it, which is the healthy direction.
23→20 context.sql.idiom uses context.sql.idiom.SqlIdiom✕
- Connections
- 1 pair of types, where a type in context.sql.idiom uses a type in context.sql.idiom.SqlIdiom.
- The types involved
zio.quill.context.sql.idiom.SqlIdiom→zio.quill.context.sql.idiom.SqlIdiom.ActionTableAliasBehavior
- Direction
- context.sql.idiom uses context.sql.idiom.SqlIdiom, so a change to context.sql.idiom.SqlIdiom can break context.sql.idiom, while a change to context.sql.idiom can't break context.sql.idiom.SqlIdiom.
- Position
- Below the diagonal: context.sql.idiom uses a module listed above it, which is the healthy direction.
23→26 context.sql.idiom uses zio.quill part of a loop✕
- Connections
- 4 pairs of types, where a type in context.sql.idiom uses a type in zio.quill.
- The types involved
zio.quill.context.sql.idiom.OnConflictSupport→zio.quill.IdiomContextzio.quill.context.sql.idiom.OnConflictSupport→zio.quill.NamingStrategyzio.quill.context.sql.idiom.SqlIdiom→zio.quill.IdiomContextzio.quill.context.sql.idiom.SqlIdiom→zio.quill.NamingStrategy
- Direction
- context.sql.idiom uses zio.quill, so a change to zio.quill can break context.sql.idiom, while a change to context.sql.idiom can't break zio.quill.
- 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.
24→11 context.qzio uses context✕
- Connections
- 13 pairs of types, where a type in context.qzio uses a type in context.
- The types involved
zio.quill.context.qzio.ZioContext→zio.quill.context.Contextzio.quill.context.qzio.ZioContext→zio.quill.context.ContextVerbStreamzio.quill.context.qzio.ZioContext→zio.quill.context.ExecutionInfozio.quill.context.qzio.ZioJdbcContext→zio.quill.context.ContextVerbPreparezio.quill.context.qzio.ZioJdbcContext→zio.quill.context.ContextVerbStreamzio.quill.context.qzio.ZioJdbcContext→zio.quill.context.ExecutionInfozio.quill.context.qzio.ZioJdbcContext→zio.quill.context.ProtoContextzio.quill.context.qzio.ZioJdbcContext→zio.quill.context.TranslateOptionszio.quill.context.qzio.ZioJdbcUnderlyingContext→zio.quill.context.ContextVerbStreamzio.quill.context.qzio.ZioJdbcUnderlyingContext→zio.quill.context.ExecutionInfozio.quill.context.qzio.ZioPrepareContext→zio.quill.context.ContextVerbPreparezio.quill.context.qzio.ZioPrepareContext→zio.quill.context.ExecutionInfozio.quill.context.qzio.ZioTranslateContext→zio.quill.context.ContextTranslateMacro
- Direction
- context.qzio uses context, so a change to context can break context.qzio, while a change to context.qzio can't break context.
- Position
- Below the diagonal: context.qzio uses a module listed above it, which is the healthy direction.
24→17 context.qzio uses ast✕
- Connections
- 1 pair of types, where a type in context.qzio uses a type in ast.
- The types involved
zio.quill.context.qzio.ZioJdbcContext→zio.quill.ast.ScalarLift
- Direction
- context.qzio uses ast, so a change to ast can break context.qzio, while a change to context.qzio can't break ast.
- Position
- Below the diagonal: context.qzio uses a module listed above it, which is the healthy direction.
24→22 context.qzio uses context.jdbc✕
- Connections
- 2 pairs of types, where a type in context.qzio uses a type in context.jdbc.
- The types involved
zio.quill.context.qzio.ZioJdbcContext→zio.quill.context.jdbc.JdbcContextTypeszio.quill.context.qzio.ZioJdbcUnderlyingContext→zio.quill.context.jdbc.JdbcContextVerbExecute
- Direction
- context.qzio uses context.jdbc, so a change to context.jdbc can break context.qzio, while a change to context.qzio can't break context.jdbc.
- Position
- Below the diagonal: context.qzio uses a module listed above it, which is the healthy direction.
24→26 context.qzio uses zio.quill part of a loop✕
- Connections
- 2 pairs of types, where a type in context.qzio uses a type in zio.quill.
- The types involved
zio.quill.context.qzio.ZioJdbcContext→zio.quill.ReturnActionzio.quill.context.qzio.ZioJdbcUnderlyingContext→zio.quill.ReturnAction
- Direction
- context.qzio uses zio.quill, so a change to zio.quill can break context.qzio, while a change to context.qzio can't break zio.quill.
- 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→12 sql.idiom uses idiom.StatementInterpolator✕
- Connections
- 1 pair of types, where a type in sql.idiom uses a type in idiom.StatementInterpolator.
- The types involved
zio.quill.sql.idiom.BooleanLiteralSupport→zio.quill.idiom.StatementInterpolator.Tokenizer
- Direction
- sql.idiom uses idiom.StatementInterpolator, so a change to idiom.StatementInterpolator can break sql.idiom, while a change to sql.idiom can't break idiom.StatementInterpolator.
- Position
- Below the diagonal: sql.idiom uses a module listed above it, which is the healthy direction.
25→13 sql.idiom uses norm✕
- Connections
- 2 pairs of types, where a type in sql.idiom uses a type in norm.
- The types involved
zio.quill.sql.idiom.BooleanLiteralSupport→zio.quill.norm.ConcatBehaviorzio.quill.sql.idiom.BooleanLiteralSupport→zio.quill.norm.EqualityBehavior
- Direction
- sql.idiom uses norm, so a change to norm can break sql.idiom, while a change to sql.idiom can't break norm.
- Position
- Below the diagonal: sql.idiom uses a module listed above it, which is the healthy direction.
25→17 sql.idiom uses ast✕
- Connections
- 2 pairs of types, where a type in sql.idiom uses a type in ast.
- The types involved
zio.quill.sql.idiom.BooleanLiteralSupport→zio.quill.ast.Astzio.quill.sql.idiom.BooleanLiteralSupport→zio.quill.ast.Value
- Direction
- sql.idiom uses ast, so a change to ast can break sql.idiom, while a change to sql.idiom can't break ast.
- Position
- Below the diagonal: sql.idiom uses a module listed above it, which is the healthy direction.
25→23 sql.idiom uses context.sql.idiom✕
- Connections
- 1 pair of types, where a type in sql.idiom uses a type in context.sql.idiom.
- The types involved
zio.quill.sql.idiom.BooleanLiteralSupport→zio.quill.context.sql.idiom.SqlIdiom
- Direction
- sql.idiom uses context.sql.idiom, so a change to context.sql.idiom can break sql.idiom, while a change to sql.idiom can't break context.sql.idiom.
- Position
- Below the diagonal: sql.idiom uses a module listed above it, which is the healthy direction.
25→26 sql.idiom uses zio.quill part of a loop✕
- Connections
- 2 pairs of types, where a type in sql.idiom uses a type in zio.quill.
- The types involved
zio.quill.sql.idiom.BooleanLiteralSupport→zio.quill.IdiomContextzio.quill.sql.idiom.BooleanLiteralSupport→zio.quill.NamingStrategy
- Direction
- sql.idiom uses zio.quill, so a change to zio.quill can break sql.idiom, while a change to sql.idiom can't break zio.quill.
- 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→2 zio.quill uses monad✕
- Connections
- 6 pairs of types, where a type in zio.quill uses a type in monad.
- The types involved
zio.quill.AsyncMirrorContext→zio.quill.monad.ScalaFutureIOMonadzio.quill.CassandraAsyncContext→zio.quill.monad.ScalaFutureIOMonadzio.quill.CassandraPekkoContext→zio.quill.monad.ScalaFutureIOMonadzio.quill.CassandraSyncContext→zio.quill.monad.SyncIOMonadzio.quill.MirrorContext→zio.quill.monad.SyncIOMonadzio.quill.OrientDBSyncContext→zio.quill.monad.SyncIOMonad
- Direction
- zio.quill uses monad, so a change to monad can break zio.quill, while a change to zio.quill can't break monad.
- Position
- Below the diagonal: zio.quill uses a module listed above it, which is the healthy direction.
26→5 zio.quill uses context.json✕
- Connections
- 1 pair of types, where a type in zio.quill uses a type in context.json.
- The types involved
zio.quill.PostgresZioJdbcContext→zio.quill.context.json.PostgresJsonExtensions
- Direction
- zio.quill uses context.json, so a change to context.json can break zio.quill, while a change to zio.quill can't break context.json.
- Position
- Below the diagonal: zio.quill uses a module listed above it, which is the healthy direction.
26→6 zio.quill uses context.mirror✕
- Connections
- 4 pairs of types, where a type in zio.quill uses a type in context.mirror.
- The types involved
zio.quill.AsyncMirrorContext→zio.quill.context.mirror.MirrorDecoderszio.quill.AsyncMirrorContext→zio.quill.context.mirror.MirrorEncoderszio.quill.MirrorContext→zio.quill.context.mirror.MirrorDecoderszio.quill.MirrorContext→zio.quill.context.mirror.MirrorEncoders
- Direction
- zio.quill uses context.mirror, so a change to context.mirror can break zio.quill, while a change to zio.quill can't break context.mirror.
- Position
- Below the diagonal: zio.quill uses a module listed above it, which is the healthy direction.
26→8 zio.quill uses idiom✕
- Connections
- 14 pairs of types, where a type in zio.quill uses a type in idiom.
- The types involved
zio.quill.AsyncMirrorContext→zio.quill.idiom.Idiomzio.quill.MirrorContext→zio.quill.idiom.Idiomzio.quill.MirrorIdiomBase→zio.quill.idiom.Idiomzio.quill.MirrorIdiomBase→zio.quill.idiom.Statementzio.quill.MirrorIdiomBase→zio.quill.idiom.Tokenzio.quill.MySQLDialect→zio.quill.idiom.Statementzio.quill.MySQLDialect→zio.quill.idiom.Tokenzio.quill.OracleDialect→zio.quill.idiom.Statementzio.quill.OracleDialect→zio.quill.idiom.StringTokenzio.quill.OracleDialect→zio.quill.idiom.Tokenzio.quill.SQLServerDialect→zio.quill.idiom.Statementzio.quill.SQLServerDialect→zio.quill.idiom.StringTokenzio.quill.SQLServerDialect→zio.quill.idiom.Tokenzio.quill.SqliteDialect→zio.quill.idiom.Token
- Direction
- zio.quill uses idiom, so a change to idiom can break zio.quill, while a change to zio.quill can't break idiom.
- Position
- Below the diagonal: zio.quill uses a module listed above it, which is the healthy direction.
26→9 zio.quill uses util✕
- Connections
- 1 pair of types, where a type in zio.quill uses a type in util.
- The types involved
zio.quill.SQLServerDialect→zio.quill.util.TraceConfig
- Direction
- zio.quill uses util, so a change to util can break zio.quill, while a change to zio.quill can't break util.
- Position
- Below the diagonal: zio.quill uses a module listed above it, which is the healthy direction.
26→11 zio.quill uses context✕
- Connections
- 48 pairs of types, where a type in zio.quill uses a type in context. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
zio.quill.AsyncMirrorContext→zio.quill.context.Contextzio.quill.AsyncMirrorContext→zio.quill.context.ContextVerbTranslatezio.quill.AsyncMirrorContext→zio.quill.context.ExecutionInfozio.quill.AsyncMirrorContext→zio.quill.context.RowContextzio.quill.BatchActionMirrorGeneric→zio.quill.context.ExecutionInfozio.quill.BatchActionReturningMirrorGeneric→zio.quill.context.ExecutionInfozio.quill.CassandraAsyncContext→zio.quill.context.ExecutionInfozio.quill.CassandraCqlSessionContext→zio.quill.context.AsyncFutureCachezio.quill.CassandraCqlSessionContext→zio.quill.context.CassandraSessionzio.quill.CassandraCqlSessionContext→zio.quill.context.SyncCachezio.quill.CassandraPekkoContext→zio.quill.context.CassandraSessionzio.quill.CassandraPekkoContext→zio.quill.context.ContextVerbStreamzio.quill.CassandraPekkoContext→zio.quill.context.ExecutionInfozio.quill.CassandraSyncContext→zio.quill.context.ExecutionInfozio.quill.CassandraZioSession→zio.quill.context.AsyncFutureCachezio.quill.CassandraZioSession→zio.quill.context.CassandraSessionzio.quill.CassandraZioSession→zio.quill.context.SyncCachezio.quill.H2Dialect→zio.quill.context.CanInsertReturningWithMultiValueszio.quill.H2Dialect→zio.quill.context.CanInsertWithMultiValueszio.quill.H2Dialect→zio.quill.context.CanReturnFieldzio.quill.MirrorContext→zio.quill.context.Contextzio.quill.MirrorContext→zio.quill.context.ContextVerbPrepareLambdazio.quill.MirrorContext→zio.quill.context.ContextVerbTranslatezio.quill.MirrorContext→zio.quill.context.ExecutionInfozio.quill.MirrorContext→zio.quill.context.ProtoContext
- Direction
- zio.quill uses context, so a change to context can break zio.quill, while a change to zio.quill can't break context.
- Position
- Below the diagonal: zio.quill uses a module listed above it, which is the healthy direction.
26→12 zio.quill uses idiom.StatementInterpolator✕
- Connections
- 7 pairs of types, where a type in zio.quill uses a type in idiom.StatementInterpolator.
- The types involved
zio.quill.H2Dialect→zio.quill.idiom.StatementInterpolator.Tokenizerzio.quill.MirrorIdiomBase→zio.quill.idiom.StatementInterpolator.Tokenizerzio.quill.MySQLDialect→zio.quill.idiom.StatementInterpolator.Tokenizerzio.quill.OracleDialect→zio.quill.idiom.StatementInterpolator.Tokenizerzio.quill.PostgresDialect→zio.quill.idiom.StatementInterpolator.Tokenizerzio.quill.SQLServerDialect→zio.quill.idiom.StatementInterpolator.Tokenizerzio.quill.SqliteDialect→zio.quill.idiom.StatementInterpolator.Tokenizer
- Direction
- zio.quill uses idiom.StatementInterpolator, so a change to idiom.StatementInterpolator can break zio.quill, while a change to zio.quill can't break idiom.StatementInterpolator.
- Position
- Below the diagonal: zio.quill uses a module listed above it, which is the healthy direction.
26→13 zio.quill uses norm✕
- Connections
- 10 pairs of types, where a type in zio.quill uses a type in norm.
- The types involved
zio.quill.IdiomContext→zio.quill.norm.TranspileConfigzio.quill.MirrorSqlDialect→zio.quill.norm.ProductAggregationTokenzio.quill.MirrorSqlDialectWithBooleanLiterals→zio.quill.norm.ProductAggregationTokenzio.quill.MirrorSqlDialectWithNoReturn→zio.quill.norm.ProductAggregationTokenzio.quill.MirrorSqlDialectWithOutputClause→zio.quill.norm.ProductAggregationTokenzio.quill.MirrorSqlDialectWithReturnClause→zio.quill.norm.ProductAggregationTokenzio.quill.MirrorSqlDialectWithReturnMulti→zio.quill.norm.ProductAggregationTokenzio.quill.OracleDialect→zio.quill.norm.ConcatBehaviorzio.quill.PostgresDialect→zio.quill.norm.ProductAggregationTokenzio.quill.SQLServerDialect→zio.quill.norm.EqualityBehavior
- Direction
- zio.quill uses norm, so a change to norm can break zio.quill, while a change to zio.quill can't break norm.
- Position
- Below the diagonal: zio.quill uses a module listed above it, which is the healthy direction.
26→14 zio.quill uses context.orientdb✕
- Connections
- 2 pairs of types, where a type in zio.quill uses a type in context.orientdb.
- The types involved
zio.quill.OrientDBMirrorContext→zio.quill.context.orientdb.OrientDBContextzio.quill.OrientDBSyncContext→zio.quill.context.orientdb.OrientDBSessionContext
- Direction
- zio.quill uses context.orientdb, so a change to context.orientdb can break zio.quill, while a change to zio.quill can't break context.orientdb.
- Position
- Below the diagonal: zio.quill uses a module listed above it, which is the healthy direction.
26→16 zio.quill uses quat✕
- Connections
- 1 pair of types, where a type in zio.quill uses a type in quat.
- The types involved
zio.quill.MirrorIdiomBase→zio.quill.quat.Quat
- Direction
- zio.quill uses quat, so a change to quat can break zio.quill, while a change to zio.quill can't break quat.
- Position
- Below the diagonal: zio.quill uses a module listed above it, which is the healthy direction.
26→17 zio.quill uses ast✕
- Connections
- 46 pairs of types, where a type in zio.quill uses a type in ast. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
zio.quill.H2Dialect→zio.quill.ast.Astzio.quill.H2Dialect→zio.quill.ast.OnConflictzio.quill.MirrorIdiomBase→zio.quill.ast.Assignmentzio.quill.MirrorIdiomBase→zio.quill.ast.AssignmentDualzio.quill.MirrorIdiomBase→zio.quill.ast.Astzio.quill.MirrorIdiomBase→zio.quill.ast.Blockzio.quill.MirrorIdiomBase→zio.quill.ast.Dynamiczio.quill.MirrorIdiomBase→zio.quill.ast.Externalzio.quill.MirrorIdiomBase→zio.quill.ast.ExternalIdentzio.quill.MirrorIdiomBase→zio.quill.ast.Functionzio.quill.MirrorIdiomBase→zio.quill.ast.Identzio.quill.MirrorIdiomBase→zio.quill.ast.Ifzio.quill.MirrorIdiomBase→zio.quill.ast.Infixzio.quill.MirrorIdiomBase→zio.quill.ast.IterableOperationzio.quill.MirrorIdiomBase→zio.quill.ast.JoinTypezio.quill.MirrorIdiomBase→zio.quill.ast.OnConflictzio.quill.MirrorIdiomBase→zio.quill.ast.Operationzio.quill.MirrorIdiomBase→zio.quill.ast.OptionOperationzio.quill.MirrorIdiomBase→zio.quill.ast.Orderingzio.quill.MirrorIdiomBase→zio.quill.ast.Propertyzio.quill.MirrorIdiomBase→zio.quill.ast.Renameablezio.quill.MirrorIdiomBase→zio.quill.ast.Valzio.quill.MirrorIdiomBase→zio.quill.ast.Valuezio.quill.MirrorIdiomBase→zio.quill.ast.Visibilityzio.quill.MySQLDialect→zio.quill.ast.Ast
- Direction
- zio.quill uses ast, so a change to ast can break zio.quill, while a change to zio.quill can't break ast.
- Position
- Below the diagonal: zio.quill uses a module listed above it, which is the healthy direction.
26→18 zio.quill uses context.cassandra✕
- Connections
- 3 pairs of types, where a type in zio.quill uses a type in context.cassandra.
- The types involved
zio.quill.CassandraCqlSessionContext→zio.quill.context.cassandra.CassandraSessionContextzio.quill.CassandraMirrorContext→zio.quill.context.cassandra.CassandraContextzio.quill.CassandraPekkoContext→zio.quill.context.cassandra.CassandraSessionContext
- Direction
- zio.quill uses context.cassandra, so a change to context.cassandra can break zio.quill, while a change to zio.quill can't break context.cassandra.
- Position
- Below the diagonal: zio.quill uses a module listed above it, which is the healthy direction.
26→19 zio.quill uses context.sql✕
- Connections
- 5 pairs of types, where a type in zio.quill uses a type in context.sql.
- The types involved
zio.quill.MySQLDialect→zio.quill.context.sql.OrderByCriteriazio.quill.OracleDialect→zio.quill.context.sql.SqlQueryzio.quill.SQLServerDialect→zio.quill.context.sql.SqlQueryzio.quill.SqlMirrorContext→zio.quill.context.sql.SqlContextzio.quill.SqliteDialect→zio.quill.context.sql.OrderByCriteria
- Direction
- zio.quill uses context.sql, so a change to context.sql can break zio.quill, while a change to zio.quill can't break context.sql.
- Position
- Below the diagonal: zio.quill uses a module listed above it, which is the healthy direction.
26→20 zio.quill uses context.sql.idiom.SqlIdiom✕
- Connections
- 4 pairs of types, where a type in zio.quill uses a type in context.sql.idiom.SqlIdiom.
- The types involved
zio.quill.MySQL5Dialect→zio.quill.context.sql.idiom.SqlIdiom.ActionTableAliasBehaviorzio.quill.MySQLDialect→zio.quill.context.sql.idiom.SqlIdiom.ActionTableAliasBehaviorzio.quill.OracleDialect→zio.quill.context.sql.idiom.SqlIdiom.ActionTableAliasBehaviorzio.quill.SQLServerDialect→zio.quill.context.sql.idiom.SqlIdiom.ActionTableAliasBehavior
- Direction
- zio.quill uses context.sql.idiom.SqlIdiom, so a change to context.sql.idiom.SqlIdiom can break zio.quill, while a change to zio.quill can't break context.sql.idiom.SqlIdiom.
- Position
- Below the diagonal: zio.quill uses a module listed above it, which is the healthy direction.
26→22 zio.quill uses context.jdbc✕
- Connections
- 18 pairs of types, where a type in zio.quill uses a type in context.jdbc.
- The types involved
zio.quill.H2JdbcContext→zio.quill.context.jdbc.H2JdbcContextBasezio.quill.H2JdbcContext→zio.quill.context.jdbc.JdbcContextzio.quill.H2ZioJdbcContext→zio.quill.context.jdbc.H2JdbcTypeszio.quill.MysqlJdbcContext→zio.quill.context.jdbc.JdbcContextzio.quill.MysqlJdbcContext→zio.quill.context.jdbc.MysqlJdbcContextBasezio.quill.MysqlZioJdbcContext→zio.quill.context.jdbc.MysqlJdbcTypeszio.quill.OracleJdbcContext→zio.quill.context.jdbc.JdbcContextzio.quill.OracleJdbcContext→zio.quill.context.jdbc.OracleJdbcContextBasezio.quill.OracleZioJdbcContext→zio.quill.context.jdbc.OracleJdbcTypeszio.quill.PostgresJdbcContext→zio.quill.context.jdbc.JdbcContextzio.quill.PostgresJdbcContext→zio.quill.context.jdbc.PostgresJdbcContextBasezio.quill.PostgresZioJdbcContext→zio.quill.context.jdbc.PostgresJdbcTypeszio.quill.SqlServerJdbcContext→zio.quill.context.jdbc.JdbcContextzio.quill.SqlServerJdbcContext→zio.quill.context.jdbc.SqlServerJdbcContextBasezio.quill.SqlServerZioJdbcContext→zio.quill.context.jdbc.SqlServerJdbcTypeszio.quill.SqliteJdbcContext→zio.quill.context.jdbc.JdbcContextzio.quill.SqliteJdbcContext→zio.quill.context.jdbc.SqliteJdbcContextBasezio.quill.SqliteZioJdbcContext→zio.quill.context.jdbc.SqliteJdbcTypes
- Direction
- zio.quill uses context.jdbc, so a change to context.jdbc can break zio.quill, while a change to zio.quill can't break context.jdbc.
- Position
- Below the diagonal: zio.quill uses a module listed above it, which is the healthy direction.
26→23 zio.quill uses context.sql.idiom✕
- Connections
- 38 pairs of types, where a type in zio.quill uses a type in context.sql.idiom. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
zio.quill.H2Dialect→zio.quill.context.sql.idiom.ConcatSupportzio.quill.H2Dialect→zio.quill.context.sql.idiom.PositionalBindVariableszio.quill.H2Dialect→zio.quill.context.sql.idiom.SqlIdiomzio.quill.MirrorSqlDialect→zio.quill.context.sql.idiom.ConcatSupportzio.quill.MirrorSqlDialect→zio.quill.context.sql.idiom.QuestionMarkBindVariableszio.quill.MirrorSqlDialect→zio.quill.context.sql.idiom.SqlIdiomzio.quill.MirrorSqlDialectWithBooleanLiterals→zio.quill.context.sql.idiom.ConcatSupportzio.quill.MirrorSqlDialectWithBooleanLiterals→zio.quill.context.sql.idiom.QuestionMarkBindVariableszio.quill.MirrorSqlDialectWithBooleanLiterals→zio.quill.context.sql.idiom.SqlIdiomzio.quill.MirrorSqlDialectWithNoReturn→zio.quill.context.sql.idiom.ConcatSupportzio.quill.MirrorSqlDialectWithNoReturn→zio.quill.context.sql.idiom.QuestionMarkBindVariableszio.quill.MirrorSqlDialectWithNoReturn→zio.quill.context.sql.idiom.SqlIdiomzio.quill.MirrorSqlDialectWithOutputClause→zio.quill.context.sql.idiom.ConcatSupportzio.quill.MirrorSqlDialectWithOutputClause→zio.quill.context.sql.idiom.QuestionMarkBindVariableszio.quill.MirrorSqlDialectWithOutputClause→zio.quill.context.sql.idiom.SqlIdiomzio.quill.MirrorSqlDialectWithReturnClause→zio.quill.context.sql.idiom.ConcatSupportzio.quill.MirrorSqlDialectWithReturnClause→zio.quill.context.sql.idiom.QuestionMarkBindVariableszio.quill.MirrorSqlDialectWithReturnClause→zio.quill.context.sql.idiom.SqlIdiomzio.quill.MirrorSqlDialectWithReturnMulti→zio.quill.context.sql.idiom.ConcatSupportzio.quill.MirrorSqlDialectWithReturnMulti→zio.quill.context.sql.idiom.QuestionMarkBindVariableszio.quill.MirrorSqlDialectWithReturnMulti→zio.quill.context.sql.idiom.SqlIdiomzio.quill.MySQLDialect→zio.quill.context.sql.idiom.NoConcatSupportzio.quill.MySQLDialect→zio.quill.context.sql.idiom.QuestionMarkBindVariableszio.quill.MySQLDialect→zio.quill.context.sql.idiom.SqlIdiomzio.quill.OracleDialect→zio.quill.context.sql.idiom.ConcatSupport
- Direction
- zio.quill uses context.sql.idiom, so a change to context.sql.idiom can break zio.quill, while a change to zio.quill can't break context.sql.idiom.
- Position
- Below the diagonal: zio.quill uses a module listed above it, which is the healthy direction.
26→24 zio.quill uses context.qzio✕
- Connections
- 13 pairs of types, where a type in zio.quill uses a type in context.qzio.
- The types involved
zio.quill.H2ZioJdbcContext→zio.quill.context.qzio.ZioJdbcContextzio.quill.H2ZioJdbcContext→zio.quill.context.qzio.ZioJdbcUnderlyingContextzio.quill.MysqlZioJdbcContext→zio.quill.context.qzio.ZioJdbcContextzio.quill.MysqlZioJdbcContext→zio.quill.context.qzio.ZioJdbcUnderlyingContextzio.quill.OracleZioJdbcContext→zio.quill.context.qzio.ZioJdbcContextzio.quill.OracleZioJdbcContext→zio.quill.context.qzio.ZioJdbcUnderlyingContextzio.quill.PostgresZioJdbcContext→zio.quill.context.qzio.ZioJdbcContextzio.quill.PostgresZioJdbcContext→zio.quill.context.qzio.ZioJdbcUnderlyingContextzio.quill.SqlServerZioJdbcContext→zio.quill.context.qzio.ZioJdbcContextzio.quill.SqlServerZioJdbcContext→zio.quill.context.qzio.ZioJdbcUnderlyingContextzio.quill.SqliteZioJdbcContext→zio.quill.context.qzio.ZioJdbcContextzio.quill.SqliteZioJdbcContext→zio.quill.context.qzio.ZioJdbcUnderlyingContextzio.quill.WithProbing→zio.quill.context.qzio.ZioJdbcUnderlyingContext
- Direction
- zio.quill uses context.qzio, so a change to context.qzio can break zio.quill, while a change to zio.quill can't break context.qzio.
- Position
- Below the diagonal: zio.quill uses a module listed above it, which is the healthy direction.
26→25 zio.quill uses sql.idiom✕
- Connections
- 3 pairs of types, where a type in zio.quill uses a type in sql.idiom.
- The types involved
zio.quill.MirrorSqlDialectWithBooleanLiterals→zio.quill.sql.idiom.BooleanLiteralSupportzio.quill.OracleDialect→zio.quill.sql.idiom.BooleanLiteralSupportzio.quill.SQLServerDialect→zio.quill.sql.idiom.BooleanLiteralSupport
- Direction
- zio.quill uses sql.idiom, so a change to sql.idiom can break zio.quill, while a change to zio.quill can't break sql.idiom.
- Position
- Below the diagonal: zio.quill uses a module listed above it, which is the healthy direction.
27→6 AsyncMirrorContext uses context.mirror✕
- Connections
- 1 pair of types, where a type in AsyncMirrorContext uses a type in context.mirror.
- The types involved
zio.quill.AsyncMirrorContext.MirrorNullChecker→zio.quill.context.mirror.Row
- Direction
- AsyncMirrorContext uses context.mirror, so a change to context.mirror can break AsyncMirrorContext, while a change to AsyncMirrorContext can't break context.mirror.
- Position
- Below the diagonal: AsyncMirrorContext uses a module listed above it, which is the healthy direction.
27→11 AsyncMirrorContext uses context✕
- Connections
- 5 pairs of types, where a type in AsyncMirrorContext uses a type in context.
- The types involved
zio.quill.AsyncMirrorContext.ActionMirror→zio.quill.context.ExecutionInfozio.quill.AsyncMirrorContext.ActionReturningMirror→zio.quill.context.ExecutionInfozio.quill.AsyncMirrorContext.BatchActionMirror→zio.quill.context.ExecutionInfozio.quill.AsyncMirrorContext.BatchActionReturningMirror→zio.quill.context.ExecutionInfozio.quill.AsyncMirrorContext.QueryMirror→zio.quill.context.ExecutionInfo
- Direction
- AsyncMirrorContext uses context, so a change to context can break AsyncMirrorContext, while a change to AsyncMirrorContext can't break context.
- Position
- Below the diagonal: AsyncMirrorContext uses a module listed above it, which is the healthy direction.
27→26 AsyncMirrorContext uses zio.quill✕
- Connections
- 1 pair of types, where a type in AsyncMirrorContext uses a type in zio.quill.
- The types involved
zio.quill.AsyncMirrorContext.ActionReturningMirror→zio.quill.ReturnAction
- Direction
- AsyncMirrorContext uses zio.quill, so a change to zio.quill can break AsyncMirrorContext, while a change to AsyncMirrorContext can't break zio.quill.
- Position
- Below the diagonal: AsyncMirrorContext uses a module listed above it, which is the healthy direction.
28→22 H2ZioJdbcContext uses context.jdbc✕
- Connections
- 1 pair of types, where a type in H2ZioJdbcContext uses a type in context.jdbc.
- The types involved
zio.quill.H2ZioJdbcContext.Underlying→zio.quill.context.jdbc.H2JdbcTypes
- Direction
- H2ZioJdbcContext uses context.jdbc, so a change to context.jdbc can break H2ZioJdbcContext, while a change to H2ZioJdbcContext can't break context.jdbc.
- Position
- Below the diagonal: H2ZioJdbcContext uses a module listed above it, which is the healthy direction.
28→24 H2ZioJdbcContext uses context.qzio✕
- Connections
- 1 pair of types, where a type in H2ZioJdbcContext uses a type in context.qzio.
- The types involved
zio.quill.H2ZioJdbcContext.Underlying→zio.quill.context.qzio.ZioJdbcUnderlyingContext
- Direction
- H2ZioJdbcContext uses context.qzio, so a change to context.qzio can break H2ZioJdbcContext, while a change to H2ZioJdbcContext can't break context.qzio.
- Position
- Below the diagonal: H2ZioJdbcContext uses a module listed above it, which is the healthy direction.
28→26 H2ZioJdbcContext uses zio.quill✕
- Connections
- 1 pair of types, where a type in H2ZioJdbcContext uses a type in zio.quill.
- The types involved
zio.quill.H2ZioJdbcContext.Underlying→zio.quill.H2Dialect
- Direction
- H2ZioJdbcContext uses zio.quill, so a change to zio.quill can break H2ZioJdbcContext, while a change to H2ZioJdbcContext can't break zio.quill.
- Position
- Below the diagonal: H2ZioJdbcContext uses a module listed above it, which is the healthy direction.
29→6 MirrorContext uses context.mirror✕
- Connections
- 1 pair of types, where a type in MirrorContext uses a type in context.mirror.
- The types involved
zio.quill.MirrorContext.MirrorNullChecker→zio.quill.context.mirror.Row
- Direction
- MirrorContext uses context.mirror, so a change to context.mirror can break MirrorContext, while a change to MirrorContext can't break context.mirror.
- Position
- Below the diagonal: MirrorContext uses a module listed above it, which is the healthy direction.
29→11 MirrorContext uses context✕
- Connections
- 3 pairs of types, where a type in MirrorContext uses a type in context.
- The types involved
zio.quill.MirrorContext.ActionMirror→zio.quill.context.ExecutionInfozio.quill.MirrorContext.ActionReturningMirror→zio.quill.context.ExecutionInfozio.quill.MirrorContext.QueryMirror→zio.quill.context.ExecutionInfo
- Direction
- MirrorContext uses context, so a change to context can break MirrorContext, while a change to MirrorContext can't break context.
- Position
- Below the diagonal: MirrorContext uses a module listed above it, which is the healthy direction.
29→26 MirrorContext uses zio.quill✕
- Connections
- 1 pair of types, where a type in MirrorContext uses a type in zio.quill.
- The types involved
zio.quill.MirrorContext.ActionReturningMirror→zio.quill.ReturnAction
- Direction
- MirrorContext uses zio.quill, so a change to zio.quill can break MirrorContext, while a change to MirrorContext can't break zio.quill.
- Position
- Below the diagonal: MirrorContext uses a module listed above it, which is the healthy direction.
30→11 MirrorSqlDialect uses context✕
- Connections
- 1 pair of types, where a type in MirrorSqlDialect uses a type in context.
- The types involved
zio.quill.MirrorSqlDialect.StrategizeElements→zio.quill.context.CanReturnField
- Direction
- MirrorSqlDialect uses context, so a change to context can break MirrorSqlDialect, while a change to MirrorSqlDialect can't break context.
- Position
- Below the diagonal: MirrorSqlDialect uses a module listed above it, which is the healthy direction.
30→23 MirrorSqlDialect uses context.sql.idiom✕
- Connections
- 3 pairs of types, where a type in MirrorSqlDialect uses a type in context.sql.idiom.
- The types involved
zio.quill.MirrorSqlDialect.StrategizeElements→zio.quill.context.sql.idiom.ConcatSupportzio.quill.MirrorSqlDialect.StrategizeElements→zio.quill.context.sql.idiom.QuestionMarkBindVariableszio.quill.MirrorSqlDialect.StrategizeElements→zio.quill.context.sql.idiom.SqlIdiom
- Direction
- MirrorSqlDialect uses context.sql.idiom, so a change to context.sql.idiom can break MirrorSqlDialect, while a change to MirrorSqlDialect can't break context.sql.idiom.
- Position
- Below the diagonal: MirrorSqlDialect uses a module listed above it, which is the healthy direction.
30→26 MirrorSqlDialect uses zio.quill✕
- Connections
- 1 pair of types, where a type in MirrorSqlDialect uses a type in zio.quill.
- The types involved
zio.quill.MirrorSqlDialect.StrategizeElements→zio.quill.NamingStrategy
- Direction
- MirrorSqlDialect uses zio.quill, so a change to zio.quill can break MirrorSqlDialect, while a change to MirrorSqlDialect can't break zio.quill.
- Position
- Below the diagonal: MirrorSqlDialect uses a module listed above it, which is the healthy direction.
31→22 MysqlZioJdbcContext uses context.jdbc✕
- Connections
- 1 pair of types, where a type in MysqlZioJdbcContext uses a type in context.jdbc.
- The types involved
zio.quill.MysqlZioJdbcContext.Underlying→zio.quill.context.jdbc.MysqlJdbcTypes
- Direction
- MysqlZioJdbcContext uses context.jdbc, so a change to context.jdbc can break MysqlZioJdbcContext, while a change to MysqlZioJdbcContext can't break context.jdbc.
- Position
- Below the diagonal: MysqlZioJdbcContext uses a module listed above it, which is the healthy direction.
31→24 MysqlZioJdbcContext uses context.qzio✕
- Connections
- 1 pair of types, where a type in MysqlZioJdbcContext uses a type in context.qzio.
- The types involved
zio.quill.MysqlZioJdbcContext.Underlying→zio.quill.context.qzio.ZioJdbcUnderlyingContext
- Direction
- MysqlZioJdbcContext uses context.qzio, so a change to context.qzio can break MysqlZioJdbcContext, while a change to MysqlZioJdbcContext can't break context.qzio.
- Position
- Below the diagonal: MysqlZioJdbcContext uses a module listed above it, which is the healthy direction.
31→26 MysqlZioJdbcContext uses zio.quill✕
- Connections
- 1 pair of types, where a type in MysqlZioJdbcContext uses a type in zio.quill.
- The types involved
zio.quill.MysqlZioJdbcContext.Underlying→zio.quill.MySQLDialect
- Direction
- MysqlZioJdbcContext uses zio.quill, so a change to zio.quill can break MysqlZioJdbcContext, while a change to MysqlZioJdbcContext can't break zio.quill.
- Position
- Below the diagonal: MysqlZioJdbcContext uses a module listed above it, which is the healthy direction.
32→8 PostgresDialect uses idiom✕
- Connections
- 1 pair of types, where a type in PostgresDialect uses a type in idiom.
- The types involved
zio.quill.PostgresDialect.ConcatableBatchUpdate→zio.quill.idiom.Statement
- Direction
- PostgresDialect uses idiom, so a change to idiom can break PostgresDialect, while a change to PostgresDialect can't break idiom.
- Position
- Below the diagonal: PostgresDialect uses a module listed above it, which is the healthy direction.
32→12 PostgresDialect uses idiom.StatementInterpolator✕
- Connections
- 1 pair of types, where a type in PostgresDialect uses a type in idiom.StatementInterpolator.
- The types involved
zio.quill.PostgresDialect.ConcatableBatchUpdate→zio.quill.idiom.StatementInterpolator.Tokenizer
- Direction
- PostgresDialect uses idiom.StatementInterpolator, so a change to idiom.StatementInterpolator can break PostgresDialect, while a change to PostgresDialect can't break idiom.StatementInterpolator.
- Position
- Below the diagonal: PostgresDialect uses a module listed above it, which is the healthy direction.
32→17 PostgresDialect uses ast✕
- Connections
- 3 pairs of types, where a type in PostgresDialect uses a type in ast.
- The types involved
zio.quill.PostgresDialect.ConcatableBatchUpdate→zio.quill.ast.Assignmentzio.quill.PostgresDialect.ConcatableBatchUpdate→zio.quill.ast.Astzio.quill.PostgresDialect.ConcatableBatchUpdate→zio.quill.ast.Update
- Direction
- PostgresDialect uses ast, so a change to ast can break PostgresDialect, while a change to PostgresDialect can't break ast.
- Position
- Below the diagonal: PostgresDialect uses a module listed above it, which is the healthy direction.
32→26 PostgresDialect uses zio.quill✕
- Connections
- 2 pairs of types, where a type in PostgresDialect uses a type in zio.quill.
- The types involved
zio.quill.PostgresDialect.ConcatableBatchUpdate→zio.quill.IdiomContextzio.quill.PostgresDialect.ConcatableBatchUpdate→zio.quill.NamingStrategy
- Direction
- PostgresDialect uses zio.quill, so a change to zio.quill can break PostgresDialect, while a change to PostgresDialect can't break zio.quill.
- Position
- Below the diagonal: PostgresDialect uses a module listed above it, which is the healthy direction.
33→5 PostgresZioJdbcContext uses context.json✕
- Connections
- 1 pair of types, where a type in PostgresZioJdbcContext uses a type in context.json.
- The types involved
zio.quill.PostgresZioJdbcContext.Underlying→zio.quill.context.json.PostgresJsonExtensions
- Direction
- PostgresZioJdbcContext uses context.json, so a change to context.json can break PostgresZioJdbcContext, while a change to PostgresZioJdbcContext can't break context.json.
- Position
- Below the diagonal: PostgresZioJdbcContext uses a module listed above it, which is the healthy direction.
33→22 PostgresZioJdbcContext uses context.jdbc✕
- Connections
- 1 pair of types, where a type in PostgresZioJdbcContext uses a type in context.jdbc.
- The types involved
zio.quill.PostgresZioJdbcContext.Underlying→zio.quill.context.jdbc.PostgresJdbcTypes
- Direction
- PostgresZioJdbcContext uses context.jdbc, so a change to context.jdbc can break PostgresZioJdbcContext, while a change to PostgresZioJdbcContext can't break context.jdbc.
- Position
- Below the diagonal: PostgresZioJdbcContext uses a module listed above it, which is the healthy direction.
33→24 PostgresZioJdbcContext uses context.qzio✕
- Connections
- 1 pair of types, where a type in PostgresZioJdbcContext uses a type in context.qzio.
- The types involved
zio.quill.PostgresZioJdbcContext.Underlying→zio.quill.context.qzio.ZioJdbcUnderlyingContext
- Direction
- PostgresZioJdbcContext uses context.qzio, so a change to context.qzio can break PostgresZioJdbcContext, while a change to PostgresZioJdbcContext can't break context.qzio.
- Position
- Below the diagonal: PostgresZioJdbcContext uses a module listed above it, which is the healthy direction.
33→26 PostgresZioJdbcContext uses zio.quill✕
- Connections
- 1 pair of types, where a type in PostgresZioJdbcContext uses a type in zio.quill.
- The types involved
zio.quill.PostgresZioJdbcContext.Underlying→zio.quill.PostgresDialect
- Direction
- PostgresZioJdbcContext uses zio.quill, so a change to zio.quill can break PostgresZioJdbcContext, while a change to PostgresZioJdbcContext can't break zio.quill.
- Position
- Below the diagonal: PostgresZioJdbcContext uses a module listed above it, which is the healthy direction.
34→9 doobie uses util✕
- Connections
- 1 pair of types, where a type in doobie uses a type in util.
- The types involved
zio.quill.doobie.DoobieContextBase→zio.quill.util.ContextLogger
- Direction
- doobie uses util, so a change to util can break doobie, while a change to doobie can't break util.
- Position
- Below the diagonal: doobie uses a module listed above it, which is the healthy direction.
34→11 doobie uses context✕
- Connections
- 2 pairs of types, where a type in doobie uses a type in context.
- The types involved
zio.quill.doobie.DoobieContextBase→zio.quill.context.ContextVerbStreamzio.quill.doobie.DoobieContextBase→zio.quill.context.ExecutionInfo
- Direction
- doobie uses context, so a change to context can break doobie, while a change to doobie can't break context.
- Position
- Below the diagonal: doobie uses a module listed above it, which is the healthy direction.
34→22 doobie uses context.jdbc✕
- Connections
- 1 pair of types, where a type in doobie uses a type in context.jdbc.
- The types involved
zio.quill.doobie.DoobieContextBase→zio.quill.context.jdbc.JdbcContextBase
- Direction
- doobie uses context.jdbc, so a change to context.jdbc can break doobie, while a change to doobie can't break context.jdbc.
- Position
- Below the diagonal: doobie uses a module listed above it, which is the healthy direction.
34→26 doobie uses zio.quill✕
- Connections
- 1 pair of types, where a type in doobie uses a type in zio.quill.
- The types involved
zio.quill.doobie.DoobieContextBase→zio.quill.ReturnAction
- Direction
- doobie uses zio.quill, so a change to zio.quill can break doobie, while a change to doobie can't break zio.quill.
- Position
- Below the diagonal: doobie uses a module listed above it, which is the healthy direction.
35→11 jdbczio uses context✕
- Connections
- 4 pairs of types, where a type in jdbczio uses a type in context.
- The types involved
zio.quill.jdbczio.QuillBaseContext→zio.quill.context.ContextVerbStreamzio.quill.jdbczio.QuillBaseContext→zio.quill.context.ExecutionInfozio.quill.jdbczio.QuillBaseContext→zio.quill.context.ProtoContextzio.quill.jdbczio.QuillBaseContext→zio.quill.context.TranslateOptions
- Direction
- jdbczio uses context, so a change to context can break jdbczio, while a change to jdbczio can't break context.
- Position
- Below the diagonal: jdbczio uses a module listed above it, which is the healthy direction.
35→17 jdbczio uses ast✕
- Connections
- 1 pair of types, where a type in jdbczio uses a type in ast.
- The types involved
zio.quill.jdbczio.QuillBaseContext→zio.quill.ast.ScalarLift
- Direction
- jdbczio uses ast, so a change to ast can break jdbczio, while a change to jdbczio can't break ast.
- Position
- Below the diagonal: jdbczio uses a module listed above it, which is the healthy direction.
35→22 jdbczio uses context.jdbc✕
- Connections
- 1 pair of types, where a type in jdbczio uses a type in context.jdbc.
- The types involved
zio.quill.jdbczio.QuillBaseContext→zio.quill.context.jdbc.JdbcContextTypes
- Direction
- jdbczio uses context.jdbc, so a change to context.jdbc can break jdbczio, while a change to jdbczio can't break context.jdbc.
- Position
- Below the diagonal: jdbczio uses a module listed above it, which is the healthy direction.
35→24 jdbczio uses context.qzio✕
- Connections
- 3 pairs of types, where a type in jdbczio uses a type in context.qzio.
- The types involved
zio.quill.jdbczio.QuillBaseContext→zio.quill.context.qzio.ZioContextzio.quill.jdbczio.QuillBaseContext→zio.quill.context.qzio.ZioJdbcContextzio.quill.jdbczio.QuillBaseContext→zio.quill.context.qzio.ZioTranslateContext
- Direction
- jdbczio uses context.qzio, so a change to context.qzio can break jdbczio, while a change to jdbczio can't break context.qzio.
- Position
- Below the diagonal: jdbczio uses a module listed above it, which is the healthy direction.
35→26 jdbczio uses zio.quill✕
- Connections
- 1 pair of types, where a type in jdbczio uses a type in zio.quill.
- The types involved
zio.quill.jdbczio.QuillBaseContext→zio.quill.ReturnAction
- Direction
- jdbczio uses zio.quill, so a change to zio.quill can break jdbczio, while a change to jdbczio can't break zio.quill.
- Position
- Below the diagonal: jdbczio uses a module listed above it, which is the healthy direction.
36→3 quotation.TranspileConfigSummoning uses util.Messages✕
- Connections
- 1 pair of types, where a type in quotation.TranspileConfigSummoning uses a type in util.Messages.
- The types involved
zio.quill.quotation.TranspileConfigSummoning.ConfigLiftables→zio.quill.util.Messages.TraceType
- Direction
- quotation.TranspileConfigSummoning uses util.Messages, so a change to util.Messages can break quotation.TranspileConfigSummoning, while a change to quotation.TranspileConfigSummoning can't break util.Messages.
- Position
- Below the diagonal: quotation.TranspileConfigSummoning uses a module listed above it, which is the healthy direction.
36→9 quotation.TranspileConfigSummoning uses util✕
- Connections
- 1 pair of types, where a type in quotation.TranspileConfigSummoning uses a type in util.
- The types involved
zio.quill.quotation.TranspileConfigSummoning.ConfigLiftables→zio.quill.util.TraceConfig
- Direction
- quotation.TranspileConfigSummoning uses util, so a change to util can break quotation.TranspileConfigSummoning, while a change to quotation.TranspileConfigSummoning can't break util.
- Position
- Below the diagonal: quotation.TranspileConfigSummoning uses a module listed above it, which is the healthy direction.
36→11 quotation.TranspileConfigSummoning uses context✕
- Connections
- 1 pair of types, where a type in quotation.TranspileConfigSummoning uses a type in context.
- The types involved
zio.quill.quotation.TranspileConfigSummoning.ConfigLiftables→zio.quill.context.ExecutionType
- Direction
- quotation.TranspileConfigSummoning uses context, so a change to context can break quotation.TranspileConfigSummoning, while a change to quotation.TranspileConfigSummoning can't break context.
- Position
- Below the diagonal: quotation.TranspileConfigSummoning uses a module listed above it, which is the healthy direction.
36→13 quotation.TranspileConfigSummoning uses norm✕
- Connections
- 2 pairs of types, where a type in quotation.TranspileConfigSummoning uses a type in norm.
- The types involved
zio.quill.quotation.TranspileConfigSummoning.ConfigLiftables→zio.quill.norm.OptionalPhasezio.quill.quotation.TranspileConfigSummoning.ConfigLiftables→zio.quill.norm.TranspileConfig
- Direction
- quotation.TranspileConfigSummoning uses norm, so a change to norm can break quotation.TranspileConfigSummoning, while a change to quotation.TranspileConfigSummoning can't break norm.
- Position
- Below the diagonal: quotation.TranspileConfigSummoning uses a module listed above it, which is the healthy direction.
36→26 quotation.TranspileConfigSummoning uses zio.quill✕
- Connections
- 1 pair of types, where a type in quotation.TranspileConfigSummoning uses a type in zio.quill.
- The types involved
zio.quill.quotation.TranspileConfigSummoning.ConfigLiftables→zio.quill.IdiomContext
- Direction
- quotation.TranspileConfigSummoning uses zio.quill, so a change to zio.quill can break quotation.TranspileConfigSummoning, while a change to quotation.TranspileConfigSummoning can't break zio.quill.
- Position
- Below the diagonal: quotation.TranspileConfigSummoning uses a module listed above it, which is the healthy direction.
37→16 sql.norm uses quat✕
- Connections
- 2 pairs of types, where a type in sql.norm uses a type in quat.
- The types involved
zio.quill.sql.norm.SelectPropertyProtractor→zio.quill.quat.Quatzio.quill.sql.norm.StatelessQueryTransformer→zio.quill.quat.Quat
- Direction
- sql.norm uses quat, so a change to quat can break sql.norm, while a change to sql.norm can't break quat.
- Position
- Below the diagonal: sql.norm uses a module listed above it, which is the healthy direction.
37→17 sql.norm uses ast✕
- Connections
- 21 pairs of types, where a type in sql.norm uses a type in ast.
- The types involved
zio.quill.sql.norm.HideInnerProperties→zio.quill.ast.Astzio.quill.sql.norm.HideInnerProperties→zio.quill.ast.Propertyzio.quill.sql.norm.HideInnerProperties→zio.quill.ast.StatelessTransformerzio.quill.sql.norm.HideTopLevelFilterAlias→zio.quill.ast.Actionzio.quill.sql.norm.HideTopLevelFilterAlias→zio.quill.ast.Assignmentzio.quill.sql.norm.HideTopLevelFilterAlias→zio.quill.ast.Astzio.quill.sql.norm.HideTopLevelFilterAlias→zio.quill.ast.Identzio.quill.sql.norm.HideTopLevelFilterAlias→zio.quill.ast.StatelessTransformerzio.quill.sql.norm.InContext→zio.quill.ast.Astzio.quill.sql.norm.ProtractQuat→zio.quill.ast.Astzio.quill.sql.norm.References→zio.quill.ast.Astzio.quill.sql.norm.References→zio.quill.ast.StatefulTransformerzio.quill.sql.norm.RemoveExtraAlias→zio.quill.ast.Propertyzio.quill.sql.norm.RemoveUnusedSelects→zio.quill.ast.Astzio.quill.sql.norm.RemoveUnusedSelects→zio.quill.ast.Propertyzio.quill.sql.norm.SelectPropertyProtractor→zio.quill.ast.Astzio.quill.sql.norm.State→zio.quill.ast.Identzio.quill.sql.norm.State→zio.quill.ast.Propertyzio.quill.sql.norm.VendorizeBooleans→zio.quill.ast.Astzio.quill.sql.norm.VendorizeBooleans→zio.quill.ast.Operationzio.quill.sql.norm.VendorizeBooleans→zio.quill.ast.StatelessTransformer
- Direction
- sql.norm uses ast, so a change to ast can break sql.norm, while a change to sql.norm can't break ast.
- Position
- Below the diagonal: sql.norm uses a module listed above it, which is the healthy direction.
37→19 sql.norm uses context.sql✕
- Connections
- 11 pairs of types, where a type in sql.norm uses a type in context.sql.
- The types involved
zio.quill.sql.norm.InContext→zio.quill.context.sql.FromContextzio.quill.sql.norm.RemoveExtraAlias→zio.quill.context.sql.FlattenSqlQueryzio.quill.sql.norm.RemoveExtraAlias→zio.quill.context.sql.SelectValuezio.quill.sql.norm.RemoveUnusedSelects→zio.quill.context.sql.FlattenSqlQueryzio.quill.sql.norm.RemoveUnusedSelects→zio.quill.context.sql.FromContextzio.quill.sql.norm.RemoveUnusedSelects→zio.quill.context.sql.SelectValuezio.quill.sql.norm.RemoveUnusedSelects→zio.quill.context.sql.SqlQueryzio.quill.sql.norm.SelectPropertyProtractor→zio.quill.context.sql.FromContextzio.quill.sql.norm.StatelessQueryTransformer→zio.quill.context.sql.FlattenSqlQueryzio.quill.sql.norm.StatelessQueryTransformer→zio.quill.context.sql.FromContextzio.quill.sql.norm.StatelessQueryTransformer→zio.quill.context.sql.SqlQuery
- Direction
- sql.norm uses context.sql, so a change to context.sql can break sql.norm, while a change to sql.norm can't break context.sql.
- Position
- Below the diagonal: sql.norm uses a module listed above it, which is the healthy direction.
37→26 sql.norm uses zio.quill✕
- Connections
- 1 pair of types, where a type in sql.norm uses a type in zio.quill.
- The types involved
zio.quill.sql.norm.RemoveExtraAlias→zio.quill.NamingStrategy
- Direction
- sql.norm uses zio.quill, so a change to zio.quill can break sql.norm, while a change to sql.norm can't break zio.quill.
- Position
- Below the diagonal: sql.norm uses a module listed above it, which is the healthy direction.
38→8 context.spark uses idiom✕
- Connections
- 1 pair of types, where a type in context.spark uses a type in idiom.
- The types involved
zio.quill.context.spark.SparkIdiom→zio.quill.idiom.Token
- Direction
- context.spark uses idiom, so a change to idiom can break context.spark, while a change to context.spark can't break idiom.
- Position
- Below the diagonal: context.spark uses a module listed above it, which is the healthy direction.
38→11 context.spark uses context✕
- Connections
- 2 pairs of types, where a type in context.spark uses a type in context.
- The types involved
zio.quill.context.spark.SparkIdiom→zio.quill.context.CannotReturnzio.quill.context.spark.SparkIdiom→zio.quill.context.ExecutionType
- Direction
- context.spark uses context, so a change to context can break context.spark, while a change to context.spark can't break context.
- Position
- Below the diagonal: context.spark uses a module listed above it, which is the healthy direction.
38→12 context.spark uses idiom.StatementInterpolator✕
- Connections
- 1 pair of types, where a type in context.spark uses a type in idiom.StatementInterpolator.
- The types involved
zio.quill.context.spark.SparkIdiom→zio.quill.idiom.StatementInterpolator.Tokenizer
- Direction
- context.spark uses idiom.StatementInterpolator, so a change to idiom.StatementInterpolator can break context.spark, while a change to context.spark can't break idiom.StatementInterpolator.
- Position
- Below the diagonal: context.spark uses a module listed above it, which is the healthy direction.
38→16 context.spark uses quat✕
- Connections
- 1 pair of types, where a type in context.spark uses a type in quat.
- The types involved
zio.quill.context.spark.SparkIdiom→zio.quill.quat.Quat
- Direction
- context.spark uses quat, so a change to quat can break context.spark, while a change to context.spark can't break quat.
- Position
- Below the diagonal: context.spark uses a module listed above it, which is the healthy direction.
38→17 context.spark uses ast✕
- Connections
- 7 pairs of types, where a type in context.spark uses a type in ast.
- The types involved
zio.quill.context.spark.SingleValuePrimitive→zio.quill.ast.Astzio.quill.context.spark.SparkIdiom→zio.quill.ast.Astzio.quill.context.spark.SparkIdiom→zio.quill.ast.ExternalIdentzio.quill.context.spark.SparkIdiom→zio.quill.ast.Identzio.quill.context.spark.SparkIdiom→zio.quill.ast.Operationzio.quill.context.spark.SparkIdiom→zio.quill.ast.Propertyzio.quill.context.spark.SparkIdiom→zio.quill.ast.Value
- Direction
- context.spark uses ast, so a change to ast can break context.spark, while a change to context.spark can't break ast.
- Position
- Below the diagonal: context.spark uses a module listed above it, which is the healthy direction.
38→19 context.spark uses context.sql✕
- Connections
- 4 pairs of types, where a type in context.spark uses a type in context.sql.
- The types involved
zio.quill.context.spark.SimpleNestedExpansion→zio.quill.context.sql.FlattenSqlQueryzio.quill.context.spark.SimpleNestedExpansion→zio.quill.context.sql.SqlQueryzio.quill.context.spark.SparkIdiom→zio.quill.context.sql.SqlQueryzio.quill.context.spark.TopLevelExpansion→zio.quill.context.sql.SelectValue
- Direction
- context.spark uses context.sql, so a change to context.sql can break context.spark, while a change to context.spark can't break context.sql.
- Position
- Below the diagonal: context.spark uses a module listed above it, which is the healthy direction.
38→23 context.spark uses context.sql.idiom✕
- Connections
- 1 pair of types, where a type in context.spark uses a type in context.sql.idiom.
- The types involved
zio.quill.context.spark.SparkIdiom→zio.quill.context.sql.idiom.SqlIdiom
- Direction
- context.spark uses context.sql.idiom, so a change to context.sql.idiom can break context.spark, while a change to context.spark can't break context.sql.idiom.
- Position
- Below the diagonal: context.spark uses a module listed above it, which is the healthy direction.
38→26 context.spark uses zio.quill✕
- Connections
- 4 pairs of types, where a type in context.spark uses a type in zio.quill.
- The types involved
zio.quill.context.spark.Decoders→zio.quill.MappedEncodingzio.quill.context.spark.Encoders→zio.quill.MappedEncodingzio.quill.context.spark.SparkIdiom→zio.quill.IdiomContextzio.quill.context.spark.SparkIdiom→zio.quill.NamingStrategy
- Direction
- context.spark uses zio.quill, so a change to zio.quill can break context.spark, while a change to context.spark can't break zio.quill.
- Position
- Below the diagonal: context.spark uses a module listed above it, which is the healthy direction.
38→37 context.spark uses sql.norm✕
- Connections
- 2 pairs of types, where a type in context.spark uses a type in sql.norm.
- The types involved
zio.quill.context.spark.SimpleNestedExpansion→zio.quill.sql.norm.QueryLevelzio.quill.context.spark.SimpleNestedExpansion→zio.quill.sql.norm.StatelessQueryTransformer
- Direction
- context.spark uses sql.norm, so a change to sql.norm can break context.spark, while a change to context.spark can't break sql.norm.
- Position
- Below the diagonal: context.spark uses a module listed above it, which is the healthy direction.
39→13 context.sql.norm uses norm✕
- Connections
- 3 pairs of types, where a type in context.sql.norm uses a type in norm.
- The types involved
zio.quill.context.sql.norm.SqlNormalize→zio.quill.norm.ConcatBehaviorzio.quill.context.sql.norm.SqlNormalize→zio.quill.norm.EqualityBehaviorzio.quill.context.sql.norm.SqlNormalize→zio.quill.norm.TranspileConfig
- Direction
- context.sql.norm uses norm, so a change to norm can break context.sql.norm, while a change to context.sql.norm can't break norm.
- Position
- Below the diagonal: context.sql.norm uses a module listed above it, which is the healthy direction.
39→16 context.sql.norm uses quat✕
- Connections
- 1 pair of types, where a type in context.sql.norm uses a type in quat.
- The types involved
zio.quill.context.sql.norm.ExpandSelection→zio.quill.quat.Quat
- Direction
- context.sql.norm uses quat, so a change to quat can break context.sql.norm, while a change to context.sql.norm can't break quat.
- Position
- Below the diagonal: context.sql.norm uses a module listed above it, which is the healthy direction.
39→17 context.sql.norm uses ast✕
- Connections
- 9 pairs of types, where a type in context.sql.norm uses a type in ast.
- The types involved
zio.quill.context.sql.norm.ExpandDistinct→zio.quill.ast.Astzio.quill.context.sql.norm.ExpandJoin→zio.quill.ast.Astzio.quill.context.sql.norm.ExpandJoin→zio.quill.ast.Identzio.quill.context.sql.norm.ExpandJoin→zio.quill.ast.Joinzio.quill.context.sql.norm.ExpandMappedInfix→zio.quill.ast.Astzio.quill.context.sql.norm.FlattenGroupByAggregation→zio.quill.ast.Astzio.quill.context.sql.norm.FlattenGroupByAggregation→zio.quill.ast.Identzio.quill.context.sql.norm.FlattenGroupByAggregation→zio.quill.ast.StatelessTransformerzio.quill.context.sql.norm.SqlNormalize→zio.quill.ast.Ast
- Direction
- context.sql.norm uses ast, so a change to ast can break context.sql.norm, while a change to context.sql.norm can't break ast.
- Position
- Below the diagonal: context.sql.norm uses a module listed above it, which is the healthy direction.
39→19 context.sql.norm uses context.sql✕
- Connections
- 6 pairs of types, where a type in context.sql.norm uses a type in context.sql.
- The types involved
zio.quill.context.sql.norm.AddDropToNestedOrderBy→zio.quill.context.sql.FromContextzio.quill.context.sql.norm.AddDropToNestedOrderBy→zio.quill.context.sql.SqlQueryzio.quill.context.sql.norm.ExpandNestedQueries→zio.quill.context.sql.FlattenSqlQueryzio.quill.context.sql.norm.ExpandNestedQueries→zio.quill.context.sql.FromContextzio.quill.context.sql.norm.ExpandNestedQueries→zio.quill.context.sql.SqlQueryzio.quill.context.sql.norm.ExpandSelection→zio.quill.context.sql.SelectValue
- Direction
- context.sql.norm uses context.sql, so a change to context.sql can break context.sql.norm, while a change to context.sql.norm can't break context.sql.
- Position
- Below the diagonal: context.sql.norm uses a module listed above it, which is the healthy direction.
39→37 context.sql.norm uses sql.norm✕
- Connections
- 3 pairs of types, where a type in context.sql.norm uses a type in sql.norm.
- The types involved
zio.quill.context.sql.norm.ExpandNestedQueries→zio.quill.sql.norm.QueryLevelzio.quill.context.sql.norm.ExpandNestedQueries→zio.quill.sql.norm.StatelessQueryTransformerzio.quill.context.sql.norm.ExpandSelection→zio.quill.sql.norm.QueryLevel
- Direction
- context.sql.norm uses sql.norm, so a change to sql.norm can break context.sql.norm, while a change to context.sql.norm can't break sql.norm.
- Position
- Below the diagonal: context.sql.norm uses a module listed above it, which is the healthy direction.
40→5 jdbczio.Quill uses context.json✕
- Connections
- 1 pair of types, where a type in jdbczio.Quill uses a type in context.json.
- The types involved
zio.quill.jdbczio.Quill.Postgres→zio.quill.context.json.PostgresJsonExtensions
- Direction
- jdbczio.Quill uses context.json, so a change to context.json can break jdbczio.Quill, while a change to jdbczio.Quill can't break context.json.
- Position
- Below the diagonal: jdbczio.Quill uses a module listed above it, which is the healthy direction.
40→22 jdbczio.Quill uses context.jdbc✕
- Connections
- 7 pairs of types, where a type in jdbczio.Quill uses a type in context.jdbc.
- The types involved
zio.quill.jdbczio.Quill.H2→zio.quill.context.jdbc.H2JdbcTypeszio.quill.jdbczio.Quill.Mysql→zio.quill.context.jdbc.MysqlJdbcTypeszio.quill.jdbczio.Quill.Oracle→zio.quill.context.jdbc.OracleJdbcTypeszio.quill.jdbczio.Quill.Postgres→zio.quill.context.jdbc.PostgresJdbcTypeszio.quill.jdbczio.Quill.PostgresLite→zio.quill.context.jdbc.PostgresJdbcTypeszio.quill.jdbczio.Quill.SqlServer→zio.quill.context.jdbc.SqlServerJdbcTypeszio.quill.jdbczio.Quill.Sqlite→zio.quill.context.jdbc.SqliteJdbcTypes
- Direction
- jdbczio.Quill uses context.jdbc, so a change to context.jdbc can break jdbczio.Quill, while a change to jdbczio.Quill can't break context.jdbc.
- Position
- Below the diagonal: jdbczio.Quill uses a module listed above it, which is the healthy direction.
40→26 jdbczio.Quill uses zio.quill✕
- Connections
- 7 pairs of types, where a type in jdbczio.Quill uses a type in zio.quill.
- The types involved
zio.quill.jdbczio.Quill.H2→zio.quill.H2Dialectzio.quill.jdbczio.Quill.Mysql→zio.quill.MySQLDialectzio.quill.jdbczio.Quill.Oracle→zio.quill.OracleDialectzio.quill.jdbczio.Quill.Postgres→zio.quill.PostgresDialectzio.quill.jdbczio.Quill.PostgresLite→zio.quill.PostgresDialectzio.quill.jdbczio.Quill.SqlServer→zio.quill.SQLServerDialectzio.quill.jdbczio.Quill.Sqlite→zio.quill.SqliteDialect
- Direction
- jdbczio.Quill uses zio.quill, so a change to zio.quill can break jdbczio.Quill, while a change to jdbczio.Quill can't break zio.quill.
- Position
- Below the diagonal: jdbczio.Quill uses a module listed above it, which is the healthy direction.
40→35 jdbczio.Quill uses jdbczio✕
- Connections
- 7 pairs of types, where a type in jdbczio.Quill uses a type in jdbczio.
- The types involved
zio.quill.jdbczio.Quill.H2→zio.quill.jdbczio.Quillzio.quill.jdbczio.Quill.Mysql→zio.quill.jdbczio.Quillzio.quill.jdbczio.Quill.Oracle→zio.quill.jdbczio.Quillzio.quill.jdbczio.Quill.Postgres→zio.quill.jdbczio.Quillzio.quill.jdbczio.Quill.PostgresLite→zio.quill.jdbczio.Quillzio.quill.jdbczio.Quill.SqlServer→zio.quill.jdbczio.Quillzio.quill.jdbczio.Quill.Sqlite→zio.quill.jdbczio.Quill
- Direction
- jdbczio.Quill uses jdbczio, so a change to jdbczio can break jdbczio.Quill, while a change to jdbczio.Quill can't break jdbczio.
- Position
- Below the diagonal: jdbczio.Quill 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 — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 50 | High / Critical |
| A02:2025 — Security Misconfiguration | 27 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 4 | Medium |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3), REDACTED (2); Resolve the 118 Orphaned file finding(s) in Knowledge Freshness — start with Encoders.scala (3), Decoders.scala (3), Quill.scala (2); 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED. | +3.1 pts | Low | Secret Scanning |
| Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3), REDACTED (2). | +4.6 pts | Medium | Static Analysis (SAST) |
| Resolve the 118 Orphaned file finding(s) in Knowledge Freshness — start with Encoders.scala (3), Decoders.scala (3), Quill.scala (2). | +4.1 pts | High | Knowledge Freshness |
| 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. | +3.9 pts | Medium | Architecture documentation |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.5 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.4 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.4 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.4 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 0.7 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 3.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| quill-engine/src/main/scala/zio/quill/sql/SqlQuery.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| quill-core/src/main/scala/zio/quill/quotation/Parsing.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| quill-core/src/main/scala/zio/quill/dsl/DynamicQueryDSL.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| quill-jdbc-zio/src/main/scala/zio/quill/context/qzio/ZioJdbcUnderlyingContext.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| quill-core/src/main/scala/zio/quill/context/ContextVerbTranslate.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| quill-engine/src/main/scala/zio/quill/MySQLDialect.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| quill-core/src/main/scala/zio/quill/context/ActionMacro.scala | 6.7 | 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
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 47 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 47 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, 363 of 386 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 or a scanner, 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 |
| Canine Code Analyzer 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 |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a Codecov configuration (codecov.yml) and a coverage step in CI (`sbt $SBT_ARGS coverageReport`) 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.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) and this repository declares an sbt build (repository root, 410 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its sbt dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (build.sbt), but 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (23626 LoC, 1262 module-visible types across 68 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `quill-core/src/main/scala/zio/quill/quotation/Parsing.scala` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This 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 Dockerfile) is simply not read here yet.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 17 — an image could not be built) — failed to solve: failed to load cache key: invalid response status 429; runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'javax.sql.DataSource' is imported (quill-jdbc-zio/src/main/scala/zio/quill/ZioJdbcContexts.scala:10), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'javax.sql.DataSource' is imported (quill-jdbc-zio/src/main/scala/zio/quill/ZioJdbcContexts.scala:10), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'javax.sql.DataSource' is imported (quill-jdbc-zio/src/main/scala/zio/quill/ZioJdbcContexts.scala:10), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- 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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- 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.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- 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
9 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SqlQueryApply.flatten at 46. A further 25 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 DefaultJdbcTyper.apply at 26 — they are counted neither in the figure above nor in this dimension's score. 14 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: quill-codegen-jdbc/src/main/scala/zio/quill/codegen/jdbc/model/DefaultJdbcTyper.scala (DefaultJdbcTyper.apply at 26), quill-engine/src/main/scala/zio/quill/MirrorIdiom.scala (MirrorIdiomBase.astTokenizer at 23), quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala (StatefulTransformer.apply at 23), quill-engine/src/main/scala/zio/quill/ast/StatefulTransformerWithStack.scala (StatefulTransformerWithStack.apply at 23), quill-engine/src/main/scala/zio/quill/ast/StatelessTransformer.scala (StatelessTransformer.apply at 23), and 9 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 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with SqlQueryApply.flatten (cyclomatic 46), QuatMakingBase.inferQuat (cyclomatic 38). — 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 2 together lifts Cyclomatic Complexity from 8.1 to about 8.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D2 · Cognitive Complexity
11 method(s) exceeded the cognitive complexity threshold of 15; the worst was SqlQueryApply.flatten at 44.
What to do
- Bring the 11 bodies over 15 down to 15 or less in Cognitive Complexity — start with SqlQueryApply.flatten (cognitive 44), QuatMakingBase.inferQuat (cognitive 40), ZioJdbcContext.transaction (cognitive 35). — 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 11 together lifts Cognitive Complexity from 8.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
8 god class(es) detected.
What to do
- Resolve the 5 TooManyMethods finding(s) in God Classes — start with SqlIdiom.scala, DynamicQueryDSL.scala, Parsing.scala. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 3 FileTooLong finding(s) in God Classes — start with Parsing.scala, SqlIdiom.scala, Ast.scala. — One of this dimension's main actionable groups (3 warning-level).
D4 · Code Duplication
25 duplicated block group(s) detected. 6.8 % of the production lines (1,602 of 23,626) are in a reported copy. A further 33 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 8 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with SqlIdiom.scala (3), StatefulTransformer.scala (2), Encoders.scala. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 4 Edited copy of a member (6 corresponding lines) finding(s) in Code Duplication — start with AddDropToNestedOrderBy.scala, StatefulTransformerWithStack.scala, AsyncMirrorContext.scala. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Edited copy of a member (5 corresponding lines) finding(s) in Code Duplication — start with MirrorEncoders.scala, StatefulTransformer.scala, CassandraPekkoContext.scala. — One of this dimension's main actionable groups (4 warning-level).
D5 · Coupling
17 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; 0 module(s) off the main sequence, with abstractness counted on 15 of the 17 (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).
D6 · Cohesion (LCOM4)
0 of 26 classes have LCOM4 above 3.
D12 · Dependency Hygiene
13 outdated direct sbt declarations. 23 of 24 direct declarations were graded against Maven Central (0 not published there, which is what a private Nexus or Artifactory artifact looks like, 1 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.
D13 · Secret Scanning
2 secret(s) detected.
What to do
- Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
D14 · License Compliance
0 of 23 declared sbt dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the production coordinates this repository's 2 sbt build file(s) (build.sbt and project/*.scala) declare with a literal version, directly or through a string-literal val — `%%` resolved to the Scala binary suffix Central publishes under, test-scoped declarations excluded — the same declaration-site closure this analysis reads for dependency currency. sbt has no lockfile a checkout carries, so this is deliberately NOT the transitive closure. 3 further production coordinate(s) are declared with a version the build computes rather than writes as a literal — sbt is a program, and this pass does not run it — and are NOT graded: this verdict covers what the build pins literally or through a string-literal val, not the full graph. A further 1 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's sbt dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: quill-engine/src/main/scala/zio/quill/norm/SheathLeafClauses.scala (2×26=52); quill-engine/src/main/scala/zio/quill/norm/BetaReduction.scala (2×16=32)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with SheathLeafClauses.scala, BetaReduction.scala. — One of this dimension's main actionable groups (2 warning-level).
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is quill-engine/src/main/scala/zio/quill/norm/ApplyMap.scala. Counted over 130 of the 305 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
30 deducted task-comment markers across 23626 LoC (0.1/KLoC) → score 9.8. 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 28 TodoComment finding(s) in Explicit Debt — start with SheathLeafClausesSpec.scala (3), Parsing.scala (3), ExpandEntityIdsSpec.scala (2). — One of this dimension's main actionable groups (28 warning-level).
- Resolve the 2 HackComment finding(s) in Explicit Debt — start with OptionJdbcSpec.scala, MirrorContexts.scala. — One of this dimension's main actionable groups (2 warning-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
50 finding(s): 0 critical, 50 high, 0 medium, 0 low. 37 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 1 file(s) — `quill-core/src/main/scala/zio/quill/quotation/Parsing.scala` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (12 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 37 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 (37 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D31 · IaC & Container Security
27 finding(s): 0 critical, 11 high, 12 medium, 4 low.
What to do
- Resolve the 12 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (12 warning-level).
- Resolve the 11 High IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (11 issue-level).
- Resolve the 4 Low IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 recommendation-level).
D34 · Knowledge Freshness
121 of 130 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is quill-core/src/main/scala/zio/quill/quotation/Parsing.scala. Counted over 130 of the 305 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 118 Orphaned file finding(s) in Knowledge Freshness — start with Encoders.scala (3), Decoders.scala (3), Quill.scala (2). — One of this dimension's main actionable groups (118 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with Parsing.scala, SqlIdiom.scala, Ast.scala. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: ActionMacro.scala↔QueryMacro.scala 75%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with ActionMacro.scala. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `CassandraContext[N]` declares 34 abstract members: `optionDecoder`, `optionEncoder`, `stringDecoder`, `bigDecimalDecoder`, `booleanDecoder`, `byteDecoder`, `shortDecoder`, `intDecoder`, `longDecoder`, `floatDecoder`, `doubleDecoder`, `byteArrayDecoder`, `uuidDecoder`, `timestampDecoder`, `cassandraLocalDateDecoder`, `stringEncoder`, `bigDecimalEncoder`, `booleanEncoder`, `byteEncoder`, `shortEncoder`, `intEncoder`, `longEncoder`, `floatEncoder`, `doubleEncoder`, `byteArrayEncoder`, `uuidEncoder`, `timestampEncoder`, `cassandraLocalDateEncoder`, `listDecoder`, `setDecoder`, `mapDecoder`, `listEncoder`, `setEncoder`, `mapEncoder`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — quill-cassandra/src/main/scala/zio/quill/context/cassandra/CassandraContext.scala:11
- `OrientDBContext[Naming]` declares 28 abstract members: `optionDecoder`, `optionEncoder`, `stringDecoder`, `doubleDecoder`, `bigDecimalDecoder`, `booleanDecoder`, `shortDecoder`, `intDecoder`, `longDecoder`, `floatDecoder`, `byteArrayDecoder`, `dateDecoder`, `stringEncoder`, `bigDecimalEncoder`, `booleanEncoder`, `shortEncoder`, `intEncoder`, `longEncoder`, `floatEncoder`, `doubleEncoder`, `dateEncoder`, `byteArrayEncoder`, `listDecoder`, `setDecoder`, `mapDecoder`, `listEncoder`, `setEncoder`, `mapEncoder`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — quill-orientdb/src/main/scala/zio/quill/context/orientdb/OrientDBContext.scala:9
- `SqlContext[Idiom, Naming]` declares 29 abstract members: `nullChecker`, `optionDecoder`, `optionEncoder`, `stringDecoder`, `bigDecimalDecoder`, `booleanDecoder`, `byteDecoder`, `shortDecoder`, `intDecoder`, `longDecoder`, `floatDecoder`, `doubleDecoder`, `byteArrayDecoder`, `dateDecoder`, `localDateDecoder`, `uuidDecoder`, `stringEncoder`, `bigDecimalEncoder`, `booleanEncoder`, `byteEncoder`, `shortEncoder`, `intEncoder`, `longEncoder`, `floatEncoder`, `doubleEncoder`, `byteArrayEncoder`, `dateEncoder`, `localDateEncoder`, `uuidEncoder`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — quill-sql/src/main/scala/zio/quill/context/sql/SqlContext.scala:12
- `ArrayEncoding` declares 22 abstract members: `arrayStringEncoder`, `arrayBigDecimalEncoder`, `arrayBooleanEncoder`, `arrayByteEncoder`, `arrayShortEncoder`, `arrayIntEncoder`, `arrayLongEncoder`, `arrayFloatEncoder`, `arrayDoubleEncoder`, `arrayDateEncoder`, `arrayLocalDateEncoder`, `arrayStringDecoder`, `arrayBigDecimalDecoder`, `arrayBooleanDecoder`, `arrayByteDecoder`, `arrayShortDecoder`, `arrayIntDecoder`, `arrayLongDecoder`, `arrayFloatDecoder`, `arrayDoubleDecoder`, `arrayDateDecoder`, `arrayLocalDateDecoder`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — quill-sql/src/main/scala/zio/quill/context/sql/encoding/ArrayEncoding.scala:11
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX8 · Test isolation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×37) — quill-core/src/test/scala/zio/quill/util/LogToFileSpec.scala:10, quill-jdbc-test-h2/src/test/scala/zio/quill/context/jdbc/h2/PeopleJdbcReturningSpec.scala:26, quill-jdbc-test-h2/src/test/scala/zio/quill/context/jdbc/h2/PeopleJdbcReturningSpec.scala:39, …
What to do
- Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- 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.
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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
What to do
- Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 6 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — .github/workflows/auto-approve.yml:7
- `.github/dependabot.yml` schedules updates, but no `package-ecosystem` entry covers `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — .github/dependabot.yml:5
What to do
- Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Dependabot is configured but does not watch `npm` — add that `package-ecosystem` entry to .github/dependabot.yml 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
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
P6 · Release Hygiene
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X27 · Collection changed while being enumerated
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — quill-core/src/main/scala/zio/logging/extensions.scala:82
What to do
- Swallowed exception (empty catch)
X5 · Nullable reference types
- No build over this repository's 302 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
Reference — by lens
| 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 | 99% | Exemplary | Solid. |
| Maturity | 52% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 61% | Adequate — gated by D13, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 46% | Checked 4 of 10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'javax.sql.DataSource' (quill-jdbc-zio/src/main/scala/zio/quill/ZioJdbcContexts.scala:10) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'javax.sql.DataSource' (quill-jdbc-zio/src/main/scala/zio/quill/ZioJdbcContexts.scala:10) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'javax.sql.DataSource' (quill-jdbc-zio/src/main/scala/zio/quill/ZioJdbcContexts.scala:10) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 66 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's 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 — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Scala code is a Play controller, a Cask routes object, a Scalatra servlet, a Finatra controller, an Akka/Pekko HTTP routes holder or a JSR-330/Spring singleton, so no instance is shared between request threads.
- 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 — compose up failed (exit 17 — an image could not be built) — failed to solve: failed to load cache key: invalid response status 429; 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.
- D10 Test Quality — ~41673 lines of test source are present (.scala) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .scala suite was found but not re-run
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 6 candidate(s) found and not reported.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .scala source were not judged.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- 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 (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 256 value object(s); 4 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — No web surface: 302 Scala file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server artifact (akka-http, pekko-http, http4s, Play, Finagle, zio-http, cask, Scalatra, a tapir server, Jetty, Undertow, …) outside test scope in its build, and no server package imported or server bound in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Scala was 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
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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 — 63 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
- 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
- REDACTED
Serious — 134 finding(s)
- TodoComment quill-sql-test/src/test/scala/zio/quill/context/sql/norm/SheathLeafClausesSpec.scala:52
- TodoComment quill-sql-test/src/test/scala/zio/quill/context/sql/norm/SheathLeafClausesSpec.scala:67
- TodoComment quill-sql-test/src/test/scala/zio/quill/context/sql/norm/SheathLeafClausesSpec.scala:117
- TodoComment quill-sql-test/src/test/scala/zio/quill/context/sql/idiom/SqlIdiomSpec.scala:499
- TodoComment quill-spark/src/test/scala/zio/quill/context/spark/norm/ExpandEntityIdsSpec.scala:370
- TodoComment quill-spark/src/test/scala/zio/quill/context/spark/norm/ExpandEntityIdsSpec.scala:371
- TodoComment quill-spark/src/main/scala/zio/quill/context/spark/SparkDialect.scala:119
- TodoComment quill-jdbc-zio/src/main/scala/zio/quill/context/qzio/ZioJdbcUnderlyingContext.scala:206
- TodoComment quill-engine/src/main/scala/zio/quill/MySQLDialect.scala:70
- TodoComment quill-engine/src/main/scala/zio/quill/SqliteDialect.scala:62
- TodoComment quill-engine/src/main/scala/zio/quill/sql/SqlQuery.scala:420
- TodoComment quill-engine/src/main/scala/zio/quill/sql/norm/SelectPropertyProtractor.scala:168
- TodoComment quill-engine/src/main/scala/zio/quill/quat/FindBranches.scala:79
- TodoComment quill-engine/src/main/scala/zio/quill/norm/ExpandReturning.scala:62
- TodoComment quill-core/src/test/scala/zio/quill/util/LogToFileSpec.scala:9
- TodoComment quill-core/src/test/scala/zio/quill/quat/QuatSpec.scala:66
- TodoComment quill-core/src/main/scala/zio/quill/quotation/Parsing.scala:379
- TodoComment quill-core/src/main/scala/zio/quill/quotation/Parsing.scala:463
- TodoComment quill-core/src/main/scala/zio/quill/quotation/Parsing.scala:471
- TodoComment quill-core/src/main/scala/zio/quill/quotation/Rebind.scala:28
- TodoComment quill-core/src/main/scala/zio/quill/dsl/DynamicQueryDSL.scala:379
- TodoComment quill-core/src/main/scala/zio/quill/dsl/DynamicQueryDSL.scala:380
- TodoComment quill-core/src/main/scala/zio/quill/context/ActionMacro.scala:39
- TodoComment quill-core/src/main/scala/zio/quill/context/ContextVerbTranslate.scala:106
- TodoComment quill-codegen/src/main/scala/zio/quill/codegen/model/Typing.scala:8
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (6 lines × 2) quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:155
- Duplicated block (6 lines × 2) quill-cassandra/src/main/scala/zio/quill/context/cassandra/encoding/Encoders.scala:28
- Duplicated block (6 lines × 2) quill-core/src/main/scala/zio/quill/quat/QuatMacro.scala:10
- Duplicated block (6 lines × 2) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:305
- Duplicated block (6 lines × 2) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:313
- Duplicated block (6 lines × 2) quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:770
- Duplicated block (6 lines × 2) quill-jdbc-zio/src/main/scala/zio/quill/context/ZioJdbc.scala:73
- Duplicated block (6 lines × 2) quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:349
- TooManyMethods: SqlIdiom quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:24
- TooManyMethods: DynamicQuery quill-core/src/main/scala/zio/quill/dsl/DynamicQueryDSL.scala:194
- TooManyMethods: Parsing quill-core/src/main/scala/zio/quill/quotation/Parsing.scala:23
- TooManyMethods: Query quill-engine/src/main/scala/zio/quill/Model.scala:15
- TooManyMethods: Messages quill-engine/src/main/scala/zio/quill/util/Messages.scala:6
- Edited copy of a member (6 corresponding lines) quill-engine/src/main/scala/zio/quill/sql/norm/AddDropToNestedOrderBy.scala:15
- Edited copy of a member (6 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformerWithStack.scala:238
- Edited copy of a member (6 corresponding lines) quill-core/src/main/scala/zio/quill/AsyncMirrorContext.scala:136
- Edited copy of a member (6 corresponding lines) quill-core/src/main/scala/zio/quill/context/ContextVerbTranslate.scala:119
- Edited copy of a member (5 corresponding lines) quill-core/src/main/scala/zio/quill/context/mirror/MirrorEncoders.scala:30
- Edited copy of a member (5 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:238
- Edited copy of a member (5 corresponding lines) quill-cassandra-pekko/src/main/scala/zio/quill/CassandraPekkoContext.scala:96
- Edited copy of a member (5 corresponding lines) quill-jdbc/src/main/scala/zio/quill/context/jdbc/JdbcContextVerbExecute.scala:73
- FileTooLong: quotation/Parsing.scala quill-core/src/main/scala/zio/quill/quotation/Parsing.scala
- FileTooLong: idiom/SqlIdiom.scala quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala
- FileTooLong: ast/Ast.scala quill-engine/src/main/scala/zio/quill/ast/Ast.scala
- Edited copy of a member (7 corresponding lines) quill-engine/src/main/scala/zio/quill/quotation/FreeVariables.scala:49
- Edited copy of a member (7 corresponding lines) quill-engine/src/main/scala/zio/quill/sql/SqlQuery.scala:544
- Edited copy of a member (7 corresponding lines) quill-core/src/main/scala/zio/quill/AsyncMirrorContext.scala:149
- Hotspot: quill-engine/src/main/scala/zio/quill/norm/SheathLeafClauses.scala quill-engine/src/main/scala/zio/quill/norm/SheathLeafClauses.scala:114
- Hotspot: quill-engine/src/main/scala/zio/quill/norm/BetaReduction.scala quill-engine/src/main/scala/zio/quill/norm/BetaReduction.scala:44
- HackComment quill-jdbc-test-sqlserver/src/test/scala/zio/quill/context/jdbc/sqlserver/OptionJdbcSpec.scala:23
- HackComment quill-core/src/test/scala/zio/quill/MirrorContexts.scala:11
- Edited copy of a member (17 corresponding lines) quill-engine/src/main/scala/zio/quill/norm/RepropagateQuats.scala:60
- Edited copy of a member (17 corresponding lines) quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:163
- Edited copy of a member (11 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:260
- Edited copy of a member (11 corresponding lines) quill-cassandra-pekko/src/main/scala/zio/quill/CassandraPekkoContext.scala:40
- Edited copy of a member (10 corresponding lines) quill-jdbc-zio/src/main/scala-2.12/zio/quill/context/json/PostgresJsonExtensions.scala:58
- Edited copy of a member (10 corresponding lines) quill-jdbc-zio/src/main/scala-2.12/zio/quill/context/json/PostgresJsonExtensions.scala:28
- Edited copy of a member (4 corresponding lines) quill-engine/src/main/scala/zio/quill/context/cassandra/CqlIdiom.scala:224
- Edited copy of a member (4 corresponding lines) quill-engine/src/main/scala/zio/quill/PostgresDialect.scala:36
- Duplicated block (11 lines × 2) quill-jdbc-zio/src/main/scala-2.12/zio/quill/context/json/PostgresJsonExtensions.scala:40
- Duplicated block (11 lines × 2) quill-jdbc-zio/src/main/scala-2.12/zio/quill/context/json/PostgresJsonExtensions.scala:75
- Duplicated block (8 lines × 2) quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:554
- Duplicated block (8 lines × 2) quill-jdbc-zio/src/main/scala-2.12/zio/quill/context/json/PostgresJsonExtensions.scala:60
- Duplicated block (7 lines × 2) quill-cassandra/src/main/scala/zio/quill/CassandraMirrorContext.scala:22
- Duplicated block (7 lines × 2) quill-core/src/main/scala/zio/quill/util/ExceptionOps.scala:7
- SqlQueryApply.flatten (cyclomatic 46) quill-engine/src/main/scala/zio/quill/sql/SqlQuery.scala:204
- QuatMakingBase.inferQuat (cyclomatic 38) quill-core/src/main/scala/zio/quill/quat/QuatMaking.scala:158
- SheathLeafClauses.apply (cyclomatic 26) quill-engine/src/main/scala/zio/quill/norm/SheathLeafClauses.scala:114
- NormalizeNestedStructures.unapply (cyclomatic 22) quill-engine/src/main/scala/zio/quill/norm/NormalizeNestedStructures.scala:7
- SqlIdiom.actionTokenizer (cyclomatic 21) quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:654
- OrientDBIdiom.orientDBQueryTokenizer (cyclomatic 21) quill-orientdb/src/main/scala/zio/quill/context/orientdb/OrientDBIdiom.scala:128
- ReifyLiftings.apply (cyclomatic 19) quill-core/src/main/scala/zio/quill/quotation/ReifyLiftings.scala:83
- AstPrinter.treeify (cyclomatic 19) quill-engine/src/main/scala/zio/quill/AstPrinter.scala:90
- BetaReduction.apply (cyclomatic 16) quill-engine/src/main/scala/zio/quill/norm/BetaReduction.scala:44
- SqlQueryApply.flatten (cognitive 44) quill-engine/src/main/scala/zio/quill/sql/SqlQuery.scala:204
- QuatMakingBase.inferQuat (cognitive 40) quill-core/src/main/scala/zio/quill/quat/QuatMaking.scala:158
- ZioJdbcContext.transaction (cognitive 35) quill-jdbc-zio/src/main/scala/zio/quill/context/qzio/ZioJdbcContext.scala:192
- OrientDBIdiom.orientDBQueryTokenizer (cognitive 32) quill-orientdb/src/main/scala/zio/quill/context/orientdb/OrientDBIdiom.scala:128
- ReifyLiftings.apply (cognitive 25) quill-core/src/main/scala/zio/quill/quotation/ReifyLiftings.scala:83
- AstPrinter.treeify (cognitive 24) quill-engine/src/main/scala/zio/quill/AstPrinter.scala:90
- Parsing.combinedInfixParser (cognitive 23) quill-core/src/main/scala/zio/quill/quotation/Parsing.scala:394
- SheathLeafClauses.apply (cognitive 22) quill-engine/src/main/scala/zio/quill/norm/SheathLeafClauses.scala:114
- InsertReturnCapabilityExtension.verifyAst (cognitive 18) quill-core/src/main/scala/zio/quill/quotation/Parsing.scala:964
- ZioJdbcUnderlyingContext.streamQuery (cognitive 18) quill-jdbc-zio/src/main/scala/zio/quill/context/qzio/ZioJdbcUnderlyingContext.scala:175
- SeedRenames.apply (cognitive 17) quill-engine/src/main/scala/zio/quill/norm/RenameProperties.scala:119
- Change coupling: ActionMacro.scala ↔ QueryMacro.scala quill-core/src/main/scala/zio/quill/context/ActionMacro.scala:1
- REDACTED
- REDACTED
- Edited copy of a member (70 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:150
- Edited copy of a member (75 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:57
- Edited copy of a member (47 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:8
- Edited copy of a member (30 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:273
- Edited copy of a member (56 corresponding lines) quill-cassandra/src/main/scala/zio/quill/context/cassandra/encoding/UdtEncodingMacro.scala:81
- Edited copy of a member (22 corresponding lines) quill-engine/src/main/scala/zio/quill/context/cassandra/CqlIdiom.scala:44
- Edited copy of a member (36 corresponding lines) quill-engine/src/main/scala/zio/quill/norm/AdHocReduction.scala:16
- Edited copy of a member (14 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:134
- Edited copy of a member (13 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:245
- Edited copy of a member (18 corresponding lines) quill-core/src/main/scala/zio/quill/quotation/TranspileConfigSummoning.scala:29
- Edited copy of a member (9 corresponding lines) quill-engine/src/main/scala/zio/quill/sql/norm/ExpandNestedQueries.scala:193
- Edited copy of a member (19 corresponding lines) quill-codegen-jdbc/src/main/scala/zio/quill/codegen/jdbc/gen/DefaultJdbcSchemaReader.scala:33
- Edited copies of one member (3 members, 13+ corresponding lines) quill-jdbc/src/main/scala/zio/quill/context/jdbc/JdbcContextVerbExecute.scala:105
- Edited copies of one member (3 members, 4+ corresponding lines) quill-engine/src/main/scala/zio/quill/MySQLDialect.scala:86
- Duplicated block (73–74 lines × 2) quill-core/src/main/scala/zio/quill/context/QueryMacro.scala:60
- Duplicated block (13–23 lines × 2) quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:141
- Duplicated block (19 lines × 2) quill-engine/src/main/scala/zio/quill/norm/SheathLeafClauses.scala:165
- Duplicated block (15 lines × 2) quill-cassandra/src/main/scala/zio/quill/context/cassandra/encoding/UdtEncodingMacro.scala:110
- Duplicated block (14–15 lines × 2) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:10
- Duplicated block (14 lines × 2) quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:164
- Duplicated block (25–26 lines × 2) quill-engine/src/main/scala/zio/quill/idiom/ReifyStatement.scala:27
- Duplicated block (7–10 lines × 2) quill-engine/src/main/scala/zio/quill/sql/SqlQuery.scala:318
- Duplicated block (10 lines × 2) quill-engine/src/main/scala/zio/quill/idiom/ReifyStatement.scala:58
- Duplicated block (7 lines × 3) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:8
- Duplicated block (5 lines × 3) quill-engine/src/main/scala/zio/quill/context/cassandra/CqlIdiom.scala:155
- Swallowed exception (empty catch) quill-core/src/main/scala/zio/logging/extensions.scala:82
Minor — 176 finding(s)
- Orphaned file quill-engine/src/main/scala/zio/quill/sql/SqlQuery.scala:1
- Orphaned file quill-engine/src/main/scala/zio/quill/quat/Quat.scala:1
- Orphaned file quill-engine/src/main/scala/zio/quill/norm/SheathLeafClauses.scala:1
- Orphaned file quill-core/src/main/scala/zio/quill/context/ActionMacro.scala:1
- Orphaned file quill-engine/src/main/scala/zio/quill/MirrorIdiom.scala:1
- Orphaned file quill-orientdb/src/main/scala/zio/quill/context/orientdb/OrientDBIdiom.scala:1
- Orphaned file quill-engine/src/main/scala/zio/quill/util/Using.scala:1
- Orphaned file quill-core/src/main/scala/zio/quill/quotation/Liftables.scala:1
- Orphaned file quill-core/src/main/scala/zio/quill/quat/QuatMaking.scala:1
- Orphaned file quill-engine/src/main/scala/zio/quill/norm/capture/AvoidAliasConflict.scala:1
- Orphaned file quill-engine/src/main/scala/zio/quill/ast/StatefulTransformerWithStack.scala:1
- Orphaned file quill-engine/src/main/scala/zio/quill/norm/BetaReduction.scala:1
- Orphaned file quill-jdbc-zio/src/main/scala/zio/quill/context/qzio/ZioJdbcContext.scala:1
- Orphaned file quill-engine/src/main/scala/zio/quill/util/Messages.scala:1
- Orphaned file quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:1
- Orphaned file quill-engine/src/main/scala/zio/quill/context/cassandra/CqlIdiom.scala:1
- Orphaned file quill-engine/src/main/scala/zio/quill/sql/norm/SelectPropertyProtractor.scala:1
- Orphaned file quill-codegen/src/main/scala/zio/quill/codegen/gen/Generator.scala:1
- Orphaned file quill-jdbc-zio/src/main/scala/zio/quill/context/qzio/ZioJdbcUnderlyingContext.scala:1
- Orphaned file quill-core/src/main/scala/zio/quill/context/QueryMacro.scala:1
- Orphaned file quill-cassandra/src/main/scala/zio/quill/context/cassandra/encoding/UdtEncodingMacro.scala:1
- Orphaned file quill-engine/src/main/scala/zio/quill/idiom/ReifyStatement.scala:1
- Orphaned file quill-spark/src/main/scala/zio/quill/context/spark/SparkDialect.scala:1
- Orphaned file quill-engine/src/main/scala/zio/quill/norm/RepropagateQuats.scala:1
- Orphaned file quill-engine/src/main/scala/zio/quill/quat/FindBranches.scala:1
- Disabled test quill-core/src/test/scala/zio/quill/util/LogToFileSpec.scala:10
- Disabled test quill-jdbc-test-h2/src/test/scala/zio/quill/context/jdbc/h2/PeopleJdbcReturningSpec.scala:26
- Disabled test quill-jdbc-test-h2/src/test/scala/zio/quill/context/jdbc/h2/PeopleJdbcReturningSpec.scala:39
- Disabled test quill-jdbc-test-h2/src/test/scala/zio/quill/context/jdbc/h2/PeopleJdbcReturningSpec.scala:46
- Disabled test quill-jdbc-test-h2/src/test/scala/zio/quill/context/jdbc/h2/PeopleJdbcReturningSpec.scala:53
- Disabled test quill-jdbc-test-mysql/src/test/scala/zio/quill/context/jdbc/mysql/PeopleJdbcReturningSpec.scala:26
- Disabled test quill-jdbc-test-mysql/src/test/scala/zio/quill/context/jdbc/mysql/PeopleJdbcReturningSpec.scala:39
- Disabled test quill-jdbc-test-mysql/src/test/scala/zio/quill/context/jdbc/mysql/PeopleJdbcReturningSpec.scala:46
- Disabled test quill-jdbc-test-mysql/src/test/scala/zio/quill/context/jdbc/mysql/PeopleJdbcReturningSpec.scala:53
- Disabled test quill-jdbc-test-oracle/src/test/scala/zio/quill/context/jdbc/oracle/JdbcContextSpec.scala:88
- Disabled test quill-jdbc-test-oracle/src/test/scala/zio/quill/context/jdbc/oracle/PeopleJdbcReturningSpec.scala:38
- Disabled test quill-jdbc-test-oracle/src/test/scala/zio/quill/context/jdbc/oracle/PeopleJdbcReturningSpec.scala:45
- Disabled test quill-jdbc-test-oracle/src/test/scala/zio/quill/context/jdbc/oracle/PeopleJdbcReturningSpec.scala:52
- Disabled test quill-jdbc-test-sqlite/src/test/scala/zio/quill/context/jdbc/sqlite/PeopleJdbcReturningSpec.scala:26
- Disabled test quill-jdbc-test-sqlite/src/test/scala/zio/quill/context/jdbc/sqlite/PeopleJdbcReturningSpec.scala:39
- Disabled test quill-jdbc-test-sqlite/src/test/scala/zio/quill/context/jdbc/sqlite/PeopleJdbcReturningSpec.scala:46
- Disabled test quill-jdbc-test-sqlite/src/test/scala/zio/quill/context/jdbc/sqlite/PeopleJdbcReturningSpec.scala:53
- Disabled test quill-jdbc-test-sqlserver/src/test/scala/zio/quill/context/jdbc/sqlserver/PeopleJdbcReturningSpec.scala:50
- Disabled test quill-jdbc-zio/src/test/scala/zio/quill/h2/PeopleZioReturningSpec.scala:29
- Disabled test quill-jdbc-zio/src/test/scala/zio/quill/h2/PeopleZioReturningSpec.scala:46
- Disabled test quill-jdbc-zio/src/test/scala/zio/quill/h2/PeopleZioReturningSpec.scala:56
- Disabled test quill-jdbc-zio/src/test/scala/zio/quill/h2/PeopleZioReturningSpec.scala:66
- Disabled test quill-jdbc-zio/src/test/scala/zio/quill/mysql/PeopleZioReturningSpec.scala:29
- Disabled test quill-jdbc-zio/src/test/scala/zio/quill/mysql/PeopleZioReturningSpec.scala:46
- Disabled test quill-jdbc-zio/src/test/scala/zio/quill/mysql/PeopleZioReturningSpec.scala:56
- Fat interface: CassandraContext[N] (34 abstract members) quill-cassandra/src/main/scala/zio/quill/context/cassandra/CassandraContext.scala:11
- Fat interface: OrientDBContext[Naming] (28 abstract members) quill-orientdb/src/main/scala/zio/quill/context/orientdb/OrientDBContext.scala:9
- Fat interface: SqlContext[Idiom, Naming] (29 abstract members) quill-sql/src/main/scala/zio/quill/context/sql/SqlContext.scala:12
- Fat interface: ArrayEncoding (22 abstract members) quill-sql/src/main/scala/zio/quill/context/sql/encoding/ArrayEncoding.scala:11
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Most significant orphaned file quill-core/src/main/scala/zio/quill/quotation/Parsing.scala:1
- Most significant orphaned file quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:1
- Most significant orphaned file quill-engine/src/main/scala/zio/quill/ast/Ast.scala:1
- Off-boarding risk: anonymized user #1
- Concentrated knowledge decay
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST .github/workflows/auto-approve.yml:7
- Dependabot does not watch npm .github/dependabot.yml:5
- No rollback/health safety
- Scala's null is not held to the type system everywhere
Minor — 13 finding(s)
- Outdated: com.github.ben-manes.caffeine:caffeine
- Outdated: com.lihaoyi:fansi_2.13
- Outdated: com.lihaoyi:pprint_2.13
- Outdated: com.lihaoyi:sourcecode_2.13
- Outdated: dev.zio:zio-json_2.13
- Outdated: dev.zio:zio-logging_2.13
- Outdated: dev.zio:zio-streams_2.13
- Outdated: dev.zio:zio_2.13
- Outdated: org.apache.pekko:pekko-connectors-cassandra_2.13
- Outdated: org.apache.spark:spark-sql_2.13
- Outdated: org.scala-lang.modules:scala-collection-compat_2.13
- Outdated: org.scala-lang.modules:scala-parallel-collections_2.13
- Outdated: org.scalameta:scalafmt-core_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/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-42c012bd62404475a90d48f528fe788c/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-42c012bd62404475a90d48f528fe788c/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 50 | 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/** . | 0 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 27 | 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 1 file(s) — `quill-core/src/main/scala/zio/quill/quotation/Parsing.scala` — so the PII/GDPR sweep did not cover them at all. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |