Public report — scio, published 27 Sep 2026. Concrete security findings (which rule fired, in which file, on which line; CVE IDs, secret matches, dependency versions) are REDACTED in this version; ask the repo owner for the full report.
Public
Codebase survey Measured under the Code Assurance Index · rubric rubric-2026.09.15 (frozen) · verify this survey Filed cd_c39728dec09c404f9a62ca44bfa6926b Filed 27 September 2026, 16:12 UTC Public

Spotify/scio

Measured 27 September 2026, 15:24 UTC

knowledge concentrated in recent work
71% Strong
CriticalWeakAdequateStrongExemplary
Architecture 99% Exemplary Code Health 86% Strong Readiness 86% Exemplary Security 72% Adequate Maturity 60% Adequate

Medium · 84,505 LoC · rebuild ~1.2 person-years · weakest lens: Maturity (60%)

Findings by grade

69 critical 276 serious 6 minor 46 could not be resolved — could be critical — see Limitations

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
27 September 2026, 15:24 UTC

A measurement, not a certificate. The Code Assurance Index does not certify, approve or guarantee this codebase; it records a reproducible number and the evidence it was computed from. The standard is authored by Canine Development, who also build Watchdog — its only implementation today. That is said here so the number is checked rather than believed.

Grounded in facts. Every number here is computed, not narrated — reproducible, tool-backed, and traceable to a line of code. How to trust this ▸

24/27dimensions tool-verifieddeterministic · confidence 1.0 · 3 LLM-assisted, advisory
340findings with an exact file:lineof 351 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
27/115dimensions across the health lenses84505 LoC — wide & deep
Chapters

Executive summary

Preview (pre-1.0). This repo hasn't declared a stable release, so it's judged against a relaxed, pre-production bar.

The system holds a strong overall standing at 71%, indicating a robust foundation that is largely healthy but carries specific, manageable risks. With a medium footprint of over 84,000 lines of production code and a rebuild cost of approximately €170,000, this asset represents significant value that requires careful stewardship to protect delivery speed and operational reliability.

The primary risk lies in knowledge maturity. While the code structure is excellent, the team’s ability to onboard new engineers and maintain long-term stability is compromised by a maturity score of 60%. This gap means that critical context is not easily accessible, increasing the cost of changes and the risk of defects when staff turnover occurs. Without clear documentation, the system becomes fragile to maintain, potentially slowing future development cycles and increasing reliance on specific individuals.

Conversely, the architecture and code health are genuinely strong. The high scores in these areas suggest that the system is well-organized, secure, and ready for production operations. This structural integrity provides a solid base for future enhancements, ensuring that new features can be added with minimal risk of breaking existing functionality. The low boilerplate content further indicates that the codebase is focused and efficient, reducing technical debt in the core logic.

To maximize leverage, the immediate focus should be on capturing significant decisions. Implementing a simple, consistent record of architectural choices will quickly address the maturity gap, making the system more understandable and maintainable for any team member. This low-effort, high-impact action will stabilize the asset’s long-term value. While other improvements are noted, establishing this decision log is the most critical step to securing the system’s operational resilience and reducing future maintenance costs.

Code Health 86% Strong Architecture 99% ★ Exemplary Maturity 60% Adequate · gated by M2 Readiness 86% ★ Exemplary Security 72% Adequate · gated by D29
How the score is built — each lens's share of the headline Width is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
Maturity 60% · 47% weightSecurity 72% · 26% weightReadiness 86% · 14% weightCode Health 86% · 8% weightArchitecture 99% · 4% weight

Raise Maturity 60 → 70 (the Healthy floor) ⇒ headline 71 → ~75.

Code composition — where the lines go
Tests 100%
New since the last scan (100+)

344 finding(s) are new versus the previous scan (2026-08-07) — surfaced by this scheduled scan itself, no pull request required. Showing the first 100; the full set is in the report.

  • D1 · FixAvroCoder.fix (cyclomatic 29) scalafix/rules/src/main/scala/fix/v0_14_0/FixAvroCoder.scala
  • D1 · MultiJoin.apply (cyclomatic 23) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D1 · MultiJoin.left (cyclomatic 23) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D1 · MultiJoin.outer (cyclomatic 23) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D1 · TypeProvider.schemaToType (cyclomatic 23) scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/TypeProvider.scala
  • D1 · MultiJoin.apply (cyclomatic 22) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D1 · MultiJoin.left (cyclomatic 22) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D1 · MultiJoin.outer (cyclomatic 22) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D1 · ConverterProvider.fromAvroInternal (cyclomatic 22) scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala
  • D1 · MultiJoin.apply (cyclomatic 21) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D1 · MultiJoin.left (cyclomatic 21) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D1 · MultiJoin.outer (cyclomatic 21) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D1 · SoccoPhase.typeTokens (cyclomatic 21) socco-plugin/src/main/scala/Socco.scala
  • D1 · MultiSourceKeyGroupReader.advance (cyclomatic 21) scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java
  • D1 · MultiJoin.apply (cyclomatic 20) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D1 · MultiJoin.left (cyclomatic 20) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D1 · MultiJoin.outer (cyclomatic 20) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D1 · TypeProvider.schemaToType (cyclomatic 19) scio-avro/src/main/scala/com/spotify/scio/avro/types/TypeProvider.scala
  • D1 · MultiJoin.apply (cyclomatic 19) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D1 · MultiJoin.left (cyclomatic 19) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D1 · MultiJoin.outer (cyclomatic 19) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D1 · StorageUtil.setRawType (cyclomatic 19) scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/StorageUtil.scala
  • D1 · MultiJoin.apply (cyclomatic 18) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D1 · MultiJoin.left (cyclomatic 18) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D1 · MultiJoin.outer (cyclomatic 18) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D1 · MultiJoin.apply (cyclomatic 17) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D1 · MultiJoin.left (cyclomatic 17) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D1 · MultiJoin.outer (cyclomatic 17) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D1 · MultiJoin.apply (cyclomatic 16) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D1 · MultiJoin.left (cyclomatic 16) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D1 · MultiJoin.outer (cyclomatic 16) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.apply (cognitive 253) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.left (cognitive 253) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.outer (cognitive 253) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.apply (cognitive 231) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.left (cognitive 231) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.outer (cognitive 231) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.apply (cognitive 210) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.left (cognitive 210) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.outer (cognitive 210) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.apply (cognitive 190) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.left (cognitive 190) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.outer (cognitive 190) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.apply (cognitive 171) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.left (cognitive 171) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.outer (cognitive 171) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.apply (cognitive 153) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.left (cognitive 153) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.outer (cognitive 153) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.apply (cognitive 136) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.left (cognitive 136) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.outer (cognitive 136) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.apply (cognitive 120) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.left (cognitive 120) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.outer (cognitive 120) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.apply (cognitive 105) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.left (cognitive 105) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.outer (cognitive 105) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.apply (cognitive 91) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.left (cognitive 91) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.outer (cognitive 91) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.apply (cognitive 78) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.left (cognitive 78) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.outer (cognitive 78) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.apply (cognitive 66) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.left (cognitive 66) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.outer (cognitive 66) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.apply (cognitive 55) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.left (cognitive 55) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.outer (cognitive 55) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiSourceKeyGroupReader.advance (cognitive 51) scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java
  • D2 · MultiJoin.apply (cognitive 45) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.left (cognitive 45) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.outer (cognitive 45) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.apply (cognitive 36) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.left (cognitive 36) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.outer (cognitive 36) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · FixAvroCoder.fix (cognitive 30) scalafix/rules/src/main/scala/fix/v0_14_0/FixAvroCoder.scala
  • D2 · MultiJoin.apply (cognitive 28) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.left (cognitive 28) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.outer (cognitive 28) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · ScioContext.parseArguments (cognitive 27) scio-core/src/main/scala/com/spotify/scio/ScioContext.scala
  • D2 · Functions.combineFn (cognitive 22) scio-core/src/main/scala/com/spotify/scio/util/Functions.scala
  • D2 · MultiJoin.apply (cognitive 21) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.left (cognitive 21) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · MultiJoin.outer (cognitive 21) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D2 · StorageUtil.setRawType (cognitive 18) scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/StorageUtil.scala
  • D2 · RemoteFileUtil.downloadImpl (cognitive 18) scio-core/src/main/java/com/spotify/scio/util/RemoteFileUtil.java
  • D2 · SortBucketShardDoFn.processElement (cognitive 17) scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/SortedBucketSink.java
  • D2 · SpecificRecordDatumFactory.addLogicalTypeConversions (cognitive 16) scio-avro/src/main/scala/com/spotify/scio/avro/AvroDatumFactory.scala
  • D2 · ParquetReadFn.processElement (cognitive 16) scio-parquet/src/main/scala/com/spotify/scio/parquet/read/ParquetReadFn.scala
  • D3 · FileTooLong: util/MultiJoin.scala scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D3 · TooManyMethods: SCollection scio-core/src/main/scala/com/spotify/scio/values/SCollection.scala
  • D3 · FileTooLong: util/SMBMultiJoin.scala scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala
  • D3 · TooManyMethods: MultiJoin scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
  • D3 · TooManyMethods: SMBMultiJoin scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala
  • D3 · TooManyMethods: PairSCollectionFunctions scio-core/src/main/scala/com/spotify/scio/values/PairSCollectionFunctions.scala
  • D3 · TooManyMethods: TableRowOps scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/syntax/TableRowSyntax.scala
  • D3 · FileTooLong: bigquery/BigQueryIO.scala scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/BigQueryIO.scala
  • D3 · ClassTooLong: SortedBucketSink scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/SortedBucketSink.java

A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.

Rebuild cost & value ~ Modeled — €57,000–€280,000
Cost to rebuild€57,000–€280,000 (0.6–1.8 person-years (943–2,993 h), ~1–3 engineers)
Domain complexityStandard — harder problems cost more per line
Quality factor1.0× (at 71% quality) — the last 20% of quality is most of the work
Size & shapeMedium · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)

This codebase represents roughly ~1.2 person-years of build effort (about ~€170,000 to rebuild). Its weakest lens is Maturity at 60% — the part of that asset most exposed by the findings below.

How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.0) — standard service × a 1.0× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source · effort from total production LoC as straight-line logic (the tier split is a C#-only syntax walk), a conservative lower bound. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).

Top priorities

The highest-leverage moves; the full ranked list is in the Roadmap below.

1
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).
+10.4 pts · Medium effort · Architecture documentation
2
Add a 'Testing' section to the root README — how to run the test suite.
+9.5 pts · Medium effort · Documentation (README)
3
Improve Documentation Quality — currently 7.0/10.
+6.4 pts · Medium effort · Documentation Quality

Diagnosis — what's actually going on

Value concentrated against a weak lens · Medium · Value at risk
This is a Medium asset (~1.2 person-years to rebuild), and its weakest lens is Maturity at 60%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
Evidence: valuation: Medium, ~1.2 person-years rebuild (84,505 LoC) · weakest lens: Maturity 60%
→ Direct remediation budget at Maturity first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form). The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).

Architecture — module dependency matrix

Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)

304 modules, 642 dependencies. 2 dependency cycles across 29 modules, marked above the diagonal.

Showing the 40 most-connected modules; 264 more are not drawn.

