Executive summary
scalacenter/scalafix falls short of our standard for production because we found no logging, tracing or health checks in the code. It scores 56 out of 100 and is rated Adequate, and 20 of its 22 critical findings are security problems in the build pipeline and in its automatic dependency updates.
Production Readiness, at 51, is the weakest lens and counts most in the score. The best first step is adding a diagnostic log, worth about 4 points. Recording design decisions comes next, worth about 3 points. Raising Production Readiness to 70 would lift the score to about 60.
Eighteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One automatic update takes new releases before a bad one can be spotted, and one secret can leak from the build pipeline. Pinning each tool to an exact version, setting a waiting period for automatic updates and limiting the secret to its own step would close these risks. The part of the code nobody has worked on for a long time needs someone to learn and document it before anyone changes it.
The product code is 19,330 lines, about €35,000 to rebuild.
If Production Readiness rose from 51 to 70, the lowest score rated Strong, the score would rise from 56 to about 60.
New since the last survey: 6 findings
- Knowledge Freshness · Orphaned knowledge scalafix-rules/src/main/scala-2/scalafix/internal/pc/ScalafixGlobal.scala
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 1 finding
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €35,000 · Estimate
| Cost to rebuild | €12,000 to €59,000, for 196 to 621 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 56. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 19,330 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 scala.meta.contrib | 2 scalafix.cli | 3 scalafix.config | 4 scalafix.v0.SemanticdbIndex | 5 scalafix.internal.diff | 6 scalafix.internal.symtab | 7 scalafix.util | 8 scalafix.v0.Signature | 9 scalafix.v1.RuleDecoder | 10 scalafix.internal.reflect | 11 scalafix.internal.util.TypeExtractors | 12 scalafix.rule | 13 scalafix | 14 scalafix.lint | 15 scalafix.internal.patch.PatchInternals | 16 scalafix.patch | 17 scalafix.internal.v1 | 18 scalafix.v1 | 19 scalafix.internal.patch | 20 scalafix.v0 | 21 scalafix.syntax | 22 scalafix.v0.Symbol | 23 scalafix.docs | 24 scalafix.internal.util.SymbolOps | 25 scalafix.patch.Patch.internal | 26 scalafix.internal.config | 27 scalafix.internal.config.ScalaVersion | 28 scalafix.internal.patch.EscapeHatch | 29 scalafix.internal.util.LintSyntax | 30 scalafix.internal.interfaces | 31 scalafix.internal.util | 32 scalafix.internal.v0 | 33 scalafix.v0.Rule | 34 scalafix.internal.util.Failure | 35 scalafix.internal.util.QualifyStrategy | 36 scala.meta.internal.pc | 37 scala.meta.internal.pc.ScalafixGlobal | 38 scalafix.internal.pc | 39 scalafix.internal.util.PrettyType | 40 scalafix.internal.rule |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 scala.meta.contrib | ||||||||||||||||||||||||||||||||||||||||
| 2 scalafix.cli | ||||||||||||||||||||||||||||||||||||||||
| 3 scalafix.config | ||||||||||||||||||||||||||||||||||||||||
| 4 scalafix.v0.SemanticdbIndex | ||||||||||||||||||||||||||||||||||||||||
| 5 scalafix.internal.diff | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 scalafix.internal.symtab | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 scalafix.util | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 8 scalafix.v0.Signature | 7 | |||||||||||||||||||||||||||||||||||||||
| 9 scalafix.v1.RuleDecoder | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 10 scalafix.internal.reflect | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 11 scalafix.internal.util.TypeExtractors | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 scalafix.rule | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 scalafix | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 14 scalafix.lint | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 scalafix.internal.patch.PatchInternals | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 scalafix.patch | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 17 scalafix.internal.v1 | 1 | 1 | 2 | 3 | 2 | 1 | 1 | 1 | 4 | 2 | 11 | 1 | 6 | 7 | 2 | 1 | ||||||||||||||||||||||||
| 18 scalafix.v1 | 2 | 1 | 13 | 4 | 1 | 1 | 1 | 1 | 3 | 11 | 2 | |||||||||||||||||||||||||||||
| 19 scalafix.internal.patch | 2 | 2 | 1 | 1 | 1 | 2 | 11 | 1 | 3 | 5 | 1 | |||||||||||||||||||||||||||||
| 20 scalafix.v0 | 1 | 4 | 2 | 3 | 5 | 1 | 1 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||
| 21 scalafix.syntax | 2 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 22 scalafix.v0.Symbol | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 scalafix.docs | 1 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 24 scalafix.internal.util.SymbolOps | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 scalafix.patch.Patch.internal | 2 | 1 | 1 | 6 | ||||||||||||||||||||||||||||||||||||
| 26 scalafix.internal.config | 1 | 5 | 3 | 2 | ||||||||||||||||||||||||||||||||||||
| 27 scalafix.internal.config.ScalaVersion | 5 | |||||||||||||||||||||||||||||||||||||||
| 28 scalafix.internal.patch.EscapeHatch | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 scalafix.internal.util.LintSyntax | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 scalafix.internal.interfaces | 3 | 3 | 2 | 4 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 31 scalafix.internal.util | 3 | 1 | 2 | 6 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 32 scalafix.internal.v0 | 2 | 2 | 2 | 1 | 9 | 3 | 24 | 3 | ||||||||||||||||||||||||||||||||
| 33 scalafix.v0.Rule | 1 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 34 scalafix.internal.util.Failure | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 35 scalafix.internal.util.QualifyStrategy | 3 | |||||||||||||||||||||||||||||||||||||||
| 36 scala.meta.internal.pc | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 scala.meta.internal.pc.ScalafixGlobal | 3 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 38 scalafix.internal.pc | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 scalafix.internal.util.PrettyType | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 scalafix.internal.rule | 4 | 1 | 2 | 4 | 6 | 23 | 2 | 12 | 1 | 14 | 3 | 1 |
5→31 scalafix.internal.diff uses scalafix.internal.util part of a loop✕
- Connections
- 1 pair of types, where a type in scalafix.internal.diff uses a type in scalafix.internal.util.
- The types involved
scalafix.internal.diff.FullDiffDisable→scalafix.internal.util.IntervalSet
- Direction
- scalafix.internal.diff uses scalafix.internal.util, so a change to scalafix.internal.util can break scalafix.internal.diff, while a change to scalafix.internal.diff can't break scalafix.internal.util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→18 scalafix.internal.symtab uses scalafix.v1 part of a loop✕
- Connections
- 1 pair of types, where a type in scalafix.internal.symtab uses a type in scalafix.v1.
- The types involved
scalafix.internal.symtab.SymbolTable→scalafix.v1.SymbolInformation
- Direction
- scalafix.internal.symtab uses scalafix.v1, so a change to scalafix.v1 can break scalafix.internal.symtab, while a change to scalafix.internal.symtab can't break scalafix.v1.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→4 scalafix.util uses scalafix.v0.SemanticdbIndex✕
- Connections
- 1 pair of types, where a type in scalafix.util uses a type in scalafix.v0.SemanticdbIndex.
- The types involved
scalafix.util.TreeOps→scalafix.v0.SemanticdbIndex.Symbol
- Direction
- scalafix.util uses scalafix.v0.SemanticdbIndex, so a change to scalafix.v0.SemanticdbIndex can break scalafix.util, while a change to scalafix.util can't break scalafix.v0.SemanticdbIndex.
- Position
- Below the diagonal: scalafix.util uses a module listed above it, which is the healthy direction.
7→35 scalafix.util uses scalafix.internal.util.QualifyStrategy part of a loop✕
- Connections
- 1 pair of types, where a type in scalafix.util uses a type in scalafix.internal.util.QualifyStrategy.
- The types involved
scalafix.util.TreeOps→scalafix.internal.util.QualifyStrategy.Name
- Direction
- scalafix.util uses scalafix.internal.util.QualifyStrategy, so a change to scalafix.internal.util.QualifyStrategy can break scalafix.util, while a change to scalafix.util can't break scalafix.internal.util.QualifyStrategy.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→20 scalafix.v0.Signature uses scalafix.v0 part of a loop✕
- Connections
- 7 pairs of types, where a type in scalafix.v0.Signature uses a type in scalafix.v0.
- The types involved
scalafix.v0.Signature.Method→scalafix.v0.Signaturescalafix.v0.Signature.Package→scalafix.v0.Signaturescalafix.v0.Signature.Self→scalafix.v0.Signaturescalafix.v0.Signature.Term→scalafix.v0.Signaturescalafix.v0.Signature.TermParameter→scalafix.v0.Signaturescalafix.v0.Signature.Type→scalafix.v0.Signaturescalafix.v0.Signature.TypeParameter→scalafix.v0.Signature
- Direction
- scalafix.v0.Signature uses scalafix.v0, so a change to scalafix.v0 can break scalafix.v0.Signature, while a change to scalafix.v0.Signature can't break scalafix.v0.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→10 scalafix.v1.RuleDecoder uses scalafix.internal.reflect part of a loop✕
- Connections
- 1 pair of types, where a type in scalafix.v1.RuleDecoder uses a type in scalafix.internal.reflect.
- The types involved
scalafix.v1.RuleDecoder.Settings→scalafix.internal.reflect.ScalafixToolbox
- Direction
- scalafix.v1.RuleDecoder uses scalafix.internal.reflect, so a change to scalafix.internal.reflect can break scalafix.v1.RuleDecoder, while a change to scalafix.v1.RuleDecoder can't break scalafix.internal.reflect.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→26 scalafix.v1.RuleDecoder uses scalafix.internal.config part of a loop✕
- Connections
- 2 pairs of types, where a type in scalafix.v1.RuleDecoder uses a type in scalafix.internal.config.
- The types involved
scalafix.v1.RuleDecoder.Settings→scalafix.internal.config.ScalafixConfigscalafix.v1.RuleDecoder.Settings→scalafix.internal.config.ScalafixReporter
- Direction
- scalafix.v1.RuleDecoder uses scalafix.internal.config, so a change to scalafix.internal.config can break scalafix.v1.RuleDecoder, while a change to scalafix.v1.RuleDecoder can't break scalafix.internal.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→27 scalafix.v1.RuleDecoder uses scalafix.internal.config.ScalaVersion part of a loop✕
- Connections
- 1 pair of types, where a type in scalafix.v1.RuleDecoder uses a type in scalafix.internal.config.ScalaVersion.
- The types involved
scalafix.v1.RuleDecoder.Settings→scalafix.internal.config.ScalaVersion.Patch
- Direction
- scalafix.v1.RuleDecoder uses scalafix.internal.config.ScalaVersion, so a change to scalafix.internal.config.ScalaVersion can break scalafix.v1.RuleDecoder, while a change to scalafix.v1.RuleDecoder can't break scalafix.internal.config.ScalaVersion.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→6 scalafix.internal.reflect uses scalafix.internal.symtab✕
- Connections
- 1 pair of types, where a type in scalafix.internal.reflect uses a type in scalafix.internal.symtab.
- The types involved
scalafix.internal.reflect.ClasspathOps→scalafix.internal.symtab.SymbolTable
- Direction
- scalafix.internal.reflect uses scalafix.internal.symtab, so a change to scalafix.internal.symtab can break scalafix.internal.reflect, while a change to scalafix.internal.reflect can't break scalafix.internal.symtab.
- Position
- Below the diagonal: scalafix.internal.reflect uses a module listed above it, which is the healthy direction.
10→9 scalafix.internal.reflect uses scalafix.v1.RuleDecoder✕
- Connections
- 1 pair of types, where a type in scalafix.internal.reflect uses a type in scalafix.v1.RuleDecoder.
- The types involved
scalafix.internal.reflect.CompilerSetup→scalafix.v1.RuleDecoder.Settings
- Direction
- scalafix.internal.reflect uses scalafix.v1.RuleDecoder, so a change to scalafix.v1.RuleDecoder can break scalafix.internal.reflect, while a change to scalafix.internal.reflect can't break scalafix.v1.RuleDecoder.
- Position
- Below the diagonal: scalafix.internal.reflect uses a module listed above it, which is the healthy direction.
10→20 scalafix.internal.reflect uses scalafix.v0 part of a loop✕
- Connections
- 2 pairs of types, where a type in scalafix.internal.reflect uses a type in scalafix.v0.
- The types involved
scalafix.internal.reflect.RuleDecoderOps→scalafix.v0.Rulescalafix.internal.reflect.RuleDecoderOps→scalafix.v0.SemanticRule
- Direction
- scalafix.internal.reflect uses scalafix.v0, so a change to scalafix.v0 can break scalafix.internal.reflect, while a change to scalafix.internal.reflect can't break scalafix.v0.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→8 scalafix.internal.util.TypeExtractors uses scalafix.v0.Signature✕
- Connections
- 1 pair of types, where a type in scalafix.internal.util.TypeExtractors uses a type in scalafix.v0.Signature.
- The types involved
scalafix.internal.util.TypeExtractors.TypeRefExtractor→scalafix.v0.Signature.Type
- Direction
- scalafix.internal.util.TypeExtractors uses scalafix.v0.Signature, so a change to scalafix.v0.Signature can break scalafix.internal.util.TypeExtractors, while a change to scalafix.internal.util.TypeExtractors can't break scalafix.v0.Signature.
- Position
- Below the diagonal: scalafix.internal.util.TypeExtractors uses a module listed above it, which is the healthy direction.
12→7 scalafix.rule uses scalafix.util✕
- Connections
- 1 pair of types, where a type in scalafix.rule uses a type in scalafix.util.
- The types involved
scalafix.rule.RuleIdentifier→scalafix.util.Deprecated
- Direction
- scalafix.rule uses scalafix.util, so a change to scalafix.util can break scalafix.rule, while a change to scalafix.rule can't break scalafix.util.
- Position
- Below the diagonal: scalafix.rule uses a module listed above it, which is the healthy direction.
12→26 scalafix.rule uses scalafix.internal.config part of a loop✕
- Connections
- 1 pair of types, where a type in scalafix.rule uses a type in scalafix.internal.config.
- The types involved
scalafix.rule.RuleName→scalafix.internal.config.ScalafixReporter
- Direction
- scalafix.rule uses scalafix.internal.config, so a change to scalafix.internal.config can break scalafix.rule, while a change to scalafix.rule can't break scalafix.internal.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→7 scalafix uses scalafix.util✕
- Connections
- 2 pairs of types, where a type in scalafix uses a type in scalafix.util.
- The types involved
scalafix.v0→scalafix.util.Apiscalafix.v1→scalafix.util.Api
- Direction
- scalafix uses scalafix.util, so a change to scalafix.util can break scalafix, while a change to scalafix can't break scalafix.util.
- Position
- Below the diagonal: scalafix uses a module listed above it, which is the healthy direction.
13→9 scalafix uses scalafix.v1.RuleDecoder✕
- Connections
- 1 pair of types, where a type in scalafix uses a type in scalafix.v1.RuleDecoder.
- The types involved
scalafix.website→scalafix.v1.RuleDecoder.Settings
- Direction
- scalafix uses scalafix.v1.RuleDecoder, so a change to scalafix.v1.RuleDecoder can break scalafix, while a change to scalafix can't break scalafix.v1.RuleDecoder.
- Position
- Below the diagonal: scalafix uses a module listed above it, which is the healthy direction.
13→11 scalafix uses scalafix.internal.util.TypeExtractors✕
- Connections
- 1 pair of types, where a type in scalafix uses a type in scalafix.internal.util.TypeExtractors.
- The types involved
scalafix.website→scalafix.internal.util.TypeExtractors.Any
- Direction
- scalafix uses scalafix.internal.util.TypeExtractors, so a change to scalafix.internal.util.TypeExtractors can break scalafix, while a change to scalafix can't break scalafix.internal.util.TypeExtractors.
- Position
- Below the diagonal: scalafix uses a module listed above it, which is the healthy direction.
14→12 scalafix.lint uses scalafix.rule✕
- Connections
- 1 pair of types, where a type in scalafix.lint uses a type in scalafix.rule.
- The types involved
scalafix.lint.RuleDiagnostic→scalafix.rule.RuleName
- Direction
- scalafix.lint uses scalafix.rule, so a change to scalafix.rule can break scalafix.lint, while a change to scalafix.lint can't break scalafix.rule.
- Position
- Below the diagonal: scalafix.lint uses a module listed above it, which is the healthy direction.
15→14 scalafix.internal.patch.PatchInternals uses scalafix.lint✕
- Connections
- 1 pair of types, where a type in scalafix.internal.patch.PatchInternals uses a type in scalafix.lint.
- The types involved
scalafix.internal.patch.PatchInternals.ResultWithContext→scalafix.lint.RuleDiagnostic
- Direction
- scalafix.internal.patch.PatchInternals uses scalafix.lint, so a change to scalafix.lint can break scalafix.internal.patch.PatchInternals, while a change to scalafix.internal.patch.PatchInternals can't break scalafix.lint.
- Position
- Below the diagonal: scalafix.internal.patch.PatchInternals uses a module listed above it, which is the healthy direction.
15→20 scalafix.internal.patch.PatchInternals uses scalafix.v0 part of a loop✕
- Connections
- 2 pairs of types, where a type in scalafix.internal.patch.PatchInternals uses a type in scalafix.v0.
- The types involved
scalafix.internal.patch.PatchInternals.ResultWithContext→scalafix.v0.RuleCtxscalafix.internal.patch.PatchInternals.ResultWithContext→scalafix.v0.SemanticdbIndex
- Direction
- scalafix.internal.patch.PatchInternals uses scalafix.v0, so a change to scalafix.v0 can break scalafix.internal.patch.PatchInternals, while a change to scalafix.internal.patch.PatchInternals can't break scalafix.v0.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→27 scalafix.internal.patch.PatchInternals uses scalafix.internal.config.ScalaVersion part of a loop✕
- Connections
- 1 pair of types, where a type in scalafix.internal.patch.PatchInternals uses a type in scalafix.internal.config.ScalaVersion.
- The types involved
scalafix.internal.patch.PatchInternals.ResultWithContext→scalafix.internal.config.ScalaVersion.Patch
- Direction
- scalafix.internal.patch.PatchInternals uses scalafix.internal.config.ScalaVersion, so a change to scalafix.internal.config.ScalaVersion can break scalafix.internal.patch.PatchInternals, while a change to scalafix.internal.patch.PatchInternals can't break scalafix.internal.config.ScalaVersion.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→4 scalafix.patch uses scalafix.v0.SemanticdbIndex✕
- Connections
- 1 pair of types, where a type in scalafix.patch uses a type in scalafix.v0.SemanticdbIndex.
- The types involved
scalafix.patch.PatchOps→scalafix.v0.SemanticdbIndex.Symbol
- Direction
- scalafix.patch uses scalafix.v0.SemanticdbIndex, so a change to scalafix.v0.SemanticdbIndex can break scalafix.patch, while a change to scalafix.patch can't break scalafix.v0.SemanticdbIndex.
- Position
- Below the diagonal: scalafix.patch uses a module listed above it, which is the healthy direction.
16→14 scalafix.patch uses scalafix.lint✕
- Connections
- 1 pair of types, where a type in scalafix.patch uses a type in scalafix.lint.
- The types involved
scalafix.patch.PatchOps→scalafix.lint.Diagnostic
- Direction
- scalafix.patch uses scalafix.lint, so a change to scalafix.lint can break scalafix.patch, while a change to scalafix.patch can't break scalafix.lint.
- Position
- Below the diagonal: scalafix.patch uses a module listed above it, which is the healthy direction.
16→20 scalafix.patch uses scalafix.v0 part of a loop✕
- Connections
- 1 pair of types, where a type in scalafix.patch uses a type in scalafix.v0.
- The types involved
scalafix.patch.PatchOps→scalafix.v0.SemanticdbIndex
- Direction
- scalafix.patch uses scalafix.v0, so a change to scalafix.v0 can break scalafix.patch, while a change to scalafix.patch can't break scalafix.v0.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→22 scalafix.patch uses scalafix.v0.Symbol part of a loop✕
- Connections
- 1 pair of types, where a type in scalafix.patch uses a type in scalafix.v0.Symbol.
- The types involved
scalafix.patch.PatchOps→scalafix.v0.Symbol.Global
- Direction
- scalafix.patch uses scalafix.v0.Symbol, so a change to scalafix.v0.Symbol can break scalafix.patch, while a change to scalafix.patch can't break scalafix.v0.Symbol.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→27 scalafix.patch uses scalafix.internal.config.ScalaVersion part of a loop✕
- Connections
- 2 pairs of types, where a type in scalafix.patch uses a type in scalafix.internal.config.ScalaVersion.
- The types involved
scalafix.patch.Patch→scalafix.internal.config.ScalaVersion.Patchscalafix.patch.PatchOps→scalafix.internal.config.ScalaVersion.Patch
- Direction
- scalafix.patch uses scalafix.internal.config.ScalaVersion, so a change to scalafix.internal.config.ScalaVersion can break scalafix.patch, while a change to scalafix.patch can't break scalafix.internal.config.ScalaVersion.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→2 scalafix.internal.v1 uses scalafix.cli✕
- Connections
- 1 pair of types, where a type in scalafix.internal.v1 uses a type in scalafix.cli.
- The types involved
scalafix.internal.v1.MainOps→scalafix.cli.ExitStatus
- Direction
- scalafix.internal.v1 uses scalafix.cli, so a change to scalafix.cli can break scalafix.internal.v1, while a change to scalafix.internal.v1 can't break scalafix.cli.
- Position
- Below the diagonal: scalafix.internal.v1 uses a module listed above it, which is the healthy direction.
17→4 scalafix.internal.v1 uses scalafix.v0.SemanticdbIndex✕
- Connections
- 1 pair of types, where a type in scalafix.internal.v1 uses a type in scalafix.v0.SemanticdbIndex.
- The types involved
scalafix.internal.v1.InternalSemanticDoc→scalafix.v0.SemanticdbIndex.Symbol
- Direction
- scalafix.internal.v1 uses scalafix.v0.SemanticdbIndex, so a change to scalafix.v0.SemanticdbIndex can break scalafix.internal.v1, while a change to scalafix.internal.v1 can't break scalafix.v0.SemanticdbIndex.
- Position
- Below the diagonal: scalafix.internal.v1 uses a module listed above it, which is the healthy direction.
17→5 scalafix.internal.v1 uses scalafix.internal.diff✕
- Connections
- 2 pairs of types, where a type in scalafix.internal.v1 uses a type in scalafix.internal.diff.
- The types involved
scalafix.internal.v1.Args→scalafix.internal.diff.DiffDisablescalafix.internal.v1.ValidatedArgs→scalafix.internal.diff.DiffDisable
- Direction
- scalafix.internal.v1 uses scalafix.internal.diff, so a change to scalafix.internal.diff can break scalafix.internal.v1, while a change to scalafix.internal.v1 can't break scalafix.internal.diff.
- Position
- Below the diagonal: scalafix.internal.v1 uses a module listed above it, which is the healthy direction.
17→6 scalafix.internal.v1 uses scalafix.internal.symtab✕
- Connections
- 3 pairs of types, where a type in scalafix.internal.v1 uses a type in scalafix.internal.symtab.
- The types involved
scalafix.internal.v1.Args→scalafix.internal.symtab.SymbolTablescalafix.internal.v1.InternalSemanticDoc→scalafix.internal.symtab.SymbolTablescalafix.internal.v1.ValidatedArgs→scalafix.internal.symtab.SymbolTable
- Direction
- scalafix.internal.v1 uses scalafix.internal.symtab, so a change to scalafix.internal.symtab can break scalafix.internal.v1, while a change to scalafix.internal.v1 can't break scalafix.internal.symtab.
- Position
- Below the diagonal: scalafix.internal.v1 uses a module listed above it, which is the healthy direction.
17→7 scalafix.internal.v1 uses scalafix.util✕
- Connections
- 2 pairs of types, where a type in scalafix.internal.v1 uses a type in scalafix.util.
- The types involved
scalafix.internal.v1.InternalDoc→scalafix.util.MatchingParensscalafix.internal.v1.InternalDoc→scalafix.util.TokenList
- Direction
- scalafix.internal.v1 uses scalafix.util, so a change to scalafix.util can break scalafix.internal.v1, while a change to scalafix.internal.v1 can't break scalafix.util.
- Position
- Below the diagonal: scalafix.internal.v1 uses a module listed above it, which is the healthy direction.
17→9 scalafix.internal.v1 uses scalafix.v1.RuleDecoder✕
- Connections
- 1 pair of types, where a type in scalafix.internal.v1 uses a type in scalafix.v1.RuleDecoder.
- The types involved
scalafix.internal.v1.Args→scalafix.v1.RuleDecoder.Settings
- Direction
- scalafix.internal.v1 uses scalafix.v1.RuleDecoder, so a change to scalafix.v1.RuleDecoder can break scalafix.internal.v1, while a change to scalafix.internal.v1 can't break scalafix.v1.RuleDecoder.
- Position
- Below the diagonal: scalafix.internal.v1 uses a module listed above it, which is the healthy direction.
17→10 scalafix.internal.v1 uses scalafix.internal.reflect✕
- Connections
- 1 pair of types, where a type in scalafix.internal.v1 uses a type in scalafix.internal.reflect.
- The types involved
scalafix.internal.v1.Args→scalafix.internal.reflect.ScalafixToolbox
- Direction
- scalafix.internal.v1 uses scalafix.internal.reflect, so a change to scalafix.internal.reflect can break scalafix.internal.v1, while a change to scalafix.internal.v1 can't break scalafix.internal.reflect.
- Position
- Below the diagonal: scalafix.internal.v1 uses a module listed above it, which is the healthy direction.
17→12 scalafix.internal.v1 uses scalafix.rule✕
- Connections
- 1 pair of types, where a type in scalafix.internal.v1 uses a type in scalafix.rule.
- The types involved
scalafix.internal.v1.Rules→scalafix.rule.RuleName
- Direction
- scalafix.internal.v1 uses scalafix.rule, so a change to scalafix.rule can break scalafix.internal.v1, while a change to scalafix.internal.v1 can't break scalafix.rule.
- Position
- Below the diagonal: scalafix.internal.v1 uses a module listed above it, which is the healthy direction.
17→14 scalafix.internal.v1 uses scalafix.lint✕
- Connections
- 4 pairs of types, where a type in scalafix.internal.v1 uses a type in scalafix.lint.
- The types involved
scalafix.internal.v1.InternalSemanticDoc→scalafix.lint.Diagnosticscalafix.internal.v1.Rules→scalafix.lint.Diagnosticscalafix.internal.v1.SemanticdbDiagnostic→scalafix.lint.Diagnosticscalafix.internal.v1.SemanticdbDiagnostic→scalafix.lint.LintSeverity
- Direction
- scalafix.internal.v1 uses scalafix.lint, so a change to scalafix.lint can break scalafix.internal.v1, while a change to scalafix.internal.v1 can't break scalafix.lint.
- Position
- Below the diagonal: scalafix.internal.v1 uses a module listed above it, which is the healthy direction.
17→15 scalafix.internal.v1 uses scalafix.internal.patch.PatchInternals✕
- Connections
- 2 pairs of types, where a type in scalafix.internal.v1 uses a type in scalafix.internal.patch.PatchInternals.
- The types involved
scalafix.internal.v1.MainOps→scalafix.internal.patch.PatchInternals.ResultWithContextscalafix.internal.v1.Rules→scalafix.internal.patch.PatchInternals.ResultWithContext
- Direction
- scalafix.internal.v1 uses scalafix.internal.patch.PatchInternals, so a change to scalafix.internal.patch.PatchInternals can break scalafix.internal.v1, while a change to scalafix.internal.v1 can't break scalafix.internal.patch.PatchInternals.
- Position
- Below the diagonal: scalafix.internal.v1 uses a module listed above it, which is the healthy direction.
17→18 scalafix.internal.v1 uses scalafix.v1 part of a loop✕
- Connections
- 11 pairs of types, where a type in scalafix.internal.v1 uses a type in scalafix.v1.
- The types involved
scalafix.internal.v1.DocumentFromProtobuf→scalafix.v1.SemanticTreescalafix.internal.v1.InternalSemanticDoc→scalafix.v1.SemanticTreescalafix.internal.v1.InternalSemanticDoc→scalafix.v1.SymbolInformationscalafix.internal.v1.InternalSemanticDoc→scalafix.v1.Symtabscalafix.internal.v1.InternalSemanticDoc→scalafix.v1.SyntacticDocumentscalafix.internal.v1.Rules→scalafix.v1.Configurationscalafix.internal.v1.Rules→scalafix.v1.SemanticDocumentscalafix.internal.v1.Rules→scalafix.v1.SyntacticDocumentscalafix.internal.v1.Rules→scalafix.v1.SyntacticRulescalafix.internal.v1.SymtabFromProtobuf→scalafix.v1.Symtabscalafix.internal.v1.Types→scalafix.v1.TypeRef
- Direction
- scalafix.internal.v1 uses scalafix.v1, so a change to scalafix.v1 can break scalafix.internal.v1, while a change to scalafix.internal.v1 can't break scalafix.v1.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→19 scalafix.internal.v1 uses scalafix.internal.patch part of a loop✕
- Connections
- 1 pair of types, where a type in scalafix.internal.v1 uses a type in scalafix.internal.patch.
- The types involved
scalafix.internal.v1.InternalDoc→scalafix.internal.patch.EscapeHatch
- Direction
- scalafix.internal.v1 uses scalafix.internal.patch, so a change to scalafix.internal.patch can break scalafix.internal.v1, while a change to scalafix.internal.v1 can't break scalafix.internal.patch.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→20 scalafix.internal.v1 uses scalafix.v0 part of a loop✕
- Connections
- 6 pairs of types, where a type in scalafix.internal.v1 uses a type in scalafix.v0.
- The types involved
scalafix.internal.v1.DocumentFromProtobuf→scalafix.v0.Syntheticscalafix.internal.v1.InternalSemanticDoc→scalafix.v0.Syntheticscalafix.internal.v1.MainOps→scalafix.v0.RuleCtxscalafix.internal.v1.MainOps→scalafix.v0.SemanticdbIndexscalafix.internal.v1.Rules→scalafix.v0.Rulescalafix.internal.v1.Rules→scalafix.v0.SemanticRule
- Direction
- scalafix.internal.v1 uses scalafix.v0, so a change to scalafix.v0 can break scalafix.internal.v1, while a change to scalafix.internal.v1 can't break scalafix.v0.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→26 scalafix.internal.v1 uses scalafix.internal.config part of a loop✕
- Connections
- 7 pairs of types, where a type in scalafix.internal.v1 uses a type in scalafix.internal.config.
- The types involved
scalafix.internal.v1.Args→scalafix.internal.config.FilterMatcherscalafix.internal.v1.Args→scalafix.internal.config.ScalaVersionscalafix.internal.v1.Args→scalafix.internal.config.ScalafixConfigscalafix.internal.v1.InternalDoc→scalafix.internal.config.ScalafixConfigscalafix.internal.v1.InternalSemanticDoc→scalafix.internal.config.ScalafixConfigscalafix.internal.v1.ValidatedArgs→scalafix.internal.config.FilterMatcherscalafix.internal.v1.ValidatedArgs→scalafix.internal.config.ScalafixConfig
- Direction
- scalafix.internal.v1 uses scalafix.internal.config, so a change to scalafix.internal.config can break scalafix.internal.v1, while a change to scalafix.internal.v1 can't break scalafix.internal.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→27 scalafix.internal.v1 uses scalafix.internal.config.ScalaVersion part of a loop✕
- Connections
- 2 pairs of types, where a type in scalafix.internal.v1 uses a type in scalafix.internal.config.ScalaVersion.
- The types involved
scalafix.internal.v1.MainOps→scalafix.internal.config.ScalaVersion.Patchscalafix.internal.v1.Rules→scalafix.internal.config.ScalaVersion.Patch
- Direction
- scalafix.internal.v1 uses scalafix.internal.config.ScalaVersion, so a change to scalafix.internal.config.ScalaVersion can break scalafix.internal.v1, while a change to scalafix.internal.v1 can't break scalafix.internal.config.ScalaVersion.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→35 scalafix.internal.v1 uses scalafix.internal.util.QualifyStrategy part of a loop✕
- Connections
- 1 pair of types, where a type in scalafix.internal.v1 uses a type in scalafix.internal.util.QualifyStrategy.
- The types involved
scalafix.internal.v1.TreePos→scalafix.internal.util.QualifyStrategy.Name
- Direction
- scalafix.internal.v1 uses scalafix.internal.util.QualifyStrategy, so a change to scalafix.internal.util.QualifyStrategy can break scalafix.internal.v1, while a change to scalafix.internal.v1 can't break scalafix.internal.util.QualifyStrategy.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→1 scalafix.v1 uses scala.meta.contrib✕
- Connections
- 2 pairs of types, where a type in scalafix.v1 uses a type in scala.meta.contrib.
- The types involved
scalafix.v1.SemanticDocument→scala.meta.contrib.AssociatedCommentsscalafix.v1.SyntacticDocument→scala.meta.contrib.AssociatedComments
- Direction
- scalafix.v1 uses scala.meta.contrib, so a change to scala.meta.contrib can break scalafix.v1, while a change to scalafix.v1 can't break scala.meta.contrib.
- Position
- Below the diagonal: scalafix.v1 uses a module listed above it, which is the healthy direction.
18→2 scalafix.v1 uses scalafix.cli✕
- Connections
- 1 pair of types, where a type in scalafix.v1 uses a type in scalafix.cli.
- The types involved
scalafix.v1.Main→scalafix.cli.ExitStatus
- Direction
- scalafix.v1 uses scalafix.cli, so a change to scalafix.cli can break scalafix.v1, while a change to scalafix.v1 can't break scalafix.cli.
- Position
- Below the diagonal: scalafix.v1 uses a module listed above it, which is the healthy direction.
18→4 scalafix.v1 uses scalafix.v0.SemanticdbIndex✕
- Connections
- 13 pairs of types, where a type in scalafix.v1 uses a type in scalafix.v0.SemanticdbIndex.
- The types involved
scalafix.v1.IdTree→scalafix.v0.SemanticdbIndex.Symbolscalafix.v1.MissingSymbolException→scalafix.v0.SemanticdbIndex.Symbolscalafix.v1.SemanticDocument→scalafix.v0.SemanticdbIndex.Symbolscalafix.v1.SingleType→scalafix.v0.SemanticdbIndex.Symbolscalafix.v1.SuperType→scalafix.v0.SemanticdbIndex.Symbolscalafix.v1.Symbol→scalafix.v0.SemanticdbIndex.Symbolscalafix.v1.SymbolInformation→scalafix.v0.SemanticdbIndex.Symbolscalafix.v1.SymbolMatcher→scalafix.v0.SemanticdbIndex.Symbolscalafix.v1.Symtab→scalafix.v0.SemanticdbIndex.Symbolscalafix.v1.ThisType→scalafix.v0.SemanticdbIndex.Symbolscalafix.v1.TypeRef→scalafix.v0.SemanticdbIndex.Symbolscalafix.v1.XtensionSemanticTree→scalafix.v0.SemanticdbIndex.Symbolscalafix.v1.XtensionTreeScalafix→scalafix.v0.SemanticdbIndex.Symbol
- Direction
- scalafix.v1 uses scalafix.v0.SemanticdbIndex, so a change to scalafix.v0.SemanticdbIndex can break scalafix.v1, while a change to scalafix.v1 can't break scalafix.v0.SemanticdbIndex.
- Position
- Below the diagonal: scalafix.v1 uses a module listed above it, which is the healthy direction.
18→7 scalafix.v1 uses scalafix.util✕
- Connections
- 4 pairs of types, where a type in scalafix.v1 uses a type in scalafix.util.
- The types involved
scalafix.v1.SemanticDocument→scalafix.util.MatchingParensscalafix.v1.SemanticDocument→scalafix.util.TokenListscalafix.v1.SyntacticDocument→scalafix.util.MatchingParensscalafix.v1.SyntacticDocument→scalafix.util.TokenList
- Direction
- scalafix.v1 uses scalafix.util, so a change to scalafix.util can break scalafix.v1, while a change to scalafix.v1 can't break scalafix.util.
- Position
- Below the diagonal: scalafix.v1 uses a module listed above it, which is the healthy direction.
18→9 scalafix.v1 uses scalafix.v1.RuleDecoder✕
- Connections
- 1 pair of types, where a type in scalafix.v1 uses a type in scalafix.v1.RuleDecoder.
- The types involved
scalafix.v1.RuleDecoder→scalafix.v1.RuleDecoder.Settings
- Direction
- scalafix.v1 uses scalafix.v1.RuleDecoder, so a change to scalafix.v1.RuleDecoder can break scalafix.v1, while a change to scalafix.v1 can't break scalafix.v1.RuleDecoder.
- Position
- Below the diagonal: scalafix.v1 uses a module listed above it, which is the healthy direction.
18→11 scalafix.v1 uses scalafix.internal.util.TypeExtractors✕
- Connections
- 1 pair of types, where a type in scalafix.v1 uses a type in scalafix.internal.util.TypeExtractors.
- The types involved
scalafix.v1.Symbol→scalafix.internal.util.TypeExtractors.Any
- Direction
- scalafix.v1 uses scalafix.internal.util.TypeExtractors, so a change to scalafix.internal.util.TypeExtractors can break scalafix.v1, while a change to scalafix.v1 can't break scalafix.internal.util.TypeExtractors.
- Position
- Below the diagonal: scalafix.v1 uses a module listed above it, which is the healthy direction.
18→12 scalafix.v1 uses scalafix.rule✕
- Connections
- 1 pair of types, where a type in scalafix.v1 uses a type in scalafix.rule.
- The types involved
scalafix.v1.Rule→scalafix.rule.RuleName
- Direction
- scalafix.v1 uses scalafix.rule, so a change to scalafix.rule can break scalafix.v1, while a change to scalafix.v1 can't break scalafix.rule.
- Position
- Below the diagonal: scalafix.v1 uses a module listed above it, which is the healthy direction.
18→14 scalafix.v1 uses scalafix.lint✕
- Connections
- 1 pair of types, where a type in scalafix.v1 uses a type in scalafix.lint.
- The types involved
scalafix.v1.SemanticDocument→scalafix.lint.Diagnostic
- Direction
- scalafix.v1 uses scalafix.lint, so a change to scalafix.lint can break scalafix.v1, while a change to scalafix.v1 can't break scalafix.lint.
- Position
- Below the diagonal: scalafix.v1 uses a module listed above it, which is the healthy direction.
18→17 scalafix.v1 uses scalafix.internal.v1✕
- Connections
- 3 pairs of types, where a type in scalafix.v1 uses a type in scalafix.internal.v1.
- The types involved
scalafix.v1.RuleDecoder→scalafix.internal.v1.Rulesscalafix.v1.SemanticDocument→scalafix.internal.v1.InternalSemanticDocscalafix.v1.SyntacticDocument→scalafix.internal.v1.InternalDoc
- Direction
- scalafix.v1 uses scalafix.internal.v1, so a change to scalafix.internal.v1 can break scalafix.v1, while a change to scalafix.v1 can't break scalafix.internal.v1.
- Position
- Below the diagonal: scalafix.v1 uses a module listed above it, which is the healthy direction.
18→20 scalafix.v1 uses scalafix.v0 part of a loop✕
- Connections
- 11 pairs of types, where a type in scalafix.v1 uses a type in scalafix.v0.
- The types involved
scalafix.v1.ClassSignature→scalafix.v0.Signaturescalafix.v1.MethodSignature→scalafix.v0.Signaturescalafix.v1.NoSignature→scalafix.v0.Signaturescalafix.v1.Rule→scalafix.v0.Rulescalafix.v1.RuleDecoder→scalafix.v0.Rulescalafix.v1.SemanticRule→scalafix.v0.Rulescalafix.v1.SymbolInformation→scalafix.v0.Signaturescalafix.v1.SymbolMatcher→scalafix.v0.SymbolMatcherscalafix.v1.SyntacticRule→scalafix.v0.Rulescalafix.v1.TypeSignature→scalafix.v0.Signaturescalafix.v1.ValueSignature→scalafix.v0.Signature
- Direction
- scalafix.v1 uses scalafix.v0, so a change to scalafix.v0 can break scalafix.v1, while a change to scalafix.v1 can't break scalafix.v0.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→27 scalafix.v1 uses scalafix.internal.config.ScalaVersion part of a loop✕
- Connections
- 2 pairs of types, where a type in scalafix.v1 uses a type in scalafix.internal.config.ScalaVersion.
- The types involved
scalafix.v1.SemanticRule→scalafix.internal.config.ScalaVersion.Patchscalafix.v1.SyntacticRule→scalafix.internal.config.ScalaVersion.Patch
- Direction
- scalafix.v1 uses scalafix.internal.config.ScalaVersion, so a change to scalafix.internal.config.ScalaVersion can break scalafix.v1, while a change to scalafix.v1 can't break scalafix.internal.config.ScalaVersion.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→4 scalafix.internal.patch uses scalafix.v0.SemanticdbIndex✕
- Connections
- 2 pairs of types, where a type in scalafix.internal.patch uses a type in scalafix.v0.SemanticdbIndex.
- The types involved
scalafix.internal.patch.ImportPatchOps→scalafix.v0.SemanticdbIndex.Symbolscalafix.internal.patch.LegacyPatchOps→scalafix.v0.SemanticdbIndex.Symbol
- Direction
- scalafix.internal.patch uses scalafix.v0.SemanticdbIndex, so a change to scalafix.v0.SemanticdbIndex can break scalafix.internal.patch, while a change to scalafix.internal.patch can't break scalafix.v0.SemanticdbIndex.
- Position
- Below the diagonal: scalafix.internal.patch uses a module listed above it, which is the healthy direction.
19→12 scalafix.internal.patch uses scalafix.rule✕
- Connections
- 2 pairs of types, where a type in scalafix.internal.patch uses a type in scalafix.rule.
- The types involved
scalafix.internal.patch.EscapeHatch→scalafix.rule.RuleNamescalafix.internal.patch.PatchInternals→scalafix.rule.RuleName
- Direction
- scalafix.internal.patch uses scalafix.rule, so a change to scalafix.rule can break scalafix.internal.patch, while a change to scalafix.internal.patch can't break scalafix.rule.
- Position
- Below the diagonal: scalafix.internal.patch uses a module listed above it, which is the healthy direction.
19→14 scalafix.internal.patch uses scalafix.lint✕
- Connections
- 1 pair of types, where a type in scalafix.internal.patch uses a type in scalafix.lint.
- The types involved
scalafix.internal.patch.LegacyPatchOps→scalafix.lint.Diagnostic
- Direction
- scalafix.internal.patch uses scalafix.lint, so a change to scalafix.lint can break scalafix.internal.patch, while a change to scalafix.internal.patch can't break scalafix.lint.
- Position
- Below the diagonal: scalafix.internal.patch uses a module listed above it, which is the healthy direction.
19→15 scalafix.internal.patch uses scalafix.internal.patch.PatchInternals✕
- Connections
- 1 pair of types, where a type in scalafix.internal.patch uses a type in scalafix.internal.patch.PatchInternals.
- The types involved
scalafix.internal.patch.PatchInternals→scalafix.internal.patch.PatchInternals.ResultWithContext
- Direction
- scalafix.internal.patch uses scalafix.internal.patch.PatchInternals, so a change to scalafix.internal.patch.PatchInternals can break scalafix.internal.patch, while a change to scalafix.internal.patch can't break scalafix.internal.patch.PatchInternals.
- Position
- Below the diagonal: scalafix.internal.patch uses a module listed above it, which is the healthy direction.
19→16 scalafix.internal.patch uses scalafix.patch✕
- Connections
- 1 pair of types, where a type in scalafix.internal.patch uses a type in scalafix.patch.
- The types involved
scalafix.internal.patch.LegacyPatchOps→scalafix.patch.PatchOps
- Direction
- scalafix.internal.patch uses scalafix.patch, so a change to scalafix.patch can break scalafix.internal.patch, while a change to scalafix.internal.patch can't break scalafix.patch.
- Position
- Below the diagonal: scalafix.internal.patch uses a module listed above it, which is the healthy direction.
19→18 scalafix.internal.patch uses scalafix.v1✕
- Connections
- 2 pairs of types, where a type in scalafix.internal.patch uses a type in scalafix.v1.
- The types involved
scalafix.internal.patch.PatchInternals→scalafix.v1.SemanticDocumentscalafix.internal.patch.PatchInternals→scalafix.v1.SyntacticDocument
- Direction
- scalafix.internal.patch uses scalafix.v1, so a change to scalafix.v1 can break scalafix.internal.patch, while a change to scalafix.internal.patch can't break scalafix.v1.
- Position
- Below the diagonal: scalafix.internal.patch uses a module listed above it, which is the healthy direction.
19→20 scalafix.internal.patch uses scalafix.v0 part of a loop✕
- Connections
- 11 pairs of types, where a type in scalafix.internal.patch uses a type in scalafix.v0.
- The types involved
scalafix.internal.patch.CrashingSemanticdbIndex→scalafix.v0.Documentscalafix.internal.patch.CrashingSemanticdbIndex→scalafix.v0.SemanticdbIndexscalafix.internal.patch.EscapeHatch→scalafix.v0.RuleCtxscalafix.internal.patch.EscapeHatch→scalafix.v0.SemanticdbIndexscalafix.internal.patch.ImportPatchOps→scalafix.v0.RuleCtxscalafix.internal.patch.ImportPatchOps→scalafix.v0.SemanticdbIndexscalafix.internal.patch.LegacyPatchOps→scalafix.v0.SemanticdbIndexscalafix.internal.patch.PatchInternals→scalafix.v0.RuleCtxscalafix.internal.patch.PatchInternals→scalafix.v0.SemanticdbIndexscalafix.internal.patch.ReplaceSymbolOps→scalafix.v0.RuleCtxscalafix.internal.patch.ReplaceSymbolOps→scalafix.v0.SemanticdbIndex
- Direction
- scalafix.internal.patch uses scalafix.v0, so a change to scalafix.v0 can break scalafix.internal.patch, while a change to scalafix.internal.patch can't break scalafix.v0.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→22 scalafix.internal.patch uses scalafix.v0.Symbol part of a loop✕
- Connections
- 1 pair of types, where a type in scalafix.internal.patch uses a type in scalafix.v0.Symbol.
- The types involved
scalafix.internal.patch.LegacyPatchOps→scalafix.v0.Symbol.Global
- Direction
- scalafix.internal.patch uses scalafix.v0.Symbol, so a change to scalafix.v0.Symbol can break scalafix.internal.patch, while a change to scalafix.internal.patch can't break scalafix.v0.Symbol.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→25 scalafix.internal.patch uses scalafix.patch.Patch.internal part of a loop✕
- Connections
- 3 pairs of types, where a type in scalafix.internal.patch uses a type in scalafix.patch.Patch.internal.
- The types involved
scalafix.internal.patch.ImportPatchOps→scalafix.patch.Patch.internal.ImportPatchscalafix.internal.patch.PatchInternals→scalafix.patch.Patch.internal.TokenPatchscalafix.internal.patch.ReplaceSymbolOps→scalafix.patch.Patch.internal.ReplaceSymbol
- Direction
- scalafix.internal.patch uses scalafix.patch.Patch.internal, so a change to scalafix.patch.Patch.internal can break scalafix.internal.patch, while a change to scalafix.internal.patch can't break scalafix.patch.Patch.internal.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→27 scalafix.internal.patch uses scalafix.internal.config.ScalaVersion part of a loop✕
- Connections
- 5 pairs of types, where a type in scalafix.internal.patch uses a type in scalafix.internal.config.ScalaVersion.
- The types involved
scalafix.internal.patch.EscapeHatch→scalafix.internal.config.ScalaVersion.Patchscalafix.internal.patch.ImportPatchOps→scalafix.internal.config.ScalaVersion.Patchscalafix.internal.patch.LegacyPatchOps→scalafix.internal.config.ScalaVersion.Patchscalafix.internal.patch.PatchInternals→scalafix.internal.config.ScalaVersion.Patchscalafix.internal.patch.ReplaceSymbolOps→scalafix.internal.config.ScalaVersion.Patch
- Direction
- scalafix.internal.patch uses scalafix.internal.config.ScalaVersion, so a change to scalafix.internal.config.ScalaVersion can break scalafix.internal.patch, while a change to scalafix.internal.patch can't break scalafix.internal.config.ScalaVersion.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→35 scalafix.internal.patch uses scalafix.internal.util.QualifyStrategy part of a loop✕
- Connections
- 1 pair of types, where a type in scalafix.internal.patch uses a type in scalafix.internal.util.QualifyStrategy.
- The types involved
scalafix.internal.patch.ReplaceSymbolOps→scalafix.internal.util.QualifyStrategy.Name
- Direction
- scalafix.internal.patch uses scalafix.internal.util.QualifyStrategy, so a change to scalafix.internal.util.QualifyStrategy can break scalafix.internal.patch, while a change to scalafix.internal.patch can't break scalafix.internal.util.QualifyStrategy.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→1 scalafix.v0 uses scala.meta.contrib✕
- Connections
- 1 pair of types, where a type in scalafix.v0 uses a type in scala.meta.contrib.
- The types involved
scalafix.v0.RuleCtx→scala.meta.contrib.AssociatedComments
- Direction
- scalafix.v0 uses scala.meta.contrib, so a change to scala.meta.contrib can break scalafix.v0, while a change to scalafix.v0 can't break scala.meta.contrib.
- Position
- Below the diagonal: scalafix.v0 uses a module listed above it, which is the healthy direction.
20→4 scalafix.v0 uses scalafix.v0.SemanticdbIndex✕
- Connections
- 4 pairs of types, where a type in scalafix.v0 uses a type in scalafix.v0.SemanticdbIndex.
- The types involved
scalafix.v0.ResolvedName→scalafix.v0.SemanticdbIndex.Symbolscalafix.v0.ResolvedSymbol→scalafix.v0.SemanticdbIndex.Symbolscalafix.v0.SemanticdbIndex→scalafix.v0.SemanticdbIndex.Symbolscalafix.v0.SymbolMatcher→scalafix.v0.SemanticdbIndex.Symbol
- Direction
- scalafix.v0 uses scalafix.v0.SemanticdbIndex, so a change to scalafix.v0.SemanticdbIndex can break scalafix.v0, while a change to scalafix.v0 can't break scalafix.v0.SemanticdbIndex.
- Position
- Below the diagonal: scalafix.v0 uses a module listed above it, which is the healthy direction.
20→7 scalafix.v0 uses scalafix.util✕
- Connections
- 2 pairs of types, where a type in scalafix.v0 uses a type in scalafix.util.
- The types involved
scalafix.v0.RuleCtx→scalafix.util.MatchingParensscalafix.v0.RuleCtx→scalafix.util.TokenList
- Direction
- scalafix.v0 uses scalafix.util, so a change to scalafix.util can break scalafix.v0, while a change to scalafix.v0 can't break scalafix.util.
- Position
- Below the diagonal: scalafix.v0 uses a module listed above it, which is the healthy direction.
20→12 scalafix.v0 uses scalafix.rule✕
- Connections
- 3 pairs of types, where a type in scalafix.v0 uses a type in scalafix.rule.
- The types involved
scalafix.v0.LintCategory→scalafix.rule.RuleNamescalafix.v0.LintMessage→scalafix.rule.RuleNamescalafix.v0.Rule→scalafix.rule.RuleName
- Direction
- scalafix.v0 uses scalafix.rule, so a change to scalafix.rule can break scalafix.v0, while a change to scalafix.v0 can't break scalafix.rule.
- Position
- Below the diagonal: scalafix.v0 uses a module listed above it, which is the healthy direction.
20→14 scalafix.v0 uses scalafix.lint✕
- Connections
- 5 pairs of types, where a type in scalafix.v0 uses a type in scalafix.lint.
- The types involved
scalafix.v0.LintCategory→scalafix.lint.Diagnosticscalafix.v0.LintCategory→scalafix.lint.LintSeverityscalafix.v0.LintMessage→scalafix.lint.Diagnosticscalafix.v0.LintMessage→scalafix.lint.LintSeverityscalafix.v0.Rule→scalafix.lint.Diagnostic
- Direction
- scalafix.v0 uses scalafix.lint, so a change to scalafix.lint can break scalafix.v0, while a change to scalafix.v0 can't break scalafix.lint.
- Position
- Below the diagonal: scalafix.v0 uses a module listed above it, which is the healthy direction.
20→16 scalafix.v0 uses scalafix.patch✕
- Connections
- 1 pair of types, where a type in scalafix.v0 uses a type in scalafix.patch.
- The types involved
scalafix.v0.RuleCtx→scalafix.patch.PatchOps
- Direction
- scalafix.v0 uses scalafix.patch, so a change to scalafix.patch can break scalafix.v0, while a change to scalafix.v0 can't break scalafix.patch.
- Position
- Below the diagonal: scalafix.v0 uses a module listed above it, which is the healthy direction.
20→18 scalafix.v0 uses scalafix.v1✕
- Connections
- 1 pair of types, where a type in scalafix.v0 uses a type in scalafix.v1.
- The types involved
scalafix.v0.SemanticdbIndex→scalafix.v1.SemanticContext
- Direction
- scalafix.v0 uses scalafix.v1, so a change to scalafix.v1 can break scalafix.v0, while a change to scalafix.v0 can't break scalafix.v1.
- Position
- Below the diagonal: scalafix.v0 uses a module listed above it, which is the healthy direction.
20→19 scalafix.v0 uses scalafix.internal.patch✕
- Connections
- 1 pair of types, where a type in scalafix.v0 uses a type in scalafix.internal.patch.
- The types involved
scalafix.v0.RuleCtx→scalafix.internal.patch.EscapeHatch
- Direction
- scalafix.v0 uses scalafix.internal.patch, so a change to scalafix.internal.patch can break scalafix.v0, while a change to scalafix.v0 can't break scalafix.internal.patch.
- Position
- Below the diagonal: scalafix.v0 uses a module listed above it, which is the healthy direction.
20→26 scalafix.v0 uses scalafix.internal.config part of a loop✕
- Connections
- 3 pairs of types, where a type in scalafix.v0 uses a type in scalafix.internal.config.
- The types involved
scalafix.v0.LintCategory→scalafix.internal.config.LintConfigscalafix.v0.Rule→scalafix.internal.config.ScalafixConfigscalafix.v0.RuleCtx→scalafix.internal.config.ScalafixConfig
- Direction
- scalafix.v0 uses scalafix.internal.config, so a change to scalafix.internal.config can break scalafix.v0, while a change to scalafix.v0 can't break scalafix.internal.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→27 scalafix.v0 uses scalafix.internal.config.ScalaVersion part of a loop✕
- Connections
- 1 pair of types, where a type in scalafix.v0 uses a type in scalafix.internal.config.ScalaVersion.
- The types involved
scalafix.v0.Rule→scalafix.internal.config.ScalaVersion.Patch
- Direction
- scalafix.v0 uses scalafix.internal.config.ScalaVersion, so a change to scalafix.internal.config.ScalaVersion can break scalafix.v0, while a change to scalafix.v0 can't break scalafix.internal.config.ScalaVersion.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→4 scalafix.syntax uses scalafix.v0.SemanticdbIndex✕
- Connections
- 2 pairs of types, where a type in scalafix.syntax uses a type in scalafix.v0.SemanticdbIndex.
- The types involved
scalafix.syntax.XtensionRefSymbolOpt→scalafix.v0.SemanticdbIndex.Symbolscalafix.syntax.XtensionSymbol→scalafix.v0.SemanticdbIndex.Symbol
- Direction
- scalafix.syntax uses scalafix.v0.SemanticdbIndex, so a change to scalafix.v0.SemanticdbIndex can break scalafix.syntax, while a change to scalafix.syntax can't break scalafix.v0.SemanticdbIndex.
- Position
- Below the diagonal: scalafix.syntax uses a module listed above it, which is the healthy direction.
21→8 scalafix.syntax uses scalafix.v0.Signature✕
- Connections
- 1 pair of types, where a type in scalafix.syntax uses a type in scalafix.v0.Signature.
- The types involved
scalafix.syntax.XtensionSymbolSemanticdbIndex→scalafix.v0.Signature.Type
- Direction
- scalafix.syntax uses scalafix.v0.Signature, so a change to scalafix.v0.Signature can break scalafix.syntax, while a change to scalafix.syntax can't break scalafix.v0.Signature.
- Position
- Below the diagonal: scalafix.syntax uses a module listed above it, which is the healthy direction.
21→20 scalafix.syntax uses scalafix.v0✕
- Connections
- 3 pairs of types, where a type in scalafix.syntax uses a type in scalafix.v0.
- The types involved
scalafix.syntax.XtensionRefSymbolOpt→scalafix.v0.Denotationscalafix.syntax.XtensionSymbolSemanticdbIndex→scalafix.v0.Denotationscalafix.syntax.XtensionTreeScalafix→scalafix.v0.SymbolMatcher
- Direction
- scalafix.syntax uses scalafix.v0, so a change to scalafix.v0 can break scalafix.syntax, while a change to scalafix.syntax can't break scalafix.v0.
- Position
- Below the diagonal: scalafix.syntax uses a module listed above it, which is the healthy direction.
22→4 scalafix.v0.Symbol uses scalafix.v0.SemanticdbIndex✕
- Connections
- 4 pairs of types, where a type in scalafix.v0.Symbol uses a type in scalafix.v0.SemanticdbIndex.
- The types involved
scalafix.v0.Symbol.Global→scalafix.v0.SemanticdbIndex.Symbolscalafix.v0.Symbol.Local→scalafix.v0.SemanticdbIndex.Symbolscalafix.v0.Symbol.Multi→scalafix.v0.SemanticdbIndex.Symbolscalafix.v0.Symbol.None→scalafix.v0.SemanticdbIndex.Symbol
- Direction
- scalafix.v0.Symbol uses scalafix.v0.SemanticdbIndex, so a change to scalafix.v0.SemanticdbIndex can break scalafix.v0.Symbol, while a change to scalafix.v0.Symbol can't break scalafix.v0.SemanticdbIndex.
- Position
- Below the diagonal: scalafix.v0.Symbol uses a module listed above it, which is the healthy direction.
22→20 scalafix.v0.Symbol uses scalafix.v0✕
- Connections
- 1 pair of types, where a type in scalafix.v0.Symbol uses a type in scalafix.v0.
- The types involved
scalafix.v0.Symbol.Global→scalafix.v0.Signature
- Direction
- scalafix.v0.Symbol uses scalafix.v0, so a change to scalafix.v0 can break scalafix.v0.Symbol, while a change to scalafix.v0.Symbol can't break scalafix.v0.
- Position
- Below the diagonal: scalafix.v0.Symbol uses a module listed above it, which is the healthy direction.
23→6 scalafix.docs uses scalafix.internal.symtab✕
- Connections
- 1 pair of types, where a type in scalafix.docs uses a type in scalafix.internal.symtab.
- The types involved
scalafix.docs.PatchDocs→scalafix.internal.symtab.SymbolTable
- Direction
- scalafix.docs uses scalafix.internal.symtab, so a change to scalafix.internal.symtab can break scalafix.docs, while a change to scalafix.docs can't break scalafix.internal.symtab.
- Position
- Below the diagonal: scalafix.docs uses a module listed above it, which is the healthy direction.
23→11 scalafix.docs uses scalafix.internal.util.TypeExtractors✕
- Connections
- 1 pair of types, where a type in scalafix.docs uses a type in scalafix.internal.util.TypeExtractors.
- The types involved
scalafix.docs.PatchDocs→scalafix.internal.util.TypeExtractors.Any
- Direction
- scalafix.docs uses scalafix.internal.util.TypeExtractors, so a change to scalafix.internal.util.TypeExtractors can break scalafix.docs, while a change to scalafix.docs can't break scalafix.internal.util.TypeExtractors.
- Position
- Below the diagonal: scalafix.docs uses a module listed above it, which is the healthy direction.
23→18 scalafix.docs uses scalafix.v1✕
- Connections
- 3 pairs of types, where a type in scalafix.docs uses a type in scalafix.v1.
- The types involved
scalafix.docs.PatchDocs→scalafix.v1.SemanticDocumentscalafix.docs.PatchDocs→scalafix.v1.Symtabscalafix.docs.SymbolInformationDocs→scalafix.v1.SymbolInformation
- Direction
- scalafix.docs uses scalafix.v1, so a change to scalafix.v1 can break scalafix.docs, while a change to scalafix.docs can't break scalafix.v1.
- Position
- Below the diagonal: scalafix.docs uses a module listed above it, which is the healthy direction.
23→22 scalafix.docs uses scalafix.v0.Symbol✕
- Connections
- 1 pair of types, where a type in scalafix.docs uses a type in scalafix.v0.Symbol.
- The types involved
scalafix.docs.PatchDocs→scalafix.v0.Symbol.Global
- Direction
- scalafix.docs uses scalafix.v0.Symbol, so a change to scalafix.v0.Symbol can break scalafix.docs, while a change to scalafix.docs can't break scalafix.v0.Symbol.
- Position
- Below the diagonal: scalafix.docs uses a module listed above it, which is the healthy direction.
24→4 scalafix.internal.util.SymbolOps uses scalafix.v0.SemanticdbIndex✕
- Connections
- 2 pairs of types, where a type in scalafix.internal.util.SymbolOps uses a type in scalafix.v0.SemanticdbIndex.
- The types involved
scalafix.internal.util.SymbolOps.Root→scalafix.v0.SemanticdbIndex.Symbolscalafix.internal.util.SymbolOps.SymbolType→scalafix.v0.SemanticdbIndex.Symbol
- Direction
- scalafix.internal.util.SymbolOps uses scalafix.v0.SemanticdbIndex, so a change to scalafix.v0.SemanticdbIndex can break scalafix.internal.util.SymbolOps, while a change to scalafix.internal.util.SymbolOps can't break scalafix.v0.SemanticdbIndex.
- Position
- Below the diagonal: scalafix.internal.util.SymbolOps uses a module listed above it, which is the healthy direction.
24→20 scalafix.internal.util.SymbolOps uses scalafix.v0✕
- Connections
- 2 pairs of types, where a type in scalafix.internal.util.SymbolOps uses a type in scalafix.v0.
- The types involved
scalafix.internal.util.SymbolOps.Root→scalafix.v0.Signaturescalafix.internal.util.SymbolOps.SignatureName→scalafix.v0.Signature
- Direction
- scalafix.internal.util.SymbolOps uses scalafix.v0, so a change to scalafix.v0 can break scalafix.internal.util.SymbolOps, while a change to scalafix.internal.util.SymbolOps can't break scalafix.v0.
- Position
- Below the diagonal: scalafix.internal.util.SymbolOps uses a module listed above it, which is the healthy direction.
24→22 scalafix.internal.util.SymbolOps uses scalafix.v0.Symbol✕
- Connections
- 1 pair of types, where a type in scalafix.internal.util.SymbolOps uses a type in scalafix.v0.Symbol.
- The types involved
scalafix.internal.util.SymbolOps.Root→scalafix.v0.Symbol.Global
- Direction
- scalafix.internal.util.SymbolOps uses scalafix.v0.Symbol, so a change to scalafix.v0.Symbol can break scalafix.internal.util.SymbolOps, while a change to scalafix.internal.util.SymbolOps can't break scalafix.v0.Symbol.
- Position
- Below the diagonal: scalafix.internal.util.SymbolOps uses a module listed above it, which is the healthy direction.
25→4 scalafix.patch.Patch.internal uses scalafix.v0.SemanticdbIndex✕
- Connections
- 2 pairs of types, where a type in scalafix.patch.Patch.internal uses a type in scalafix.v0.SemanticdbIndex.
- The types involved
scalafix.patch.Patch.internal.AddGlobalSymbol→scalafix.v0.SemanticdbIndex.Symbolscalafix.patch.Patch.internal.RemoveGlobalImport→scalafix.v0.SemanticdbIndex.Symbol
- Direction
- scalafix.patch.Patch.internal uses scalafix.v0.SemanticdbIndex, so a change to scalafix.v0.SemanticdbIndex can break scalafix.patch.Patch.internal, while a change to scalafix.patch.Patch.internal can't break scalafix.v0.SemanticdbIndex.
- Position
- Below the diagonal: scalafix.patch.Patch.internal uses a module listed above it, which is the healthy direction.
25→14 scalafix.patch.Patch.internal uses scalafix.lint✕
- Connections
- 1 pair of types, where a type in scalafix.patch.Patch.internal uses a type in scalafix.lint.
- The types involved
scalafix.patch.Patch.internal.LintPatch→scalafix.lint.Diagnostic
- Direction
- scalafix.patch.Patch.internal uses scalafix.lint, so a change to scalafix.lint can break scalafix.patch.Patch.internal, while a change to scalafix.patch.Patch.internal can't break scalafix.lint.
- Position
- Below the diagonal: scalafix.patch.Patch.internal uses a module listed above it, which is the healthy direction.
25→22 scalafix.patch.Patch.internal uses scalafix.v0.Symbol✕
- Connections
- 1 pair of types, where a type in scalafix.patch.Patch.internal uses a type in scalafix.v0.Symbol.
- The types involved
scalafix.patch.Patch.internal.ReplaceSymbol→scalafix.v0.Symbol.Global
- Direction
- scalafix.patch.Patch.internal uses scalafix.v0.Symbol, so a change to scalafix.v0.Symbol can break scalafix.patch.Patch.internal, while a change to scalafix.patch.Patch.internal can't break scalafix.v0.Symbol.
- Position
- Below the diagonal: scalafix.patch.Patch.internal uses a module listed above it, which is the healthy direction.
25→27 scalafix.patch.Patch.internal uses scalafix.internal.config.ScalaVersion part of a loop✕
- Connections
- 6 pairs of types, where a type in scalafix.patch.Patch.internal uses a type in scalafix.internal.config.ScalaVersion.
- The types involved
scalafix.patch.Patch.internal.AtomicPatch→scalafix.internal.config.ScalaVersion.Patchscalafix.patch.Patch.internal.Concat→scalafix.internal.config.ScalaVersion.Patchscalafix.patch.Patch.internal.EmptyPatch→scalafix.internal.config.ScalaVersion.Patchscalafix.patch.Patch.internal.LintPatch→scalafix.internal.config.ScalaVersion.Patchscalafix.patch.Patch.internal.TokenPatch→scalafix.internal.config.ScalaVersion.Patchscalafix.patch.Patch.internal.TreePatch→scalafix.internal.config.ScalaVersion.Patch
- Direction
- scalafix.patch.Patch.internal uses scalafix.internal.config.ScalaVersion, so a change to scalafix.internal.config.ScalaVersion can break scalafix.patch.Patch.internal, while a change to scalafix.patch.Patch.internal can't break scalafix.internal.config.ScalaVersion.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→3 scalafix.internal.config uses scalafix.config✕
- Connections
- 1 pair of types, where a type in scalafix.internal.config uses a type in scalafix.config.
- The types involved
scalafix.internal.config.FilterMatcher→scalafix.config.Regex
- Direction
- scalafix.internal.config uses scalafix.config, so a change to scalafix.config can break scalafix.internal.config, while a change to scalafix.internal.config can't break scalafix.config.
- Position
- Below the diagonal: scalafix.internal.config uses a module listed above it, which is the healthy direction.
26→14 scalafix.internal.config uses scalafix.lint✕
- Connections
- 5 pairs of types, where a type in scalafix.internal.config uses a type in scalafix.lint.
- The types involved
scalafix.internal.config.LintConfig→scalafix.lint.LintSeverityscalafix.internal.config.PrintStreamReporter→scalafix.lint.LintSeverityscalafix.internal.config.PrintStreamReporter→scalafix.lint.RuleDiagnosticscalafix.internal.config.ScalafixReporter→scalafix.lint.LintSeverityscalafix.internal.config.ScalafixReporter→scalafix.lint.RuleDiagnostic
- Direction
- scalafix.internal.config uses scalafix.lint, so a change to scalafix.lint can break scalafix.internal.config, while a change to scalafix.internal.config can't break scalafix.lint.
- Position
- Below the diagonal: scalafix.internal.config uses a module listed above it, which is the healthy direction.
26→25 scalafix.internal.config uses scalafix.patch.Patch.internal✕
- Connections
- 3 pairs of types, where a type in scalafix.internal.config uses a type in scalafix.patch.Patch.internal.
- The types involved
scalafix.internal.config.ConfigRulePatches→scalafix.patch.Patch.internal.AddGlobalImportscalafix.internal.config.ConfigRulePatches→scalafix.patch.Patch.internal.RemoveGlobalImportscalafix.internal.config.ConfigRulePatches→scalafix.patch.Patch.internal.ReplaceSymbol
- Direction
- scalafix.internal.config uses scalafix.patch.Patch.internal, so a change to scalafix.patch.Patch.internal can break scalafix.internal.config, while a change to scalafix.internal.config can't break scalafix.patch.Patch.internal.
- Position
- Below the diagonal: scalafix.internal.config uses a module listed above it, which is the healthy direction.
26→27 scalafix.internal.config uses scalafix.internal.config.ScalaVersion part of a loop✕
- Connections
- 2 pairs of types, where a type in scalafix.internal.config uses a type in scalafix.internal.config.ScalaVersion.
- The types involved
scalafix.internal.config.ConfigRulePatches→scalafix.internal.config.ScalaVersion.Patchscalafix.internal.config.ScalaVersion→scalafix.internal.config.ScalaVersion.MajorVersion
- Direction
- scalafix.internal.config uses scalafix.internal.config.ScalaVersion, so a change to scalafix.internal.config.ScalaVersion can break scalafix.internal.config, while a change to scalafix.internal.config can't break scalafix.internal.config.ScalaVersion.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→26 scalafix.internal.config.ScalaVersion uses scalafix.internal.config✕
- Connections
- 5 pairs of types, where a type in scalafix.internal.config.ScalaVersion uses a type in scalafix.internal.config.
- The types involved
scalafix.internal.config.ScalaVersion.Major→scalafix.internal.config.ScalaVersionscalafix.internal.config.ScalaVersion.Minor→scalafix.internal.config.ScalaVersionscalafix.internal.config.ScalaVersion.Nightly→scalafix.internal.config.ScalaVersionscalafix.internal.config.ScalaVersion.Patch→scalafix.internal.config.ScalaVersionscalafix.internal.config.ScalaVersion.RC→scalafix.internal.config.ScalaVersion
- Direction
- scalafix.internal.config.ScalaVersion uses scalafix.internal.config, so a change to scalafix.internal.config can break scalafix.internal.config.ScalaVersion, while a change to scalafix.internal.config.ScalaVersion can't break scalafix.internal.config.
- Position
- Below the diagonal: scalafix.internal.config.ScalaVersion uses a module listed above it, which is the healthy direction.
28→3 scalafix.internal.patch.EscapeHatch uses scalafix.config✕
- Connections
- 1 pair of types, where a type in scalafix.internal.patch.EscapeHatch uses a type in scalafix.config.
- The types involved
scalafix.internal.patch.EscapeHatch.Anchor→scalafix.config.Regex
- Direction
- scalafix.internal.patch.EscapeHatch uses scalafix.config, so a change to scalafix.config can break scalafix.internal.patch.EscapeHatch, while a change to scalafix.internal.patch.EscapeHatch can't break scalafix.config.
- Position
- Below the diagonal: scalafix.internal.patch.EscapeHatch uses a module listed above it, which is the healthy direction.
28→12 scalafix.internal.patch.EscapeHatch uses scalafix.rule✕
- Connections
- 3 pairs of types, where a type in scalafix.internal.patch.EscapeHatch uses a type in scalafix.rule.
- The types involved
scalafix.internal.patch.EscapeHatch.AnchoredEscapes→scalafix.rule.RuleNamescalafix.internal.patch.EscapeHatch.AnnotatedEscapes→scalafix.rule.RuleNamescalafix.internal.patch.EscapeHatch.EscapeFilter→scalafix.rule.RuleName
- Direction
- scalafix.internal.patch.EscapeHatch uses scalafix.rule, so a change to scalafix.rule can break scalafix.internal.patch.EscapeHatch, while a change to scalafix.internal.patch.EscapeHatch can't break scalafix.rule.
- Position
- Below the diagonal: scalafix.internal.patch.EscapeHatch uses a module listed above it, which is the healthy direction.
28→26 scalafix.internal.patch.EscapeHatch uses scalafix.internal.config✕
- Connections
- 1 pair of types, where a type in scalafix.internal.patch.EscapeHatch uses a type in scalafix.internal.config.
- The types involved
scalafix.internal.patch.EscapeHatch.EscapeFilter→scalafix.internal.config.FilterMatcher
- Direction
- scalafix.internal.patch.EscapeHatch uses scalafix.internal.config, so a change to scalafix.internal.config can break scalafix.internal.patch.EscapeHatch, while a change to scalafix.internal.patch.EscapeHatch can't break scalafix.internal.config.
- Position
- Below the diagonal: scalafix.internal.patch.EscapeHatch uses a module listed above it, which is the healthy direction.
29→12 scalafix.internal.util.LintSyntax uses scalafix.rule✕
- Connections
- 1 pair of types, where a type in scalafix.internal.util.LintSyntax uses a type in scalafix.rule.
- The types involved
scalafix.internal.util.LintSyntax.XtensionDiagnostic→scalafix.rule.RuleName
- Direction
- scalafix.internal.util.LintSyntax uses scalafix.rule, so a change to scalafix.rule can break scalafix.internal.util.LintSyntax, while a change to scalafix.internal.util.LintSyntax can't break scalafix.rule.
- Position
- Below the diagonal: scalafix.internal.util.LintSyntax uses a module listed above it, which is the healthy direction.
29→14 scalafix.internal.util.LintSyntax uses scalafix.lint✕
- Connections
- 2 pairs of types, where a type in scalafix.internal.util.LintSyntax uses a type in scalafix.lint.
- The types involved
scalafix.internal.util.LintSyntax.XtensionDiagnostic→scalafix.lint.RuleDiagnosticscalafix.internal.util.LintSyntax.XtensionRuleDiagnostic→scalafix.lint.RuleDiagnostic
- Direction
- scalafix.internal.util.LintSyntax uses scalafix.lint, so a change to scalafix.lint can break scalafix.internal.util.LintSyntax, while a change to scalafix.internal.util.LintSyntax can't break scalafix.lint.
- Position
- Below the diagonal: scalafix.internal.util.LintSyntax uses a module listed above it, which is the healthy direction.
29→26 scalafix.internal.util.LintSyntax uses scalafix.internal.config✕
- Connections
- 1 pair of types, where a type in scalafix.internal.util.LintSyntax uses a type in scalafix.internal.config.
- The types involved
scalafix.internal.util.LintSyntax.XtensionDiagnostic→scalafix.internal.config.ScalafixConfig
- Direction
- scalafix.internal.util.LintSyntax uses scalafix.internal.config, so a change to scalafix.internal.config can break scalafix.internal.util.LintSyntax, while a change to scalafix.internal.util.LintSyntax can't break scalafix.internal.config.
- Position
- Below the diagonal: scalafix.internal.util.LintSyntax uses a module listed above it, which is the healthy direction.
30→2 scalafix.internal.interfaces uses scalafix.cli✕
- Connections
- 3 pairs of types, where a type in scalafix.internal.interfaces uses a type in scalafix.cli.
- The types involved
scalafix.internal.interfaces.ScalafixErrorImpl→scalafix.cli.ExitStatusscalafix.internal.interfaces.ScalafixEvaluationImpl→scalafix.cli.ExitStatusscalafix.internal.interfaces.ScalafixFileEvaluationImpl→scalafix.cli.ExitStatus
- Direction
- scalafix.internal.interfaces uses scalafix.cli, so a change to scalafix.cli can break scalafix.internal.interfaces, while a change to scalafix.internal.interfaces can't break scalafix.cli.
- Position
- Below the diagonal: scalafix.internal.interfaces uses a module listed above it, which is the healthy direction.
30→14 scalafix.internal.interfaces uses scalafix.lint✕
- Connections
- 3 pairs of types, where a type in scalafix.internal.interfaces uses a type in scalafix.lint.
- The types involved
scalafix.internal.interfaces.DelegateJavaDiagnostic→scalafix.lint.RuleDiagnosticscalafix.internal.interfaces.ScalafixDiagnosticImpl→scalafix.lint.RuleDiagnosticscalafix.internal.interfaces.ScalafixFileEvaluationImpl→scalafix.lint.RuleDiagnostic
- Direction
- scalafix.internal.interfaces uses scalafix.lint, so a change to scalafix.lint can break scalafix.internal.interfaces, while a change to scalafix.internal.interfaces can't break scalafix.lint.
- Position
- Below the diagonal: scalafix.internal.interfaces uses a module listed above it, which is the healthy direction.
30→17 scalafix.internal.interfaces uses scalafix.internal.v1✕
- Connections
- 2 pairs of types, where a type in scalafix.internal.interfaces uses a type in scalafix.internal.v1.
- The types involved
scalafix.internal.interfaces.ScalafixArgumentsImpl→scalafix.internal.v1.Argsscalafix.internal.interfaces.ScalafixFileEvaluationImpl→scalafix.internal.v1.ValidatedArgs
- Direction
- scalafix.internal.interfaces uses scalafix.internal.v1, so a change to scalafix.internal.v1 can break scalafix.internal.interfaces, while a change to scalafix.internal.interfaces can't break scalafix.internal.v1.
- Position
- Below the diagonal: scalafix.internal.interfaces uses a module listed above it, which is the healthy direction.
30→20 scalafix.internal.interfaces uses scalafix.v0✕
- Connections
- 4 pairs of types, where a type in scalafix.internal.interfaces uses a type in scalafix.v0.
- The types involved
scalafix.internal.interfaces.ScalafixFileEvaluationImpl→scalafix.v0.RuleCtxscalafix.internal.interfaces.ScalafixFileEvaluationImpl→scalafix.v0.SemanticdbIndexscalafix.internal.interfaces.ScalafixPatchImpl→scalafix.v0.RuleCtxscalafix.internal.interfaces.ScalafixPatchImpl→scalafix.v0.SemanticdbIndex
- Direction
- scalafix.internal.interfaces uses scalafix.v0, so a change to scalafix.v0 can break scalafix.internal.interfaces, while a change to scalafix.internal.interfaces can't break scalafix.v0.
- Position
- Below the diagonal: scalafix.internal.interfaces uses a module listed above it, which is the healthy direction.
30→26 scalafix.internal.interfaces uses scalafix.internal.config✕
- Connections
- 1 pair of types, where a type in scalafix.internal.interfaces uses a type in scalafix.internal.config.
- The types involved
scalafix.internal.interfaces.MainCallbackImpl→scalafix.internal.config.ScalafixReporter
- Direction
- scalafix.internal.interfaces uses scalafix.internal.config, so a change to scalafix.internal.config can break scalafix.internal.interfaces, while a change to scalafix.internal.interfaces can't break scalafix.internal.config.
- Position
- Below the diagonal: scalafix.internal.interfaces uses a module listed above it, which is the healthy direction.
30→27 scalafix.internal.interfaces uses scalafix.internal.config.ScalaVersion✕
- Connections
- 1 pair of types, where a type in scalafix.internal.interfaces uses a type in scalafix.internal.config.ScalaVersion.
- The types involved
scalafix.internal.interfaces.ScalafixPatchImpl→scalafix.internal.config.ScalaVersion.Patch
- Direction
- scalafix.internal.interfaces uses scalafix.internal.config.ScalaVersion, so a change to scalafix.internal.config.ScalaVersion can break scalafix.internal.interfaces, while a change to scalafix.internal.interfaces can't break scalafix.internal.config.ScalaVersion.
- Position
- Below the diagonal: scalafix.internal.interfaces uses a module listed above it, which is the healthy direction.
31→4 scalafix.internal.util uses scalafix.v0.SemanticdbIndex✕
- Connections
- 3 pairs of types, where a type in scalafix.internal.util uses a type in scalafix.v0.SemanticdbIndex.
- The types involved
scalafix.internal.util.DenotationOps→scalafix.v0.SemanticdbIndex.Symbolscalafix.internal.util.Pretty→scalafix.v0.SemanticdbIndex.Symbolscalafix.internal.util.SymbolOps→scalafix.v0.SemanticdbIndex.Symbol
- Direction
- scalafix.internal.util uses scalafix.v0.SemanticdbIndex, so a change to scalafix.v0.SemanticdbIndex can break scalafix.internal.util, while a change to scalafix.internal.util can't break scalafix.v0.SemanticdbIndex.
- Position
- Below the diagonal: scalafix.internal.util uses a module listed above it, which is the healthy direction.
31→6 scalafix.internal.util uses scalafix.internal.symtab✕
- Connections
- 1 pair of types, where a type in scalafix.internal.util uses a type in scalafix.internal.symtab.
- The types involved
scalafix.internal.util.PrettyType→scalafix.internal.symtab.SymbolTable
- Direction
- scalafix.internal.util uses scalafix.internal.symtab, so a change to scalafix.internal.symtab can break scalafix.internal.util, while a change to scalafix.internal.util can't break scalafix.internal.symtab.
- Position
- Below the diagonal: scalafix.internal.util uses a module listed above it, which is the healthy direction.
31→8 scalafix.internal.util uses scalafix.v0.Signature✕
- Connections
- 2 pairs of types, where a type in scalafix.internal.util uses a type in scalafix.v0.Signature.
- The types involved
scalafix.internal.util.DenotationOps→scalafix.v0.Signature.Typescalafix.internal.util.PrettyType→scalafix.v0.Signature.Type
- Direction
- scalafix.internal.util uses scalafix.v0.Signature, so a change to scalafix.v0.Signature can break scalafix.internal.util, while a change to scalafix.internal.util can't break scalafix.v0.Signature.
- Position
- Below the diagonal: scalafix.internal.util uses a module listed above it, which is the healthy direction.
31→18 scalafix.internal.util uses scalafix.v1✕
- Connections
- 6 pairs of types, where a type in scalafix.internal.util uses a type in scalafix.v1.
- The types involved
scalafix.internal.util.Pretty→scalafix.v1.Annotationscalafix.internal.util.Pretty→scalafix.v1.Constantscalafix.internal.util.Pretty→scalafix.v1.SemanticTreescalafix.internal.util.Pretty→scalafix.v1.SemanticTypescalafix.internal.util.Pretty→scalafix.v1.SymbolInformationscalafix.internal.util.PrettyType→scalafix.v1.SymbolInformation
- Direction
- scalafix.internal.util uses scalafix.v1, so a change to scalafix.v1 can break scalafix.internal.util, while a change to scalafix.internal.util can't break scalafix.v1.
- Position
- Below the diagonal: scalafix.internal.util uses a module listed above it, which is the healthy direction.
31→20 scalafix.internal.util uses scalafix.v0✕
- Connections
- 2 pairs of types, where a type in scalafix.internal.util uses a type in scalafix.v0.
- The types involved
scalafix.internal.util.DenotationOps→scalafix.v0.Denotationscalafix.internal.util.Pretty→scalafix.v0.Signature
- Direction
- scalafix.internal.util uses scalafix.v0, so a change to scalafix.v0 can break scalafix.internal.util, while a change to scalafix.internal.util can't break scalafix.v0.
- Position
- Below the diagonal: scalafix.internal.util uses a module listed above it, which is the healthy direction.
31→27 scalafix.internal.util uses scalafix.internal.config.ScalaVersion✕
- Connections
- 1 pair of types, where a type in scalafix.internal.util uses a type in scalafix.internal.config.ScalaVersion.
- The types involved
scalafix.internal.util.SuppressOps→scalafix.internal.config.ScalaVersion.Patch
- Direction
- scalafix.internal.util uses scalafix.internal.config.ScalaVersion, so a change to scalafix.internal.config.ScalaVersion can break scalafix.internal.util, while a change to scalafix.internal.util can't break scalafix.internal.config.ScalaVersion.
- Position
- Below the diagonal: scalafix.internal.util uses a module listed above it, which is the healthy direction.
32→4 scalafix.internal.v0 uses scalafix.v0.SemanticdbIndex✕
- Connections
- 2 pairs of types, where a type in scalafix.internal.v0 uses a type in scalafix.v0.SemanticdbIndex.
- The types involved
scalafix.internal.v0.LegacyInMemorySemanticdbIndex→scalafix.v0.SemanticdbIndex.Symbolscalafix.internal.v0.LegacySemanticdbIndex→scalafix.v0.SemanticdbIndex.Symbol
- Direction
- scalafix.internal.v0 uses scalafix.v0.SemanticdbIndex, so a change to scalafix.v0.SemanticdbIndex can break scalafix.internal.v0, while a change to scalafix.internal.v0 can't break scalafix.v0.SemanticdbIndex.
- Position
- Below the diagonal: scalafix.internal.v0 uses a module listed above it, which is the healthy direction.
32→6 scalafix.internal.v0 uses scalafix.internal.symtab✕
- Connections
- 2 pairs of types, where a type in scalafix.internal.v0 uses a type in scalafix.internal.symtab.
- The types involved
scalafix.internal.v0.LegacyInMemorySemanticdbIndex→scalafix.internal.symtab.SymbolTablescalafix.internal.v0.LegacySemanticdbIndex→scalafix.internal.symtab.SymbolTable
- Direction
- scalafix.internal.v0 uses scalafix.internal.symtab, so a change to scalafix.internal.symtab can break scalafix.internal.v0, while a change to scalafix.internal.v0 can't break scalafix.internal.symtab.
- Position
- Below the diagonal: scalafix.internal.v0 uses a module listed above it, which is the healthy direction.
32→7 scalafix.internal.v0 uses scalafix.util✕
- Connections
- 2 pairs of types, where a type in scalafix.internal.v0 uses a type in scalafix.util.
- The types involved
scalafix.internal.v0.LegacyRuleCtx→scalafix.util.MatchingParensscalafix.internal.v0.LegacyRuleCtx→scalafix.util.TokenList
- Direction
- scalafix.internal.v0 uses scalafix.util, so a change to scalafix.util can break scalafix.internal.v0, while a change to scalafix.internal.v0 can't break scalafix.util.
- Position
- Below the diagonal: scalafix.internal.v0 uses a module listed above it, which is the healthy direction.
32→8 scalafix.internal.v0 uses scalafix.v0.Signature✕
- Connections
- 1 pair of types, where a type in scalafix.internal.v0 uses a type in scalafix.v0.Signature.
- The types involved
scalafix.internal.v0.LegacyCodePrinter→scalafix.v0.Signature.Type
- Direction
- scalafix.internal.v0 uses scalafix.v0.Signature, so a change to scalafix.v0.Signature can break scalafix.internal.v0, while a change to scalafix.internal.v0 can't break scalafix.v0.Signature.
- Position
- Below the diagonal: scalafix.internal.v0 uses a module listed above it, which is the healthy direction.
32→18 scalafix.internal.v0 uses scalafix.v1✕
- Connections
- 9 pairs of types, where a type in scalafix.internal.v0 uses a type in scalafix.v1.
- The types involved
scalafix.internal.v0.LegacyCodePrinter→scalafix.v1.Constantscalafix.internal.v0.LegacyInMemorySemanticdbIndex→scalafix.v1.SymbolInformationscalafix.internal.v0.LegacySemanticRule→scalafix.v1.Configurationscalafix.internal.v0.LegacySemanticRule→scalafix.v1.SemanticDocumentscalafix.internal.v0.LegacySemanticdbIndex→scalafix.v1.SemanticDocumentscalafix.internal.v0.LegacySemanticdbIndex→scalafix.v1.SymbolInformationscalafix.internal.v0.LegacySyntacticRule→scalafix.v1.Configurationscalafix.internal.v0.LegacySyntacticRule→scalafix.v1.SyntacticDocumentscalafix.internal.v0.LegacySyntacticRule→scalafix.v1.SyntacticRule
- Direction
- scalafix.internal.v0 uses scalafix.v1, so a change to scalafix.v1 can break scalafix.internal.v0, while a change to scalafix.internal.v0 can't break scalafix.v1.
- Position
- Below the diagonal: scalafix.internal.v0 uses a module listed above it, which is the healthy direction.
32→19 scalafix.internal.v0 uses scalafix.internal.patch✕
- Connections
- 3 pairs of types, where a type in scalafix.internal.v0 uses a type in scalafix.internal.patch.
- The types involved
scalafix.internal.v0.LegacyInMemorySemanticdbIndex→scalafix.internal.patch.CrashingSemanticdbIndexscalafix.internal.v0.LegacyRuleCtx→scalafix.internal.patch.LegacyPatchOpsscalafix.internal.v0.LegacySemanticdbIndex→scalafix.internal.patch.CrashingSemanticdbIndex
- Direction
- scalafix.internal.v0 uses scalafix.internal.patch, so a change to scalafix.internal.patch can break scalafix.internal.v0, while a change to scalafix.internal.v0 can't break scalafix.internal.patch.
- Position
- Below the diagonal: scalafix.internal.v0 uses a module listed above it, which is the healthy direction.
32→20 scalafix.internal.v0 uses scalafix.v0✕
- Connections
- 24 pairs of types, where a type in scalafix.internal.v0 uses a type in scalafix.v0.
- The types involved
scalafix.internal.v0.LegacyCodePrinter→scalafix.v0.Denotationscalafix.internal.v0.LegacyCodePrinter→scalafix.v0.Signaturescalafix.internal.v0.LegacyCodePrinter→scalafix.v0.Syntheticscalafix.internal.v0.LegacyInMemorySemanticdbIndex→scalafix.v0.Databasescalafix.internal.v0.LegacyInMemorySemanticdbIndex→scalafix.v0.Denotationscalafix.internal.v0.LegacyInMemorySemanticdbIndex→scalafix.v0.Documentscalafix.internal.v0.LegacyInMemorySemanticdbIndex→scalafix.v0.ResolvedNamescalafix.internal.v0.LegacyInMemorySemanticdbIndex→scalafix.v0.SemanticdbIndexscalafix.internal.v0.LegacyInMemorySemanticdbIndex→scalafix.v0.Syntheticscalafix.internal.v0.LegacyRule→scalafix.v0.Rulescalafix.internal.v0.LegacyRule→scalafix.v0.RuleCtxscalafix.internal.v0.LegacyRule→scalafix.v0.SemanticdbIndexscalafix.internal.v0.LegacyRuleCtx→scalafix.v0.RuleCtxscalafix.internal.v0.LegacyRuleCtx→scalafix.v0.SemanticdbIndexscalafix.internal.v0.LegacySemanticRule→scalafix.v0.Rulescalafix.internal.v0.LegacySemanticRule→scalafix.v0.SemanticRulescalafix.internal.v0.LegacySemanticdbIndex→scalafix.v0.Databasescalafix.internal.v0.LegacySemanticdbIndex→scalafix.v0.Denotationscalafix.internal.v0.LegacySemanticdbIndex→scalafix.v0.Documentscalafix.internal.v0.LegacySemanticdbIndex→scalafix.v0.Messagescalafix.internal.v0.LegacySemanticdbIndex→scalafix.v0.ResolvedNamescalafix.internal.v0.LegacySemanticdbIndex→scalafix.v0.ResolvedSymbolscalafix.internal.v0.LegacySemanticdbIndex→scalafix.v0.Syntheticscalafix.internal.v0.LegacySyntacticRule→scalafix.v0.Rule
- Direction
- scalafix.internal.v0 uses scalafix.v0, so a change to scalafix.v0 can break scalafix.internal.v0, while a change to scalafix.internal.v0 can't break scalafix.v0.
- Position
- Below the diagonal: scalafix.internal.v0 uses a module listed above it, which is the healthy direction.
32→27 scalafix.internal.v0 uses scalafix.internal.config.ScalaVersion✕
- Connections
- 3 pairs of types, where a type in scalafix.internal.v0 uses a type in scalafix.internal.config.ScalaVersion.
- The types involved
scalafix.internal.v0.LegacyRule→scalafix.internal.config.ScalaVersion.Patchscalafix.internal.v0.LegacySemanticRule→scalafix.internal.config.ScalaVersion.Patchscalafix.internal.v0.LegacySyntacticRule→scalafix.internal.config.ScalaVersion.Patch
- Direction
- scalafix.internal.v0 uses scalafix.internal.config.ScalaVersion, so a change to scalafix.internal.config.ScalaVersion can break scalafix.internal.v0, while a change to scalafix.internal.v0 can't break scalafix.internal.config.ScalaVersion.
- Position
- Below the diagonal: scalafix.internal.v0 uses a module listed above it, which is the healthy direction.
33→12 scalafix.v0.Rule uses scalafix.rule✕
- Connections
- 1 pair of types, where a type in scalafix.v0.Rule uses a type in scalafix.rule.
- The types involved
scalafix.v0.Rule.CompositeRule→scalafix.rule.RuleName
- Direction
- scalafix.v0.Rule uses scalafix.rule, so a change to scalafix.rule can break scalafix.v0.Rule, while a change to scalafix.v0.Rule can't break scalafix.rule.
- Position
- Below the diagonal: scalafix.v0.Rule uses a module listed above it, which is the healthy direction.
33→14 scalafix.v0.Rule uses scalafix.lint✕
- Connections
- 1 pair of types, where a type in scalafix.v0.Rule uses a type in scalafix.lint.
- The types involved
scalafix.v0.Rule.CompositeRule→scalafix.lint.Diagnostic
- Direction
- scalafix.v0.Rule uses scalafix.lint, so a change to scalafix.lint can break scalafix.v0.Rule, while a change to scalafix.v0.Rule can't break scalafix.lint.
- Position
- Below the diagonal: scalafix.v0.Rule uses a module listed above it, which is the healthy direction.
33→20 scalafix.v0.Rule uses scalafix.v0✕
- Connections
- 3 pairs of types, where a type in scalafix.v0.Rule uses a type in scalafix.v0.
- The types involved
scalafix.v0.Rule.CompositeRule→scalafix.v0.Rulescalafix.v0.Rule.CompositeRule→scalafix.v0.RuleCtxscalafix.v0.Rule.CompositeRule→scalafix.v0.SemanticdbIndex
- Direction
- scalafix.v0.Rule uses scalafix.v0, so a change to scalafix.v0 can break scalafix.v0.Rule, while a change to scalafix.v0.Rule can't break scalafix.v0.
- Position
- Below the diagonal: scalafix.v0.Rule uses a module listed above it, which is the healthy direction.
33→27 scalafix.v0.Rule uses scalafix.internal.config.ScalaVersion✕
- Connections
- 1 pair of types, where a type in scalafix.v0.Rule uses a type in scalafix.internal.config.ScalaVersion.
- The types involved
scalafix.v0.Rule.CompositeRule→scalafix.internal.config.ScalaVersion.Patch
- Direction
- scalafix.v0.Rule uses scalafix.internal.config.ScalaVersion, so a change to scalafix.internal.config.ScalaVersion can break scalafix.v0.Rule, while a change to scalafix.v0.Rule can't break scalafix.internal.config.ScalaVersion.
- Position
- Below the diagonal: scalafix.v0.Rule uses a module listed above it, which is the healthy direction.
34→20 scalafix.internal.util.Failure uses scalafix.v0✕
- Connections
- 1 pair of types, where a type in scalafix.internal.util.Failure uses a type in scalafix.v0.
- The types involved
scalafix.internal.util.Failure.MismatchingSemanticdbIndex→scalafix.v0.SemanticdbIndex
- Direction
- scalafix.internal.util.Failure uses scalafix.v0, so a change to scalafix.v0 can break scalafix.internal.util.Failure, while a change to scalafix.internal.util.Failure can't break scalafix.v0.
- Position
- Below the diagonal: scalafix.internal.util.Failure uses a module listed above it, which is the healthy direction.
34→27 scalafix.internal.util.Failure uses scalafix.internal.config.ScalaVersion✕
- Connections
- 1 pair of types, where a type in scalafix.internal.util.Failure uses a type in scalafix.internal.config.ScalaVersion.
- The types involved
scalafix.internal.util.Failure.TokenPatchMergeError→scalafix.internal.config.ScalaVersion.Patch
- Direction
- scalafix.internal.util.Failure uses scalafix.internal.config.ScalaVersion, so a change to scalafix.internal.config.ScalaVersion can break scalafix.internal.util.Failure, while a change to scalafix.internal.util.Failure can't break scalafix.internal.config.ScalaVersion.
- Position
- Below the diagonal: scalafix.internal.util.Failure uses a module listed above it, which is the healthy direction.
34→31 scalafix.internal.util.Failure uses scalafix.internal.util✕
- Connections
- 4 pairs of types, where a type in scalafix.internal.util.Failure uses a type in scalafix.internal.util.
- The types involved
scalafix.internal.util.Failure.InvariantFailedException→scalafix.internal.util.Failurescalafix.internal.util.Failure.MismatchingSemanticdbIndex→scalafix.internal.util.Failurescalafix.internal.util.Failure.TokenPatchMergeError→scalafix.internal.util.Failurescalafix.internal.util.Failure.Unsupported→scalafix.internal.util.Failure
- Direction
- scalafix.internal.util.Failure uses scalafix.internal.util, so a change to scalafix.internal.util can break scalafix.internal.util.Failure, while a change to scalafix.internal.util.Failure can't break scalafix.internal.util.
- Position
- Below the diagonal: scalafix.internal.util.Failure uses a module listed above it, which is the healthy direction.
35→31 scalafix.internal.util.QualifyStrategy uses scalafix.internal.util✕
- Connections
- 3 pairs of types, where a type in scalafix.internal.util.QualifyStrategy uses a type in scalafix.internal.util.
- The types involved
scalafix.internal.util.QualifyStrategy.Full→scalafix.internal.util.QualifyStrategyscalafix.internal.util.QualifyStrategy.Name→scalafix.internal.util.QualifyStrategyscalafix.internal.util.QualifyStrategy.Readable→scalafix.internal.util.QualifyStrategy
- Direction
- scalafix.internal.util.QualifyStrategy uses scalafix.internal.util, so a change to scalafix.internal.util can break scalafix.internal.util.QualifyStrategy, while a change to scalafix.internal.util.QualifyStrategy can't break scalafix.internal.util.
- Position
- Below the diagonal: scalafix.internal.util.QualifyStrategy uses a module listed above it, which is the healthy direction.
36→35 scala.meta.internal.pc uses scalafix.internal.util.QualifyStrategy✕
- Connections
- 1 pair of types, where a type in scala.meta.internal.pc uses a type in scalafix.internal.util.QualifyStrategy.
- The types involved
scala.meta.internal.pc.Identifier→scalafix.internal.util.QualifyStrategy.Name
- Direction
- scala.meta.internal.pc uses scalafix.internal.util.QualifyStrategy, so a change to scalafix.internal.util.QualifyStrategy can break scala.meta.internal.pc, while a change to scala.meta.internal.pc can't break scalafix.internal.util.QualifyStrategy.
- Position
- Below the diagonal: scala.meta.internal.pc uses a module listed above it, which is the healthy direction.
37→4 scala.meta.internal.pc.ScalafixGlobal uses scalafix.v0.SemanticdbIndex✕
- Connections
- 3 pairs of types, where a type in scala.meta.internal.pc.ScalafixGlobal uses a type in scalafix.v0.SemanticdbIndex.
- The types involved
scala.meta.internal.pc.ScalafixGlobal.ShortName→scalafix.v0.SemanticdbIndex.Symbolscala.meta.internal.pc.ScalafixGlobal.ShortenedNames→scalafix.v0.SemanticdbIndex.Symbolscala.meta.internal.pc.ScalafixGlobal.XtensionSymbolMetals→scalafix.v0.SemanticdbIndex.Symbol
- Direction
- scala.meta.internal.pc.ScalafixGlobal uses scalafix.v0.SemanticdbIndex, so a change to scalafix.v0.SemanticdbIndex can break scala.meta.internal.pc.ScalafixGlobal, while a change to scala.meta.internal.pc.ScalafixGlobal can't break scalafix.v0.SemanticdbIndex.
- Position
- Below the diagonal: scala.meta.internal.pc.ScalafixGlobal uses a module listed above it, which is the healthy direction.
37→8 scala.meta.internal.pc.ScalafixGlobal uses scalafix.v0.Signature✕
- Connections
- 2 pairs of types, where a type in scala.meta.internal.pc.ScalafixGlobal uses a type in scalafix.v0.Signature.
- The types involved
scala.meta.internal.pc.ScalafixGlobal.PrettyType→scalafix.v0.Signature.Typescala.meta.internal.pc.ScalafixGlobal.ShortenedNames→scalafix.v0.Signature.Type
- Direction
- scala.meta.internal.pc.ScalafixGlobal uses scalafix.v0.Signature, so a change to scalafix.v0.Signature can break scala.meta.internal.pc.ScalafixGlobal, while a change to scala.meta.internal.pc.ScalafixGlobal can't break scalafix.v0.Signature.
- Position
- Below the diagonal: scala.meta.internal.pc.ScalafixGlobal uses a module listed above it, which is the healthy direction.
37→35 scala.meta.internal.pc.ScalafixGlobal uses scalafix.internal.util.QualifyStrategy✕
- Connections
- 3 pairs of types, where a type in scala.meta.internal.pc.ScalafixGlobal uses a type in scalafix.internal.util.QualifyStrategy.
- The types involved
scala.meta.internal.pc.ScalafixGlobal.ShortName→scalafix.internal.util.QualifyStrategy.Namescala.meta.internal.pc.ScalafixGlobal.ShortenedNames→scalafix.internal.util.QualifyStrategy.Namescala.meta.internal.pc.ScalafixGlobal.XtensionNameMetals→scalafix.internal.util.QualifyStrategy.Name
- Direction
- scala.meta.internal.pc.ScalafixGlobal uses scalafix.internal.util.QualifyStrategy, so a change to scalafix.internal.util.QualifyStrategy can break scala.meta.internal.pc.ScalafixGlobal, while a change to scala.meta.internal.pc.ScalafixGlobal can't break scalafix.internal.util.QualifyStrategy.
- Position
- Below the diagonal: scala.meta.internal.pc.ScalafixGlobal uses a module listed above it, which is the healthy direction.
38→18 scalafix.internal.pc uses scalafix.v1✕
- Connections
- 1 pair of types, where a type in scalafix.internal.pc uses a type in scalafix.v1.
- The types involved
scalafix.internal.pc.PresentationCompilerTypeInferrer→scalafix.v1.SemanticDocument
- Direction
- scalafix.internal.pc uses scalafix.v1, so a change to scalafix.v1 can break scalafix.internal.pc, while a change to scalafix.internal.pc can't break scalafix.v1.
- Position
- Below the diagonal: scalafix.internal.pc uses a module listed above it, which is the healthy direction.
38→27 scalafix.internal.pc uses scalafix.internal.config.ScalaVersion✕
- Connections
- 1 pair of types, where a type in scalafix.internal.pc uses a type in scalafix.internal.config.ScalaVersion.
- The types involved
scalafix.internal.pc.PresentationCompilerTypeInferrer→scalafix.internal.config.ScalaVersion.Patch
- Direction
- scalafix.internal.pc uses scalafix.internal.config.ScalaVersion, so a change to scalafix.internal.config.ScalaVersion can break scalafix.internal.pc, while a change to scalafix.internal.pc can't break scalafix.internal.config.ScalaVersion.
- Position
- Below the diagonal: scalafix.internal.pc uses a module listed above it, which is the healthy direction.
38→35 scalafix.internal.pc uses scalafix.internal.util.QualifyStrategy✕
- Connections
- 1 pair of types, where a type in scalafix.internal.pc uses a type in scalafix.internal.util.QualifyStrategy.
- The types involved
scalafix.internal.pc.PresentationCompilerTypeInferrer→scalafix.internal.util.QualifyStrategy.Name
- Direction
- scalafix.internal.pc uses scalafix.internal.util.QualifyStrategy, so a change to scalafix.internal.util.QualifyStrategy can break scalafix.internal.pc, while a change to scalafix.internal.pc can't break scalafix.internal.util.QualifyStrategy.
- Position
- Below the diagonal: scalafix.internal.pc uses a module listed above it, which is the healthy direction.
39→8 scalafix.internal.util.PrettyType uses scalafix.v0.Signature✕
- Connections
- 2 pairs of types, where a type in scalafix.internal.util.PrettyType uses a type in scalafix.v0.Signature.
- The types involved
scalafix.internal.util.PrettyType.XtensionSchemaType→scalafix.v0.Signature.Typescalafix.internal.util.PrettyType.XtensionSymbolInformationProperties→scalafix.v0.Signature.Type
- Direction
- scalafix.internal.util.PrettyType uses scalafix.v0.Signature, so a change to scalafix.v0.Signature can break scalafix.internal.util.PrettyType, while a change to scalafix.internal.util.PrettyType can't break scalafix.v0.Signature.
- Position
- Below the diagonal: scalafix.internal.util.PrettyType uses a module listed above it, which is the healthy direction.
39→18 scalafix.internal.util.PrettyType uses scalafix.v1✕
- Connections
- 1 pair of types, where a type in scalafix.internal.util.PrettyType uses a type in scalafix.v1.
- The types involved
scalafix.internal.util.PrettyType.XtensionScopeHardlinks→scalafix.v1.SymbolInformation
- Direction
- scalafix.internal.util.PrettyType uses scalafix.v1, so a change to scalafix.v1 can break scalafix.internal.util.PrettyType, while a change to scalafix.internal.util.PrettyType can't break scalafix.v1.
- Position
- Below the diagonal: scalafix.internal.util.PrettyType uses a module listed above it, which is the healthy direction.
39→35 scalafix.internal.util.PrettyType uses scalafix.internal.util.QualifyStrategy✕
- Connections
- 1 pair of types, where a type in scalafix.internal.util.PrettyType uses a type in scalafix.internal.util.QualifyStrategy.
- The types involved
scalafix.internal.util.PrettyType.XtensionSymbolInfo→scalafix.internal.util.QualifyStrategy.Name
- Direction
- scalafix.internal.util.PrettyType uses scalafix.internal.util.QualifyStrategy, so a change to scalafix.internal.util.QualifyStrategy can break scalafix.internal.util.PrettyType, while a change to scalafix.internal.util.PrettyType can't break scalafix.internal.util.QualifyStrategy.
- Position
- Below the diagonal: scalafix.internal.util.PrettyType uses a module listed above it, which is the healthy direction.
40→3 scalafix.internal.rule uses scalafix.config✕
- Connections
- 4 pairs of types, where a type in scalafix.internal.rule uses a type in scalafix.config.
- The types involved
scalafix.internal.rule.DisableSyntaxConfig→scalafix.config.CustomMessagescalafix.internal.rule.DisableSyntaxConfig→scalafix.config.Regexscalafix.internal.rule.TPrintImplicits→scalafix.config.CustomMessagescalafix.internal.rule.TPrintImplicits→scalafix.config.Regex
- Direction
- scalafix.internal.rule uses scalafix.config, so a change to scalafix.config can break scalafix.internal.rule, while a change to scalafix.internal.rule can't break scalafix.config.
- Position
- Below the diagonal: scalafix.internal.rule uses a module listed above it, which is the healthy direction.
40→4 scalafix.internal.rule uses scalafix.v0.SemanticdbIndex✕
- Connections
- 1 pair of types, where a type in scalafix.internal.rule uses a type in scalafix.v0.SemanticdbIndex.
- The types involved
scalafix.internal.rule.CompilerTypePrinter→scalafix.v0.SemanticdbIndex.Symbol
- Direction
- scalafix.internal.rule uses scalafix.v0.SemanticdbIndex, so a change to scalafix.v0.SemanticdbIndex can break scalafix.internal.rule, while a change to scalafix.internal.rule can't break scalafix.v0.SemanticdbIndex.
- Position
- Below the diagonal: scalafix.internal.rule uses a module listed above it, which is the healthy direction.
40→7 scalafix.internal.rule uses scalafix.util✕
- Connections
- 2 pairs of types, where a type in scalafix.internal.rule uses a type in scalafix.util.
- The types involved
scalafix.internal.rule.RuleCtxImpl→scalafix.util.MatchingParensscalafix.internal.rule.RuleCtxImpl→scalafix.util.TokenList
- Direction
- scalafix.internal.rule uses scalafix.util, so a change to scalafix.util can break scalafix.internal.rule, while a change to scalafix.internal.rule can't break scalafix.util.
- Position
- Below the diagonal: scalafix.internal.rule uses a module listed above it, which is the healthy direction.
40→8 scalafix.internal.rule uses scalafix.v0.Signature✕
- Connections
- 4 pairs of types, where a type in scalafix.internal.rule uses a type in scalafix.v0.Signature.
- The types involved
scalafix.internal.rule.CompilerTypePrinter→scalafix.v0.Signature.Typescalafix.internal.rule.ExplicitResultTypesBase→scalafix.v0.Signature.Termscalafix.internal.rule.NoAutoTupling→scalafix.v0.Signature.Termscalafix.internal.rule.SimpleDefinitions→scalafix.v0.Signature.Term
- Direction
- scalafix.internal.rule uses scalafix.v0.Signature, so a change to scalafix.v0.Signature can break scalafix.internal.rule, while a change to scalafix.internal.rule can't break scalafix.v0.Signature.
- Position
- Below the diagonal: scalafix.internal.rule uses a module listed above it, which is the healthy direction.
40→14 scalafix.internal.rule uses scalafix.lint✕
- Connections
- 6 pairs of types, where a type in scalafix.internal.rule uses a type in scalafix.lint.
- The types involved
scalafix.internal.rule.DisableSyntax→scalafix.lint.Diagnosticscalafix.internal.rule.ImporterSymbolNotFound→scalafix.lint.Diagnosticscalafix.internal.rule.ImporterSymbolNotFound→scalafix.lint.LintSeverityscalafix.internal.rule.OrganizeImports→scalafix.lint.Diagnosticscalafix.internal.rule.TooManyAliases→scalafix.lint.Diagnosticscalafix.internal.rule.TooManyAliases→scalafix.lint.LintSeverity
- Direction
- scalafix.internal.rule uses scalafix.lint, so a change to scalafix.lint can break scalafix.internal.rule, while a change to scalafix.internal.rule can't break scalafix.lint.
- Position
- Below the diagonal: scalafix.internal.rule uses a module listed above it, which is the healthy direction.
40→18 scalafix.internal.rule uses scalafix.v1✕
- Connections
- 23 pairs of types, where a type in scalafix.internal.rule uses a type in scalafix.v1.
- The types involved
scalafix.internal.rule.DisableSyntax→scalafix.v1.Configurationscalafix.internal.rule.DisableSyntax→scalafix.v1.SyntacticDocumentscalafix.internal.rule.DisableSyntax→scalafix.v1.SyntacticRulescalafix.internal.rule.ExplicitResultTypes→scalafix.v1.Configurationscalafix.internal.rule.ExplicitResultTypes→scalafix.v1.SemanticDocumentscalafix.internal.rule.ExplicitResultTypesBase→scalafix.v1.SemanticDocumentscalafix.internal.rule.LeakingImplicitClassVal→scalafix.v1.SyntacticDocumentscalafix.internal.rule.LeakingImplicitClassVal→scalafix.v1.SyntacticRulescalafix.internal.rule.NoAutoTupling→scalafix.v1.SemanticDocumentscalafix.internal.rule.NoValInForComprehension→scalafix.v1.SyntacticDocumentscalafix.internal.rule.NoValInForComprehension→scalafix.v1.SyntacticRulescalafix.internal.rule.OrganizeImports→scalafix.v1.Configurationscalafix.internal.rule.OrganizeImports→scalafix.v1.SemanticDocumentscalafix.internal.rule.Printer→scalafix.v1.SemanticDocumentscalafix.internal.rule.ProcedureSyntax→scalafix.v1.SyntacticDocumentscalafix.internal.rule.ProcedureSyntax→scalafix.v1.SyntacticRulescalafix.internal.rule.RedundantSyntax→scalafix.v1.Configurationscalafix.internal.rule.RedundantSyntax→scalafix.v1.SyntacticDocumentscalafix.internal.rule.RedundantSyntax→scalafix.v1.SyntacticRulescalafix.internal.rule.RemoveUnused→scalafix.v1.Configurationscalafix.internal.rule.RemoveUnused→scalafix.v1.SemanticDocumentscalafix.internal.rule.Scala2Printer→scalafix.v1.SemanticDocumentscalafix.internal.rule.Scala3Printer→scalafix.v1.SemanticDocument
- Direction
- scalafix.internal.rule uses scalafix.v1, so a change to scalafix.v1 can break scalafix.internal.rule, while a change to scalafix.internal.rule can't break scalafix.v1.
- Position
- Below the diagonal: scalafix.internal.rule uses a module listed above it, which is the healthy direction.
40→19 scalafix.internal.rule uses scalafix.internal.patch✕
- Connections
- 2 pairs of types, where a type in scalafix.internal.rule uses a type in scalafix.internal.patch.
- The types involved
scalafix.internal.rule.RuleCtxImpl→scalafix.internal.patch.EscapeHatchscalafix.internal.rule.RuleCtxImpl→scalafix.internal.patch.LegacyPatchOps
- Direction
- scalafix.internal.rule uses scalafix.internal.patch, so a change to scalafix.internal.patch can break scalafix.internal.rule, while a change to scalafix.internal.rule can't break scalafix.internal.patch.
- Position
- Below the diagonal: scalafix.internal.rule uses a module listed above it, which is the healthy direction.
40→20 scalafix.internal.rule uses scalafix.v0✕
- Connections
- 12 pairs of types, where a type in scalafix.internal.rule uses a type in scalafix.v0.
- The types involved
scalafix.internal.rule.DisableSyntax→scalafix.v0.LintCategoryscalafix.internal.rule.DisableSyntax→scalafix.v0.Rulescalafix.internal.rule.ExplicitResultTypes→scalafix.v0.Rulescalafix.internal.rule.ExplicitResultTypesBase→scalafix.v0.SemanticRulescalafix.internal.rule.NoAutoTupling→scalafix.v0.SemanticRulescalafix.internal.rule.OrganizeImports→scalafix.v0.Rulescalafix.internal.rule.OrganizeImports→scalafix.v0.SemanticRulescalafix.internal.rule.RedundantSyntax→scalafix.v0.Rulescalafix.internal.rule.RemoveUnused→scalafix.v0.Rulescalafix.internal.rule.RemoveUnused→scalafix.v0.SemanticRulescalafix.internal.rule.RuleCtxImpl→scalafix.v0.RuleCtxscalafix.internal.rule.RuleCtxImpl→scalafix.v0.SemanticdbIndex
- Direction
- scalafix.internal.rule uses scalafix.v0, so a change to scalafix.v0 can break scalafix.internal.rule, while a change to scalafix.internal.rule can't break scalafix.v0.
- Position
- Below the diagonal: scalafix.internal.rule uses a module listed above it, which is the healthy direction.
40→26 scalafix.internal.rule uses scalafix.internal.config✕
- Connections
- 1 pair of types, where a type in scalafix.internal.rule uses a type in scalafix.internal.config.
- The types involved
scalafix.internal.rule.RuleCtxImpl→scalafix.internal.config.ScalafixConfig
- Direction
- scalafix.internal.rule uses scalafix.internal.config, so a change to scalafix.internal.config can break scalafix.internal.rule, while a change to scalafix.internal.rule can't break scalafix.internal.config.
- Position
- Below the diagonal: scalafix.internal.rule uses a module listed above it, which is the healthy direction.
40→27 scalafix.internal.rule uses scalafix.internal.config.ScalaVersion✕
- Connections
- 14 pairs of types, where a type in scalafix.internal.rule uses a type in scalafix.internal.config.ScalaVersion.
- The types involved
scalafix.internal.rule.CompilerTypePrinter→scalafix.internal.config.ScalaVersion.Patchscalafix.internal.rule.DisableSyntax→scalafix.internal.config.ScalaVersion.Patchscalafix.internal.rule.ExplicitResultTypes→scalafix.internal.config.ScalaVersion.Patchscalafix.internal.rule.ExplicitResultTypesBase→scalafix.internal.config.ScalaVersion.Patchscalafix.internal.rule.LeakingImplicitClassVal→scalafix.internal.config.ScalaVersion.Patchscalafix.internal.rule.NoAutoTupling→scalafix.internal.config.ScalaVersion.Patchscalafix.internal.rule.NoValInForComprehension→scalafix.internal.config.ScalaVersion.Patchscalafix.internal.rule.OrganizeImports→scalafix.internal.config.ScalaVersion.Patchscalafix.internal.rule.Printer→scalafix.internal.config.ScalaVersion.Patchscalafix.internal.rule.ProcedureSyntax→scalafix.internal.config.ScalaVersion.Patchscalafix.internal.rule.RedundantSyntax→scalafix.internal.config.ScalaVersion.Patchscalafix.internal.rule.RemoveUnused→scalafix.internal.config.ScalaVersion.Patchscalafix.internal.rule.Scala2Printer→scalafix.internal.config.ScalaVersion.Patchscalafix.internal.rule.Scala3Printer→scalafix.internal.config.ScalaVersion.Patch
- Direction
- scalafix.internal.rule uses scalafix.internal.config.ScalaVersion, so a change to scalafix.internal.config.ScalaVersion can break scalafix.internal.rule, while a change to scalafix.internal.rule can't break scalafix.internal.config.ScalaVersion.
- Position
- Below the diagonal: scalafix.internal.rule uses a module listed above it, which is the healthy direction.
40→35 scalafix.internal.rule uses scalafix.internal.util.QualifyStrategy✕
- Connections
- 3 pairs of types, where a type in scalafix.internal.rule uses a type in scalafix.internal.util.QualifyStrategy.
- The types involved
scalafix.internal.rule.DisableSyntax→scalafix.internal.util.QualifyStrategy.Namescalafix.internal.rule.ImporterSymbolNotFound→scalafix.internal.util.QualifyStrategy.Namescalafix.internal.rule.TooManyAliases→scalafix.internal.util.QualifyStrategy.Name
- Direction
- scalafix.internal.rule uses scalafix.internal.util.QualifyStrategy, so a change to scalafix.internal.util.QualifyStrategy can break scalafix.internal.rule, while a change to scalafix.internal.rule can't break scalafix.internal.util.QualifyStrategy.
- Position
- Below the diagonal: scalafix.internal.rule uses a module listed above it, which is the healthy direction.
40→37 scalafix.internal.rule uses scala.meta.internal.pc.ScalafixGlobal✕
- Connections
- 1 pair of types, where a type in scalafix.internal.rule uses a type in scala.meta.internal.pc.ScalafixGlobal.
- The types involved
scalafix.internal.rule.CompilerTypePrinter→scala.meta.internal.pc.ScalafixGlobal.ShortenedNames
- Direction
- scalafix.internal.rule uses scala.meta.internal.pc.ScalafixGlobal, so a change to scala.meta.internal.pc.ScalafixGlobal can break scalafix.internal.rule, while a change to scalafix.internal.rule can't break scala.meta.internal.pc.ScalafixGlobal.
- Position
- Below the diagonal: scalafix.internal.rule uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 20 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 8 | Medium |
Roadmap
Begin by implementing diagnostic logging with verbose flags to capture error paths that currently go unreported, ensuring users can provide actionable bug data. Simultaneously, establish architectural decision records in a dedicated folder and expand the README with clear getting-started and architecture guides to improve project discoverability. Next, resolve the thirty orphaned files, prioritizing ScalafixArguments.java, Pretty.scala, and Rule.scala, to clean up the codebase. Finally, improve allocation hygiene on hot paths by adopting idioms that reduce unnecessary object creation.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +3.9 pts | Medium | Observability |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.4 pts | Medium | Architecture documentation |
| Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with ScalafixGlobal.scala. | +1.7 pts | Low | Knowledge Freshness |
| Expand the README with getting-started, architecture overview and a project map. | +3.3 pts | Medium | Documentation (README) |
| Resolve the 30 Orphaned file finding(s) in Knowledge Freshness — start with ScalafixArguments.java, Pretty.scala, Rule.scala. | +2.9 pts | Medium | Knowledge Freshness |
| Raise allocation-aware density on the hot paths — currently 17 use(s) across 20,971 production line(s) (~0.8/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10. | +1.8 pts | Medium | Allocation hygiene |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +1.8 pts | Medium | Deployment & Rollback |
| Resolve the 2 Off-boarding risk finding(s) in Bus Factor. | +0.9 pts | Low | Bus Factor |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| scalafix-core/src/main/scala/scalafix/internal/patch/ImportPatchOps.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| scalafix-core/src/main/scala-2/scalafix/internal/util/PrettyType.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| scalafix-rules/src/main/scala/scalafix/internal/rule/OrganizeImports.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| compat-metaconfig-macros/src/main/scala-3/metaconfig/pprint/TPrintImpl.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| project/ScalafixBuild.scala | 6.2 | Mixed | Change Coupling: Boundary-crossing change coupling: ScalafixBuild.scala ↔ ScalafixImpl.scala |
| scalafix-tests/output/src/main/scala-2/test/explicitResultTypes/RscCompat.scala | 6.4 | Mixed | Explicit Debt: TodoComment |
| scalafix-tests/input/src/main/scala-2/test/explicitResultTypes/RscCompat.scala | 6.4 | Mixed | Explicit Debt: TodoComment |
| scalafix-core/src/main/scala/scalafix/internal/v0/LegacyCodePrinter.scala | 6.9 | Mixed | Explicit Debt: TodoComment |
| scalafix-rules/src/main/scala-2/scalafix/internal/pc/ScalafixGlobal.scala | 7.2 | Mixed | Cyclomatic Complexity: ScalafixGlobal.shortType (cyclomatic 37) |
| scalafix-rules/src/main/scala/scalafix/internal/rule/DisableSyntax.scala | 7.2 | Mixed | Cyclomatic Complexity: DisableSyntax.checkTree (cyclomatic 30) |
| scalafix-rules/src/main/scala-2/scalafix/internal/rule/CompilerTypePrinter.scala | 7.2 | Mixed | Cyclomatic Complexity: CompilerTypePrinter.preProcess (cyclomatic 21) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| scalafix-core/src/main/scala/scalafix/internal/util/Pretty.scala | 7.4 | Mixed | Cyclomatic Complexity: Pretty.pretty (cyclomatic 28) |
| scalafix-rules/src/main/scala/scalafix/internal/rule/RemoveUnused.scala | 7.8 | Mixed | Cyclomatic Complexity: RemoveUnused.fix (cyclomatic 47) |
| scalafix-core/src/main/scala/scalafix/v0/HasFlags.scala | 7.8 | Mixed | Cyclomatic Complexity: HasFlags.flagSyntax (cyclomatic 34) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 62 of 62 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 62 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 163 of 184 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.scala) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) and this repository declares an sbt build (repository root, 63 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its sbt dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D19 Documentation Quality — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (build.sbt), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `compat-metaconfig-macros/src/main/scala-3/metaconfig/generic/package.scala` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
- C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). 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.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
20 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was RemoveUnused.fix at 47. A further 3 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being TreePos.symbolImpl at 34 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: scalafix-core/src/main/scala/scalafix/internal/v1/TreePos.scala (TreePos.symbolImpl at 34), scalafix-core/src/main/scala/scalafix/internal/v0/LegacyCodePrinter.scala (LegacyCodePrinter.pprint at 21), scalafix-core/src/main/scala/scalafix/internal/v1/SymtabFromProtobuf.scala (SymtabFromProtobuf.stype at 18). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 20 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with RemoveUnused.fix (cyclomatic 47), ScalafixGlobal.shortType (cyclomatic 37), ImportPatchOps.superNaiveImportPatchToTokenPatchConverter (cyclomatic 34). — 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 20 together lifts Cyclomatic Complexity from 7.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
27 method(s) exceeded the cognitive complexity threshold of 15; the worst was PrettyType.toTree at 64.
What to do
- Bring the 27 bodies over 15 down to 15 or less in Cognitive Complexity — start with PrettyType.toTree (cognitive 64), ScalafixGlobal.shortType (cognitive 63), Symbol.apply (cognitive 57). — 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 27 together lifts Cognitive Complexity from 6.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
2 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 FileTooLong finding(s) in God Classes — start with OrganizeImports.scala, PrettyType.scala. — One of this dimension's main actionable groups (2 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
3 duplicated block group(s) detected.
What to do
- Resolve the 3 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with DisableSyntax.scala, RuleInstrumentation.scala, PresentationCompilerTypeInferrer.scala. — One of this dimension's main actionable groups (3 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
15 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; 1 module(s) off the main sequence, with abstractness counted on 11 of the 15 (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).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
1 of 25 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with InternalSemanticDoc.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
174 test methods: 106 unit, 68 integration, 0 BDD, 0 e2e. The Scala suite contributes 174 test case(s) across 35 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
D12 · Dependency Hygiene
3 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.
What to do
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 6 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. 2 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 2 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's sbt dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
11 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is scalafix-rules/src/main/scala-2/scalafix/internal/rule/CompilerTypePrinter.scala. Counted over 72 of the 253 production source files in this repository: 177 are under the ~2,400-byte size floor this dimension measures over, and the remaining 4 have no attributable history left to measure.
What to do
- Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
41 deducted task-comment markers across 19330 LoC (0.2/KLoC) → score 9.6. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 28 TodoComment finding(s) in Explicit Debt — start with RscCompat.scala (10), ExplicitResultTypesImports.scala (3), LegacyCodePrinter.scala (3). — One of this dimension's main actionable groups (28 warning-level).
- Resolve the 12 FixmeComment finding(s) in Explicit Debt — start with RscCompat.scala (10), PrettyTypeSuite.scala, PrettyType.scala. — One of this dimension's main actionable groups (12 warning-level).
- Resolve the 1 XxxComment finding(s) in Explicit Debt — start with DisableSyntaxConfig.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D26 · Project Cohesion
1 of 2 build units (npm, sbt) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
20 finding(s): 0 critical, 20 high, 0 medium, 0 low. 18 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `compat-metaconfig-macros/src/main/scala-3/metaconfig/generic/package.scala` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 18 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 (18 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
31 of 76 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is scalafix-rules/src/main/scala-2/scalafix/internal/pc/ScalafixGlobal.scala. Counted over 76 of the 253 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 30 Orphaned file finding(s) in Knowledge Freshness — start with ScalafixArguments.java, Pretty.scala, Rule.scala. — One of this dimension's main actionable groups (30 recommendation-level).
- Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with ScalafixGlobal.scala. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: ScalafixBuild.scala↔ScalafixImpl.scala 50%; RuleCtxImpl.scala↔LegacyRuleCtx.scala 50%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with ScalafixBuild.scala. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with RuleCtxImpl.scala. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 5 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `Scalafix` declares 17 abstract methods: `mainHelp`, `newArguments`, `scala211`, `scala212`, `scala213`, `scala33`, `scala35`, `scala36`, `scala37`, `scala38`, `scala39`, `scala3LTS`, `scala3Next`, `scalaVersion`, `scalafixVersion`, `scalametaVersion`, `supportedScalaVersions`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — scalafix-interfaces/src/main/java/scalafix/interfaces/Scalafix.java:24
- `ScalafixArguments` declares 24 abstract methods: `availableRules`, `evaluate`, `rulesThatWillRun`, `run`, `validate`, `withCharset`, `withClasspath`, `withConfig`, `withExcludedPaths`, `withMainCallback`, `withMode`, `withParsedArguments`, `withPaths`, `withPrintStream`, `withRules`, `withScalaVersion`, `withScalacOptions`, `withSemanticdbTargetroots`, `withSourceroot`, `withToolClasspath`, `withToolClasspath`, `withToolClasspath`, `withToolClasspath`, `withWorkingDirectory`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 24 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — scalafix-interfaces/src/main/java/scalafix/interfaces/ScalafixArguments.java:26
- `PatchOps` declares 18 abstract members under just 13 distinct name(s): `removeImportee`, `addGlobalImport`, `replaceToken`, `removeTokens`, `removeTokens`, `removeToken`, `replaceTree`, `addRight`, `addLeft`, `addRight`, `addLeft`, `lint`, `removeGlobalImport`, `addGlobalImport`, `replaceSymbol`, `renameSymbol`, `replaceSymbols`, `replaceSymbols`. 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 18 separate responsibilities: a caller binds to 13 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 18 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. — scalafix-core/src/main/scala/scalafix/patch/PatchOps.scala:9
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
- Where the width is an overload set rather than separate responsibilities, collapse the overloads instead — segregating those relieves no caller.
AX8 · Test isolation
GD1 · Unfinished & placeholder code
- `structure` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — scalafix-core/src/main/scala/scalafix/v0/Document.scala:44
What to do
- Finish or delete the members whose body is still `???` or a "not implemented" throw where nothing overrides them, and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
- `structure` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — scalafix-core/src/main/scala/scalafix/v0/Document.scala:44
- A bare `// scalastyle:off`, `// scalafix:off` or `@nowarn` (or Wartremover's `warts.All`) switches every rule or warning off — hidden debt. Suppress the specific rule on the specific line, with a justification, instead. — scalafix-cli/src/main/scala/scalafix/internal/v1/Args.scala:494
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
- Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
M1 · Documentation (README)
- The root README is 80 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
- 48 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
- Expand the README with getting-started, architecture overview and a project map.
- 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.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 1 of 1 project(s) that lack one — worth up to 2 pts.
- Review the README against recent changes; refresh the parts that drifted.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
- Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
P10 · Library API & versioning
- 19/23 types (83%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Java: package-private (no modifier), or leave its package out of `module-info` exports) so internals can change without breaking consumers.
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
What to do
- Dependabot is configured but does not watch `npm` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
PF2 · Allocation hygiene
What to do
- Raise allocation-aware density on the hot paths — currently 17 use(s) across 20,971 production line(s) (~0.8/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
- Java: on hot paths, work through buffer views (ByteBuffer/LongBuffer slices, MemorySegment) instead of copies, avoid boxing with primitive collections (fastutil, Eclipse Collections, HPPC, Trove), presize collections and StringBuilders, and pool expensive buffers (Netty's pooled allocator, commons-pool).
- Scala: on hot paths, make small wrappers value classes (extends AnyVal), @specialized generic code over primitives, use primitive collections, and presize builders.
S1 · Web-Security Posture
- MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`MessageDigest.getInstance("SHA-256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. — scalafix-core/src/main/scala/scalafix/internal/v1/FingerprintOps.scala:14
What to do
- Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- 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. — scalafix-rules/src/main/scala-2/scalafix/internal/rule/ExplicitResultTypes.scala:31
- `case NonFatal(_)` 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. — scalafix-rules/src/main/scala-2/scalafix/internal/pc/ScalafixGlobal.scala:88
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- No build over this repository's 212 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 62% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 89% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 52% | Adequate — gated by M1, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 51% | Adequate — gated by P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 80% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 64% | Adequate | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 55 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Scala imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Scala code is a Play controller, a Cask routes object, a Scalatra servlet, a Finatra controller, an Akka/Pekko HTTP routes holder or a JSR-330/Spring singleton, so no instance is shared between request threads. 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- 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 — ~15742 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 reads .NET projects as units only; 1 folder(s) declared by package.json were not judged for an overview, an example or the map.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# only; Java, JavaScript, Scala not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. 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# and Visual Basic comments only — this repository's production source is .java, .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- 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 (1 of 2 signals for this style — below the bar we score at): 117 value object(s)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- 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
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Java was read, and it logs through none that an assembled message defeats: java.util.logging's level methods, log4j 1, commons-logging, JBoss Logging and Flogger take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J or log4j 2 (`org.slf4j.Logger`, `org.apache.logging.log4j.Logger`, Lombok's `@Slf4j`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 22 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge scalafix-rules/src/main/scala-2/scalafix/internal/pc/ScalafixGlobal.scala:1
- Boundary-crossing change coupling: ScalafixBuild.scala ↔ ScalafixImpl.scala project/ScalafixBuild.scala:1
Serious — 110 finding(s)
- TodoComment scalafix-tests/output/src/main/scala-3/test/explicitResultTypes/ExplicitResultTypesImports.scala:26
- TodoComment scalafix-tests/output/src/main/scala-2/test/explicitResultTypes/ExplicitResultTypesImports.scala:25
- TodoComment scalafix-tests/input/src/main/scala/test/explicitResultTypes/ExplicitResultTypesImports.scala:23
- TodoComment scalafix-tests/output/src/main/scala-2/test/explicitResultTypes/RscCompat.scala:101
- TodoComment scalafix-tests/output/src/main/scala-2/test/explicitResultTypes/RscCompat.scala:104
- TodoComment scalafix-tests/output/src/main/scala-2/test/explicitResultTypes/RscCompat.scala:132
- TodoComment scalafix-tests/output/src/main/scala-2/test/explicitResultTypes/RscCompat.scala:149
- TodoComment scalafix-tests/input/src/main/scala-2/test/explicitResultTypes/RscCompat.scala:103
- TodoComment scalafix-tests/input/src/main/scala-2/test/explicitResultTypes/RscCompat.scala:106
- TodoComment scalafix-tests/input/src/main/scala-2/test/explicitResultTypes/RscCompat.scala:132
- TodoComment scalafix-tests/input/src/main/scala-2/test/explicitResultTypes/RscCompat.scala:149
- TodoComment scalafix-tests/output/src/main/scala-2/test/explicitResultTypes/RscCompat.scala:162
- TodoComment scalafix-tests/input/src/main/scala-2/test/explicitResultTypes/RscCompat.scala:162
- TodoComment scalafix-rules/src/main/scala/scalafix/internal/rule/OrganizeImports.scala:446
- TodoComment scalafix-docs/src/main/scala/docs/website.scala:71
- TodoComment scalafix-core/src/main/scala-2/scalafix/internal/util/PrettyType.scala:58
- TodoComment scalafix-core/src/main/scala-2/scalafix/internal/util/PrettyType.scala:530
- TodoComment scalafix-core/src/main/scala/scalafix/internal/v1/DocumentFromProtobuf.scala:20
- TodoComment scalafix-core/src/main/scala/scalafix/internal/v0/LegacyCodePrinter.scala:198
- TodoComment scalafix-core/src/main/scala/scalafix/internal/v0/LegacyCodePrinter.scala:113
- TodoComment scalafix-core/src/main/scala/scalafix/internal/v0/LegacyCodePrinter.scala:188
- TodoComment scalafix-core/src/main/scala/scalafix/internal/patch/ImportPatchOps.scala:80
- TodoComment scalafix-core/src/main/scala/scalafix/internal/patch/PatchInternals.scala:182
- TodoComment scalafix-cli/src/main/scala/scalafix/internal/v1/Args.scala:161
- TodoComment scalafix-cli/src/main/scala/scalafix/internal/v1/Ls.scala:11
- FixmeComment scalafix-tests/output/src/main/scala-2/test/explicitResultTypes/RscCompat.scala:108
- FixmeComment scalafix-tests/input/src/main/scala-2/test/explicitResultTypes/RscCompat.scala:110
- FixmeComment scalafix-tests/output/src/main/scala-2/test/explicitResultTypes/RscCompat.scala:113
- FixmeComment scalafix-tests/input/src/main/scala-2/test/explicitResultTypes/RscCompat.scala:115
- FixmeComment scalafix-tests/output/src/main/scala-2/test/explicitResultTypes/RscCompat.scala:126
- FixmeComment scalafix-tests/input/src/main/scala-2/test/explicitResultTypes/RscCompat.scala:126
- FixmeComment scalafix-tests/output/src/main/scala-2/test/explicitResultTypes/RscCompat.scala:136
- FixmeComment scalafix-tests/input/src/main/scala-2/test/explicitResultTypes/RscCompat.scala:136
- FixmeComment scalafix-tests/output/src/main/scala-2/test/explicitResultTypes/RscCompat.scala:189
- FixmeComment scalafix-tests/input/src/main/scala-2/test/explicitResultTypes/RscCompat.scala:185
- FixmeComment scalafix-tests/integration/src/test/scala-2/scalafix/tests/core/PrettyTypeSuite.scala:96
- FixmeComment scalafix-core/src/main/scala-2/scalafix/internal/util/PrettyType.scala:285
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (5 lines × 2) scalafix-rules/src/main/scala/scalafix/internal/rule/DisableSyntax.scala:285
- Duplicated block (5 lines × 2) scalafix-reflect/src/main/scala/scalafix/internal/reflect/RuleInstrumentation.scala:19
- Duplicated block (5 lines × 2) scalafix-rules/src/main/scala-3/pc/PresentationCompilerTypeInferrer.scala:28
- FileTooLong: rule/OrganizeImports.scala scalafix-rules/src/main/scala/scalafix/internal/rule/OrganizeImports.scala
- FileTooLong: util/PrettyType.scala scalafix-core/src/main/scala-2/scalafix/internal/util/PrettyType.scala
- RemoveUnused.fix (cyclomatic 47) scalafix-rules/src/main/scala/scalafix/internal/rule/RemoveUnused.scala:60
- ScalafixGlobal.shortType (cyclomatic 37) scalafix-rules/src/main/scala-2/scalafix/internal/pc/ScalafixGlobal.scala:214
- ImportPatchOps.superNaiveImportPatchToTokenPatchConverter (cyclomatic 34) scalafix-core/src/main/scala/scalafix/internal/patch/ImportPatchOps.scala:66
- HasFlags.flagSyntax (cyclomatic 34) scalafix-core/src/main/scala/scalafix/v0/HasFlags.scala:41
- LegacySemanticdbIndex.infoToDenotation (cyclomatic 32) scalafix-core/src/main/scala/scalafix/internal/v0/LegacySemanticdbIndex.scala:99
- PrettyType.toTree (cyclomatic 31) scalafix-core/src/main/scala-2/scalafix/internal/util/PrettyType.scala:156
- DisableSyntax.checkTree (cyclomatic 30) scalafix-rules/src/main/scala/scalafix/internal/rule/DisableSyntax.scala:167
- PrettyType.toType (cyclomatic 29) scalafix-core/src/main/scala-2/scalafix/internal/util/PrettyType.scala:473
- Pretty.pretty (cyclomatic 28) scalafix-core/src/main/scala/scalafix/internal/util/Pretty.scala:30
- Symbol.apply (cyclomatic 26) scalafix-core/src/main/scala/scalafix/v0/Symbol.scala:56
- ReplaceSymbolOps.naiveMoveSymbolPatch (cyclomatic 25) scalafix-core/src/main/scala/scalafix/internal/patch/ReplaceSymbolOps.scala:54
- OrganizeImports.prettyPrintImportGroups (cyclomatic 24) scalafix-rules/src/main/scala/scalafix/internal/rule/OrganizeImports.scala:744
- CompilerTypePrinter.preProcess (cyclomatic 21) scalafix-rules/src/main/scala-2/scalafix/internal/rule/CompilerTypePrinter.scala:315
- TreeOps.inferGlobalSymbol (cyclomatic 20) scalafix-core/src/main/scala/scalafix/util/TreeOps.scala:41
- TPrintLowPri.typePrintImpl (cyclomatic 19) compat-metaconfig-macros/src/main/scala-3/metaconfig/pprint/TPrintImpl.scala:45
- OrganizeImports.mergeImporters (cyclomatic 18) scalafix-rules/src/main/scala/scalafix/internal/rule/OrganizeImports.scala:425
- RuleInstrumentation.getRuleFqn (cyclomatic 17) scalafix-reflect/src/main/scala/scalafix/internal/reflect/RuleInstrumentation.scala:11
- ScalafixGlobal.inverseSemanticdbSymbols (cyclomatic 17) scalafix-rules/src/main/scala-2/scalafix/internal/pc/ScalafixGlobal.scala:70
- XtensionDenotation.skind (cyclomatic 16) scalafix-core/src/main/scala/scalafix/internal/v0/package.scala:33
- DisableSyntax.checkTokens (cyclomatic 16) scalafix-rules/src/main/scala/scalafix/internal/rule/DisableSyntax.scala:95
- XxxComment scalafix-rules/src/main/scala/scalafix/internal/rule/DisableSyntaxConfig.scala:197
- PrettyType.toTree (cognitive 64) scalafix-core/src/main/scala-2/scalafix/internal/util/PrettyType.scala:156
- ScalafixGlobal.shortType (cognitive 63) scalafix-rules/src/main/scala-2/scalafix/internal/pc/ScalafixGlobal.scala:214
- Symbol.apply (cognitive 57) scalafix-core/src/main/scala/scalafix/v0/Symbol.scala:56
- OrganizeImports.prettyPrintImportGroups (cognitive 54) scalafix-rules/src/main/scala/scalafix/internal/rule/OrganizeImports.scala:744
- ImportPatchOps.superNaiveImportPatchToTokenPatchConverter (cognitive 49) scalafix-core/src/main/scala/scalafix/internal/patch/ImportPatchOps.scala:66
- TreeOps.inferGlobalSymbol (cognitive 47) scalafix-core/src/main/scala/scalafix/util/TreeOps.scala:41
- RemoveUnused.fix (cognitive 45) scalafix-rules/src/main/scala/scalafix/internal/rule/RemoveUnused.scala:60
- PrettyType.toType (cognitive 43) scalafix-core/src/main/scala-2/scalafix/internal/util/PrettyType.scala:473
- HasFlags.flagSyntax (cognitive 34) scalafix-core/src/main/scala/scalafix/v0/HasFlags.scala:41
- OrganizeImports.mergeImporters (cognitive 34) scalafix-rules/src/main/scala/scalafix/internal/rule/OrganizeImports.scala:425
- ReplaceSymbolOps.naiveMoveSymbolPatch (cognitive 32) scalafix-core/src/main/scala/scalafix/internal/patch/ReplaceSymbolOps.scala:54
- DisableSyntax.checkTree (cognitive 30) scalafix-rules/src/main/scala/scalafix/internal/rule/DisableSyntax.scala:167
- TPrintLowPri.typePrintImpl (cognitive 28) compat-metaconfig-macros/src/main/scala-3/metaconfig/pprint/TPrintImpl.scala:45
- Pretty.pretty (cognitive 28) scalafix-core/src/main/scala/scalafix/internal/util/Pretty.scala:172
- Pretty.pretty (cognitive 27) scalafix-core/src/main/scala/scalafix/internal/util/Pretty.scala:30
- CompilerTypePrinter.rewriteRefinedTypeToNamedSubclass (cognitive 24) scalafix-rules/src/main/scala-2/scalafix/internal/rule/CompilerTypePrinter.scala:229
- CompilerTypePrinter.preProcess (cognitive 23) scalafix-rules/src/main/scala-2/scalafix/internal/rule/CompilerTypePrinter.scala:315
- ExplicitResultTypesBase.fixDefinition (cognitive 23) scalafix-rules/src/main/scala/scalafix/internal/rule/ExplicitResultTypesBase.scala:113
- Plot.writePlots (cognitive 21) .github/scripts/plot.scala:18
- AnchoredEscapes.collectEscapes (cognitive 20) scalafix-core/src/main/scala/scalafix/internal/patch/EscapeHatch.scala:386
- ScalafixGlobal.inverseSemanticdbSymbols (cognitive 20) scalafix-rules/src/main/scala-2/scalafix/internal/pc/ScalafixGlobal.scala:70
- SemanticRuleSuite.parseTestkitCommentOpt (cognitive 19) scalafix-testkit/src/main/scala/scalafix/testkit/SemanticRuleSuite.scala:54
- LegacySemanticdbIndex.infoToDenotation (cognitive 18) scalafix-core/src/main/scala/scalafix/internal/v0/LegacySemanticdbIndex.scala:99
- Compatibility.earlySemver (cognitive 17) scalafix-cli/src/main/scala/scalafix/internal/util/Compatibility.scala:16
- EscapeHatch.filter (cognitive 17) scalafix-core/src/main/scala/scalafix/internal/patch/EscapeHatch.scala:55
- CompilerTypePrinter.importPatches (cognitive 17) scalafix-rules/src/main/scala-2/scalafix/internal/rule/CompilerTypePrinter.scala:161
- XtensionDenotation.skind (cognitive 16) scalafix-core/src/main/scala/scalafix/internal/v0/package.scala:33
- Change coupling: RuleCtxImpl.scala ↔ LegacyRuleCtx.scala scalafix-core/src/main/scala/scalafix/internal/rule/RuleCtxImpl.scala:1
- REDACTED
- Off the main sequence: core
- Low cohesion: InternalSemanticDoc (LCOM4 4) scalafix-core/src/main/scala/scalafix/internal/v1/InternalSemanticDoc.scala:22
- Unfinished stub — body is `???` scalafix-core/src/main/scala/scalafix/v0/Document.scala:44
- Unfinished stub — body is ??? / NotImplementedError scalafix-core/src/main/scala/scalafix/v0/Document.scala:44
- README may be stale
- No structured logging
- Weak hash algorithm scalafix-core/src/main/scala/scalafix/internal/v1/FingerprintOps.scala:14
- JavaScript dependencies are not locked
- Swallowed exception (empty catch) scalafix-rules/src/main/scala-2/scalafix/internal/rule/ExplicitResultTypes.scala:31
- Swallowed exception (caught, then discarded) scalafix-rules/src/main/scala-2/scalafix/internal/pc/ScalafixGlobal.scala:88
Minor — 49 finding(s)
- Orphaned file scalafix-interfaces/src/main/java/scalafix/interfaces/ScalafixArguments.java:1
- Orphaned file scalafix-core/src/main/scala/scalafix/internal/util/Pretty.scala:1
- Orphaned file scalafix-core/src/main/scala/scalafix/v0/Rule.scala:1
- Orphaned file scalafix-rules/src/main/scala/scalafix/internal/rule/DisableSyntaxConfig.scala:1
- Orphaned file scalafix-core/src/main/scala/scalafix/v1/SymbolInformation.scala:1
- Orphaned file scalafix-core/src/main/scala/scalafix/internal/config/ScalafixMetaconfigReaders.scala:1
- Orphaned file scalafix-core/src/main/scala/scalafix/v0/Symbol.scala:1
- Orphaned file scalafix-testkit/src/main/scala/scalafix/internal/testkit/AssertDiff.scala:1
- Orphaned file scalafix-core/src/main/scala/scalafix/patch/PatchOps.scala:1
- Orphaned file scalafix-cli/src/main/scala/scalafix/internal/jgit/JGitDiff.scala:1
- Orphaned file scalafix-core/src/main/scala/scalafix/internal/v1/InternalSemanticDoc.scala:1
- Orphaned file scalafix-reflect/src/main/scala/scalafix/internal/v0/LegacyInMemorySemanticdbIndex.scala:1
- Orphaned file scalafix-reflect/src/main/scala/scalafix/internal/reflect/RuleDecoderOps.scala:1
- Orphaned file scalafix-testkit/src/main/scala/scalafix/testkit/TestkitProperties.scala:1
- Orphaned file scalafix-testkit/src/main/scala/scalafix/internal/testkit/CommentAssertion.scala:1
- Orphaned file scalafix-core/src/main/scala/scalafix/internal/patch/LegacyPatchOps.scala:1
- Orphaned file scalafix-core/src/main/scala/scalafix/v0/HasFlags.scala:1
- Orphaned file scalafix-testkit/src/main/scala/scalafix/testkit/DiffAssertions.scala:1
- Orphaned file scalafix-core/src/main/scala/scalafix/v0/SemanticdbIndex.scala:1
- Orphaned file scalafix-core/src/main/scala/scalafix/internal/util/SymbolOps.scala:1
- Orphaned file scalafix-core/src/main/scala/scalafix/internal/util/ProductStructure.scala:1
- Orphaned file scalafix-core/src/main/scala/scalafix/util/TreeOps.scala:1
- Orphaned file scalafix-core/src/main/scala/scalafix/internal/v1/package.scala:1
- Orphaned file scalafix-core/src/main/scala/scalafix/internal/v1/Rules.scala:1
- Orphaned file scalafix-cli/src/main/scala/scalafix/internal/v1/CompletionsOps.scala:1
- Fat interface: Scalafix (17 abstract methods) scalafix-interfaces/src/main/java/scalafix/interfaces/Scalafix.java:24
- Fat interface: ScalafixArguments (24 abstract methods) scalafix-interfaces/src/main/java/scalafix/interfaces/ScalafixArguments.java:26
- Fat interface: PatchOps (18 abstract members) scalafix-core/src/main/scala/scalafix/patch/PatchOps.scala:9
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Further sole-owners (lower concentration)
- Projects may be oversized for their cohesion
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- Blanket warning suppression scalafix-cli/src/main/scala/scalafix/internal/v1/Args.scala:494
- Thin README
- No ADRs
- CI build step not evidenced
- Large public API surface
- No release approval gate
- Duplicated predicate scalafix-rules/src/main/scala/scalafix/internal/rule/OrganizeImports.scala:1150
- Scala's null is not held to the type system everywhere
- Silent fallback default in catch scalafix-rules/src/main/scala-2/scalafix/internal/pc/ScalafixGlobal.scala:88
Minor — 3 finding(s)
- Outdated: io.get-coursier:coursier_3
- Outdated: io.get-coursier:interface
- Outdated: org.eclipse.jgit:org.eclipse.jgit
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ab52f71e4ac0406db5798d803449fc5e/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ab52f71e4ac0406db5798d803449fc5e/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-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 . | 20 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | 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 1 file(s) — `compat-metaconfig-macros/src/main/scala-3/metaconfig/generic/package.scala` — so the PII/GDPR sweep did not cover them at all. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |