Public report of 7mind/izumi, published 14 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 14 November 2026, 14:49 UTC · Survey ID cd_695f21337ac24097a6ac1f5b989dda19

7mind/izumi

Measured 14 November 2026, 14:49 UTC, at code version 8b4a31f

CAI score 57out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Down 2 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A medium codebase: 50,825 lines of product code in 41 projects, tests not counted · Estimated rebuild effort: about 0.5 person-years · Weakest lens: Production Readiness, 47

Findings by how serious they are

19 critical 226 serious 33 minor

13 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 14:49 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

48of 48 dimensions measured by tools.
263of 278 findings point to an exact file and line, so you can open each one in the code. The other 15 concern the repository as a whole, such as missing documentation.
48dimensions across 6 lenses, read from 50,825 lines of product code in 41 projects.
Chapters

Executive summary

7mind/izumi falls short of our standard for production because we found no automated security scanning of the code, its secrets or its dependencies. It scores 57 out of 100 and is rated Adequate, and all 19 of its critical findings are security problems.

Production Readiness, at 47, is the weakest lens and counts most in the score. The best first step is fixing the password or key in the code, worth about 8 points. Adding automated security scanning comes next, worth about 7 points. Raising Production Readiness to 70 would lift the score to about 65.

Fifteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three secrets can leak from the build pipeline, and one password or key is open to anyone who can read the repository. Replacing the exposed password or key, pinning each tool to an exact version and limiting each secret to its own step would close these risks.

The product code is 50,825 lines, about €70,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Production Readiness 47 · counts for 46%Security and Compliance 61 · counts for 25%Code Health 62 · counts for 14%Maturity 63 · counts for 8%Architecture 98 · counts for 4%Performance 100 · counts for 2%

If Production Readiness rose from 47 to 70, the lowest score rated Strong, the score would rise from 57 to about 65.

Code composition: what the lines of code are
Product code 75%Tests 25%
New since the last survey: 54 findings

These 54 critical or serious findings weren't in the previous survey, on 26 October 2026.

  • Code Duplication · Edited copy of a member (32 corresponding lines) fundamentals/fundamentals-bio/.js/src/main/scala/izumi/functional/quasi/__QuasiAsyncPlatformSpecific.scala
  • Code Duplication · Edited copy of a member (46 corresponding lines) logstage/logstage-core/src/main/scala/izumi/logstage/api/rendering/LogstageReprWriter.scala
  • Code Duplication · Edited copy of a member (39 corresponding lines) logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/ArgumentNameExtractionMacro.scala
  • Code Duplication · Edited copy of a member (9 corresponding lines) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/quasi/QuasiIO.scala
  • Code Duplication · Edited copy of a member (16 corresponding lines) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/Mutex2.scala
  • Code Duplication · Edited copies of one member (4 members, 19+ corresponding lines) logstage/logstage-core/src/main/scala/logstage/LogIO.scala
  • Code Duplication · Edited copy of a member (21 corresponding lines) fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/collections/nonempty/NonEmptyListInstances.scala
  • Code Duplication · Edited copy of a member (26 corresponding lines) fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/graphs/tools/random/RandomGraph.scala
  • Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LogIOMacroMethods.scala
  • Code Duplication · Edited copies of one member (4 members, 11+ corresponding lines) logstage/logstage-core/src/main/scala/logstage/LogZIO.scala
  • Code Duplication · Edited copy of a member (12 corresponding lines) fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/cli/SubArgsParser.scala
  • Code Duplication · Edited copy of a member (10 corresponding lines) distage/distage-core-api/src/main/scala/izumi/distage/model/definition/dsl/LifecycleAdapters.scala
  • Code Duplication · Edited copy of a member (10 corresponding lines) fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/strings/TextTree.scala
  • Code Duplication · Edited copy of a member (15 corresponding lines) distage/distage-extension-config/.js/src/main/scala/izumi/distage/config/package.scala
  • Code Duplication · Edited copy of a member (21 corresponding lines) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/BioEither.scala
  • Code Duplication · Edited copy of a member (11 corresponding lines) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/lifecycle/LifecycleMethodImpls.scala
  • Code Duplication · Edited copy of a member (4 corresponding lines) fundamentals/fundamentals-bio/.js/src/main/scala/izumi/functional/quasi/QuasiIORunner.scala
  • Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/retry/RetryPolicy.scala
  • Code Duplication · Edited copy of a member (16 corresponding lines) fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/tags/TagExpr.scala
  • Code Duplication · Edited copy of a member (9 corresponding lines) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/ErrorAccumulatingOps2.scala
  • Code Duplication · Edited copies of one member (4 members, 11+ corresponding lines) logstage/logstage-core/src/main/scala/logstage/LogstageCats.scala
  • Code Duplication · Edited copies of one member (4 members, 11+ corresponding lines) logstage/logstage-core/src/main/scala/logstage/LogZIO.scala
  • Code Duplication · Edited copy of a member (14 corresponding lines) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/BioEither.scala
  • Code Duplication · Edited copy of a member (9 corresponding lines) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/ErrorAccumulatingOps2.scala
  • Code Duplication · Edited copy of a member (10 corresponding lines) logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LogMethodMacro.scala
  • Code Duplication · Edited copy of a member (12 corresponding lines) fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/strings/TextTree.scala
  • Code Duplication · Edited copy of a member (17 corresponding lines) fundamentals/fundamentals-platform/.jvm/src/main/scala/izumi/fundamentals/platform/files/RecursiveFileRemovals.scala
  • Code Duplication · Edited copy of a member (16 corresponding lines) fundamentals/fundamentals-platform/src/main/scala-3/izumi/fundamentals/platform/reflection/ReflectionUtil.scala
  • Code Duplication · Edited copy of a member (9 corresponding lines) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/Monad2.scala
  • Code Duplication · Edited copy of a member (9 corresponding lines) fundamentals/fundamentals-platform/src/main/scala-2/izumi/fundamentals/reflection/ReflectionUtil.scala
  • Code Duplication · Edited copy of a member (10 corresponding lines) logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/ArgumentNameExtractionMacro.scala
  • Code Duplication · Edited copy of a member (6 corresponding lines) distage/distage-core-api/src/main/scala/izumi/distage/model/definition/Bindings.scala
  • Code Duplication · Edited copy of a member (5 corresponding lines) distage/distage-testkit-core/src/main/scala/izumi/distage/testkit/model/TestConfig.scala
  • Code Duplication · Edited copy of a member (15 corresponding lines) distage/distage-testkit-core/.js/src/main/scala/izumi/distage/testkit/runner/impl/services/BootstrapFactory.scala
  • Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/BioEither.scala
  • Code Duplication · Edited copy of a member (10 corresponding lines) logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/ArgumentNameExtractionMacro.scala
  • Code Duplication · Edited copies of one member (6 members, 12+ corresponding lines) distage/distage-testkit-scalatest/src/main/scala-2/izumi/distage/testkit/scalatest/AssertCIO.scala
  • Code Duplication · Edited copy of a member (12 corresponding lines) fundamentals/fundamentals-bio/.js/src/main/scala/izumi/functional/bio/impl/MiniBIOAsyncPlatformSpecific.scala
  • Code Duplication · Edited copy of a member (16 corresponding lines) logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/ArgumentNameExtractionMacro.scala
  • Code Duplication · Edited copy of a member (15 corresponding lines) fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/strings/CharEscape.scala
  • Code Duplication · Edited copy of a member (9 corresponding lines) fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/collections/WildcardPrefixTree.scala
  • Code Duplication · Edited copy of a member (11 corresponding lines) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/BioEither.scala
  • Code Duplication · Edited copy of a member (10 corresponding lines) distage/distage-testkit-scalatest/src/main/scala-2/izumi/distage/testkit/scalatest/AssertCIO.scala
  • Code Duplication · Edited copy of a member (6 corresponding lines) logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LogIOMacroMethods.scala
  • Code Duplication · Edited copy of a member (4 corresponding lines) fundamentals/fundamentals-bio/.js/src/main/scala/izumi/functional/quasi/QuasiIORunner.scala
  • Code Duplication · Edited copy of a member (6 corresponding lines) logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LogIOMacroMethods.scala
  • Code Duplication · Edited copy of a member (13 corresponding lines) doc/microsite/src/main/scala/microsite/FakePackageModifier.scala
  • Code Duplication · Edited copy of a member (4 corresponding lines) distage/distage-extension-config/.jvm/src/main/scala-3/izumi/distage/config/codec/MetaInstances.scala
  • Code Duplication · Edited copy of a member (7 corresponding lines) distage/distage-extension-config/.jvm/src/main/scala-3/izumi/distage/config/codec/MetaInstances.scala
  • Code Duplication · Edited copy of a member (8 corresponding lines) distage/distage-framework/.js/src/main/scala/izumi/distage/roles/launcher/PreparedAppSyntaxPlatformSpecific.scala
  • Code Duplication · Edited copy of a member (5 corresponding lines) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/CatsConversions.scala
  • Code Duplication · Edited copy of a member (3 corresponding lines) logstage/logstage-core/src/main/scala-3/izumi/logstage/api/logger/AbstractMacroLogIO.scala
  • Code Duplication · Edited copy of a member (3 corresponding lines) fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/cli/MultiModalArgsParserImpl.scala
  • Code Duplication · Edited copy of a member (3 corresponding lines) distage/distage-testkit-scalatest/src/main/scala-3/izumi/distage/testkit/scalatest/AssertIO2.scala

We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Rebuild cost: about €70,000 · Estimate
Cost to rebuild€23,000 to €120,000, for 385 to 1,221 hours of work, about 0.5 person-years for one engineer
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.8 at a score of 57. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 50,825 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.
Raises the score by about 8 points · Low effort · Secret Scanning
2
Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Raises the score by about 7 points · Medium effort · Security & performance tooling
3
Resolve the 1 `TransZio` spells `Zio` where 21 names in the project spell it `ZIO` finding(s) in Naming Consistency — start with package.scala.
Raises the score by about 3 points · Low effort · Naming Consistency

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €70,000 to build again, about 0.5 person-years of work. Its weakest lens is Production Readiness, at 47 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 Leaked secret finding(s) in Secret Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 8 points for low effort, because it clears the 1 Secret Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

At a glance — Code Health · 62% · Adequate · gated by X5 ·

At a glance — Architecture · 98% · Exemplary ·

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

At a glance — Readiness · 47% · Weak · gated by P3 ·

At a glance — Security · 61% · Adequate · gated by D36 ·

At a glance — Performance · 100% · Exemplary ·

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
A05:2025 — Injection18High / Critical
A03:2025 — Software Supply Chain Failures4Medium
A07:2025 — Authentication Failures1High / Critical

Roadmap

Top priorities: Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED; Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.

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

Do thisHelpsEffortDimension
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.+7.7 ptsLowSecret Scanning
Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.+7.4 ptsMediumSecurity & performance tooling
Resolve the 1 `TransZio` spells `Zio` where 21 names in the project spell it `ZIO` finding(s) in Naming Consistency — start with package.scala.+2.7 ptsLowNaming Consistency
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.+2.9 ptsMediumRelease Hygiene
Hide `org.slf4j.impl` (`StaticLoggerBinder`, `StaticLoggerServiceProvider`, `StaticMDCBinder`, `StaticMarkerBinder`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.+1.9 ptsMediumLibrary API & versioning
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.+1.7 ptsMediumArchitecture documentation
On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.+1.6 ptsMediumNullable reference types
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3).+0.8 ptsLowStatic Analysis (SAST)

File quality

Per-file score 0–10 — a quality signature. Of 123 files carrying findings, judged against the Production bar: 1% slop · 44% mixed · 55% near-clean.

FileScoreBandWorst signal
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
distage/distage-core-api/src/main/scala-3/izumi/distage/constructors/ConstructorUtil.scala6.0MixedExplicit Debt: FixmeComment
fundamentals/fundamentals-functoid/src/main/scala-3/izumi/distage/reflection/macros/DummyImplicitsExtractorMacro.scala6.0MixedExplicit Debt: FixmeComment
distage/distage-framework/src/main/scala/izumi/distage/framework/PlanCheck.scala6.0MixedExplicit Debt: FixmeComment
distage/distage-testkit-core/src/main/scala/izumi/distage/testkit/runner/impl/TestPlanner.scala6.0MixedExplicit Debt: FixmeComment
distage/distage-framework-docker/src/main/scala/izumi/distage/docker/impl/ContainerResource.scala6.0MixedExplicit Debt: FixmeComment
distage/distage-core/src/main/scala/izumi/distage/planning/sequential/ForwardingRefResolverDefaultImpl.scala6.0MixedExplicit Debt: TodoComment
fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/collections/nonempty/NEList.scala6.0MixedExplicit Debt: TodoComment
fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/collections/nonempty/NEString.scala6.0MixedExplicit Debt: TodoComment
distage/distage-core/src/main/scala/izumi/distage/planning/solver/PlanVerifier.scala6.0MixedExplicit Debt: TodoComment
distage/distage-core/src/test/scala/izumi/distage/injector/JSRAnnotationTest.scala6.5MixedExplicit Debt: FixmeComment
distage/distage-core-api/src/main/scala-3/izumi/distage/constructors/MakeMacro.scala6.7MixedExplicit Debt: FixmeComment
distage/distage-framework/src/main/scala-3/izumi/distage/framework/PlanCheckMaterializer.scala6.7MixedExplicit Debt: HackComment
fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/graphs/tools/cycles/CycleEraser.scala6.7MixedExplicit Debt: TodoComment
fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/collections/nonempty/NESet.scala6.7MixedExplicit Debt: TodoComment
fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/collections/nonempty/NEMap.scala6.7MixedExplicit Debt: TodoComment
sbtgen/Deps.scala6.7MixedExplicit Debt: FixmeComment
fundamentals/fundamentals-bio/src/main/scala/izumi/functional/quasi/QuasiIO.scala6.7MixedExplicit Debt: FixmeComment
fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/CatsConversions.scala6.7MixedExplicit Debt: FixmeComment
distage/distage-framework-docker/src/main/scala/izumi/distage/docker/ContainerNetworkDef.scala6.7MixedExplicit Debt: FixmeComment

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

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

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

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