Module dependency matrix. The row depends on the column; the number is how many type pairs create the dependency. A cell above the diagonal is part of a dependency cycle.
depends on →1 com.spotify.scio.bigquery.client.CompressionT2 com.spotify.scio.bigtable.TableAdmin3 com.spotify.scio.examples.extra.MagnolifyTypedBigQueryTornadoes4 com.spotify.scio.parquet.read.ParquetReadFn.SplitGranularity5 com.spotify.scio.redis.types6 fix.v0_13_0.FixTfParameter7 com.spotify.scio.extra.csv.CsvIO8 com.spotify.scio.schemas9 com.spotify.scio.coders10 com.spotify.scio.io.dynamic.syntax11 com.spotify.scio.io12 com.spotify.scio.bigquery.BigQueryTyped13 com.spotify.scio.elasticsearch14 com.spotify.scio.bigquery.client15 com.spotify.scio.bigquery16 com.spotify.scio.values17 com.spotify.scio.testing.JobTest18 com.spotify.scio.util19 com.spotify.scio.avro.AvroIO20 com.spotify.scio.coders.instances21 com.spotify.scio.extra.sparkey.instances22 com.spotify.scio.bigquery.BigQueryTypedTable23 com.spotify.scio.iceberg24 com.spotify.scio.bigquery.BigQueryTypedTable.Format25 com.spotify.scio.avro.syntax26 com.spotify.scio.bigquery.types27 com.spotify.scio.testing28 com.spotify.scio.bigquery.syntax29 fix.v0_14_030 com.spotify.scio31 com.spotify.scio.avro32 com.spotify.scio.bigtable33 com.spotify.scio.examples.extra34 com.spotify.scio.extra.sparkey35 com.spotify.scio.jdbc.sharded36 com.spotify.scio.parquet.avro37 com.spotify.scio.parquet.avro.syntax38 com.spotify.scio.parquet.tensorflow39 com.spotify.scio.redis40 com.spotify.scio.jdbc.syntax
1 com.spotify.scio.bigquery.client.CompressionT
2 com.spotify.scio.bigtable.TableAdmin
3 com.spotify.scio.examples.extra.MagnolifyTypedBigQueryTornadoes
4 com.spotify.scio.parquet.read.ParquetReadFn.SplitGranularity
5 com.spotify.scio.redis.types
6 fix.v0_13_0.FixTfParameter
7 com.spotify.scio.extra.csv.CsvIO27444
8 com.spotify.scio.schemas113111
9 com.spotify.scio.coders111111
10 com.spotify.scio.io.dynamic.syntax1111
11 com.spotify.scio.io2321192413
12 com.spotify.scio.bigquery.BigQueryTyped57414
13 com.spotify.scio.elasticsearch113121
14 com.spotify.scio.bigquery.client111
15 com.spotify.scio.bigquery111111691915221314
16 com.spotify.scio.values2164317
17 com.spotify.scio.testing.JobTest11241
18 com.spotify.scio.util442
19 com.spotify.scio.avro.AvroIO1
20 com.spotify.scio.coders.instances14681953
21 com.spotify.scio.extra.sparkey.instances11221
22 com.spotify.scio.bigquery.BigQueryTypedTable131
23 com.spotify.scio.iceberg112121
24 com.spotify.scio.bigquery.BigQueryTypedTable.Format2
25 com.spotify.scio.avro.syntax33710762
26 com.spotify.scio.bigquery.types5112
27 com.spotify.scio.testing11712841112
28 com.spotify.scio.bigquery.syntax24266158126134
29 fix.v0_14_03162642
30 com.spotify.scio1722111514
31 com.spotify.scio.avro68198559
32 com.spotify.scio.bigtable1211433
33 com.spotify.scio.examples.extra12252414
34 com.spotify.scio.extra.sparkey32163141
35 com.spotify.scio.jdbc.sharded1211
36 com.spotify.scio.parquet.avro11132112
37 com.spotify.scio.parquet.avro.syntax2214132
38 com.spotify.scio.parquet.tensorflow1132112
39 com.spotify.scio.redis1312112
40 com.spotify.scio.jdbc.syntax213221
Dependency, pointing down the layeringAbove the diagonal — part of a cycleThe module itself
…y.client.CompressionT…o.bigtable.TableAdmin…ypedBigQueryTornadoes…adFn.SplitGranularity…tify.scio.redis.types…0_13_0.FixTfParameter….scio.extra.csv.CsvIO….spotify.scio.schemas…m.spotify.scio.coders…cio.io.dynamic.syntaxcom.spotify.scio.io…igquery.BigQueryTyped…fy.scio.elasticsearch….scio.bigquery.client…spotify.scio.bigquery…m.spotify.scio.values….scio.testing.JobTestcom.spotify.scio.util…tify.scio.avro.AvroIO…scio.coders.instances…tra.sparkey.instances…ry.BigQueryTypedTable….spotify.scio.iceberg…ueryTypedTable.Format…tify.scio.avro.syntax…y.scio.bigquery.types….spotify.scio.testing….scio.bigquery.syntaxfix.v0_14_0com.spotify.sciocom.spotify.scio.avro…spotify.scio.bigtable…y.scio.examples.extra…fy.scio.extra.sparkey…ify.scio.jdbc.sharded…ify.scio.parquet.avro…o.parquet.avro.syntax…io.parquet.tensorflowcom.spotify.scio.redis…tify.scio.jdbc.syntax…y.client.CompressionT1…o.bigtable.TableAdmin2…ypedBigQueryTornadoes3…adFn.SplitGranularity4…tify.scio.redis.types5…0_13_0.FixTfParameter6….scio.extra.csv.CsvIO7….spotify.scio.schemas8…m.spotify.scio.coders9…cio.io.dynamic.syntax10com.spotify.scio.io11…igquery.BigQueryTyped12…fy.scio.elasticsearch13….scio.bigquery.client14…spotify.scio.bigquery15…m.spotify.scio.values16….scio.testing.JobTest17com.spotify.scio.util18…tify.scio.avro.AvroIO19…scio.coders.instances20…tra.sparkey.instances21…ry.BigQueryTypedTable22….spotify.scio.iceberg23…ueryTypedTable.Format24…tify.scio.avro.syntax25…y.scio.bigquery.types26….spotify.scio.testing27….scio.bigquery.syntax28fix.v0_14_029com.spotify.scio30com.spotify.scio.avro31…spotify.scio.bigtable32…y.scio.examples.extra33…fy.scio.extra.sparkey34…ify.scio.jdbc.sharded35…ify.scio.parquet.avro36…o.parquet.avro.syntax37…io.parquet.tensorflow38com.spotify.scio.redis39…tify.scio.jdbc.syntax402744411311111111111112321192413574141131211111111116919152213142164317112414421146819531122113111212123371076251121171284111224266158126134316264217221115146819855912114331225241432163141121111132112221413211321121312112213221+264 more modules (most-connected shown)

At a glance — Code Health · 86% · Strong ·

The Good
D1 · Scala Cyclomatic Complexity 7.3 D3 · Scala God Classes 9.1 D4 · Scala Code Duplication 9.5 D17 · Scala Explicit Debt 9.9
The Bad
D2 · Scala Cognitive Complexity 5.0

At a glance — Architecture · 99% · Exemplary ·

The Good
D6 · Scala Cohesion (LCOM4) 9.8 D35 · Scala Change Coupling 10.0 AX10 · Repo Code composition 10.0

At a glance — Maturity · 60% · Adequate · gated by M2 ·

The Good
D15 · Scala Churn × Complexity Hotspots 10.0 D16 · Scala Bus Factor 9.8 D19 · Scala Documentation Quality 7.0 D21 · Scala Naming Consistency 10.0 M1 · Repo Documentation (README) 7.2 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 10.0
The Ugly
M2 · Repo Architecture documentation 0.0

At a glance — Readiness · 86% · Exemplary ·

The Good
D9 · Scala Test Distribution 10.0 D13 · Scala Secret Scanning 10.0 P1 · Repo CI/CD gates 10.0 P3 · Repo Security & performance tooling 8.0 P4 · Repo Deployment & Rollback 7.0 P6 · Repo Release Hygiene 10.0

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

The Good
D28 · Scala Secrets (history) 10.0 D31 · Scala IaC & Container Security 10.0 D37 · Scala Vulnerability-disclosure Policy 10.0
The Bad
D36 · Scala Supply-chain Provenance & Signing 5.0
The Ugly
D29 · Scala Static Analysis (SAST) 0.9

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A03:2021 — Injection69High / Critical

Roadmap

Begin by establishing a formal record of significant architectural decisions in a dedicated directory to capture context and consequences. Simultaneously, enhance the root README by adding a clear section on how to run the test suite and address the existing documentation quality gaps. Finally, resolve the identified static analysis findings in the CI and publishing workflows to eliminate security risks related to secrets and unpinned actions.

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

Do thisHelpsEffortDimension
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).+10.4 ptsMediumArchitecture documentation
Add a 'Testing' section to the root README — how to run the test suite.+9.5 ptsMediumDocumentation (README)
Improve Documentation Quality — currently 7.0/10.+6.4 ptsMediumDocumentation Quality
Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (2), REDACTED.+3.4 ptsMediumStatic Analysis (SAST)
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED.+1.0 ptsLowStatic Analysis (SAST)
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.+0.7 ptsLowSupply-chain Provenance & Signing
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.+0.7 ptsLowSupply-chain Provenance & Signing
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.+0.7 ptsLowSupply-chain Provenance & Signing

File quality

Per-file score 0–10 — a quality signature. Of 98 files carrying findings, judged against the Preview bar: 0% slop · 19% mixed · 81% near-clean.

FileScoreBandWorst signal
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
scio-avro/src/main/scala/com/spotify/scio/avro/types/TypeProvider.scala6.0MixedExplicit Debt: TodoComment
scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/StorageUtil.scala6.0MixedExplicit Debt: FixmeComment
scio-core/src/main/scala/com/spotify/scio/ScioContext.scala6.0MixedExplicit Debt: FixmeComment
scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/SortedBucketSink.java6.0MixedExplicit Debt: TodoComment
scio-core/src/main/scala/com/spotify/scio/values/SCollection.scala6.0MixedExplicit Debt: TodoComment
scio-core/src/main/scala/com/spotify/scio/util/random/RandomSampler.scala6.6MixedExplicit Debt: TodoComment
scio-test/core/src/test/scala/com/spotify/scio/testing/SCollectionMatchersTest.scala6.6MixedExplicit Debt: FixmeComment
scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/TypeProvider.scala6.7MixedExplicit Debt: TodoComment
scio-avro/src/main/scala/com/spotify/scio/avro/AvroDatumFactory.scala6.7MixedExplicit Debt: TodoComment
scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/BigQueryIO.scala6.7MixedExplicit Debt: TodoComment
scio-snowflake/src/main/scala/com/spotify/scio/snowflake/SnowflakeIO.scala6.7MixedExplicit Debt: TodoComment
scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/taps.scala6.7MixedExplicit Debt: TodoComment
scio-avro/src/test/scala/com/spotify/scio/avro/AvroIOTest.scala6.9MixedExplicit Debt: TodoComment
scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala7.0Near-cleanCyclomatic Complexity: MultiJoin.apply (cyclomatic 23)

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 69

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

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

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

