Public report of lensesio/stream-reactor, published 14 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 14 November 2026, 14:35 UTC · Survey ID cd_1f2bf484c4f8436a8a6325f82704a778
lensesio/stream-reactor
Measured 14 November 2026, 14:33 UTC, at code version e5d3e37
CAI scoreAt riskUp 4 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 73,609 lines of product code in 37 projects, tests not counted · Estimated rebuild effort: about 1.7 person-years · Weakest lens: Production Readiness, 53
Findings by how serious they are
105 critical299 serious232 minor
13 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 14:33 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
58of 58 dimensions measured by tools.
624of 636 findings point to an exact file and line, so you can open each one in the code. The other 12 concern the repository as a whole, such as missing documentation.
58dimensions across 7 lenses, read from 73,609 lines of product code in 37 projects.
lensesio/stream-reactor is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 64 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 53, is the weakest lens and counts most in the score. The best first step is adding automated security scanning, worth about 5 points. Documenting the recovery plan comes next, worth about 4 points. Raising Production Readiness to 70 would lift the score to about 71.
Seventy-one pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Thirteen known security holes in the packages the code depends on can be used by attackers, and twelve weaknesses in the code could be used by an attacker. Pinning each tool to an exact version, updating the vulnerable packages and fixing the weaknesses the scanner points to would close these risks. Passing outside input through environment variables would fix the three pipeline steps that put outside input straight into a shell command, and limiting each secret to its own step would deal with the two secrets exposed to more of the pipeline than needed. The two parts of the code nobody has worked on for a long time need someone to learn and document them before anyone changes them.
The product code is 73,609 lines, about €240,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 53 to 70, the lowest score rated Strong, the score would rise from 64 to about 71.
Code composition: what the lines of code are
Product code 41%Tests 59%
New since the last survey: 69 findings
These 69 critical or serious findings weren't in the previous survey, on 26 October 2026.
Code Duplication · Edited copy of a member (49 corresponding lines) kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala
Code Duplication · Edited copy of a member (38 corresponding lines) kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonConverterWithSchemaEvolution.scala
Code Duplication · Edited copy of a member (77 corresponding lines) kafka-connect-mqtt/src/main/scala/io/lenses/streamreactor/connect/mqtt/config/MqttSinkSettings.scala
Code Duplication · Edited copy of a member (81 corresponding lines) kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/PrimaryKeyExtractor.scala
Code Duplication · Edited copy of a member (20 corresponding lines) kafka-connect-jms/src/main/scala/io/lenses/streamreactor/connect/jms/sink/converters/MapMessageConverter.scala
Code Duplication · Edited copy of a member (43 corresponding lines) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/MergeQueries.java
Code Duplication · Edited copy of a member (27 corresponding lines) kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/KElasticClient.scala
Code Duplication · Edited copy of a member (22 corresponding lines) java-connectors/kafka-connect-azure-eventhubs/src/main/java/io/lenses/streamreactor/connect/azure/eventhubs/util/KcqlConfigTopicMapper.java
Code Duplication · Edited copy of a member (23 corresponding lines) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/transformers/AddConnectSchemaTransformer.scala
Code Duplication · Edited copy of a member (35 corresponding lines) kafka-connect-cassandra/src/main/scala/io/lenses/streamreactor/common/concurrent/FutureAwaitWithFailFastFn.scala
Code Duplication · Edited copies of one member (3 members, 22+ corresponding lines) kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/Sql.scala
Code Duplication · Edited copy of a member (24 corresponding lines) kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/config/ElasticSettings.scala
Code Duplication · Edited copy of a member (16 corresponding lines) kafka-connect-jms/src/main/scala/io/lenses/streamreactor/connect/jms/sink/converters/MapMessageConverter.scala
Code Duplication · Edited copy of a member (17 corresponding lines) kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/converters/sink/AvroConverter.scala
Code Duplication · Edited copy of a member (21 corresponding lines) kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/ElasticWriter.scala
Code Duplication · Edited copy of a member (21 corresponding lines) kafka-connect-aws-s3/src/main/scala/io/lenses/streamreactor/connect/aws/s3/storage/AwsS3StorageInterface.scala
Code Duplication · Edited copy of a member (18 corresponding lines) kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/KElasticBulkClient.scala
Code Duplication · Edited copy of a member (14 corresponding lines) java-connectors/kafka-connect-query-language/src/main/java/io/lenses/kcql/Kcql.java
Code Duplication · Edited copy of a member (13 corresponding lines) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/config/PropertiesHelper.scala
Code Duplication · Edited copy of a member (18 corresponding lines) kafka-connect-aws-s3/src/main/scala/io/lenses/streamreactor/connect/aws/s3/storage/AwsS3StorageInterface.scala
Code Duplication · Edited copy of a member (17 corresponding lines) kafka-connect-jms/src/main/scala/io/lenses/streamreactor/connect/jms/sink/JMSSinkTask.scala
Code Duplication · Edited copy of a member (24 corresponding lines) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/config/FormatSelection.scala
Code Duplication · Edited copy of a member (19 corresponding lines) kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/KElasticBulkClient.scala
Code Duplication · Edited copy of a member (21 corresponding lines) kafka-connect-cassandra/src/main/scala/io/lenses/streamreactor/connect/cassandra/source/CqlGenerator.scala
Code Duplication · Edited copy of a member (10 corresponding lines) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/SchemaManager.java
Code Duplication · Edited copy of a member (15 corresponding lines) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/convert/logicaltype/DebeziumLogicalConverters.java
Code Duplication · Edited copy of a member (9 corresponding lines) kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/config/FlushSettings.scala
Code Duplication · Edited copy of a member (14 corresponding lines) java-connectors/kafka-connect-query-language/src/main/java/io/lenses/kcql/Field.java
Code Duplication · Edited copy of a member (12 corresponding lines) kafka-connect-azure-datalake/src/main/scala/io/lenses/streamreactor/connect/datalake/storage/DatalakeStorageInterface.scala
Code Duplication · Edited copy of a member (6 corresponding lines) java-connectors/kafka-connect-common/src/main/java/io/lenses/streamreactor/common/collections/TopicPartitionOffsetAndMetadataStorage.java
Code Duplication · Edited copy of a member (12 corresponding lines) java-connectors/kafka-connect-common/src/main/java/io/lenses/streamreactor/common/security/StoresInfo.java
Code Duplication · Edited copy of a member (10 corresponding lines) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/BigQuerySinkTask.java
Code Duplication · Edited copy of a member (8 corresponding lines) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/transformers/EnvelopeWithSchemaTransformer.scala
Code Duplication · Edited copy of a member (6 corresponding lines) java-connectors/kafka-connect-common/src/main/java/io/lenses/streamreactor/common/validation/validators/DistinctSourceNamesValidator.java
Code Duplication · Edited copy of a member (9 corresponding lines) kafka-connect-common/src/main/scala/io/lenses/streamreactor/connect/config/kcqlprops/KcqlProperties.scala
Code Duplication · Edited copy of a member (11 corresponding lines) kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/StructSql.scala
Code Duplication · Edited copy of a member (12 corresponding lines) kafka-connect-http/src/main/scala/io/lenses/streamreactor/connect/http/sink/metrics/MetricsResetter.scala
Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) java-connectors/kafka-connect-azure-eventhubs/src/main/java/io/lenses/streamreactor/connect/azure/eventhubs/util/KcqlConfigTopicMapper.java
Code Duplication · Edited copy of a member (14 corresponding lines) java-connectors/kafka-connect-gcp-common/src/main/java/io/lenses/streamreactor/connect/gcp/common/config/AuthModeSettings.java
Code Duplication · Edited copy of a member (12 corresponding lines) java-connectors/kafka-connect-query-language/src/main/java/io/lenses/kcql/Kcql.java
Code Duplication · Edited copy of a member (7 corresponding lines) kafka-connect-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/extractors/ArrayExtractor.scala
Code Duplication · Edited copy of a member (14 corresponding lines) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/GcpClientBuilder.java
Code Duplication · Edited copy of a member (8 corresponding lines) kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/sink/writer/CosmosDbQueueProcessor.scala
Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/formats/reader/converters/BytesOutputRowConverter.scala
Code Duplication · Edited copy of a member (11 corresponding lines) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/transformers/EnvelopeWithSchemaTransformer.scala
Code Duplication · Edited copy of a member (11 corresponding lines) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/write/batch/GCSBatchTableWriter.java
Code Duplication · Edited copy of a member (3 corresponding lines) kafka-connect-cassandra/src/main/scala/io/lenses/streamreactor/connect/cassandra/config/CassandraConfig.scala
Code Duplication · Edited copy of a member (8 corresponding lines) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/write/row/AdaptiveBigQueryWriter.java
Code Duplication · Edited copy of a member (3 corresponding lines) kafka-connect-aws-s3/src/main/scala/io/lenses/streamreactor/connect/aws/s3/storage/AwsS3StorageInterface.scala
Code Duplication · Edited copy of a member (10 corresponding lines) kafka-connect-cassandra-sink/src/main/scala/io/lenses/streamreactor/connect/cassandra/CassandraSinkConnector.scala
Code Duplication · Edited copy of a member (7 corresponding lines) kafka-connect-common/src/main/scala/io/lenses/streamreactor/connect/io/text/LineStartLineEndReader.scala
Code Duplication · Edited copy of a member (5 corresponding lines) kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/KElasticClient.scala
Code Duplication · Edited copy of a member (8 corresponding lines) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/write/row/AdaptiveBigQueryWriter.java
Code Duplication · Edited copy of a member (11 corresponding lines) test-common/src/main/scala/io/lenses/streamreactor/connect/testcontainers/connect/KafkaConnectClient.scala
Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) test-common/src/main/scala/io/lenses/streamreactor/connect/testcontainers/connect/KafkaConnectClient.scala
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 17 findings
These 17 critical or serious findings were in the previous survey, on 26 October 2026, and are gone from this one.
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Documentation (README) · README may be stale
Rebuild cost: about €240,000 · Estimate
Cost to rebuild
€80,000 to €400,000, for 1,335 to 4,234 hours of work, about 1.7 person-years for 1 to 4 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.9 at a score of 64. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 73,609 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.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
Raises the score by about 4 points · Medium effort · DR & Backup
3
On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`.
Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €240,000 to build again, about 1.7 person-years of work. Its weakest lens is Production Readiness, at 53 (Adequate). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
49 modules, with 88 dependencies between them. 5 loops run through 14 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 9 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
com.wepay.kafka.connect.bigquery.convert uses com.wepay.kafka.connect.bigquery.api, so a change to com.wepay.kafka.connect.bigquery.api can break com.wepay.kafka.connect.bigquery.convert, while a change to com.wepay.kafka.connect.bigquery.convert can't break com.wepay.kafka.connect.bigquery.api.
Position
Below the diagonal: com.wepay.kafka.connect.bigquery.convert uses a module listed above it, which is the healthy direction.
com.wepay.kafka.connect.bigquery.retrieve uses com.wepay.kafka.connect.bigquery.api, so a change to com.wepay.kafka.connect.bigquery.api can break com.wepay.kafka.connect.bigquery.retrieve, while a change to com.wepay.kafka.connect.bigquery.retrieve can't break com.wepay.kafka.connect.bigquery.api.
Position
Below the diagonal: com.wepay.kafka.connect.bigquery.retrieve uses a module listed above it, which is the healthy direction.
11→25 com.wepay.kafka.connect.bigquery.write.row uses com.wepay.kafka.connect.bigquery.utilspart of a loop✕
Connections
4 pairs of types, where a type in com.wepay.kafka.connect.bigquery.write.row uses a type in com.wepay.kafka.connect.bigquery.utils.
com.wepay.kafka.connect.bigquery.write.row uses com.wepay.kafka.connect.bigquery.utils, so a change to com.wepay.kafka.connect.bigquery.utils can break com.wepay.kafka.connect.bigquery.write.row, while a change to com.wepay.kafka.connect.bigquery.write.row can't break com.wepay.kafka.connect.bigquery.utils.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→32 com.wepay.kafka.connect.bigquery.write.row uses com.wepay.kafka.connect.bigquerypart of a loop✕
Connections
7 pairs of types, where a type in com.wepay.kafka.connect.bigquery.write.row uses a type in com.wepay.kafka.connect.bigquery.
com.wepay.kafka.connect.bigquery.write.row uses com.wepay.kafka.connect.bigquery, so a change to com.wepay.kafka.connect.bigquery can break com.wepay.kafka.connect.bigquery.write.row, while a change to com.wepay.kafka.connect.bigquery.write.row can't break com.wepay.kafka.connect.bigquery.
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→17 io.lenses.kcql.partitions uses io.lenses.kcqlpart of a loop✕
Connections
1 pair of types, where a type in io.lenses.kcql.partitions uses a type in io.lenses.kcql.
io.lenses.kcql.partitions uses io.lenses.kcql, so a change to io.lenses.kcql can break io.lenses.kcql.partitions, while a change to io.lenses.kcql.partitions can't break io.lenses.kcql.
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.
io.lenses.streamreactor.common.security uses io.lenses.streamreactor.common.exception, so a change to io.lenses.streamreactor.common.exception can break io.lenses.streamreactor.common.security, while a change to io.lenses.streamreactor.common.security can't break io.lenses.streamreactor.common.exception.
Position
Below the diagonal: io.lenses.streamreactor.common.security uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io.lenses.streamreactor.connect.gcp.pubsub.source.admin uses a type in io.lenses.streamreactor.connect.gcp.common.auth.mode.
io.lenses.streamreactor.connect.gcp.pubsub.source.admin uses io.lenses.streamreactor.connect.gcp.common.auth.mode, so a change to io.lenses.streamreactor.connect.gcp.common.auth.mode can break io.lenses.streamreactor.connect.gcp.pubsub.source.admin, while a change to io.lenses.streamreactor.connect.gcp.pubsub.source.admin can't break io.lenses.streamreactor.connect.gcp.common.auth.mode.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.pubsub.source.admin uses a module listed above it, which is the healthy direction.
15→19 io.lenses.streamreactor.connect.reporting.model uses io.lenses.streamreactor.connect.reportingpart of a loop✕
Connections
1 pair of types, where a type in io.lenses.streamreactor.connect.reporting.model uses a type in io.lenses.streamreactor.connect.reporting.
io.lenses.streamreactor.connect.reporting.model uses io.lenses.streamreactor.connect.reporting, so a change to io.lenses.streamreactor.connect.reporting can break io.lenses.streamreactor.connect.reporting.model, while a change to io.lenses.streamreactor.connect.reporting.model can't break io.lenses.streamreactor.connect.reporting.
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.
com.wepay.kafka.connect.bigquery.config uses com.wepay.kafka.connect.bigquery.api, so a change to com.wepay.kafka.connect.bigquery.api can break com.wepay.kafka.connect.bigquery.config, while a change to com.wepay.kafka.connect.bigquery.config can't break com.wepay.kafka.connect.bigquery.api.
Position
Below the diagonal: com.wepay.kafka.connect.bigquery.config uses a module listed above it, which is the healthy direction.
com.wepay.kafka.connect.bigquery.config uses com.wepay.kafka.connect.bigquery.convert, so a change to com.wepay.kafka.connect.bigquery.convert can break com.wepay.kafka.connect.bigquery.config, while a change to com.wepay.kafka.connect.bigquery.config can't break com.wepay.kafka.connect.bigquery.convert.
Position
Below the diagonal: com.wepay.kafka.connect.bigquery.config uses a module listed above it, which is the healthy direction.
16→32 com.wepay.kafka.connect.bigquery.config uses com.wepay.kafka.connect.bigquerypart of a loop✕
Connections
3 pairs of types, where a type in com.wepay.kafka.connect.bigquery.config uses a type in com.wepay.kafka.connect.bigquery.
com.wepay.kafka.connect.bigquery.config uses com.wepay.kafka.connect.bigquery, so a change to com.wepay.kafka.connect.bigquery can break com.wepay.kafka.connect.bigquery.config, while a change to com.wepay.kafka.connect.bigquery.config can't break com.wepay.kafka.connect.bigquery.
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.
io.lenses.kcql uses io.lenses.kcql.targettype, so a change to io.lenses.kcql.targettype can break io.lenses.kcql, while a change to io.lenses.kcql can't break io.lenses.kcql.targettype.
Position
Below the diagonal: io.lenses.kcql uses a module listed above it, which is the healthy direction.
io.lenses.kcql uses io.lenses.kcql.partitions, so a change to io.lenses.kcql.partitions can break io.lenses.kcql, while a change to io.lenses.kcql can't break io.lenses.kcql.partitions.
Position
Below the diagonal: io.lenses.kcql uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in io.lenses.streamreactor.connect.gcp.pubsub.source.subscriber uses a type in io.lenses.streamreactor.connect.gcp.pubsub.source.admin.
io.lenses.streamreactor.connect.gcp.pubsub.source.subscriber uses io.lenses.streamreactor.connect.gcp.pubsub.source.admin, so a change to io.lenses.streamreactor.connect.gcp.pubsub.source.admin can break io.lenses.streamreactor.connect.gcp.pubsub.source.subscriber, while a change to io.lenses.streamreactor.connect.gcp.pubsub.source.subscriber can't break io.lenses.streamreactor.connect.gcp.pubsub.source.admin.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.pubsub.source.subscriber uses a module listed above it, which is the healthy direction.
18→31 io.lenses.streamreactor.connect.gcp.pubsub.source.subscriber uses io.lenses.streamreactor.connect.gcp.pubsub.source.configpart of a loop✕
Connections
3 pairs of types, where a type in io.lenses.streamreactor.connect.gcp.pubsub.source.subscriber uses a type in io.lenses.streamreactor.connect.gcp.pubsub.source.config.
io.lenses.streamreactor.connect.gcp.pubsub.source.subscriber uses io.lenses.streamreactor.connect.gcp.pubsub.source.config, so a change to io.lenses.streamreactor.connect.gcp.pubsub.source.config can break io.lenses.streamreactor.connect.gcp.pubsub.source.subscriber, while a change to io.lenses.streamreactor.connect.gcp.pubsub.source.subscriber can't break io.lenses.streamreactor.connect.gcp.pubsub.source.config.
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.
io.lenses.streamreactor.connect.reporting uses io.lenses.streamreactor.common.config.source, so a change to io.lenses.streamreactor.common.config.source can break io.lenses.streamreactor.connect.reporting, while a change to io.lenses.streamreactor.connect.reporting can't break io.lenses.streamreactor.common.config.source.
Position
Below the diagonal: io.lenses.streamreactor.connect.reporting uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.connect.reporting uses io.lenses.streamreactor.common.exception, so a change to io.lenses.streamreactor.common.exception can break io.lenses.streamreactor.connect.reporting, while a change to io.lenses.streamreactor.connect.reporting can't break io.lenses.streamreactor.common.exception.
Position
Below the diagonal: io.lenses.streamreactor.connect.reporting uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.connect.reporting uses io.lenses.streamreactor.connect.reporting.model, so a change to io.lenses.streamreactor.connect.reporting.model can break io.lenses.streamreactor.connect.reporting, while a change to io.lenses.streamreactor.connect.reporting can't break io.lenses.streamreactor.connect.reporting.model.
Position
Below the diagonal: io.lenses.streamreactor.connect.reporting uses a module listed above it, which is the healthy direction.
com.wepay.kafka.connect.bigquery.write.batch uses com.wepay.kafka.connect.bigquery.write.row, so a change to com.wepay.kafka.connect.bigquery.write.row can break com.wepay.kafka.connect.bigquery.write.batch, while a change to com.wepay.kafka.connect.bigquery.write.batch can't break com.wepay.kafka.connect.bigquery.write.row.
Position
Below the diagonal: com.wepay.kafka.connect.bigquery.write.batch uses a module listed above it, which is the healthy direction.
com.wepay.kafka.connect.bigquery.write.batch uses com.wepay.kafka.connect.bigquery.config, so a change to com.wepay.kafka.connect.bigquery.config can break com.wepay.kafka.connect.bigquery.write.batch, while a change to com.wepay.kafka.connect.bigquery.write.batch can't break com.wepay.kafka.connect.bigquery.config.
Position
Below the diagonal: com.wepay.kafka.connect.bigquery.write.batch uses a module listed above it, which is the healthy direction.
20→25 com.wepay.kafka.connect.bigquery.write.batch uses com.wepay.kafka.connect.bigquery.utilspart of a loop✕
Connections
2 pairs of types, where a type in com.wepay.kafka.connect.bigquery.write.batch uses a type in com.wepay.kafka.connect.bigquery.utils.
com.wepay.kafka.connect.bigquery.write.batch uses com.wepay.kafka.connect.bigquery.utils, so a change to com.wepay.kafka.connect.bigquery.utils can break com.wepay.kafka.connect.bigquery.write.batch, while a change to com.wepay.kafka.connect.bigquery.write.batch can't break com.wepay.kafka.connect.bigquery.utils.
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.
io.lenses.streamreactor.common.config.base uses io.lenses.streamreactor.common.config.base.model, so a change to io.lenses.streamreactor.common.config.base.model can break io.lenses.streamreactor.common.config.base, while a change to io.lenses.streamreactor.common.config.base can't break io.lenses.streamreactor.common.config.base.model.
Position
Below the diagonal: io.lenses.streamreactor.common.config.base uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.common.config.base uses io.lenses.streamreactor.common.config.source, so a change to io.lenses.streamreactor.common.config.source can break io.lenses.streamreactor.common.config.base, while a change to io.lenses.streamreactor.common.config.base can't break io.lenses.streamreactor.common.config.source.
Position
Below the diagonal: io.lenses.streamreactor.common.config.base uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.common.config.base uses io.lenses.kcql, so a change to io.lenses.kcql can break io.lenses.streamreactor.common.config.base, while a change to io.lenses.streamreactor.common.config.base can't break io.lenses.kcql.
Position
Below the diagonal: io.lenses.streamreactor.common.config.base uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.common.validation.validators uses io.lenses.kcql, so a change to io.lenses.kcql can break io.lenses.streamreactor.common.validation.validators, while a change to io.lenses.streamreactor.common.validation.validators can't break io.lenses.kcql.
Position
Below the diagonal: io.lenses.streamreactor.common.validation.validators uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.connect.azure.servicebus.util uses io.lenses.streamreactor.common.exception, so a change to io.lenses.streamreactor.common.exception can break io.lenses.streamreactor.connect.azure.servicebus.util, while a change to io.lenses.streamreactor.connect.azure.servicebus.util can't break io.lenses.streamreactor.common.exception.
Position
Below the diagonal: io.lenses.streamreactor.connect.azure.servicebus.util uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.connect.azure.servicebus.util uses io.lenses.kcql, so a change to io.lenses.kcql can break io.lenses.streamreactor.connect.azure.servicebus.util, while a change to io.lenses.streamreactor.connect.azure.servicebus.util can't break io.lenses.kcql.
Position
Below the diagonal: io.lenses.streamreactor.connect.azure.servicebus.util uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io.lenses.streamreactor.connect.gcp.pubsub.source.mapping uses a type in io.lenses.streamreactor.common.config.base.intf.
io.lenses.streamreactor.connect.gcp.pubsub.source.mapping uses io.lenses.streamreactor.common.config.base.intf, so a change to io.lenses.streamreactor.common.config.base.intf can break io.lenses.streamreactor.connect.gcp.pubsub.source.mapping, while a change to io.lenses.streamreactor.connect.gcp.pubsub.source.mapping can't break io.lenses.streamreactor.common.config.base.intf.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.pubsub.source.mapping uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io.lenses.streamreactor.connect.gcp.pubsub.source.mapping uses a type in io.lenses.streamreactor.connect.gcp.pubsub.source.subscriber.
io.lenses.streamreactor.connect.gcp.pubsub.source.mapping uses io.lenses.streamreactor.connect.gcp.pubsub.source.subscriber, so a change to io.lenses.streamreactor.connect.gcp.pubsub.source.subscriber can break io.lenses.streamreactor.connect.gcp.pubsub.source.mapping, while a change to io.lenses.streamreactor.connect.gcp.pubsub.source.mapping can't break io.lenses.streamreactor.connect.gcp.pubsub.source.subscriber.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.pubsub.source.mapping uses a module listed above it, which is the healthy direction.
com.wepay.kafka.connect.bigquery.utils uses com.wepay.kafka.connect.bigquery.convert, so a change to com.wepay.kafka.connect.bigquery.convert can break com.wepay.kafka.connect.bigquery.utils, while a change to com.wepay.kafka.connect.bigquery.utils can't break com.wepay.kafka.connect.bigquery.convert.
Position
Below the diagonal: com.wepay.kafka.connect.bigquery.utils uses a module listed above it, which is the healthy direction.
com.wepay.kafka.connect.bigquery.utils uses com.wepay.kafka.connect.bigquery.config, so a change to com.wepay.kafka.connect.bigquery.config can break com.wepay.kafka.connect.bigquery.utils, while a change to com.wepay.kafka.connect.bigquery.utils can't break com.wepay.kafka.connect.bigquery.config.
Position
Below the diagonal: com.wepay.kafka.connect.bigquery.utils uses a module listed above it, which is the healthy direction.
com.wepay.kafka.connect.bigquery.utils uses com.wepay.kafka.connect.bigquery.write.batch, so a change to com.wepay.kafka.connect.bigquery.write.batch can break com.wepay.kafka.connect.bigquery.utils, while a change to com.wepay.kafka.connect.bigquery.utils can't break com.wepay.kafka.connect.bigquery.write.batch.
Position
Below the diagonal: com.wepay.kafka.connect.bigquery.utils uses a module listed above it, which is the healthy direction.
25→32 com.wepay.kafka.connect.bigquery.utils uses com.wepay.kafka.connect.bigquerypart of a loop✕
Connections
1 pair of types, where a type in com.wepay.kafka.connect.bigquery.utils uses a type in com.wepay.kafka.connect.bigquery.
com.wepay.kafka.connect.bigquery.utils uses com.wepay.kafka.connect.bigquery, so a change to com.wepay.kafka.connect.bigquery can break com.wepay.kafka.connect.bigquery.utils, while a change to com.wepay.kafka.connect.bigquery.utils can't break com.wepay.kafka.connect.bigquery.
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.
io.lenses.streamreactor.common.util uses io.lenses.streamreactor.common.exception, so a change to io.lenses.streamreactor.common.exception can break io.lenses.streamreactor.common.util, while a change to io.lenses.streamreactor.common.util can't break io.lenses.streamreactor.common.exception.
Position
Below the diagonal: io.lenses.streamreactor.common.util uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.common.util uses io.lenses.streamreactor.common.config.base, so a change to io.lenses.streamreactor.common.config.base can break io.lenses.streamreactor.common.util, while a change to io.lenses.streamreactor.common.util can't break io.lenses.streamreactor.common.config.base.
Position
Below the diagonal: io.lenses.streamreactor.common.util uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.common.validation uses io.lenses.streamreactor.common.exception, so a change to io.lenses.streamreactor.common.exception can break io.lenses.streamreactor.common.validation, while a change to io.lenses.streamreactor.common.validation can't break io.lenses.streamreactor.common.exception.
Position
Below the diagonal: io.lenses.streamreactor.common.validation uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.common.validation uses io.lenses.kcql, so a change to io.lenses.kcql can break io.lenses.streamreactor.common.validation, while a change to io.lenses.streamreactor.common.validation can't break io.lenses.kcql.
Position
Below the diagonal: io.lenses.streamreactor.common.validation uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.common.validation uses io.lenses.streamreactor.common.validation.validators, so a change to io.lenses.streamreactor.common.validation.validators can break io.lenses.streamreactor.common.validation, while a change to io.lenses.streamreactor.common.validation can't break io.lenses.streamreactor.common.validation.validators.
Position
Below the diagonal: io.lenses.streamreactor.common.validation uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io.lenses.streamreactor.connect.azure.eventhubs.config uses a type in io.lenses.streamreactor.common.config.base.intf.
io.lenses.streamreactor.connect.azure.eventhubs.config uses io.lenses.streamreactor.common.config.base.intf, so a change to io.lenses.streamreactor.common.config.base.intf can break io.lenses.streamreactor.connect.azure.eventhubs.config, while a change to io.lenses.streamreactor.connect.azure.eventhubs.config can't break io.lenses.streamreactor.common.config.base.intf.
Position
Below the diagonal: io.lenses.streamreactor.connect.azure.eventhubs.config uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.connect.azure.eventhubs.config uses io.lenses.streamreactor.common.config.base, so a change to io.lenses.streamreactor.common.config.base can break io.lenses.streamreactor.connect.azure.eventhubs.config, while a change to io.lenses.streamreactor.connect.azure.eventhubs.config can't break io.lenses.streamreactor.common.config.base.
Position
Below the diagonal: io.lenses.streamreactor.connect.azure.eventhubs.config uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in io.lenses.streamreactor.connect.azure.servicebus.config uses a type in io.lenses.streamreactor.common.config.base.intf.
io.lenses.streamreactor.connect.azure.servicebus.config uses io.lenses.streamreactor.common.config.base.intf, so a change to io.lenses.streamreactor.common.config.base.intf can break io.lenses.streamreactor.connect.azure.servicebus.config, while a change to io.lenses.streamreactor.connect.azure.servicebus.config can't break io.lenses.streamreactor.common.config.base.intf.
Position
Below the diagonal: io.lenses.streamreactor.connect.azure.servicebus.config uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.connect.azure.servicebus.config uses io.lenses.streamreactor.common.config.base, so a change to io.lenses.streamreactor.common.config.base can break io.lenses.streamreactor.connect.azure.servicebus.config, while a change to io.lenses.streamreactor.connect.azure.servicebus.config can't break io.lenses.streamreactor.common.config.base.
Position
Below the diagonal: io.lenses.streamreactor.connect.azure.servicebus.config uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.connect.gcp.common.auth uses io.lenses.streamreactor.common.config.base.intf, so a change to io.lenses.streamreactor.common.config.base.intf can break io.lenses.streamreactor.connect.gcp.common.auth, while a change to io.lenses.streamreactor.connect.gcp.common.auth can't break io.lenses.streamreactor.common.config.base.intf.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.common.auth uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.connect.gcp.common.auth uses io.lenses.streamreactor.connect.gcp.common.auth.mode, so a change to io.lenses.streamreactor.connect.gcp.common.auth.mode can break io.lenses.streamreactor.connect.gcp.common.auth, while a change to io.lenses.streamreactor.connect.gcp.common.auth can't break io.lenses.streamreactor.connect.gcp.common.auth.mode.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.common.auth uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.connect.gcp.common.auth uses io.lenses.streamreactor.common.config.base, so a change to io.lenses.streamreactor.common.config.base can break io.lenses.streamreactor.connect.gcp.common.auth, while a change to io.lenses.streamreactor.connect.gcp.common.auth can't break io.lenses.streamreactor.common.config.base.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.common.auth uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io.lenses.streamreactor.connect.gcp.pubsub.source.config uses a type in io.lenses.streamreactor.connect.gcp.common.auth.mode.
io.lenses.streamreactor.connect.gcp.pubsub.source.config uses io.lenses.streamreactor.connect.gcp.common.auth.mode, so a change to io.lenses.streamreactor.connect.gcp.common.auth.mode can break io.lenses.streamreactor.connect.gcp.pubsub.source.config, while a change to io.lenses.streamreactor.connect.gcp.pubsub.source.config can't break io.lenses.streamreactor.connect.gcp.common.auth.mode.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.pubsub.source.config uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.connect.gcp.pubsub.source.config uses io.lenses.kcql, so a change to io.lenses.kcql can break io.lenses.streamreactor.connect.gcp.pubsub.source.config, while a change to io.lenses.streamreactor.connect.gcp.pubsub.source.config can't break io.lenses.kcql.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.pubsub.source.config uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io.lenses.streamreactor.connect.gcp.pubsub.source.config uses a type in io.lenses.streamreactor.connect.gcp.pubsub.source.mapping.
io.lenses.streamreactor.connect.gcp.pubsub.source.config uses io.lenses.streamreactor.connect.gcp.pubsub.source.mapping, so a change to io.lenses.streamreactor.connect.gcp.pubsub.source.mapping can break io.lenses.streamreactor.connect.gcp.pubsub.source.config, while a change to io.lenses.streamreactor.connect.gcp.pubsub.source.config can't break io.lenses.streamreactor.connect.gcp.pubsub.source.mapping.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.pubsub.source.config uses a module listed above it, which is the healthy direction.
com.wepay.kafka.connect.bigquery uses com.wepay.kafka.connect.bigquery.api, so a change to com.wepay.kafka.connect.bigquery.api can break com.wepay.kafka.connect.bigquery, while a change to com.wepay.kafka.connect.bigquery can't break com.wepay.kafka.connect.bigquery.api.
Position
Below the diagonal: com.wepay.kafka.connect.bigquery uses a module listed above it, which is the healthy direction.
com.wepay.kafka.connect.bigquery uses com.wepay.kafka.connect.bigquery.convert, so a change to com.wepay.kafka.connect.bigquery.convert can break com.wepay.kafka.connect.bigquery, while a change to com.wepay.kafka.connect.bigquery can't break com.wepay.kafka.connect.bigquery.convert.
Position
Below the diagonal: com.wepay.kafka.connect.bigquery uses a module listed above it, which is the healthy direction.
com.wepay.kafka.connect.bigquery uses com.wepay.kafka.connect.bigquery.write.row, so a change to com.wepay.kafka.connect.bigquery.write.row can break com.wepay.kafka.connect.bigquery, while a change to com.wepay.kafka.connect.bigquery can't break com.wepay.kafka.connect.bigquery.write.row.
Position
Below the diagonal: com.wepay.kafka.connect.bigquery uses a module listed above it, which is the healthy direction.
com.wepay.kafka.connect.bigquery uses com.wepay.kafka.connect.bigquery.config, so a change to com.wepay.kafka.connect.bigquery.config can break com.wepay.kafka.connect.bigquery, while a change to com.wepay.kafka.connect.bigquery can't break com.wepay.kafka.connect.bigquery.config.
Position
Below the diagonal: com.wepay.kafka.connect.bigquery uses a module listed above it, which is the healthy direction.
com.wepay.kafka.connect.bigquery uses com.wepay.kafka.connect.bigquery.write.batch, so a change to com.wepay.kafka.connect.bigquery.write.batch can break com.wepay.kafka.connect.bigquery, while a change to com.wepay.kafka.connect.bigquery can't break com.wepay.kafka.connect.bigquery.write.batch.
Position
Below the diagonal: com.wepay.kafka.connect.bigquery uses a module listed above it, which is the healthy direction.
com.wepay.kafka.connect.bigquery uses com.wepay.kafka.connect.bigquery.utils, so a change to com.wepay.kafka.connect.bigquery.utils can break com.wepay.kafka.connect.bigquery, while a change to com.wepay.kafka.connect.bigquery can't break com.wepay.kafka.connect.bigquery.utils.
Position
Below the diagonal: com.wepay.kafka.connect.bigquery uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.connect.azure.eventhubs.source uses io.lenses.streamreactor.common.util, so a change to io.lenses.streamreactor.common.util can break io.lenses.streamreactor.connect.azure.eventhubs.source, while a change to io.lenses.streamreactor.connect.azure.eventhubs.source can't break io.lenses.streamreactor.common.util.
Position
Below the diagonal: io.lenses.streamreactor.connect.azure.eventhubs.source uses a module listed above it, which is the healthy direction.
5 pairs of types, where a type in io.lenses.streamreactor.connect.azure.eventhubs.source uses a type in io.lenses.streamreactor.connect.azure.eventhubs.config.
io.lenses.streamreactor.connect.azure.eventhubs.source uses io.lenses.streamreactor.connect.azure.eventhubs.config, so a change to io.lenses.streamreactor.connect.azure.eventhubs.config can break io.lenses.streamreactor.connect.azure.eventhubs.source, while a change to io.lenses.streamreactor.connect.azure.eventhubs.source can't break io.lenses.streamreactor.connect.azure.eventhubs.config.
Position
Below the diagonal: io.lenses.streamreactor.connect.azure.eventhubs.source uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.connect.azure.eventhubs.util uses io.lenses.streamreactor.common.exception, so a change to io.lenses.streamreactor.common.exception can break io.lenses.streamreactor.connect.azure.eventhubs.util, while a change to io.lenses.streamreactor.connect.azure.eventhubs.util can't break io.lenses.streamreactor.common.exception.
Position
Below the diagonal: io.lenses.streamreactor.connect.azure.eventhubs.util uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.connect.azure.eventhubs.util uses io.lenses.kcql, so a change to io.lenses.kcql can break io.lenses.streamreactor.connect.azure.eventhubs.util, while a change to io.lenses.streamreactor.connect.azure.eventhubs.util can't break io.lenses.kcql.
Position
Below the diagonal: io.lenses.streamreactor.connect.azure.eventhubs.util uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.connect.azure.eventhubs.util uses io.lenses.streamreactor.common.validation, so a change to io.lenses.streamreactor.common.validation can break io.lenses.streamreactor.connect.azure.eventhubs.util, while a change to io.lenses.streamreactor.connect.azure.eventhubs.util can't break io.lenses.streamreactor.common.validation.
Position
Below the diagonal: io.lenses.streamreactor.connect.azure.eventhubs.util uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.connect.azure.servicebus.sink uses io.lenses.streamreactor.common.collections, so a change to io.lenses.streamreactor.common.collections can break io.lenses.streamreactor.connect.azure.servicebus.sink, while a change to io.lenses.streamreactor.connect.azure.servicebus.sink can't break io.lenses.streamreactor.common.collections.
Position
Below the diagonal: io.lenses.streamreactor.connect.azure.servicebus.sink uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.connect.azure.servicebus.sink uses io.lenses.streamreactor.common.exception, so a change to io.lenses.streamreactor.common.exception can break io.lenses.streamreactor.connect.azure.servicebus.sink, while a change to io.lenses.streamreactor.connect.azure.servicebus.sink can't break io.lenses.streamreactor.common.exception.
Position
Below the diagonal: io.lenses.streamreactor.connect.azure.servicebus.sink uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io.lenses.streamreactor.connect.azure.servicebus.sink uses a type in io.lenses.streamreactor.connect.azure.servicebus.util.
io.lenses.streamreactor.connect.azure.servicebus.sink uses io.lenses.streamreactor.connect.azure.servicebus.util, so a change to io.lenses.streamreactor.connect.azure.servicebus.util can break io.lenses.streamreactor.connect.azure.servicebus.sink, while a change to io.lenses.streamreactor.connect.azure.servicebus.sink can't break io.lenses.streamreactor.connect.azure.servicebus.util.
Position
Below the diagonal: io.lenses.streamreactor.connect.azure.servicebus.sink uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.connect.azure.servicebus.sink uses io.lenses.streamreactor.common.util, so a change to io.lenses.streamreactor.common.util can break io.lenses.streamreactor.connect.azure.servicebus.sink, while a change to io.lenses.streamreactor.connect.azure.servicebus.sink can't break io.lenses.streamreactor.common.util.
Position
Below the diagonal: io.lenses.streamreactor.connect.azure.servicebus.sink uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io.lenses.streamreactor.connect.azure.servicebus.sink uses a type in io.lenses.streamreactor.connect.azure.servicebus.config.
io.lenses.streamreactor.connect.azure.servicebus.sink uses io.lenses.streamreactor.connect.azure.servicebus.config, so a change to io.lenses.streamreactor.connect.azure.servicebus.config can break io.lenses.streamreactor.connect.azure.servicebus.sink, while a change to io.lenses.streamreactor.connect.azure.servicebus.sink can't break io.lenses.streamreactor.connect.azure.servicebus.config.
Position
Below the diagonal: io.lenses.streamreactor.connect.azure.servicebus.sink uses a module listed above it, which is the healthy direction.
35→38 io.lenses.streamreactor.connect.azure.servicebus.sink uses io.lenses.streamreactor.connect.azure.servicebus.mappingpart of a loop✕
Connections
2 pairs of types, where a type in io.lenses.streamreactor.connect.azure.servicebus.sink uses a type in io.lenses.streamreactor.connect.azure.servicebus.mapping.
io.lenses.streamreactor.connect.azure.servicebus.sink uses io.lenses.streamreactor.connect.azure.servicebus.mapping, so a change to io.lenses.streamreactor.connect.azure.servicebus.mapping can break io.lenses.streamreactor.connect.azure.servicebus.sink, while a change to io.lenses.streamreactor.connect.azure.servicebus.sink can't break io.lenses.streamreactor.connect.azure.servicebus.mapping.
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.
io.lenses.streamreactor.connect.azure.servicebus.source uses io.lenses.kcql, so a change to io.lenses.kcql can break io.lenses.streamreactor.connect.azure.servicebus.source, while a change to io.lenses.streamreactor.connect.azure.servicebus.source can't break io.lenses.kcql.
Position
Below the diagonal: io.lenses.streamreactor.connect.azure.servicebus.source uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.connect.azure.servicebus.source uses io.lenses.streamreactor.common.util, so a change to io.lenses.streamreactor.common.util can break io.lenses.streamreactor.connect.azure.servicebus.source, while a change to io.lenses.streamreactor.connect.azure.servicebus.source can't break io.lenses.streamreactor.common.util.
Position
Below the diagonal: io.lenses.streamreactor.connect.azure.servicebus.source uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.connect.gcp.common.config uses io.lenses.streamreactor.common.config.base.model, so a change to io.lenses.streamreactor.common.config.base.model can break io.lenses.streamreactor.connect.gcp.common.config, while a change to io.lenses.streamreactor.connect.gcp.common.config can't break io.lenses.streamreactor.common.config.base.model.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.common.config uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.connect.gcp.common.config uses io.lenses.streamreactor.common.config.source, so a change to io.lenses.streamreactor.common.config.source can break io.lenses.streamreactor.connect.gcp.common.config, while a change to io.lenses.streamreactor.connect.gcp.common.config can't break io.lenses.streamreactor.common.config.source.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.common.config uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io.lenses.streamreactor.connect.gcp.common.config uses a type in io.lenses.streamreactor.connect.gcp.common.auth.mode.
io.lenses.streamreactor.connect.gcp.common.config uses io.lenses.streamreactor.connect.gcp.common.auth.mode, so a change to io.lenses.streamreactor.connect.gcp.common.auth.mode can break io.lenses.streamreactor.connect.gcp.common.config, while a change to io.lenses.streamreactor.connect.gcp.common.config can't break io.lenses.streamreactor.connect.gcp.common.auth.mode.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.common.config uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.connect.gcp.common.config uses io.lenses.streamreactor.common.config.base, so a change to io.lenses.streamreactor.common.config.base can break io.lenses.streamreactor.connect.gcp.common.config, while a change to io.lenses.streamreactor.connect.gcp.common.config can't break io.lenses.streamreactor.common.config.base.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.common.config uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.connect.gcp.common.config uses io.lenses.streamreactor.connect.gcp.common.auth, so a change to io.lenses.streamreactor.connect.gcp.common.auth can break io.lenses.streamreactor.connect.gcp.common.config, while a change to io.lenses.streamreactor.connect.gcp.common.config can't break io.lenses.streamreactor.connect.gcp.common.auth.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.common.config uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io.lenses.streamreactor.connect.azure.servicebus.mapping uses a type in io.lenses.streamreactor.connect.azure.servicebus.sink.
io.lenses.streamreactor.connect.azure.servicebus.mapping uses io.lenses.streamreactor.connect.azure.servicebus.sink, so a change to io.lenses.streamreactor.connect.azure.servicebus.sink can break io.lenses.streamreactor.connect.azure.servicebus.mapping, while a change to io.lenses.streamreactor.connect.azure.servicebus.mapping can't break io.lenses.streamreactor.connect.azure.servicebus.sink.
Position
Below the diagonal: io.lenses.streamreactor.connect.azure.servicebus.mapping uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in io.lenses.streamreactor.connect.gcp.pubsub.source.configdef uses a type in io.lenses.streamreactor.common.config.base.model.
io.lenses.streamreactor.connect.gcp.pubsub.source.configdef uses io.lenses.streamreactor.common.config.base.model, so a change to io.lenses.streamreactor.common.config.base.model can break io.lenses.streamreactor.connect.gcp.pubsub.source.configdef, while a change to io.lenses.streamreactor.connect.gcp.pubsub.source.configdef can't break io.lenses.streamreactor.common.config.base.model.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.pubsub.source.configdef uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in io.lenses.streamreactor.connect.gcp.pubsub.source.configdef uses a type in io.lenses.streamreactor.common.config.source.
io.lenses.streamreactor.connect.gcp.pubsub.source.configdef uses io.lenses.streamreactor.common.config.source, so a change to io.lenses.streamreactor.common.config.source can break io.lenses.streamreactor.connect.gcp.pubsub.source.configdef, while a change to io.lenses.streamreactor.connect.gcp.pubsub.source.configdef can't break io.lenses.streamreactor.common.config.source.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.pubsub.source.configdef uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in io.lenses.streamreactor.connect.gcp.pubsub.source.configdef uses a type in io.lenses.streamreactor.common.config.base.
io.lenses.streamreactor.connect.gcp.pubsub.source.configdef uses io.lenses.streamreactor.common.config.base, so a change to io.lenses.streamreactor.common.config.base can break io.lenses.streamreactor.connect.gcp.pubsub.source.configdef, while a change to io.lenses.streamreactor.connect.gcp.pubsub.source.configdef can't break io.lenses.streamreactor.common.config.base.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.pubsub.source.configdef uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in io.lenses.streamreactor.connect.gcp.pubsub.source.configdef uses a type in io.lenses.streamreactor.connect.gcp.pubsub.source.config.
io.lenses.streamreactor.connect.gcp.pubsub.source.configdef uses io.lenses.streamreactor.connect.gcp.pubsub.source.config, so a change to io.lenses.streamreactor.connect.gcp.pubsub.source.config can break io.lenses.streamreactor.connect.gcp.pubsub.source.configdef, while a change to io.lenses.streamreactor.connect.gcp.pubsub.source.configdef can't break io.lenses.streamreactor.connect.gcp.pubsub.source.config.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.pubsub.source.configdef uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io.lenses.streamreactor.connect.gcp.pubsub.source.configdef uses a type in io.lenses.streamreactor.connect.gcp.common.config.
io.lenses.streamreactor.connect.gcp.pubsub.source.configdef uses io.lenses.streamreactor.connect.gcp.common.config, so a change to io.lenses.streamreactor.connect.gcp.common.config can break io.lenses.streamreactor.connect.gcp.pubsub.source.configdef, while a change to io.lenses.streamreactor.connect.gcp.pubsub.source.configdef can't break io.lenses.streamreactor.connect.gcp.common.config.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.pubsub.source.configdef uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io.lenses.streamreactor.connect.gcp.pubsub.source uses a type in io.lenses.streamreactor.connect.gcp.pubsub.source.admin.
io.lenses.streamreactor.connect.gcp.pubsub.source uses io.lenses.streamreactor.connect.gcp.pubsub.source.admin, so a change to io.lenses.streamreactor.connect.gcp.pubsub.source.admin can break io.lenses.streamreactor.connect.gcp.pubsub.source, while a change to io.lenses.streamreactor.connect.gcp.pubsub.source can't break io.lenses.streamreactor.connect.gcp.pubsub.source.admin.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.pubsub.source uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.connect.gcp.pubsub.source uses io.lenses.kcql, so a change to io.lenses.kcql can break io.lenses.streamreactor.connect.gcp.pubsub.source, while a change to io.lenses.streamreactor.connect.gcp.pubsub.source can't break io.lenses.kcql.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.pubsub.source uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io.lenses.streamreactor.connect.gcp.pubsub.source uses a type in io.lenses.streamreactor.connect.gcp.pubsub.source.subscriber.
io.lenses.streamreactor.connect.gcp.pubsub.source uses io.lenses.streamreactor.connect.gcp.pubsub.source.subscriber, so a change to io.lenses.streamreactor.connect.gcp.pubsub.source.subscriber can break io.lenses.streamreactor.connect.gcp.pubsub.source, while a change to io.lenses.streamreactor.connect.gcp.pubsub.source can't break io.lenses.streamreactor.connect.gcp.pubsub.source.subscriber.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.pubsub.source uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io.lenses.streamreactor.connect.gcp.pubsub.source uses a type in io.lenses.streamreactor.connect.gcp.pubsub.source.mapping.
io.lenses.streamreactor.connect.gcp.pubsub.source uses io.lenses.streamreactor.connect.gcp.pubsub.source.mapping, so a change to io.lenses.streamreactor.connect.gcp.pubsub.source.mapping can break io.lenses.streamreactor.connect.gcp.pubsub.source, while a change to io.lenses.streamreactor.connect.gcp.pubsub.source can't break io.lenses.streamreactor.connect.gcp.pubsub.source.mapping.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.pubsub.source uses a module listed above it, which is the healthy direction.
io.lenses.streamreactor.connect.gcp.pubsub.source uses io.lenses.streamreactor.common.util, so a change to io.lenses.streamreactor.common.util can break io.lenses.streamreactor.connect.gcp.pubsub.source, while a change to io.lenses.streamreactor.connect.gcp.pubsub.source can't break io.lenses.streamreactor.common.util.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.pubsub.source uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in io.lenses.streamreactor.connect.gcp.pubsub.source uses a type in io.lenses.streamreactor.connect.gcp.pubsub.source.config.
io.lenses.streamreactor.connect.gcp.pubsub.source uses io.lenses.streamreactor.connect.gcp.pubsub.source.config, so a change to io.lenses.streamreactor.connect.gcp.pubsub.source.config can break io.lenses.streamreactor.connect.gcp.pubsub.source, while a change to io.lenses.streamreactor.connect.gcp.pubsub.source can't break io.lenses.streamreactor.connect.gcp.pubsub.source.config.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.pubsub.source uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in io.lenses.streamreactor.connect.gcp.pubsub.source uses a type in io.lenses.streamreactor.connect.gcp.pubsub.source.configdef.
io.lenses.streamreactor.connect.gcp.pubsub.source uses io.lenses.streamreactor.connect.gcp.pubsub.source.configdef, so a change to io.lenses.streamreactor.connect.gcp.pubsub.source.configdef can break io.lenses.streamreactor.connect.gcp.pubsub.source, while a change to io.lenses.streamreactor.connect.gcp.pubsub.source can't break io.lenses.streamreactor.connect.gcp.pubsub.source.configdef.
Position
Below the diagonal: io.lenses.streamreactor.connect.gcp.pubsub.source uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 65% · Adequate · gated by X5 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
91
High / Critical
A03:2025 — Software Supply Chain Failures
28
High / Critical
A02:2025 — Security Misconfiguration
5
Medium
Roadmap
Top priorities: Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery); On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
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.
Bring the 25 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with SinkRecordConverter.fromStruct (cyclomatic 45), OpenSearchSettings.apply (cyclomatic 43), Transform.apply (cyclomatic 35).
Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 105
A definite problem that already costs you something and drags the score down: a
missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here
tends to cause failures elsewhere.
Serious — 299
Likely wrong, but not failing yet. It degrades
the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to
carry for two years either.
Minor — 232
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 13
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 58 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 58 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 624 of 636 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git 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.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.scala, .java) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala, .java) and this repository declares an sbt build (repository root, 476 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. Not scored — 13 Maven/Gradle manifest(s) were read, stating a version for 2 dependency(ies) and leaving 23 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares an sbt build (build.sbt), but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its sbt dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D19 Documentation Quality — 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. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: 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.
D28 Secrets (history) — 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. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `kafka-connect-aws-s3/src/it/resources/json/1.json`, `kafka-connect-aws-s3/src/it/resources/json/2.json`, `kafka-connect-aws-s3/src/it/resources/json/3.json`, `kafka-connect-aws-s3/src/it/resources/json/4.json`, `kafka-connect-aws-s3/src/it/resources/json/5.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
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 1 — a container did not start, exited, or never became healthy) — Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error setting rlimits for ready process: error setting rlimit type 8: operation not permitted: unknown; 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. 'com.mongodb' is imported (kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/sink/MongoWriter.scala:27), 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. 'com.mongodb' is imported (kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/sink/MongoWriter.scala:27), 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. 'com.mongodb' is imported (kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/sink/MongoWriter.scala:27), 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.
DM8 Value-object opportunities — 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 finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
DM9 Scattered domain decisions — 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. Arm one resolves each comparison operand to the domain member it judges, and that binding exists only in a Roslyn compilation, which this run did not load. Arm two ran over the neutral model because this repository's frontend declares whether each construction is produced or passed. A rule decided in two places would not appear above.
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.
X12 Unreachable branch — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X17 Uncapped recursion over a caller-supplied document — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
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.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
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".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
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.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
25 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SinkRecordConverter.fromStruct at 45. A further 11 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 ValueToSinkDataConverter.apply at 23 — they are counted neither in the figure above nor in this dimension's score. 6 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: kafka-connect-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/conversion/ValueToSinkDataConverter.scala (ValueToSinkDataConverter.apply at 23), kafka-connect-cassandra/src/main/scala/io/lenses/streamreactor/connect/cassandra/source/CassandraTypeConverter.scala (CassandraTypeConverter.mapTypes at 21), kafka-connect-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/extractors/KafkaConnectExtractor.scala (KafkaConnectExtractor.extract at 20), kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/JsonPayloadExtractor.scala (JsonPayloadExtractor.handleSchemaLess at 18), java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/convert/BigQueryRecordConverter.java (BigQueryRecordConverter.convertObject at 16), and 1 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 20 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 25 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with SinkRecordConverter.fromStruct (cyclomatic 45), OpenSearchSettings.apply (cyclomatic 43), Transform.apply (cyclomatic 35). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 25 together lifts Cyclomatic Complexity from 6.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 64 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 6 bodies over 60 down to 60 or less in Cognitive Complexity — start with SinkRecordConverter.fromStruct (cognitive 109), CloudSinkBucketOptions.apply (cognitive 91), Transform.apply (cognitive 67). — 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 Cognitive Complexity from 5.9 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.5 / 10Stronggated by 12 serious findings✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 5 ClassTooLong finding(s) in God Classes — start with BigQuerySinkConfig.java, Kcql.java, SchemaManager.java. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 3 TooManyMethods finding(s) in God Classes — start with CloudSinkMetricsMBean.scala, Kcql.java, IndexManagerV2.scala. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 MethodTooLong finding(s) in God Classes — start with BigQuerySinkConfig.java, Kcql.java. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
65 duplicated block group(s) detected. 4.0 % of the production lines (2,930 of 73,609) are in a reported copy. A further 58 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 2 of the 123 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
Edited copy of a member (14 corresponding lines) · ×4java-connectors/kafka-connect-query-language/src/main/java/io/lenses/kcql/Kcql.java:560
Edited copy of a member (12 corresponding lines) · ×4kafka-connect-azure-datalake/src/main/scala/io/lenses/streamreactor/connect/datalake/storage/DatalakeStorageInterface.scala:196
+ 68 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 6 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with SinkRecordConverter.scala, AddConnectSchemaTransformer.scala, IndexManagerV2.scala. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 5 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with REDACTED (3), ToJsonWithProjections.scala (2). — One of this dimension's main actionable groups (5 warning-level).
Resolve the 5 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with DatalakeStorageInterface.scala, FlushSettings.scala, ConfigParse.scala. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.8 / 10Stronggated by 1 serious finding✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
37 production modules (Gradle+Maven+sbt), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 2 module(s) off the main sequence, with abstractness counted on 28 of the 37 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: :kafka-connect-query-language
Off the main sequence: common
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with GCPStorageStorageInterface.scala, DatalakeStorageInterface.scala, KOpenSearchClient.scala. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Secret scan ran and found no leaked secrets. 3 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 2 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 13 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 23 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares an sbt build (build.sbt), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: REDACTED (4×43=172); kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/WriterManagerCreator.scala (2×19=38)
Hotspot: REDACTED · ×2REDACTED:62
What to do
Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED, WriterManagerCreator.scala. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor8.8 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
46 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/seek/IndexManagerV2.scala. Counted over 402 of the 816 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1 · ×2
Further sole-owners (lower concentration)
What to do
Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
41 deducted task-comment markers across 73609 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 39 TodoComment finding(s) in Explicit Debt — start with ITSampleSchemaAndData.scala (3), CoreSinkTaskTestCases.scala (3), BigQueryErrorResponses.java (3). — One of this dimension's main actionable groups (39 warning-level).
Resolve the 2 FixmeComment finding(s) in Explicit Debt — start with MongoWriterTest.scala, PartitionDiscovery.scala. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 13 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
1 of 10 build units (Gradle, Maven, sbt) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
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).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
91 finding(s): 0 critical, 89 high, 1 medium, 1 low. 71 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 6 file(s) — `java-connectors/gradlew` (line 72, line 178), `kafka-connect-aws-s3/src/it/resources/json/1.json`, `kafka-connect-aws-s3/src/it/resources/json/2.json`, `kafka-connect-aws-s3/src/it/resources/json/3.json`, `kafka-connect-aws-s3/src/it/resources/json/4.json`, … (+1 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. 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 5 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (12 issue-level).
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
No action in Static Analysis (SAST) — all 70 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 (70 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 9 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (9). — One of this dimension's main actionable groups (9 issue-level).
Resolve the 8 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8). — One of this dimension's main actionable groups (8 warning-level).
Resolve the 4 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 5 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
200 of 402 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is java-connectors/kafka-connect-query-language/src/main/java/io/lenses/kcql/Kcql.java. Counted over 402 of the 816 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 198 Orphaned file finding(s) in Knowledge Freshness — start with SinkRecordConverter.scala (2), SinkRecordToDocument.scala (2), KElasticClient.scala (2). — One of this dimension's main actionable groups (198 recommendation-level).
Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with Kcql.java, CassandraTableReader.scala. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with S3SinkConfig.scala. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Change coupling finding(s) in Change Coupling — start with ErrantRecordHandler.scala. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 6 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.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`CloudSinkMetricsMBean` declares 71 abstract members: `getWriterCount`, `getIdleWriterEvictions`, `getGranularCacheSize`, `getGranularCacheHits`, `getGranularCacheMisses`, `getGcQueueDepth`, `getGcLocksEnqueued`, `getGcLocksDeleted`, `getGcLocksSkippedReclaimed`, `getGcLocksSkippedRevoked`, `getGcDeleteFailures`, `getGcDeleteRetries`, `getMasterLockUpdates`, `getMasterLockFailures`, `getMasterLockWriteSkipped`, `getMasterLockWriteForcedRevoke`, `getMasterLockWriteForcedStop`, `getMasterLockWriteForcedPostCleanUp`, `getMasterLockWriteForcedRevokeFailures`, `getMasterLockWriteForcedStopFailures`, `getMasterLockWriteForcedPostCleanUpFailures`, `getMasterLockDirtyWindowCycles`, `getMasterLockDirty`, `getSweepRuns`, `getSweepOrphansEnqueued`, `getSweepGetBudgetUsed`, `getSafeOffsetBarrierWriters`, `getRecordsReceivedTotal`, `getRecordsWrittenTotal`, `getNullRecordsSkippedTotal`, `getLastPutEpochMillis`, `getPutTimerCount`, `getPutTimerSumMillis`, `getPutTimerMaxMillis`, `getFilesOpenedTotal`, `getFilesCommittedTotal`, `getFilesFailedTotal`, `getBytesWrittenTotal`, `getRecordsCommittedTotal`, `getCommitTimerCount`, and 31 more. 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. — kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/metrics/CloudSinkMetricsMBean.scala:35
`IndexManager` declares 16 abstract members: `indexingEnabled`, `open`, `update`, `getSeekedOffsetForTopicPartition`, `getSeekedOffsetForPartitionKey`, `updateForPartitionKey`, `batchDedupFloor`, `afterBatchCommit`, `updateMasterLock`, `cleanUpObsoleteLocks`, `ensureGranularLock`, `evictGranularLock`, `evictAllGranularLocks`, `clearTopicPartitionState`, `suspendBackgroundWork`, `close`. 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. — kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/seek/IndexManager.scala:27
`StorageInterface[SM]` declares 19 abstract members: `system`, `uploadFile`, `close`, `pathExists`, `list`, `listFileMetaRecursive`, `listKeysRecursive`, `seekToFile`, `getBlob`, `getBlobAsString`, `writeBlobToFile`, `getBlobAsStringAndEtag`, `getMetadata`, `writeStringToFile`, `deleteFiles`, `deleteFile`, `mvFile`, `createDirectoryIfNotExists`, `touchFile`. 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. — kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/storage/StorageInterface.scala:31
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Do you agree with this assessment?
DM12 · Ambient inputs in the domain10.0 / 10Exemplary○ Nothing flagged
Other · Domain Modelling — Whether domain types receive the time and randomness their rules depend on, rather than reading the process clock or a global random source directly — an ambient read makes the rule it feeds untestable at the instant that matters and lets two reads inside one operation disagree.
Method: Roslyn (DDD-gated, C#/VB only): domain-layer types scanned for ambient reads — DateTime/DateTimeOffset.Now/UtcNow/Today, Random.Shared, new Random(), Stopwatch.GetTimestamp — resolved against the semantic model, with a comment/string-stripped token fallback only where resolution fails. Body reads are scored; field/property initialisers are surfaced unscored. Apply/When folds excluded (ES1 owns them). Deterministic, symbol-resolved.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.
Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.
Other · Code Health — Unreviewed-generation residue in this repository's Scala: methods whose whole body is still `???` or a "not implemented" throw where nothing overrides them, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Scala: methods whose body is `???` or only throws a "not implemented" error, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
A bare `// scalastyle:off`, `// scalafix:off` or `@nowarn` (or Wartremover's `warts.All`) switches every rule or warning off — hidden debt. Suppress the specific rule on the specific line, with a justification, instead. (×6) — kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/sink/converter/SinkRecordToDocument.scala:36, REDACTED:186, kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/formats/reader/converters/SchemalessEnvelopeConverter.scala:137, …
What to do
Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
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.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 6 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:3
`REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, `maven`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — REDACTED:6
What to do
Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Dependabot is configured but does not watch `github-actions`, `maven` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
What to do
Add an approval/environment gate (required reviewers / protection rules) before production promotion.
Do you agree with this assessment?
P5 · DR & Backup4.0 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
No persistence guard on critical data stores — use Docker named volumes (or your orchestrator's persistent-volume equivalent) so the data store can't be wiped by a container recreate (or, in cloud, set purge-protection / soft-delete / prevent_destroy).
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document3.5 / 10Weak✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`JsonOptNullConverter.convert` is public and takes `value: JValue` from its caller, and it calls itself at line 80 with a piece of `value` (and at line 82), not as a tail call the compiler turns into a loop — and nowhere in `JsonOptNullConverter.convert` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a walk like this one throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25), while `ujson.read`, Jackson's `readTree` before 2.15 and circe before 0.14.16 accept any nesting (2,000,000 levels from 4 MB) and circe 0.14.16 accepts 4,096 — on a cold JVM even play-json's cap of 1,000 is past the point the walk fails. `StackOverflowError` is not `NonFatal`: `Try`, `case NonFatal(e)` and `recover` do not stop it, and in a `Future` on the global execution context it leaves the future forever incomplete. Thread a depth argument through `JsonOptNullConverter.convert` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonOptNullConverter.scala:80
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
`Files.find(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.toArray` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(Files.find(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`. — project/Settings.scala:258
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements (or a repository exception type deriving from it) controlled by an `if` — directly or through the `using`, `lock` or `try` that wraps the throw — whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`); in the `else` branch, for a conjunct of the admitting condition that is FALSE of a non-null `p`. Range guards are read for bounds that leave nothing and for a `p > C.Count` bound whose index then reaches `C[p]`, `C.RemoveAt(p)` or a method of the same type that indexes with it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for` comprehension or `foreach` leaves the mutable collection it is walking alone — an `ArrayBuffer` or `ListBuffer` counts its changes and its iterator checks the count, an `ArrayDeque` (and `mutable.Queue`/`mutable.Stack`) is walked by index up to its starting length, and a `java.util` collection walked through `asScala` is fail-fast, so a body that adds to or removes from the very collection the loop is walking makes a later step throw `ConcurrentModificationException` (`IndexOutOfBoundsException` for a deque) and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`warn` at line 104 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/GcpClientBuilder.java:104
`debug` at line 336 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/SchemaManager.java:336
`info` at line 87 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-connectors/kafka-connect-sink-reporting/src/main/java/io/lenses/streamreactor/connect/reporting/ReportSender.java:87
`info` at line 123 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-connectors/kafka-connect-sink-reporting/src/main/java/io/lenses/streamreactor/connect/reporting/ReportSender.java:123
`warn` at line 92 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — java-connectors/kafka-connect-sink-reporting/src/main/java/io/lenses/streamreactor/connect/reporting/model/RecordConverter.java:92
Other · Code Health — Whether Scala's null is held to the type system and not undermined by assertions — a file compiled with `-Yexplicit-nulls` is one where `String` excludes null and `String | Null` admits it, a file under WartRemover's `Null` wart or Scalafix's `DisableSyntax.noNulls` is one whose code cannot write `null` and must say `Option`, and each `.nn`, `import scala.language.unsafeNulls` or null-lint suppression is the author overruling that.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
No build over this repository's 639 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.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 1 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: this repository stores data through 'com.mongodb' (kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/sink/MongoWriter.scala:27) 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 'com.mongodb' (kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/sink/MongoWriter.scala:27) 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 'com.mongodb' (kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/sink/MongoWriter.scala:27) 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.
Not included — 65 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Scala imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. 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 1 — a container did not start, exited, or never became healthy) — Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error setting rlimits for ready process: error setting rlimit type 8: operation not permitted: unknown; 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 — ~107432 lines of test source are present (.scala, .java) 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 — Not scored — 13 Maven/Gradle manifest(s) were read, stating a version for 2 dependency(ies) and leaving 23 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
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.
D21 Naming Consistency — D21 withholds its sibling role token rows: 2 candidate(s) found and not reported.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — 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) — 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.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
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 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show 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 — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
S1 Web-Security Posture — No web surface: 768 Scala file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository builds on an HTTP-server library (REDACTED:253 — depends on `http4s-dsl`) but serves no HTTP of its own: its production source starts no server (no `newServerAt`/`bindAndHandle`, server builder, `Server.serve`, `Http.serve`, tapir server interpreter or Netty HTTP pipeline), declares no application one runs (no Play application, servlet, cask `MainRoutes`, `HttpApp` or twitter-server), so it is a library whose server controls belong to the application that serves it — HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library. If this codebase starts serving HTTP, the dimension reactivates automatically.
X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — no C# was loaded; this repository's Scala and Java were read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter; a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Orphaned knowledge java-connectors/kafka-connect-query-language/src/main/java/io/lenses/kcql/Kcql.java:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge kafka-connect-cassandra/src/main/scala/io/lenses/streamreactor/connect/cassandra/source/CassandraTableReader.scala:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Boundary-crossing change coupling: S3SinkConfig.scala ↔ WriterManager.scala kafka-connect-aws-s3/src/main/scala/io/lenses/streamreactor/connect/aws/s3/sink/config/S3SinkConfig.scala:1— `kafka-connect-aws-s3/src/main/scala/io/lenses/streamreactor/connect/aws/s3/sink/config/S3SinkConfig.scala` (context kafka-connect-aws-s3) and `kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/writer/WriterManager.scala` (context kafka-connect-cloud-common) sit in DIFFERENT parts of the tree yet change together 56% of the time (9 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `4db242c1` Enable skipping of null records - defaults to false (#211); `4d42d053` Optimised Schema Change for Cloud Datalake Sinks (#200); `21698d95` Rollover on schema change (#157) — run `git show` on any of them.
TodoComment kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/KeyExtractor.scala:28— //TODO would be nice to return an Either rather than throw exception — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/KeyExtractor.scala:111— //TODO would be nice to return an Either rather than throw exception — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/schemas/StructHelper.scala:131— //TODO: this should return an Either with the Schema as opposed to log the error — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/converters/sink/SinkRecordToJson.scala:82— // TODO: is this an error case? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment kafka-connect-mqtt/src/it/scala/io/lenses/streamreactor/connect/mqtt/sink/MqttWriterIT.scala:216— // TODO: this is not correct as the input to the writer is a Set, so the order is not — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment kafka-connect-mongodb/src/test/scala/io/lenses/streamreactor/connect/mongodb/SinkRecordToDocumentTest.scala:114— // TODO: This test is exactly the same as the above test "convert String Schema + Json payload to a Mongo Document". — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment kafka-connect-mongodb/src/test/scala/io/lenses/streamreactor/connect/mongodb/converters/SinkRecordConverterTest.scala:295— // Todo move the json tests under convertTimestamps() and — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment kafka-connect-jms/src/main/scala/io/lenses/streamreactor/connect/jms/sink/JMSSinkTask.scala:91— //TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment kafka-connect-http/src/main/scala/io/lenses/streamreactor/connect/http/sink/HttpWriter.scala:146— // TODO: feedback to kafka a warning if the queue gets too large — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment kafka-connect-http/src/it/scala/io/lenses/streamreactor/connect/http/sink/HttpSinkTaskIT.scala:124— // TODO: I don't think this is a valid use case unless you want to aggregate records. It doesn't really make sense, perhaps this should throw an error instead. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment kafka-connect-http/src/fun/scala/io/lenses/streamreactor/connect/http/sink/RecordsQueueBatcherTest.scala:64— // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment kafka-connect-http/src/fun/scala/io/lenses/streamreactor/connect/http/sink/RecordsQueueBatcherTest.scala:95— // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment kafka-connect-gcp-storage/src/it/scala/io/lenses/streamreactor/connect/cloud/common/utils/ITSampleSchemaAndData.scala:16— // TODO: Reuse these throughout all tests! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment kafka-connect-azure-datalake/src/it/scala/io/lenses/streamreactor/connect/cloud/common/utils/ITSampleSchemaAndData.scala:16— // TODO: Reuse these throughout all tests! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment kafka-connect-aws-s3/src/it/scala/io/lenses/streamreactor/connect/cloud/common/utils/ITSampleSchemaAndData.scala:18— // TODO: Reuse these throughout all tests! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment kafka-connect-gcp-storage/src/it/scala/io/lenses/streamreactor/connect/cloud/common/sink/CoreSinkTaskTestCases.scala:1969— // TODO check records — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment kafka-connect-azure-datalake/src/it/scala/io/lenses/streamreactor/connect/cloud/common/sink/CoreSinkTaskTestCases.scala:1915— // TODO check records — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment kafka-connect-aws-s3/src/it/scala/io/lenses/streamreactor/connect/cloud/common/sink/CoreSinkTaskTestCases.scala:1915— // TODO check records — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment kafka-connect-ftp/src/main/scala/io/lenses/streamreactor/connect/ftp/source/FtpMonitor.scala:44— // tells to monitor which directory and how files are dealt with, might be better a trait and is TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment kafka-connect-ftp/src/main/scala/io/lenses/streamreactor/connect/ftp/source/FtpMonitor.scala:335— // TODO: maybe we should keep the connection open. However, the underlying ftp client is a major PITA and this is way easier. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment kafka-connect-ftp/src/main/scala/io/lenses/streamreactor/connect/ftp/source/MaxLinesFileConverter.scala:48— // TODO : warn that no line seprator was found, suggest that the line sizes maybe exceeds the slice size — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment kafka-connect-ftp/src/it/scala/io/lenses/streamreactor/connect/ftp/source/EndToEnd.scala:41— // TODO: to be done for more advanced tests — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment kafka-connect-elastic7/src/it/scala/io/lenses/streamreactor/connect/elastic7/ElasticWriterTest.scala:56— // TODO: Ensure these Settings properties are used — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/writer/WriterManager.scala:404— //TODO: fix this; it cannot always be VALUE and it depends on writer requiring a roll over to new file — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment kafka-connect-cassandra/src/test/scala/io/lenses/streamreactor/connect/cassandra/utils/KeyUtilsTest.scala:71— // TODO can this be more specific? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Duplicated block (8 lines × 2) kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala:201— kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala:201-208 | kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/converters/SinkRecordConverter.scala:162-169 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala:201` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/transformers/AddConnectSchemaTransformer.scala:135— kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/transformers/AddConnectSchemaTransformer.scala:135-142 | kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/transformers/AddConnectSchemaTransformer.scala:159-166 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/transformers/AddConnectSchemaTransformer.scala:135` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/seek/IndexManagerV2.scala:1072— kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/seek/IndexManagerV2.scala:1072-1079 | kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/seek/IndexManagerV2.scala:1210-1217 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/seek/IndexManagerV2.scala:1072` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) REDACTED:79— REDACTED:79-86 | REDACTED:108-115 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) kafka-connect-cassandra/src/main/scala/io/lenses/streamreactor/connect/cassandra/sink/CassandraSinkTask.scala:72— kafka-connect-cassandra/src/main/scala/io/lenses/streamreactor/connect/cassandra/sink/CassandraSinkTask.scala:72-79 | kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/sink/MongoSinkTask.scala:72-80 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) java-connectors/kafka-connect-azure-servicebus/src/main/java/io/lenses/streamreactor/connect/azure/servicebus/sink/AzureServiceBusSinkConnector.java:67— java-connectors/kafka-connect-azure-servicebus/src/main/java/io/lenses/streamreactor/connect/azure/servicebus/sink/AzureServiceBusSinkConnector.java:67-74 | java-connectors/kafka-connect-azure-servicebus/src/main/java/io/lenses/streamreactor/connect/azure/servicebus/source/AzureServiceBusSourceConnector.java:70-77 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
ClassTooLong: BigQuerySinkConfig java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/config/BigQuerySinkConfig.java:71— ClassTooLong — 835 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 435 over it, 2.09× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Kcql java-connectors/kafka-connect-query-language/src/main/java/io/lenses/kcql/Kcql.java:50— ClassTooLong — 432 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 32 over it, 1.08× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SchemaManager java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/SchemaManager.java:74— ClassTooLong — 424 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 24 over it, 1.06× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: DatalakeStorageInterface kafka-connect-azure-datalake/src/main/scala/io/lenses/streamreactor/connect/datalake/storage/DatalakeStorageInterface.scala:52— ClassTooLong — 414 significant lines (blank, comment-only and punctuation-only lines excluded), 4 methods. The bar is 400 significant lines; this is 14 over it, 1.04× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: BigQuerySinkTask java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/BigQuerySinkTask.java:104— ClassTooLong — 410 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 10 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (7 lines × 2) kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:54— kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:54-60 | kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:106-112 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:54` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:65— kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:65-71 | kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:96-102 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:65` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:92— kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:92-98 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/converters/ToJsonWithProjections.scala:99-105 — before extracting anything, compare `kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala` and `kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/converters/ToJsonWithProjections.scala` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:92` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/converters/ToJsonWithProjections.scala:61— kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/converters/ToJsonWithProjections.scala:61-67 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/converters/ToJsonWithProjections.scala:113-119 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/converters/ToJsonWithProjections.scala:61` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/converters/ToJsonWithProjections.scala:72— kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/converters/ToJsonWithProjections.scala:72-78 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/converters/ToJsonWithProjections.scala:103-109 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/converters/ToJsonWithProjections.scala:72` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) kafka-connect-azure-datalake/src/main/scala/io/lenses/streamreactor/connect/datalake/storage/DatalakeStorageInterface.scala:242— kafka-connect-azure-datalake/src/main/scala/io/lenses/streamreactor/connect/datalake/storage/DatalakeStorageInterface.scala:242-246 | kafka-connect-azure-datalake/src/main/scala/io/lenses/streamreactor/connect/datalake/storage/DatalakeStorageInterface.scala:631-641 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-azure-datalake/src/main/scala/io/lenses/streamreactor/connect/datalake/storage/DatalakeStorageInterface.scala:242` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/config/FlushSettings.scala:69— kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/config/FlushSettings.scala:69-73 | kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/config/FlushSettings.scala:76-80 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note first that the copies are not typed on the same thing: `FlushCount` names `io.lenses.streamreactor.connect.azure.cosmosdb.config.kcqlprops.PropsKeyEnum.FlushCount` in one and `io.lenses.streamreactor.connect.cloud.common.config.kcqlprops.PropsKeyEnum.FlushCount` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 2) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/config/ConfigParse.scala:29— kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/config/ConfigParse.scala:29-33 | kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/config/PropertiesHelper.scala:38-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/KElasticBulkClient.scala:136— kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/KElasticBulkClient.scala:136-140 | kafka-connect-opensearch/src/main/scala/io/lenses/streamreactor/connect/opensearch/KOpenSearchClient.scala:185-189 — before extracting anything, compare `kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/KElasticBulkClient.scala` and `kafka-connect-opensearch/src/main/scala/io/lenses/streamreactor/connect/opensearch/KOpenSearchClient.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) java-connectors/kafka-connect-common/src/main/java/io/lenses/streamreactor/common/validation/validators/PatternMatchingSourceNameValidator.java:36— java-connectors/kafka-connect-common/src/main/java/io/lenses/streamreactor/common/validation/validators/PatternMatchingSourceNameValidator.java:36-40 | java-connectors/kafka-connect-common/src/main/java/io/lenses/streamreactor/common/validation/validators/PatternMatchingTargetNameValidator.java:36-40 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×4
Edited copy of a member (14 corresponding lines) java-connectors/kafka-connect-query-language/src/main/java/io/lenses/kcql/Kcql.java:560— java-connectors/kafka-connect-query-language/src/main/java/io/lenses/kcql/Kcql.java:560-574 | java-connectors/kafka-connect-query-language/src/main/java/io/lenses/kcql/Kcql.java:577-590 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) java-connectors/kafka-connect-query-language/src/main/java/io/lenses/kcql/Field.java:82— java-connectors/kafka-connect-query-language/src/main/java/io/lenses/kcql/Field.java:82-97 | java-connectors/kafka-connect-query-language/src/main/java/io/lenses/kcql/Tag.java:57-70 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) java-connectors/kafka-connect-gcp-common/src/main/java/io/lenses/streamreactor/connect/gcp/common/config/AuthModeSettings.java:152— java-connectors/kafka-connect-gcp-common/src/main/java/io/lenses/streamreactor/connect/gcp/common/config/AuthModeSettings.java:152-165 | java-connectors/kafka-connect-gcp-common/src/main/java/io/lenses/streamreactor/connect/gcp/common/config/AuthModeSettings.java:167-183 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/GcpClientBuilder.java:161— java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/GcpClientBuilder.java:161-174 | java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/GcpClientBuilder.java:180-193 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×4
Edited copy of a member (12 corresponding lines) kafka-connect-azure-datalake/src/main/scala/io/lenses/streamreactor/connect/datalake/storage/DatalakeStorageInterface.scala:196— kafka-connect-azure-datalake/src/main/scala/io/lenses/streamreactor/connect/datalake/storage/DatalakeStorageInterface.scala:196-207 | kafka-connect-azure-datalake/src/main/scala/io/lenses/streamreactor/connect/datalake/storage/DatalakeStorageInterface.scala:425-444 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) java-connectors/kafka-connect-common/src/main/java/io/lenses/streamreactor/common/security/StoresInfo.java:135— java-connectors/kafka-connect-common/src/main/java/io/lenses/streamreactor/common/security/StoresInfo.java:135-147 | java-connectors/kafka-connect-common/src/main/java/io/lenses/streamreactor/common/security/StoresInfo.java:150-161 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) kafka-connect-http/src/main/scala/io/lenses/streamreactor/connect/http/sink/metrics/MetricsResetter.scala:60— kafka-connect-http/src/main/scala/io/lenses/streamreactor/connect/http/sink/metrics/MetricsResetter.scala:60-72 | kafka-connect-http/src/main/scala/io/lenses/streamreactor/connect/http/sink/metrics/MetricsResetter.scala:75-86 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) java-connectors/kafka-connect-query-language/src/main/java/io/lenses/kcql/Kcql.java:527— java-connectors/kafka-connect-query-language/src/main/java/io/lenses/kcql/Kcql.java:527-538 | java-connectors/kafka-connect-query-language/src/main/java/io/lenses/kcql/Kcql.java:541-552 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×4
Edited copy of a member (8 corresponding lines) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/transformers/EnvelopeWithSchemaTransformer.scala:123— kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/transformers/EnvelopeWithSchemaTransformer.scala:123-130 | kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/transformers/SchemalessEnvelopeTransformer.scala:100-107 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/sink/writer/CosmosDbQueueProcessor.scala:116— kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/sink/writer/CosmosDbQueueProcessor.scala:116-123 | kafka-connect-http/src/main/scala/io/lenses/streamreactor/connect/http/sink/HttpWriter.scala:457-467 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/write/row/AdaptiveBigQueryWriter.java:170— java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/write/row/AdaptiveBigQueryWriter.java:170-177 | java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/write/row/UpsertDeleteBigQueryWriter.java:85-95 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/write/row/AdaptiveBigQueryWriter.java:179— java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/write/row/AdaptiveBigQueryWriter.java:179-186 | java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/write/row/GCSToBQWriter.java:223-231 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×4
Edited copy of a member (11 corresponding lines) kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/StructSql.scala:65— kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/StructSql.scala:65-77 | kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/StructSql.scala:80-90 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/transformers/EnvelopeWithSchemaTransformer.scala:35— kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/transformers/EnvelopeWithSchemaTransformer.scala:35-45 | kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/transformers/SchemalessEnvelopeTransformer.scala:35-45 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/write/batch/GCSBatchTableWriter.java:128— java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/write/batch/GCSBatchTableWriter.java:128-139 | java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/write/batch/TableWriter.java:198-208 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) test-common/src/main/scala/io/lenses/streamreactor/connect/testcontainers/connect/KafkaConnectClient.scala:36— test-common/src/main/scala/io/lenses/streamreactor/connect/testcontainers/connect/KafkaConnectClient.scala:36-46 | test-common/src/main/scala/io/lenses/streamreactor/connect/testcontainers/connect/KafkaConnectClient.scala:51-63 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
TooManyMethods: CloudSinkMetrics kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/metrics/CloudSinkMetricsMBean.scala:413— TooManyMethods — 57 methods. The bar is 30 methods; this is 27 over it, 1.90× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: 2 java-connectors/kafka-connect-query-language/src/main/java/io/lenses/kcql/Kcql.java:288— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: IndexManagerV2 kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/seek/IndexManagerV2.scala:70— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×3
Edited copy of a member (21 corresponding lines) kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/ElasticWriter.scala:31— kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/ElasticWriter.scala:31-51 | kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/ElasticWriter.scala:31-51 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) kafka-connect-aws-s3/src/main/scala/io/lenses/streamreactor/connect/aws/s3/storage/AwsS3StorageInterface.scala:157— kafka-connect-aws-s3/src/main/scala/io/lenses/streamreactor/connect/aws/s3/storage/AwsS3StorageInterface.scala:157-177 | kafka-connect-gcp-storage/src/main/scala/io/lenses/streamreactor/connect/gcp/storage/storage/GCPStorageStorageInterface.scala:72-99 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) kafka-connect-cassandra/src/main/scala/io/lenses/streamreactor/connect/cassandra/source/CqlGenerator.scala:42— kafka-connect-cassandra/src/main/scala/io/lenses/streamreactor/connect/cassandra/source/CqlGenerator.scala:42-62 | kafka-connect-cassandra/src/main/scala/io/lenses/streamreactor/connect/cassandra/source/CqlGenerator.scala:69-89 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×3
Edited copy of a member (10 corresponding lines) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/SchemaManager.java:562— java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/SchemaManager.java:562-574 | java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/SchemaManager.java:583-592 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/BigQuerySinkTask.java:696— java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/BigQuerySinkTask.java:696-705 | java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/BigQuerySinkTask.java:707-716 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) kafka-connect-cassandra-sink/src/main/scala/io/lenses/streamreactor/connect/cassandra/CassandraSinkConnector.scala:62— kafka-connect-cassandra-sink/src/main/scala/io/lenses/streamreactor/connect/cassandra/CassandraSinkConnector.scala:62-71 | kafka-connect-cassandra/src/main/scala/io/lenses/streamreactor/connect/cassandra/sink/CassandraSinkConnector.scala:65-74 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (14 lines × 2) kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala:243— kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala:243-256 | kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/converters/SinkRecordConverter.scala:247-260 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala:243` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `Document` names `com.azure.cosmos.implementation.Document` in one and `org.bson.Document` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (14 lines × 2) kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/StructSchemaSql.scala:117— kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/StructSchemaSql.scala:117-130 | kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/StructSql.scala:103-116 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/StructSchemaSql.scala:117` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 2) kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/config/base/settings/Projections.scala:136— kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/config/base/settings/Projections.scala:136-149 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/config/base/settings/Projections.scala:152-165 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/seek/PendingOperationsProcessors.scala:222— kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/seek/PendingOperationsProcessors.scala:222-232 | kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/seek/PendingOperationsProcessors.scala:289-299 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/seek/PendingOperationsProcessors.scala:222` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/converters/SinkRecordConverter.scala:94— kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/converters/SinkRecordConverter.scala:94-104 | kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/converters/SinkRecordConverter.scala:205-215 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/converters/SinkRecordConverter.scala:94` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) java-connectors/kafka-connect-query-language/src/main/java/io/lenses/kcql/Kcql.java:566— java-connectors/kafka-connect-query-language/src/main/java/io/lenses/kcql/Kcql.java:566-576 | java-connectors/kafka-connect-query-language/src/main/java/io/lenses/kcql/Kcql.java:582-592 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `java-connectors/kafka-connect-query-language/src/main/java/io/lenses/kcql/Kcql.java:566` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (6 lines × 2) kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala:222— kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala:222-227 | kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/converters/SinkRecordConverter.scala:184-189 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala:222` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `Document` names `com.azure.cosmos.implementation.Document` in one and `org.bson.Document` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 2) kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:62— kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:62-67 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/converters/ToJsonWithProjections.scala:69-74 — before extracting anything, compare `kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala` and `kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/converters/ToJsonWithProjections.scala` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:62` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) REDACTED:97— REDACTED:97-102 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/converters/ToJsonWithProjections.scala:91-96 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:97` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Low cohesion: GCPStorageStorageInterface (LCOM4 9) kafka-connect-gcp-storage/src/main/scala/io/lenses/streamreactor/connect/gcp/storage/storage/GCPStorageStorageInterface.scala:66— GCPStorageStorageInterface's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: DatalakeStorageInterface (LCOM4 7) kafka-connect-azure-datalake/src/main/scala/io/lenses/streamreactor/connect/datalake/storage/DatalakeStorageInterface.scala:52— DatalakeStorageInterface's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: KOpenSearchClient (LCOM4 5) kafka-connect-opensearch/src/main/scala/io/lenses/streamreactor/connect/opensearch/KOpenSearchClient.scala:56— KOpenSearchClient's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Hotspot: REDACTED REDACTED:62— REDACTED changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in OpenSearchSettings.apply at line 62. 2 of those changes were fix/bug commits, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:56:26 +00:00' --until='2026-11-02 18:56:26 +00:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/WriterManagerCreator.scala kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/WriterManagerCreator.scala:49— kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/WriterManagerCreator.scala changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in WriterManagerCreator.from at line 49. 1 of those changes was a fix/bug commit, and the other 1 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-04..2026-11-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-04 18:56:26 +00:00' --until='2026-11-02 18:56:26 +00:00' --full-history --no-merges -- kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/WriterManagerCreator.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
FixmeComment kafka-connect-mongodb/src/it/scala/io/lenses/streamreactor/connect/mongodb/sink/MongoWriterTest.scala:471— // FIXME: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/source/reader/PartitionDiscovery.scala:45— // FIXME: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
MethodTooLong: BigQuerySinkConfig.getConfig java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/config/BigQuerySinkConfig.java:580— MethodTooLong — getConfig runs 297 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 197 over it, 2.97× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Kcql.parse java-connectors/kafka-connect-query-language/src/main/java/io/lenses/kcql/Kcql.java:260— MethodTooLong — parse runs 281 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 181 over it, 2.81× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FileTooLong: seek/IndexManagerV2.scala kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/seek/IndexManagerV2.scala— FileTooLong — 1066 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: IndexManagerV2 (70-1892). The bar is 500 significant lines; this is 566 over it, 2.13× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: config/BigQuerySinkConfig.java java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/config/BigQuerySinkConfig.java— FileTooLong — 864 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: BigQuerySinkConfig (71-1152). The bar is 500 significant lines; this is 364 over it, 1.73× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×2
Edited copy of a member (24 corresponding lines) kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/config/ElasticSettings.scala:27— kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/config/ElasticSettings.scala:27-50 | kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/config/ElasticSettings.scala:29-58 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/config/FormatSelection.scala:160— kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/config/FormatSelection.scala:160-183 | kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/config/FormatSelection.scala:203-226 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×2
Edited copy of a member (17 corresponding lines) kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/converters/sink/AvroConverter.scala:90— kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/converters/sink/AvroConverter.scala:90-106 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/AvroConverter.scala:105-128 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) kafka-connect-jms/src/main/scala/io/lenses/streamreactor/connect/jms/sink/JMSSinkTask.scala:50— kafka-connect-jms/src/main/scala/io/lenses/streamreactor/connect/jms/sink/JMSSinkTask.scala:50-66 | kafka-connect-mqtt/src/main/scala/io/lenses/streamreactor/connect/mqtt/sink/MqttSinkTask.scala:44-61 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×2
Edited copy of a member (18 corresponding lines) kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/KElasticBulkClient.scala:142— kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/KElasticBulkClient.scala:142-159 | kafka-connect-opensearch/src/main/scala/io/lenses/streamreactor/connect/opensearch/KOpenSearchClient.scala:191-208 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) kafka-connect-aws-s3/src/main/scala/io/lenses/streamreactor/connect/aws/s3/storage/AwsS3StorageInterface.scala:331— kafka-connect-aws-s3/src/main/scala/io/lenses/streamreactor/connect/aws/s3/storage/AwsS3StorageInterface.scala:331-366 | kafka-connect-aws-s3/src/main/scala/io/lenses/streamreactor/connect/aws/s3/storage/AwsS3Uploader.scala:34-51 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×2
Edited copy of a member (9 corresponding lines) kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/config/FlushSettings.scala:52— kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/config/FlushSettings.scala:52-60 | kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/config/FlushSettings.scala:59-67 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) kafka-connect-common/src/main/scala/io/lenses/streamreactor/connect/config/kcqlprops/KcqlProperties.scala:54— kafka-connect-common/src/main/scala/io/lenses/streamreactor/connect/config/kcqlprops/KcqlProperties.scala:54-62 | kafka-connect-common/src/main/scala/io/lenses/streamreactor/connect/config/kcqlprops/KcqlProperties.scala:65-73 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×2
Edited copy of a member (6 corresponding lines) java-connectors/kafka-connect-common/src/main/java/io/lenses/streamreactor/common/collections/TopicPartitionOffsetAndMetadataStorage.java:68— java-connectors/kafka-connect-common/src/main/java/io/lenses/streamreactor/common/collections/TopicPartitionOffsetAndMetadataStorage.java:68-73 | java-connectors/kafka-connect-common/src/main/java/io/lenses/streamreactor/common/collections/TopicPartitionOffsetAndMetadataStorage.java:99-104 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) java-connectors/kafka-connect-common/src/main/java/io/lenses/streamreactor/common/validation/validators/DistinctSourceNamesValidator.java:30— java-connectors/kafka-connect-common/src/main/java/io/lenses/streamreactor/common/validation/validators/DistinctSourceNamesValidator.java:30-35 | java-connectors/kafka-connect-common/src/main/java/io/lenses/streamreactor/common/validation/validators/DistinctTargetNamesValidator.java:30-35 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×2
Edited copy of a member (7 corresponding lines) kafka-connect-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/extractors/ArrayExtractor.scala:42— kafka-connect-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/extractors/ArrayExtractor.scala:42-48 | kafka-connect-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/extractors/WrappedArrayExtractor.scala:28-35 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) kafka-connect-common/src/main/scala/io/lenses/streamreactor/connect/io/text/LineStartLineEndReader.scala:54— kafka-connect-common/src/main/scala/io/lenses/streamreactor/connect/io/text/LineStartLineEndReader.scala:54-60 | kafka-connect-common/src/main/scala/io/lenses/streamreactor/connect/io/text/SequenceBasedLineReader.scala:81-87 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×2
Edited copy of a member (3 corresponding lines) kafka-connect-cassandra/src/main/scala/io/lenses/streamreactor/connect/cassandra/config/CassandraConfig.scala:534— kafka-connect-cassandra/src/main/scala/io/lenses/streamreactor/connect/cassandra/config/CassandraConfig.scala:534-536 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/config/base/settings/Projections.scala:100-102 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) kafka-connect-aws-s3/src/main/scala/io/lenses/streamreactor/connect/aws/s3/storage/AwsS3StorageInterface.scala:432— kafka-connect-aws-s3/src/main/scala/io/lenses/streamreactor/connect/aws/s3/storage/AwsS3StorageInterface.scala:432-434 | kafka-connect-gcp-storage/src/main/scala/io/lenses/streamreactor/connect/gcp/storage/storage/GCPStorageStorageInterface.scala:408-410 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (29 lines × 2) kafka-connect-aws-s3/src/main/scala/io/lenses/streamreactor/connect/aws/s3/config/S3CommonConfigDef.scala:112— kafka-connect-aws-s3/src/main/scala/io/lenses/streamreactor/connect/aws/s3/config/S3CommonConfigDef.scala:112-140 | kafka-connect-azure-datalake/src/main/scala/io/lenses/streamreactor/connect/datalake/config/CommonConfigDef.scala:79-107 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-aws-s3/src/main/scala/io/lenses/streamreactor/connect/aws/s3/config/S3CommonConfigDef.scala:112` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (29 lines × 2) kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/KElasticBulkClient.scala:73— kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/KElasticBulkClient.scala:73-101 | kafka-connect-opensearch/src/main/scala/io/lenses/streamreactor/connect/opensearch/KOpenSearchClient.scala:114-142 — before extracting anything, compare `kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/KElasticBulkClient.scala` and `kafka-connect-opensearch/src/main/scala/io/lenses/streamreactor/connect/opensearch/KOpenSearchClient.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (18 lines × 2) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/config/FormatSelection.scala:163— kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/config/FormatSelection.scala:163-180 | kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/config/FormatSelection.scala:205-222 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2) kafka-connect-mqtt/src/main/scala/io/lenses/streamreactor/connect/mqtt/config/MqttSinkSettings.scala:58— kafka-connect-mqtt/src/main/scala/io/lenses/streamreactor/connect/mqtt/config/MqttSinkSettings.scala:58-75 | kafka-connect-mqtt/src/main/scala/io/lenses/streamreactor/connect/mqtt/config/MqttSourceSettings.scala:77-94 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (16 lines × 2) kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/KElasticBulkClient.scala:144— kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/KElasticBulkClient.scala:144-159 | kafka-connect-opensearch/src/main/scala/io/lenses/streamreactor/connect/opensearch/KOpenSearchClient.scala:193-208 — before extracting anything, compare `kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/KElasticBulkClient.scala` and `kafka-connect-opensearch/src/main/scala/io/lenses/streamreactor/connect/opensearch/KOpenSearchClient.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:42— kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:42-57 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/converters/ToJsonWithProjections.scala:49-64 — before extracting anything, compare `kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala` and `kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/converters/ToJsonWithProjections.scala` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:42` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/PrimaryKeyExtractor.scala:232— kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/PrimaryKeyExtractor.scala:232-246 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/KeyExtractor.scala:233-247 — before extracting anything, compare `kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/PrimaryKeyExtractor.scala` and `kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/KeyExtractor.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 145 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/PrimaryKeyExtractor.scala:232` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala:259— kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala:259-273 | kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/converters/SinkRecordConverter.scala:265-279 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala:259` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `Document` names `com.azure.cosmos.implementation.Document` in one and `org.bson.Document` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (12 lines × 2) kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/KElasticClient.scala:43— kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/KElasticClient.scala:43-54 | kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/KElasticClient.scala:47-58 — before extracting anything, compare `kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/KElasticClient.scala` and `kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/KElasticClient.scala` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/KElasticClient.scala:43` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/KElasticClient.scala:59` calls `JavaClient` and `kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/KElasticClient.scala:55` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/ElasticWriter.scala:32— kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/ElasticWriter.scala:32-43 | kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/ElasticWriter.scala:32-43 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/ElasticWriter.scala:32` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `ElasticConfigConstants` names `io.lenses.streamreactor.connect.elastic6.config.ElasticConfigConstants` in one and `io.lenses.streamreactor.connect.elastic7.config.ElasticConfigConstants` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (13 lines × 2) kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonConverterWithSchemaEvolution.scala:104— kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonConverterWithSchemaEvolution.scala:104-116 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonSimpleConverter.scala:104-116 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonConverterWithSchemaEvolution.scala:104` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 2) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/convert/logicaltype/DebeziumLogicalConverters.java:111— java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/convert/logicaltype/DebeziumLogicalConverters.java:111-123 | java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/convert/logicaltype/DebeziumLogicalConverters.java:143-155 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/config/ElasticSettings.scala:28— kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/config/ElasticSettings.scala:28-36 | kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/config/ElasticSettings.scala:30-38 — before extracting anything, compare `kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/config/ElasticSettings.scala` and `kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/config/ElasticSettings.scala` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/KElasticBulkClient.scala:240— kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/KElasticBulkClient.scala:240-248 | kafka-connect-opensearch/src/main/scala/io/lenses/streamreactor/connect/opensearch/KOpenSearchClient.scala:286-294 — before extracting anything, compare `kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/KElasticBulkClient.scala` and `kafka-connect-opensearch/src/main/scala/io/lenses/streamreactor/connect/opensearch/KOpenSearchClient.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/KElasticBulkClient.scala:240` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6–7 lines × 2) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/writer/WriterManager.scala:270— kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/writer/WriterManager.scala:270-275 | kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/writer/WriterManager.scala:675-681 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/writer/WriterManager.scala:270` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6–7 lines × 2) REDACTED:69— REDACTED:69-75 | REDACTED:120-125 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:69` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
SinkRecordConverter.fromStruct (cyclomatic 45) kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/converters/SinkRecordConverter.scala:64— SinkRecordConverter.fromStruct has cyclomatic complexity 45 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
OpenSearchSettings.apply (cyclomatic 43) REDACTED:62— OpenSearchSettings.apply has cyclomatic complexity 43 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Transform.apply (cyclomatic 35) REDACTED:33— Transform.apply has cyclomatic complexity 35 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
ToJsonWithProjections.apply (cyclomatic 33) kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/converters/ToJsonWithProjections.scala:37— ToJsonWithProjections.apply has cyclomatic complexity 33 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
SimpleJsonConverter.convertToJsonInner (cyclomatic 32) kafka-connect-common/src/main/scala/io/lenses/streamreactor/connect/json/SimpleJsonConverter.scala:56— SimpleJsonConverter.convertToJsonInner has cyclomatic complexity 32 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
Transform.apply (cyclomatic 31) kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:37— Transform.apply has cyclomatic complexity 31 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
PrimaryKeyExtractor.extract (cyclomatic 28) kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/PrimaryKeyExtractor.scala:120— PrimaryKeyExtractor.extract has cyclomatic complexity 28 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
KeyExtractor.extract (cyclomatic 28) kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/KeyExtractor.scala:112— KeyExtractor.extract has cyclomatic complexity 28 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
SinkRecordConverter.fromJson (cyclomatic 25) kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/converters/SinkRecordConverter.scala:246— SinkRecordConverter.fromJson has cyclomatic complexity 25 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
JsonSqlExtensions.kcqlFlatten (cyclomatic 23) REDACTED:78— JsonSqlExtensions.kcqlFlatten has cyclomatic complexity 23 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
SinkRecordConverter.fromJson (cyclomatic 22) kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala:242— SinkRecordConverter.fromJson has cyclomatic complexity 22 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
DatalakeStorageInterface.writeBlobToFile (cyclomatic 20) kafka-connect-azure-datalake/src/main/scala/io/lenses/streamreactor/connect/datalake/storage/DatalakeStorageInterface.scala:475— DatalakeStorageInterface.writeBlobToFile has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Writer.commit (cyclomatic 20) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/writer/Writer.scala:267— Writer.commit has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Field.from (cyclomatic 20) java-connectors/kafka-connect-query-language/src/main/java/io/lenses/kcql/Field.java:112— Field.from has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SinkRecordConverter.convertToDocument (cyclomatic 19) kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala:79— SinkRecordConverter.convertToDocument has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WriterManagerCreator.from (cyclomatic 19) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/WriterManagerCreator.scala:49— WriterManagerCreator.from has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
EnvelopeWithSchemaTransformer.toOptional (cyclomatic 18) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/transformers/EnvelopeWithSchemaTransformer.scala:179— EnvelopeWithSchemaTransformer.toOptional has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ToAvroDataConverter.convertBySchemaType (cyclomatic 17) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/conversion/ToAvroDataConverter.scala:177— ToAvroDataConverter.convertBySchemaType has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
ConverterUtil.convertFromStringAsJson (cyclomatic 17) kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/schemas/ConverterUtil.scala:139— ConverterUtil.convertFromStringAsJson has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
AdaptiveBigQueryWriter.performWriteRequest (cyclomatic 17) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/write/row/AdaptiveBigQueryWriter.java:105— AdaptiveBigQueryWriter.performWriteRequest has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BigQueryWriter.writeRows (cyclomatic 17) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/write/row/BigQueryWriter.java:119— BigQueryWriter.writeRows has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DatalakeStorageInterface.mvFile (cyclomatic 16) kafka-connect-azure-datalake/src/main/scala/io/lenses/streamreactor/connect/datalake/storage/DatalakeStorageInterface.scala:311— DatalakeStorageInterface.mvFile has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
IndexManagerV2.sweepPartition (cyclomatic 16) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/seek/IndexManagerV2.scala:1696— IndexManagerV2.sweepPartition has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This is NOT this file's highest cyclomatic complexity: IndexManagerV2.decideOpen (cyclomatic 17) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
ReaderManager.poll (cyclomatic 16) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/source/reader/ReaderManager.scala:51— ReaderManager.poll has cyclomatic complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
KeysExtractor.fromStruct (cyclomatic 16) kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/sink/KeysExtractor.scala:35— KeysExtractor.fromStruct has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SinkRecordConverter.fromStruct (cognitive 109) kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/converters/SinkRecordConverter.scala:64— SinkRecordConverter.fromStruct has cognitive complexity 109 (threshold 15). Drivers by points: match/switch 14 (53 pts), if/else 32 (50 pts), loops 1 (3 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 60). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
CloudSinkBucketOptions.apply (cognitive 91) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/config/CloudSinkBucketOptions.scala:64— CloudSinkBucketOptions.apply has cognitive complexity 91 (threshold 15). Drivers by points: loops 13 (91 pts) (nesting depth added 78). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Transform.apply (cognitive 67) REDACTED:33— Transform.apply has cognitive complexity 67 (threshold 15). Drivers by points: match/switch 14 (55 pts), if/else 9 (11 pts), boolean chains 1 (nesting depth added 43). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
HttpRequestSender.sendHttpRequest (cognitive 66) kafka-connect-http/src/main/scala/io/lenses/streamreactor/connect/http/sink/client/HttpRequestSender.scala:147— HttpRequestSender.sendHttpRequest has cognitive complexity 66 (threshold 15). Drivers by points: loops 11 (66 pts) (nesting depth added 55). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
ToJsonWithProjections.apply (cognitive 66) kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/converters/ToJsonWithProjections.scala:37— ToJsonWithProjections.apply has cognitive complexity 66 (threshold 15). Drivers by points: match/switch 13 (54 pts), if/else 9 (11 pts), boolean chains 1 (nesting depth added 43). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Transform.apply (cognitive 62) kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:37— Transform.apply has cognitive complexity 62 (threshold 15). Drivers by points: match/switch 13 (54 pts), if/else 7 (8 pts) (nesting depth added 42). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ResultReader.create (cognitive 59) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/source/reader/ResultReader.scala:73— ResultReader.create has cognitive complexity 59 (threshold 15). Drivers by points: loops 9 (45 pts), match/switch 1 (9 pts), if/else 3 (5 pts) (nesting depth added 46). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
OpenSearchSettings.apply (cognitive 57) REDACTED:62— OpenSearchSettings.apply has cognitive complexity 57 (threshold 15). Drivers by points: if/else 26 (39 pts), boolean chains 18 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CloudSourceTask.make (cognitive 56) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/source/CloudSourceTask.scala:133— CloudSourceTask.make has cognitive complexity 56 (threshold 15). Drivers by points: loops 9 (45 pts), if/else 2 (11 pts) (nesting depth added 45). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Field.from (cognitive 52) java-connectors/kafka-connect-query-language/src/main/java/io/lenses/kcql/Field.java:112— Field.from has cognitive complexity 52 (threshold 15). Drivers by points: if/else 13 (44 pts), loops 1 (4 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 36). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
CosmosDbSinkSettings.apply (cognitive 51) kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/config/CosmosDbSinkSettings.scala:54— CosmosDbSinkSettings.apply has cognitive complexity 51 (threshold 15). Drivers by points: loops 8 (36 pts), if/else 6 (15 pts) (nesting depth added 37). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
ReaderManager.poll (cognitive 46) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/source/reader/ReaderManager.scala:51— ReaderManager.poll has cognitive complexity 46 (threshold 15). Drivers by points: loops 10 (37 pts), match/switch 2 (7 pts), if/else 2 (nesting depth added 32). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
SimpleJsonConverter.convertToJsonInner (cognitive 45) kafka-connect-common/src/main/scala/io/lenses/streamreactor/connect/json/SimpleJsonConverter.scala:56— SimpleJsonConverter.convertToJsonInner has cognitive complexity 45 (threshold 15). Drivers by points: if/else 12 (25 pts), match/switch 5 (12 pts), loops 2 (6 pts), error handling 1 (2 pts) (nesting depth added 25). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ConnectorTaskIdCreator.fromProps (cognitive 43) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/config/ConnectorTaskId.scala:49— ConnectorTaskIdCreator.fromProps has cognitive complexity 43 (threshold 15). Drivers by points: loops 7 (28 pts), if/else 6 (15 pts) (nesting depth added 30). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
AttachLatestSchemaOptimizer.adaptValue (cognitive 40) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/optimization/AttachLatestSchemaOptimizer.scala:175— AttachLatestSchemaOptimizer.adaptValue has cognitive complexity 40 (threshold 15). Drivers by points: match/switch 6 (20 pts), if/else 12 (19 pts), boolean chains 1 (nesting depth added 21). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
WriterManager.getOffsetAndMeta (cognitive 39) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/writer/WriterManager.scala:515— WriterManager.getOffsetAndMeta has cognitive complexity 39 (threshold 15). Drivers by points: if/else 17 (34 pts), match/switch 1 (4 pts), boolean chains 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConsumerGroupsWriter.extractOffsets (cognitive 38) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/consumers/ConsumerGroupsWriter.scala:81— ConsumerGroupsWriter.extractOffsets has cognitive complexity 38 (threshold 15). Drivers by points: loops 6 (27 pts), match/switch 2 (6 pts), if/else 2 (4 pts), boolean chains 1 (nesting depth added 27). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
DataStorageSettings.from (cognitive 36) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/config/DataStorageSettings.scala:86— DataStorageSettings.from has cognitive complexity 36 (threshold 15). Drivers by points: loops 7 (28 pts), if/else 2 (8 pts) (nesting depth added 27). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
HttpSinkConfig.from (cognitive 36) kafka-connect-http/src/main/scala/io/lenses/streamreactor/connect/http/sink/config/HttpSinkConfig.scala:179— HttpSinkConfig.from has cognitive complexity 36 (threshold 15). Drivers by points: loops 8 (36 pts) (nesting depth added 28). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
ConverterUtil.convertFromStringAsJson (cognitive 34) kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/schemas/ConverterUtil.scala:139— ConverterUtil.convertFromStringAsJson has cognitive complexity 34 (threshold 15). Drivers by points: match/switch 5 (18 pts), if/else 11 (15 pts), boolean chains 1 (nesting depth added 17). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
IndexManagerV2.sweepPartition (cognitive 32) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/seek/IndexManagerV2.scala:1696— IndexManagerV2.sweepPartition has cognitive complexity 32 (threshold 15). Drivers by points: match/switch 6 (17 pts), if/else 5 (11 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 18). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Writer.commit (cognitive 32) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/writer/Writer.scala:267— Writer.commit has cognitive complexity 32 (threshold 15). Drivers by points: match/switch 7 (16 pts), loops 3 (9 pts), if/else 4 (7 pts) (nesting depth added 18). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
BigQuerySinkTask.writeSinkRecords (cognitive 32) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/BigQuerySinkTask.java:278— BigQuerySinkTask.writeSinkRecords has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (25 pts), error handling 1 (3 pts), boolean chains 2, loops 2 (nesting depth added 19). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
IndexManagerV2.startExecutors (cognitive 31) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/seek/IndexManagerV2.scala:197— IndexManagerV2.startExecutors has cognitive complexity 31 (threshold 15). Drivers by points: if/else 6 (18 pts), error handling 3 (11 pts), match/switch 1 (2 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AddConnectSchemaTransformer.transform (cognitive 31) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/transformers/AddConnectSchemaTransformer.scala:43— AddConnectSchemaTransformer.transform has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (20 pts), loops 2 (7 pts), boolean chains 4 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ToAvroDataConverter.convertFieldValue (cognitive 29) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/conversion/ToAvroDataConverter.scala:131— ToAvroDataConverter.convertFieldValue has cognitive complexity 29 (threshold 15). Drivers by points: match/switch 7 (20 pts), if/else 9 (nesting depth added 13). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
HttpSinkTask.start (cognitive 29) kafka-connect-http/src/main/scala/io/lenses/streamreactor/connect/http/sink/HttpSinkTask.scala:61— HttpSinkTask.start has cognitive complexity 29 (threshold 15). Drivers by points: loops 7 (28 pts), match/switch 1 (nesting depth added 21). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
BigQueryWriter.writeRows (cognitive 29) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/write/row/BigQueryWriter.java:119— BigQueryWriter.writeRows has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (24 pts), error handling 1 (2 pts), boolean chains 1, loops 1, ternaries 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IndexManagerV2.snapshotLegacyLocks (cognitive 28) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/seek/IndexManagerV2.scala:809— IndexManagerV2.snapshotLegacyLocks has cognitive complexity 28 (threshold 15). Drivers by points: match/switch 5 (15 pts), if/else 5 (10 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 16). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
CloudSourceBucketOptions.apply (cognitive 28) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/source/config/CloudSourceBucketOptions.scala:34— CloudSourceBucketOptions.apply has cognitive complexity 28 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 4 (10 pts), match/switch 1 (5 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AdaptiveBigQueryWriter.performWriteRequest (cognitive 28) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/write/row/AdaptiveBigQueryWriter.java:105— AdaptiveBigQueryWriter.performWriteRequest has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 6, error handling 3 (6 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ReadTextMode.apply (cognitive 26) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/source/config/ReadTextMode.scala:39— ReadTextMode.apply has cognitive complexity 26 (threshold 15). Drivers by points: loops 8 (25 pts), match/switch 1 (nesting depth added 17). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
SinkRecordConverter.convertToDocument (cognitive 25) kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala:79— SinkRecordConverter.convertToDocument has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (18 pts), match/switch 2 (3 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ToAvroDataConverter.convertBySchemaType (cognitive 23) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/conversion/ToAvroDataConverter.scala:177— ToAvroDataConverter.convertBySchemaType has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 8 (15 pts), if/else 8 (nesting depth added 7). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
WriterManager.createWriter (cognitive 23) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/writer/WriterManager.scala:446— WriterManager.createWriter has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 2 (9 pts), if/else 5 (8 pts), loops 3 (6 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PartitionDiscovery.run (cognitive 23) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/source/reader/PartitionDiscovery.scala:33— PartitionDiscovery.run has cognitive complexity 23 (threshold 15). Drivers by points: loops 6 (21 pts), if/else 2 (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
JsonSqlExtensions.kcqlFlatten (cognitive 23) REDACTED:78— JsonSqlExtensions.kcqlFlatten has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (16 pts), match/switch 4 (7 pts) (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Field.from (cognitive 23) kafka-connect-sql-common/src/main/scala/io/lenses/sql/Field.scala:27— Field.from has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (17 pts), match/switch 3 (5 pts), boolean chains 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
SchemaSqlExtensions.createRecordSchemaForFlatten (cognitive 22) kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/StructSchemaSql.scala:99— SchemaSqlExtensions.createRecordSchemaForFlatten has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (17 pts), match/switch 3 (5 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BigQuerySinkTask.getRecordTable (cognitive 22) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/BigQuerySinkTask.java:212— BigQuerySinkTask.getRecordTable has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (21 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CosmosDbSinkConnector.start (cognitive 21) kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/sink/CosmosDbSinkConnector.scala:85— CosmosDbSinkConnector.start has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CassandraTableReader.process (cognitive 21) kafka-connect-cassandra/src/main/scala/io/lenses/streamreactor/connect/cassandra/source/CassandraTableReader.scala:270— CassandraTableReader.process has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (14 pts), error handling 1 (2 pts), loops 1 (2 pts), match/switch 2, boolean chains 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
CloudSinkTask.createWriterMan (cognitive 21) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/CloudSinkTask.scala:389— CloudSinkTask.createWriterMan has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
IndexManagerV2.sweepOrphanedLocks (cognitive 21) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/seek/IndexManagerV2.scala:1585— IndexManagerV2.sweepOrphanedLocks has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (9 pts), match/switch 2 (7 pts), error handling 1 (2 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JsonFormatWriter.complete (cognitive 20) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/formats/writer/JsonFormatWriter.scala:70— JsonFormatWriter.complete has cognitive complexity 20 (threshold 15). Drivers by points: loops 6 (18 pts), if/else 2 (nesting depth added 12). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Writer.stage (cognitive 20) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/writer/Writer.scala:177— Writer.stage has cognitive complexity 20 (threshold 15). Drivers by points: loops 3 (9 pts), match/switch 4 (7 pts), if/else 3 (4 pts) (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
PrimaryKeyExtractor.extract (cognitive 20) kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/PrimaryKeyExtractor.scala:120— PrimaryKeyExtractor.extract has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (10 pts), match/switch 6 (10 pts) (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
KeysExtractor.fromStruct (cognitive 20) kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/sink/KeysExtractor.scala:35— KeysExtractor.fromStruct has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (15 pts), match/switch 2 (3 pts), boolean chains 2 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
KeyExtractor.extract (cognitive 20) kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/KeyExtractor.scala:112— KeyExtractor.extract has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (10 pts), match/switch 6 (10 pts) (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
DatalakeStorageInterface.mvFile (cognitive 19) kafka-connect-azure-datalake/src/main/scala/io/lenses/streamreactor/connect/datalake/storage/DatalakeStorageInterface.scala:311— DatalakeStorageInterface.mvFile has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 6 (13 pts), if/else 3 (5 pts), boolean chains 1 (nesting depth added 9). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
DatalakeStorageInterface.writeBlobToFile (cognitive 19) kafka-connect-azure-datalake/src/main/scala/io/lenses/streamreactor/connect/datalake/storage/DatalakeStorageInterface.scala:475— DatalakeStorageInterface.writeBlobToFile has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 7 (10 pts), loops 3 (6 pts), if/else 2, boolean chains 1 (nesting depth added 6). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
CassandraTableReader.processRow (cognitive 19) kafka-connect-cassandra/src/main/scala/io/lenses/streamreactor/connect/cassandra/source/CassandraTableReader.scala:356— CassandraTableReader.processRow has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 1, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WriterManagerCreator.from (cognitive 19) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/WriterManagerCreator.scala:49— WriterManagerCreator.from has cognitive complexity 19 (threshold 15). Drivers by points: loops 5 (12 pts), match/switch 6, error handling 1 (nesting depth added 7). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
AttachLatestSchemaOptimizer.applyLatestSchema (cognitive 19) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/optimization/AttachLatestSchemaOptimizer.scala:94— AttachLatestSchemaOptimizer.applyLatestSchema has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CosmosDbWriterManagerFactory.apply (cognitive 18) kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/sink/writer/CosmosDbWriterManagerFactory.scala:34— CosmosDbWriterManagerFactory.apply has cognitive complexity 18 (threshold 15). Drivers by points: loops 5 (15 pts), match/switch 1 (2 pts), if/else 1 (nesting depth added 11). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
SchemalessEnvelopeConverter.convert (cognitive 18) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/formats/reader/converters/SchemalessEnvelopeConverter.scala:70— SchemalessEnvelopeConverter.convert has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 4 (10 pts), if/else 6 (8 pts) (nesting depth added 8). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
IndexManagerV2.ensureGranularLock (cognitive 18) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/seek/IndexManagerV2.scala:1240— IndexManagerV2.ensureGranularLock has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 3 (11 pts), loops 2 (5 pts), if/else 2 (nesting depth added 11). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
WriterCommitManager.commitBatch (cognitive 18) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/writer/WriterCommitManager.scala:195— WriterCommitManager.commitBatch has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (9 pts), match/switch 3 (9 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WriterManager.attemptForceMasterLockWrite (cognitive 18) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/writer/WriterManager.scala:229— WriterManager.attemptForceMasterLockWrite has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (9 pts), match/switch 2 (7 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ConverterUtil.convert (cognitive 18) kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/schemas/ConverterUtil.scala:211— ConverterUtil.convert has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
2.exitColumn_name (cognitive 18) java-connectors/kafka-connect-query-language/src/main/java/io/lenses/kcql/Kcql.java:355— 2.exitColumn_name has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IndexManagerV2.sweepOrphansUnder (cognitive 17) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/seek/IndexManagerV2.scala:437— IndexManagerV2.sweepOrphansUnder has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), match/switch 3 (6 pts), boolean chains 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
EnvelopeWithSchemaTransformer.toOptional (cognitive 17) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/transformers/EnvelopeWithSchemaTransformer.scala:179— EnvelopeWithSchemaTransformer.toOptional has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (15 pts), match/switch 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PostProcessAction.apply (cognitive 17) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/source/config/PostProcessAction.scala:84— PostProcessAction.apply has cognitive complexity 17 (threshold 15). Drivers by points: loops 5 (16 pts), match/switch 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
MqttManager.messageArrived (cognitive 17) kafka-connect-mqtt/src/main/scala/io/lenses/streamreactor/connect/mqtt/source/MqttManager.scala:80— MqttManager.messageArrived has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 2, error handling 1 (2 pts), match/switch 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CosmosDbWriterManager.createWriter (cognitive 16) kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/sink/writer/CosmosDbWriterManager.scala:121— CosmosDbWriterManager.createWriter has cognitive complexity 16 (threshold 15). Drivers by points: loops 5 (13 pts), if/else 2 (3 pts) (nesting depth added 9). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
IndexManagerV2.drainGcQueue (cognitive 16) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/seek/IndexManagerV2.scala:1480— IndexManagerV2.drainGcQueue has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), error handling 2, match/switch 1 (2 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AvroSchemaExtension.fromPathInternal (cognitive 16) kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/StructSchemaSql.scala:317— AvroSchemaExtension.fromPathInternal has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), match/switch 3 (5 pts), boolean chains 1 (nesting depth added 6). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
MergeQueries.mergeFlush (cognitive 16) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/MergeQueries.java:164— MergeQueries.mergeFlush has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), error handling 1 (3 pts), loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Change coupling: ErrantRecordHandler.scala ↔ AbstractElasticSinkTask.scala kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/dlq/ErrantRecordHandler.scala:1— `kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/dlq/ErrantRecordHandler.scala` and `kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/sink/AbstractElasticSinkTask.scala` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `d40efa8a` improve the logging to make it useful; `1c8b5db0` Ensure a message for each the fields cannot be extracted, or the valu…; `52dc74df` Refactor error handling and documentation in BulkItemErrorClassifier … — run `git show` on any of them.
Near-duplicate member pair (96 shared lines) kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/PrimaryKeyExtractor.scala:120— kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/PrimaryKeyExtractor.scala:120-246 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/KeyExtractor.scala:112-247 — These two members are variants of one another: 96 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (49 shared lines) kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:37— kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:37-118 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/converters/ToJsonWithProjections.scala:42-125 — These two members are variants of one another: 49 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/AvroConverter.scala:46— kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/AvroConverter.scala:46-89 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonConverterWithSchemaEvolution.scala:44-81 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonOptNullConverter.scala:36-66 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonSimpleConverter.scala:42-78 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (49 corresponding lines) · ×1
Edited copy of a member (49 corresponding lines) kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala:242— kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala:242-290 | kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/converters/SinkRecordConverter.scala:246-294 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (38 corresponding lines) · ×1
Edited copy of a member (38 corresponding lines) kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonConverterWithSchemaEvolution.scala:94— kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonConverterWithSchemaEvolution.scala:94-142 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonOptNullConverter.scala:77-114 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (77 corresponding lines) · ×1
Edited copy of a member (77 corresponding lines) kafka-connect-mqtt/src/main/scala/io/lenses/streamreactor/connect/mqtt/config/MqttSinkSettings.scala:54— kafka-connect-mqtt/src/main/scala/io/lenses/streamreactor/connect/mqtt/config/MqttSinkSettings.scala:54-130 | kafka-connect-mqtt/src/main/scala/io/lenses/streamreactor/connect/mqtt/config/MqttSourceSettings.scala:72-149 — These two members are one piece of code written twice and then edited apart: 77 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (81 corresponding lines) · ×1
Edited copy of a member (81 corresponding lines) kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/PrimaryKeyExtractor.scala:28— kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/PrimaryKeyExtractor.scala:28-118 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/KeyExtractor.scala:29-109 — These two members are one piece of code written twice and then edited apart: 81 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×1
Edited copy of a member (20 corresponding lines) kafka-connect-jms/src/main/scala/io/lenses/streamreactor/connect/jms/sink/converters/MapMessageConverter.scala:52— kafka-connect-jms/src/main/scala/io/lenses/streamreactor/connect/jms/sink/converters/MapMessageConverter.scala:52-71 | kafka-connect-jms/src/main/scala/io/lenses/streamreactor/connect/jms/sink/converters/ObjectMessageConverter.scala:54-73 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (43 corresponding lines) · ×1
Edited copy of a member (43 corresponding lines) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/MergeQueries.java:264— java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/MergeQueries.java:264-306 | java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/MergeQueries.java:429-478 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×1
Edited copy of a member (27 corresponding lines) kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/KElasticClient.scala:42— kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/KElasticClient.scala:42-68 | kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/KElasticClient.scala:46-74 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×1
Edited copy of a member (22 corresponding lines) java-connectors/kafka-connect-azure-eventhubs/src/main/java/io/lenses/streamreactor/connect/azure/eventhubs/util/KcqlConfigTopicMapper.java:56— java-connectors/kafka-connect-azure-eventhubs/src/main/java/io/lenses/streamreactor/connect/azure/eventhubs/util/KcqlConfigTopicMapper.java:56-77 | java-connectors/kafka-connect-azure-servicebus/src/main/java/io/lenses/streamreactor/connect/azure/servicebus/util/KcqlConfigBusMapper.java:72-96 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/transformers/AddConnectSchemaTransformer.scala:129— kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/transformers/AddConnectSchemaTransformer.scala:129-151 | kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/transformers/AddConnectSchemaTransformer.scala:154-178 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (35 corresponding lines) · ×1
Edited copy of a member (35 corresponding lines) kafka-connect-cassandra/src/main/scala/io/lenses/streamreactor/common/concurrent/FutureAwaitWithFailFastFn.scala:32— kafka-connect-cassandra/src/main/scala/io/lenses/streamreactor/common/concurrent/FutureAwaitWithFailFastFn.scala:32-66 | kafka-connect-cassandra/src/main/scala/io/lenses/streamreactor/common/concurrent/FutureAwaitWithFailFastFn.scala:68-104 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 22+ corresponding lines) · ×1
Edited copies of one member (3 members, 22+ corresponding lines) kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/Sql.scala:27— kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/Sql.scala:27-48 | kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/StructSql.scala:42-63 | REDACTED:34-55 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×1
Edited copy of a member (16 corresponding lines) kafka-connect-jms/src/main/scala/io/lenses/streamreactor/connect/jms/sink/converters/MapMessageConverter.scala:32— kafka-connect-jms/src/main/scala/io/lenses/streamreactor/connect/jms/sink/converters/MapMessageConverter.scala:32-47 | kafka-connect-jms/src/main/scala/io/lenses/streamreactor/connect/jms/sink/converters/ObjectMessageConverter.scala:34-49 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×1
Edited copy of a member (13 corresponding lines) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/config/PropertiesHelper.scala:55— kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/config/PropertiesHelper.scala:55-67 | kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/config/PropertiesHelper.scala:71-83 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/KElasticBulkClient.scala:230— kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/KElasticBulkClient.scala:230-248 | kafka-connect-opensearch/src/main/scala/io/lenses/streamreactor/connect/opensearch/KOpenSearchClient.scala:276-294 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×1
Edited copy of a member (15 corresponding lines) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/convert/logicaltype/DebeziumLogicalConverters.java:109— java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/convert/logicaltype/DebeziumLogicalConverters.java:109-123 | java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/convert/logicaltype/DebeziumLogicalConverters.java:141-155 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 7+ corresponding lines) · ×1
Edited copies of one member (4 members, 7+ corresponding lines) java-connectors/kafka-connect-azure-eventhubs/src/main/java/io/lenses/streamreactor/connect/azure/eventhubs/util/KcqlConfigTopicMapper.java:86— java-connectors/kafka-connect-azure-eventhubs/src/main/java/io/lenses/streamreactor/connect/azure/eventhubs/util/KcqlConfigTopicMapper.java:86-93 | java-connectors/kafka-connect-azure-servicebus/src/main/java/io/lenses/streamreactor/connect/azure/servicebus/util/KcqlConfigBusMapper.java:105-111 | java-connectors/kafka-connect-common/src/main/java/io/lenses/streamreactor/common/validation/validators/DistinctSourceNamesValidator.java:37-44 | java-connectors/kafka-connect-common/src/main/java/io/lenses/streamreactor/common/validation/validators/DistinctTargetNamesValidator.java:37-44 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 15+ corresponding lines) · ×1
Edited copies of one member (3 members, 15+ corresponding lines) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/formats/reader/converters/BytesOutputRowConverter.scala:36— kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/formats/reader/converters/BytesOutputRowConverter.scala:36-50 | kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/formats/reader/converters/SchemaAndValueConverter.scala:35-49 | kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/formats/reader/converters/TextConverter.scala:36-50 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×1
Edited copy of a member (5 corresponding lines) kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/KElasticClient.scala:77— kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/KElasticClient.scala:77-81 | kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/KElasticClient.scala:83-88 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (51–54 lines × 2) kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/PrimaryKeyExtractor.scala:177— kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/PrimaryKeyExtractor.scala:177-227 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/KeyExtractor.scala:174-227 — before extracting anything, compare `kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/PrimaryKeyExtractor.scala` and `kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/KeyExtractor.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 145 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/PrimaryKeyExtractor.scala:177` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (45 lines × 2) kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/PrimaryKeyExtractor.scala:29— kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/PrimaryKeyExtractor.scala:29-73 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/KeyExtractor.scala:30-74 — before extracting anything, compare `kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/PrimaryKeyExtractor.scala` and `kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/KeyExtractor.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 145 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/PrimaryKeyExtractor.scala:29` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (34–35 lines × 2) kafka-connect-azure-datalake/src/main/scala/io/lenses/streamreactor/connect/datalake/config/CommonConfigDef.scala:35— kafka-connect-azure-datalake/src/main/scala/io/lenses/streamreactor/connect/datalake/config/CommonConfigDef.scala:35-69 | kafka-connect-gcp-storage/src/main/scala/io/lenses/streamreactor/connect/gcp/storage/config/CommonConfigDef.scala:34-67 — before extracting anything, compare `kafka-connect-azure-datalake/src/main/scala/io/lenses/streamreactor/connect/datalake/config/CommonConfigDef.scala` and `kafka-connect-gcp-storage/src/main/scala/io/lenses/streamreactor/connect/gcp/storage/config/CommonConfigDef.scala` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-azure-datalake/src/main/scala/io/lenses/streamreactor/connect/datalake/config/CommonConfigDef.scala:35` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (26–31 lines × 3) kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/AvroConverter.scala:63— kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/AvroConverter.scala:63-89 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonOptNullConverter.scala:41-66 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonSimpleConverter.scala:48-78 — before extracting anything, compare `kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonOptNullConverter.scala` and `kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonSimpleConverter.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/AvroConverter.scala:63` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (30–31 lines × 2) kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/PrimaryKeyExtractor.scala:123— kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/PrimaryKeyExtractor.scala:123-152 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/KeyExtractor.scala:116-146 — before extracting anything, compare `kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/PrimaryKeyExtractor.scala` and `kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/KeyExtractor.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 145 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/PrimaryKeyExtractor.scala:123` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (30 lines × 2) kafka-connect-cassandra/src/main/scala/io/lenses/streamreactor/common/concurrent/FutureAwaitWithFailFastFn.scala:34— kafka-connect-cassandra/src/main/scala/io/lenses/streamreactor/common/concurrent/FutureAwaitWithFailFastFn.scala:34-63 | kafka-connect-cassandra/src/main/scala/io/lenses/streamreactor/common/concurrent/FutureAwaitWithFailFastFn.scala:70-99 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-cassandra/src/main/scala/io/lenses/streamreactor/common/concurrent/FutureAwaitWithFailFastFn.scala:34` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 3) kafka-connect-azure-datalake/src/main/scala/io/lenses/streamreactor/connect/datalake/config/CommonConfigDef.scala:47— kafka-connect-azure-datalake/src/main/scala/io/lenses/streamreactor/connect/datalake/config/CommonConfigDef.scala:47-68 | kafka-connect-common/src/main/scala/io/lenses/streamreactor/common/config/base/traits/RetryConfigSettings.scala:40-61 | kafka-connect-gcp-storage/src/main/scala/io/lenses/streamreactor/connect/gcp/storage/config/CommonConfigDef.scala:45-66 — before extracting anything, compare `kafka-connect-azure-datalake/src/main/scala/io/lenses/streamreactor/connect/datalake/config/CommonConfigDef.scala` and `kafka-connect-gcp-storage/src/main/scala/io/lenses/streamreactor/connect/gcp/storage/config/CommonConfigDef.scala` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-azure-datalake/src/main/scala/io/lenses/streamreactor/connect/datalake/config/CommonConfigDef.scala:47` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 2) kafka-connect-aws-s3/src/main/scala/io/lenses/streamreactor/connect/aws/s3/storage/AwsS3StorageInterface.scala:474— kafka-connect-aws-s3/src/main/scala/io/lenses/streamreactor/connect/aws/s3/storage/AwsS3StorageInterface.scala:474-494 | kafka-connect-gcp-storage/src/main/scala/io/lenses/streamreactor/connect/gcp/storage/storage/GCPStorageStorageInterface.scala:449-469 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-aws-s3/src/main/scala/io/lenses/streamreactor/connect/aws/s3/storage/AwsS3StorageInterface.scala:474` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (19 lines × 3) kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/Sql.scala:28— kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/Sql.scala:28-46 | kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/StructSql.scala:43-61 | REDACTED:35-53 — before extracting anything, compare `kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/Sql.scala` and `kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/StructSql.scala` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14–15 lines × 2) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/writer/Writer.scala:181— kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/writer/Writer.scala:181-195 | kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/writer/Writer.scala:270-283 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/writer/Writer.scala:181` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–14 lines × 2) kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonOptNullConverter.scala:99— kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonOptNullConverter.scala:99-112 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonSimpleConverter.scala:137-149 — before extracting anything, compare `kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonOptNullConverter.scala` and `kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonSimpleConverter.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonOptNullConverter.scala:113` calls `IllegalStateException` and `kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonSimpleConverter.scala:150` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13–15 lines × 2) kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala:97— kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala:97-109 | kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/sink/KeysExtractor.scala:52-66 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala:97` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11–12 lines × 2) kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/KElasticClient.scala:55— kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/KElasticClient.scala:55-66 | kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/KElasticClient.scala:60-70 — before extracting anything, compare `kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/KElasticClient.scala` and `kafka-connect-elastic7/src/main/scala/io/lenses/streamreactor/connect/elastic7/KElasticClient.scala` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-elastic6/src/main/scala/io/lenses/streamreactor/connect/elastic6/KElasticClient.scala:55` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6–11 lines × 4) kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/AvroConverter.scala:62— kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/AvroConverter.scala:62-68 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonConverterWithSchemaEvolution.scala:50-55 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonOptNullConverter.scala:40-45 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonSimpleConverter.scala:47-57 — before extracting anything, compare `kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonOptNullConverter.scala` and `kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonSimpleConverter.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/AvroConverter.scala:62` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonConverterWithSchemaEvolution.scala:48` calls `Some`, `schema` and `kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonOptNullConverter.scala:39` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10–11 lines × 2) kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:78— kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:78-88 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/converters/ToJsonWithProjections.scala:86-95 — before extracting anything, compare `kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala` and `kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/converters/ToJsonWithProjections.scala` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:78` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 2) kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:100— kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:100-109 | kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/converters/ToJsonWithProjections.scala:107-116 — before extracting anything, compare `kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala` and `kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/common/converters/ToJsonWithProjections.scala` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/Transform.scala:100` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (3–5 lines × 3) kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/StructSchemaSql.scala:107— kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/StructSchemaSql.scala:107-109 | kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/StructSql.scala:101-105 | REDACTED:106-110 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/StructSchemaSql.scala:107` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/StructSql.scala:101` calls `Option`, `mkString`, `getOrElse` and `kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/StructSchemaSql.scala:107` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (22–23 lines × 2) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/MergeQueries.java:268— java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/MergeQueries.java:268-289 | java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/MergeQueries.java:337-359 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/MergeQueries.java:268` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12–14 lines × 3) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/MergeQueries.java:265— java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/MergeQueries.java:265-276 | java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/MergeQueries.java:334-345 | java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/MergeQueries.java:430-443 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11–12 lines × 3) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/MergeQueries.java:296— java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/MergeQueries.java:296-306 | java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/MergeQueries.java:362-373 | java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/MergeQueries.java:468-478 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/MergeQueries.java:296` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8–10 lines × 2) java-connectors/kafka-connect-azure-eventhubs/src/main/java/io/lenses/streamreactor/connect/azure/eventhubs/util/KcqlConfigTopicMapper.java:70— java-connectors/kafka-connect-azure-eventhubs/src/main/java/io/lenses/streamreactor/connect/azure/eventhubs/util/KcqlConfigTopicMapper.java:70-77 | java-connectors/kafka-connect-azure-servicebus/src/main/java/io/lenses/streamreactor/connect/azure/servicebus/util/KcqlConfigBusMapper.java:87-96 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `java-connectors/kafka-connect-azure-eventhubs/src/main/java/io/lenses/streamreactor/connect/azure/eventhubs/util/KcqlConfigTopicMapper.java:70` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8–9 lines × 2) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/convert/BigQuerySchemaConverter.java:132— java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/convert/BigQuerySchemaConverter.java:132-139 | java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/convert/BigQuerySchemaConverter.java:228-236 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7–8 lines × 2) java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/SchemaManager.java:656— java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/SchemaManager.java:656-662 | java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/SchemaManager.java:706-713 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 3) java-connectors/kafka-connect-azure-eventhubs/src/main/java/io/lenses/streamreactor/connect/azure/eventhubs/util/KcqlConfigTopicMapper.java:87— java-connectors/kafka-connect-azure-eventhubs/src/main/java/io/lenses/streamreactor/connect/azure/eventhubs/util/KcqlConfigTopicMapper.java:87-93 | java-connectors/kafka-connect-common/src/main/java/io/lenses/streamreactor/common/validation/validators/DistinctSourceNamesValidator.java:38-44 | java-connectors/kafka-connect-common/src/main/java/io/lenses/streamreactor/common/validation/validators/DistinctTargetNamesValidator.java:38-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication· Edited copies of one member (3 members, 11+ corresponding lines) · ×1
Edited copies of one member (3 members, 11+ corresponding lines) test-common/src/main/scala/io/lenses/streamreactor/connect/testcontainers/connect/KafkaConnectClient.scala:65— test-common/src/main/scala/io/lenses/streamreactor/connect/testcontainers/connect/KafkaConnectClient.scala:65-76 | test-common/src/main/scala/io/lenses/streamreactor/connect/testcontainers/connect/KafkaConnectClient.scala:78-88 | test-common/src/main/scala/io/lenses/streamreactor/connect/testcontainers/connect/KafkaConnectClient.scala:90-100 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Off the main sequence: :kafka-connect-query-language — :kafka-connect-query-language: abstractness 0.13, instability 0.00, distance 0.87 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×1
Recursive walk over a caller-supplied document has no depth cap kafka-connect-sql-common/src/main/scala/io/lenses/streamreactor/connect/converters/source/JsonOptNullConverter.scala:80— `JsonOptNullConverter.convert` is public and takes `value: JValue` from its caller, and it calls itself at line 80 with a piece of `value` (and at line 82), not as a tail call the compiler turns into a loop — and nowhere in `JsonOptNullConverter.convert` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a walk like this one throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25), while `ujson.read`, Jackson's `readTree` before 2.15 and circe before 0.14.16 accept any nesting (2,000,000 levels from 4 MB) and circe 0.14.16 accepts 4,096 — on a cold JVM even play-json's cap of 1,000 is past the point the walk fails. `StackOverflowError` is not `NonFatal`: `Try`, `case NonFatal(e)` and `recover` do not stop it, and in a `Future` on the global execution context it leaves the future forever incomplete. Thread a depth argument through `JsonOptNullConverter.convert` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
X18 · Disposal-pattern correctness· Disposable created and abandoned in the function that made it · ×1
Disposable created and abandoned in the function that made it project/Settings.scala:258— `Files.find(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.toArray` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(Files.find(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`.
Orphaned file kafka-connect-ftp/src/main/scala/io/lenses/streamreactor/connect/ftp/source/FtpMonitor.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file kafka-connect-cassandra/src/main/scala/io/lenses/streamreactor/connect/cassandra/config/CassandraConfig.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/converters/SinkRecordConverter.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/StructSchemaSql.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/source/config/CloudSourceSettingsKeys.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file kafka-connect-cassandra/src/main/scala/io/lenses/streamreactor/connect/cassandra/config/CassandraConfigConstants.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/config/FormatSelection.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/StructSql.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file kafka-connect-ftp/src/main/scala/io/lenses/streamreactor/connect/ftp/source/SFTPClient.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file java-connectors/kafka-connect-common/src/main/java/io/lenses/streamreactor/common/security/StoresInfo.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file kafka-connect-cassandra/src/main/scala/io/lenses/streamreactor/connect/cassandra/config/CassandraSettings.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/sink/MongoWriter.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/naming/CloudKeyNamer.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file kafka-connect-cassandra/src/main/scala/io/lenses/streamreactor/connect/cassandra/source/CassandraTypeConverter.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file kafka-connect-http/src/main/scala/io/lenses/streamreactor/connect/http/sink/client/HttpRequestSender.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file kafka-connect-jms/src/main/scala/io/lenses/streamreactor/connect/jms/sink/converters/ProtoStoredAsConverter.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file kafka-connect-mqtt/src/main/scala/io/lenses/streamreactor/connect/mqtt/config/MqttConfig.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file java-connectors/kafka-connect-azure-servicebus/src/main/java/io/lenses/streamreactor/connect/azure/servicebus/sink/TaskToSenderBridge.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/config/CosmosDbConfig.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file java-connectors/kafka-connect-azure-servicebus/src/main/java/io/lenses/streamreactor/connect/azure/servicebus/util/KcqlConfigBusMapper.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file kafka-connect-jms/src/main/scala/io/lenses/streamreactor/connect/jms/config/JMSConfig.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file kafka-connect-common/src/main/scala/io/lenses/streamreactor/connect/json/SimpleJsonConverter.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Blanket warning suppression kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/sink/converter/SinkRecordToDocument.scala:36— A bare `// scalastyle:off`, `// scalafix:off` or `@nowarn` (or Wartremover's `warts.All`) switches every rule or warning off — hidden debt. Suppress the specific rule on the specific line, with a justification, instead.
Blanket warning suppression REDACTED:186— A bare `// scalastyle:off`, `// scalafix:off` or `@nowarn` (or Wartremover's `warts.All`) switches every rule or warning off — hidden debt. Suppress the specific rule on the specific line, with a justification, instead.
Blanket warning suppression kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/formats/reader/converters/SchemalessEnvelopeConverter.scala:137— A bare `// scalastyle:off`, `// scalafix:off` or `@nowarn` (or Wartremover's `warts.All`) switches every rule or warning off — hidden debt. Suppress the specific rule on the specific line, with a justification, instead.
Blanket warning suppression kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/sink/ConverterUtilProxy.scala:24— A bare `// scalastyle:off`, `// scalafix:off` or `@nowarn` (or Wartremover's `warts.All`) switches every rule or warning off — hidden debt. Suppress the specific rule on the specific line, with a justification, instead.
Blanket warning suppression kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/sink/MongoWriter.scala:48— A bare `// scalastyle:off`, `// scalafix:off` or `@nowarn` (or Wartremover's `warts.All`) switches every rule or warning off — hidden debt. Suppress the specific rule on the specific line, with a justification, instead.
Blanket warning suppression kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/sink/SinkRecordToDocument.scala:76— A bare `// scalastyle:off`, `// scalafix:off` or `@nowarn` (or Wartremover's `warts.All`) switches every rule or warning off — hidden debt. Suppress the specific rule on the specific line, with a justification, instead.
Duplicated predicate java-connectors/kafka-connect-azure-eventhubs/src/main/java/io/lenses/streamreactor/connect/azure/eventhubs/source/EventHubsKafkaConsumerController.java:87— `consumerRecords != null && !consumerRecords.isEmpty()` appears character-identically in 2 files — java-connectors/kafka-connect-azure-eventhubs/src/main/java/io/lenses/streamreactor/connect/azure/eventhubs/source/EventHubsKafkaConsumerController.java, java-connectors/kafka-connect-azure-eventhubs/src/main/java/io/lenses/streamreactor/connect/azure/eventhubs/source/KafkaByteBlockingQueuedProducer.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate .claude/helpers/graft-hooks.cjs:6— `process.env.CLAUDE_PROJECT_DIR || process.cwd()` appears character-identically in 2 files — .claude/helpers/graft-hooks.cjs, .claude/helpers/graft-statusline.cjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/transformers/EnvelopeWithSchemaTransformer.scala:35— `message.topic != topic && topic != Topic.All` appears character-identically in 2 files — kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/transformers/EnvelopeWithSchemaTransformer.scala, kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/transformers/SchemalessEnvelopeTransformer.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala:98— `schema != null && Date.LOGICAL_NAME == schema.name` appears character-identically in 2 files — kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala, kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/sink/KeysExtractor.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala:100— `schema != null && Time.LOGICAL_NAME == schema.name` appears character-identically in 2 files — kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala, kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/sink/KeysExtractor.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Interpolated log message defeats structured logging java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/GcpClientBuilder.java:104— `warn` at line 104 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging java-connectors/kcbq-connector/src/main/java/com/wepay/kafka/connect/bigquery/SchemaManager.java:336— `debug` at line 336 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging java-connectors/kafka-connect-sink-reporting/src/main/java/io/lenses/streamreactor/connect/reporting/ReportSender.java:87— `info` at line 87 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging java-connectors/kafka-connect-sink-reporting/src/main/java/io/lenses/streamreactor/connect/reporting/ReportSender.java:123— `info` at line 123 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging java-connectors/kafka-connect-sink-reporting/src/main/java/io/lenses/streamreactor/connect/reporting/model/RecordConverter.java:92— `warn` at line 92 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Fat interface: CloudSinkMetricsMBean (71 abstract members) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/metrics/CloudSinkMetricsMBean.scala:35— `CloudSinkMetricsMBean` declares 71 abstract members: `getWriterCount`, `getIdleWriterEvictions`, `getGranularCacheSize`, `getGranularCacheHits`, `getGranularCacheMisses`, `getGcQueueDepth`, `getGcLocksEnqueued`, `getGcLocksDeleted`, `getGcLocksSkippedReclaimed`, `getGcLocksSkippedRevoked`, `getGcDeleteFailures`, `getGcDeleteRetries`, `getMasterLockUpdates`, `getMasterLockFailures`, `getMasterLockWriteSkipped`, `getMasterLockWriteForcedRevoke`, `getMasterLockWriteForcedStop`, `getMasterLockWriteForcedPostCleanUp`, `getMasterLockWriteForcedRevokeFailures`, `getMasterLockWriteForcedStopFailures`, `getMasterLockWriteForcedPostCleanUpFailures`, `getMasterLockDirtyWindowCycles`, `getMasterLockDirty`, `getSweepRuns`, `getSweepOrphansEnqueued`, `getSweepGetBudgetUsed`, `getSafeOffsetBarrierWriters`, `getRecordsReceivedTotal`, `getRecordsWrittenTotal`, `getNullRecordsSkippedTotal`, `getLastPutEpochMillis`, `getPutTimerCount`, `getPutTimerSumMillis`, `getPutTimerMaxMillis`, `getFilesOpenedTotal`, `getFilesCommittedTotal`, `getFilesFailedTotal`, `getBytesWrittenTotal`, `getRecordsCommittedTotal`, `getCommitTimerCount`, and 31 more. 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.
Fat interface: IndexManager (16 abstract members) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/seek/IndexManager.scala:27— `IndexManager` declares 16 abstract members: `indexingEnabled`, `open`, `update`, `getSeekedOffsetForTopicPartition`, `getSeekedOffsetForPartitionKey`, `updateForPartitionKey`, `batchDedupFloor`, `afterBatchCommit`, `updateMasterLock`, `cleanUpObsoleteLocks`, `ensureGranularLock`, `evictGranularLock`, `evictAllGranularLocks`, `clearTopicPartitionState`, `suspendBackgroundWork`, `close`. 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.
Fat interface: StorageInterface[SM] (19 abstract members) kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/storage/StorageInterface.scala:31— `StorageInterface[SM]` declares 19 abstract members: `system`, `uploadFile`, `close`, `pathExists`, `list`, `listFileMetaRecursive`, `listKeysRecursive`, `seekToFile`, `getBlob`, `getBlobAsString`, `writeBlobToFile`, `getBlobAsStringAndEtag`, `getMetadata`, `writeStringToFile`, `deleteFiles`, `deleteFile`, `mvFile`, `createDirectoryIfNotExists`, `touchFile`. 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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 37 significant file(s) lose their only recent owner: kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/seek/IndexManagerV2.scala, kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/metrics/CloudSinkMetricsMBean.scala, kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/writer/JsonBulkWriter.scala, kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/seek/PendingOperationsProcessors.scala, kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/dlq/ErrantRecordHandler.scala, kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/optimization/AttachLatestSchemaOptimizer.scala, kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/sink/CloudSinkTask.scala, kafka-connect-elastic-common/src/main/scala/io/lenses/streamreactor/connect/elastic/common/sink/AbstractElasticSinkTask.scala (+29 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 8 significant file(s) lose their only recent owner: kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/config/CosmosDbConfig.scala, kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/sink/converter/SinkRecordToDocument.scala, kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/sink/writer/CosmosDbWriterManager.scala, kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/sink/writer/CosmosDbBulkWriter.scala, kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/sink/CosmosDbSinkConnector.scala, kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/sink/CosmosDbSinkTask.scala, kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/CosmosClientProvider.scala, kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/sink/writer/CosmosDbSingleWriter.scala. Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 1 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (46 single-owned of 402 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 402 of the 816 production source files in this repository met that bar). They are anonymized user #3 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: kafka-connect-cloud-common/src/main/scala/io/lenses/streamreactor/connect/cloud/common/source/files/DateOrderingBatchLister.scala.
No ADRs found java-connectors/build.gradle:49— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `java-connectors/build.gradle` makes this repository a deployable product (line 49).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 10 project(s) overshoot their size bounds, lowering Project Cohesion to 8.0/10. The most over is `(repository root)` (56020 LoC, 1202 module-visible types across 162 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 198 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: kafka-connect-ftp/src/main/scala/io/lenses/streamreactor/connect/ftp/source/FtpMonitor.scala, kafka-connect-mongodb/src/main/scala/io/lenses/streamreactor/connect/mongodb/converters/SinkRecordConverter.scala, kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/StructSchemaSql.scala, kafka-connect-azure-cosmosdb/src/main/scala/io/lenses/streamreactor/connect/azure/cosmosdb/converters/SinkRecordConverter.scala, kafka-connect-sql-common/src/main/scala/io/lenses/connect/sql/StructSql.scala, kafka-connect-ftp/src/main/scala/io/lenses/streamreactor/connect/ftp/source/SFTPClient.scala, java-connectors/kafka-connect-common/src/main/java/io/lenses/streamreactor/common/security/StoresInfo.java, REDACTED (and 190 more) (200 orphaned of 402 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 402 of the 816 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No SAST REDACTED:3— No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 6 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling· Dependabot does not watch github-actions/maven · ×1
Dependabot does not watch github-actions/maven REDACTED:6— `REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, `maven`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list.
No release approval gate — Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
X5 · Nullable reference types· Scala's null is not held to the type system everywhere · ×1
Scala's null is not held to the type system everywhere — No build over this repository's 639 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.
Off the main sequence: common — common: abstractness 0.20, instability 0.00, distance 0.80 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
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.
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.
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.
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.
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.
Run 01a1da7a-b1bd-7162-9524-ce38b144ea85 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 105 · Warnings: 299 · Recommendations: 231 · Info: 1 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 14:33 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.