Executive summary
zio/zio-protoquill falls short of our standard for production, in part because it has pipeline tools referenced by a changeable name. It scores 62 out of 100 and is rated Adequate, and all 42 of its critical findings are security problems.
Security and Compliance, at 58, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is fixing the password or key in the code, worth about 3 points. Stopping the eight pipeline steps that hand secrets to unpinned tools would lift Security and Compliance itself, worth about 2 points.
Nineteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Thirteen settings leave the servers or containers unsafe, and nine secrets can leak from the build pipeline. Pinning each tool to an exact version, correcting the unsafe settings and limiting each secret to its own step would close these risks.
The product code is 18,599 lines, about €47,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
The weakest lenses score close to each other, so improving any of them moves the score.
New since the last survey: 191 findings
- Cyclomatic Complexity · QueryParser.attempt (cyclomatic 28) quill-sql/src/main/scala/zio/quill/parser/Parser.scala
- Cyclomatic Complexity · Dynamic.apply (cyclomatic 21) quill-sql/src/main/scala/zio/quill/context/Particularize.scala
- Cyclomatic Complexity · OptionParser.attempt (cyclomatic 19) quill-sql/src/main/scala/zio/quill/parser/Parser.scala
- Cyclomatic Complexity · PrepareDynamicExecution.processLifts (cyclomatic 18) quill-sql/src/main/scala/zio/quill/context/QueryExecution.scala
- Cyclomatic Complexity · StaticTranslationMacro.processLifts (cyclomatic 18) quill-sql/src/main/scala/zio/quill/context/StaticTranslationMacro.scala
- Cyclomatic Complexity · StaticTranslationMacro.apply (cyclomatic 17) quill-sql/src/main/scala/zio/quill/context/StaticTranslationMacro.scala
- Cognitive Complexity · StaticTranslationMacro.apply (cognitive 36) quill-sql/src/main/scala/zio/quill/context/StaticTranslationMacro.scala
- Cognitive Complexity · ZioJdbcContext.transaction (cognitive 35) quill-jdbc-zio/src/main/scala/zio/quill/context/qzio/ZioJdbcContext.scala
- Cognitive Complexity · Dynamic.apply (cognitive 22) quill-sql/src/main/scala/zio/quill/context/Particularize.scala
- Cognitive Complexity · GenericDecoder.decode (cognitive 20) quill-sql/src/main/scala/zio/quill/generic/GenericDecoder.scala
- Cognitive Complexity · InserteeSchema.summon (cognitive 18) quill-sql/src/main/scala/zio/quill/context/InsertUpdateMacro.scala
- Cognitive Complexity · PrepareDynamicExecution.processLifts (cognitive 17) quill-sql/src/main/scala/zio/quill/context/QueryExecution.scala
- Cognitive Complexity · StaticTranslationMacro.processLifts (cognitive 17) quill-sql/src/main/scala/zio/quill/context/StaticTranslationMacro.scala
- Cognitive Complexity · ElaborateStructure.base (cognitive 16) quill-sql/src/main/scala/zio/quill/generic/ElaborateStructure.scala
- Cognitive Complexity · OptionParser.attempt (cognitive 16) quill-sql/src/main/scala/zio/quill/parser/Parser.scala
- God Classes · MethodTooLong: QueryExecutionBatchIteration.apply quill-sql/src/main/scala/zio/quill/context/QueryExecutionBatchIteration.scala
- God Classes · FileTooLong: parser/Parser.scala quill-sql/src/main/scala/zio/quill/parser/Parser.scala
- God Classes · TooManyMethods: DynamicQuery quill-sql/src/main/scala/zio/quill/DynamicDslModel.scala
- God Classes · FileTooLong: metaprog/Extractors.scala quill-sql/src/main/scala/zio/quill/metaprog/Extractors.scala
- Code Duplication · Duplicated block (69 lines × 2) quill-sql/src/main/scala/zio/quill/context/QueryExecution.scala
- Code Duplication · Duplicated block (9–13 lines × 2) quill-sql/src/main/scala/zio/quill/context/InsertUpdateMacro.scala
- Code Duplication · Duplicated block (13 lines × 2) quill-sql/src/main/scala/zio/quill/generic/ConstructType.scala
- Code Duplication · Duplicated block (12 lines × 2) quill-sql/src/main/scala/zio/quill/context/QueryExecution.scala
- Code Duplication · Duplicated block (10–11 lines × 2) quill-sql/src/main/scala/zio/quill/context/QueryMetaExtractor.scala
- Code Duplication · Duplicated block (8 lines × 2) quill-sql/src/main/scala/zio/quill/parser/ParserHelpers.scala
- Code Duplication · Duplicated block (5 lines × 2) quill-cassandra/src/main/scala/zio/quill/context/cassandra/encoding/UdtEncodingMacro.scala
- Code Duplication · Duplicated block (5 lines × 2) quill-cassandra/src/main/scala/zio/quill/context/cassandra/encoding/UdtEncodingMacro.scala
- Code Duplication · Duplicated block (5 lines × 2) quill-sql/src/main/scala/zio/quill/context/QueryExecutionBatch.scala
- Code Duplication · Duplicated block (6 lines × 2) quill-jdbc-zio/src/main/scala/zio/quill/context/ZioJdbc.scala
- Code Duplication · Duplicated block (7 lines × 3) quill-sql/src/main/scala/zio/quill/metaprog/Extractors.scala
- Code Duplication · Duplicated block (5 lines × 2) quill-sql/src/main/scala/zio/quill/generic/GenericDecoder.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/zio/quill/InsertAdvancedSpec.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/zio/quill/InsertAdvancedSpec.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/zio/quill/InsertAdvancedSpec.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/zio/quill/InsertAdvancedSpec.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/zio/quill/InsertAdvancedSpec.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/zio/quill/InsertAdvancedSpec.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/zio/quill/InsertAdvancedSpec.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/zio/quill/ported/sqlidiomspec/QuerySpec.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/zio/quill/ported/sqlidiomspec/QuerySpec.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/zio/quill/ported/quotationspec/ActionTest.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/zio/quill/ported/quotationspec/ActionTest.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/zio/quill/ported/quotationspec/ActionTest.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/zio/quill/ported/quotationspec/IdentAndPropertyTest.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/zio/quill/ported/quotationspec/OptionOperationTest.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/zio/quill/ported/quotationspec/QueryTest.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/zio/quill/ported/quotationspec/QueryTest.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/zio/quill/ported/quotationspec/ValueTest.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/zio/quill/examples/TypeclassUsecase_Repetitive.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/zio/quill/context/sql/idiom/SqlIdiomOptionCompareSpec.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/zio/quill/context/sql/idiom/SqlIdiomOptionCompareSpec.scala
- Explicit Debt · TodoComment quill-sql/src/test/scala/zio/quill/BatchActionMultiTest.scala
- Explicit Debt · TodoComment quill-sql/src/test/scala/zio/quill/BatchActionTest.scala
- Explicit Debt · TodoComment quill-sql/src/test/scala/zio/quill/GenericDecoderCoproductTestAdditional.scala
- Explicit Debt · TodoComment quill-sql/src/test/scala/zio/quill/QuerySchemaTest.scala
- Explicit Debt · TodoComment quill-sql/src/test/scala/zio/quill/QuotationTest.scala
- Explicit Debt · TodoComment quill-sql/src/test/scala/zio/quill/quat/QuatSpec.scala
- Explicit Debt · TodoComment quill-sql/src/test/scala/zio/quill/quat/QuatSpec.scala
- Explicit Debt · TodoComment quill-sql/src/test/scala/zio/quill/quat/QuatSpec.scala
- Explicit Debt · TodoComment quill-sql/src/test/scala/zio/quill/quat/QuatSpec.scala
- Explicit Debt · TodoComment quill-sql/src/test/scala/zio/quill/quat/QuatSpec.scala
- Explicit Debt · TodoComment quill-sql/src/test/scala/zio/quill/quat/QuatSpec.scala
- Explicit Debt · TodoComment quill-sql/src/test/scala/zio/quill/quat/QuatSpec.scala
- Explicit Debt · TodoComment quill-sql/src/test/scala/zio/quill/quat/QuatSpec.scala
- Explicit Debt · TodoComment quill-sql/src/test/scala/zio/quill/quat/QuatSpec.scala
- Explicit Debt · TodoComment quill-sql/src/test/scala/zio/quill/quat/QuatSpec.scala
- Explicit Debt · TodoComment quill-sql/src/test/scala/zio/quill/quat/QuatSpec.scala
- Explicit Debt · TodoComment quill-sql/src/test/scala/zio/quill/idiom/LoadNamingTest.scala
- Explicit Debt · TodoComment quill-sql/src/test/scala/zio/quill/context/sql/DepartmentsSpec.scala
- Explicit Debt · TodoComment quill-sql/src/test/scala/zio/quill/context/sql/EncodingSpec.scala
- Explicit Debt · TodoComment quill-sql/src/test/scala/zio/quill/context/sql/PeopleSpec.scala
- Explicit Debt · TodoComment quill-sql/src/test/scala/zio/quill/context/sql/PeopleSpec.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/DslModel.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/DslModel.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/DslModel.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/DslModel.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/DynamicDslModel.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/DynamicDslModel.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/util/CommonExtensions.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/util/GetTraces.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/util/GroupByOps.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/util/GroupByOps.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/util/LoadObject.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/util/LoadObject.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/util/LoadObject.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/metaprog/SummonTraceTypeUse.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/util/SummonMac.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/util/UseSummonMac.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/quat/QuatMaking.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/quat/QuatMaking.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/quat/QuatMaking.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/quat/QuatMaking.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/parser/Parser.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/parser/Parser.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/parser/Parser.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/parser/Parser.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/parser/Parser.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/parser/Parser.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/parser/Parser.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/zio/quill/parser/Parser.scala
Fixed since the last survey: 190 findings
- Cyclomatic Complexity · QueryParser.attempt (cyclomatic 28) quill-sql/src/main/scala/io/getquill/parser/Parser.scala
- Cyclomatic Complexity · Dynamic.apply (cyclomatic 21) quill-sql/src/main/scala/io/getquill/context/Particularize.scala
- Cyclomatic Complexity · OptionParser.attempt (cyclomatic 19) quill-sql/src/main/scala/io/getquill/parser/Parser.scala
- Cyclomatic Complexity · PrepareDynamicExecution.processLifts (cyclomatic 18) quill-sql/src/main/scala/io/getquill/context/QueryExecution.scala
- Cyclomatic Complexity · StaticTranslationMacro.processLifts (cyclomatic 18) quill-sql/src/main/scala/io/getquill/context/StaticTranslationMacro.scala
- Cyclomatic Complexity · StaticTranslationMacro.apply (cyclomatic 17) quill-sql/src/main/scala/io/getquill/context/StaticTranslationMacro.scala
- Cognitive Complexity · StaticTranslationMacro.apply (cognitive 36) quill-sql/src/main/scala/io/getquill/context/StaticTranslationMacro.scala
- Cognitive Complexity · ZioJdbcContext.transaction (cognitive 35) quill-jdbc-zio/src/main/scala/io/getquill/context/qzio/ZioJdbcContext.scala
- Cognitive Complexity · Dynamic.apply (cognitive 22) quill-sql/src/main/scala/io/getquill/context/Particularize.scala
- Cognitive Complexity · GenericDecoder.decode (cognitive 20) quill-sql/src/main/scala/io/getquill/generic/GenericDecoder.scala
- Cognitive Complexity · InserteeSchema.summon (cognitive 18) quill-sql/src/main/scala/io/getquill/context/InsertUpdateMacro.scala
- Cognitive Complexity · PrepareDynamicExecution.processLifts (cognitive 17) quill-sql/src/main/scala/io/getquill/context/QueryExecution.scala
- Cognitive Complexity · StaticTranslationMacro.processLifts (cognitive 17) quill-sql/src/main/scala/io/getquill/context/StaticTranslationMacro.scala
- Cognitive Complexity · ElaborateStructure.base (cognitive 16) quill-sql/src/main/scala/io/getquill/generic/ElaborateStructure.scala
- Cognitive Complexity · OptionParser.attempt (cognitive 16) quill-sql/src/main/scala/io/getquill/parser/Parser.scala
- God Classes · MethodTooLong: QueryExecutionBatchIteration.apply quill-sql/src/main/scala/io/getquill/context/QueryExecutionBatchIteration.scala
- God Classes · FileTooLong: parser/Parser.scala quill-sql/src/main/scala/io/getquill/parser/Parser.scala
- God Classes · TooManyMethods: DynamicQuery quill-sql/src/main/scala/io/getquill/DynamicDslModel.scala
- Code Duplication · Duplicated block (69 lines × 2) quill-sql/src/main/scala/io/getquill/context/QueryExecution.scala
- Code Duplication · Duplicated block (9–13 lines × 2) quill-sql/src/main/scala/io/getquill/context/InsertUpdateMacro.scala
- Code Duplication · Duplicated block (13 lines × 2) quill-sql/src/main/scala/io/getquill/generic/ConstructType.scala
- Code Duplication · Duplicated block (12 lines × 2) quill-sql/src/main/scala/io/getquill/context/QueryExecution.scala
- Code Duplication · Duplicated block (10–11 lines × 2) quill-sql/src/main/scala/io/getquill/context/QueryMetaExtractor.scala
- Code Duplication · Duplicated block (8 lines × 2) quill-sql/src/main/scala/io/getquill/parser/ParserHelpers.scala
- Code Duplication · Duplicated block (5 lines × 2) quill-cassandra/src/main/scala/io/getquill/context/cassandra/encoding/UdtEncodingMacro.scala
- Code Duplication · Duplicated block (5 lines × 2) quill-cassandra/src/main/scala/io/getquill/context/cassandra/encoding/UdtEncodingMacro.scala
- Code Duplication · Duplicated block (5 lines × 2) quill-sql/src/main/scala/io/getquill/context/QueryExecutionBatch.scala
- Code Duplication · Duplicated block (6 lines × 2) quill-jdbc-zio/src/main/scala/io/getquill/context/ZioJdbc.scala
- Code Duplication · Duplicated block (7 lines × 3) quill-sql/src/main/scala/io/getquill/metaprog/Extractors.scala
- Code Duplication · Duplicated block (5 lines × 2) quill-sql/src/main/scala/io/getquill/generic/GenericDecoder.scala
- Explicit Debt · TodoComment quill-cassandra-zio/src/main/scala/io/getquill/CassandraZioContext.scala
- Explicit Debt · TodoComment quill-cassandra-zio/src/main/scala/io/getquill/CassandraZioContext.scala
- Explicit Debt · TodoComment quill-cassandra/src/main/scala/io/getquill/UdtMetaDsl.scala
- Explicit Debt · TodoComment quill-cassandra/src/main/scala/io/getquill/UdtMetaDsl.scala
- Explicit Debt · TodoComment quill-cassandra/src/main/scala/io/getquill/context/cassandra/encoding/UdtEncodingMacro.scala
- Explicit Debt · TodoComment quill-cassandra/src/main/scala/io/getquill/context/cassandra/encoding/UdtEncodingMacro.scala
- Explicit Debt · TodoComment quill-cassandra/src/main/scala/io/getquill/context/cassandra/UdtMetaDslMacro.scala
- Explicit Debt · TodoComment quill-cassandra/src/main/scala/io/getquill/context/cassandra/encoding/UdtEncodingMacro.scala
- Explicit Debt · TodoComment quill-cassandra/src/main/scala/io/getquill/context/cassandra/encoding/UdtEncodingMacro.scala
- Explicit Debt · TodoComment quill-cassandra/src/main/scala/io/getquill/context/cassandra/encoding/UdtEncodingMacro.scala
- Explicit Debt · TodoComment quill-cassandra/src/main/scala/io/getquill/context/cassandra/encoding/CollectionEncoders.scala
- Explicit Debt · TodoComment quill-cassandra/src/main/scala/io/getquill/context/cassandra/encoding/CollectionDecoders.scala
- Explicit Debt · TodoComment quill-cassandra/src/main/scala/io/getquill/context/cassandra/encoding/CollectionDecoders.scala
- Explicit Debt · TodoComment quill-jdbc-zio/src/main/scala/io/getquill/context/qzio/ZioJdbcUnderlyingContext.scala
- Explicit Debt · TodoComment quill-jdbc-zio/src/test/scala/io/getquill/sqlserver/PrepareJdbcSpec.scala
- Explicit Debt · TodoComment quill-jdbc/src/main/scala/io/getquill/context/jdbc/ResultSetExtractor.scala
- Explicit Debt · TodoComment quill-jdbc/src/test/scala/io/getquill/context/jdbc/postgres/PeopleJdbcSpec.scala
- Explicit Debt · TodoComment quill-jdbc/src/test/scala/io/getquill/context/jdbc/postgres/JdbcContextSpec.scala
- Explicit Debt · HackComment quill-jdbc/src/test/scala/io/getquill/context/jdbc/sqlserver/OptionJdbcSpec.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/io/getquill/InsertAdvancedSpec.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/io/getquill/InsertAdvancedSpec.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/io/getquill/InsertAdvancedSpec.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/io/getquill/InsertAdvancedSpec.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/io/getquill/InsertAdvancedSpec.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/io/getquill/InsertAdvancedSpec.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/io/getquill/InsertAdvancedSpec.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/io/getquill/context/sql/idiom/SqlIdiomOptionCompareSpec.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/io/getquill/context/sql/idiom/SqlIdiomOptionCompareSpec.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/io/getquill/examples/TypeclassUsecase_Repetitive.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/io/getquill/ported/quotationspec/ValueTest.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/io/getquill/ported/quotationspec/QueryTest.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/io/getquill/ported/quotationspec/QueryTest.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/io/getquill/ported/quotationspec/OptionOperationTest.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/io/getquill/ported/quotationspec/IdentAndPropertyTest.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/io/getquill/ported/quotationspec/ActionTest.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/io/getquill/ported/quotationspec/ActionTest.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/io/getquill/ported/quotationspec/ActionTest.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/io/getquill/ported/sqlidiomspec/QuerySpec.scala
- Explicit Debt · TodoComment quill-sql-tests/src/test/scala/io/getquill/ported/sqlidiomspec/QuerySpec.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/DynamicDslModel.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/DynamicDslModel.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/DslModel.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/DslModel.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/DslModel.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/DslModel.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/context/StaticTranslationMacro.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/context/QueryExecution.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/context/StaticTranslationMacro.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/context/StaticSpliceMacro.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/context/StaticSpliceMacro.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/context/StaticSpliceMacro.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/context/StaticSpliceMacro.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/context/SchemaMetaMacro.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/context/QuoteMacro.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/context/QuoteMacro.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/context/QueryMetaExtractor.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/context/QueryMetaExtractor.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/context/QueryMacro.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/context/QueryExecutionBatch.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/context/QueryExecutionBatch.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/context/QueryExecutionBatch.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/context/QueryExecutionBatch.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/context/QueryExecutionBatch.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/context/QueryExecution.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/context/QueryExecution.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/context/QueryExecution.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/context/QueryExecution.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/context/QueryExecution.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/context/Particularize.scala
- Explicit Debt · TodoComment quill-sql/src/main/scala/io/getquill/context/LiftMacro.scala
Rebuild cost: about €47,000 · Estimate
| Cost to rebuild | €16,000 to €79,000, for 262 to 830 hours of work, about 0.3 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 62. 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 | Small: 18,599 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 parser.engine | 2 quat | 3 util | 4 context.Execution | 5 context.QueryExecutionBatchModel | 6 parser.ParserHelpers | 7 generic | 8 parser | 9 context.cassandra.encoding | 10 context.mirror | 11 metaprog | 12 parser.Lifters | 13 context | 14 MirrorContextBase | 15 context.cassandra | 16 context.sql | 17 context.jdbc | 18 context.json | 19 context.qzio | 20 zio.quill | 21 H2ZioJdbcContext | 22 MysqlZioJdbcContext | 23 OracleZioJdbcContext | 24 PostgresZioJdbcContext | 25 SqlServerZioJdbcContext | 26 SqliteZioJdbcContext | 27 context.BatchStatic | 28 context.InsertUpdateMacro | 29 context.Particularize | 30 context.QueryExecution | 31 context.QueryExecutionBatch | 32 context.QueryExecutionBatchDynamic.PlanterKind | 33 context.cassandra.encoding.UdtDecodingMacro | 34 context.cassandra.encoding.UdtEncodingMacro | 35 doobie | 36 jdbczio | 37 metaprog.QuotationLotExpr | 38 context.BatchStatic.PlanterKind | 39 context.InsertUpdateMacro.Pipeline | 40 jdbczio.Quill |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 parser.engine | ||||||||||||||||||||||||||||||||||||||||
| 2 quat | ||||||||||||||||||||||||||||||||||||||||
| 3 util | ||||||||||||||||||||||||||||||||||||||||
| 4 context.Execution | 2 | |||||||||||||||||||||||||||||||||||||||
| 5 context.QueryExecutionBatchModel | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 parser.ParserHelpers | 7 | 4 | ||||||||||||||||||||||||||||||||||||||
| 7 generic | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 8 parser | 24 | 3 | 20 | |||||||||||||||||||||||||||||||||||||
| 9 context.cassandra.encoding | 4 | 6 | ||||||||||||||||||||||||||||||||||||||
| 10 context.mirror | 3 | |||||||||||||||||||||||||||||||||||||||
| 11 metaprog | 1 | 3 | 1 | 10 | ||||||||||||||||||||||||||||||||||||
| 12 parser.Lifters | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 context | 1 | 4 | 1 | 2 | 6 | 5 | 28 | |||||||||||||||||||||||||||||||||
| 14 MirrorContextBase | 1 | 7 | ||||||||||||||||||||||||||||||||||||||
| 15 context.cassandra | 5 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 context.sql | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 context.jdbc | 3 | 9 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 18 context.json | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 19 context.qzio | 12 | 2 | 6 | |||||||||||||||||||||||||||||||||||||
| 20 zio.quill | 4 | 2 | 3 | 14 | 2 | 1 | 18 | 1 | 13 | |||||||||||||||||||||||||||||||
| 21 H2ZioJdbcContext | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 MysqlZioJdbcContext | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 OracleZioJdbcContext | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 PostgresZioJdbcContext | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 SqlServerZioJdbcContext | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 SqliteZioJdbcContext | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 context.BatchStatic | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 context.InsertUpdateMacro | 2 | 4 | ||||||||||||||||||||||||||||||||||||||
| 29 context.Particularize | 3 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 30 context.QueryExecution | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 31 context.QueryExecutionBatch | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 context.QueryExecutionBatchDynamic.PlanterKind | 3 | |||||||||||||||||||||||||||||||||||||||
| 33 context.cassandra.encoding.UdtDecodingMacro | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 context.cassandra.encoding.UdtEncodingMacro | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 doobie | 3 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 36 jdbczio | 3 | 1 | 3 | 3 | ||||||||||||||||||||||||||||||||||||
| 37 metaprog.QuotationLotExpr | 5 | 4 | ||||||||||||||||||||||||||||||||||||||
| 38 context.BatchStatic.PlanterKind | 3 | 3 | ||||||||||||||||||||||||||||||||||||||
| 39 context.InsertUpdateMacro.Pipeline | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 40 jdbczio.Quill | 7 | 1 | 7 |
4→13 context.Execution uses context part of a loop✕
- Connections
- 2 pairs of types, where a type in context.Execution uses a type in context.
- The types involved
zio.quill.context.Execution.MakeExtractor→zio.quill.context.Extractionzio.quill.context.Execution.MakeExtractor→zio.quill.context.StaticState
- Direction
- context.Execution uses context, so a change to context can break context.Execution, while a change to context.Execution 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.
5→20 context.QueryExecutionBatchModel uses zio.quill part of a loop✕
- Connections
- 1 pair of types, where a type in context.QueryExecutionBatchModel uses a type in zio.quill.
- The types involved
zio.quill.context.QueryExecutionBatchModel.SingleEntityLifts→zio.quill.Planter
- Direction
- context.QueryExecutionBatchModel uses zio.quill, so a change to zio.quill can break context.QueryExecutionBatchModel, while a change to context.QueryExecutionBatchModel 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→1 parser.ParserHelpers uses parser.engine✕
- Connections
- 7 pairs of types, where a type in parser.ParserHelpers uses a type in parser.engine.
- The types involved
zio.quill.parser.ParserHelpers.Assignments→zio.quill.parser.engine.Parserzio.quill.parser.ParserHelpers.ComparisonTechniques→zio.quill.parser.engine.Historyzio.quill.parser.ParserHelpers.ComparisonTechniques→zio.quill.parser.engine.Parserzio.quill.parser.ParserHelpers.PatternMatchingValues→zio.quill.parser.engine.Historyzio.quill.parser.ParserHelpers.PatternMatchingValues→zio.quill.parser.engine.Parserzio.quill.parser.ParserHelpers.PropertyAliases→zio.quill.parser.engine.Parserzio.quill.parser.ParserHelpers.PropertyParser→zio.quill.parser.engine.Parser
- Direction
- parser.ParserHelpers uses parser.engine, so a change to parser.engine can break parser.ParserHelpers, while a change to parser.ParserHelpers can't break parser.engine.
- Position
- Below the diagonal: parser.ParserHelpers uses a module listed above it, which is the healthy direction.
6→2 parser.ParserHelpers uses quat✕
- Connections
- 4 pairs of types, where a type in parser.ParserHelpers uses a type in quat.
- The types involved
zio.quill.parser.ParserHelpers.Helpers→zio.quill.quat.QuatMakingzio.quill.parser.ParserHelpers.Helpers→zio.quill.quat.QuatMakingBasezio.quill.parser.ParserHelpers.Idents→zio.quill.quat.QuatMakingzio.quill.parser.ParserHelpers.PatternMatchingValues→zio.quill.quat.QuatMaking
- Direction
- parser.ParserHelpers uses quat, so a change to quat can break parser.ParserHelpers, while a change to parser.ParserHelpers can't break quat.
- Position
- Below the diagonal: parser.ParserHelpers uses a module listed above it, which is the healthy direction.
7→4 generic uses context.Execution✕
- Connections
- 1 pair of types, where a type in generic uses a type in context.Execution.
- The types involved
zio.quill.generic.ElaborateTrivial→zio.quill.context.Execution.ElaborationBehavior
- Direction
- generic uses context.Execution, so a change to context.Execution can break generic, while a change to generic can't break context.Execution.
- Position
- Below the diagonal: generic uses a module listed above it, which is the healthy direction.
7→20 generic uses zio.quill part of a loop✕
- Connections
- 1 pair of types, where a type in generic uses a type in zio.quill.
- The types involved
zio.quill.generic.GenericEncoderWithStringFallback→zio.quill.FromString
- Direction
- generic uses zio.quill, so a change to zio.quill can break generic, while a change to generic 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→1 parser uses parser.engine✕
- Connections
- 24 pairs of types, where a type in parser uses a type in parser.engine.
- The types involved
zio.quill.parser.ActionParser→zio.quill.parser.engine.Parserzio.quill.parser.ArbitraryTupleBlockParser→zio.quill.parser.engine.Parserzio.quill.parser.BatchActionParser→zio.quill.parser.engine.Parserzio.quill.parser.BlockParser→zio.quill.parser.engine.Parserzio.quill.parser.CasePatMatchParser→zio.quill.parser.engine.Parserzio.quill.parser.ComplexValueParser→zio.quill.parser.engine.Parserzio.quill.parser.ExtrasParser→zio.quill.parser.engine.Parserzio.quill.parser.FunctionApplyParser→zio.quill.parser.engine.Parserzio.quill.parser.FunctionParser→zio.quill.parser.engine.Parserzio.quill.parser.GenericExpressionsParser→zio.quill.parser.engine.Parserzio.quill.parser.IfElseParser→zio.quill.parser.engine.Parserzio.quill.parser.InfixParser→zio.quill.parser.engine.Historyzio.quill.parser.InfixParser→zio.quill.parser.engine.Parserzio.quill.parser.OperationsParser→zio.quill.parser.engine.Parserzio.quill.parser.OptionParser→zio.quill.parser.engine.Parserzio.quill.parser.OrderingParser→zio.quill.parser.engine.Historyzio.quill.parser.OrderingParser→zio.quill.parser.engine.Parserzio.quill.parser.QueryParser→zio.quill.parser.engine.Parserzio.quill.parser.QueryScalarsParser→zio.quill.parser.engine.Parserzio.quill.parser.QuotationParser→zio.quill.parser.engine.Parserzio.quill.parser.SetOperationsParser→zio.quill.parser.engine.Parserzio.quill.parser.TraversableOperationParser→zio.quill.parser.engine.Parserzio.quill.parser.ValParser→zio.quill.parser.engine.Parserzio.quill.parser.ValueParser→zio.quill.parser.engine.Parser
- Direction
- parser uses parser.engine, so a change to parser.engine can break parser, while a change to parser can't break parser.engine.
- Position
- Below the diagonal: parser uses a module listed above it, which is the healthy direction.
8→2 parser uses quat✕
- Connections
- 3 pairs of types, where a type in parser uses a type in quat.
- The types involved
zio.quill.parser.ComplexValueParser→zio.quill.quat.QuatMakingzio.quill.parser.OperationsParser→zio.quill.quat.QuatMakingzio.quill.parser.ValueParser→zio.quill.quat.QuatMaking
- Direction
- parser uses quat, so a change to quat can break parser, while a change to parser can't break quat.
- Position
- Below the diagonal: parser uses a module listed above it, which is the healthy direction.
8→6 parser uses parser.ParserHelpers✕
- Connections
- 20 pairs of types, where a type in parser uses a type in parser.ParserHelpers.
- The types involved
zio.quill.parser.ActionParser→zio.quill.parser.ParserHelpers.Assignmentszio.quill.parser.ActionParser→zio.quill.parser.ParserHelpers.PropertyParserzio.quill.parser.ArbitraryTupleBlockParser→zio.quill.parser.ParserHelpers.PatternMatchingValueszio.quill.parser.BatchActionParser→zio.quill.parser.ParserHelpers.Assignmentszio.quill.parser.BlockParser→zio.quill.parser.ParserHelpers.PatternMatchingValueszio.quill.parser.CasePatMatchParser→zio.quill.parser.ParserHelpers.PatternMatchingValueszio.quill.parser.ComplexValueParser→zio.quill.parser.ParserHelpers.Helperszio.quill.parser.ExtrasParser→zio.quill.parser.ParserHelpers.ComparisonTechniqueszio.quill.parser.FunctionParser→zio.quill.parser.ParserHelpers.Helperszio.quill.parser.GenericExpressionsParser→zio.quill.parser.ParserHelpers.PropertyParserzio.quill.parser.InfixParser→zio.quill.parser.ParserHelpers.Assignmentszio.quill.parser.OperationsParser→zio.quill.parser.ParserHelpers.ComparisonTechniqueszio.quill.parser.OptionParser→zio.quill.parser.ParserHelpers.Helperszio.quill.parser.OrderingParser→zio.quill.parser.ParserHelpers.PatternMatchingValueszio.quill.parser.QueryParser→zio.quill.parser.ParserHelpers.Helperszio.quill.parser.QueryParser→zio.quill.parser.ParserHelpers.PropertyAliaseszio.quill.parser.QueryScalarsParser→zio.quill.parser.ParserHelpers.PropertyAliaseszio.quill.parser.SetOperationsParser→zio.quill.parser.ParserHelpers.PropertyAliaseszio.quill.parser.TraversableOperationParser→zio.quill.parser.ParserHelpers.PatternMatchingValueszio.quill.parser.ValParser→zio.quill.parser.ParserHelpers.PatternMatchingValues
- Direction
- parser uses parser.ParserHelpers, so a change to parser.ParserHelpers can break parser, while a change to parser can't break parser.ParserHelpers.
- Position
- Below the diagonal: parser uses a module listed above it, which is the healthy direction.
9→7 context.cassandra.encoding uses generic✕
- Connections
- 4 pairs of types, where a type in context.cassandra.encoding uses a type in generic.
- The types involved
zio.quill.context.cassandra.encoding.CollectionDecoders→zio.quill.generic.EncodingDslzio.quill.context.cassandra.encoding.CollectionEncoders→zio.quill.generic.EncodingDslzio.quill.context.cassandra.encoding.Decoders→zio.quill.generic.EncodingDslzio.quill.context.cassandra.encoding.Encoders→zio.quill.generic.EncodingDsl
- Direction
- context.cassandra.encoding uses generic, so a change to generic can break context.cassandra.encoding, while a change to context.cassandra.encoding can't break generic.
- Position
- Below the diagonal: context.cassandra.encoding uses a module listed above it, which is the healthy direction.
9→15 context.cassandra.encoding uses context.cassandra part of a loop✕
- Connections
- 6 pairs of types, where a type in context.cassandra.encoding uses a type in context.cassandra.
- The types involved
zio.quill.context.cassandra.encoding.CollectionDecoders→zio.quill.context.cassandra.CassandraRowContextzio.quill.context.cassandra.encoding.CollectionEncoders→zio.quill.context.cassandra.CassandraRowContextzio.quill.context.cassandra.encoding.Decoders→zio.quill.context.cassandra.CassandraRowContextzio.quill.context.cassandra.encoding.Encoders→zio.quill.context.cassandra.CassandraRowContextzio.quill.context.cassandra.encoding.UdtDecoding→zio.quill.context.cassandra.CassandraRowContextzio.quill.context.cassandra.encoding.UdtEncoding→zio.quill.context.cassandra.CassandraRowContext
- Direction
- context.cassandra.encoding uses context.cassandra, so a change to context.cassandra can break context.cassandra.encoding, while a change to context.cassandra.encoding can't break context.cassandra.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→7 context.mirror uses generic✕
- Connections
- 3 pairs of types, where a type in context.mirror uses a type in generic.
- The types involved
zio.quill.context.mirror.ArrayMirrorEncoding→zio.quill.generic.ArrayEncodingzio.quill.context.mirror.MirrorDecoders→zio.quill.generic.EncodingDslzio.quill.context.mirror.MirrorEncoders→zio.quill.generic.EncodingDsl
- Direction
- context.mirror uses generic, so a change to generic can break context.mirror, while a change to context.mirror can't break generic.
- Position
- Below the diagonal: context.mirror uses a module listed above it, which is the healthy direction.
11→3 metaprog uses util✕
- Connections
- 1 pair of types, where a type in metaprog uses a type in util.
- The types involved
zio.quill.metaprog.TranspileConfigLiftable→zio.quill.util.TraceConfig
- Direction
- metaprog uses util, so a change to util can break metaprog, while a change to metaprog can't break util.
- Position
- Below the diagonal: metaprog uses a module listed above it, which is the healthy direction.
11→7 metaprog uses generic✕
- Connections
- 3 pairs of types, where a type in metaprog uses a type in generic.
- The types involved
zio.quill.metaprog.EagerListPlanterExpr→zio.quill.generic.GenericEncoderzio.quill.metaprog.EagerPlanterExpr→zio.quill.generic.GenericEncoderzio.quill.metaprog.InjectableEagerPlanterExpr→zio.quill.generic.GenericEncoder
- Direction
- metaprog uses generic, so a change to generic can break metaprog, while a change to metaprog can't break generic.
- Position
- Below the diagonal: metaprog uses a module listed above it, which is the healthy direction.
11→8 metaprog uses parser✕
- Connections
- 1 pair of types, where a type in metaprog uses a type in parser.
- The types involved
zio.quill.metaprog.SummonParser→zio.quill.parser.ParserFactory
- Direction
- metaprog uses parser, so a change to parser can break metaprog, while a change to metaprog can't break parser.
- Position
- Below the diagonal: metaprog uses a module listed above it, which is the healthy direction.
11→20 metaprog uses zio.quill part of a loop✕
- Connections
- 10 pairs of types, where a type in metaprog uses a type in zio.quill.
- The types involved
zio.quill.metaprog.EagerEntitiesPlanterExpr→zio.quill.EagerEntitiesPlanterzio.quill.metaprog.EagerEntitiesPlanterExpr→zio.quill.InjectableEagerPlanterzio.quill.metaprog.EagerListPlanterExpr→zio.quill.EagerListPlanterzio.quill.metaprog.EagerPlanterExpr→zio.quill.EagerPlanterzio.quill.metaprog.InjectableEagerPlanterExpr→zio.quill.EagerPlanterzio.quill.metaprog.InjectableEagerPlanterExpr→zio.quill.InjectableEagerPlanterzio.quill.metaprog.LazyPlanterExpr→zio.quill.LazyPlanterzio.quill.metaprog.PlanterExpr→zio.quill.Planterzio.quill.metaprog.QuotedExpr→zio.quill.Planterzio.quill.metaprog.QuotedExpr→zio.quill.QuotationVase
- Direction
- metaprog uses zio.quill, so a change to zio.quill can break metaprog, while a change to metaprog 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 parser.Lifters uses parser✕
- Connections
- 1 pair of types, where a type in parser.Lifters uses a type in parser.
- The types involved
zio.quill.parser.Lifters.Proxy→zio.quill.parser.Lifter
- Direction
- parser.Lifters uses parser, so a change to parser can break parser.Lifters, while a change to parser.Lifters can't break parser.
- Position
- Below the diagonal: parser.Lifters uses a module listed above it, which is the healthy direction.
13→1 context uses parser.engine✕
- Connections
- 1 pair of types, where a type in context uses a type in parser.engine.
- The types involved
zio.quill.context.QuoteMacro→zio.quill.parser.engine.Parser
- Direction
- context uses parser.engine, so a change to parser.engine can break context, while a change to context can't break parser.engine.
- Position
- Below the diagonal: context uses a module listed above it, which is the healthy direction.
13→3 context uses util✕
- Connections
- 4 pairs of types, where a type in context uses a type in util.
- The types involved
zio.quill.context.BatchStatic→zio.quill.util.TraceConfigzio.quill.context.PrepareBatchComponents→zio.quill.util.TraceConfigzio.quill.context.QueryExecutionBatchDynamic→zio.quill.util.TraceConfigzio.quill.context.QueryExecutionBatchIteration→zio.quill.util.TraceConfig
- Direction
- context uses util, so a change to util can break context, while a change to context can't break util.
- Position
- Below the diagonal: context uses a module listed above it, which is the healthy direction.
13→4 context uses context.Execution✕
- Connections
- 1 pair of types, where a type in context uses a type in context.Execution.
- The types involved
zio.quill.context.StaticTranslationMacro→zio.quill.context.Execution.ElaborationBehavior
- Direction
- context uses context.Execution, so a change to context.Execution can break context, while a change to context can't break context.Execution.
- Position
- Below the diagonal: context uses a module listed above it, which is the healthy direction.
13→5 context uses context.QueryExecutionBatchModel✕
- Connections
- 2 pairs of types, where a type in context uses a type in context.QueryExecutionBatchModel.
- The types involved
zio.quill.context.QueryExecutionBatchIteration→zio.quill.context.QueryExecutionBatchModel.BatchingBehaviorzio.quill.context.QueryExecutionBatchIteration→zio.quill.context.QueryExecutionBatchModel.SingleEntityLifts
- Direction
- context uses context.QueryExecutionBatchModel, so a change to context.QueryExecutionBatchModel can break context, while a change to context can't break context.QueryExecutionBatchModel.
- Position
- Below the diagonal: context uses a module listed above it, which is the healthy direction.
13→7 context uses generic✕
- Connections
- 6 pairs of types, where a type in context uses a type in generic.
- The types involved
zio.quill.context.Context→zio.quill.generic.EncodingDslzio.quill.context.Context→zio.quill.generic.GenericDecoderzio.quill.context.Execution→zio.quill.generic.DecodingTypezio.quill.context.Execution→zio.quill.generic.GenericDecoderzio.quill.context.SummonDecoderMacro→zio.quill.generic.DecodingTypezio.quill.context.SummonDecoderMacro→zio.quill.generic.GenericDecoder
- Direction
- context uses generic, so a change to generic can break context, while a change to context can't break generic.
- Position
- Below the diagonal: context uses a module listed above it, which is the healthy direction.
13→11 context uses metaprog✕
- Connections
- 5 pairs of types, where a type in context uses a type in metaprog.
- The types involved
zio.quill.context.BatchStatic→zio.quill.metaprog.PlanterExprzio.quill.context.QueryMetaExtractor→zio.quill.metaprog.PlanterExprzio.quill.context.QueryMetaExtractor→zio.quill.metaprog.QuotedExprzio.quill.context.StaticState→zio.quill.metaprog.PlanterExprzio.quill.context.StaticTranslationMacro→zio.quill.metaprog.PlanterExpr
- Direction
- context uses metaprog, so a change to metaprog can break context, while a change to context can't break metaprog.
- Position
- Below the diagonal: context uses a module listed above it, which is the healthy direction.
13→20 context uses zio.quill part of a loop✕
- Connections
- 28 pairs of types, where a type in context uses a type in zio.quill. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
zio.quill.context.ContextTranslateMacro→zio.quill.Quotedzio.quill.context.ContextVerbPrepare→zio.quill.Quotedzio.quill.context.ContextVerbStream→zio.quill.Quotedzio.quill.context.InsertMetaMacro→zio.quill.InsertMetazio.quill.context.InsertUpdateMacro→zio.quill.EntityQueryzio.quill.context.LiftMacro→zio.quill.CaseClassLiftzio.quill.context.LiftsExtractor→zio.quill.Planterzio.quill.context.PrepareDynamicExecution→zio.quill.Planterzio.quill.context.PrepareDynamicExecution→zio.quill.Quotedzio.quill.context.QueryExecution→zio.quill.OuterSelectWrapzio.quill.context.QueryExecution→zio.quill.Quotedzio.quill.context.QueryExecutionBatch→zio.quill.Quotedzio.quill.context.QueryExecutionBatchDynamic→zio.quill.Planterzio.quill.context.QueryExecutionBatchDynamic→zio.quill.Quotedzio.quill.context.QueryExecutionBatchIteration→zio.quill.InjectableEagerPlanterzio.quill.context.QueryExecutionBatchIteration→zio.quill.Planterzio.quill.context.QueryMacro→zio.quill.EntityQueryzio.quill.context.QueryMetaExtractor→zio.quill.QueryMetazio.quill.context.QueryMetaExtractor→zio.quill.Quotedzio.quill.context.QueryMetaMacro→zio.quill.QueryMetazio.quill.context.QueryMetaMacro→zio.quill.Quotedzio.quill.context.QuerySingleAsQuery→zio.quill.Quotedzio.quill.context.QuoteMacro→zio.quill.Quotedzio.quill.context.RunDynamicExecution→zio.quill.Quotedzio.quill.context.SchemaMetaMacro→zio.quill.SchemaMeta
- 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.
14→10 MirrorContextBase uses context.mirror✕
- Connections
- 1 pair of types, where a type in MirrorContextBase uses a type in context.mirror.
- The types involved
zio.quill.MirrorContextBase.MirrorNullChecker→zio.quill.context.mirror.Row
- Direction
- MirrorContextBase uses context.mirror, so a change to context.mirror can break MirrorContextBase, while a change to MirrorContextBase can't break context.mirror.
- Position
- Below the diagonal: MirrorContextBase uses a module listed above it, which is the healthy direction.
14→13 MirrorContextBase uses context✕
- Connections
- 7 pairs of types, where a type in MirrorContextBase uses a type in context.
- The types involved
zio.quill.MirrorContextBase.ActionMirror→zio.quill.context.ExecutionInfozio.quill.MirrorContextBase.ActionReturningMirror→zio.quill.context.ExecutionInfozio.quill.MirrorContextBase.BatchActionMirror→zio.quill.context.ExecutionInfozio.quill.MirrorContextBase.BatchActionReturningMirror→zio.quill.context.ExecutionInfozio.quill.MirrorContextBase.PrepareBatchMirror→zio.quill.context.ExecutionInfozio.quill.MirrorContextBase.PrepareQueryMirror→zio.quill.context.ExecutionInfozio.quill.MirrorContextBase.QueryMirror→zio.quill.context.ExecutionInfo
- Direction
- MirrorContextBase uses context, so a change to context can break MirrorContextBase, while a change to MirrorContextBase can't break context.
- Position
- Below the diagonal: MirrorContextBase uses a module listed above it, which is the healthy direction.
15→9 context.cassandra uses context.cassandra.encoding✕
- Connections
- 5 pairs of types, where a type in context.cassandra uses a type in context.cassandra.encoding.
- The types involved
zio.quill.context.cassandra.CassandraContext→zio.quill.context.cassandra.encoding.CassandraMapperzio.quill.context.cassandra.CassandraContext→zio.quill.context.cassandra.encoding.Encodingszio.quill.context.cassandra.CassandraStandardContext→zio.quill.context.cassandra.encoding.CassandraTypeszio.quill.context.cassandra.CassandraStandardContext→zio.quill.context.cassandra.encoding.Decoderszio.quill.context.cassandra.CassandraStandardContext→zio.quill.context.cassandra.encoding.Encoders
- Direction
- context.cassandra uses context.cassandra.encoding, so a change to context.cassandra.encoding can break context.cassandra, while a change to context.cassandra can't break context.cassandra.encoding.
- Position
- Below the diagonal: context.cassandra uses a module listed above it, which is the healthy direction.
15→13 context.cassandra uses context✕
- Connections
- 3 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.CassandraStandardContext→zio.quill.context.Contextzio.quill.context.cassandra.CassandraStandardContext→zio.quill.context.ExecutionInfo
- 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.
15→20 context.cassandra uses zio.quill part of a loop✕
- Connections
- 1 pair of types, where a type in context.cassandra uses a type in zio.quill.
- The types involved
zio.quill.context.cassandra.UdtMetaDslMacro→zio.quill.UdtMeta
- Direction
- context.cassandra uses zio.quill, so a change to zio.quill can break context.cassandra, while a change to context.cassandra 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.
16→7 context.sql uses generic✕
- Connections
- 1 pair of types, where a type in context.sql uses a type in generic.
- The types involved
zio.quill.context.sql.SqlContext→zio.quill.generic.EncodingDsl
- Direction
- context.sql uses generic, so a change to generic can break context.sql, while a change to context.sql can't break generic.
- Position
- Below the diagonal: context.sql uses a module listed above it, which is the healthy direction.
16→13 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.
17→7 context.jdbc uses generic✕
- Connections
- 3 pairs of types, where a type in context.jdbc uses a type in generic.
- The types involved
zio.quill.context.jdbc.ArrayDecoders→zio.quill.generic.ArrayEncodingzio.quill.context.jdbc.ArrayEncoders→zio.quill.generic.ArrayEncodingzio.quill.context.jdbc.Encoders→zio.quill.generic.EncodingDsl
- Direction
- context.jdbc uses generic, so a change to generic can break context.jdbc, while a change to context.jdbc can't break generic.
- Position
- Below the diagonal: context.jdbc uses a module listed above it, which is the healthy direction.
17→13 context.jdbc uses context✕
- Connections
- 9 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.ProtoContextSecunduszio.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.
17→16 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.
17→20 context.jdbc uses zio.quill part of a loop✕
- Connections
- 3 pairs of types, where a type in context.jdbc uses a type in zio.quill.
- The types involved
zio.quill.context.jdbc.JdbcContext→zio.quill.BinaryCompatHackzio.quill.context.jdbc.JdbcContext→zio.quill.OuterSelectWrapzio.quill.context.jdbc.JdbcContext→zio.quill.Quoted
- 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.
18→17 context.json uses context.jdbc✕
- Connections
- 2 pairs of types, where a type in context.json uses a type in context.jdbc.
- The types involved
zio.quill.context.json.PostgresJsonExtensions→zio.quill.context.jdbc.Decoderszio.quill.context.json.PostgresJsonExtensions→zio.quill.context.jdbc.Encoders
- Direction
- context.json uses context.jdbc, so a change to context.jdbc can break context.json, while a change to context.json can't break context.jdbc.
- Position
- Below the diagonal: context.json uses a module listed above it, which is the healthy direction.
18→20 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.
19→13 context.qzio uses context✕
- Connections
- 12 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.ContextVerbStreamzio.quill.context.qzio.ZioJdbcContext→zio.quill.context.ExecutionInfozio.quill.context.qzio.ZioJdbcContext→zio.quill.context.ProtoContextSecunduszio.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.Contextzio.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.
19→17 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.
19→20 context.qzio uses zio.quill part of a loop✕
- Connections
- 6 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.BinaryCompatHackzio.quill.context.qzio.ZioJdbcContext→zio.quill.OuterSelectWrapzio.quill.context.qzio.ZioJdbcContext→zio.quill.Quotedzio.quill.context.qzio.ZioJdbcUnderlyingContext→zio.quill.BinaryCompatHackzio.quill.context.qzio.ZioJdbcUnderlyingContext→zio.quill.OuterSelectWrapzio.quill.context.qzio.ZioJdbcUnderlyingContext→zio.quill.Quoted
- 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.
20→7 zio.quill uses generic✕
- Connections
- 4 pairs of types, where a type in zio.quill uses a type in generic.
- The types involved
zio.quill.DynamicEntityQuery→zio.quill.generic.GenericEncoderzio.quill.EagerListPlanter→zio.quill.generic.GenericEncoderzio.quill.EagerPlanter→zio.quill.generic.GenericEncoderzio.quill.InjectableEagerPlanter→zio.quill.generic.GenericEncoder
- Direction
- zio.quill uses generic, so a change to generic can break zio.quill, while a change to zio.quill can't break generic.
- Position
- Below the diagonal: zio.quill uses a module listed above it, which is the healthy direction.
20→9 zio.quill uses context.cassandra.encoding✕
- Connections
- 2 pairs of types, where a type in zio.quill uses a type in context.cassandra.encoding.
- The types involved
zio.quill.CassandraMirrorContext→zio.quill.context.cassandra.encoding.CassandraMapperzio.quill.CassandraMirrorContext→zio.quill.context.cassandra.encoding.CassandraType
- Direction
- zio.quill uses context.cassandra.encoding, so a change to context.cassandra.encoding can break zio.quill, while a change to zio.quill can't break context.cassandra.encoding.
- Position
- Below the diagonal: zio.quill uses a module listed above it, which is the healthy direction.
20→10 zio.quill uses context.mirror✕
- Connections
- 3 pairs of types, where a type in zio.quill uses a type in context.mirror.
- The types involved
zio.quill.MirrorContextBase→zio.quill.context.mirror.MirrorDecoderszio.quill.MirrorContextBase→zio.quill.context.mirror.MirrorEncoderszio.quill.SqlMirrorContext→zio.quill.context.mirror.ArrayMirrorEncoding
- 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.
20→13 zio.quill uses context✕
- Connections
- 14 pairs of types, where a type in zio.quill uses a type in context.
- The types involved
zio.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.CassandraSyncContext→zio.quill.context.ExecutionInfozio.quill.CassandraZioSession→zio.quill.context.AsyncFutureCachezio.quill.CassandraZioSession→zio.quill.context.CassandraSessionzio.quill.CassandraZioSession→zio.quill.context.SyncCachezio.quill.MirrorContext→zio.quill.context.AstSplicingzio.quill.MirrorContextBase→zio.quill.context.Contextzio.quill.MirrorContextBase→zio.quill.context.ContextVerbPreparezio.quill.MirrorContextBase→zio.quill.context.ContextVerbTranslatezio.quill.MirrorContextBase→zio.quill.context.ExecutionInfozio.quill.SqlMirrorContext→zio.quill.context.AstSplicing
- 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.
20→15 zio.quill uses context.cassandra✕
- Connections
- 2 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.CassandraContext
- 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.
20→16 zio.quill uses context.sql✕
- Connections
- 1 pair of types, where a type in zio.quill uses a type in context.sql.
- The types involved
zio.quill.SqlMirrorContext→zio.quill.context.sql.SqlContext
- 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.
20→17 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.
20→18 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.
20→19 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.
21→17 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.
21→19 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.
22→17 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.
22→19 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.
23→17 OracleZioJdbcContext uses context.jdbc✕
- Connections
- 1 pair of types, where a type in OracleZioJdbcContext uses a type in context.jdbc.
- The types involved
zio.quill.OracleZioJdbcContext.Underlying→zio.quill.context.jdbc.OracleJdbcTypes
- Direction
- OracleZioJdbcContext uses context.jdbc, so a change to context.jdbc can break OracleZioJdbcContext, while a change to OracleZioJdbcContext can't break context.jdbc.
- Position
- Below the diagonal: OracleZioJdbcContext uses a module listed above it, which is the healthy direction.
23→19 OracleZioJdbcContext uses context.qzio✕
- Connections
- 1 pair of types, where a type in OracleZioJdbcContext uses a type in context.qzio.
- The types involved
zio.quill.OracleZioJdbcContext.Underlying→zio.quill.context.qzio.ZioJdbcUnderlyingContext
- Direction
- OracleZioJdbcContext uses context.qzio, so a change to context.qzio can break OracleZioJdbcContext, while a change to OracleZioJdbcContext can't break context.qzio.
- Position
- Below the diagonal: OracleZioJdbcContext uses a module listed above it, which is the healthy direction.
24→17 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.
24→18 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.
24→19 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.
25→17 SqlServerZioJdbcContext uses context.jdbc✕
- Connections
- 2 pairs of types, where a type in SqlServerZioJdbcContext uses a type in context.jdbc.
- The types involved
zio.quill.SqlServerZioJdbcContext.Underlying→zio.quill.context.jdbc.SqlServerExecuteOverridezio.quill.SqlServerZioJdbcContext.Underlying→zio.quill.context.jdbc.SqlServerJdbcTypes
- Direction
- SqlServerZioJdbcContext uses context.jdbc, so a change to context.jdbc can break SqlServerZioJdbcContext, while a change to SqlServerZioJdbcContext can't break context.jdbc.
- Position
- Below the diagonal: SqlServerZioJdbcContext uses a module listed above it, which is the healthy direction.
25→19 SqlServerZioJdbcContext uses context.qzio✕
- Connections
- 1 pair of types, where a type in SqlServerZioJdbcContext uses a type in context.qzio.
- The types involved
zio.quill.SqlServerZioJdbcContext.Underlying→zio.quill.context.qzio.ZioJdbcUnderlyingContext
- Direction
- SqlServerZioJdbcContext uses context.qzio, so a change to context.qzio can break SqlServerZioJdbcContext, while a change to SqlServerZioJdbcContext can't break context.qzio.
- Position
- Below the diagonal: SqlServerZioJdbcContext uses a module listed above it, which is the healthy direction.
26→17 SqliteZioJdbcContext uses context.jdbc✕
- Connections
- 1 pair of types, where a type in SqliteZioJdbcContext uses a type in context.jdbc.
- The types involved
zio.quill.SqliteZioJdbcContext.Underlying→zio.quill.context.jdbc.SqliteJdbcTypes
- Direction
- SqliteZioJdbcContext uses context.jdbc, so a change to context.jdbc can break SqliteZioJdbcContext, while a change to SqliteZioJdbcContext can't break context.jdbc.
- Position
- Below the diagonal: SqliteZioJdbcContext uses a module listed above it, which is the healthy direction.
26→19 SqliteZioJdbcContext uses context.qzio✕
- Connections
- 1 pair of types, where a type in SqliteZioJdbcContext uses a type in context.qzio.
- The types involved
zio.quill.SqliteZioJdbcContext.Underlying→zio.quill.context.qzio.ZioJdbcUnderlyingContext
- Direction
- SqliteZioJdbcContext uses context.qzio, so a change to context.qzio can break SqliteZioJdbcContext, while a change to SqliteZioJdbcContext can't break context.qzio.
- Position
- Below the diagonal: SqliteZioJdbcContext uses a module listed above it, which is the healthy direction.
27→13 context.BatchStatic uses context✕
- Connections
- 1 pair of types, where a type in context.BatchStatic uses a type in context.
- The types involved
zio.quill.context.BatchStatic.Components→zio.quill.context.BatchActionType
- Direction
- context.BatchStatic uses context, so a change to context can break context.BatchStatic, while a change to context.BatchStatic can't break context.
- Position
- Below the diagonal: context.BatchStatic uses a module listed above it, which is the healthy direction.
27→20 context.BatchStatic uses zio.quill✕
- Connections
- 1 pair of types, where a type in context.BatchStatic uses a type in zio.quill.
- The types involved
zio.quill.context.BatchStatic.Components→zio.quill.InjectableEagerPlanter
- Direction
- context.BatchStatic uses zio.quill, so a change to zio.quill can break context.BatchStatic, while a change to context.BatchStatic can't break zio.quill.
- Position
- Below the diagonal: context.BatchStatic uses a module listed above it, which is the healthy direction.
28→2 context.InsertUpdateMacro uses quat✕
- Connections
- 2 pairs of types, where a type in context.InsertUpdateMacro uses a type in quat.
- The types involved
zio.quill.context.InsertUpdateMacro.Pipeline→zio.quill.quat.QuatMakingzio.quill.context.InsertUpdateMacro.Pipeline→zio.quill.quat.QuatMakingBase
- Direction
- context.InsertUpdateMacro uses quat, so a change to quat can break context.InsertUpdateMacro, while a change to context.InsertUpdateMacro can't break quat.
- Position
- Below the diagonal: context.InsertUpdateMacro uses a module listed above it, which is the healthy direction.
28→20 context.InsertUpdateMacro uses zio.quill✕
- Connections
- 4 pairs of types, where a type in context.InsertUpdateMacro uses a type in zio.quill.
- The types involved
zio.quill.context.InsertUpdateMacro.DynamicUtil→zio.quill.Quotedzio.quill.context.InsertUpdateMacro.Pipeline→zio.quill.EntityQueryzio.quill.context.InsertUpdateMacro.Pipeline→zio.quill.Planterzio.quill.context.InsertUpdateMacro.Pipeline→zio.quill.QuotationVase
- Direction
- context.InsertUpdateMacro uses zio.quill, so a change to zio.quill can break context.InsertUpdateMacro, while a change to context.InsertUpdateMacro can't break zio.quill.
- Position
- Below the diagonal: context.InsertUpdateMacro uses a module listed above it, which is the healthy direction.
29→3 context.Particularize uses util✕
- Connections
- 3 pairs of types, where a type in context.Particularize uses a type in util.
- The types involved
zio.quill.context.Particularize.Dynamic→zio.quill.util.TraceConfigzio.quill.context.Particularize.LiftsOrderer→zio.quill.util.TraceConfigzio.quill.context.Particularize.Static→zio.quill.util.TraceConfig
- Direction
- context.Particularize uses util, so a change to util can break context.Particularize, while a change to context.Particularize can't break util.
- Position
- Below the diagonal: context.Particularize uses a module listed above it, which is the healthy direction.
29→5 context.Particularize uses context.QueryExecutionBatchModel✕
- Connections
- 1 pair of types, where a type in context.Particularize uses a type in context.QueryExecutionBatchModel.
- The types involved
zio.quill.context.Particularize.LiftsOrderer→zio.quill.context.QueryExecutionBatchModel.SingleEntityLifts
- Direction
- context.Particularize uses context.QueryExecutionBatchModel, so a change to context.QueryExecutionBatchModel can break context.Particularize, while a change to context.Particularize can't break context.QueryExecutionBatchModel.
- Position
- Below the diagonal: context.Particularize uses a module listed above it, which is the healthy direction.
29→20 context.Particularize uses zio.quill✕
- Connections
- 3 pairs of types, where a type in context.Particularize uses a type in zio.quill.
- The types involved
zio.quill.context.Particularize.Dynamic→zio.quill.Planterzio.quill.context.Particularize.LiftsOrderer→zio.quill.Planterzio.quill.context.Particularize.Static→zio.quill.Planter
- Direction
- context.Particularize uses zio.quill, so a change to zio.quill can break context.Particularize, while a change to context.Particularize can't break zio.quill.
- Position
- Below the diagonal: context.Particularize uses a module listed above it, which is the healthy direction.
30→13 context.QueryExecution uses context✕
- Connections
- 1 pair of types, where a type in context.QueryExecution uses a type in context.
- The types involved
zio.quill.context.QueryExecution.RunQuery→zio.quill.context.StaticState
- Direction
- context.QueryExecution uses context, so a change to context can break context.QueryExecution, while a change to context.QueryExecution can't break context.
- Position
- Below the diagonal: context.QueryExecution uses a module listed above it, which is the healthy direction.
30→20 context.QueryExecution uses zio.quill✕
- Connections
- 2 pairs of types, where a type in context.QueryExecution uses a type in zio.quill.
- The types involved
zio.quill.context.QueryExecution.RunQuery→zio.quill.Planterzio.quill.context.QueryExecution.RunQuery→zio.quill.Quoted
- Direction
- context.QueryExecution uses zio.quill, so a change to zio.quill can break context.QueryExecution, while a change to context.QueryExecution can't break zio.quill.
- Position
- Below the diagonal: context.QueryExecution uses a module listed above it, which is the healthy direction.
31→13 context.QueryExecutionBatch uses context✕
- Connections
- 1 pair of types, where a type in context.QueryExecutionBatch uses a type in context.
- The types involved
zio.quill.context.QueryExecutionBatch.RunQuery→zio.quill.context.BatchActionType
- Direction
- context.QueryExecutionBatch uses context, so a change to context can break context.QueryExecutionBatch, while a change to context.QueryExecutionBatch can't break context.
- Position
- Below the diagonal: context.QueryExecutionBatch uses a module listed above it, which is the healthy direction.
31→20 context.QueryExecutionBatch uses zio.quill✕
- Connections
- 1 pair of types, where a type in context.QueryExecutionBatch uses a type in zio.quill.
- The types involved
zio.quill.context.QueryExecutionBatch.RunQuery→zio.quill.InjectableEagerPlanter
- Direction
- context.QueryExecutionBatch uses zio.quill, so a change to zio.quill can break context.QueryExecutionBatch, while a change to context.QueryExecutionBatch can't break zio.quill.
- Position
- Below the diagonal: context.QueryExecutionBatch uses a module listed above it, which is the healthy direction.
32→20 context.QueryExecutionBatchDynamic.PlanterKind uses zio.quill✕
- Connections
- 3 pairs of types, where a type in context.QueryExecutionBatchDynamic.PlanterKind uses a type in zio.quill.
- The types involved
zio.quill.context.QueryExecutionBatchDynamic.PlanterKind.Other→zio.quill.Planterzio.quill.context.QueryExecutionBatchDynamic.PlanterKind.PrimaryEntitiesList→zio.quill.EagerEntitiesPlanterzio.quill.context.QueryExecutionBatchDynamic.PlanterKind.PrimaryScalarList→zio.quill.EagerListPlanter
- Direction
- context.QueryExecutionBatchDynamic.PlanterKind uses zio.quill, so a change to zio.quill can break context.QueryExecutionBatchDynamic.PlanterKind, while a change to context.QueryExecutionBatchDynamic.PlanterKind can't break zio.quill.
- Position
- Below the diagonal: context.QueryExecutionBatchDynamic.PlanterKind uses a module listed above it, which is the healthy direction.
33→9 context.cassandra.encoding.UdtDecodingMacro uses context.cassandra.encoding✕
- Connections
- 1 pair of types, where a type in context.cassandra.encoding.UdtDecodingMacro uses a type in context.cassandra.encoding.
- The types involved
zio.quill.context.cassandra.encoding.UdtDecodingMacro.UdtDecoderMaker→zio.quill.context.cassandra.encoding.CassandraMapper
- Direction
- context.cassandra.encoding.UdtDecodingMacro uses context.cassandra.encoding, so a change to context.cassandra.encoding can break context.cassandra.encoding.UdtDecodingMacro, while a change to context.cassandra.encoding.UdtDecodingMacro can't break context.cassandra.encoding.
- Position
- Below the diagonal: context.cassandra.encoding.UdtDecodingMacro uses a module listed above it, which is the healthy direction.
33→13 context.cassandra.encoding.UdtDecodingMacro uses context✕
- Connections
- 1 pair of types, where a type in context.cassandra.encoding.UdtDecodingMacro uses a type in context.
- The types involved
zio.quill.context.cassandra.encoding.UdtDecodingMacro.UdtParams→zio.quill.context.UdtValueLookup
- Direction
- context.cassandra.encoding.UdtDecodingMacro uses context, so a change to context can break context.cassandra.encoding.UdtDecodingMacro, while a change to context.cassandra.encoding.UdtDecodingMacro can't break context.
- Position
- Below the diagonal: context.cassandra.encoding.UdtDecodingMacro uses a module listed above it, which is the healthy direction.
33→20 context.cassandra.encoding.UdtDecodingMacro uses zio.quill✕
- Connections
- 1 pair of types, where a type in context.cassandra.encoding.UdtDecodingMacro uses a type in zio.quill.
- The types involved
zio.quill.context.cassandra.encoding.UdtDecodingMacro.UdtParams→zio.quill.UdtMeta
- Direction
- context.cassandra.encoding.UdtDecodingMacro uses zio.quill, so a change to zio.quill can break context.cassandra.encoding.UdtDecodingMacro, while a change to context.cassandra.encoding.UdtDecodingMacro can't break zio.quill.
- Position
- Below the diagonal: context.cassandra.encoding.UdtDecodingMacro uses a module listed above it, which is the healthy direction.
34→9 context.cassandra.encoding.UdtEncodingMacro uses context.cassandra.encoding✕
- Connections
- 1 pair of types, where a type in context.cassandra.encoding.UdtEncodingMacro uses a type in context.cassandra.encoding.
- The types involved
zio.quill.context.cassandra.encoding.UdtEncodingMacro.UdtEncoderMaker→zio.quill.context.cassandra.encoding.CassandraMapper
- Direction
- context.cassandra.encoding.UdtEncodingMacro uses context.cassandra.encoding, so a change to context.cassandra.encoding can break context.cassandra.encoding.UdtEncodingMacro, while a change to context.cassandra.encoding.UdtEncodingMacro can't break context.cassandra.encoding.
- Position
- Below the diagonal: context.cassandra.encoding.UdtEncodingMacro uses a module listed above it, which is the healthy direction.
34→13 context.cassandra.encoding.UdtEncodingMacro uses context✕
- Connections
- 1 pair of types, where a type in context.cassandra.encoding.UdtEncodingMacro uses a type in context.
- The types involved
zio.quill.context.cassandra.encoding.UdtEncodingMacro.UdtParams→zio.quill.context.UdtValueLookup
- Direction
- context.cassandra.encoding.UdtEncodingMacro uses context, so a change to context can break context.cassandra.encoding.UdtEncodingMacro, while a change to context.cassandra.encoding.UdtEncodingMacro can't break context.
- Position
- Below the diagonal: context.cassandra.encoding.UdtEncodingMacro uses a module listed above it, which is the healthy direction.
34→20 context.cassandra.encoding.UdtEncodingMacro uses zio.quill✕
- Connections
- 1 pair of types, where a type in context.cassandra.encoding.UdtEncodingMacro uses a type in zio.quill.
- The types involved
zio.quill.context.cassandra.encoding.UdtEncodingMacro.UdtParams→zio.quill.UdtMeta
- Direction
- context.cassandra.encoding.UdtEncodingMacro uses zio.quill, so a change to zio.quill can break context.cassandra.encoding.UdtEncodingMacro, while a change to context.cassandra.encoding.UdtEncodingMacro can't break zio.quill.
- Position
- Below the diagonal: context.cassandra.encoding.UdtEncodingMacro uses a module listed above it, which is the healthy direction.
35→13 doobie uses context✕
- Connections
- 3 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.ExecutionInfozio.quill.doobie.DoobieContextBase→zio.quill.context.ProtoContextSecundus
- 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.
35→17 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.JdbcContextTypes
- 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.
35→20 doobie uses zio.quill✕
- Connections
- 2 pairs of types, where a type in doobie uses a type in zio.quill.
- The types involved
zio.quill.doobie.DoobieContextBase→zio.quill.OuterSelectWrapzio.quill.doobie.DoobieContextBase→zio.quill.Quoted
- 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.
36→13 jdbczio uses context✕
- Connections
- 3 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.ProtoContextSecundus
- 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.
36→17 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.
36→19 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.
36→20 jdbczio uses zio.quill✕
- Connections
- 3 pairs of types, where a type in jdbczio uses a type in zio.quill.
- The types involved
zio.quill.jdbczio.QuillBaseContext→zio.quill.BinaryCompatHackzio.quill.jdbczio.QuillBaseContext→zio.quill.OuterSelectWrapzio.quill.jdbczio.QuillBaseContext→zio.quill.Quoted
- 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.
37→11 metaprog.QuotationLotExpr uses metaprog✕
- Connections
- 5 pairs of types, where a type in metaprog.QuotationLotExpr uses a type in metaprog.
- The types involved
zio.quill.metaprog.QuotationLotExpr.Pluckable→zio.quill.metaprog.QuotationLotExprzio.quill.metaprog.QuotationLotExpr.Pointable→zio.quill.metaprog.QuotationLotExprzio.quill.metaprog.QuotationLotExpr.Unquoted→zio.quill.metaprog.QuotationLotExprzio.quill.metaprog.QuotationLotExpr.Uprootable→zio.quill.metaprog.PlanterExprzio.quill.metaprog.QuotationLotExpr.Uprootable→zio.quill.metaprog.QuotationLotExpr
- Direction
- metaprog.QuotationLotExpr uses metaprog, so a change to metaprog can break metaprog.QuotationLotExpr, while a change to metaprog.QuotationLotExpr can't break metaprog.
- Position
- Below the diagonal: metaprog.QuotationLotExpr uses a module listed above it, which is the healthy direction.
37→20 metaprog.QuotationLotExpr uses zio.quill✕
- Connections
- 4 pairs of types, where a type in metaprog.QuotationLotExpr uses a type in zio.quill.
- The types involved
zio.quill.metaprog.QuotationLotExpr.Pluckable→zio.quill.Quotedzio.quill.metaprog.QuotationLotExpr.Pointable→zio.quill.QuotationLotzio.quill.metaprog.QuotationLotExpr.Uprootable→zio.quill.QuotationLotzio.quill.metaprog.QuotationLotExpr.Uprootable→zio.quill.Quoted
- Direction
- metaprog.QuotationLotExpr uses zio.quill, so a change to zio.quill can break metaprog.QuotationLotExpr, while a change to metaprog.QuotationLotExpr can't break zio.quill.
- Position
- Below the diagonal: metaprog.QuotationLotExpr uses a module listed above it, which is the healthy direction.
38→11 context.BatchStatic.PlanterKind uses metaprog✕
- Connections
- 3 pairs of types, where a type in context.BatchStatic.PlanterKind uses a type in metaprog.
- The types involved
zio.quill.context.BatchStatic.PlanterKind.Other→zio.quill.metaprog.PlanterExprzio.quill.context.BatchStatic.PlanterKind.PrimaryEntitiesList→zio.quill.metaprog.EagerEntitiesPlanterExprzio.quill.context.BatchStatic.PlanterKind.PrimaryScalarList→zio.quill.metaprog.EagerListPlanterExpr
- Direction
- context.BatchStatic.PlanterKind uses metaprog, so a change to metaprog can break context.BatchStatic.PlanterKind, while a change to context.BatchStatic.PlanterKind can't break metaprog.
- Position
- Below the diagonal: context.BatchStatic.PlanterKind uses a module listed above it, which is the healthy direction.
38→27 context.BatchStatic.PlanterKind uses context.BatchStatic✕
- Connections
- 3 pairs of types, where a type in context.BatchStatic.PlanterKind uses a type in context.BatchStatic.
- The types involved
zio.quill.context.BatchStatic.PlanterKind.Other→zio.quill.context.BatchStatic.PlanterKindzio.quill.context.BatchStatic.PlanterKind.PrimaryEntitiesList→zio.quill.context.BatchStatic.PlanterKindzio.quill.context.BatchStatic.PlanterKind.PrimaryScalarList→zio.quill.context.BatchStatic.PlanterKind
- Direction
- context.BatchStatic.PlanterKind uses context.BatchStatic, so a change to context.BatchStatic can break context.BatchStatic.PlanterKind, while a change to context.BatchStatic.PlanterKind can't break context.BatchStatic.
- Position
- Below the diagonal: context.BatchStatic.PlanterKind uses a module listed above it, which is the healthy direction.
39→20 context.InsertUpdateMacro.Pipeline uses zio.quill✕
- Connections
- 1 pair of types, where a type in context.InsertUpdateMacro.Pipeline uses a type in zio.quill.
- The types involved
zio.quill.context.InsertUpdateMacro.Pipeline.InserteeSchema→zio.quill.EntityQuery
- Direction
- context.InsertUpdateMacro.Pipeline uses zio.quill, so a change to zio.quill can break context.InsertUpdateMacro.Pipeline, while a change to context.InsertUpdateMacro.Pipeline can't break zio.quill.
- Position
- Below the diagonal: context.InsertUpdateMacro.Pipeline uses a module listed above it, which is the healthy direction.
39→28 context.InsertUpdateMacro.Pipeline uses context.InsertUpdateMacro✕
- Connections
- 2 pairs of types, where a type in context.InsertUpdateMacro.Pipeline uses a type in context.InsertUpdateMacro.
- The types involved
zio.quill.context.InsertUpdateMacro.Pipeline.IgnoredColumns→zio.quill.context.InsertUpdateMacro.IgnoresSummonStatezio.quill.context.InsertUpdateMacro.Pipeline.InserteeSchema→zio.quill.context.InsertUpdateMacro.EntitySummonState
- Direction
- context.InsertUpdateMacro.Pipeline uses context.InsertUpdateMacro, so a change to context.InsertUpdateMacro can break context.InsertUpdateMacro.Pipeline, while a change to context.InsertUpdateMacro.Pipeline can't break context.InsertUpdateMacro.
- Position
- Below the diagonal: context.InsertUpdateMacro.Pipeline uses a module listed above it, which is the healthy direction.
40→17 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→18 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→36 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 | 29 | High / Critical |
| A02:2025 — Security Misconfiguration | 28 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 5 | Medium |
| A07:2025 — Authentication Failures | 1 | High / Critical |
Roadmap
Top priorities: Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED; Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2), REDACTED (2); 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. | +2.7 pts | Low | Secret Scanning |
| Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2), REDACTED (2). | +2.0 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.2 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. | +1.0 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.0 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. | +1.0 pts | Low | Supply-chain Provenance & Signing |
| 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. | +1.8 pts | Medium | Nullable reference types |
| 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. | +1.8 pts | Medium | Architecture documentation |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | 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 | 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.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| quill-sql/src/main/scala/zio/quill/parser/Parser.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| quill-sql/src/main/scala/zio/quill/context/Particularize.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| quill-sql/src/main/scala/zio/quill/context/QueryExecution.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| quill-sql/src/main/scala/zio/quill/context/StaticTranslationMacro.scala | 6.0 | 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 59 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 59 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, 285 of 292 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 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. To have the real number read, produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — 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, 320 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — 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 repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because repo1.maven.org — the registry that answers it — was asked and did not reply (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/com/datastax/oss/java-driver-core/maven-metadata.xml). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add repo1.maven.org to the allowlist and re-run — not to build anything.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (34 contributor(s) across 1128 commit(s) sampled, automation and bot accounts excluded). One of them holds 82% of the history; the other 33 hold 0.5% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — 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.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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-sql/src/main/scala/zio/quill/DslModel.scala`, `quill-sql/src/main/scala/zio/quill/metaprog/etc/ListFlicer.scala`, `quill-sql/src/main/scala/zio/quill/parser/ParserHelpers.scala`, `quill-sql/src/main/scala/zio/quill/parser/engine/Parser.scala`, `quill-sql/src/main/scala/zio/quill/parser/engine/ParserChain.scala` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D34 Knowledge Freshness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. File-level freshness contradicts repo activity: 46 commits in the last 90 days, yet 72 of 85 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- 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 register layer: write /var/log/lastlog: no space left on device; 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:9), 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:9), 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:9), 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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- 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").
- 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.
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: 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
6 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was QueryParser.attempt at 28. A further 3 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 OperationsParser.attempt at 34 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: quill-sql/src/main/scala/zio/quill/util/Interpolator2.scala (Traceable.generateString at 16). 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 6 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with QueryParser.attempt (cyclomatic 28), Dynamic.apply (cyclomatic 21), OptionParser.attempt (cyclomatic 19). — 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 6 together lifts Cyclomatic Complexity from 8.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
9 method(s) exceeded the cognitive complexity threshold of 15; the worst was StaticTranslationMacro.apply at 36.
What to do
- Bring the 9 bodies over 15 down to 15 or less in Cognitive Complexity — start with StaticTranslationMacro.apply (cognitive 36), ZioJdbcContext.transaction (cognitive 35), Dynamic.apply (cognitive 22). — 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 9 together lifts Cognitive Complexity from 8.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
4 god class(es) detected.
What to do
- Resolve the 2 FileTooLong finding(s) in God Classes — start with Parser.scala, Extractors.scala. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with QueryExecutionBatchIteration.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with DynamicDslModel.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
12 duplicated block group(s) detected.
What to do
- Resolve the 4 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with UdtEncodingMacro.scala (2), QueryExecutionBatch.scala, GenericDecoder.scala. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Duplicated block (69 lines × 2) finding(s) in Code Duplication — start with QueryExecution.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (9–13 lines × 2) finding(s) in Code Duplication — start with InsertUpdateMacro.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
9 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 8 of the 9 (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 14 classes have LCOM4 above 3.
D9 · Test Distribution
1923 test methods: 1913 unit, 10 integration, 0 BDD, 0 e2e. The Scala suite contributes 1923 test case(s) across 214 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
D13 · Secret Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
158 deducted task-comment markers across 18599 LoC (0.8/KLoC) → score 8.5. 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 155 TodoComment finding(s) in Explicit Debt — start with QuatSpec.scala (11), ElaborateStructure.scala (10), Parser.scala (8). — One of this dimension's main actionable groups (155 warning-level).
- Resolve the 2 FixmeComment finding(s) in Explicit Debt — start with Extractors.scala (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 HackComment finding(s) in Explicit Debt — start with OptionJdbcSpec.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D26 · Project Cohesion
1 of 1 build units (sbt) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
29 finding(s): 0 critical, 28 high, 1 medium, 0 low. 19 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 3 file(s) — `quill-sql/src/main/scala/zio/quill/DslModel.scala`, `quill-sql/src/main/scala/zio/quill/metaprog/etc/ListFlicer.scala`, `quill-sql/src/main/scala/zio/quill/parser/ParserHelpers.scala` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (8 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 19 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 (19 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D31 · IaC & Container Security
28 finding(s): 0 critical, 13 high, 10 medium, 5 low.
What to do
- Resolve the 13 High IaC finding(s) in IaC & Container Security — start with REDACTED (5), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (13 issue-level).
- Resolve the 10 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 5 Low IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (5 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
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 — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `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
- `SqlContext[Idiom, Naming]` declares 28 abstract members: `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 24 abstract members: `arrayStringEncoder`, `arrayBigDecimalEncoder`, `arrayBooleanEncoder`, `arrayByteEncoder`, `arrayShortEncoder`, `arrayIntEncoder`, `arrayLongEncoder`, `arrayFloatEncoder`, `arrayDoubleEncoder`, `arrayDateEncoder`, `arrayLocalDateEncoder`, `arrayUuidEncoder`, `arrayStringDecoder`, `arrayBigDecimalDecoder`, `arrayBooleanDecoder`, `arrayByteDecoder`, `arrayShortDecoder`, `arrayIntDecoder`, `arrayLongDecoder`, `arrayFloatDecoder`, `arrayDoubleDecoder`, `arrayDateDecoder`, `arrayLocalDateDecoder`, `arrayUuidDecoder`. 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/generic/ArrayEncoding.scala:15
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
- `like` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — quill-sql/src/main/scala/zio/quill/Dsl.scala:42
What to do
- Finish or delete the members whose body is still `???` or a "not implemented" throw where nothing overrides them, and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
- `like` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — quill-sql/src/main/scala/zio/quill/Dsl.scala:42
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×25) — quill-jdbc-zio/src/test/scala/zio/quill/h2/PeopleZioReturningSpec.scala:44, quill-jdbc-zio/src/test/scala/zio/quill/h2/PeopleZioReturningSpec.scala:54, quill-jdbc-zio/src/test/scala/zio/quill/h2/PeopleZioReturningSpec.scala:60, …
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
- Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- build/m1/README.MD links to `../../CONTRIBUTING.md`, but `CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — build/m1/README.MD:36
What to do
- Reconcile the README with reality: build/m1/README.MD links to `../../CONTRIBUTING.md`, but `CONTRIBUTING.md` does not exist.
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics (opentelemetry-java or Micrometer) and a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) for operability.
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 13193 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
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.
- 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
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- `case e` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — quill-sql/src/main/scala/zio/quill/quat/QuatMaking.scala:288
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- No build over this repository's 186 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 | 60% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 91% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 63% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 62% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 58% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
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:9) 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:9) 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:9) 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 — 56 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.
- AC7 A11y enforcement — 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 register layer: write /var/log/lastlog: no space left on device; 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 — ~23862 lines of test source are present (.scala) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .scala suite was found but not re-run
- D12 Dependency Hygiene — Dependency currency not established — repo1.maven.org did not answer
- D14 License Compliance — Not scored — this repository's 14 pinned sbt dependency coordinate(s) were read from its 1 sbt build file(s), but Maven Central could not be asked for the licence of 14 of them (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/com/datastax/oss/java-driver-core/4.17.0/java-driver-core-4.17.0.pom), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- 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 — Naming consistency is measured on C# and TypeScript only; Scala not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — 5 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- 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): 105 value object(s); 3 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 source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- 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: 186 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.
- 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
- 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 — 42 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
Serious — 206 finding(s)
- TodoComment quill-sql-tests/src/test/scala/zio/quill/InsertAdvancedSpec.scala:68
- TodoComment quill-sql-tests/src/test/scala/zio/quill/InsertAdvancedSpec.scala:75
- TodoComment quill-sql-tests/src/test/scala/zio/quill/InsertAdvancedSpec.scala:127
- TodoComment quill-sql-tests/src/test/scala/zio/quill/InsertAdvancedSpec.scala:133
- TodoComment quill-sql-tests/src/test/scala/zio/quill/InsertAdvancedSpec.scala:140
- TodoComment quill-sql-tests/src/test/scala/zio/quill/InsertAdvancedSpec.scala:266
- TodoComment quill-sql-tests/src/test/scala/zio/quill/InsertAdvancedSpec.scala:283
- TodoComment quill-sql-tests/src/test/scala/zio/quill/ported/sqlidiomspec/QuerySpec.scala:221
- TodoComment quill-sql-tests/src/test/scala/zio/quill/ported/sqlidiomspec/QuerySpec.scala:547
- TodoComment quill-sql-tests/src/test/scala/zio/quill/ported/quotationspec/ActionTest.scala:73
- TodoComment quill-sql-tests/src/test/scala/zio/quill/ported/quotationspec/ActionTest.scala:211
- TodoComment quill-sql-tests/src/test/scala/zio/quill/ported/quotationspec/ActionTest.scala:197
- TodoComment quill-sql-tests/src/test/scala/zio/quill/ported/quotationspec/IdentAndPropertyTest.scala:35
- TodoComment quill-sql-tests/src/test/scala/zio/quill/ported/quotationspec/OptionOperationTest.scala:132
- TodoComment quill-sql-tests/src/test/scala/zio/quill/ported/quotationspec/QueryTest.scala:23
- TodoComment quill-sql-tests/src/test/scala/zio/quill/ported/quotationspec/QueryTest.scala:95
- TodoComment quill-sql-tests/src/test/scala/zio/quill/ported/quotationspec/ValueTest.scala:34
- TodoComment quill-sql-tests/src/test/scala/zio/quill/examples/TypeclassUsecase_Repetitive.scala:21
- TodoComment quill-sql-tests/src/test/scala/zio/quill/context/sql/idiom/SqlIdiomOptionCompareSpec.scala:152
- TodoComment quill-sql-tests/src/test/scala/zio/quill/context/sql/idiom/SqlIdiomOptionCompareSpec.scala:363
- TodoComment quill-sql/src/test/scala/zio/quill/BatchActionMultiTest.scala:81
- TodoComment quill-sql/src/test/scala/zio/quill/BatchActionTest.scala:87
- TodoComment quill-sql/src/test/scala/zio/quill/GenericDecoderCoproductTestAdditional.scala:56
- TodoComment quill-sql/src/test/scala/zio/quill/QuerySchemaTest.scala:81
- TodoComment quill-sql/src/test/scala/zio/quill/QuotationTest.scala:281
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (5 lines × 2) quill-cassandra/src/main/scala/zio/quill/context/cassandra/encoding/UdtEncodingMacro.scala:100
- Duplicated block (5 lines × 2) quill-cassandra/src/main/scala/zio/quill/context/cassandra/encoding/UdtEncodingMacro.scala:235
- Duplicated block (5 lines × 2) quill-sql/src/main/scala/zio/quill/context/QueryExecutionBatch.scala:494
- Duplicated block (5 lines × 2) quill-sql/src/main/scala/zio/quill/generic/GenericDecoder.scala:104
- FixmeComment quill-sql/src/main/scala/zio/quill/metaprog/Extractors.scala:383
- FixmeComment quill-sql/src/main/scala/zio/quill/metaprog/Extractors.scala:388
- FileTooLong: parser/Parser.scala quill-sql/src/main/scala/zio/quill/parser/Parser.scala
- FileTooLong: metaprog/Extractors.scala quill-sql/src/main/scala/zio/quill/metaprog/Extractors.scala
- QueryParser.attempt (cyclomatic 28) quill-sql/src/main/scala/zio/quill/parser/Parser.scala:644
- Dynamic.apply (cyclomatic 21) quill-sql/src/main/scala/zio/quill/context/Particularize.scala:76
- OptionParser.attempt (cyclomatic 19) quill-sql/src/main/scala/zio/quill/parser/Parser.scala:575
- PrepareDynamicExecution.processLifts (cyclomatic 18) quill-sql/src/main/scala/zio/quill/context/QueryExecution.scala:580
- StaticTranslationMacro.processLifts (cyclomatic 18) quill-sql/src/main/scala/zio/quill/context/StaticTranslationMacro.scala:115
- StaticTranslationMacro.apply (cyclomatic 17) quill-sql/src/main/scala/zio/quill/context/StaticTranslationMacro.scala:215
- HackComment quill-jdbc/src/test/scala/zio/quill/context/jdbc/sqlserver/OptionJdbcSpec.scala:22
- StaticTranslationMacro.apply (cognitive 36) quill-sql/src/main/scala/zio/quill/context/StaticTranslationMacro.scala:215
- ZioJdbcContext.transaction (cognitive 35) quill-jdbc-zio/src/main/scala/zio/quill/context/qzio/ZioJdbcContext.scala:184
- Dynamic.apply (cognitive 22) quill-sql/src/main/scala/zio/quill/context/Particularize.scala:76
- GenericDecoder.decode (cognitive 20) quill-sql/src/main/scala/zio/quill/generic/GenericDecoder.scala:240
- InserteeSchema.summon (cognitive 18) quill-sql/src/main/scala/zio/quill/context/InsertUpdateMacro.scala:141
- PrepareDynamicExecution.processLifts (cognitive 17) quill-sql/src/main/scala/zio/quill/context/QueryExecution.scala:580
- StaticTranslationMacro.processLifts (cognitive 17) quill-sql/src/main/scala/zio/quill/context/StaticTranslationMacro.scala:115
- ElaborateStructure.base (cognitive 16) quill-sql/src/main/scala/zio/quill/generic/ElaborateStructure.scala:363
- OptionParser.attempt (cognitive 16) quill-sql/src/main/scala/zio/quill/parser/Parser.scala:575
- REDACTED
- MethodTooLong: QueryExecutionBatchIteration.apply quill-sql/src/main/scala/zio/quill/context/QueryExecutionBatchIteration.scala:75
- TooManyMethods: DynamicQuery quill-sql/src/main/scala/zio/quill/DynamicDslModel.scala:61
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (69 lines × 2) quill-sql/src/main/scala/zio/quill/context/QueryExecution.scala:602
- Duplicated block (9–13 lines × 2) quill-sql/src/main/scala/zio/quill/context/InsertUpdateMacro.scala:347
- Duplicated block (13 lines × 2) quill-sql/src/main/scala/zio/quill/generic/ConstructType.scala:38
- Duplicated block (12 lines × 2) quill-sql/src/main/scala/zio/quill/context/QueryExecution.scala:585
- Duplicated block (10–11 lines × 2) quill-sql/src/main/scala/zio/quill/context/QueryMetaExtractor.scala:165
- Duplicated block (8 lines × 2) quill-sql/src/main/scala/zio/quill/parser/ParserHelpers.scala:389
- Duplicated block (6 lines × 2) quill-jdbc-zio/src/main/scala/zio/quill/context/ZioJdbc.scala:69
- Duplicated block (7 lines × 3) quill-sql/src/main/scala/zio/quill/metaprog/Extractors.scala:583
- Unfinished stub — body is `???` quill-sql/src/main/scala/zio/quill/Dsl.scala:42
- Unfinished stub — body is ??? / NotImplementedError quill-sql/src/main/scala/zio/quill/Dsl.scala:42
- Swallowed exception (caught, then discarded) quill-sql/src/main/scala/zio/quill/quat/QuatMaking.scala:288
Minor — 44 finding(s)
- Disabled test quill-jdbc-zio/src/test/scala/zio/quill/h2/PeopleZioReturningSpec.scala:44
- Disabled test quill-jdbc-zio/src/test/scala/zio/quill/h2/PeopleZioReturningSpec.scala:54
- Disabled test quill-jdbc-zio/src/test/scala/zio/quill/h2/PeopleZioReturningSpec.scala:60
- Disabled test quill-jdbc-zio/src/test/scala/zio/quill/mysql/PeopleZioReturningSpec.scala:44
- Disabled test quill-jdbc-zio/src/test/scala/zio/quill/mysql/PeopleZioReturningSpec.scala:60
- Disabled test quill-jdbc-zio/src/test/scala/zio/quill/oracle/PeopleZioReturningSpec.scala:46
- Disabled test quill-jdbc-zio/src/test/scala/zio/quill/oracle/PeopleZioReturningSpec.scala:56
- Disabled test quill-jdbc-zio/src/test/scala/zio/quill/oracle/PeopleZioReturningSpec.scala:66
- Disabled test quill-jdbc-zio/src/test/scala/zio/quill/sqlite/PeopleZioReturningSpec.scala:44
- Disabled test quill-jdbc-zio/src/test/scala/zio/quill/sqlite/PeopleZioReturningSpec.scala:60
- Disabled test quill-jdbc-zio/src/test/scala/zio/quill/sqlserver/PeopleZioReturningSpec.scala:64
- Disabled test quill-jdbc/src/test/scala/zio/quill/context/jdbc/h2/PeopleJdbcReturningSpec.scala:39
- Disabled test quill-jdbc/src/test/scala/zio/quill/context/jdbc/h2/PeopleJdbcReturningSpec.scala:52
- Disabled test quill-jdbc/src/test/scala/zio/quill/context/jdbc/mysql/PeopleJdbcReturningSpec.scala:39
- Disabled test quill-jdbc/src/test/scala/zio/quill/context/jdbc/mysql/PeopleJdbcReturningSpec.scala:46
- Disabled test quill-jdbc/src/test/scala/zio/quill/context/jdbc/mysql/PeopleJdbcReturningSpec.scala:52
- Disabled test quill-jdbc/src/test/scala/zio/quill/context/jdbc/oracle/JdbcContextSpec.scala:90
- Disabled test quill-jdbc/src/test/scala/zio/quill/context/jdbc/oracle/PeopleJdbcReturningSpec.scala:39
- Disabled test quill-jdbc/src/test/scala/zio/quill/context/jdbc/oracle/PeopleJdbcReturningSpec.scala:46
- Disabled test quill-jdbc/src/test/scala/zio/quill/context/jdbc/oracle/PeopleJdbcReturningSpec.scala:53
- Disabled test quill-jdbc/src/test/scala/zio/quill/context/jdbc/sqlite/PeopleJdbcReturningSpec.scala:27
- Disabled test quill-jdbc/src/test/scala/zio/quill/context/jdbc/sqlite/PeopleJdbcReturningSpec.scala:39
- Disabled test quill-jdbc/src/test/scala/zio/quill/context/jdbc/sqlite/PeopleJdbcReturningSpec.scala:52
- Disabled test quill-jdbc/src/test/scala/zio/quill/context/jdbc/sqlserver/PeopleJdbcReturningSpec.scala:51
- Disabled test quill-sql-tests/src/test/scala/zio/quill/ported/sqlidiomspec/QuerySpec.scala:546
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Fat interface: CassandraContext[N] (34 abstract members) quill-cassandra/src/main/scala/zio/quill/context/cassandra/CassandraContext.scala:11
- Fat interface: SqlContext[Idiom, Naming] (28 abstract members) quill-sql/src/main/scala/zio/quill/context/sql/SqlContext.scala:12
- Fat interface: ArrayEncoding (24 abstract members) quill-sql/src/main/scala/zio/quill/generic/ArrayEncoding.scala:15
- Duplicated predicate quill-sql/src/main/scala/zio/quill/generic/DeconstructElaboratedEntityLevels.scala:53
- Duplicated predicate quill-sql/src/main/scala/zio/quill/context/QueryExecution.scala:643
- Duplicated predicate quill-sql/src/main/scala/zio/quill/generic/ConstructType.scala:37
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- No ADRs
- README/code drift build/m1/README.MD:36
- No SAST .github/workflows/auto-approve.yml:7
- No rollback/health safety
- Scala's null is not held to the type system everywhere
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-8a6b68dbf6194833b1143713ec83f567/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-8a6b68dbf6194833b1143713ec83f567/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 . | 29 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-7c5dcfd2d1834e25b1b9f26fe9e5a557 | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 28 | 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 5 file(s) — `quill-sql/src/main/scala/zio/quill/DslModel.scala`, `quill-sql/src/main/scala/zio/quill/metaprog/etc/ListFlicer.scala`, `quill-sql/src/main/scala/zio/quill/parser/ParserHelpers.scala`, `quill-sql/src/main/scala/zio/quill/parser/engine/Parser.scala`, `quill-sql/src/main/scala/zio/quill/parser/engine/ParserChain.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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-7c5dcfd2d1834e25b1b9f26fe9e5a557 | 0 | artifacts/raw/osv-scanner.json |