Could not be resolved — 46

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 24 of 27 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three 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; ◐ Advisory — an LLM prose judgement. 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; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 27 dimensions across the health lenses
D1D2D3D4D6D9D13D15D16D17D19D21D28D29D31D35D36D37AX10M1M2M3M4P1P3P4P6

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 340 of 351 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Watchdog duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurementLocal LLM◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a0e377-cdcc-7877-a0bc-78261a60e836.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D4 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 87 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .java (23,637 lines, 28% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
  • D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a coverage step in CI (`codecov/codecov-action`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.java, .scala), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report` or the Gradle `jacocoTestReport` task, or `addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report` or the Gradle `jacocoTestReport` task, or `addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.java, .scala) and this repository declares an sbt build (repository root, 261 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 — evaluation did not complete — Dependency Hygiene not included (check did not complete) — excluded from the score.
  • D14 License Compliance — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository's package manifest is not parsed for licence data yet. A gap in the analyzer's language coverage, NOT a finding that the repository's licenses are compliant (an sbt build (build.sbt)), which this pass does not parse yet — so this dimension asserts nothing about this repository's licensing in either direction.
  • D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (scalafix/build.sbt), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
  • D34 Knowledge Freshness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. File-level freshness contradicts repo activity: 38 commits in the last 90 days, yet 376 of 418 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
  • D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (go.mod, a Gemfile's ruby directive, a Dockerfile) is simply not read here yet.
  • AX3 Project dependency cycles — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over which project references which. That is a language-neutral question, but the project-reference graph is collected from MSBuild .csproj, Gradle and Maven builds only, and this repository commits none — so there was no graph to read, and re-running the same commit reads the same nothing. Its modules are declared as: sbt subprojects (build.sbt). A reader for that graph is the collector this check is missing. That is a COLLECTOR gap in this analyzer — no change to the scan image closes it — and not a finding that the repository is free of what this check looks for.
  • AX4 Dependency direction — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the direction each project reference points. That is a language-neutral question, but the project-reference graph is collected from MSBuild .csproj, Gradle and Maven builds only, and this repository commits none — so there was no graph to read, and re-running the same commit reads the same nothing. Its modules are declared as: sbt subprojects (build.sbt). A reader for that graph is the collector this check is missing. That is a COLLECTOR gap in this analyzer — no change to the scan image closes it — and not a finding that the repository is free of what this check looks for.
  • AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • AX8 Test isolation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over which projects are test projects, and what they reference. That is a language-neutral question, but the project-reference graph is collected from MSBuild .csproj, Gradle and Maven builds only, and this repository commits none — so there was no graph to read, and re-running the same commit reads the same nothing. Its modules are declared as: sbt subprojects (build.sbt). A reader for that graph is the collector this check is missing. That is a COLLECTOR gap in this analyzer — no change to the scan image closes it — and not a finding that the repository is free of what this check looks for.
  • AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, or a Dockerfile. None was found, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
  • C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
  • C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
  • C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit 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 audit controls.
  • C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention 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 retention controls.
  • C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights 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 data-subject rights controls.
  • ED5 Idempotency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds retry-prone mutations by walking the repository's declared types, and NONE was loaded on this run, so it had nothing to look at. That is a limit of the analyzer's reach — it reads .NET projects — not a finding that this repository has no command handlers or message consumers.
  • GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and none applies: this repository publishes a library and deploys nothing (no container, IaC or deployment manifest), so it holds no runtime state of its own. Any data-access dependency it declares is the store it is a CLIENT for, not one it operates. The DR control belongs to whoever runs that data.
  • S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security 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 web-security controls.
  • X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X14 Bypassable address classification — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X20 Mistyped argument guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X21 Side-effecting pattern guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X26 Unsynchronised callback handoff — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X27 Collection changed while being enumerated — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X28 Index access outside its own emptiness guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X29 Per-element action decided by a fixed element — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X30 Support guard that admits what it rejects — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X32 Type resolved by simple name across every loaded assembly — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

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

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

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.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • 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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
  • D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
  • 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").
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (3): D19, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity7.3 / 10Strong✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

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

31 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was FixAvroCoder.fix at 29. A further 9 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 ConverterProvider.toAvroInternal at 22 — 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: scalafix/rules/src/main/scala/fix/v0_7_0/RewriteSysProp.scala (RewriteSysProp.fix at 20), scalafix/rules/src/main/scala/fix/v0_7_0/BQClientRefactoring.scala (BQClientRefactoring.fix at 19), scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/SchemaProvider.scala (SchemaProvider.rawType at 19), scio-extra/src/main/scala/com/spotify/scio/extra/bigquery/ToTableRow.scala (ToTableRow.toTableRowField at 18), scio-core/src/main/scala/com/spotify/scio/coders/CoderMaterializer.scala (CoderMaterializer.beamImpl at 17), 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.

FixAvroCoder.fix (cyclomatic 29)scalafix/rules/src/main/scala/fix/v0_14_0/FixAvroCoder.scala:191
MultiJoin.apply (cyclomatic 23)scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1258
MultiJoin.left (cyclomatic 23)scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2035
MultiJoin.outer (cyclomatic 23)scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2812
TypeProvider.schemaToType (cyclomatic 23)scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/TypeProvider.scala:254

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

What to do

  1. Resolve the 1 FixAvroCoder.fix (cyclomatic 29) finding(s) in Cyclomatic Complexity — start with FixAvroCoder.scala. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 MultiJoin.apply (cyclomatic 23) finding(s) in Cyclomatic Complexity — start with MultiJoin.scala. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 MultiJoin.left (cyclomatic 23) finding(s) in Cyclomatic Complexity — start with MultiJoin.scala. — One of this dimension's main actionable groups (1 warning-level).
  4. Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D2 · Cognitive Complexity5.0 / 10Adequate✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

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

60 method(s) exceeded the cognitive complexity threshold of 15; the worst was MultiJoin.apply at 253.

MultiJoin.apply (cognitive 253)scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1258
MultiJoin.left (cognitive 253)scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2035
MultiJoin.outer (cognitive 253)scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2812
MultiJoin.apply (cognitive 231)scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1203
MultiJoin.left (cognitive 231)scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1980

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

What to do

  1. Resolve the 1 MultiJoin.apply (cognitive 253) finding(s) in Cognitive Complexity — start with MultiJoin.scala. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 MultiJoin.left (cognitive 253) finding(s) in Cognitive Complexity — start with MultiJoin.scala. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 MultiJoin.outer (cognitive 253) finding(s) in Cognitive Complexity — start with MultiJoin.scala. — One of this dimension's main actionable groups (1 warning-level).
  4. Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D3 · God Classes9.1 / 10Stronggated by 24 serious findings✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

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

24 god class(es) detected.

TooManyMethods: SCollection · ×10scio-core/src/main/scala/com/spotify/scio/values/SCollection.scala:121
FileTooLong: util/MultiJoin.scala · ×8scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala
ClassTooLong: SortedBucketSink · ×6scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/SortedBucketSink.java:124

What to do

  1. Resolve the 10 TooManyMethods finding(s) in God Classes — start with FixPubsubSpecializations.scala (2), SCollection.scala, MultiJoin.scala. — One of this dimension's main actionable groups (10 warning-level).
  2. Resolve the 8 FileTooLong finding(s) in God Classes — start with MultiJoin.scala, SMBMultiJoin.scala, BigQueryIO.scala. — One of this dimension's main actionable groups (8 warning-level).
  3. Resolve the 6 ClassTooLong finding(s) in God Classes — start with SortedBucketSink.java, ElasticsearchIO.java, SortMergeBucketScioContextSyntax.scala. — One of this dimension's main actionable groups (6 warning-level).
  4. Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D4 · Code Duplication9.5 / 10Stronggated by 96 serious findings✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

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

87 duplicated block group(s) detected. A further 9 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 11 of the 96 are in trees this repository does not ship — vendored, example/demo, 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. Measured on part of this repository only: .java (28% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.

Duplicated block (7 lines × 2) · ×7scio-core/src/main/scala/com/spotify/scio/values/PairHashSCollectionFunctions.scala:145
Duplicated block (10 lines × 2) · ×6scio-core/src/main/scala/com/spotify/scio/util/FunctionsWithWindowedValue.scala:47
Duplicated block (5 lines × 3) · ×6scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:814
Duplicated block (4–5 lines × 4) · ×5scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:163
Members sharing a duplicated core (4 members, 50+ identical tokens) · ×4scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:48

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

What to do

  1. Resolve the 7 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with SMBMultiJoin.scala (2), MultiJoin.scala (2), PairHashSCollectionFunctions.scala. — One of this dimension's main actionable groups (7 warning-level).
  2. Resolve the 6 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with SortMergeBucketScioContextSyntax.scala (2), FunctionsWithWindowedValue.scala, PairHashSCollectionFunctions.scala. — One of this dimension's main actionable groups (6 warning-level).
  3. Resolve the 6 Duplicated block (5 lines × 3) finding(s) in Code Duplication — start with MultiJoin.scala (5), MagnolifyAvroExample.scala. — One of this dimension's main actionable groups (6 warning-level).
  4. Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D6 · Cohesion (LCOM4)9.8 / 10Stronggated by 2 serious findings✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

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

2 of 124 classes have LCOM4 above 3.

Low cohesion: ScioResult (LCOM4 5) · ×2scio-core/src/main/scala/com/spotify/scio/ScioResult.scala:44

What to do

  1. Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with ScioResult.scala, SCollectionWithFanout.scala. — One of this dimension's main actionable groups (2 warning-level).
  2. Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

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

192 test methods: 192 unit, 0 integration, 0 BDD, 0 e2e.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D16 · Bus Factor9.8 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

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

9 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/SortedBucketSink.java. Counted over 386 of the 771 production source files in this repository: 353 are under the ~2,400-byte size floor this dimension measures over, and the remaining 32 have no attributable history left to measure.

Off-boarding risk: anonymized user #1 · ×2
Further sole-owners (lower concentration)

✓ On the Gold path — maintain.

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

D17 · Explicit Debt9.9 / 10Stronggated by 58 serious findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

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

58 deducted task-comment markers across 84505 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.

TodoComment · ×40integration/src/test/scala/com/spotify/scio/bigquery/TypedBigQueryIT.scala:281
FixmeComment · ×14scio-avro/src/test/scala/com/spotify/scio/avro/types/ConverterProviderSpec.scala:122
XxxComment · ×4integration/src/test/scala/com/spotify/scio/testing/util/ItUtils.scala:35

What to do

  1. Resolve the 40 TodoComment finding(s) in Explicit Debt — start with RandomSampler.scala (4), SCollection.scala (4), AvroIOTest.scala (3). — One of this dimension's main actionable groups (40 warning-level).
  2. Resolve the 14 FixmeComment finding(s) in Explicit Debt — start with SCollectionMatchersTest.scala (4), ConverterProviderSpec.scala, ScioContext.scala. — One of this dimension's main actionable groups (14 warning-level).
  3. Resolve the 4 XxxComment finding(s) in Explicit Debt — start with SchemaMaterializer.scala (2), ItUtils.scala, AvroCoders.scala. — One of this dimension's main actionable groups (4 warning-level).
  4. Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D19 · Documentation QualityStrong◐ Sampled · advisory

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

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

Scio's root README gives a strong overview (Apache Beam/Dataflow-inspired Scala API with Ecclesiastical Latin IPA verb and the four stars), lists features, and shows CI/codecov badges plus links to Maven Central, Scaladoc, and Scala Steward. It also documents several subdirectories: scalafix/readme.md (Scalafix rules for scio), scio-jmh/README.md (JMH benchmarks getting started), scio-examples directories with complete and cookbook examples each showing how to run pipelines via sbt commands, and ends the root README with an outline that all sections exist. The visible content is clear and comprehensive; the unshown features and architecture docs are flagged as present in the outline.

What to do

  1. Improve Documentation Quality — currently 7.0/10. — Scio's root README gives a strong overview (Apache Beam/Dataflow-inspired Scala API with Ecclesiastical Latin IPA verb and the four stars), lists features, and shows CI/codecov badges plus links to Maven Central, Scaladoc, and Scala Steward. It also documents several subdirectories: scalafix/readme.md (Scalafix rules for scio), scio-jmh/README.md (JMH benchmarks getting started), scio-examples directories with complete and cookbook examples each showing how to run pipelines via sbt commands, and ends the root README with an outline that all sections exist. The visible content is clear and comprehensive; the unshown features and architecture docs are flagged as present in the outline.

Detailed fixes: d19_recommendation.md.

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

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

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

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

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)0.9 / 10Critical✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

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

69 finding(s): 0 critical, 69 high, 0 medium, 0 low. 55 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 3 file(s) — `integration/src/main/resources/shakespeare-sample-10.json`, `scio-core/src/main/scala-2.12/com/spotify/scio/coders/instances/TupleCoders.scala`, `scio-core/src/main/scala-2.13/com/spotify/scio/coders/instances/TupleCoders.scala` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (10 issue-level).
  2. Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
  3. No action in Static Analysis (SAST) — all 55 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 (55 issue-level, 0 of them charged here).

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

D31 · IaC & Container Security10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (Dockerfile/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

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

trivy and checkov found no infrastructure-as-code or container misconfigurations.

✓ On the Gold path — maintain.

Detailed fixes: d31_recommendation.md.

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D36 · Supply-chain Provenance & Signing5.0 / 10Adequate✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

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

2/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).

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

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

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

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

What to do

  • The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
M1 · Documentation (README)7.2 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

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

  • 20 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.

What to do

  • Add a 'Testing' section to the root README — how to run the test suite.
  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
  • Review the README against recent changes; refresh the parts that drifted.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

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

M4 · Documentation accuracy10.0 / 10Exemplary◐ Sampled · advisory

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

P3 · Security & performance tooling8.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

What to do

  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health86%StrongSolid.
Architecture99%ExemplaryStrongest area.
Maturity60%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness86%ExemplarySolid.
Security72%Adequate — gated by D29Capped at Fair by a Critical contributor — resolve it before relying on this lens.
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.

  • P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
Not evidenced — 4 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: these audit 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 audit 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.
  • C4 Data Retention — Not assessed: these retention 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 retention 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.
  • C5 Data-Subject Rights — Not assessed: these data-subject rights 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 data-subject rights 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.
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 83 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.
  • AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — no DI registrations detected
  • AX2 Stateful singletons — no singleton implementations detected
  • AX3 Project dependency cycles — not assessed — project cycles and dependency direction are computed over a project-reference graph that was not loaded for this repository, because the repository commits no project file of a kind this check models. This is a gap in the analyzer, not a finding about this repository
  • AX4 Dependency direction — not assessed — project cycles and dependency direction are computed over a project-reference graph that was not loaded for this repository, because the repository commits no project file of a kind this check models. This is a gap in the analyzer, not a finding about this repository
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX6 Interface segregation — not assessed — interface segregation is computed over a type surface 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
  • AX8 Test isolation — not assessed — test isolation is computed from a project graph (which projects are test projects, and what they reference) that was not loaded for this repository, because the repository commits no project file of a kind this check models. This is a gap in the analyzer, not a finding about this repository
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • 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 — ~43477 lines of test source are present (.java, .scala) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
  • D11 Test Reliability — Test reliability not included — the .scala suite was found but not re-run
  • D12 Dependency Hygiene — Dependency Hygiene not included (check did not complete)
  • D14 License Compliance — Package manifest not parsed for licence data — analyzer language-coverage gap
  • 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.
  • D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D23 Boundary Type-Coupling — Production source is present (.java, .py, .scala) but bounded contexts are resolved over the C#/VB project set, which exposed none, so context scope could not be assessed. Not scored — this is a gap in the analyzer, not a verdict about this repository. Declaring the codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed — see the recommendation on this dimension for where. 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 — No inline comments to assess — comment value is not applicable here.
  • D25 ADR Conformance — no ADRs to check
  • D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
  • D27 Navigability — symbol resolution incomplete — navigability not assessed
  • D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (an sbt build (build.sbt) — not scanned yet).
  • 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.
  • D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
  • D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (an sbt build (build.sbt) — not scanned yet).
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • D5 Coupling — Inter-project coupling could not be assessed — no analyzable project graph was found for this repository. Not scored: a gap in the analyzer's reach, not a verdict about this repository. (Coupling here is Martin afferent/efferent/instability plus reference cycles across a project-reference graph, read today from .NET project files; other ecosystems' module graphs are not read yet.)
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not included — suite not readable by the collector
  • DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 447 value object(s); 1 domain event(s)
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — This check finds retry-prone mutations (command handlers and message/event consumers) by walking the repository's declared types, and none was loaded here, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C# syntax, and none was loaded for this repository. That is a limit of the analyzer, not a finding about your code.
  • IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • P2 Observability — Observability was not assessed: this check reads a source model that does not carry this repository's product — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of a logging idiom this check recognises is NOT evidence that this repo lacks structured logging (it may log through its own ecosystem's logger). This is a gap in the analyzer, not a finding about this repository.
  • P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
  • P8 Schema migrations — not assessed — schema-migration practice is read from a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • PF1 Benchmark discipline — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
  • PF2 Allocation hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
  • PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
  • S1 Web-Security Posture — Not assessed: these web-security 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 web-security 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.
  • X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X20 Mistyped argument guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X23 Unguarded diagnostic materialisation — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X27 Collection changed while being enumerated — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X28 Index access outside its own emptiness guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 69 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 30 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 276 finding(s)
D17 · Explicit Debt · TodoComment · ×40
  • TodoComment integration/src/test/scala/com/spotify/scio/bigquery/TypedBigQueryIT.scala:281 — // Todo remove special casing when fixed — 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 integration/src/test/scala/com/spotify/scio/bigquery/TypedBigQueryIT.scala:340 — // Todo remove assertThrows after fixing in Beam — 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 integration/src/test/scala/com/spotify/scio/cassandra/CassandraIT.scala:40 — // TODO: figure out why inet/InetAddress doesn't work — 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 scio-avro/src/main/scala/com/spotify/scio/avro/AvroDatumFactory.scala:78 — // TODO move this to companion object — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment scio-avro/src/main/scala/com/spotify/scio/avro/schemas/instances/AvroInstances.scala:34 — // TODO: broken because of a bug upstream https://issues.apache.org/jira/browse/BEAM-6742
  • TodoComment scio-avro/src/main/scala/com/spotify/scio/avro/types/TypeProvider.scala:423 — // TODO: add this as key/value settings with default etc — 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 scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/TypeProvider.scala:517 — // TODO: add this as key/value settings with default etc — 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 scio-avro/src/test/scala/com/spotify/scio/avro/AvroIOTest.scala:52 — // TODO there is an exception with auto-sharding that fails for unbounded streams due to a GBK so numShards must be specified — 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 scio-avro/src/test/scala/com/spotify/scio/avro/AvroIOTest.scala:82 — // TODO there is an exception with auto-sharding that fails for unbounded streams due to a GBK so numShards must be specified — 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 scio-avro/src/test/scala/com/spotify/scio/avro/AvroIOTest.scala:110 — // TODO there is an exception with auto-sharding that fails for unbounded streams due to a GBK so numShards must be specified — 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 scio-core/src/test/scala/com/spotify/scio/io/ScioIOTest.scala:183 — // TODO there is an exception with auto-sharding that fails for unbounded streams due to a GBK so numShards must be specified — 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 scio-core/src/test/scala/com/spotify/scio/io/ScioIOTest.scala:212 — // TODO there is an exception with auto-sharding that fails for unbounded streams due to a GBK so numShards must be specified — 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 scio-parquet/src/test/scala/com/spotify/scio/parquet/avro/ParquetAvroIOTest.scala:66 — // TODO there is an exception with auto-sharding that fails for unbounded streams due to a GBK so numShards must be specified — 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 scio-parquet/src/test/scala/com/spotify/scio/parquet/tensorflow/ParquetExampleIOTest.scala:159 — // TODO there is an exception with auto-sharding that fails for unbounded streams due to a GBK so numShards must be specified — 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 scio-parquet/src/test/scala/com/spotify/scio/parquet/types/ParquetTypeIOTest.scala:47 — // TODO there is an exception with auto-sharding that fails for unbounded streams due to a GBK so numShards must be specified — 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 scio-tensorflow/src/test/scala/com/spotify/scio/tensorflow/TFExampleIOTest.scala:63 — // TODO there is an exception with auto-sharding that fails for unbounded streams due to a GBK so numShards must be specified — 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 scio-core/src/main/scala/com/spotify/scio/ScioContext.scala:471 — // Todo replace with getReadChannelOptions when GoogleCloudDataproc/hadoop-connectors#1294 is released
  • TodoComment scio-core/src/main/scala/com/spotify/scio/io/ScioIO.scala:177 — // TODO: add possibility to fill this for testing — 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 scio-core/src/main/scala/com/spotify/scio/schemas/Schema.scala:189 — // TODO: polymorphism ? — 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 scio-core/src/main/scala/com/spotify/scio/schemas/instances/ScalaInstances.scala:102 — // TODO: WrappedArray ? — 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 scio-core/src/main/scala/com/spotify/scio/util/random/RandomSampler.scala:45 — // TODO: is it necessary to setSeed for each instance like Spark does? — 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 scio-core/src/main/scala/com/spotify/scio/util/random/RandomSampler.scala:151 — // TODO: is it necessary to setSeed for each instance like Spark does? — 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 scio-core/src/main/scala/com/spotify/scio/util/random/RandomSampler.scala:185 — // TODO: is it necessary to setSeed for each instance like Spark does? — 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 scio-core/src/main/scala/com/spotify/scio/util/random/RandomSampler.scala:213 — // TODO: is it necessary to setSeed for each instance like Spark does? — 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 scio-core/src/main/scala/com/spotify/scio/values/SCollection.scala:927 — // TODO move to implicit — 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.
  • + 15 more in this group — see findings.md.