Could not be resolved — 13

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

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 48 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.

Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked — 48 dimensions across the health lenses
D1D2D3D4D5D6D12D13D14D15D16D17D21D28D29D30D34D35D36D43AX10AX3AX4AX6AX8GD1IC1M1M2M3M4P1P10P2P3P6PF3X1X12X14X16X18X21X23X27X3X30X5

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, 263 of 278 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 or a scanner, 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
Canine Code Analyzer 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 · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1da88-da2f-78ed-a012-e7eb250997bf.

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.

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a Codecov configuration (.codecov.yml, target 65%) and 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 (.scala), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) and this repository declares an sbt build (repository root, 201 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.
  • D19 Documentation Quality — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (project/plugins.sbt), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
  • D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (50897 LoC, 2645 module-visible types across 277 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
  • D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `distage/distage-core-api/src/main/scala-3/izumi/distage/constructors/ClassConstructorMacro.scala`, `distage/distage-core-api/src/main/scala-3/izumi/distage/constructors/MakeMacro.scala`, `distage/distage-core-api/src/main/scala-3/izumi/distage/reflection/macros/FunctoidMacro.scala`, `distage/distage-core-api/src/main/scala/izumi/distage/model/definition/ModuleBase.scala`, `distage/distage-core-api/src/main/scala/izumi/distage/model/definition/dsl/ModuleDefDSL.scala`, … (+46 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
  • AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is distage, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
  • C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's Scala imports SLF4J but logs through a logger the reading cannot trace to it — a `log` handed down by a trait or passed in as a parameter — so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

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

Limitations & what we did not check

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

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity7.6 / 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.6 / 10 · rule-coverage 100% · ceiling Prevented

15 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was JsonSchemaGenerator.generateSchema at 48. A further 4 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 SingletonRef.interpret at 21 — they are counted neither in the figure above nor in this dimension's score. 4 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: distage/distage-core-api/src/main/scala/izumi/distage/model/definition/dsl/AbstractBindingDefDSL.scala (SingletonRef.interpret at 21), distage/distage-extension-plugins/src/main/scala-2/izumi/distage/plugins/ForcedRecompilationToken.scala (UniqueRecompilationTokenMacro.whiteboxMaterializeImpl at 18), distage/distage-extension-plugins/src/main/scala-3/izumi/distage/plugins/ForcedRecompilationToken.scala (UniqueRecompilationTokenMacro.materializeImpl at 18), fundamentals/fundamentals-platform/src/main/scala-3/izumi/fundamentals/platform/reflection/ReflectionUtil.scala (ReflectionUtil.allPartsStrong at 17). 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.

JsonSchemaGenerator.generateSchema (cyclomatic 48)distage/distage-framework/.jvm/src/main/scala/izumi/distage/roles/bundled/JsonSchemaGenerator.scala:61
LogMessageMacro.message (cyclomatic 34)logstage/logstage-core/src/main/scala-3/izumi/logstage/macros/LogMessageMacro.scala:24
ProvisioningFailureOps.render (cyclomatic 31)distage/distage-core-api/src/main/scala/izumi/distage/model/provisioning/PlanInterpreter.scala:97
MiniBIOAsync.runSyncToFirstAsyncBoundaryImpl (cyclomatic 26)fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIOAsync.scala:38
TypeUtil.isAssignableFrom (cyclomatic 26)fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/reflection/TypeUtil.scala:7

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

What to do

  1. Bring the 3 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with JsonSchemaGenerator.generateSchema (cyclomatic 48), LogMessageMacro.message (cyclomatic 34), ProvisioningFailureOps.render (cyclomatic 31). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 7.6 to about 8.1/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.

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

D2 · Cognitive Complexity6.5 / 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 6.5 / 10 · rule-coverage 100% · ceiling Prevented

38 method(s) exceeded the cognitive complexity threshold of 15; the worst was TestPlanner.prepareTestEnv at 63.

TestPlanner.prepareTestEnv (cognitive 63)distage/distage-testkit-core/src/main/scala/izumi/distage/testkit/runner/impl/TestPlanner.scala:237
JsonFlattener.parsePath (cognitive 45)fundamentals/fundamentals-json-circe/src/main/scala/izumi/fundamentals/json/flat/JsonFlattener.scala:99
GenericSemigraphTraverse.trace (cognitive 44)distage/distage-core/src/main/scala/izumi/distage/planning/solver/GenericSemigraphTraverse.scala:94
LogMessageMacro.message (cognitive 38)logstage/logstage-core/src/main/scala-3/izumi/logstage/macros/LogMessageMacro.scala:24
MiniBIOAsync.runSyncToFirstAsyncBoundaryImpl (cognitive 35)fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIOAsync.scala:38

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

What to do

  1. Bring the 7 bodies over 30 down to 30 or less in Cognitive Complexity — start with TestPlanner.prepareTestEnv (cognitive 63), JsonFlattener.parsePath (cognitive 45), GenericSemigraphTraverse.trace (cognitive 44). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 7 together lifts Cognitive Complexity from 6.5 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.

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

D3 · God Classes9.5 / 10Stronggated by 5 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.5 / 10 · rule-coverage 100% · ceiling Prevented

5 god class(es) detected.

TooManyMethods: NEList · ×4fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/collections/nonempty/NEList.scala:11
FileTooLong: sbtgen/Deps.scalasbtgen/Deps.scala

What to do

  1. Resolve the 4 TooManyMethods finding(s) in God Classes — start with NEList.scala, NEString.scala, NESet.scala. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 1 FileTooLong finding(s) in God Classes — start with Deps.scala. — One of this dimension's main actionable groups (1 warning-level).

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

D4 · Code Duplication8.6 / 10Strong✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

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

33 duplicated block group(s) detected. 3.5 % of the production lines (1,796 of 50,825) are in a reported copy. A further 54 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Edited copy of a member (9 corresponding lines) · ×6fundamentals/fundamentals-bio/src/main/scala/izumi/functional/quasi/QuasiIO.scala:467
Edited copy of a member (10 corresponding lines) · ×6distage/distage-core-api/src/main/scala/izumi/distage/model/definition/dsl/LifecycleAdapters.scala:95
Duplicated block (9 lines × 2) · ×5distage/distage-framework-docker/src/main/scala/izumi/distage/docker/ContainerNetworkDef.scala:101
Duplicated block (5 lines × 2) · ×5distage/distage-testkit-scalatest/src/main/scala-2/izumi/distage/testkit/scalatest/AssertCIO.scala:67
Edited copy of a member (16 corresponding lines) · ×4fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/Mutex2.scala:14

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

What to do

  1. Resolve the 6 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with ErrorAccumulatingOps2.scala (2), QuasiIO.scala, Monad2.scala. — One of this dimension's main actionable groups (6 warning-level).
  2. Resolve the 6 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with ArgumentNameExtractionMacro.scala (2), LifecycleAdapters.scala, TextTree.scala. — One of this dimension's main actionable groups (6 warning-level).
  3. Resolve the 5 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with ContainerNetworkDef.scala, DistageScalatestReporter.scala, LogMessageMacro.scala. — One of this dimension's main actionable groups (5 warning-level).

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

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

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

41 production modules (sbt), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 0 module(s) off the main sequence, with abstractness counted on 24 of the 41 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)9.8 / 10Stronggated by 1 serious finding✓ 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

1 of 72 classes have LCOM4 above 3.

Low cohesion: ConstructorUtil (LCOM4 8)distage/distage-core-api/src/main/scala-3/izumi/distage/constructors/ConstructorUtil.scala:118

What to do

  1. Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with ConstructorUtil.scala. — One of this dimension's main actionable groups (1 warning-level).

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

D12 · Dependency Hygiene9.7 8.5 / 10Strong✓ Tool-verified

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

Maturity: Documented → Verified → Prevented · effective 8.5 / 10 · rule-coverage 88% · ceiling Verified

6 outdated direct sbt declarations. 7 of 8 direct declarations were graded against Maven Central (1 not published there, which is what a private Nexus or Artifactory artifact looks like, 0 declaring a version range rather than an exact version). An sbt declaration names an EXACT version, so the remedy is an edit to the build file — there is no lockfile refresh that would move it. Test-, Provided- and it-scoped declarations are excluded, because a consumer of this project never receives them. A version held in a Scala val is read only when the val is one string literal: sbt is a program rather than a manifest, and evaluating a computed version would invent the measurement rather than take it. Whether any artifact is DEPRECATED or ABANDONED is not graded and cannot be — Maven Central publishes no such marker, and release age does not stand in for one: the most widely depended-upon libraries are routinely the stalest, being finished rather than abandoned. Known CVEs in this dependency graph are D30's question.

Outdated: com.github.docker-java:docker-java-core · ×6

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

D13 · Secret Scanning5.0 / 10Adequate✓ Tool-verified

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 5.0 / 10 · rule-coverage 100% · ceiling Prevented

1 secret(s) detected.

REDACTED

What to do

  1. Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

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

0 of 7 declared sbt dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the production coordinates this repository's 6 sbt build file(s) (build.sbt and project/*.scala) declare with a literal version, directly or through a string-literal val — `%%` resolved to the Scala binary suffix Central publishes under, test-scoped declarations excluded — the same declaration-site closure this analysis reads for dependency currency. sbt has no lockfile a checkout carries, so this is deliberately NOT the transitive closure. 33 further production coordinate(s) are declared with a version the build computes rather than writes as a literal — sbt is a program, and this pass does not run it — and are NOT graded: this verdict covers what the build pins literally or through a string-literal val, not the full graph. A further 1 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.

✓ On the Gold path — maintain.

Detailed fixes: d14_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.3 / 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.3 / 10 · rule-coverage 100% · ceiling Documented

17 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/syntax/Syntax2.scala. Counted over 253 of the 789 production source files in this repository: 532 are under the ~2,400-byte size floor this dimension measures over, and the remaining 4 have no attributable history left to measure.

Off-boarding risk: anonymized user #1
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.7 / 10Stronggated by 70 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.7 / 10 · rule-coverage 100% · ceiling Prevented

70 deducted task-comment markers across 50825 LoC (0.1/KLoC) → score 9.7. 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.

FixmeComment · ×38sbtgen/Deps.scala:125
TodoComment · ×30logstage/logstage-core/src/main/scala/izumi/logstage/api/rendering/logunits/LogFormat.scala:90
HackComment · ×2distage/distage-framework/src/main/scala-3/izumi/distage/framework/PlanCheckMaterializer.scala:168

What to do

  1. Resolve the 38 FixmeComment finding(s) in Explicit Debt — start with JSRAnnotationTest.scala (5), TestPlanner.scala (4), ConstructorUtil.scala (3). — One of this dimension's main actionable groups (38 warning-level).
  2. Resolve the 30 TodoComment finding(s) in Explicit Debt — start with LogFormat.scala (2), NEList.scala (2), NEString.scala (2). — One of this dimension's main actionable groups (30 warning-level).
  3. Resolve the 2 HackComment finding(s) in Explicit Debt — start with PlanCheckMaterializer.scala, ReflectionProviderDefaultImpl.scala. — One of this dimension's main actionable groups (2 warning-level).

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

D21 · Naming Consistency5.5 / 10Adequate✓ Tool-verified

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

Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.

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

1 naming inconsistencies among 22 declarations measured against a convention their peers follow.

`TransZio` spells `Zio` where 21 names in the project spell it `ZIO`fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/package.scala:137

What to do

  1. Resolve the 1 `TransZio` spells `Zio` where 21 names in the project spell it `ZIO` finding(s) in Naming Consistency — start with package.scala. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.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)6.0 / 10Adequate✓ 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 6.0 / 10 · rule-coverage 100% · ceiling Documented

18 finding(s): 0 critical, 18 high, 0 medium, 0 low. 15 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 43 file(s) — `distage/distage-core-api/src/main/scala-3/izumi/distage/constructors/MakeMacro.scala`, `distage/distage-core-api/src/main/scala/izumi/distage/model/definition/ModuleBase.scala`, `distage/distage-core-api/src/main/scala/izumi/distage/model/definition/dsl/ModuleDefDSL.scala`, `distage/distage-core/src/main/scala/izumi/distage/modules/support/ZIOSupportModule.scala`, `distage/distage-core/src/main/scala/izumi/distage/modules/typeclass/ZIOCatsEffectInstancesModule.scala`, … (+38 more) — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED

What to do

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

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

D30 · Dependency Vulnerabilities10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

No known-vulnerable dependencies in any ecosystem this repository declares.

✓ On the Gold path — maintain.

Detailed fixes: d30_recommendation.md.

D34 · Knowledge Freshness9.6 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

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

11 of 257 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is logstage/logstage-core/src/main/scala-3/izumi/logstage/macros/LogMethodMacro.scala. Counted over 257 of the 789 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×11logstage/logstage-core/src/main/scala-3/izumi/logstage/macros/LogMethodMacro.scala:1
Orphaned files with no living knowledge

✓ On the Gold path — maintain.

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

D35 · Change Coupling10.0 / 10Stronggated by 1 serious finding✓ 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

Strongest change-coupling: ScalatestLinearizedTestReporter.scala↔DistageScalatestReporter.scala 53%

Change coupling: ScalatestLinearizedTestReporter.scala ↔ DistageScalatestReporter.scaladistage/distage-testkit-scalatest/src/main/scala/izumi/distage/testkit/services/scalatest/dstest/ScalatestLinearizedTestReporter.scala:1

What to do

  1. Resolve the 1 Change coupling finding(s) in Change Coupling — start with ScalatestLinearizedTestReporter.scala. — One of this dimension's main actionable groups (1 warning-level).

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

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ 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 2.5 / 10 · rule-coverage 100% · ceiling Documented

1/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 — start with REDACTED. — 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 recommendation-level).

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

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Frontend & cross-cutting dimensions

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

AX10 · Code composition9.4 / 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.

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

  • `Entropy1[F]` declares 17 abstract members under just 15 distinct name(s): `nextBoolean`, `nextInt`, `nextInt`, `nextLong`, `nextLong`, `nextFloat`, `nextDouble`, `nextGaussian`, `nextBytes`, `nextPrintableChar`, `nextString`, `nextTimeUUID`, `nextUUID`, `shuffle`, `withSeed`, `setSeed`, `writeRandomBytes`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 17 separate responsibilities: a caller binds to 15 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 17 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/Entropy1.scala:13
  • `IzUUID` declares 17 abstract members under just 14 distinct name(s): `generateTimeUUID`, `generateTimeUUIDBytes`, `generateRandomUUID`, `getTimeUUID`, `getTimeUUIDFromMicros`, `getRandomTimeUUIDFromMicros`, `getTimeUUID`, `getTimeUUID`, `getUUID`, `decompose`, `minTimeUUID`, `maxTimeUUID`, `unixTimestamp`, `microsTimestamp`, `getTimeUUIDBytes`, `getTimeUUIDBytes`, `getAdjustedTimestamp`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 17 separate responsibilities: a caller binds to 14 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 17 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — fundamentals/fundamentals-bio/src/main/scala/izumi/fundamentals/platform/uuid/IzUUID.scala:8

What to do

  • Collapse overload sets (optional/default parameters, or an options object) — these interfaces are wide in SIGNATURES, not in responsibilities, so segregating them would relieve no caller.
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue in this repository's Scala: methods whose whole body is still `???` or a "not implemented" throw where nothing overrides them, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

IC1 · Incompleteness & stubs9.0 / 10Strong✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Scala: methods whose body is `???` or only throws a "not implemented" error, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • `forget` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — fundamentals/fundamentals-language/src/main/scala/izumi/fundamentals/platform/language/Quirks.scala:28

What to do

  • Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
M1 · Documentation (README)6.0 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

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

What to do

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation2.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.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

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

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

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.

P10 · Library API & versioning6.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

  • 4 public types in `org.slf4j.impl` are marked as implementation by their own namespace, folder or name: `StaticLoggerBinder` (logstage/logstage-adapter-slf4j/src/main/java/org/slf4j/impl/StaticLoggerBinder.java:7, `impl`), `StaticLoggerServiceProvider` (logstage/logstage-adapter-slf4j/src/main/java/org/slf4j/impl/StaticLoggerServiceProvider.java:11, `impl`), `StaticMDCBinder` (logstage/logstage-adapter-slf4j/src/main/java/org/slf4j/impl/StaticMDCBinder.java:7, `impl`), `StaticMarkerBinder` (logstage/logstage-adapter-slf4j/src/main/java/org/slf4j/impl/StaticMarkerBinder.java:7, `impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — logstage/logstage-adapter-slf4j/src/main/java/org/slf4j/impl/StaticLoggerBinder.java:7

What to do

  • Hide `org.slf4j.impl` (`StaticLoggerBinder`, `StaticLoggerServiceProvider`, `StaticMDCBinder`, `StaticMarkerBinder`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
P2 · Observability7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

P3 · Security & performance tooling0.0 / 10Critical✓ 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.

  • No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:9

What to do

  • Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene5.0 / 10Adequate✓ 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.

  • No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for` comprehension or `foreach` leaves the mutable collection it is walking alone — an `ArrayBuffer` or `ListBuffer` counts its changes and its iterator checks the count, an `ArrayDeque` (and `mutable.Queue`/`mutable.Stack`) is walked by index up to its starting length, and a `java.util` collection walked through `asScala` is fail-fast, so a body that adds to or removes from the very collection the loop is walking makes a later step throw `ConcurrentModificationException` (`IndexOutOfBoundsException` for a deque) and the remaining elements are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

X3 · Exception handling6.1 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×5) — fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/resources/IzResources.scala:177, fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/resources/IzResources.scala:205, distage/distage-framework/src/main/scala-3/izumi/distage/framework/PlanCheckMaterializer.scala:128, …
  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — distage/distage-framework/src/main/scala/izumi/distage/roles/launcher/AppShutdownStrategy.scala:123

What to do

  • Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

X5 · Nullable reference types2.0 / 10Critical✓ Tool-verified

Other · Code Health — Whether Scala's null is held to the type system and not undermined by assertions — a file compiled with `-Yexplicit-nulls` is one where `String` excludes null and `String | Null` admits it, a file under WartRemover's `Null` wart or Scalafix's `DisableSyntax.noNulls` is one whose code cannot write `null` and must say `Option`, and each `.nn`, `import scala.language.unsafeNulls` or null-lint suppression is the author overruling that.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • No build over this repository's 786 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.

What to do

  • On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.

Reference — by lens

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 Health62%Adequate — gated by X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture98%ExemplarySolid.
Maturity63%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness47%Weak — gated by P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security61%Adequate — gated by D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100%ExemplaryStrongest area.
Unscored — 1 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 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.

  • P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 65 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — not 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
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Scala code is a Play controller, a Cask routes object, a Scalatra servlet, a Finatra controller, an Akka/Pekko HTTP routes holder or a JSR-330/Spring singleton, so no instance is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
  • C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
  • C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
  • D10 Test Quality — ~16550 lines of test source are present (.scala) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
  • D11 Test Reliability — Test reliability not included — the .scala suite was found but not re-run
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D19 Documentation Quality — D19 withholds "Documentation: empty section": 1 candidate(s) were measured and not published.
  • 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 — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .java, .scala source were not judged.
  • D25 ADR Conformance — no ADRs to check
  • D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — 51 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not included — suite not readable by the collector
  • DM1 Domain Modelling — applicable but not scored (3 signals for this style, 2 needed — the count is met but a required primary signal is absent): 3 strongly-typed id(s); 398 value object(s); 16 domain event(s); its domain events are published by services or handlers — no domain entity raises one; no aggregate is declared and no domain structure surrounds the state-guarding types: not claimed as DDD
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • S1 Web-Security Posture — No web surface: 785 Scala file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server artifact (akka-http, pekko-http, http4s, Play, Finagle, zio-http, cask, Scalatra, a tapir server, Jetty, Undertow, …) outside test scope in its build, and no server package imported or server bound in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — no C# was loaded; this repository's Scala and Java were read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter; a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
  • X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — 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
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 19 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D13 · Secret Scanning · Leaked secret · ×1
  • REDACTED
Serious — 226 finding(s)
D17 · Explicit Debt · FixmeComment · ×38
  • FixmeComment sbtgen/Deps.scala:125 — // FIXME Disable monix due to lack of CE3 support as of now, see: — 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 fundamentals/fundamentals-functoid/src/main/scala-3/izumi/distage/reflection/macros/DummyImplicitsExtractorMacro.scala:85 — // FIXME carry forward `tpe` in the accumulator, instead of fixing-up "non-updated" dummies afterwards — 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 fundamentals/fundamentals-bio/src/main/scala/izumi/functional/quasi/QuasiIO.scala:512 — // FIXME: This instance's type is QuasiFunctor not QuasiApplicative to Scala 3 bug https://github.com/lampepfl/dotty/issues/16431
  • FixmeComment fundamentals/fundamentals-bio/src/main/scala/izumi/functional/lifecycle/Lifecycle.scala:544 — // FIXME: `Lifecycle.release` should have an `exit` parameter — 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 fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/CatsConversions.scala:179 — // FIXME: we're forced to constrain MonadCancel to Throwable — 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 fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/ForkZio.scala:23 — // FIXME: ZIO Bug / feature (interruption inheritance) breaks behavior in bracket/Lifecycle — 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 fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/ForkZio.scala:38 — // FIXME: ZIO Bug / feature (interruption inheritance) breaks behavior in bracket/Lifecycle — 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 fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/data/Free.scala:20 — // FIXME: Scala 3.1.4 bug: false unexhaustive match warning — 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 fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/data/FreeError.scala:36 — // FIXME: Scala 3.1.4 bug: false unexhaustive match warning — 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 fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/data/FreePanic.scala:45 — // FIXME: Scala 3.1.4 bug: false unexhaustive match warning — 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 distage/distage-testkit-core/src/main/scala/izumi/distage/testkit/runner/impl/TestPlanner.scala:181 — // FIXME: this shit is too fragile, this needs to be solved properly — 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 distage/distage-testkit-core/src/main/scala/izumi/distage/testkit/runner/impl/TestPlanner.scala:183 — // FIXME: remove IzLogger dependency in `ResourceRewriter` and stop inserting LogstageModule in bootstrap — 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 distage/distage-testkit-core/src/main/scala/izumi/distage/testkit/runner/impl/TestPlanner.scala:185 — // FIXME: HACK: _bootstrap_ keys that may vary between envs but shouldn't cause them to differ (because they should only impact bootstrap) — 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 distage/distage-testkit-core/src/main/scala/izumi/distage/testkit/runner/impl/TestPlanner.scala:254 — // FIXME: Including both bootstrap Plan & bootstrap Module into merge criteria to prevent `Bootloader` — 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 distage/distage-framework-docker/src/main/scala/izumi/distage/docker/ContainerNetworkDef.scala:146 — // FIXME: temporary hack to allow missing containers to skip tests (happens when both DockerWrapper & integration check that depends on Docker.Container are memoized) — 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 distage/distage-framework-docker/src/main/scala/izumi/distage/docker/impl/ContainerResource.scala:356 — // FIXME: temporary hack to allow missing containers to skip tests (happens when both DockerWrapper & integration check that depends on Docker.Container are memoized) — 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 distage/distage-framework/src/main/scala/izumi/distage/framework/PlanCheck.scala:173 — // fixme missing DefaultModule bindings !!! — 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 distage/distage-extension-config/src/test/scala/izumi/distage/config/ConfigTest.scala:49 — // FIXME: pureconfig can't read specialized map types — 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 distage/distage-extension-config/src/test/scala/izumi/distage/config/ConfigTest.scala:150 — // FIXME: pureconfig-magnolia can't read enumerations properly — 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 distage/distage-extension-config/src/main/scala/izumi/distage/config/model/AppConfig.scala:10 — // FIXME: exclude `shared` & `roles` fields from equals/hashCode for now, — 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 distage/distage-core-api/src/main/scala-3/izumi/distage/constructors/ClassConstructorMacro.scala:22 — // FIXME remove redundant check across macros — 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 distage/distage-core-api/src/main/scala-3/izumi/distage/constructors/ConstructorUtil.scala:354 — // FIXME duplicates FunctoidMacro.FunctoidParametersMacro#dropByName — 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 distage/distage-core-api/src/main/scala-3/izumi/distage/constructors/ConstructorUtil.scala:486 — // FIXME: move back to FactoryConstructor — 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 distage/distage-core-api/src/main/scala-3/izumi/distage/constructors/ConstructorUtil.scala:529 — // FIXME perform manual substition to work around https://github.com/lampepfl/dotty/issues/16468
  • FixmeComment distage/distage-core-api/src/main/scala-3/izumi/distage/constructors/MakeMacro.scala:129 — // FIXME remove redundant wrapping and .provider call — 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.
  • + 13 more in this group — see findings.md.
D17 · Explicit Debt · TodoComment · ×30
  • TodoComment logstage/logstage-core/src/main/scala/izumi/logstage/api/rendering/logunits/LogFormat.scala:90 — // TODO: we may try to use codec here — 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 logstage/logstage-core/src/main/scala/izumi/logstage/api/rendering/logunits/LogFormat.scala:204 — // TODO: we may try to use codec here — 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 fundamentals/fundamentals-json-circe/src/main/scala-2/izumi/fundamentals/json/circe/MaterializeDerivationMacros.scala:8 — // TODO: merge upstream, also with @JsonCodec — 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 fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/graphs/tools/gc/GC.scala:7 — // TODO: this class is not required for distage — 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 fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/graphs/tools/gc/Tracer.scala:8 — // TODO: this class is not required for distage — 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 fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/graphs/tools/cycles/CycleEraser.scala:8 — // TODO: this class is not required for distage — 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 fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/graphs/tools/cycles/LoopDetector.scala:8 — // TODO: this class is not required for distage — 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 fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/collections/nonempty/NEList.scala:33 — // TODO: Have I added these extra ++, etc. methods to Vector that take a NEList? — 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 fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/collections/nonempty/NEList.scala:315 — // TODO: Search for that: Vector in here and add a that: NEList in Vector. — 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 fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/collections/nonempty/NEMap.scala:112 — // TODO: Have I added these extra ++, etc. methods to Vector that take a NEMap? — 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 fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/collections/nonempty/NESet.scala:156 — // TODO: Have I added these extra ++, etc. methods to Vector that take a NESet? — 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 fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/collections/nonempty/NEString.scala:151 — // TODO: Have I added these extra ++, etc. methods to Vector that take a NEString? — 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 fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/collections/nonempty/NEString.scala:384 — // TODO: Search for that: Vector in here and add a that: NEString in Vector. — 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 distage/distage-testkit-core/src/main/scala/izumi/distage/testkit/runner/impl/services/TestStatusConverter.scala:82 — // TODO: can this match here?.. — 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 distage/distage-testkit-core/src/main/scala/izumi/distage/testkit/runner/impl/services/TestStatusConverter.scala:87 — // TODO: can this match here?.. — 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 distage/distage-framework-docker/src/test/scala/izumi/distage/testkit/docker/DistageTestDockerBIO.scala:26 — // TODO: additionally check flyway outcome with doobie — 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 distage/distage-core-api/src/main/scala-3/izumi/distage/constructors/ConstructorUtil.scala:701 — // TODO: check that there are no unconsumed parameters — 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 distage/distage-core-api/src/main/scala/izumi/distage/model/plan/Plan.scala:26 — // TODO: equals/hashcode should not be used under normal circumstances. Currently we need them for "memoization levels" to work but we have to get rid of that — 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 distage/distage-core-api/src/main/scala/izumi/distage/model/exceptions/runtime/MissingInstanceException.scala:12 — // TODO: this representation is imperfect, we will have to change this once we have https://github.com/zio/izumi-reflect/issues/367 implemented
  • TodoComment distage/distage-core-api/src/main/scala/izumi/distage/model/definition/LocatorDef.scala:27 — // TODO: shameless copypaste of [[ModuleDef]] for now; but we CAN unify all of LocatorDef, ModuleDef, TypeLevelDSL and Bindings DSLs into one... — 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 distage/distage-core-api/src/main/scala/izumi/distage/model/definition/errors/DIFailureInterpreter.scala:8 — // TODO: we need to completely get rid of exceptions, this is just some transitional stuff — 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 distage/distage-core/src/test/scala/izumi/distage/injector/CircularDependenciesTest.scala:116 — // assert(instance eq instance.self) // TODO: commented out to fit into scala3 factoryconstructor restrictions — 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 distage/distage-core/src/main/scala/izumi/distage/InjectorDefaultImpl.scala:56 — // TODO: probably this should be a part of the Planner itself — 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 distage/distage-core/src/main/scala/izumi/distage/planning/solver/GraphQueries.scala:54 — // TODO: I'm not sure if it's "correct" to "activate" all the points together but it simplifies things greatly — 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 distage/distage-core/src/main/scala/izumi/distage/planning/solver/GraphQueries.scala:129 — // TODO: should we remove roots which are retained by effective roots? see #1476
  • + 5 more in this group — see findings.md.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×6
  • Edited copy of a member (9 corresponding lines) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/quasi/QuasiIO.scala:467 — fundamentals/fundamentals-bio/src/main/scala/izumi/functional/quasi/QuasiIO.scala:467-475 | fundamentals/fundamentals-bio/src/main/scala/izumi/functional/quasi/QuasiIO.scala:485-494 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/ErrorAccumulatingOps2.scala:19 — fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/ErrorAccumulatingOps2.scala:19-27 | fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/ErrorAccumulatingOps2.scala:104-112 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/ErrorAccumulatingOps2.scala:51 — fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/ErrorAccumulatingOps2.scala:51-59 | fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/ErrorAccumulatingOps2.scala:86-94 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/Monad2.scala:53 — fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/Monad2.scala:53-61 | fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/Monad2.scala:63-75 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) fundamentals/fundamentals-platform/src/main/scala-2/izumi/fundamentals/reflection/ReflectionUtil.scala:103 — fundamentals/fundamentals-platform/src/main/scala-2/izumi/fundamentals/reflection/ReflectionUtil.scala:103-111 | fundamentals/fundamentals-platform/src/main/scala-2/izumi/fundamentals/reflection/ReflectionUtil.scala:113-121 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/collections/WildcardPrefixTree.scala:10 — fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/collections/WildcardPrefixTree.scala:10-23 | fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/collections/WildcardPrefixTree.scala:50-58 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×6
  • Edited copy of a member (10 corresponding lines) distage/distage-core-api/src/main/scala/izumi/distage/model/definition/dsl/LifecycleAdapters.scala:95 — distage/distage-core-api/src/main/scala/izumi/distage/model/definition/dsl/LifecycleAdapters.scala:95-104 | distage/distage-core-api/src/main/scala/izumi/distage/model/definition/dsl/LifecycleAdapters.scala:109-118 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/strings/TextTree.scala:110 — fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/strings/TextTree.scala:110-119 | fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/strings/TextTree.scala:122-131 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LogMethodMacro.scala:195 — logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LogMethodMacro.scala:195-204 | logstage/logstage-core/src/main/scala-3/izumi/logstage/macros/LogMethodMacro.scala:245-256 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/ArgumentNameExtractionMacro.scala:77 — logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/ArgumentNameExtractionMacro.scala:77-86 | logstage/logstage-core/src/main/scala-3/izumi/logstage/macros/ArgumentNameExtractionMacro.scala:76-85 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/ArgumentNameExtractionMacro.scala:88 — logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/ArgumentNameExtractionMacro.scala:88-97 | logstage/logstage-core/src/main/scala-3/izumi/logstage/macros/ArgumentNameExtractionMacro.scala:87-96 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) distage/distage-testkit-scalatest/src/main/scala-2/izumi/distage/testkit/scalatest/AssertCIO.scala:48 — distage/distage-testkit-scalatest/src/main/scala-2/izumi/distage/testkit/scalatest/AssertCIO.scala:48-57 | distage/distage-testkit-scalatest/src/main/scala-2/izumi/distage/testkit/scalatest/AssertZIO.scala:57-66 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×5
  • Duplicated block (9 lines × 2) distage/distage-framework-docker/src/main/scala/izumi/distage/docker/ContainerNetworkDef.scala:101 — distage/distage-framework-docker/src/main/scala/izumi/distage/docker/ContainerNetworkDef.scala:101-109 | distage/distage-framework-docker/src/main/scala/izumi/distage/docker/impl/ContainerResource.scala:627-635 — 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 `distage/distage-framework-docker/src/main/scala/izumi/distage/docker/ContainerNetworkDef.scala:101` 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) distage/distage-testkit-scalatest/src/main/scala/org/scalatest/distage/DistageScalatestReporter.scala:84 — distage/distage-testkit-scalatest/src/main/scala/org/scalatest/distage/DistageScalatestReporter.scala:84-92 | distage/distage-testkit-scalatest/src/main/scala/org/scalatest/distage/DistageScalatestReporter.scala:144-152 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `distage/distage-testkit-scalatest/src/main/scala/org/scalatest/distage/DistageScalatestReporter.scala:95` calls `Some` and `distage/distage-testkit-scalatest/src/main/scala/org/scalatest/distage/DistageScalatestReporter.scala:153` 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 (9 lines × 2) logstage/logstage-core/src/main/scala-3/izumi/logstage/macros/LogMessageMacro.scala:79 — logstage/logstage-core/src/main/scala-3/izumi/logstage/macros/LogMessageMacro.scala:79-87 | logstage/logstage-core/src/main/scala-3/izumi/logstage/macros/LogMessageMacro.scala:89-97 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) logstage/logstage-core/src/main/scala-3/izumi/logstage/macros/LogMethodMacro.scala:91 — logstage/logstage-core/src/main/scala-3/izumi/logstage/macros/LogMethodMacro.scala:91-99 | logstage/logstage-core/src/main/scala-3/izumi/logstage/macros/LogMethodMacro.scala:110-118 — 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 `logstage/logstage-core/src/main/scala-3/izumi/logstage/macros/LogMethodMacro.scala:91` 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) distage/distage-core/src/main/scala/izumi/distage/planning/solver/PlanVerifier.scala:56 — distage/distage-core/src/main/scala/izumi/distage/planning/solver/PlanVerifier.scala:56-64 | distage/distage-core/src/main/scala/izumi/distage/planning/solver/PlanVerifier.scala:116-124 — 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 `distage/distage-core/src/main/scala/izumi/distage/planning/solver/PlanVerifier.scala:56` 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 (5 lines × 2) · ×5
  • Duplicated block (5 lines × 2) distage/distage-testkit-scalatest/src/main/scala-2/izumi/distage/testkit/scalatest/AssertCIO.scala:67 — distage/distage-testkit-scalatest/src/main/scala-2/izumi/distage/testkit/scalatest/AssertCIO.scala:67-71 | distage/distage-testkit-scalatest/src/main/scala-2/izumi/distage/testkit/scalatest/AssertZIO.scala:77-81 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LogIOMacroMethods.scala:82 — logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LogIOMacroMethods.scala:82-86 | logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LogIOMacroMethods.scala:101-105 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) logstage/logstage-core/src/main/scala/logstage/LogZIO.scala:74 — logstage/logstage-core/src/main/scala/logstage/LogZIO.scala:74-78 | logstage/logstage-core/src/main/scala/logstage/strict/LogZIOStrict.scala:45-49 — 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 `logstage/logstage-core/src/main/scala/logstage/LogZIO.scala:74` 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 (5 lines × 2) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIO.scala:207 — fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIO.scala:207-211 | fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIOAsync.scala:560-564 — before extracting anything, compare `fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIO.scala` and `fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIOAsync.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 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.
  • Duplicated block (5 lines × 2) logstage/logstage-core/src/main/scala/logstage/LogZIO.scala:98 — logstage/logstage-core/src/main/scala/logstage/LogZIO.scala:98-102 | logstage/logstage-core/src/main/scala/logstage/strict/LogZIOStrict.scala:69-73 — 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 `logstage/logstage-core/src/main/scala/logstage/LogZIO.scala:98` 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.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×5
  • Swallowed exception (caught, then discarded) fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/resources/IzResources.scala:177 — `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/resources/IzResources.scala:205 — `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) distage/distage-framework/src/main/scala-3/izumi/distage/framework/PlanCheckMaterializer.scala:128 — `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) distage/distage-core-api/src/main/scala-3/izumi/distage/constructors/MakeMacro.scala:56 — `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) distage/distage-core-api/src/main/scala-3/izumi/distage/constructors/MakeMacro.scala:60 — `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
D3 · God Classes · TooManyMethods · ×4
  • TooManyMethods: NEList fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/collections/nonempty/NEList.scala:11 — TooManyMethods — 138 methods. The bar is 30 methods; this is 108 over it, 4.60× 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: NEString fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/collections/nonempty/NEString.scala:133 — TooManyMethods — 131 methods. The bar is 30 methods; this is 101 over it, 4.37× 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: NESet fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/collections/nonempty/NESet.scala:134 — TooManyMethods — 80 methods. The bar is 30 methods; this is 50 over it, 2.67× 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: NEMap fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/collections/nonempty/NEMap.scala:88 — TooManyMethods — 75 methods. The bar is 30 methods; this is 45 over it, 2.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×4
  • Edited copy of a member (16 corresponding lines) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/Mutex2.scala:14 — fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/Mutex2.scala:14-29 | fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/Mutex2.scala:31-48 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/tags/TagExpr.scala:214 — fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/tags/TagExpr.scala:214-229 | fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/tags/TagExpr.scala:231-246 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) fundamentals/fundamentals-platform/src/main/scala-3/izumi/fundamentals/platform/reflection/ReflectionUtil.scala:33 — fundamentals/fundamentals-platform/src/main/scala-3/izumi/fundamentals/platform/reflection/ReflectionUtil.scala:33-48 | fundamentals/fundamentals-platform/src/main/scala-3/izumi/fundamentals/platform/reflection/ReflectionUtil.scala:50-65 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/ArgumentNameExtractionMacro.scala:59 — logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/ArgumentNameExtractionMacro.scala:59-74 | logstage/logstage-core/src/main/scala-3/izumi/logstage/macros/ArgumentNameExtractionMacro.scala:58-73 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 11+ corresponding lines) · ×3
  • Edited copies of one member (4 members, 11+ corresponding lines) logstage/logstage-core/src/main/scala/logstage/LogZIO.scala:68 — logstage/logstage-core/src/main/scala/logstage/LogZIO.scala:68-78 | logstage/logstage-core/src/main/scala/logstage/LogZIO.scala:92-102 | logstage/logstage-core/src/main/scala/logstage/strict/LogZIOStrict.scala:39-49 | logstage/logstage-core/src/main/scala/logstage/strict/LogZIOStrict.scala:63-73 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 11+ corresponding lines) logstage/logstage-core/src/main/scala/logstage/LogstageCats.scala:13 — logstage/logstage-core/src/main/scala/logstage/LogstageCats.scala:13-23 | logstage/logstage-core/src/main/scala/logstage/LogstageCats.scala:25-35 | logstage/logstage-core/src/main/scala/logstage/strict/LogstageCatsStrict.scala:14-24 | logstage/logstage-core/src/main/scala/logstage/strict/LogstageCatsStrict.scala:26-36 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 11+ corresponding lines) logstage/logstage-core/src/main/scala/logstage/LogZIO.scala:56 — logstage/logstage-core/src/main/scala/logstage/LogZIO.scala:56-66 | logstage/logstage-core/src/main/scala/logstage/LogZIO.scala:80-90 | logstage/logstage-core/src/main/scala/logstage/strict/LogZIOStrict.scala:27-37 | logstage/logstage-core/src/main/scala/logstage/strict/LogZIOStrict.scala:51-61 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×3
  • Edited copy of a member (12 corresponding lines) fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/cli/SubArgsParser.scala:51 — fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/cli/SubArgsParser.scala:51-63 | fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/cli/SubArgsParser.scala:81-92 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/strings/TextTree.scala:240 — fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/strings/TextTree.scala:240-251 | fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/strings/TextTree.scala:254-265 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) fundamentals/fundamentals-bio/.js/src/main/scala/izumi/functional/bio/impl/MiniBIOAsyncPlatformSpecific.scala:12 — fundamentals/fundamentals-bio/.js/src/main/scala/izumi/functional/bio/impl/MiniBIOAsyncPlatformSpecific.scala:12-23 | fundamentals/fundamentals-bio/.jvm/src/main/scala/izumi/functional/bio/impl/MiniBIOAsyncPlatformSpecific.scala:18-33 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×3
  • Edited copy of a member (15 corresponding lines) distage/distage-extension-config/.js/src/main/scala/izumi/distage/config/package.scala:33 — distage/distage-extension-config/.js/src/main/scala/izumi/distage/config/package.scala:33-47 | distage/distage-extension-config/.js/src/main/scala/izumi/distage/config/package.scala:48-62 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) distage/distage-testkit-core/.js/src/main/scala/izumi/distage/testkit/runner/impl/services/BootstrapFactory.scala:48 — distage/distage-testkit-core/.js/src/main/scala/izumi/distage/testkit/runner/impl/services/BootstrapFactory.scala:48-62 | distage/distage-testkit-core/.jvm/src/main/scala/izumi/distage/testkit/runner/impl/services/BootstrapFactory.scala:65-79 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/strings/CharEscape.scala:6 — fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/strings/CharEscape.scala:6-20 | fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/strings/CharEscape.scala:22-40 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×3
  • Edited copy of a member (4 corresponding lines) fundamentals/fundamentals-bio/.js/src/main/scala/izumi/functional/quasi/QuasiIORunner.scala:56 — fundamentals/fundamentals-bio/.js/src/main/scala/izumi/functional/quasi/QuasiIORunner.scala:56-59 | fundamentals/fundamentals-bio/.jvm/src/main/scala/izumi/functional/quasi/QuasiIORunner.scala:93-97 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) fundamentals/fundamentals-bio/.js/src/main/scala/izumi/functional/quasi/QuasiIORunner.scala:37 — fundamentals/fundamentals-bio/.js/src/main/scala/izumi/functional/quasi/QuasiIORunner.scala:37-40 | fundamentals/fundamentals-bio/.jvm/src/main/scala/izumi/functional/quasi/QuasiIORunner.scala:72-75 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) distage/distage-extension-config/.jvm/src/main/scala-3/izumi/distage/config/codec/MetaInstances.scala:87 — distage/distage-extension-config/.jvm/src/main/scala-3/izumi/distage/config/codec/MetaInstances.scala:87-90 | distage/distage-extension-config/.jvm/src/main/scala-3/izumi/distage/config/codec/PureconfigInstances.scala:175-178 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×3
  • Edited copy of a member (6 corresponding lines) distage/distage-core-api/src/main/scala/izumi/distage/model/definition/Bindings.scala:61 — distage/distage-core-api/src/main/scala/izumi/distage/model/definition/Bindings.scala:61-66 | distage/distage-core-api/src/main/scala/izumi/distage/model/definition/Bindings.scala:68-73 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LogIOMacroMethods.scala:127 — logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LogIOMacroMethods.scala:127-132 | logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LoggerMacroMethods.scala:96-101 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LogIOMacroMethods.scala:115 — logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LogIOMacroMethods.scala:115-120 | logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LoggerMacroMethods.scala:84-89 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (3 corresponding lines) · ×3
  • Edited copy of a member (3 corresponding lines) logstage/logstage-core/src/main/scala-3/izumi/logstage/api/logger/AbstractMacroLogIO.scala:38 — logstage/logstage-core/src/main/scala-3/izumi/logstage/api/logger/AbstractMacroLogIO.scala:38-40 | logstage/logstage-core/src/main/scala-3/izumi/logstage/api/logger/AbstractMacroLogger.scala:38-40 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/cli/MultiModalArgsParserImpl.scala:49 — fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/cli/MultiModalArgsParserImpl.scala:49-51 | fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/cli/SubArgsParser.scala:95-102 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) distage/distage-testkit-scalatest/src/main/scala-3/izumi/distage/testkit/scalatest/AssertIO2.scala:30 — distage/distage-testkit-scalatest/src/main/scala-3/izumi/distage/testkit/scalatest/AssertIO2.scala:30-32 | distage/distage-testkit-scalatest/src/main/scala-3/izumi/distage/testkit/scalatest/AssertSync.scala:30-32 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×3
  • Duplicated block (11 lines × 2) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIOAsync.scala:363 — fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIOAsync.scala:363-373 | fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIOAsync.scala:448-458 — 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 `fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIOAsync.scala:363` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) logstage/logstage-core/src/main/scala/logstage/LogIO.scala:63 — logstage/logstage-core/src/main/scala/logstage/LogIO.scala:63-73 | logstage/logstage-core/src/main/scala/logstage/strict/LogIOStrict.scala:42-52 — 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 (11 lines × 2) logstage/logstage-core/src/main/scala/logstage/LogIO.scala:43 — logstage/logstage-core/src/main/scala/logstage/LogIO.scala:43-53 | logstage/logstage-core/src/main/scala/logstage/strict/LogIOStrict.scala:62-72 — 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 (10 lines × 2) · ×3
  • Duplicated block (10 lines × 2) distage/distage-testkit-scalatest/src/main/scala/org/scalatest/distage/DistageScalatestReporter.scala:68 — distage/distage-testkit-scalatest/src/main/scala/org/scalatest/distage/DistageScalatestReporter.scala:68-77 | distage/distage-testkit-scalatest/src/main/scala/org/scalatest/distage/DistageScalatestReporter.scala:150-159 — 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 `distage/distage-testkit-scalatest/src/main/scala/org/scalatest/distage/DistageScalatestReporter.scala:68` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `distage/distage-testkit-scalatest/src/main/scala/org/scalatest/distage/DistageScalatestReporter.scala:67` calls `Some` and `distage/distage-testkit-scalatest/src/main/scala/org/scalatest/distage/DistageScalatestReporter.scala:149` 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.
  • Duplicated block (10 lines × 2) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/BioEither.scala:57 — fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/BioEither.scala:57-66 | fundamentals/fundamentals-collections/src/main/scala/izumi/functional/IzEither.scala:240-249 — 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 `fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/BioEither.scala:57` 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 (10 lines × 2) distage/distage-core-api/src/main/scala/izumi/distage/model/plan/repr/DepTreeRenderer.scala:55 — distage/distage-core-api/src/main/scala/izumi/distage/model/plan/repr/DepTreeRenderer.scala:55-64 | distage/distage-core-api/src/main/scala/izumi/distage/model/plan/repr/OpFormatter.scala:20-29 — 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 (8 lines × 2) · ×3
  • Duplicated block (8 lines × 2) distage/distage-core-api/src/main/scala-3/izumi/distage/reflection/macros/IdExtractorImpl.scala:27 — distage/distage-core-api/src/main/scala-3/izumi/distage/reflection/macros/IdExtractorImpl.scala:27-34 | fundamentals/fundamentals-platform/src/main/scala-3/izumi/fundamentals/platform/reflection/ReflectionUtil.scala:124-131 — 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 `distage/distage-core-api/src/main/scala-3/izumi/distage/reflection/macros/IdExtractorImpl.scala:27` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) distage/distage-core-api/src/main/scala-2/izumi/distage/constructors/constructors.scala:65 — distage/distage-core-api/src/main/scala-2/izumi/distage/constructors/constructors.scala:65-72 | distage/distage-core-api/src/main/scala-3/izumi/distage/constructors/constructors.scala:63-70 — before extracting anything, compare `distage/distage-core-api/src/main/scala-2/izumi/distage/constructors/constructors.scala` and `distage/distage-core-api/src/main/scala-3/izumi/distage/constructors/constructors.scala` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 (8 lines × 2) distage/distage-framework/src/main/scala-2/izumi/distage/framework/PlanCheckMaterializer.scala:45 — distage/distage-framework/src/main/scala-2/izumi/distage/framework/PlanCheckMaterializer.scala:45-52 | distage/distage-framework/src/main/scala-3/izumi/distage/framework/PlanCheckMaterializer.scala:44-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 (6 lines × 2) · ×3
  • Duplicated block (6 lines × 2) fundamentals/fundamentals-bio/.jvm/src/main/scala/izumi/functional/bio/impl/MiniBIOAsyncPlatformSpecific.scala:37 — fundamentals/fundamentals-bio/.jvm/src/main/scala/izumi/functional/bio/impl/MiniBIOAsyncPlatformSpecific.scala:37-42 | fundamentals/fundamentals-bio/.jvm/src/main/scala/izumi/functional/bio/impl/MiniBIOPlatformSpecific.scala:9-14 — 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 (6 lines × 2) fundamentals/fundamentals-platform/src/main/scala-2/izumi/fundamentals/platform/resources/PortableResource.scala:106 — fundamentals/fundamentals-platform/src/main/scala-2/izumi/fundamentals/platform/resources/PortableResource.scala:106-111 | fundamentals/fundamentals-platform/src/main/scala-2/izumi/fundamentals/reflection/ReflectionUtil.scala:144-149 — 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 (6 lines × 2) logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LogIOMacroMethods.scala:138 — logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LogIOMacroMethods.scala:138-143 | logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LoggerMacroMethods.scala:107-112 — 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 `logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LogIOMacroMethods.scala:138` 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.