D17 · Explicit Debt · FixmeComment · ×14
  • FixmeComment scio-avro/src/test/scala/com/spotify/scio/avro/types/ConverterProviderSpec.scala:122 — // FIXME: can't derive Eq for this — 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 scio-core/src/main/scala/com/spotify/scio/ScioContext.scala:89 — // FIXME: this is ugly, is there a better way? — 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 scio-core/src/main/scala/com/spotify/scio/coders/KryoAtomicCoder.scala:187 — // FIXME: handle ElementByteSizeObservableIterable[_, _] — 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 scio-core/src/main/scala/com/spotify/scio/util/ScioUtil.scala:55 — // FIXME: cover Flink, Spark, etc. in local mode — 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 scio-core/src/test/scala/com/spotify/scio/coders/CoderTest.scala:489 — // FIXME: TableRowJsonCoder cannot be tested in scio-test because of circular dependency on scio-google-cloud-platform — 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 scio-core/src/test/scala/com/spotify/scio/transforms/PipeDoFnTest.scala:137 — // FIXME: this test is flaky because teardown is called asynchronously — 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 scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/StorageUtil.scala:101 — // FIXME: schema.getLogicalType == null in this case, BigQuery service side bug? — 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 scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/ParquetBucketMetadata.java:216 — // FIXME: what about `Option[T]` — 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 scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/KeyGroupIterator.java:31 — // FIXME: current limitation: must exhaust Iterator<ValueT> before starting the next key group — 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 scio-tensorflow/src/main/java/org/apache/beam/sdk/io/TFRecordFileBasedSink.java:49 — // FIXME why! make! things! private? — 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 scio-test/core/src/test/scala/com/spotify/scio/testing/SCollectionMatchersTest.scala:336 — // FIXME: these will fail if TR in predicate is pulled in via closure, not sure if fixable — 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 scio-test/core/src/test/scala/com/spotify/scio/testing/SCollectionMatchersTest.scala:389 — // FIXME: these will fail if TR in predicate is pulled in via closure, not sure if fixable — 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 scio-test/core/src/test/scala/com/spotify/scio/testing/SCollectionMatchersTest.scala:443 — // FIXME: these will fail if TR in predicate is pulled in via closure, not sure if fixable — 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 scio-test/core/src/test/scala/com/spotify/scio/testing/SCollectionMatchersTest.scala:518 — // FIXME: these will fail if TR in predicate is pulled in via closure, not sure if fixable — 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.
D3 · God Classes · TooManyMethods · ×10
  • TooManyMethods: SCollection scio-core/src/main/scala/com/spotify/scio/values/SCollection.scala:121 — TooManyMethods — 123 methods. The bar is 30 methods; this is 93 over it, 4.10× 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: MultiJoin scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:28 — TooManyMethods — 86 methods. The bar is 30 methods; this is 56 over it, 2.87× 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: SMBMultiJoin scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:31 — TooManyMethods — 85 methods. The bar is 30 methods; this is 55 over it, 2.83× 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: PairSCollectionFunctions scio-core/src/main/scala/com/spotify/scio/values/PairSCollectionFunctions.scala:58 — TooManyMethods — 69 methods. The bar is 30 methods; this is 39 over it, 2.30× 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: TableRowOps scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/syntax/TableRowSyntax.scala:168 — TooManyMethods — 51 methods. The bar is 30 methods; this is 21 over it, 1.70× 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: BucketMetadata scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/BucketMetadata.java:82 — TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× 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: FixPubsubSpecializations scalafix/input-0_12/src/main/scala/fix/v0_12_0/FixPubsubSpecializations.scala:11 — TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× 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: FixPubsubSpecializations scalafix/output-0_12/src/main/scala/fix/v0_12_0/FixPubsubSpecializations.scala:8 — TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× 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: ScioContext scio-core/src/main/scala/com/spotify/scio/ScioContext.scala:432 — TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× 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: SortedBucketScioContext scio-smb/src/main/scala/com/spotify/scio/smb/syntax/SortMergeBucketScioContextSyntax.scala:40 — 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.
D3 · God Classes · FileTooLong · ×8
  • FileTooLong: util/MultiJoin.scala scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala — FileTooLong — 2595 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2095 over it, 5.19× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: util/SMBMultiJoin.scala scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala — FileTooLong — 1685 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: SMBMultiJoin (31-2084). The bar is 500 significant lines; this is 1185 over it, 3.37× 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: bigquery/BigQueryIO.scala scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/BigQueryIO.scala — FileTooLong — 756 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 256 over it, 1.51× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: values/SCollection.scala scio-core/src/main/scala/com/spotify/scio/values/SCollection.scala — FileTooLong — 659 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 159 over it, 1.32× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: smb/SortedBucketSink.java scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/SortedBucketSink.java — FileTooLong — 640 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: SortedBucketSink (124-894). The bar is 500 significant lines; this is 140 over it, 1.28× 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: elasticsearch/ElasticsearchIO.java scio-elasticsearch/common/src/main/java/org/apache/beam/sdk/io/elasticsearch/ElasticsearchIO.java — FileTooLong — 569 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: ElasticsearchIO (74-808). The bar is 500 significant lines; this is 69 over it, 1.14× 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: scio/ScioContext.scala scio-core/src/main/scala/com/spotify/scio/ScioContext.scala — FileTooLong — 562 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 62 over it, 1.12× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: syntax/SortMergeBucketScioContextSyntax.scala scio-smb/src/main/scala/com/spotify/scio/smb/syntax/SortMergeBucketScioContextSyntax.scala — FileTooLong — 504 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: SortedBucketScioContext (40-756). The bar is 500 significant lines; this is 4 over it, 1.01× 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 · Duplicated block (7 lines × 2) · ×7
  • Duplicated block (7 lines × 2) scio-core/src/main/scala/com/spotify/scio/values/PairHashSCollectionFunctions.scala:145 — scio-core/src/main/scala/com/spotify/scio/values/PairHashSCollectionFunctions.scala:145-151 | scio-extra/src/main/scala/com/spotify/scio/extra/sparkey/PairLargeHashSCollectionFunctions.scala:169-175 — before extracting anything, compare `scio-core/src/main/scala/com/spotify/scio/values/PairHashSCollectionFunctions.scala` and `scio-extra/src/main/scala/com/spotify/scio/extra/sparkey/PairLargeHashSCollectionFunctions.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 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 `scio-core/src/main/scala/com/spotify/scio/values/PairHashSCollectionFunctions.scala:145` 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) scio-smb/src/main/scala/com/spotify/scio/smb/syntax/SortMergeBucketScioContextSyntax.scala:77 — scio-smb/src/main/scala/com/spotify/scio/smb/syntax/SortMergeBucketScioContextSyntax.scala:77-83 | scio-smb/src/main/scala/com/spotify/scio/smb/syntax/SortMergeBucketScioContextSyntax.scala:124-130 — 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 `scio-smb/src/main/scala/com/spotify/scio/smb/syntax/SortMergeBucketScioContextSyntax.scala:77` 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) scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:468 — scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:468-474 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1474-1480 — 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 `scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:468` 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 (7 lines × 2) scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:816 — scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:816-822 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1792-1798 — 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 `scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:816` 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 (7 lines × 2) scio-avro/src/main/scala/com/spotify/scio/avro/types/TypeProvider.scala:456 — scio-avro/src/main/scala/com/spotify/scio/avro/types/TypeProvider.scala:456-462 | scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/TypeProvider.scala:557-563 — 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 (7 lines × 2) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1556 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1556-1562 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2333-2339 — 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 `scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1556` 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) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1802 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1802-1808 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2579-2585 — 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 `scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1802` 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.
D3 · God Classes · ClassTooLong · ×6
  • ClassTooLong: SortedBucketSink scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/SortedBucketSink.java:124 — ClassTooLong — 578 significant lines (blank, comment-only and punctuation-only lines excluded), 5 methods. The bar is 400 significant lines; this is 178 over it, 1.45× 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: ElasticsearchIO scio-elasticsearch/common/src/main/java/org/apache/beam/sdk/io/elasticsearch/ElasticsearchIO.java:74 — ClassTooLong — 516 significant lines (blank, comment-only and punctuation-only lines excluded), 0 methods. The bar is 400 significant lines; this is 116 over it, 1.29× 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: SortedBucketScioContext scio-smb/src/main/scala/com/spotify/scio/smb/syntax/SortMergeBucketScioContextSyntax.scala:40 — ClassTooLong — 487 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 400 significant lines; this is 87 over it, 1.22× 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: SortedBucketIO scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/SortedBucketIO.java:63 — ClassTooLong — 434 significant lines (blank, comment-only and punctuation-only lines excluded), 3 methods. The bar is 400 significant lines; this is 34 over it, 1.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: SortedBucketTransform scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/SortedBucketTransform.java:77 — ClassTooLong — 418 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 18 over it, 1.05× 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: SortedBucketSource scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/SortedBucketSource.java:89 — ClassTooLong — 417 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 17 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.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×6
  • Duplicated block (10 lines × 2) scio-core/src/main/scala/com/spotify/scio/util/FunctionsWithWindowedValue.scala:47 — scio-core/src/main/scala/com/spotify/scio/util/FunctionsWithWindowedValue.scala:47-56 | scio-core/src/main/scala/com/spotify/scio/util/FunctionsWithWindowedValue.scala:67-76 — 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 `scio-core/src/main/scala/com/spotify/scio/util/FunctionsWithWindowedValue.scala:47` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) scio-core/src/main/scala/com/spotify/scio/values/PairHashSCollectionFunctions.scala:64 — scio-core/src/main/scala/com/spotify/scio/values/PairHashSCollectionFunctions.scala:64-73 | scio-extra/src/main/scala/com/spotify/scio/extra/sparkey/PairLargeHashSCollectionFunctions.scala:75-84 — before extracting anything, compare `scio-core/src/main/scala/com/spotify/scio/values/PairHashSCollectionFunctions.scala` and `scio-extra/src/main/scala/com/spotify/scio/extra/sparkey/PairLargeHashSCollectionFunctions.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 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 `scio-core/src/main/scala/com/spotify/scio/values/PairHashSCollectionFunctions.scala:64` 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 (10 lines × 2) scio-smb/src/main/scala/com/spotify/scio/smb/syntax/SortMergeBucketScioContextSyntax.scala:406 — scio-smb/src/main/scala/com/spotify/scio/smb/syntax/SortMergeBucketScioContextSyntax.scala:406-415 | scio-smb/src/main/scala/com/spotify/scio/smb/syntax/SortMergeBucketScioContextSyntax.scala:502-511 — 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 `scio-smb/src/main/scala/com/spotify/scio/smb/syntax/SortMergeBucketScioContextSyntax.scala:406` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) scio-smb/src/main/scala/com/spotify/scio/smb/syntax/SortMergeBucketScioContextSyntax.scala:637 — scio-smb/src/main/scala/com/spotify/scio/smb/syntax/SortMergeBucketScioContextSyntax.scala:637-646 | scio-smb/src/main/scala/com/spotify/scio/smb/syntax/SortMergeBucketScioContextSyntax.scala:713-722 — 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 `scio-smb/src/main/scala/com/spotify/scio/smb/syntax/SortMergeBucketScioContextSyntax.scala:637` 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 (10 lines × 2) scio-snowflake/src/main/scala/com/spotify/scio/snowflake/SnowflakeIO.scala:152 — scio-snowflake/src/main/scala/com/spotify/scio/snowflake/SnowflakeIO.scala:152-161 | scio-snowflake/src/main/scala/com/spotify/scio/snowflake/SnowflakeIO.scala:188-197 — 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 `scio-snowflake/src/main/scala/com/spotify/scio/snowflake/SnowflakeIO.scala:152` 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 (10 lines × 2) scio-examples/src/main/scala/com/spotify/scio/examples/complete/game/GameStats.scala:58 — scio-examples/src/main/scala/com/spotify/scio/examples/complete/game/GameStats.scala:58-67 | scio-examples/src/main/scala/com/spotify/scio/examples/complete/game/LeaderBoard.scala:61-70 — 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.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×6
  • Duplicated block (5 lines × 3) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:814 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:814-818 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1591-1595 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2368-2372 — 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 `scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:814` 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 × 3) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:852 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:852-856 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1629-1633 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2406-2410 — 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 `scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:852` 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 × 3) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1072 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1072-1076 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1849-1853 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2626-2630 — 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 `scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1072` 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 × 3) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1122 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1122-1126 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1899-1903 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2676-2680 — 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 `scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1122` 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 × 3) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1179 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1179-1183 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1234-1238 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1291-1295 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1233` calls `getAll` and `scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1178` 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 (5 lines × 3) scio-examples/src/main/scala/com/spotify/scio/examples/extra/MagnolifyAvroExample.scala:46 — scio-examples/src/main/scala/com/spotify/scio/examples/extra/MagnolifyAvroExample.scala:46-50 | scio-examples/src/main/scala/com/spotify/scio/examples/extra/MagnolifyDatastoreExample.scala:48-52 | scio-examples/src/main/scala/com/spotify/scio/examples/extra/MagnolifyTensorFlowExample.scala:53-57 — 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 all 3 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (4–5 lines × 4) · ×5
  • Duplicated block (4–5 lines × 4) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:163 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:163-166 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:712-716 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1489-1493 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2266-2270 — all 4 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 `scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:163` 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 (4–5 lines × 4) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:284 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:284-287 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:892-896 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1669-1673 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2446-2450 — all 4 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 `scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:284` 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 (4–5 lines × 4) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:310 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:310-313 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:934-938 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1711-1715 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2488-2492 — all 4 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 `scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:310` 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 (4–5 lines × 4) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:461 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:461-464 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1174-1178 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1951-1955 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2728-2732 — all 4 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 `scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:461` 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 (4–5 lines × 4) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:493 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:493-496 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1228-1232 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2005-2009 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2782-2786 — all 4 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 `scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:493` 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.
D17 · Explicit Debt · XxxComment · ×4
  • XxxComment integration/src/test/scala/com/spotify/scio/testing/util/ItUtils.scala:35 — // XXX: Copied from BigQueryClient — 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.
  • XxxComment scio-avro/src/main/scala/com/spotify/scio/coders/avro/AvroCoders.scala:133 — // XXX: similar to GenericAvroSerializer — 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.
  • XxxComment scio-core/src/main/scala/com/spotify/scio/schemas/SchemaMaterializer.scala:51 — // XXX: scalac can't unify schema.Repr with s.Repr — 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.
  • XxxComment scio-core/src/main/scala/com/spotify/scio/schemas/SchemaMaterializer.scala:110 — // XXX: scalac can't unify schema.Repr with s.Repr — 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.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×4
  • Members sharing a duplicated core (4 members, 50+ identical tokens) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:48 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:48-61 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:555-572 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1332-1349 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2109-2126 — 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.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:63 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:63-77 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:574-593 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1351-1370 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2128-2147 — 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.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala:64 — scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala:64-165 | scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala:167-285 | scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala:289-357 | scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala:361-459 — 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.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) scio-redis/src/main/scala/com/spotify/scio/redis/RedisMutator.scala:87 — scio-redis/src/main/scala/com/spotify/scio/redis/RedisMutator.scala:87-99 | scio-redis/src/main/scala/com/spotify/scio/redis/RedisMutator.scala:101-113 | scio-redis/src/main/scala/com/spotify/scio/redis/RedisMutator.scala:115-127 | scio-redis/src/main/scala/com/spotify/scio/redis/RedisMutator.scala:130-142 — 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 · Duplicated block (6 lines × 4) · ×4
  • Duplicated block (6 lines × 4) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:67 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:67-72 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:578-583 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1355-1360 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2132-2137 — all 4 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.
  • Duplicated block (6 lines × 4) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:184 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:184-189 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:740-745 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1517-1522 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2294-2299 — all 4 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 `scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:184` 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 × 4) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:337 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:337-342 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:974-979 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1751-1756 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2528-2533 — all 4 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 `scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:337` 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 × 4) scio-redis/src/main/scala/com/spotify/scio/redis/RedisMutator.scala:89 — scio-redis/src/main/scala/com/spotify/scio/redis/RedisMutator.scala:89-94 | scio-redis/src/main/scala/com/spotify/scio/redis/RedisMutator.scala:103-108 | scio-redis/src/main/scala/com/spotify/scio/redis/RedisMutator.scala:117-122 | scio-redis/src/main/scala/com/spotify/scio/redis/RedisMutator.scala:132-137 — all 4 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.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×4
  • Duplicated block (5 lines × 2) scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala:175 — scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala:175-179 | scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala:369-373 — 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 `scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala:175` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:900 — scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:900-904 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1926-1930 — 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 `scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:900` 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) scio-core/src/main/scala-2.12/com/spotify/scio/coders/instances/JavaCollectionWrappers.scala:39 — scio-core/src/main/scala-2.12/com/spotify/scio/coders/instances/JavaCollectionWrappers.scala:39-43 | scio-core/src/main/scala-2.13/com/spotify/scio/coders/instances/JavaCollectionWrappers.scala:39-43 — before extracting anything, compare `scio-core/src/main/scala-2.12/com/spotify/scio/coders/instances/JavaCollectionWrappers.scala` and `scio-core/src/main/scala-2.13/com/spotify/scio/coders/instances/JavaCollectionWrappers.scala` as WHOLE FILES: 85% 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 (5 lines × 2) scio-examples/src/main/scala/com/spotify/scio/examples/WordCount.scala:77 — scio-examples/src/main/scala/com/spotify/scio/examples/WordCount.scala:77-81 | scio-examples/src/main/scala/com/spotify/scio/examples/extra/WordCountScioIO.scala:79-83 — 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.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×3
  • Duplicated block (13 lines × 2) scio-grpc/src/main/scala/com/spotify/scio/grpc/SCollectionSyntax.scala:137 — scio-grpc/src/main/scala/com/spotify/scio/grpc/SCollectionSyntax.scala:137-149 | scio-grpc/src/main/scala/com/spotify/scio/grpc/SCollectionSyntax.scala:194-206 — 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 `scio-grpc/src/main/scala/com/spotify/scio/grpc/SCollectionSyntax.scala:137` 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 lines × 2) scio-parquet/src/main/scala/com/spotify/scio/parquet/tensorflow/ParquetExampleIO.scala:191 — scio-parquet/src/main/scala/com/spotify/scio/parquet/tensorflow/ParquetExampleIO.scala:191-203 | scio-parquet/src/main/scala/com/spotify/scio/parquet/types/ParquetTypeIO.scala:164-176 — 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 `scio-parquet/src/main/scala/com/spotify/scio/parquet/tensorflow/ParquetExampleIO.scala:191` 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 (13 lines × 2) scalafix/input-0_7/src/main/scala/fix/v0_7_0/FixAvroIO.scala:11 — scalafix/input-0_7/src/main/scala/fix/v0_7_0/FixAvroIO.scala:11-23 | scalafix/output-0_7/src/main/scala/fix/v0_7_0/FixAvroIO.scala:11-23 — 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 `scalafix/input-0_7/src/main/scala/fix/v0_7_0/FixAvroIO.scala:11` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×3
  • Duplicated block (11 lines × 2) scio-repl/src/main/scala-2.12/com/spotify/scio/repl/ScioGenericRunner.scala:39 — scio-repl/src/main/scala-2.12/com/spotify/scio/repl/ScioGenericRunner.scala:39-49 | scio-repl/src/main/scala-2.13/com/spotify/scio/repl/ScioGenericRunner.scala:37-47 — before extracting anything, compare `scio-repl/src/main/scala-2.12/com/spotify/scio/repl/ScioGenericRunner.scala` and `scio-repl/src/main/scala-2.13/com/spotify/scio/repl/ScioGenericRunner.scala` as WHOLE FILES: 97% 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 (11 lines × 2) scalafix/rules/src/main/scala/fix/v0_14_0/FixAvroCoder.scala:78 — scalafix/rules/src/main/scala/fix/v0_14_0/FixAvroCoder.scala:78-88 | scalafix/rules/src/main/scala/fix/v0_14_0/FixAvroSchemasPackage.scala:48-58 — before extracting anything, compare `scalafix/rules/src/main/scala/fix/v0_14_0/FixAvroCoder.scala` and `scalafix/rules/src/main/scala/fix/v0_14_0/FixAvroSchemasPackage.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 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. 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 (11 lines × 2) scio-examples/src/main/scala/com/spotify/scio/examples/complete/TrafficMaxLaneFlow.scala:70 — scio-examples/src/main/scala/com/spotify/scio/examples/complete/TrafficMaxLaneFlow.scala:70-80 | scio-examples/src/main/scala/com/spotify/scio/examples/complete/TrafficRoutes.scala:57-67 — 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 `scio-examples/src/main/scala/com/spotify/scio/examples/complete/TrafficMaxLaneFlow.scala:70` 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 before the matched lines, `scio-examples/src/main/scala/com/spotify/scio/examples/complete/TrafficMaxLaneFlow.scala:67` calls `setup` and `scio-examples/src/main/scala/com/spotify/scio/examples/complete/TrafficRoutes.scala:54` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (5 members, 50+ identical tokens) scio-core/src/main/scala/com/spotify/scio/util/ArtisanJoin.scala:48 — scio-core/src/main/scala/com/spotify/scio/util/ArtisanJoin.scala:48-94 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:34-46 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:538-553 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1315-1330 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2092-2107 — These 5 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 5 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 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) scio-examples/src/main/scala/com/spotify/scio/examples/cookbook/BigQueryTornadoes.scala:35 — scio-examples/src/main/scala/com/spotify/scio/examples/cookbook/BigQueryTornadoes.scala:35-74 | scio-examples/src/main/scala/com/spotify/scio/examples/cookbook/CombinePerKeyExamples.scala:35-72 | scio-examples/src/main/scala/com/spotify/scio/examples/cookbook/DistinctByKeyExample.scala:34-67 | scio-examples/src/main/scala/com/spotify/scio/examples/cookbook/MaxPerKeyExamples.scala:34-62 | scio-examples/src/main/scala/com/spotify/scio/examples/cookbook/StorageBigQueryTornadoes.scala:35-84 — These 5 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 5 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 5 times.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×2
  • Duplicated block (12 lines × 2) scio-smb/src/main/scala/com/spotify/scio/smb/syntax/SortMergeBucketScioContextSyntax.scala:700 — scio-smb/src/main/scala/com/spotify/scio/smb/syntax/SortMergeBucketScioContextSyntax.scala:700-711 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1129-1140 — 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 `scio-smb/src/main/scala/com/spotify/scio/smb/syntax/SortMergeBucketScioContextSyntax.scala:700` 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 (12 lines × 2) scalafix/rules/src/main/scala/fix/v0_14_0/FixAvroCoder.scala:53 — scalafix/rules/src/main/scala/fix/v0_14_0/FixAvroCoder.scala:53-64 | scalafix/rules/src/main/scala/fix/v0_14_0/FixAvroSchemasPackage.scala:23-34 — before extracting anything, compare `scalafix/rules/src/main/scala/fix/v0_14_0/FixAvroCoder.scala` and `scalafix/rules/src/main/scala/fix/v0_14_0/FixAvroSchemasPackage.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 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. 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 · Duplicated block (9 lines × 2) · ×2
  • Duplicated block (9 lines × 2) scio-core/src/main/scala/com/spotify/scio/coders/BeamCoders.scala:84 — scio-core/src/main/scala/com/spotify/scio/coders/BeamCoders.scala:84-92 | scio-core/src/main/scala/com/spotify/scio/coders/BeamCoders.scala:109-117 — 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 `scio-core/src/main/scala/com/spotify/scio/coders/BeamCoders.scala:84` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) scio-parquet/src/main/scala/com/spotify/scio/parquet/tensorflow/ParquetExampleIO.scala:55 — scio-parquet/src/main/scala/com/spotify/scio/parquet/tensorflow/ParquetExampleIO.scala:55-63 | scio-parquet/src/main/scala/com/spotify/scio/parquet/types/ParquetTypeIO.scala:56-64 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×2
  • Duplicated block (8 lines × 2) scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala:228 — scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala:228-235 | scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala:420-427 — 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 `scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala:228` 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) scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1087 — scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1087-1094 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:2043-2050 — 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 `scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1087` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×2
  • Duplicated block (7 lines × 4) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:83 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:83-89 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:599-605 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1376-1382 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2153-2159 — all 4 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.
  • Duplicated block (7 lines × 4) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:525 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:525-531 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1279-1285 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2056-2062 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2833-2839 — all 4 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 `scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:525` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×2
  • Duplicated block (6 lines × 2) scalafix/rules/src/main/scala/fix/v0_12_0/FixPubsubSpecializations.scala:173 — scalafix/rules/src/main/scala/fix/v0_12_0/FixPubsubSpecializations.scala:173-178 | scalafix/rules/src/main/scala/fix/v0_12_0/FixPubsubSpecializations.scala:180-185 — 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 `scalafix/rules/src/main/scala/fix/v0_12_0/FixPubsubSpecializations.scala:173` 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) scio-avro/src/main/scala/com/spotify/scio/avro/types/MacroUtil.scala:36 — scio-avro/src/main/scala/com/spotify/scio/avro/types/MacroUtil.scala:36-41 | scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/MacroUtil.scala:39-44 — 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.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×2
  • Duplicated block (21 lines × 2) scio-examples/src/main/scala/com/spotify/scio/examples/cookbook/CombinePerKeyExamples.scala:37 — scio-examples/src/main/scala/com/spotify/scio/examples/cookbook/CombinePerKeyExamples.scala:37-57 | scio-examples/src/main/scala/com/spotify/scio/examples/cookbook/DistinctByKeyExample.scala:36-56 — 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 (21 lines × 2) scio-examples/src/main/scala/com/spotify/scio/examples/extra/MagnolifyTypedStorageBigQueryTornadoes.scala:52 — scio-examples/src/main/scala/com/spotify/scio/examples/extra/MagnolifyTypedStorageBigQueryTornadoes.scala:52-72 | scio-examples/src/main/scala/com/spotify/scio/examples/extra/TypedStorageBigQueryTornadoes.scala:60-80 — 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 `scio-examples/src/main/scala/com/spotify/scio/examples/extra/MagnolifyTypedStorageBigQueryTornadoes.scala:52` 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×2
  • Low cohesion: ScioResult (LCOM4 5) scio-core/src/main/scala/com/spotify/scio/ScioResult.scala:44 — ScioResult'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.
  • Low cohesion: SCollectionWithFanout (LCOM4 4) scio-core/src/main/scala/com/spotify/scio/values/SCollectionWithFanout.scala:35 — SCollectionWithFanout's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
D1 · Cyclomatic Complexity · FixAvroCoder.fix (cyclomatic 29) · ×1
  • FixAvroCoder.fix (cyclomatic 29) scalafix/rules/src/main/scala/fix/v0_14_0/FixAvroCoder.scala:191 — FixAvroCoder.fix has cyclomatic complexity 29 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · MultiJoin.apply (cyclomatic 23) · ×1
  • MultiJoin.apply (cyclomatic 23) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1258 — MultiJoin.apply has cyclomatic complexity 23 (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. This shape REPEATS in the file: 2 other methods here (MultiJoin.left, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · MultiJoin.left (cyclomatic 23) · ×1
  • MultiJoin.left (cyclomatic 23) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2035 — MultiJoin.left has cyclomatic complexity 23 (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. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · MultiJoin.outer (cyclomatic 23) · ×1
  • MultiJoin.outer (cyclomatic 23) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2812 — MultiJoin.outer has cyclomatic complexity 23 (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. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.left) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · TypeProvider.schemaToType (cyclomatic 23) · ×1
  • TypeProvider.schemaToType (cyclomatic 23) scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/TypeProvider.scala:254 — TypeProvider.schemaToType 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.
D1 · Cyclomatic Complexity · MultiJoin.apply (cyclomatic 22) · ×1
  • MultiJoin.apply (cyclomatic 22) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1203 — MultiJoin.apply has cyclomatic complexity 22 (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. This shape REPEATS in the file: 2 other methods here (MultiJoin.left, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · MultiJoin.left (cyclomatic 22) · ×1
  • MultiJoin.left (cyclomatic 22) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1980 — MultiJoin.left has cyclomatic complexity 22 (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. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · MultiJoin.outer (cyclomatic 22) · ×1
  • MultiJoin.outer (cyclomatic 22) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2757 — MultiJoin.outer has cyclomatic complexity 22 (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. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.left) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · ConverterProvider.fromAvroInternal (cyclomatic 22) · ×1
  • ConverterProvider.fromAvroInternal (cyclomatic 22) scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala:64 — ConverterProvider.fromAvroInternal 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.
D1 · Cyclomatic Complexity · MultiJoin.apply (cyclomatic 21) · ×1
  • MultiJoin.apply (cyclomatic 21) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1150 — MultiJoin.apply has cyclomatic complexity 21 (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. This shape REPEATS in the file: 2 other methods here (MultiJoin.left, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · MultiJoin.left (cyclomatic 21) · ×1
  • MultiJoin.left (cyclomatic 21) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1927 — MultiJoin.left has cyclomatic complexity 21 (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. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · MultiJoin.outer (cyclomatic 21) · ×1
  • MultiJoin.outer (cyclomatic 21) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2704 — MultiJoin.outer has cyclomatic complexity 21 (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. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.left) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · SoccoPhase.typeTokens (cyclomatic 21) · ×1
  • SoccoPhase.typeTokens (cyclomatic 21) socco-plugin/src/main/scala/Socco.scala:224 — SoccoPhase.typeTokens has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · MultiSourceKeyGroupReader.advance (cyclomatic 21) · ×1
  • MultiSourceKeyGroupReader.advance (cyclomatic 21) scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java:113 — MultiSourceKeyGroupReader.advance has cyclomatic complexity 21 (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.
D1 · Cyclomatic Complexity · MultiJoin.apply (cyclomatic 20) · ×1
  • MultiJoin.apply (cyclomatic 20) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1099 — MultiJoin.apply has cyclomatic complexity 20 (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. This shape REPEATS in the file: 2 other methods here (MultiJoin.left, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · MultiJoin.left (cyclomatic 20) · ×1
  • MultiJoin.left (cyclomatic 20) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1876 — MultiJoin.left has cyclomatic complexity 20 (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. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · MultiJoin.outer (cyclomatic 20) · ×1
  • MultiJoin.outer (cyclomatic 20) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2653 — MultiJoin.outer has cyclomatic complexity 20 (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. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.left) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · TypeProvider.schemaToType (cyclomatic 19) · ×1
  • TypeProvider.schemaToType (cyclomatic 19) scio-avro/src/main/scala/com/spotify/scio/avro/types/TypeProvider.scala:198 — TypeProvider.schemaToType 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.
D1 · Cyclomatic Complexity · MultiJoin.apply (cyclomatic 19) · ×1
  • MultiJoin.apply (cyclomatic 19) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1050 — MultiJoin.apply has cyclomatic complexity 19 (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. This shape REPEATS in the file: 2 other methods here (MultiJoin.left, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · MultiJoin.left (cyclomatic 19) · ×1
  • MultiJoin.left (cyclomatic 19) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1827 — MultiJoin.left has cyclomatic complexity 19 (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. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · MultiJoin.outer (cyclomatic 19) · ×1
  • MultiJoin.outer (cyclomatic 19) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2604 — MultiJoin.outer has cyclomatic complexity 19 (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. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.left) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · StorageUtil.setRawType (cyclomatic 19) · ×1
  • StorageUtil.setRawType (cyclomatic 19) scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/StorageUtil.scala:66 — StorageUtil.setRawType 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.
D1 · Cyclomatic Complexity · MultiJoin.apply (cyclomatic 18) · ×1
  • MultiJoin.apply (cyclomatic 18) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1003 — MultiJoin.apply has cyclomatic complexity 18 (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. This shape REPEATS in the file: 2 other methods here (MultiJoin.left, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · MultiJoin.left (cyclomatic 18) · ×1
  • MultiJoin.left (cyclomatic 18) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1780 — MultiJoin.left has cyclomatic complexity 18 (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. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · MultiJoin.outer (cyclomatic 18) · ×1
  • MultiJoin.outer (cyclomatic 18) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2557 — MultiJoin.outer has cyclomatic complexity 18 (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. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.left) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · MultiJoin.apply (cyclomatic 17) · ×1
  • MultiJoin.apply (cyclomatic 17) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:958 — MultiJoin.apply has cyclomatic complexity 17 (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. This shape REPEATS in the file: 2 other methods here (MultiJoin.left, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · MultiJoin.left (cyclomatic 17) · ×1
  • MultiJoin.left (cyclomatic 17) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1735 — MultiJoin.left has cyclomatic complexity 17 (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. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · MultiJoin.outer (cyclomatic 17) · ×1
  • MultiJoin.outer (cyclomatic 17) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2512 — MultiJoin.outer has cyclomatic complexity 17 (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. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.left) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · MultiJoin.apply (cyclomatic 16) · ×1
  • MultiJoin.apply (cyclomatic 16) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:915 — MultiJoin.apply 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. This shape REPEATS in the file: 2 other methods here (MultiJoin.left, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · MultiJoin.left (cyclomatic 16) · ×1
  • MultiJoin.left (cyclomatic 16) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1692 — MultiJoin.left 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. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · MultiJoin.outer (cyclomatic 16) · ×1
  • MultiJoin.outer (cyclomatic 16) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2469 — MultiJoin.outer 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. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.left) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · MultiJoin.apply (cognitive 253) · ×1
  • MultiJoin.apply (cognitive 253) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1258 — MultiJoin.apply has cognitive complexity 253 (threshold 15). Drivers by points: loops 22 (253 pts) (nesting depth added 231). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.left, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.left (cognitive 253) · ×1
  • MultiJoin.left (cognitive 253) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2035 — MultiJoin.left has cognitive complexity 253 (threshold 15). Drivers by points: loops 22 (253 pts) (nesting depth added 231). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.outer (cognitive 253) · ×1
  • MultiJoin.outer (cognitive 253) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2812 — MultiJoin.outer has cognitive complexity 253 (threshold 15). Drivers by points: loops 22 (253 pts) (nesting depth added 231). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.left) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.apply (cognitive 231) · ×1
  • MultiJoin.apply (cognitive 231) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1203 — MultiJoin.apply has cognitive complexity 231 (threshold 15). Drivers by points: loops 21 (231 pts) (nesting depth added 210). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.left, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.left (cognitive 231) · ×1
  • MultiJoin.left (cognitive 231) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1980 — MultiJoin.left has cognitive complexity 231 (threshold 15). Drivers by points: loops 21 (231 pts) (nesting depth added 210). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.outer (cognitive 231) · ×1
  • MultiJoin.outer (cognitive 231) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2757 — MultiJoin.outer has cognitive complexity 231 (threshold 15). Drivers by points: loops 21 (231 pts) (nesting depth added 210). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.left) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.apply (cognitive 210) · ×1
  • MultiJoin.apply (cognitive 210) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1150 — MultiJoin.apply has cognitive complexity 210 (threshold 15). Drivers by points: loops 20 (210 pts) (nesting depth added 190). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.left, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.left (cognitive 210) · ×1
  • MultiJoin.left (cognitive 210) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1927 — MultiJoin.left has cognitive complexity 210 (threshold 15). Drivers by points: loops 20 (210 pts) (nesting depth added 190). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.outer (cognitive 210) · ×1
  • MultiJoin.outer (cognitive 210) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2704 — MultiJoin.outer has cognitive complexity 210 (threshold 15). Drivers by points: loops 20 (210 pts) (nesting depth added 190). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.left) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.apply (cognitive 190) · ×1
  • MultiJoin.apply (cognitive 190) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1099 — MultiJoin.apply has cognitive complexity 190 (threshold 15). Drivers by points: loops 19 (190 pts) (nesting depth added 171). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.left, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.left (cognitive 190) · ×1
  • MultiJoin.left (cognitive 190) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1876 — MultiJoin.left has cognitive complexity 190 (threshold 15). Drivers by points: loops 19 (190 pts) (nesting depth added 171). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.outer (cognitive 190) · ×1
  • MultiJoin.outer (cognitive 190) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2653 — MultiJoin.outer has cognitive complexity 190 (threshold 15). Drivers by points: loops 19 (190 pts) (nesting depth added 171). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.left) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.apply (cognitive 171) · ×1
  • MultiJoin.apply (cognitive 171) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1050 — MultiJoin.apply has cognitive complexity 171 (threshold 15). Drivers by points: loops 18 (171 pts) (nesting depth added 153). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.left, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.left (cognitive 171) · ×1
  • MultiJoin.left (cognitive 171) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1827 — MultiJoin.left has cognitive complexity 171 (threshold 15). Drivers by points: loops 18 (171 pts) (nesting depth added 153). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.outer (cognitive 171) · ×1
  • MultiJoin.outer (cognitive 171) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2604 — MultiJoin.outer has cognitive complexity 171 (threshold 15). Drivers by points: loops 18 (171 pts) (nesting depth added 153). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.left) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.apply (cognitive 153) · ×1
  • MultiJoin.apply (cognitive 153) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1003 — MultiJoin.apply has cognitive complexity 153 (threshold 15). Drivers by points: loops 17 (153 pts) (nesting depth added 136). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.left, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.left (cognitive 153) · ×1
  • MultiJoin.left (cognitive 153) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1780 — MultiJoin.left has cognitive complexity 153 (threshold 15). Drivers by points: loops 17 (153 pts) (nesting depth added 136). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.outer (cognitive 153) · ×1
  • MultiJoin.outer (cognitive 153) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2557 — MultiJoin.outer has cognitive complexity 153 (threshold 15). Drivers by points: loops 17 (153 pts) (nesting depth added 136). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.left) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.apply (cognitive 136) · ×1
  • MultiJoin.apply (cognitive 136) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:958 — MultiJoin.apply has cognitive complexity 136 (threshold 15). Drivers by points: loops 16 (136 pts) (nesting depth added 120). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.left, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.left (cognitive 136) · ×1
  • MultiJoin.left (cognitive 136) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1735 — MultiJoin.left has cognitive complexity 136 (threshold 15). Drivers by points: loops 16 (136 pts) (nesting depth added 120). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.outer (cognitive 136) · ×1
  • MultiJoin.outer (cognitive 136) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2512 — MultiJoin.outer has cognitive complexity 136 (threshold 15). Drivers by points: loops 16 (136 pts) (nesting depth added 120). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.left) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.apply (cognitive 120) · ×1
  • MultiJoin.apply (cognitive 120) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:915 — MultiJoin.apply has cognitive complexity 120 (threshold 15). Drivers by points: loops 15 (120 pts) (nesting depth added 105). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.left, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.left (cognitive 120) · ×1
  • MultiJoin.left (cognitive 120) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1692 — MultiJoin.left has cognitive complexity 120 (threshold 15). Drivers by points: loops 15 (120 pts) (nesting depth added 105). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.outer (cognitive 120) · ×1
  • MultiJoin.outer (cognitive 120) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2469 — MultiJoin.outer has cognitive complexity 120 (threshold 15). Drivers by points: loops 15 (120 pts) (nesting depth added 105). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.left) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.apply (cognitive 105) · ×1
  • MultiJoin.apply (cognitive 105) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:874 — MultiJoin.apply has cognitive complexity 105 (threshold 15). Drivers by points: loops 14 (105 pts) (nesting depth added 91). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.left, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.left (cognitive 105) · ×1
  • MultiJoin.left (cognitive 105) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1651 — MultiJoin.left has cognitive complexity 105 (threshold 15). Drivers by points: loops 14 (105 pts) (nesting depth added 91). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.outer (cognitive 105) · ×1
  • MultiJoin.outer (cognitive 105) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2428 — MultiJoin.outer has cognitive complexity 105 (threshold 15). Drivers by points: loops 14 (105 pts) (nesting depth added 91). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.left) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.apply (cognitive 91) · ×1
  • MultiJoin.apply (cognitive 91) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:835 — MultiJoin.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. This shape REPEATS in the file: 2 other methods here (MultiJoin.left, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.left (cognitive 91) · ×1
  • MultiJoin.left (cognitive 91) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1612 — MultiJoin.left 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. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.outer (cognitive 91) · ×1
  • MultiJoin.outer (cognitive 91) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2389 — MultiJoin.outer 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. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.left) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.apply (cognitive 78) · ×1
  • MultiJoin.apply (cognitive 78) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:798 — MultiJoin.apply has cognitive complexity 78 (threshold 15). Drivers by points: loops 12 (78 pts) (nesting depth added 66). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.left, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.left (cognitive 78) · ×1
  • MultiJoin.left (cognitive 78) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1575 — MultiJoin.left has cognitive complexity 78 (threshold 15). Drivers by points: loops 12 (78 pts) (nesting depth added 66). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.outer (cognitive 78) · ×1
  • MultiJoin.outer (cognitive 78) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2352 — MultiJoin.outer has cognitive complexity 78 (threshold 15). Drivers by points: loops 12 (78 pts) (nesting depth added 66). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.left) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.apply (cognitive 66) · ×1
  • MultiJoin.apply (cognitive 66) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:763 — MultiJoin.apply 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. This shape REPEATS in the file: 2 other methods here (MultiJoin.left, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.left (cognitive 66) · ×1
  • MultiJoin.left (cognitive 66) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1540 — MultiJoin.left 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. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.outer (cognitive 66) · ×1
  • MultiJoin.outer (cognitive 66) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2317 — MultiJoin.outer 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. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.left) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.apply (cognitive 55) · ×1
  • MultiJoin.apply (cognitive 55) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:730 — MultiJoin.apply has cognitive complexity 55 (threshold 15). Drivers by points: loops 10 (55 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. This shape REPEATS in the file: 2 other methods here (MultiJoin.left, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.left (cognitive 55) · ×1
  • MultiJoin.left (cognitive 55) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1507 — MultiJoin.left has cognitive complexity 55 (threshold 15). Drivers by points: loops 10 (55 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. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.outer (cognitive 55) · ×1
  • MultiJoin.outer (cognitive 55) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2284 — MultiJoin.outer has cognitive complexity 55 (threshold 15). Drivers by points: loops 10 (55 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. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.left) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiSourceKeyGroupReader.advance (cognitive 51) · ×1
  • MultiSourceKeyGroupReader.advance (cognitive 51) scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java:113 — MultiSourceKeyGroupReader.advance has cognitive complexity 51 (threshold 15). Drivers by points: if/else 12 (26 pts), ternaries 2 (12 pts), boolean chains 6, error handling 1 (4 pts), loops 2 (3 pts) (nesting depth added 28). 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.
D2 · Cognitive Complexity · MultiJoin.apply (cognitive 45) · ×1
  • MultiJoin.apply (cognitive 45) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:699 — MultiJoin.apply has cognitive complexity 45 (threshold 15). Drivers by points: loops 9 (45 pts) (nesting depth added 36). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.left, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.left (cognitive 45) · ×1
  • MultiJoin.left (cognitive 45) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1476 — MultiJoin.left has cognitive complexity 45 (threshold 15). Drivers by points: loops 9 (45 pts) (nesting depth added 36). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.outer (cognitive 45) · ×1
  • MultiJoin.outer (cognitive 45) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2253 — MultiJoin.outer has cognitive complexity 45 (threshold 15). Drivers by points: loops 9 (45 pts) (nesting depth added 36). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.left) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.apply (cognitive 36) · ×1
  • MultiJoin.apply (cognitive 36) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:670 — MultiJoin.apply 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. This shape REPEATS in the file: 2 other methods here (MultiJoin.left, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.left (cognitive 36) · ×1
  • MultiJoin.left (cognitive 36) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1447 — MultiJoin.left 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. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.outer (cognitive 36) · ×1
  • MultiJoin.outer (cognitive 36) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2224 — MultiJoin.outer 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. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.left) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · FixAvroCoder.fix (cognitive 30) · ×1
  • FixAvroCoder.fix (cognitive 30) scalafix/rules/src/main/scala/fix/v0_14_0/FixAvroCoder.scala:191 — FixAvroCoder.fix has cognitive complexity 30 (threshold 15). Drivers by points: match/switch 8 (14 pts), boolean chains 8, if/else 8 (nesting depth added 6). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · MultiJoin.apply (cognitive 28) · ×1
  • MultiJoin.apply (cognitive 28) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:643 — MultiJoin.apply has cognitive complexity 28 (threshold 15). Drivers by points: loops 7 (28 pts) (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. This shape REPEATS in the file: 2 other methods here (MultiJoin.left, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.left (cognitive 28) · ×1
  • MultiJoin.left (cognitive 28) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1420 — MultiJoin.left has cognitive complexity 28 (threshold 15). Drivers by points: loops 7 (28 pts) (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. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.outer (cognitive 28) · ×1
  • MultiJoin.outer (cognitive 28) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2197 — MultiJoin.outer has cognitive complexity 28 (threshold 15). Drivers by points: loops 7 (28 pts) (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. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.left) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · ScioContext.parseArguments (cognitive 27) · ×1
  • ScioContext.parseArguments (cognitive 27) scio-core/src/main/scala/com/spotify/scio/ScioContext.scala:325 — ScioContext.parseArguments has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (19 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 11). 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.
D2 · Cognitive Complexity · Functions.combineFn (cognitive 22) · ×1
  • Functions.combineFn (cognitive 22) scio-core/src/main/scala/com/spotify/scio/util/Functions.scala:149 — Functions.combineFn has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 3, loops 1 (3 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.
D2 · Cognitive Complexity · MultiJoin.apply (cognitive 21) · ×1
  • MultiJoin.apply (cognitive 21) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:618 — MultiJoin.apply has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.left, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.left (cognitive 21) · ×1
  • MultiJoin.left (cognitive 21) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1395 — MultiJoin.left has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.outer) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MultiJoin.outer (cognitive 21) · ×1
  • MultiJoin.outer (cognitive 21) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2172 — MultiJoin.outer has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This shape REPEATS in the file: 2 other methods here (MultiJoin.apply, MultiJoin.left) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala holds 51 of the 60 methods over the threshold — including the worst — and 5202 of the 5282 points over it (98%), 144.5× the next-largest file (scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/MultiSourceKeyGroupReader.java at 36). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · StorageUtil.setRawType (cognitive 18) · ×1
  • StorageUtil.setRawType (cognitive 18) scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/StorageUtil.scala:66 — StorageUtil.setRawType has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 6 (12 pts), if/else 6 (nesting depth added 6). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · RemoteFileUtil.downloadImpl (cognitive 18) · ×1
  • RemoteFileUtil.downloadImpl (cognitive 18) scio-core/src/main/java/com/spotify/scio/util/RemoteFileUtil.java:164 — RemoteFileUtil.downloadImpl has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 2, ternaries 1 (2 pts), error handling 1 (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.
D2 · Cognitive Complexity · SortBucketShardDoFn.processElement (cognitive 17) · ×1
  • SortBucketShardDoFn.processElement (cognitive 17) scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/SortedBucketSink.java:394 — SortBucketShardDoFn.processElement has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (3 pts), ternaries 1 (2 pts), error handling 1 (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.
D2 · Cognitive Complexity · SpecificRecordDatumFactory.addLogicalTypeConversions (cognitive 16) · ×1
  • SpecificRecordDatumFactory.addLogicalTypeConversions (cognitive 16) scio-avro/src/main/scala/com/spotify/scio/avro/AvroDatumFactory.scala:118 — SpecificRecordDatumFactory.addLogicalTypeConversions has cognitive complexity 16 (threshold 15). Drivers by points: loops 3 (9 pts), match/switch 2 (5 pts), if/else 2 (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.
D2 · Cognitive Complexity · ParquetReadFn.processElement (cognitive 16) · ×1
  • ParquetReadFn.processElement (cognitive 16) scio-parquet/src/main/scala/com/spotify/scio/parquet/read/ParquetReadFn.scala:159 — ParquetReadFn.processElement has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 2 (4 pts), boolean chains 1, match/switch 1 (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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Edited copy of a member (28 corresponding lines) · ×1
  • Edited copy of a member (28 corresponding lines) scio-core/src/main/scala/com/spotify/scio/values/PairHashSCollectionFunctions.scala:145 — scio-core/src/main/scala/com/spotify/scio/values/PairHashSCollectionFunctions.scala:145-172 | scio-extra/src/main/scala/com/spotify/scio/extra/sparkey/PairLargeHashSCollectionFunctions.scala:169-196 — These two members are one piece of code written twice and then edited apart: 28 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 · Members sharing a duplicated core (72 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (72 members, 50+ identical tokens) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:79 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:79-94 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:96-112 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:114-131 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:133-151 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:153-172 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:174-194 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:196-217 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:219-241 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:243-266 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:268-292 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:294-319 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:321-347 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:349-376 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:378-406 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:408-437 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:439-469 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:471-502 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:504-536 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:595-616 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:618-641 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:643-668 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:670-697 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:699-728 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:730-761 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:763-796 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:798-833 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:835-872 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:874-913 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:915-956 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:958-1001 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1003-1048 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1050-1097 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1099-1148 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1150-1201 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1203-1256 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1258-1313 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1372-1393 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1395-1418 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1420-1445 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1447-1474 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1476-1505 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1507-1538 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1540-1573 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1575-1610 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1612-1649 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1651-1690 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1692-1733 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1735-1778 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1780-1825 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1827-1874 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1876-1925 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1927-1978 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1980-2033 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2035-2090 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2149-2170 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2172-2195 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2197-2222 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2224-2251 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2253-2282 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2284-2315 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2317-2350 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2352-2387 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2389-2426 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2428-2467 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2469-2510 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2512-2555 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2557-2602 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2604-2651 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2653-2702 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2704-2755 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2757-2810 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2812-2867 — These 72 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 72 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 72 times.
D4 · Code Duplication · Members sharing a duplicated core (32 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (32 members, 50+ identical tokens) scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:207 — scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:207-242 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:248-285 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:291-330 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:336-377 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:383-426 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:432-477 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:483-530 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:536-585 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:591-642 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:648-701 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:707-762 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:768-825 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:831-890 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:896-957 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:963-1026 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1032-1097 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1253-1283 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1289-1321 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1327-1361 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1367-1403 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1409-1447 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1453-1493 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1499-1541 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1547-1591 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1597-1643 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1649-1697 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1703-1753 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1759-1811 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1817-1871 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1877-1933 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1939-1997 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:2003-2063 — These 32 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 32 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 32 times.
D4 · Code Duplication · Duplicated block (28 lines × 2) · ×1
  • Duplicated block (28 lines × 2) scalafix/rules/src/main/scala/fix/v0_14_0/FixAvroCoder.scala:109 — scalafix/rules/src/main/scala/fix/v0_14_0/FixAvroCoder.scala:109-136 | scalafix/rules/src/main/scala/fix/v0_14_0/FixAvroSchemasPackage.scala:79-106 — before extracting anything, compare `scalafix/rules/src/main/scala/fix/v0_14_0/FixAvroCoder.scala` and `scalafix/rules/src/main/scala/fix/v0_14_0/FixAvroSchemasPackage.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 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. 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 · Duplicated block (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) scio-avro/src/main/scala/com/spotify/scio/avro/types/SchemaUtil.scala:89 — scio-avro/src/main/scala/com/spotify/scio/avro/types/SchemaUtil.scala:89-106 | scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/SchemaUtil.scala:76-93 — 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 `scio-avro/src/main/scala/com/spotify/scio/avro/types/SchemaUtil.scala:89` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (4–17 lines × 4) · ×1
  • Duplicated block (4–17 lines × 4) scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala:96 — scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala:96-103 | scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala:182-198 | scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala:311-314 | scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala:376-392 — all 4 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 `scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala:182` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (16 lines × 3) · ×1
  • Duplicated block (16 lines × 3) scio-avro/src/main/scala/com/spotify/scio/avro/dynamic/syntax/AvroDynamicSCollectionSyntax.scala:64 — scio-avro/src/main/scala/com/spotify/scio/avro/dynamic/syntax/AvroDynamicSCollectionSyntax.scala:64-80 | scio-avro/src/main/scala/com/spotify/scio/avro/dynamic/syntax/AvroDynamicSCollectionSyntax.scala:113-129 | scio-avro/src/main/scala/com/spotify/scio/avro/dynamic/syntax/AvroDynamicSCollectionSyntax.scala:158-173 — 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 `scio-avro/src/main/scala/com/spotify/scio/avro/dynamic/syntax/AvroDynamicSCollectionSyntax.scala:64` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) scio-parquet/src/main/scala/com/spotify/scio/parquet/avro/dynamic/syntax/SCollectionSyntax.scala:63 — scio-parquet/src/main/scala/com/spotify/scio/parquet/avro/dynamic/syntax/SCollectionSyntax.scala:63-77 | scio-parquet/src/main/scala/com/spotify/scio/parquet/types/dynamic/syntax/SCollectionSyntax.scala:51-65 — 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 `scio-parquet/src/main/scala/com/spotify/scio/parquet/avro/dynamic/syntax/SCollectionSyntax.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.
D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×1
  • Duplicated block (13–14 lines × 2) scio-avro/src/main/scala/com/spotify/scio/avro/types/ConverterProvider.scala:69 — scio-avro/src/main/scala/com/spotify/scio/avro/types/ConverterProvider.scala:69-82 | scio-avro/src/main/scala/com/spotify/scio/avro/types/ConverterProvider.scala:151-163 — 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 `scio-avro/src/main/scala/com/spotify/scio/avro/types/ConverterProvider.scala:69` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×1
  • Duplicated block (14 lines × 2) scio-core/src/main/scala/com/spotify/scio/values/PairHashSCollectionFunctions.scala:153 — scio-core/src/main/scala/com/spotify/scio/values/PairHashSCollectionFunctions.scala:153-166 | scio-extra/src/main/scala/com/spotify/scio/extra/sparkey/PairLargeHashSCollectionFunctions.scala:177-190 — before extracting anything, compare `scio-core/src/main/scala/com/spotify/scio/values/PairHashSCollectionFunctions.scala` and `scio-extra/src/main/scala/com/spotify/scio/extra/sparkey/PairLargeHashSCollectionFunctions.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 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 `scio-core/src/main/scala/com/spotify/scio/values/PairHashSCollectionFunctions.scala:153` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10–11 lines × 19) · ×1
  • Duplicated block (10–11 lines × 19) scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:111 — scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:111-121 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:147-156 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:185-194 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:225-234 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:267-276 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:311-320 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:357-366 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:405-414 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:455-464 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:507-516 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:561-570 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:617-626 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:675-684 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:735-744 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:797-806 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:861-870 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:927-936 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:995-1004 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1065-1074 — all 19 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 `scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:111` 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 after the matched lines, `scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:156` calls `getAll` and `scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:121` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (10 lines × 26) · ×1
  • Duplicated block (10 lines × 26) scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:347 — scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:347-356 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:394-403 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:443-452 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:494-503 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:547-556 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:602-611 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:659-668 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:718-727 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:779-788 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:842-851 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:907-916 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:974-983 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1043-1052 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1368-1377 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1410-1419 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1454-1463 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1500-1509 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1548-1557 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1598-1607 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1650-1659 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1704-1713 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1760-1769 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1818-1827 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1878-1887 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1940-1949 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:2004-2013 — all 26 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.