D17 · Explicit Debt · HackComment · ×2
  • HackComment distage/distage-framework/src/main/scala-3/izumi/distage/framework/PlanCheckMaterializer.scala:168 — // hack around nested objects — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
  • HackComment distage/distage-core-api/src/main/scala-2/izumi/distage/reflection/macros/universe/ReflectionProviderDefaultImpl.scala:184 — // Hack due to .typeSignatureIn throwing out type annotations... — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×2
  • Edited copy of a member (21 corresponding lines) fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/collections/nonempty/NonEmptyListInstances.scala:7 — fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/collections/nonempty/NonEmptyListInstances.scala:7-27 | fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/collections/nonempty/NonEmptySetInstances.scala:7-27 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/BioEither.scala:120 — fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/BioEither.scala:120-141 | fundamentals/fundamentals-collections/src/main/scala/izumi/functional/IzEither.scala:65-85 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×2
  • Edited copy of a member (11 corresponding lines) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/lifecycle/LifecycleMethodImpls.scala:65 — fundamentals/fundamentals-bio/src/main/scala/izumi/functional/lifecycle/LifecycleMethodImpls.scala:65-75 | fundamentals/fundamentals-bio/src/main/scala/izumi/functional/lifecycle/LifecycleMethodImpls.scala:80-90 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/BioEither.scala:100 — fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/BioEither.scala:100-110 | fundamentals/fundamentals-collections/src/main/scala/izumi/functional/IzEither.scala:260-270 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×2
  • Edited copy of a member (5 corresponding lines) distage/distage-testkit-core/src/main/scala/izumi/distage/testkit/model/TestConfig.scala:128 — distage/distage-testkit-core/src/main/scala/izumi/distage/testkit/model/TestConfig.scala:128-132 | distage/distage-testkit-core/src/main/scala/izumi/distage/testkit/model/TestConfig.scala:164-168 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/CatsConversions.scala:228 — fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/CatsConversions.scala:228-232 | fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/Panic2.scala:125-129 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×2
  • Duplicated block (16 lines × 2) logstage/logstage-core/src/main/scala/izumi/logstage/api/rendering/LogstageReprWriter.scala:39 — logstage/logstage-core/src/main/scala/izumi/logstage/api/rendering/LogstageReprWriter.scala:39-54 | logstage/logstage-rendering-circe/src/main/scala/izumi/logstage/api/rendering/json/LogstageCirceWriter.scala:36-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. Read the line range as the matched WINDOW rather than a finished unit: at `logstage/logstage-core/src/main/scala/izumi/logstage/api/rendering/LogstageReprWriter.scala:39` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `Token` names `izumi.logstage.api.rendering.LogstageReprWriter.Token` in one and `izumi.logstage.api.rendering.json.LogstageCirceWriter.Token` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (16 lines × 2) distage/distage-extension-config/.js/src/main/scala/izumi/distage/config/codec/DIConfigReaderPlatformSpecific.scala:37 — distage/distage-extension-config/.js/src/main/scala/izumi/distage/config/codec/DIConfigReaderPlatformSpecific.scala:37-52 | distage/distage-extension-config/.jvm/src/main/scala/izumi/distage/config/codec/DIConfigReaderPlatformSpecific.scala:29-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 (7 lines × 2) · ×2
  • Duplicated block (7 lines × 2) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/lifecycle/LifecycleMethodImpls.scala:40 — fundamentals/fundamentals-bio/src/main/scala/izumi/functional/lifecycle/LifecycleMethodImpls.scala:40-46 | fundamentals/fundamentals-bio/src/main/scala/izumi/functional/lifecycle/LifecycleMethodImpls.scala:115-121 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) distage/distage-core/src/main/scala/izumi/distage/planning/solver/PlanVerifier.scala:34 — distage/distage-core/src/main/scala/izumi/distage/planning/solver/PlanVerifier.scala:34-40 | distage/distage-core/src/main/scala/izumi/distage/planning/solver/PlanVerifier.scala:106-112 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `distage/distage-core/src/main/scala/izumi/distage/planning/solver/PlanVerifier.scala:34` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D1 · Cyclomatic Complexity · JsonSchemaGenerator.generateSchema (cyclomatic 48) · ×1
  • JsonSchemaGenerator.generateSchema (cyclomatic 48) distage/distage-framework/.jvm/src/main/scala/izumi/distage/roles/bundled/JsonSchemaGenerator.scala:61 — JsonSchemaGenerator.generateSchema has cyclomatic complexity 48 (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 · LogMessageMacro.message (cyclomatic 34) · ×1
  • LogMessageMacro.message (cyclomatic 34) logstage/logstage-core/src/main/scala-3/izumi/logstage/macros/LogMessageMacro.scala:24 — LogMessageMacro.message has cyclomatic complexity 34 (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 · ProvisioningFailureOps.render (cyclomatic 31) · ×1
  • ProvisioningFailureOps.render (cyclomatic 31) distage/distage-core-api/src/main/scala/izumi/distage/model/provisioning/PlanInterpreter.scala:97 — ProvisioningFailureOps.render has cyclomatic complexity 31 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · MiniBIOAsync.runSyncToFirstAsyncBoundaryImpl (cyclomatic 26) · ×1
  • MiniBIOAsync.runSyncToFirstAsyncBoundaryImpl (cyclomatic 26) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIOAsync.scala:38 — MiniBIOAsync.runSyncToFirstAsyncBoundaryImpl has cyclomatic complexity 26 (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 · TypeUtil.isAssignableFrom (cyclomatic 26) · ×1
  • TypeUtil.isAssignableFrom (cyclomatic 26) fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/reflection/TypeUtil.scala:7 — TypeUtil.isAssignableFrom has cyclomatic complexity 26 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · LogMessageMacro.processExpr (cyclomatic 23) · ×1
  • LogMessageMacro.processExpr (cyclomatic 23) logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LogMessageMacro.scala:57 — LogMessageMacro.processExpr 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 · factoryUtil.getFactoryProductData (cyclomatic 20) · ×1
  • factoryUtil.getFactoryProductData (cyclomatic 20) distage/distage-core-api/src/main/scala-3/izumi/distage/constructors/ConstructorUtil.scala:506 — factoryUtil.getFactoryProductData has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · GenericSemigraphTraverse.trace (cyclomatic 20) · ×1
  • GenericSemigraphTraverse.trace (cyclomatic 20) distage/distage-core/src/main/scala/izumi/distage/planning/solver/GenericSemigraphTraverse.scala:94 — GenericSemigraphTraverse.trace 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.
D1 · Cyclomatic Complexity · Impl.format (cyclomatic 19) · ×1
  • Impl.format (cyclomatic 19) distage/distage-core-api/src/main/scala/izumi/distage/model/plan/repr/OpFormatter.scala:48 — Impl.format 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 · GraphDumpObserver.modify (cyclomatic 18) · ×1
  • GraphDumpObserver.modify (cyclomatic 18) distage/distage-core/.jvm/src/main/scala/izumi/distage/planning/extensions/GraphDumpObserver.scala:124 — GraphDumpObserver.modify has cyclomatic complexity 18 (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 · PlanInterpreterNonSequentialRuntimeImpl.instantiateImpl (cyclomatic 18) · ×1
  • PlanInterpreterNonSequentialRuntimeImpl.instantiateImpl (cyclomatic 18) distage/distage-core/src/main/scala/izumi/distage/provisioning/PlanInterpreterNonSequentialRuntimeImpl.scala:58 — PlanInterpreterNonSequentialRuntimeImpl.instantiateImpl has cyclomatic complexity 18 (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 · DummyImplicitsExtractorMacro.extractDummyArguments (cyclomatic 18) · ×1
  • DummyImplicitsExtractorMacro.extractDummyArguments (cyclomatic 18) fundamentals/fundamentals-functoid/src/main/scala-3/izumi/distage/reflection/macros/DummyImplicitsExtractorMacro.scala:35 — DummyImplicitsExtractorMacro.extractDummyArguments has cyclomatic complexity 18 (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 · TypeUtil.defaultValue (cyclomatic 17) · ×1
  • TypeUtil.defaultValue (cyclomatic 17) fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/reflection/TypeUtil.scala:33 — TypeUtil.defaultValue has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · runtime.checkAppParsed (cyclomatic 16) · ×1
  • runtime.checkAppParsed (cyclomatic 16) distage/distage-framework/src/main/scala/izumi/distage/framework/PlanCheck.scala:116 — runtime.checkAppParsed has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · TestPlanner.prepareTestEnv (cyclomatic 16) · ×1
  • TestPlanner.prepareTestEnv (cyclomatic 16) distage/distage-testkit-core/src/main/scala/izumi/distage/testkit/runner/impl/TestPlanner.scala:237 — TestPlanner.prepareTestEnv 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.
D2 · Cognitive Complexity · TestPlanner.prepareTestEnv (cognitive 63) · ×1
  • TestPlanner.prepareTestEnv (cognitive 63) distage/distage-testkit-core/src/main/scala/izumi/distage/testkit/runner/impl/TestPlanner.scala:237 — TestPlanner.prepareTestEnv has cognitive complexity 63 (threshold 15). Drivers by points: loops 8 (31 pts), if/else 8 (25 pts), match/switch 1 (5 pts), boolean chains 2 (nesting depth added 44). 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 · JsonFlattener.parsePath (cognitive 45) · ×1
  • JsonFlattener.parsePath (cognitive 45) fundamentals/fundamentals-json-circe/src/main/scala/izumi/fundamentals/json/flat/JsonFlattener.scala:99 — JsonFlattener.parsePath has cognitive complexity 45 (threshold 15). Drivers by points: if/else 13 (29 pts), match/switch 2 (11 pts), loops 1 (4 pts), boolean chains 1 (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 · GenericSemigraphTraverse.trace (cognitive 44) · ×1
  • GenericSemigraphTraverse.trace (cognitive 44) distage/distage-core/src/main/scala/izumi/distage/planning/solver/GenericSemigraphTraverse.scala:94 — GenericSemigraphTraverse.trace has cognitive complexity 44 (threshold 15). Drivers by points: loops 7 (21 pts), if/else 7 (11 pts), match/switch 4 (11 pts), boolean chains 1 (nesting depth added 25). 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 · LogMessageMacro.message (cognitive 38) · ×1
  • LogMessageMacro.message (cognitive 38) logstage/logstage-core/src/main/scala-3/izumi/logstage/macros/LogMessageMacro.scala:24 — LogMessageMacro.message has cognitive complexity 38 (threshold 15). Drivers by points: match/switch 12 (29 pts), if/else 8 (9 pts) (nesting depth added 18). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · MiniBIOAsync.runSyncToFirstAsyncBoundaryImpl (cognitive 35) · ×1
  • MiniBIOAsync.runSyncToFirstAsyncBoundaryImpl (cognitive 35) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIOAsync.scala:38 — MiniBIOAsync.runSyncToFirstAsyncBoundaryImpl has cognitive complexity 35 (threshold 15). Drivers by points: error handling 5 (14 pts), match/switch 7 (14 pts), if/else 3 (7 pts) (nesting depth added 20). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · DummyImplicitsExtractorMacro.extractDummyArguments (cognitive 35) · ×1
  • DummyImplicitsExtractorMacro.extractDummyArguments (cognitive 35) fundamentals/fundamentals-functoid/src/main/scala-3/izumi/distage/reflection/macros/DummyImplicitsExtractorMacro.scala:35 — DummyImplicitsExtractorMacro.extractDummyArguments has cognitive complexity 35 (threshold 15). Drivers by points: match/switch 8 (18 pts), if/else 12 (17 pts) (nesting depth added 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · LogMessageMacro.processExpr (cognitive 31) · ×1
  • LogMessageMacro.processExpr (cognitive 31) logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LogMessageMacro.scala:57 — LogMessageMacro.processExpr has cognitive complexity 31 (threshold 15). Drivers by points: match/switch 12 (17 pts), if/else 13 (14 pts) (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 · factoryUtil.getFactoryProductData (cognitive 30) · ×1
  • factoryUtil.getFactoryProductData (cognitive 30) distage/distage-core-api/src/main/scala-3/izumi/distage/constructors/ConstructorUtil.scala:506 — factoryUtil.getFactoryProductData has cognitive complexity 30 (threshold 15). Drivers by points: match/switch 11 (17 pts), if/else 11 (13 pts) (nesting depth added 8). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · PlanInterpreterNonSequentialRuntimeImpl.instantiateImpl (cognitive 29) · ×1
  • PlanInterpreterNonSequentialRuntimeImpl.instantiateImpl (cognitive 29) distage/distage-core/src/main/scala/izumi/distage/provisioning/PlanInterpreterNonSequentialRuntimeImpl.scala:58 — PlanInterpreterNonSequentialRuntimeImpl.instantiateImpl has cognitive complexity 29 (threshold 15). Drivers by points: match/switch 5 (15 pts), loops 5 (11 pts), if/else 2 (3 pts) (nesting depth added 17). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · IndividualTestRunnerImpl.proceedTest (cognitive 27) · ×1
  • IndividualTestRunnerImpl.proceedTest (cognitive 27) distage/distage-testkit-core/src/main/scala/izumi/distage/testkit/runner/impl/IndividualTestRunner.scala:34 — IndividualTestRunnerImpl.proceedTest has cognitive complexity 27 (threshold 15). Drivers by points: loops 7 (25 pts), boolean chains 2 (nesting depth added 18). 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 · TypeUtil.isAssignableFrom (cognitive 26) · ×1
  • TypeUtil.isAssignableFrom (cognitive 26) fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/reflection/TypeUtil.scala:7 — TypeUtil.isAssignableFrom has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 16, if/else 10. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · ProxyStrategyDefaultImplPlatformSpecific.makeCogenProxy (cognitive 25) · ×1
  • ProxyStrategyDefaultImplPlatformSpecific.makeCogenProxy (cognitive 25) distage/distage-core/.jvm/src/main/scala/izumi/distage/provisioning/strategies/ProxyStrategyDefaultImplPlatformSpecific.scala:18 — ProxyStrategyDefaultImplPlatformSpecific.makeCogenProxy has cognitive complexity 25 (threshold 15). Drivers by points: loops 5 (14 pts), if/else 5 (7 pts), match/switch 1 (4 pts) (nesting depth added 14). 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 · Toposort.cycleBreaking (cognitive 25) · ×1
  • Toposort.cycleBreaking (cognitive 25) fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/graphs/tools/Toposort.scala:15 — Toposort.cycleBreaking has cognitive complexity 25 (threshold 15). Drivers by points: loops 3 (12 pts), if/else 6 (10 pts), match/switch 1 (3 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.
D2 · Cognitive Complexity · ConstructorMacrosBase.mkNewAbstractTypeInstanceApplyExpr (cognitive 23) · ×1
  • ConstructorMacrosBase.mkNewAbstractTypeInstanceApplyExpr (cognitive 23) distage/distage-core-api/src/main/scala-2/izumi/distage/reflection/macros/constructors/ConstructorMacros.scala:237 — ConstructorMacrosBase.mkNewAbstractTypeInstanceApplyExpr has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (12 pts), match/switch 3 (8 pts), boolean chains 3 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · Impl.format (cognitive 23) · ×1
  • Impl.format (cognitive 23) distage/distage-core-api/src/main/scala/izumi/distage/model/plan/repr/OpFormatter.scala:48 — Impl.format has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (15 pts), match/switch 4 (8 pts) (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · runtime.checkAppParsed (cognitive 23) · ×1
  • runtime.checkAppParsed (cognitive 23) distage/distage-framework/src/main/scala/izumi/distage/framework/PlanCheck.scala:116 — runtime.checkAppParsed has cognitive complexity 23 (threshold 15). Drivers by points: if/else 19 (20 pts), match/switch 2, error handling 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · GlobParser.globToRegex (cognitive 21) · ×1
  • GlobParser.globToRegex (cognitive 21) fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/resources/GlobParser.scala:82 — GlobParser.globToRegex has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ContainerResource.await (cognitive 20) · ×1
  • ContainerResource.await (cognitive 20) distage/distage-framework-docker/src/main/scala/izumi/distage/docker/impl/ContainerResource.scala:129 — ContainerResource.await has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (11 pts), match/switch 3 (9 pts) (nesting depth added 13). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · MakeMacro.makeMethodImpl (cognitive 19) · ×1
  • MakeMacro.makeMethodImpl (cognitive 19) distage/distage-core-api/src/main/scala-3/izumi/distage/constructors/MakeMacro.scala:44 — MakeMacro.makeMethodImpl has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (12 pts), error handling 2 (4 pts), boolean chains 2, match/switch 1 (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · GraphDumpObserver.modify (cognitive 19) · ×1
  • GraphDumpObserver.modify (cognitive 19) distage/distage-core/.jvm/src/main/scala/izumi/distage/planning/extensions/GraphDumpObserver.scala:124 — GraphDumpObserver.modify has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 5 (11 pts), if/else 3 (8 pts) (nesting depth added 11). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · TagStyler.parseSinglePart (cognitive 19) · ×1
  • TagStyler.parseSinglePart (cognitive 19) logstage/logstage-core/src/main/scala/izumi/logstage/api/rendering/logunits/TagStyler.scala:31 — TagStyler.parseSinglePart has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (15 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Default.verify (cognitive 18) · ×1
  • Default.verify (cognitive 18) distage/distage-core/src/main/scala/izumi/distage/provisioning/ProvisionOperationVerifier.scala:20 — Default.verify has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (9 pts), match/switch 2 (5 pts), loops 2 (3 pts), boolean chains 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 · LogstageReprWriter.translate (cognitive 18) · ×1
  • LogstageReprWriter.translate (cognitive 18) logstage/logstage-core/src/main/scala/izumi/logstage/api/rendering/LogstageReprWriter.scala:10 — LogstageReprWriter.translate has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 4 (8 pts), if/else 4 (6 pts), loops 2 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LogstageCirceWriter.translate (cognitive 18) · ×1
  • LogstageCirceWriter.translate (cognitive 18) logstage/logstage-rendering-circe/src/main/scala/izumi/logstage/api/rendering/json/LogstageCirceWriter.scala:11 — LogstageCirceWriter.translate has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 4 (8 pts), if/else 4 (6 pts), loops 2 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ProvisioningFailureOps.render (cognitive 17) · ×1
  • ProvisioningFailureOps.render (cognitive 17) distage/distage-core-api/src/main/scala/izumi/distage/model/provisioning/PlanInterpreter.scala:97 — ProvisioningFailureOps.render has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 5 (11 pts), if/else 4 (6 pts) (nesting depth added 8). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · ForwardingRefResolverDefaultImpl.resolveMatrix (cognitive 17) · ×1
  • ForwardingRefResolverDefaultImpl.resolveMatrix (cognitive 17) distage/distage-core/src/main/scala/izumi/distage/planning/sequential/ForwardingRefResolverDefaultImpl.scala:112 — ForwardingRefResolverDefaultImpl.resolveMatrix has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (7 pts), loops 3 (5 pts), match/switch 2 (5 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 · PlanCheckMaterializer.materializeImpl (cognitive 17) · ×1
  • PlanCheckMaterializer.materializeImpl (cognitive 17) distage/distage-framework/src/main/scala-3/izumi/distage/framework/PlanCheckMaterializer.scala:67 — PlanCheckMaterializer.materializeImpl has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), error handling 1 (3 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.
D2 · Cognitive Complexity · WeakAsyncForMiniBIOAsync.parTraverseN_ (cognitive 17) · ×1
  • WeakAsyncForMiniBIOAsync.parTraverseN_ (cognitive 17) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIOAsync.scala:440 — WeakAsyncForMiniBIOAsync.parTraverseN_ has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 4 (10 pts), if/else 6 (7 pts) (nesting depth added 7). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · GraphVizDotML.source (cognitive 17) · ×1
  • GraphVizDotML.source (cognitive 17) fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/graphs/dotml/GraphVizDotML.scala:122 — GraphVizDotML.source has cognitive complexity 17 (threshold 15). Drivers by points: if/else 16, boolean chains 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · CycleEraser.run (cognitive 17) · ×1
  • CycleEraser.run (cognitive 17) fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/graphs/tools/cycles/CycleEraser.scala:13 — CycleEraser.run has cognitive complexity 17 (threshold 15). Drivers by points: loops 3 (12 pts), if/else 4 (5 pts) (nesting depth added 10). 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 · FriendlyAnnoTools.makeFriendly (cognitive 17) · ×1
  • FriendlyAnnoTools.makeFriendly (cognitive 17) fundamentals/fundamentals-functoid/src/main/scala-2/izumi/distage/reflection/macros/universe/basicuniverse/FriendlyAnnoTools.scala:21 — FriendlyAnnoTools.makeFriendly has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 5 (11 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 · CirceToolMacro.handleNonGeneric (cognitive 17) · ×1
  • CirceToolMacro.handleNonGeneric (cognitive 17) fundamentals/fundamentals-json-circe/src/main/scala-2/izumi/fundamentals/json/circe/CirceTool.scala:79 — CirceToolMacro.handleNonGeneric has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 2 (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 · JsonFlattener.inflateParsed (cognitive 17) · ×1
  • JsonFlattener.inflateParsed (cognitive 17) fundamentals/fundamentals-json-circe/src/main/scala/izumi/fundamentals/json/flat/JsonFlattener.scala:174 — JsonFlattener.inflateParsed has cognitive complexity 17 (threshold 15). Drivers by points: loops 4 (11 pts), if/else 3 (4 pts), boolean chains 1, match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · TypeUtil.defaultValue (cognitive 17) · ×1
  • TypeUtil.defaultValue (cognitive 17) fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/reflection/TypeUtil.scala:33 — TypeUtil.defaultValue has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, boolean chains 8. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · PlannerDefaultImpl.preparePlan (cognitive 16) · ×1
  • PlannerDefaultImpl.preparePlan (cognitive 16) distage/distage-core/src/main/scala/izumi/distage/planning/PlannerDefaultImpl.scala:48 — PlannerDefaultImpl.preparePlan has cognitive complexity 16 (threshold 15). Drivers by points: loops 6 (13 pts), match/switch 1 (3 pts) (nesting depth added 9). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · ProxyStrategyDefaultImpl.makeProxy (cognitive 16) · ×1
  • ProxyStrategyDefaultImpl.makeProxy (cognitive 16) distage/distage-core/src/main/scala/izumi/distage/provisioning/strategies/ProxyStrategyDefaultImpl.scala:28 — ProxyStrategyDefaultImpl.makeProxy has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 4 (6 pts) (nesting depth added 8). 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 · ContainerResource.findAcceptableCandidate (cognitive 16) · ×1
  • ContainerResource.findAcceptableCandidate (cognitive 16) distage/distage-framework-docker/src/main/scala/izumi/distage/docker/impl/ContainerResource.scala:262 — ContainerResource.findAcceptableCandidate has cognitive complexity 16 (threshold 15). Drivers by points: loops 3 (6 pts), if/else 3 (5 pts), match/switch 2 (4 pts), boolean chains 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 · MiniBIO.run (cognitive 16) · ×1
  • MiniBIO.run (cognitive 16) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIO.scala:35 — MiniBIO.run has cognitive complexity 16 (threshold 15). Drivers by points: error handling 3 (8 pts), match/switch 4 (8 pts) (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D3 · God Classes · FileTooLong · ×1
  • FileTooLong: sbtgen/Deps.scala sbtgen/Deps.scala — FileTooLong — 731 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 231 over it, 1.46× 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.
D35 · Change Coupling · Change coupling · ×1
  • Change coupling: ScalatestLinearizedTestReporter.scala ↔ DistageScalatestReporter.scala distage/distage-testkit-scalatest/src/main/scala/izumi/distage/testkit/services/scalatest/dstest/ScalatestLinearizedTestReporter.scala:1 — `distage/distage-testkit-scalatest/src/main/scala/izumi/distage/testkit/services/scalatest/dstest/ScalatestLinearizedTestReporter.scala` and `distage/distage-testkit-scalatest/src/main/scala/org/scalatest/distage/DistageScalatestReporter.scala` change together 53% of the time (8 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `e6f18f6b` distage-testkit: Fix 1.3 series regression, wrong test count and test…; `e49227b3` Feature/memoization levels (#1251) (at that commit the file was still `distage/distage-testkit-scalatest/src/main/scala/izumi/distage/testkit/services/scalatest/dstest/SafeTestReporter.scala`); `eb836739` distage-testkit-scalatest: Fix compatibility with Scalatest matchers … (at that commit the file was still `distage/distage-testkit-scalatest/src/main/scala/izumi/distage/testkit/services/scalatest/dstest/SafeTestReporter.scala`) — run `git show` on any of them.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Edited copy of a member (32 corresponding lines) · ×1
  • Edited copy of a member (32 corresponding lines) fundamentals/fundamentals-bio/.js/src/main/scala/izumi/functional/quasi/__QuasiAsyncPlatformSpecific.scala:9 — fundamentals/fundamentals-bio/.js/src/main/scala/izumi/functional/quasi/__QuasiAsyncPlatformSpecific.scala:9-42 | fundamentals/fundamentals-bio/.jvm/src/main/scala/izumi/functional/quasi/__QuasiAsyncPlatformSpecific.scala:21-52 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (46 corresponding lines) · ×1
  • Edited copy of a member (46 corresponding lines) logstage/logstage-core/src/main/scala/izumi/logstage/api/rendering/LogstageReprWriter.scala:10 — logstage/logstage-core/src/main/scala/izumi/logstage/api/rendering/LogstageReprWriter.scala:10-59 | logstage/logstage-rendering-circe/src/main/scala/izumi/logstage/api/rendering/json/LogstageCirceWriter.scala:11-56 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (39 corresponding lines) · ×1
  • Edited copy of a member (39 corresponding lines) logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/ArgumentNameExtractionMacro.scala:99 — logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/ArgumentNameExtractionMacro.scala:99-137 | logstage/logstage-core/src/main/scala-3/izumi/logstage/macros/ArgumentNameExtractionMacro.scala:98-136 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 19+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 19+ corresponding lines) logstage/logstage-core/src/main/scala/logstage/LogIO.scala:41 — logstage/logstage-core/src/main/scala/logstage/LogIO.scala:41-59 | logstage/logstage-core/src/main/scala/logstage/LogIO.scala:61-79 | logstage/logstage-core/src/main/scala/logstage/strict/LogIOStrict.scala:40-58 | logstage/logstage-core/src/main/scala/logstage/strict/LogIOStrict.scala:60-78 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (26 corresponding lines) · ×1
  • Edited copy of a member (26 corresponding lines) fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/graphs/tools/random/RandomGraph.scala:10 — fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/graphs/tools/random/RandomGraph.scala:10-35 | fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/graphs/tools/random/RandomGraph.scala:37-63 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 11+ corresponding lines) logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LogIOMacroMethods.scala:77 — logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LogIOMacroMethods.scala:77-90 | logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LogIOMacroMethods.scala:96-109 | logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LoggerMacroMethods.scala:72-82 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 10+ corresponding lines) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/retry/RetryPolicy.scala:72 — fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/retry/RetryPolicy.scala:72-82 | fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/retry/RetryPolicy.scala:84-95 | fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/retry/RetryPolicy.scala:97-106 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×1
  • Edited copy of a member (14 corresponding lines) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/BioEither.scala:53 — fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/BioEither.scala:53-66 | fundamentals/fundamentals-collections/src/main/scala/izumi/functional/IzEither.scala:236-249 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×1
  • Edited copy of a member (17 corresponding lines) fundamentals/fundamentals-platform/.jvm/src/main/scala/izumi/fundamentals/platform/files/RecursiveFileRemovals.scala:8 — fundamentals/fundamentals-platform/.jvm/src/main/scala/izumi/fundamentals/platform/files/RecursiveFileRemovals.scala:8-24 | fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/resources/IzResources.scala:238-254 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 15+ corresponding lines) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/BioEither.scala:68 — fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/BioEither.scala:68-82 | fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/BioEither.scala:84-98 | fundamentals/fundamentals-collections/src/main/scala/izumi/functional/IzEither.scala:219-233 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 12+ corresponding lines) distage/distage-testkit-scalatest/src/main/scala-2/izumi/distage/testkit/scalatest/AssertCIO.scala:66 — distage/distage-testkit-scalatest/src/main/scala-2/izumi/distage/testkit/scalatest/AssertCIO.scala:66-77 | distage/distage-testkit-scalatest/src/main/scala-2/izumi/distage/testkit/scalatest/AssertIO2.scala:57-71 | distage/distage-testkit-scalatest/src/main/scala-2/izumi/distage/testkit/scalatest/AssertIO2.scala:81-96 | distage/distage-testkit-scalatest/src/main/scala-2/izumi/distage/testkit/scalatest/AssertSync.scala:58-72 | distage/distage-testkit-scalatest/src/main/scala-2/izumi/distage/testkit/scalatest/AssertSync.scala:82-98 | distage/distage-testkit-scalatest/src/main/scala-2/izumi/distage/testkit/scalatest/AssertZIO.scala:76-88 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×1
  • Edited copy of a member (13 corresponding lines) doc/microsite/src/main/scala/microsite/FakePackageModifier.scala:7 — doc/microsite/src/main/scala/microsite/FakePackageModifier.scala:7-19 | doc/microsite/src/main/scala/microsite/HackOverrideModifier.scala:7-19 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×1
  • Edited copy of a member (7 corresponding lines) distage/distage-extension-config/.jvm/src/main/scala-3/izumi/distage/config/codec/MetaInstances.scala:93 — distage/distage-extension-config/.jvm/src/main/scala-3/izumi/distage/config/codec/MetaInstances.scala:93-99 | distage/distage-extension-config/.jvm/src/main/scala-3/izumi/distage/config/codec/PureconfigInstances.scala:181-187 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×1
  • Edited copy of a member (8 corresponding lines) distage/distage-framework/.js/src/main/scala/izumi/distage/roles/launcher/PreparedAppSyntaxPlatformSpecific.scala:7 — distage/distage-framework/.js/src/main/scala/izumi/distage/roles/launcher/PreparedAppSyntaxPlatformSpecific.scala:7-14 | distage/distage-framework/.jvm/src/main/scala/izumi/distage/roles/launcher/PreparedAppSyntaxPlatformSpecific.scala:5-12 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIO.scala:53 — fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIO.scala:53-71 | fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIOAsync.scala:60-78 — before extracting anything, compare `fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIO.scala` and `fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIOAsync.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIO.scala:53` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `Fail` names `izumi.functional.bio.impl.MiniBIO.Fail` in one and `izumi.functional.bio.impl.MiniBIOAsync.Fail` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (15 lines × 3) · ×1
  • Duplicated block (15 lines × 3) distage/distage-core/src/main/scala/izumi/distage/planning/sequential/ForwardingRefResolverDefaultImpl.scala:186 — distage/distage-core/src/main/scala/izumi/distage/planning/sequential/ForwardingRefResolverDefaultImpl.scala:186-200 | fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/graphs/tools/Toposort.scala:53-67 | fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/graphs/tools/ToposortLoopBreaker.scala:45-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (12–14 lines × 2) · ×1
  • Duplicated block (12–14 lines × 2) logstage/logstage-core/src/main/scala/izumi/logstage/api/rendering/LogstageReprWriter.scala:18 — logstage/logstage-core/src/main/scala/izumi/logstage/api/rendering/LogstageReprWriter.scala:18-31 | logstage/logstage-rendering-circe/src/main/scala/izumi/logstage/api/rendering/json/LogstageCirceWriter.scala:18-29 — 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 `logstage/logstage-core/src/main/scala/izumi/logstage/api/rendering/LogstageReprWriter.scala:18` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `Token` names `izumi.logstage.api.rendering.LogstageReprWriter.Token` in one and `izumi.logstage.api.rendering.json.LogstageCirceWriter.Token` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1
  • Duplicated block (13 lines × 2) distage/distage-testkit-core/.js/src/main/scala/izumi/distage/testkit/runner/impl/services/BootstrapFactory.scala:50 — distage/distage-testkit-core/.js/src/main/scala/izumi/distage/testkit/runner/impl/services/BootstrapFactory.scala:50-62 | distage/distage-testkit-core/.jvm/src/main/scala/izumi/distage/testkit/runner/impl/services/BootstrapFactory.scala:67-79 — 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. 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 (12 lines × 2) · ×1
  • Duplicated block (12 lines × 2) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIO.scala:79 — fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIO.scala:79-90 | fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIOAsync.scala:87-98 — before extracting anything, compare `fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIO.scala` and `fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIOAsync.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/impl/MiniBIO.scala:79` 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 (8–9 lines × 2) · ×1
  • Duplicated block (8–9 lines × 2) fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/graphs/tools/random/RandomGraph.scala:11 — fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/graphs/tools/random/RandomGraph.scala:11-18 | fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/graphs/tools/random/RandomGraph.scala:38-46 — 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 `fundamentals/fundamentals-collections/src/main/scala/izumi/fundamentals/graphs/tools/random/RandomGraph.scala:11` 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 × 2) · ×1
  • Duplicated block (6–7 lines × 2) distage/distage-core-api/src/main/scala-3/izumi/distage/reflection/macros/IdExtractorImpl.scala:17 — distage/distage-core-api/src/main/scala-3/izumi/distage/reflection/macros/IdExtractorImpl.scala:17-22 | distage/distage-core-api/src/main/scala-3/izumi/distage/reflection/macros/IdExtractorImpl.scala:27-33 — 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 `distage/distage-core-api/src/main/scala-3/izumi/distage/reflection/macros/IdExtractorImpl.scala:17` 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: ConstructorUtil (LCOM4 8) distage/distage-core-api/src/main/scala-3/izumi/distage/constructors/ConstructorUtil.scala:118 — ConstructorUtil's methods fall into 8 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 8 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.
IC1 · Incompleteness & stubs · Empty method body · ×1
  • Empty method body — does nothing with its inputs fundamentals/fundamentals-language/src/main/scala/izumi/fundamentals/platform/language/Quirks.scala:28 — `forget` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
X3 · Exception handling · Swallowed exception (empty catch) · ×1
  • Swallowed exception (empty catch) distage/distage-framework/src/main/scala/izumi/distage/roles/launcher/AppShutdownStrategy.scala:123 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Minor — 27 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×11
  • Orphaned file logstage/logstage-core/src/main/scala-3/izumi/logstage/macros/LogMethodMacro.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/retry/RetryPolicy.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LogMethodMacro.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file fundamentals/fundamentals-functoid/src/main/scala-3/izumi/distage/reflection/macros/DummyImplicitsExtractorMacro.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file distage/distage-framework-docker/src/main/scala/izumi/distage/docker/healthcheck/PostgreSqlProtocolCheck.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file distage/distage-framework/src/main/scala/izumi/distage/framework/PlanCheckConfig.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file distage/distage-framework-docker/src/main/scala/izumi/distage/docker/bundled/KafkaDocker.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/reflection/TypeUtil.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file logstage/logstage-core/src/main/scala/izumi/logstage/api/rendering/logunits/TagStyler.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file distage/distage-core-api/src/main/scala-3/izumi/distage/reflection/macros/DischargeDummyMacro.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file logstage/logstage-core/src/main/scala-3/izumi/logstage/macros/LogValuesMacro.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
X10 · Duplicated predicate · Duplicated predicate · ×3
  • Duplicated predicate fundamentals/fundamentals-language/src/main/scala-2/izumi/fundamentals/platform/language/CodePositionMaterializer.scala:37 — `!name.startsWith("$") && !name.startsWith("<")` appears character-identically in 2 files — fundamentals/fundamentals-language/src/main/scala-2/izumi/fundamentals/platform/language/CodePositionMaterializer.scala, fundamentals/fundamentals-language/src/main/scala-3/izumi/fundamentals/platform/language/CodePositionMaterializer.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate distage/distage-core-api/src/main/scala/izumi/distage/model/plan/Plan.scala:166 — `op.effectHKTypeCtor != SafeType.identityEffectType && !(op.effectHKTypeCtor <:< effectType)` appears character-identically in 2 files — distage/distage-core-api/src/main/scala/izumi/distage/model/plan/Plan.scala, distage/distage-core/src/main/scala/izumi/distage/planning/solver/PlanVerifier.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate distage/distage-core-api/src/main/scala-2/izumi/distage/reflection/macros/universe/impl/WithDISymbolInfo.scala:113 — `tpe.typeSymbol.isClass && tpe.typeSymbol.asClass == u.definitions.ByNameParamClass` appears character-identically in 3 files — distage/distage-core-api/src/main/scala-2/izumi/distage/reflection/macros/universe/impl/WithDISymbolInfo.scala, fundamentals/fundamentals-functoid/src/main/scala-2/izumi/distage/reflection/macros/universe/basicuniverse/MacroSymbolInfoCompactImpl.scala, fundamentals/fundamentals-platform/src/main/scala-2/izumi/fundamentals/reflection/ReflectionUtil.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
AX6 · Interface segregation · Fat interface · ×2
  • Fat interface: Entropy1[F] (17 abstract members) fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/Entropy1.scala:13 — `Entropy1[F]` declares 17 abstract members under just 15 distinct name(s): `nextBoolean`, `nextInt`, `nextInt`, `nextLong`, `nextLong`, `nextFloat`, `nextDouble`, `nextGaussian`, `nextBytes`, `nextPrintableChar`, `nextString`, `nextTimeUUID`, `nextUUID`, `shuffle`, `withSeed`, `setSeed`, `writeRandomBytes`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 17 separate responsibilities: a caller binds to 15 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 17 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
  • Fat interface: IzUUID (17 abstract members) fundamentals/fundamentals-bio/src/main/scala/izumi/fundamentals/platform/uuid/IzUUID.scala:8 — `IzUUID` declares 17 abstract members under just 14 distinct name(s): `generateTimeUUID`, `generateTimeUUIDBytes`, `generateRandomUUID`, `getTimeUUID`, `getTimeUUIDFromMicros`, `getRandomTimeUUIDFromMicros`, `getTimeUUID`, `getTimeUUID`, `getUUID`, `decompose`, `minTimeUUID`, `maxTimeUUID`, `unixTimestamp`, `microsTimestamp`, `getTimeUUIDBytes`, `getTimeUUIDBytes`, `getAdjustedTimestamp`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 17 separate responsibilities: a caller binds to 14 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 17 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 14 significant file(s) lose their only recent owner: fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/syntax/Syntax2.scala, distage/distage-testkit-scalatest/src/main/scala/org/scalatest/distage/DistageScalatestTestSuiteRunner.scala, distage/distage-testkit-scalatest/src/main/scala/org/scalatest/distage/DistageScalatestReporter.scala, distage/distage-framework/src/main/scala/izumi/distage/roles/RoleAppBootModule.scala, distage/distage-testkit-scalatest/src/main/scala/izumi/distage/testkit/services/scalatest/dstest/ScalatestLinearizedTestReporter.scala, distage/distage-framework-docker/src/main/scala/izumi/distage/docker/ContainerNetworkDef.scala, distage/distage-core-api/src/main/scala-3/izumi/distage/constructors/MakeMacro.scala, distage/distage-framework/src/main/scala/izumi/distage/roles/launcher/RoleProvider.scala (+6 more). Pair on, review, or document these before any departure.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 2 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 (17 single-owned of 253 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 253 of the 789 production source files in this repository met that bar). They are anonymized user #2 (2 file(s)), anonymized user #3 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: logstage/logstage-core/src/main/scala/izumi/logstage/api/rendering/StringRenderingPolicy.scala, logstage/logstage-core/src/main/scala/izumi/logstage/api/logger/AbstractLogger.scala, fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/platform/resources/GlobParser.scala.
D21 · Naming Consistency · `TransZio` spells `Zio` where 21 names in the project spell it `ZIO` · ×1
  • `TransZio` spells `Zio` where 21 names in the project spell it `ZIO` fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/package.scala:137 — 21 of 22 names in project repository spell the token `ZIO` (21 of 22; unit: names in project repository containing `ZIO`). Peers: AdaptFunctoid.providerFromZIOScopedProvider (distage/distage-core-api/src/main/scala/izumi/distage/model/definition/dsl/LifecycleAdapters.scala:78); FunctoidLifecycleAdapters.providerFromZIOScoped (distage/distage-core-api/src/main/scala/izumi/distage/model/providers/FunctoidLifecycleAdapters.scala:47); FunctoidLifecycleAdapters.providerFromZIOScopedNothing (distage/distage-core-api/src/main/scala/izumi/distage/model/providers/FunctoidLifecycleAdapters.scala:59); LowPriorityDefaultModulesInstances1.forZIOPlusCats (distage/distage-core/src/main/scala/izumi/distage/modules/DefaultModule.scala:61); LowPriorityDefaultModulesInstances1.forZIOPlusCats(isZIO) (distage/distage-core/src/main/scala/izumi/distage/modules/DefaultModule.scala:61). Rename to `TransZIO`. [rule N6]
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 11 of 257 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 257 of the 789 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: logstage/logstage-core/src/main/scala-3/izumi/logstage/macros/LogMethodMacro.scala, fundamentals/fundamentals-bio/src/main/scala/izumi/functional/bio/retry/RetryPolicy.scala, logstage/logstage-core/src/main/scala-2/izumi/logstage/macros/LogMethodMacro.scala, fundamentals/fundamentals-functoid/src/main/scala-3/izumi/distage/reflection/macros/DummyImplicitsExtractorMacro.scala, distage/distage-framework-docker/src/main/scala/izumi/distage/docker/healthcheck/PostgreSqlProtocolCheck.scala, distage/distage-framework/src/main/scala/izumi/distage/framework/PlanCheckConfig.scala, distage/distage-framework-docker/src/main/scala/izumi/distage/docker/bundled/KafkaDocker.scala, fundamentals/fundamentals-platform/src/main/scala/izumi/fundamentals/reflection/TypeUtil.scala (and 3 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
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.
P10 · Library API & versioning · Implementation type on the public API · ×1
  • Implementation type on the public API logstage/logstage-adapter-slf4j/src/main/java/org/slf4j/impl/StaticLoggerBinder.java:7 — 4 public types in `org.slf4j.impl` are marked as implementation by their own namespace, folder or name: `StaticLoggerBinder` (logstage/logstage-adapter-slf4j/src/main/java/org/slf4j/impl/StaticLoggerBinder.java:7, `impl`), `StaticLoggerServiceProvider` (logstage/logstage-adapter-slf4j/src/main/java/org/slf4j/impl/StaticLoggerServiceProvider.java:11, `impl`), `StaticMDCBinder` (logstage/logstage-adapter-slf4j/src/main/java/org/slf4j/impl/StaticMDCBinder.java:7, `impl`), `StaticMarkerBinder` (logstage/logstage-adapter-slf4j/src/main/java/org/slf4j/impl/StaticMarkerBinder.java:7, `impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:9 — No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
X5 · Nullable reference types · Scala's null is not held to the type system everywhere · ×1
  • Scala's null is not held to the type system everywhere — No build over this repository's 786 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
Minor — 6 finding(s)
D12 · Dependency Hygiene · Outdated · ×6
  • Outdated: com.github.docker-java:docker-java-core — `com.github.docker-java %% docker-java-core` is declared at 3.6.0 in build.sbt, but 3.7.1 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 3.6.0 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.github.docker-java:docker-java-transport-zerodep — `com.github.docker-java %% docker-java-transport-zerodep` is declared at 3.6.0 in build.sbt, but 3.7.1 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 3.6.0 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.github.sbt:paradox-material-theme — `com.github.sbt %% paradox-material-theme` is declared at 0.7.0 in project/ParadoxMaterialTheme.scala, but 0.8.0 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 0.7.0 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: io.github.classgraph:classgraph — `io.github.classgraph %% classgraph` is declared at 4.8.181 in build.sbt, but 6.0.2 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 4.8.181 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: net.bytebuddy:byte-buddy — `net.bytebuddy %% byte-buddy` is declared at 1.17.7 in build.sbt, but 1.18.17 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.17.7 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: org.slf4j:slf4j-api — `org.slf4j %% slf4j-api` is declared at 2.0.17 in build.sbt, but 2.0.20 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.0.17 until the declaration is edited — there is no lockfile refresh that would move it.

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/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8cb36f9428ed4af38f697aba06ff641e/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/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8cb36f9428ed4af38f697aba06ff641e/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/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .18artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-49d39a72f5f340acb9f6708c3ae375850artifacts/raw/osv-scanner.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 51 file(s) — `distage/distage-core-api/src/main/scala-3/izumi/distage/constructors/ClassConstructorMacro.scala`, `distage/distage-core-api/src/main/scala-3/izumi/distage/constructors/MakeMacro.scala`, `distage/distage-core-api/src/main/scala-3/izumi/distage/reflection/macros/FunctoidMacro.scala`, `distage/distage-core-api/src/main/scala/izumi/distage/model/definition/ModuleBase.scala`, `distage/distage-core-api/src/main/scala/izumi/distage/model/definition/dsl/ModuleDefDSL.scala`, … (+46 more) — so the PII/GDPR sweep did not cover them at all.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress 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 Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-49d39a72f5f340acb9f6708c3ae375850artifacts/raw/osv-scanner.json

Run 01a1da88-da2f-78ed-a012-e7eb250997bf · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

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