D4 · Code Duplication · Duplicated block (10 lines × 16) · ×1
  • Duplicated block (10 lines × 16) scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:215 — scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:215-224 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:256-265 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:299-308 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:344-353 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:391-400 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:440-449 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:491-500 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:544-553 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:599-608 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:656-665 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:715-724 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:776-785 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:839-848 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:904-913 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:971-980 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1040-1049 — all 16 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 `scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:215` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10 lines × 6) · ×1
  • Duplicated block (10 lines × 6) scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:917 — scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:917-926 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:984-993 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1053-1062 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1888-1897 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1950-1959 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:2014-2023 — all 6 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.
D4 · Code Duplication · Duplicated block (10 lines × 4) · ×1
  • Duplicated block (10 lines × 4) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:137 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:137-146 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:674-683 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1451-1460 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2228-2237 — all 4 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.
D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×1
  • Duplicated block (9–10 lines × 2) scio-core/src/main/scala/com/spotify/scio/io/BinaryIO.scala:96 — scio-core/src/main/scala/com/spotify/scio/io/BinaryIO.scala:96-104 | scio-tensorflow/src/main/scala/com/spotify/scio/tensorflow/TFRecordIO.scala:231-240 — 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.
D4 · Code Duplication · Duplicated block (9 lines × 7) · ×1
  • Duplicated block (9 lines × 7) scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:917 — scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:917-925 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:984-992 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1053-1061 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1828-1836 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1888-1896 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1950-1958 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:2014-2022 — all 7 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.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×1
  • Duplicated block (9 lines × 4) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:118 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:118-126 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:647-655 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1424-1432 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2201-2209 — all 4 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.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×1
  • Duplicated block (9 lines × 3) scio-smb/src/main/scala/com/spotify/scio/smb/syntax/SortMergeBucketScioContextSyntax.scala:321 — scio-smb/src/main/scala/com/spotify/scio/smb/syntax/SortMergeBucketScioContextSyntax.scala:321-329 | scio-smb/src/main/scala/com/spotify/scio/smb/syntax/SortMergeBucketScioContextSyntax.scala:406-414 | scio-smb/src/main/scala/com/spotify/scio/smb/syntax/SortMergeBucketScioContextSyntax.scala:502-510 — 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 `scio-smb/src/main/scala/com/spotify/scio/smb/syntax/SortMergeBucketScioContextSyntax.scala:321` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (4–9 lines × 4) · ×1
  • Duplicated block (4–9 lines × 4) scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala:103 — scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala:103-110 | scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala:205-213 | scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala:314-317 | scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala:397-405 — all 4 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 `scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/types/ConverterProvider.scala:103` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (7–8 lines × 32) · ×1
  • Duplicated block (7–8 lines × 32) scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:231 — scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:231-238 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:273-279 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:317-323 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:363-369 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:411-417 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:461-467 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:513-519 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:567-573 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:623-629 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:681-687 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:741-747 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:803-809 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:867-873 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:933-939 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1001-1007 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1071-1077 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1262-1269 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1299-1305 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1338-1344 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1379-1385 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1422-1428 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1467-1473 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1514-1520 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1563-1569 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1614-1620 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1667-1673 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1722-1728 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1779-1785 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1838-1844 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1899-1905 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1962-1968 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:2027-2033 — all 32 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 `scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:231` 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 after the matched lines, `scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:279` calls `getAll` and `scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:238` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (7–8 lines × 17) · ×1
  • Duplicated block (7–8 lines × 17) scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1226 — scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1226-1233 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1261-1267 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1298-1304 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1337-1343 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1378-1384 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1421-1427 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1466-1472 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1513-1519 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1562-1568 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1613-1619 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1666-1672 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1721-1727 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1778-1784 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1837-1843 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1898-1904 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1961-1967 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:2026-2032 — all 17 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 `scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1226` 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 after the matched lines, `scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1267` calls `getAll` and `scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1233` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8 lines × 4) · ×1
  • Duplicated block (8 lines × 4) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:100 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:100-107 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:622-629 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1399-1406 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2176-2183 — all 4 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.
D4 · Code Duplication · Duplicated block (7–8 lines × 2) · ×1
  • Duplicated block (7–8 lines × 2) scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/taps.scala:162 — scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/taps.scala:162-168 | scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/taps.scala:177-184 — 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 `scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigquery/taps.scala:162` 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.
D4 · Code Duplication · Duplicated block (6–7 lines × 20) · ×1
  • Duplicated block (6–7 lines × 20) scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:520 — scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:520-526 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:574-579 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:630-635 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:688-693 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:748-753 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:810-815 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:874-879 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:940-945 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1008-1013 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1078-1083 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1521-1527 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1570-1575 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1621-1626 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1674-1679 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1729-1734 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1786-1791 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1845-1850 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1906-1911 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1969-1974 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:2034-2039 — all 20 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. 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 after the matched lines, `scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:579` calls `getAll` and `scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:526` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (6–7 lines × 8) · ×1
  • Duplicated block (6–7 lines × 8) scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:880 — scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:880-886 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:946-951 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1014-1019 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1084-1089 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1851-1857 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1912-1917 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1975-1980 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:2040-2045 — all 8 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. 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 after the matched lines, `scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:951` calls `getAll` and `scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:886` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (4–7 lines × 5) · ×1
  • Duplicated block (4–7 lines × 5) scio-core/src/main/scala/com/spotify/scio/util/ArtisanJoin.scala:68 — scio-core/src/main/scala/com/spotify/scio/util/ArtisanJoin.scala:68-71 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:35-38 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:542-548 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1319-1325 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2096-2102 — there are 5 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:542` 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 after the matched lines, `scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:39` calls `of` and `scio-core/src/main/scala/com/spotify/scio/util/ArtisanJoin.scala:71` 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.
D4 · Code Duplication · Duplicated block (6 lines × 72) · ×1
  • Duplicated block (6 lines × 72) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:83 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:83-88 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:100-105 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:118-123 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:137-142 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:157-162 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:178-183 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:200-205 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:223-228 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:247-252 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:272-277 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:298-303 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:325-330 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:353-358 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:382-387 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:412-417 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:443-448 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:475-480 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:508-513 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:599-604 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:622-627 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:647-652 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:674-679 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:703-708 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:734-739 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:767-772 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:802-807 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:839-844 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:878-883 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:919-924 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:962-967 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1007-1012 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1054-1059 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1103-1108 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1154-1159 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1207-1212 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1262-1267 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1376-1381 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1399-1404 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1424-1429 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1451-1456 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1480-1485 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1511-1516 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1544-1549 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1579-1584 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1616-1621 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1655-1660 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1696-1701 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1739-1744 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1784-1789 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1831-1836 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1880-1885 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1931-1936 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1984-1989 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2039-2044 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2153-2158 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2176-2181 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2201-2206 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2228-2233 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2257-2262 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2288-2293 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2321-2326 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2356-2361 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2393-2398 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2432-2437 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2473-2478 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2516-2521 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2561-2566 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2608-2613 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2657-2662 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2708-2713 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2761-2766 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2816-2821 — all 72 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.
D4 · Code Duplication · Duplicated block (6 lines × 48) · ×1
  • Duplicated block (6 lines × 48) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:206 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:206-211 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:229-234 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:253-258 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:278-283 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:304-309 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:331-336 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:359-364 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:388-393 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:418-423 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:449-454 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:481-486 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:514-519 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:773-778 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:808-813 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:845-850 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:884-889 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:925-930 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:968-973 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1013-1018 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1060-1065 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1109-1114 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1160-1165 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1213-1218 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1268-1273 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1550-1555 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1585-1590 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1622-1627 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1661-1666 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1702-1707 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1745-1750 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1790-1795 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1837-1842 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1886-1891 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1937-1942 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1990-1995 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2045-2050 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2327-2332 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2362-2367 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2399-2404 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2438-2443 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2479-2484 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2522-2527 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2567-2572 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2614-2619 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2663-2668 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2714-2719 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2767-2772 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2822-2827 — all 48 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 `scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:206` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6 lines × 24) · ×1
  • Duplicated block (6 lines × 24) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:365 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:365-370 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:394-399 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:424-429 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:455-460 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:487-492 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:520-525 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1019-1024 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1066-1071 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1115-1120 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1166-1171 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1219-1224 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1274-1279 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1796-1801 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1843-1848 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1892-1897 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1943-1948 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1996-2001 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2051-2056 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2573-2578 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2620-2625 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2669-2674 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2720-2725 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2773-2778 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2828-2833 — all 24 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 `scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:365` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5 lines × 16) · ×1
  • Duplicated block (5 lines × 16) scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1274 — scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1274-1278 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1312-1316 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1352-1356 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1394-1398 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1438-1442 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1484-1488 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1532-1536 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1582-1586 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1634-1638 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1688-1692 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1744-1748 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1802-1806 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1862-1866 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1924-1928 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1988-1992 | scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:2054-2058 — all 16 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 `scio-smb/src/main/scala/com/spotify/scio/smb/util/SMBMultiJoin.scala:1274` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5 lines × 4) · ×1
  • Duplicated block (5 lines × 4) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:52 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:52-56 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:559-563 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1336-1340 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:2113-2117 — all 4 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.
D4 · Code Duplication · Duplicated block (26 lines × 2) · ×1
  • Duplicated block (26 lines × 2) scalafix/input-0_8/src/main/scala/fix/v0_8_0/FixJoinNames.scala:29 — scalafix/input-0_8/src/main/scala/fix/v0_8_0/FixJoinNames.scala:29-54 | scalafix/output-0_8/src/main/scala/fix/v0_8_0/FixJoinNames.scala:26-51 — 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.
D4 · Code Duplication · Duplicated block (5 lines × 18) · ×1
  • Duplicated block (5 lines × 18) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:609 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:609-613 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:634-638 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:661-665 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:690-694 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:721-725 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:754-758 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:789-793 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:826-830 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:865-869 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:906-910 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:949-953 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:994-998 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1041-1045 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1090-1094 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1141-1145 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1194-1198 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1249-1253 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1306-1310 — all 18 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:633` calls `getAll` and `scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:608` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 13) · ×1
  • Duplicated block (5 lines × 13) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:749 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:749-753 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:784-788 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:821-825 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:860-864 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:901-905 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:944-948 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:989-993 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1036-1040 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1085-1089 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1136-1140 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1189-1193 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1244-1248 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1301-1305 — all 13 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:783` calls `getAll` and `scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:748` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 8) · ×1
  • Duplicated block (5 lines × 8) scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:939 — scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:939-943 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:984-988 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1031-1035 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1080-1084 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1131-1135 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1184-1188 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1239-1243 | scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:1296-1300 — all 8 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:983` calls `getAll` and `scio-core/src/main/scala/com/spotify/scio/util/MultiJoin.scala:938` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) scio-examples/src/main/scala/com/spotify/scio/examples/extra/MagnolifyTypedBigQueryTornadoes.scala:47 — scio-examples/src/main/scala/com/spotify/scio/examples/extra/MagnolifyTypedBigQueryTornadoes.scala:47-65 | scio-examples/src/main/scala/com/spotify/scio/examples/extra/TypedBigQueryTornadoes.scala:55-73 — 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 `scio-examples/src/main/scala/com/spotify/scio/examples/extra/MagnolifyTypedBigQueryTornadoes.scala:47` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×1
  • Duplicated block (12 lines × 3) scio-examples/src/main/scala/com/spotify/scio/examples/cookbook/BigQueryTornadoes.scala:37 — scio-examples/src/main/scala/com/spotify/scio/examples/cookbook/BigQueryTornadoes.scala:37-48 | scio-examples/src/main/scala/com/spotify/scio/examples/cookbook/MaxPerKeyExamples.scala:36-47 | scio-examples/src/main/scala/com/spotify/scio/examples/cookbook/StorageBigQueryTornadoes.scala:37-48 — 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 all 3 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×1
  • Duplicated block (11 lines × 3) scio-examples/src/main/scala/com/spotify/scio/examples/cookbook/JoinExamples.scala:60 — scio-examples/src/main/scala/com/spotify/scio/examples/cookbook/JoinExamples.scala:60-70 | scio-examples/src/main/scala/com/spotify/scio/examples/cookbook/JoinExamples.scala:124-134 | scio-examples/src/main/scala/com/spotify/scio/examples/cookbook/JoinExamples.scala:152-163 — 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.
D4 · Code Duplication · Duplicated block (6 lines × 5) · ×1
  • Duplicated block (6 lines × 5) scio-examples/src/main/scala/com/spotify/scio/examples/cookbook/BigQueryTornadoes.scala:40 — scio-examples/src/main/scala/com/spotify/scio/examples/cookbook/BigQueryTornadoes.scala:40-45 | scio-examples/src/main/scala/com/spotify/scio/examples/cookbook/CombinePerKeyExamples.scala:42-47 | scio-examples/src/main/scala/com/spotify/scio/examples/cookbook/DistinctByKeyExample.scala:41-46 | scio-examples/src/main/scala/com/spotify/scio/examples/cookbook/MaxPerKeyExamples.scala:39-44 | scio-examples/src/main/scala/com/spotify/scio/examples/cookbook/StorageBigQueryTornadoes.scala:40-45 — 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 all 5 call sites, so a change lands once.
M1 · Documentation (README) · README may be stale · ×1
  • README may be stale — 20 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
P12 · CI test-gate honesty · Coverage collected but not gated · ×1
  • Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
Minor — 6 finding(s)
D16 · Bus Factor · Off-boarding risk · ×2
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 5 significant file(s) lose their only recent owner: scio-parquet/src/main/scala/com/spotify/scio/parquet/avro/ParquetAvroIO.scala, scio-smb/src/main/java/org/apache/beam/sdk/extensions/smb/ParquetAvroFileOperations.java, scio-parquet/src/main/scala/com/spotify/scio/parquet/types/ParquetTypeIO.scala, scio-core/src/main/scala/com/spotify/scio/io/Taps.scala, scio-avro/src/main/scala/com/spotify/scio/avro/types/SchemaProvider.scala. Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 3 significant file(s) lose their only recent owner: scio-google-cloud-platform/src/main/scala/com/spotify/scio/bigtable/syntax/ScioContextSyntax.scala, scio-avro/src/main/scala/com/spotify/scio/avro/AvroDatumFactory.scala, scio-core/src/main/scala/com/spotify/scio/SysProps.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 (9 single-owned of 386 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 386 of the 771 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • 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.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-c5a4bfc057e14e21bb1f06c3415489a8/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-c5a4bfc057e14e21bb1f06c3415489a8/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .69artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnone (dependency manifest found, not scanned for vulnerabilities here)—none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (an sbt build (build.sbt) — not scanned yet).0—
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .0artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesnone (dependency manifest found, not scanned for vulnerabilities here)—none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (an sbt build (build.sbt) — not scanned yet).0—

Run 01a0e377-cdcc-7877-a0bc-78261a60e836 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 69 · Warnings: 276 · Recommendations: 6 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 27-09-2026 @ 15:24 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.

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