Executive summary
VirtusLab/scala-cli falls short of our standard for production, in part because the project keeps no record of its design decisions. It scores 62 out of 100 and is rated Adequate, and 316 of its 318 critical findings are security problems.
Maturity, at 53, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 9 points. Having someone learn and document the file no active contributor knows is another step, worth about 3 points. Raising Maturity to 70 would lift the score to about 68.
289 pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Fourteen secrets can leak from the build pipeline, and seven settings leave the servers or containers unsafe. Pinning each tool to an exact version, limiting each secret to its own step and correcting the unsafe settings would close these risks. Fixing the weaknesses the scanner points to would fix the three security weaknesses in the code, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once. The set of files in separate parts that keep changing together needs that dependency made explicit.
The product code is 52,308 lines, about €110,000 to rebuild.
If Maturity rose from 53 to 70, the lowest score rated Strong, the score would rise from 62 to about 68.
New since the last survey: 18 findings
- Cognitive Complexity · ScalaJsLinkerConfig.linkerCliArgs (cognitive 17) modules/options/src/main/scala/scala/build/internal/ScalaJsLinkerConfig.scala
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- 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
- Web-Security Posture · Weak hash algorithm modules/build/src/main/scala/scala/build/input/Inputs.scala
- Web-Security Posture · Weak hash algorithm modules/build/src/main/scala/scala/build/postprocessing/SemanticdbProcessor.scala
- Web-Security Posture · Weak hash algorithm modules/build/src/main/scala/scala/build/postprocessing/SlothPatcher.scala
- Web-Security Posture · Weak hash algorithm modules/build/src/main/scala/scala/build/postprocessing/SlothPatcher.scala
- Web-Security Posture · Weak hash algorithm modules/cli/src/main/scala/scala/cli/internal/CachedBinary.scala
- Web-Security Posture · Weak hash algorithm modules/cli/src/main/scala/scala/cli/internal/CachedBinary.scala
- Web-Security Posture · Weak hash algorithm modules/cli/src/main/scala/scala/cli/internal/CachedBinary.scala
- Web-Security Posture · Weak hash algorithm modules/options/src/main/scala/scala/build/options/BuildOptions.scala
Fixed since the last survey: 2 findings
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €110,000 · Estimate
| Cost to rebuild | €35,000 to €180,000, for 585 to 1,856 hours of work, about 0.7 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 62. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 52,308 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 build.bsp.protocol | 2 build.options.publish | 3 cli.commands.github.GitHubApi | 4 build.compiler | 5 build.internals | 6 cli.commands.shared | 7 build.preprocessing | 8 cli.commands.util | 9 build.input | 10 cli.commands.repl | 11 cli.commands.run | 12 cli.commands.default | 13 cli.commands | 14 cli.commands.pgp | 15 cli.config | 16 cli.config.PasswordOption | 17 build.internal | 18 cli.commands.package0 | 19 cli.commands.publish | 20 build.options | 21 build.directives | 22 build.preprocessing.directives | 23 build.errors | 24 build.Build | 25 build | 26 build.actionable.ActionableDiagnostic | 27 build.bsp.BspImpl | 28 cli.commands.config | 29 cli.commands.doc | 30 cli.commands.fix | 31 cli.commands.fmt | 32 cli.commands.github | 33 cli.commands.publish.checks | 34 cli.commands.setupide | 35 cli.commands.update | 36 cli.exportCmd | 37 cli.internal.ScalaJsLinker | 38 build.bsp | 39 cli.commands.export0 | 40 cli.internal |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 build.bsp.protocol | ||||||||||||||||||||||||||||||||||||||||
| 2 build.options.publish | ||||||||||||||||||||||||||||||||||||||||
| 3 cli.commands.github.GitHubApi | ||||||||||||||||||||||||||||||||||||||||
| 4 build.compiler | 3 | 3 | 14 | |||||||||||||||||||||||||||||||||||||
| 5 build.internals | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 cli.commands.shared | 1 | 3 | 3 | 3 | 7 | |||||||||||||||||||||||||||||||||||
| 7 build.preprocessing | 10 | 15 | 2 | 3 | 4 | 7 | 11 | 10 | ||||||||||||||||||||||||||||||||
| 8 cli.commands.util | 2 | 1 | 1 | 3 | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 9 build.input | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 10 cli.commands.repl | 6 | 1 | 1 | 1 | 2 | 1 | 4 | |||||||||||||||||||||||||||||||||
| 11 cli.commands.run | 10 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||
| 12 cli.commands.default | 5 | 1 | 1 | 1 | 2 | 3 | ||||||||||||||||||||||||||||||||||
| 13 cli.commands | 3 | 1 | 3 | 1 | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||
| 14 cli.commands.pgp | 16 | 2 | 1 | 3 | 4 | 3 | 7 | |||||||||||||||||||||||||||||||||
| 15 cli.config | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 cli.config.PasswordOption | 4 | 4 | ||||||||||||||||||||||||||||||||||||||
| 17 build.internal | 1 | 1 | 8 | 5 | ||||||||||||||||||||||||||||||||||||
| 18 cli.commands.package0 | 1 | 10 | 1 | 1 | 1 | 4 | 2 | 1 | 3 | |||||||||||||||||||||||||||||||
| 19 cli.commands.publish | 2 | 1 | 2 | 24 | 1 | 1 | 5 | 5 | 4 | 1 | 3 | 4 | 1 | 7 | ||||||||||||||||||||||||||
| 20 build.options | 4 | 5 | 1 | 1 | 2 | 1 | 1 | 9 | 7 | 11 | ||||||||||||||||||||||||||||||
| 21 build.directives | 1 | 1 | 4 | 4 | ||||||||||||||||||||||||||||||||||||
| 22 build.preprocessing.directives | 5 | 1 | 1 | 3 | 51 | 36 | 41 | 28 | ||||||||||||||||||||||||||||||||
| 23 build.errors | 1 | 1 | 6 | |||||||||||||||||||||||||||||||||||||
| 24 build.Build | 3 | 6 | 1 | 12 | ||||||||||||||||||||||||||||||||||||
| 25 build | 2 | 2 | 2 | 1 | 16 | 2 | 9 | 2 | ||||||||||||||||||||||||||||||||
| 26 build.actionable.ActionableDiagnostic | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 build.bsp.BspImpl | 2 | 1 | 6 | 2 | ||||||||||||||||||||||||||||||||||||
| 28 cli.commands.config | 1 | 6 | 2 | 1 | 3 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||
| 29 cli.commands.doc | 4 | 1 | 2 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 30 cli.commands.fix | 1 | 5 | 1 | 2 | 4 | 1 | 1 | 1 | 2 | 1 | 2 | 5 | ||||||||||||||||||||||||||||
| 31 cli.commands.fmt | 4 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 32 cli.commands.github | 7 | 5 | 4 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||
| 33 cli.commands.publish.checks | 1 | 1 | 23 | 11 | 12 | |||||||||||||||||||||||||||||||||||
| 34 cli.commands.setupide | 5 | 1 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 35 cli.commands.update | 1 | 2 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 36 cli.exportCmd | 4 | 7 | 1 | 5 | 14 | |||||||||||||||||||||||||||||||||||
| 37 cli.internal.ScalaJsLinker | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 build.bsp | 1 | 7 | 5 | 3 | 1 | 9 | 1 | |||||||||||||||||||||||||||||||||
| 39 cli.commands.export0 | 4 | 1 | 2 | 2 | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||
| 40 cli.internal | 1 | 1 | 1 | 4 | 1 | 5 | 1 |
4→20 build.compiler uses build.options part of a loop✕
- Connections
- 3 pairs of types, where a type in build.compiler uses a type in build.options.
- The types involved
scala.build.compiler.BloopCompilerMaker→scala.build.options.BuildOptionsscala.build.compiler.ScalaCompilerMaker→scala.build.options.BuildOptionsscala.build.compiler.SimpleScalaCompilerMaker→scala.build.options.BuildOptions
- Direction
- build.compiler uses build.options, so a change to build.options can break build.compiler, while a change to build.compiler can't break build.options.
- 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.
4→23 build.compiler uses build.errors part of a loop✕
- Connections
- 3 pairs of types, where a type in build.compiler uses a type in build.errors.
- The types involved
scala.build.compiler.BloopCompilerMaker→scala.build.errors.BuildExceptionscala.build.compiler.ScalaCompilerMaker→scala.build.errors.BuildExceptionscala.build.compiler.SimpleScalaCompilerMaker→scala.build.errors.BuildException
- Direction
- build.compiler uses build.errors, so a change to build.errors can break build.compiler, while a change to build.compiler can't break build.errors.
- 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.
4→25 build.compiler uses build part of a loop✕
- Connections
- 14 pairs of types, where a type in build.compiler uses a type in build.
- The types involved
scala.build.compiler.BloopCompiler→scala.build.Loggerscala.build.compiler.BloopCompiler→scala.build.Positionedscala.build.compiler.BloopCompiler→scala.build.Projectscala.build.compiler.BloopCompilerMaker→scala.build.Loggerscala.build.compiler.ScalaCompiler→scala.build.Loggerscala.build.compiler.ScalaCompiler→scala.build.Positionedscala.build.compiler.ScalaCompiler→scala.build.Projectscala.build.compiler.ScalaCompilerMaker→scala.build.Loggerscala.build.compiler.SimpleJavaCompiler→scala.build.Loggerscala.build.compiler.SimpleJavaCompiler→scala.build.Projectscala.build.compiler.SimpleScalaCompiler→scala.build.Loggerscala.build.compiler.SimpleScalaCompiler→scala.build.Positionedscala.build.compiler.SimpleScalaCompiler→scala.build.Projectscala.build.compiler.SimpleScalaCompilerMaker→scala.build.Logger
- Direction
- build.compiler uses build, so a change to build can break build.compiler, while a change to build.compiler can't break build.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→25 build.internals uses build part of a loop✕
- Connections
- 1 pair of types, where a type in build.internals uses a type in build.
- The types involved
scala.build.internals.MsvcEnvironment→scala.build.Logger
- Direction
- build.internals uses build, so a change to build can break build.internals, while a change to build.internals can't break build.
- 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→4 cli.commands.shared uses build.compiler✕
- Connections
- 1 pair of types, where a type in cli.commands.shared uses a type in build.compiler.
- The types involved
scala.cli.commands.shared.SharedOptions→scala.build.compiler.ScalaCompilerMaker
- Direction
- cli.commands.shared uses build.compiler, so a change to build.compiler can break cli.commands.shared, while a change to cli.commands.shared can't break build.compiler.
- Position
- Below the diagonal: cli.commands.shared uses a module listed above it, which is the healthy direction.
6→9 cli.commands.shared uses build.input part of a loop✕
- Connections
- 3 pairs of types, where a type in cli.commands.shared uses a type in build.input.
- The types involved
scala.cli.commands.shared.SharedOptions→scala.build.input.Elementscala.cli.commands.shared.SharedOptions→scala.build.input.Inputsscala.cli.commands.shared.SharedOptions→scala.build.input.ScalaCliInvokeData
- Direction
- cli.commands.shared uses build.input, so a change to build.input can break cli.commands.shared, while a change to cli.commands.shared can't break build.input.
- 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→20 cli.commands.shared uses build.options part of a loop✕
- Connections
- 3 pairs of types, where a type in cli.commands.shared uses a type in build.options.
- The types involved
scala.cli.commands.shared.HasSharedWatchOptions→scala.build.options.BuildOptionsscala.cli.commands.shared.SharedOptions→scala.build.options.BuildOptionsscala.cli.commands.shared.SharedWatchOptions→scala.build.options.BuildOptions
- Direction
- cli.commands.shared uses build.options, so a change to build.options can break cli.commands.shared, while a change to cli.commands.shared can't break build.options.
- 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→23 cli.commands.shared uses build.errors part of a loop✕
- Connections
- 3 pairs of types, where a type in cli.commands.shared uses a type in build.errors.
- The types involved
scala.cli.commands.shared.HasSharedWatchOptions→scala.build.errors.BuildExceptionscala.cli.commands.shared.MainClassOptions→scala.build.errors.MainClassErrorscala.cli.commands.shared.SharedOptions→scala.build.errors.BuildException
- Direction
- cli.commands.shared uses build.errors, so a change to build.errors can break cli.commands.shared, while a change to cli.commands.shared can't break build.errors.
- 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→25 cli.commands.shared uses build part of a loop✕
- Connections
- 7 pairs of types, where a type in cli.commands.shared uses a type in build.
- The types involved
scala.cli.commands.shared.CoursierOptions→scala.build.Loggerscala.cli.commands.shared.LoggingOptions→scala.build.Loggerscala.cli.commands.shared.SharedCompilationServerOptions→scala.build.Directoriesscala.cli.commands.shared.SharedCompilationServerOptions→scala.build.Loggerscala.cli.commands.shared.SharedOptions→scala.build.BuildThreadsscala.cli.commands.shared.SharedOptions→scala.build.Loggerscala.cli.commands.shared.SharedOptions→scala.build.Positioned
- Direction
- cli.commands.shared uses build, so a change to build can break cli.commands.shared, while a change to cli.commands.shared can't break build.
- 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→6 build.preprocessing uses cli.commands.shared✕
- Connections
- 10 pairs of types, where a type in build.preprocessing uses a type in cli.commands.shared.
- The types involved
scala.build.preprocessing.DataPreprocessor→scala.cli.commands.shared.SuppressWarningOptionsscala.build.preprocessing.DeprecatedDirectives→scala.cli.commands.shared.SuppressWarningOptionsscala.build.preprocessing.DirectivesPreprocessor→scala.cli.commands.shared.SuppressWarningOptionsscala.build.preprocessing.JarPreprocessor→scala.cli.commands.shared.SuppressWarningOptionsscala.build.preprocessing.JavaPreprocessor→scala.cli.commands.shared.SuppressWarningOptionsscala.build.preprocessing.MarkdownCodeBlockProcessor→scala.cli.commands.shared.SuppressWarningOptionsscala.build.preprocessing.MarkdownPreprocessor→scala.cli.commands.shared.SuppressWarningOptionsscala.build.preprocessing.Preprocessor→scala.cli.commands.shared.SuppressWarningOptionsscala.build.preprocessing.ScalaPreprocessor→scala.cli.commands.shared.SuppressWarningOptionsscala.build.preprocessing.ScriptPreprocessor→scala.cli.commands.shared.SuppressWarningOptions
- Direction
- build.preprocessing uses cli.commands.shared, so a change to cli.commands.shared can break build.preprocessing, while a change to build.preprocessing can't break cli.commands.shared.
- Position
- Below the diagonal: build.preprocessing uses a module listed above it, which is the healthy direction.
7→9 build.preprocessing uses build.input part of a loop✕
- Connections
- 15 pairs of types, where a type in build.preprocessing uses a type in build.input.
- The types involved
scala.build.preprocessing.DataPreprocessor→scala.build.input.ScalaCliInvokeDatascala.build.preprocessing.DataPreprocessor→scala.build.input.SingleElementscala.build.preprocessing.DirectivesPreprocessor→scala.build.input.ScalaCliInvokeDatascala.build.preprocessing.JarPreprocessor→scala.build.input.ScalaCliInvokeDatascala.build.preprocessing.JarPreprocessor→scala.build.input.SingleElementscala.build.preprocessing.JavaPreprocessor→scala.build.input.ScalaCliInvokeDatascala.build.preprocessing.JavaPreprocessor→scala.build.input.SingleElementscala.build.preprocessing.MarkdownPreprocessor→scala.build.input.ScalaCliInvokeDatascala.build.preprocessing.MarkdownPreprocessor→scala.build.input.SingleElementscala.build.preprocessing.Preprocessor→scala.build.input.ScalaCliInvokeDatascala.build.preprocessing.Preprocessor→scala.build.input.SingleElementscala.build.preprocessing.ScalaPreprocessor→scala.build.input.ScalaCliInvokeDatascala.build.preprocessing.ScalaPreprocessor→scala.build.input.SingleElementscala.build.preprocessing.ScriptPreprocessor→scala.build.input.ScalaCliInvokeDatascala.build.preprocessing.ScriptPreprocessor→scala.build.input.SingleElement
- Direction
- build.preprocessing uses build.input, so a change to build.input can break build.preprocessing, while a change to build.preprocessing can't break build.input.
- 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→16 build.preprocessing uses cli.config.PasswordOption part of a loop✕
- Connections
- 2 pairs of types, where a type in build.preprocessing uses a type in cli.config.PasswordOption.
- The types involved
scala.build.preprocessing.ExtractedDirectives→scala.cli.config.PasswordOption.Filescala.build.preprocessing.PreprocessedSource→scala.cli.config.PasswordOption.File
- Direction
- build.preprocessing uses cli.config.PasswordOption, so a change to cli.config.PasswordOption can break build.preprocessing, while a change to build.preprocessing can't break cli.config.PasswordOption.
- 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→17 build.preprocessing uses build.internal part of a loop✕
- Connections
- 3 pairs of types, where a type in build.preprocessing uses a type in build.internal.
- The types involved
scala.build.preprocessing.MarkdownPreprocessor→scala.build.internal.JavaParserProxyscala.build.preprocessing.ScriptPreprocessor→scala.build.internal.CodeWrapperscala.build.preprocessing.ScriptPreprocessor→scala.build.internal.Name
- Direction
- build.preprocessing uses build.internal, so a change to build.internal can break build.preprocessing, while a change to build.preprocessing can't break build.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.
7→20 build.preprocessing uses build.options part of a loop✕
- Connections
- 4 pairs of types, where a type in build.preprocessing uses a type in build.options.
- The types involved
scala.build.preprocessing.PreprocessedSource→scala.build.options.BuildOptionsscala.build.preprocessing.PreprocessedSource→scala.build.options.BuildRequirementsscala.build.preprocessing.PreprocessedSource→scala.build.options.WithBuildRequirementsscala.build.preprocessing.ScriptPreprocessor→scala.build.options.BuildOptions
- Direction
- build.preprocessing uses build.options, so a change to build.options can break build.preprocessing, while a change to build.preprocessing can't break build.options.
- 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→22 build.preprocessing uses build.preprocessing.directives part of a loop✕
- Connections
- 7 pairs of types, where a type in build.preprocessing uses a type in build.preprocessing.directives.
- The types involved
scala.build.preprocessing.DeprecatedDirectives→scala.build.preprocessing.directives.DirectiveHandlerscala.build.preprocessing.DeprecatedDirectives→scala.build.preprocessing.directives.StrictDirectivescala.build.preprocessing.DirectivesPreprocessor→scala.build.preprocessing.directives.DirectiveHandlerscala.build.preprocessing.DirectivesPreprocessor→scala.build.preprocessing.directives.PartiallyProcessedDirectivesscala.build.preprocessing.DirectivesPreprocessor→scala.build.preprocessing.directives.PreprocessedDirectivesscala.build.preprocessing.DirectivesPreprocessor→scala.build.preprocessing.directives.StrictDirectivescala.build.preprocessing.ExtractedDirectives→scala.build.preprocessing.directives.StrictDirective
- Direction
- build.preprocessing uses build.preprocessing.directives, so a change to build.preprocessing.directives can break build.preprocessing, while a change to build.preprocessing can't break build.preprocessing.directives.
- 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→23 build.preprocessing uses build.errors part of a loop✕
- Connections
- 11 pairs of types, where a type in build.preprocessing uses a type in build.errors.
- The types involved
scala.build.preprocessing.DataPreprocessor→scala.build.errors.BuildExceptionscala.build.preprocessing.DirectivesPreprocessor→scala.build.errors.BuildExceptionscala.build.preprocessing.JarPreprocessor→scala.build.errors.BuildExceptionscala.build.preprocessing.JavaPreprocessor→scala.build.errors.BuildExceptionscala.build.preprocessing.MarkdownCodeBlockProcessor→scala.build.errors.BuildExceptionscala.build.preprocessing.MarkdownPreprocessor→scala.build.errors.BuildExceptionscala.build.preprocessing.PreprocessingUtil→scala.build.errors.BuildExceptionscala.build.preprocessing.Preprocessor→scala.build.errors.BuildExceptionscala.build.preprocessing.ScalaPreprocessor→scala.build.errors.BuildExceptionscala.build.preprocessing.Scoped→scala.build.errors.BuildExceptionscala.build.preprocessing.ScriptPreprocessor→scala.build.errors.BuildException
- Direction
- build.preprocessing uses build.errors, so a change to build.errors can break build.preprocessing, while a change to build.preprocessing can't break build.errors.
- 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→25 build.preprocessing uses build part of a loop✕
- Connections
- 10 pairs of types, where a type in build.preprocessing uses a type in build.
- The types involved
scala.build.preprocessing.DataPreprocessor→scala.build.Loggerscala.build.preprocessing.DeprecatedDirectives→scala.build.Loggerscala.build.preprocessing.DirectivesPreprocessor→scala.build.Loggerscala.build.preprocessing.JarPreprocessor→scala.build.Loggerscala.build.preprocessing.JavaPreprocessor→scala.build.Loggerscala.build.preprocessing.MarkdownCodeBlockProcessor→scala.build.Loggerscala.build.preprocessing.MarkdownPreprocessor→scala.build.Loggerscala.build.preprocessing.Preprocessor→scala.build.Loggerscala.build.preprocessing.ScalaPreprocessor→scala.build.Loggerscala.build.preprocessing.ScriptPreprocessor→scala.build.Logger
- Direction
- build.preprocessing uses build, so a change to build can break build.preprocessing, while a change to build.preprocessing can't break build.
- 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→6 cli.commands.util uses cli.commands.shared✕
- Connections
- 2 pairs of types, where a type in cli.commands.util uses a type in cli.commands.shared.
- The types involved
scala.cli.commands.util.JvmUtils→scala.cli.commands.shared.CoursierOptionsscala.cli.commands.util.JvmUtils→scala.cli.commands.shared.SharedJvmOptions
- Direction
- cli.commands.util uses cli.commands.shared, so a change to cli.commands.shared can break cli.commands.util, while a change to cli.commands.util can't break cli.commands.shared.
- Position
- Below the diagonal: cli.commands.util uses a module listed above it, which is the healthy direction.
8→20 cli.commands.util uses build.options part of a loop✕
- Connections
- 1 pair of types, where a type in cli.commands.util uses a type in build.options.
- The types involved
scala.cli.commands.util.JvmUtils→scala.build.options.BuildOptions
- Direction
- cli.commands.util uses build.options, so a change to build.options can break cli.commands.util, while a change to cli.commands.util can't break build.options.
- 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→22 cli.commands.util uses build.preprocessing.directives part of a loop✕
- Connections
- 1 pair of types, where a type in cli.commands.util uses a type in build.preprocessing.directives.
- The types involved
scala.cli.commands.util.JvmUtils→scala.build.preprocessing.directives.JavaOptions
- Direction
- cli.commands.util uses build.preprocessing.directives, so a change to build.preprocessing.directives can break cli.commands.util, while a change to cli.commands.util can't break build.preprocessing.directives.
- 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→23 cli.commands.util uses build.errors part of a loop✕
- Connections
- 3 pairs of types, where a type in cli.commands.util uses a type in build.errors.
- The types involved
scala.cli.commands.util.JvmUtils→scala.build.errors.BuildExceptionscala.cli.commands.util.RunHadoop→scala.build.errors.BuildExceptionscala.cli.commands.util.RunSpark→scala.build.errors.BuildException
- Direction
- cli.commands.util uses build.errors, so a change to build.errors can break cli.commands.util, while a change to cli.commands.util can't break build.errors.
- 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→24 cli.commands.util uses build.Build part of a loop✕
- Connections
- 2 pairs of types, where a type in cli.commands.util uses a type in build.Build.
- The types involved
scala.cli.commands.util.RunHadoop→scala.build.Build.Successfulscala.cli.commands.util.RunSpark→scala.build.Build.Successful
- Direction
- cli.commands.util uses build.Build, so a change to build.Build can break cli.commands.util, while a change to cli.commands.util can't break build.Build.
- 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→25 cli.commands.util uses build part of a loop✕
- Connections
- 2 pairs of types, where a type in cli.commands.util uses a type in build.
- The types involved
scala.cli.commands.util.RunHadoop→scala.build.Loggerscala.cli.commands.util.RunSpark→scala.build.Logger
- Direction
- cli.commands.util uses build, so a change to build can break cli.commands.util, while a change to cli.commands.util can't break build.
- 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→7 build.input uses build.preprocessing✕
- Connections
- 1 pair of types, where a type in build.input uses a type in build.preprocessing.
- The types involved
scala.build.input.Virtual→scala.build.preprocessing.ScopePath
- Direction
- build.input uses build.preprocessing, so a change to build.preprocessing can break build.input, while a change to build.input can't break build.preprocessing.
- Position
- Below the diagonal: build.input uses a module listed above it, which is the healthy direction.
9→20 build.input uses build.options part of a loop✕
- Connections
- 1 pair of types, where a type in build.input uses a type in build.options.
- The types involved
scala.build.input.Inputs→scala.build.options.Scope
- Direction
- build.input uses build.options, so a change to build.options can break build.input, while a change to build.input can't break build.options.
- 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→25 build.input uses build part of a loop✕
- Connections
- 1 pair of types, where a type in build.input uses a type in build.
- The types involved
scala.build.input.Inputs→scala.build.Directories
- Direction
- build.input uses build, so a change to build can break build.input, while a change to build.input can't break build.
- 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 cli.commands.repl uses cli.commands.shared✕
- Connections
- 6 pairs of types, where a type in cli.commands.repl uses a type in cli.commands.shared.
- The types involved
scala.cli.commands.repl.Repl→scala.cli.commands.shared.SharedOptionsscala.cli.commands.repl.ReplOptions→scala.cli.commands.shared.HasSharedOptionsscala.cli.commands.repl.ReplOptions→scala.cli.commands.shared.SharedOptionsscala.cli.commands.repl.SharedReplOptions→scala.cli.commands.shared.CrossOptionsscala.cli.commands.repl.SharedReplOptions→scala.cli.commands.shared.SharedJavaOptionsscala.cli.commands.repl.SharedReplOptions→scala.cli.commands.shared.SharedWatchOptions
- Direction
- cli.commands.repl uses cli.commands.shared, so a change to cli.commands.shared can break cli.commands.repl, while a change to cli.commands.repl can't break cli.commands.shared.
- Position
- Below the diagonal: cli.commands.repl uses a module listed above it, which is the healthy direction.
10→8 cli.commands.repl uses cli.commands.util✕
- Connections
- 1 pair of types, where a type in cli.commands.repl uses a type in cli.commands.util.
- The types involved
scala.cli.commands.repl.Repl→scala.cli.commands.util.BuildCommandHelpers
- Direction
- cli.commands.repl uses cli.commands.util, so a change to cli.commands.util can break cli.commands.repl, while a change to cli.commands.repl can't break cli.commands.util.
- Position
- Below the diagonal: cli.commands.repl uses a module listed above it, which is the healthy direction.
10→13 cli.commands.repl uses cli.commands part of a loop✕
- Connections
- 1 pair of types, where a type in cli.commands.repl uses a type in cli.commands.
- The types involved
scala.cli.commands.repl.Repl→scala.cli.commands.ScalaCommand
- Direction
- cli.commands.repl uses cli.commands, so a change to cli.commands can break cli.commands.repl, while a change to cli.commands.repl can't break cli.commands.
- 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→20 cli.commands.repl uses build.options part of a loop✕
- Connections
- 1 pair of types, where a type in cli.commands.repl uses a type in build.options.
- The types involved
scala.cli.commands.repl.Repl→scala.build.options.BuildOptions
- Direction
- cli.commands.repl uses build.options, so a change to build.options can break cli.commands.repl, while a change to cli.commands.repl can't break build.options.
- 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→23 cli.commands.repl uses build.errors part of a loop✕
- Connections
- 2 pairs of types, where a type in cli.commands.repl uses a type in build.errors.
- The types involved
scala.cli.commands.repl.JShellRunner→scala.build.errors.BuildExceptionscala.cli.commands.repl.Repl→scala.build.errors.BuildException
- Direction
- cli.commands.repl uses build.errors, so a change to build.errors can break cli.commands.repl, while a change to cli.commands.repl can't break build.errors.
- 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→24 cli.commands.repl uses build.Build part of a loop✕
- Connections
- 1 pair of types, where a type in cli.commands.repl uses a type in build.Build.
- The types involved
scala.cli.commands.repl.Repl→scala.build.Build.Successful
- Direction
- cli.commands.repl uses build.Build, so a change to build.Build can break cli.commands.repl, while a change to cli.commands.repl can't break build.Build.
- 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→25 cli.commands.repl uses build part of a loop✕
- Connections
- 4 pairs of types, where a type in cli.commands.repl uses a type in build.
- The types involved
scala.cli.commands.repl.JShellRunner→scala.build.Loggerscala.cli.commands.repl.Repl→scala.build.Artifactsscala.cli.commands.repl.Repl→scala.build.Buildsscala.cli.commands.repl.Repl→scala.build.Logger
- Direction
- cli.commands.repl uses build, so a change to build can break cli.commands.repl, while a change to cli.commands.repl can't break build.
- 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→6 cli.commands.run uses cli.commands.shared✕
- Connections
- 10 pairs of types, where a type in cli.commands.run uses a type in cli.commands.shared.
- The types involved
scala.cli.commands.run.Run→scala.cli.commands.shared.HelpGroupscala.cli.commands.run.Run→scala.cli.commands.shared.SharedOptionsscala.cli.commands.run.RunOptions→scala.cli.commands.shared.HasSharedOptionsscala.cli.commands.run.RunOptions→scala.cli.commands.shared.HasSharedWatchOptionsscala.cli.commands.run.RunOptions→scala.cli.commands.shared.SharedOptionsscala.cli.commands.run.RunOptions→scala.cli.commands.shared.SharedWatchOptionsscala.cli.commands.run.SharedRunOptions→scala.cli.commands.shared.CrossOptionsscala.cli.commands.run.SharedRunOptions→scala.cli.commands.shared.MainClassOptionsscala.cli.commands.run.SharedRunOptions→scala.cli.commands.shared.SharedJavaOptionsscala.cli.commands.run.SharedRunOptions→scala.cli.commands.shared.SharedWatchOptions
- Direction
- cli.commands.run uses cli.commands.shared, so a change to cli.commands.shared can break cli.commands.run, while a change to cli.commands.run can't break cli.commands.shared.
- Position
- Below the diagonal: cli.commands.run uses a module listed above it, which is the healthy direction.
11→8 cli.commands.run uses cli.commands.util✕
- Connections
- 1 pair of types, where a type in cli.commands.run uses a type in cli.commands.util.
- The types involved
scala.cli.commands.run.Run→scala.cli.commands.util.BuildCommandHelpers
- Direction
- cli.commands.run uses cli.commands.util, so a change to cli.commands.util can break cli.commands.run, while a change to cli.commands.run can't break cli.commands.util.
- Position
- Below the diagonal: cli.commands.run uses a module listed above it, which is the healthy direction.
11→9 cli.commands.run uses build.input✕
- Connections
- 1 pair of types, where a type in cli.commands.run uses a type in build.input.
- The types involved
scala.cli.commands.run.Run→scala.build.input.ScalaCliInvokeData
- Direction
- cli.commands.run uses build.input, so a change to build.input can break cli.commands.run, while a change to cli.commands.run can't break build.input.
- Position
- Below the diagonal: cli.commands.run uses a module listed above it, which is the healthy direction.
11→13 cli.commands.run uses cli.commands part of a loop✕
- Connections
- 2 pairs of types, where a type in cli.commands.run uses a type in cli.commands.
- The types involved
scala.cli.commands.run.Run→scala.cli.commands.ScalaCommandscala.cli.commands.run.Run→scala.cli.commands.SpecificationLevel
- Direction
- cli.commands.run uses cli.commands, so a change to cli.commands can break cli.commands.run, while a change to cli.commands.run can't break cli.commands.
- 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→17 cli.commands.run uses build.internal part of a loop✕
- Connections
- 1 pair of types, where a type in cli.commands.run uses a type in build.internal.
- The types involved
scala.cli.commands.run.Run→scala.build.internal.ScalaJsLinkerConfig
- Direction
- cli.commands.run uses build.internal, so a change to build.internal can break cli.commands.run, while a change to cli.commands.run can't break build.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.
11→20 cli.commands.run uses build.options part of a loop✕
- Connections
- 1 pair of types, where a type in cli.commands.run uses a type in build.options.
- The types involved
scala.cli.commands.run.Run→scala.build.options.BuildOptions
- Direction
- cli.commands.run uses build.options, so a change to build.options can break cli.commands.run, while a change to cli.commands.run can't break build.options.
- 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→22 cli.commands.run uses build.preprocessing.directives part of a loop✕
- Connections
- 1 pair of types, where a type in cli.commands.run uses a type in build.preprocessing.directives.
- The types involved
scala.cli.commands.run.Run→scala.build.preprocessing.directives.Python
- Direction
- cli.commands.run uses build.preprocessing.directives, so a change to build.preprocessing.directives can break cli.commands.run, while a change to cli.commands.run can't break build.preprocessing.directives.
- 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→23 cli.commands.run uses build.errors part of a loop✕
- Connections
- 1 pair of types, where a type in cli.commands.run uses a type in build.errors.
- The types involved
scala.cli.commands.run.Run→scala.build.errors.BuildException
- Direction
- cli.commands.run uses build.errors, so a change to build.errors can break cli.commands.run, while a change to cli.commands.run can't break build.errors.
- 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→24 cli.commands.run uses build.Build part of a loop✕
- Connections
- 1 pair of types, where a type in cli.commands.run uses a type in build.Build.
- The types involved
scala.cli.commands.run.Run→scala.build.Build.Successful
- Direction
- cli.commands.run uses build.Build, so a change to build.Build can break cli.commands.run, while a change to cli.commands.run can't break build.Build.
- 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→25 cli.commands.run uses build part of a loop✕
- Connections
- 1 pair of types, where a type in cli.commands.run uses a type in build.
- The types involved
scala.cli.commands.run.Run→scala.build.Logger
- Direction
- cli.commands.run uses build, so a change to build can break cli.commands.run, while a change to cli.commands.run can't break build.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→6 cli.commands.default uses cli.commands.shared✕
- Connections
- 5 pairs of types, where a type in cli.commands.default uses a type in cli.commands.shared.
- The types involved
scala.cli.commands.default.Default→scala.cli.commands.shared.SharedOptionsscala.cli.commands.default.DefaultFileOptions→scala.cli.commands.shared.GlobalOptionsscala.cli.commands.default.DefaultFileOptions→scala.cli.commands.shared.HasGlobalOptionsscala.cli.commands.default.DefaultOptions→scala.cli.commands.shared.HasSharedOptionsscala.cli.commands.default.DefaultOptions→scala.cli.commands.shared.SharedOptions
- Direction
- cli.commands.default uses cli.commands.shared, so a change to cli.commands.shared can break cli.commands.default, while a change to cli.commands.default can't break cli.commands.shared.
- Position
- Below the diagonal: cli.commands.default uses a module listed above it, which is the healthy direction.
12→9 cli.commands.default uses build.input✕
- Connections
- 1 pair of types, where a type in cli.commands.default uses a type in build.input.
- The types involved
scala.cli.commands.default.Default→scala.build.input.ScalaCliInvokeData
- Direction
- cli.commands.default uses build.input, so a change to build.input can break cli.commands.default, while a change to cli.commands.default can't break build.input.
- Position
- Below the diagonal: cli.commands.default uses a module listed above it, which is the healthy direction.
12→10 cli.commands.default uses cli.commands.repl✕
- Connections
- 1 pair of types, where a type in cli.commands.default uses a type in cli.commands.repl.
- The types involved
scala.cli.commands.default.DefaultOptions→scala.cli.commands.repl.SharedReplOptions
- Direction
- cli.commands.default uses cli.commands.repl, so a change to cli.commands.repl can break cli.commands.default, while a change to cli.commands.default can't break cli.commands.repl.
- Position
- Below the diagonal: cli.commands.default uses a module listed above it, which is the healthy direction.
12→11 cli.commands.default uses cli.commands.run✕
- Connections
- 1 pair of types, where a type in cli.commands.default uses a type in cli.commands.run.
- The types involved
scala.cli.commands.default.DefaultOptions→scala.cli.commands.run.SharedRunOptions
- Direction
- cli.commands.default uses cli.commands.run, so a change to cli.commands.run can break cli.commands.default, while a change to cli.commands.default can't break cli.commands.run.
- Position
- Below the diagonal: cli.commands.default uses a module listed above it, which is the healthy direction.
12→13 cli.commands.default uses cli.commands part of a loop✕
- Connections
- 2 pairs of types, where a type in cli.commands.default uses a type in cli.commands.
- The types involved
scala.cli.commands.default.Default→scala.cli.commands.ScalaCommandWithCustomHelpscala.cli.commands.default.DefaultFile→scala.cli.commands.ScalaCommand
- Direction
- cli.commands.default uses cli.commands, so a change to cli.commands can break cli.commands.default, while a change to cli.commands.default can't break cli.commands.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→25 cli.commands.default uses build part of a loop✕
- Connections
- 3 pairs of types, where a type in cli.commands.default uses a type in build.
- The types involved
scala.cli.commands.default.Default→scala.build.Loggerscala.cli.commands.default.DefaultFile→scala.build.Loggerscala.cli.commands.default.LegacyScalaOptions→scala.build.Logger
- Direction
- cli.commands.default uses build, so a change to build can break cli.commands.default, while a change to cli.commands.default can't break build.
- 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→6 cli.commands uses cli.commands.shared✕
- Connections
- 3 pairs of types, where a type in cli.commands uses a type in cli.commands.shared.
- The types involved
scala.cli.commands.HelpCmd→scala.cli.commands.shared.HelpOptionsscala.cli.commands.ScalaCommand→scala.cli.commands.shared.GlobalOptionsscala.cli.commands.ScalaCommand→scala.cli.commands.shared.SharedOptions
- Direction
- cli.commands uses cli.commands.shared, so a change to cli.commands.shared can break cli.commands, while a change to cli.commands can't break cli.commands.shared.
- Position
- Below the diagonal: cli.commands uses a module listed above it, which is the healthy direction.
13→8 cli.commands uses cli.commands.util✕
- Connections
- 1 pair of types, where a type in cli.commands uses a type in cli.commands.util.
- The types involved
scala.cli.commands.ScalaCommand→scala.cli.commands.util.CommandHelpers
- Direction
- cli.commands uses cli.commands.util, so a change to cli.commands.util can break cli.commands, while a change to cli.commands can't break cli.commands.util.
- Position
- Below the diagonal: cli.commands uses a module listed above it, which is the healthy direction.
13→9 cli.commands uses build.input✕
- Connections
- 3 pairs of types, where a type in cli.commands uses a type in build.input.
- The types involved
scala.cli.commands.RestrictableCommand→scala.build.input.ScalaCliInvokeDatascala.cli.commands.RestrictedCommandsParser→scala.build.input.ScalaCliInvokeDatascala.cli.commands.ScalaCommand→scala.build.input.ScalaCliInvokeData
- Direction
- cli.commands uses build.input, so a change to build.input can break cli.commands, while a change to cli.commands can't break build.input.
- Position
- Below the diagonal: cli.commands uses a module listed above it, which is the healthy direction.
13→12 cli.commands uses cli.commands.default✕
- Connections
- 1 pair of types, where a type in cli.commands uses a type in cli.commands.default.
- The types involved
scala.cli.commands.ScalaCommandWithCustomHelp→scala.cli.commands.default.LegacyScalaOptions
- Direction
- cli.commands uses cli.commands.default, so a change to cli.commands.default can break cli.commands, while a change to cli.commands can't break cli.commands.default.
- Position
- Below the diagonal: cli.commands uses a module listed above it, which is the healthy direction.
13→17 cli.commands uses build.internal part of a loop✕
- Connections
- 1 pair of types, where a type in cli.commands uses a type in build.internal.
- The types involved
scala.cli.commands.ScalaCommand→scala.build.internal.Name
- Direction
- cli.commands uses build.internal, so a change to build.internal can break cli.commands, while a change to cli.commands can't break build.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.
13→20 cli.commands uses build.options part of a loop✕
- Connections
- 1 pair of types, where a type in cli.commands uses a type in build.options.
- The types involved
scala.cli.commands.ScalaCommand→scala.build.options.BuildOptions
- Direction
- cli.commands uses build.options, so a change to build.options can break cli.commands, while a change to cli.commands can't break build.options.
- 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→25 cli.commands uses build part of a loop✕
- Connections
- 4 pairs of types, where a type in cli.commands uses a type in build.
- The types involved
scala.cli.commands.HelpCmd→scala.build.Loggerscala.cli.commands.RestrictableCommand→scala.build.Loggerscala.cli.commands.RestrictedCommandsParser→scala.build.Loggerscala.cli.commands.ScalaCommand→scala.build.Logger
- Direction
- cli.commands uses build, so a change to build can break cli.commands, while a change to cli.commands can't break build.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→6 cli.commands.pgp uses cli.commands.shared✕
- Connections
- 16 pairs of types, where a type in cli.commands.pgp uses a type in cli.commands.shared.
- The types involved
scala.cli.commands.pgp.PgpExternalCommand→scala.cli.commands.shared.CoursierOptionsscala.cli.commands.pgp.PgpExternalCommand→scala.cli.commands.shared.SharedJvmOptionsscala.cli.commands.pgp.PgpExternalOptions→scala.cli.commands.shared.CoursierOptionsscala.cli.commands.pgp.PgpExternalOptions→scala.cli.commands.shared.GlobalOptionsscala.cli.commands.pgp.PgpExternalOptions→scala.cli.commands.shared.HasGlobalOptionsscala.cli.commands.pgp.PgpExternalOptions→scala.cli.commands.shared.SharedJvmOptionsscala.cli.commands.pgp.PgpProxy→scala.cli.commands.shared.CoursierOptionsscala.cli.commands.pgp.PgpProxy→scala.cli.commands.shared.SharedJvmOptionsscala.cli.commands.pgp.PgpProxyJvm→scala.cli.commands.shared.CoursierOptionsscala.cli.commands.pgp.PgpProxyJvm→scala.cli.commands.shared.SharedJvmOptionsscala.cli.commands.pgp.PgpPullOptions→scala.cli.commands.shared.GlobalOptionsscala.cli.commands.pgp.PgpPullOptions→scala.cli.commands.shared.HasGlobalOptionsscala.cli.commands.pgp.PgpPushOptions→scala.cli.commands.shared.CoursierOptionsscala.cli.commands.pgp.PgpPushOptions→scala.cli.commands.shared.GlobalOptionsscala.cli.commands.pgp.PgpPushOptions→scala.cli.commands.shared.HasGlobalOptionsscala.cli.commands.pgp.PgpPushOptions→scala.cli.commands.shared.SharedJvmOptions
- Direction
- cli.commands.pgp uses cli.commands.shared, so a change to cli.commands.shared can break cli.commands.pgp, while a change to cli.commands.pgp can't break cli.commands.shared.
- Position
- Below the diagonal: cli.commands.pgp uses a module listed above it, which is the healthy direction.
14→8 cli.commands.pgp uses cli.commands.util✕
- Connections
- 2 pairs of types, where a type in cli.commands.pgp uses a type in cli.commands.util.
- The types involved
scala.cli.commands.pgp.ExternalCommand→scala.cli.commands.util.CommandHelpersscala.cli.commands.pgp.PgpCommand→scala.cli.commands.util.CommandHelpers
- Direction
- cli.commands.pgp uses cli.commands.util, so a change to cli.commands.util can break cli.commands.pgp, while a change to cli.commands.pgp can't break cli.commands.util.
- Position
- Below the diagonal: cli.commands.pgp uses a module listed above it, which is the healthy direction.
14→9 cli.commands.pgp uses build.input✕
- Connections
- 1 pair of types, where a type in cli.commands.pgp uses a type in build.input.
- The types involved
scala.cli.commands.pgp.PgpCommand→scala.build.input.ScalaCliInvokeData
- Direction
- cli.commands.pgp uses build.input, so a change to build.input can break cli.commands.pgp, while a change to cli.commands.pgp can't break build.input.
- Position
- Below the diagonal: cli.commands.pgp uses a module listed above it, which is the healthy direction.
14→13 cli.commands.pgp uses cli.commands✕
- Connections
- 3 pairs of types, where a type in cli.commands.pgp uses a type in cli.commands.
- The types involved
scala.cli.commands.pgp.PgpCommand→scala.cli.commands.RestrictableCommandscala.cli.commands.pgp.PgpPull→scala.cli.commands.ScalaCommandscala.cli.commands.pgp.PgpPush→scala.cli.commands.ScalaCommand
- Direction
- cli.commands.pgp uses cli.commands, so a change to cli.commands can break cli.commands.pgp, while a change to cli.commands.pgp can't break cli.commands.
- Position
- Below the diagonal: cli.commands.pgp uses a module listed above it, which is the healthy direction.
14→20 cli.commands.pgp uses build.options part of a loop✕
- Connections
- 4 pairs of types, where a type in cli.commands.pgp uses a type in build.options.
- The types involved
scala.cli.commands.pgp.PgpExternalCommand→scala.build.options.ScalaSigningCliOptionsscala.cli.commands.pgp.PgpProxy→scala.build.options.ScalaSigningCliOptionsscala.cli.commands.pgp.PgpProxyJvm→scala.build.options.ScalaSigningCliOptionsscala.cli.commands.pgp.PgpScalaSigningOptions→scala.build.options.ScalaSigningCliOptions
- Direction
- cli.commands.pgp uses build.options, so a change to build.options can break cli.commands.pgp, while a change to cli.commands.pgp can't break build.options.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→23 cli.commands.pgp uses build.errors part of a loop✕
- Connections
- 3 pairs of types, where a type in cli.commands.pgp uses a type in build.errors.
- The types involved
scala.cli.commands.pgp.PgpExternalCommand→scala.build.errors.BuildExceptionscala.cli.commands.pgp.PgpProxy→scala.build.errors.BuildExceptionscala.cli.commands.pgp.PgpProxyJvm→scala.build.errors.BuildException
- Direction
- cli.commands.pgp uses build.errors, so a change to build.errors can break cli.commands.pgp, while a change to cli.commands.pgp can't break build.errors.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→25 cli.commands.pgp uses build part of a loop✕
- Connections
- 7 pairs of types, where a type in cli.commands.pgp uses a type in build.
- The types involved
scala.cli.commands.pgp.PgpCommand→scala.build.Loggerscala.cli.commands.pgp.PgpExternalCommand→scala.build.Loggerscala.cli.commands.pgp.PgpProxy→scala.build.Loggerscala.cli.commands.pgp.PgpProxyJvm→scala.build.Loggerscala.cli.commands.pgp.PgpPull→scala.build.Loggerscala.cli.commands.pgp.PgpPush→scala.build.Loggerscala.cli.commands.pgp.SharedPgpPushPullOptions→scala.build.Logger
- Direction
- cli.commands.pgp uses build, so a change to build can break cli.commands.pgp, while a change to cli.commands.pgp can't break build.
- 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→3 cli.config uses cli.commands.github.GitHubApi✕
- Connections
- 2 pairs of types, where a type in cli.config uses a type in cli.commands.github.GitHubApi.
- The types involved
scala.cli.config.PasswordOption→scala.cli.commands.github.GitHubApi.Secretscala.cli.config.Secret→scala.cli.commands.github.GitHubApi.Secret
- Direction
- cli.config uses cli.commands.github.GitHubApi, so a change to cli.commands.github.GitHubApi can break cli.config, while a change to cli.config can't break cli.commands.github.GitHubApi.
- Position
- Below the diagonal: cli.config uses a module listed above it, which is the healthy direction.
15→13 cli.config uses cli.commands✕
- Connections
- 1 pair of types, where a type in cli.config uses a type in cli.commands.
- The types involved
scala.cli.config.Key→scala.cli.commands.SpecificationLevel
- Direction
- cli.config uses cli.commands, so a change to cli.commands can break cli.config, while a change to cli.config can't break cli.commands.
- Position
- Below the diagonal: cli.config uses a module listed above it, which is the healthy direction.
16→3 cli.config.PasswordOption uses cli.commands.github.GitHubApi✕
- Connections
- 4 pairs of types, where a type in cli.config.PasswordOption uses a type in cli.commands.github.GitHubApi.
- The types involved
scala.cli.config.PasswordOption.Command→scala.cli.commands.github.GitHubApi.Secretscala.cli.config.PasswordOption.Env→scala.cli.commands.github.GitHubApi.Secretscala.cli.config.PasswordOption.File→scala.cli.commands.github.GitHubApi.Secretscala.cli.config.PasswordOption.Value→scala.cli.commands.github.GitHubApi.Secret
- Direction
- cli.config.PasswordOption uses cli.commands.github.GitHubApi, so a change to cli.commands.github.GitHubApi can break cli.config.PasswordOption, while a change to cli.config.PasswordOption can't break cli.commands.github.GitHubApi.
- Position
- Below the diagonal: cli.config.PasswordOption uses a module listed above it, which is the healthy direction.
16→15 cli.config.PasswordOption uses cli.config✕
- Connections
- 4 pairs of types, where a type in cli.config.PasswordOption uses a type in cli.config.
- The types involved
scala.cli.config.PasswordOption.Command→scala.cli.config.PasswordOptionscala.cli.config.PasswordOption.Env→scala.cli.config.PasswordOptionscala.cli.config.PasswordOption.File→scala.cli.config.PasswordOptionscala.cli.config.PasswordOption.Value→scala.cli.config.PasswordOption
- Direction
- cli.config.PasswordOption uses cli.config, so a change to cli.config can break cli.config.PasswordOption, while a change to cli.config.PasswordOption can't break cli.config.
- Position
- Below the diagonal: cli.config.PasswordOption uses a module listed above it, which is the healthy direction.
17→16 build.internal uses cli.config.PasswordOption✕
- Connections
- 1 pair of types, where a type in build.internal uses a type in cli.config.PasswordOption.
- The types involved
scala.build.internal.Runner→scala.cli.config.PasswordOption.File
- Direction
- build.internal uses cli.config.PasswordOption, so a change to cli.config.PasswordOption can break build.internal, while a change to build.internal can't break cli.config.PasswordOption.
- Position
- Below the diagonal: build.internal uses a module listed above it, which is the healthy direction.
17→22 build.internal uses build.preprocessing.directives part of a loop✕
- Connections
- 1 pair of types, where a type in build.internal uses a type in build.preprocessing.directives.
- The types involved
scala.build.internal.ExternalBinaryParams→scala.build.preprocessing.directives.Dependency
- Direction
- build.internal uses build.preprocessing.directives, so a change to build.preprocessing.directives can break build.internal, while a change to build.internal can't break build.preprocessing.directives.
- 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→23 build.internal uses build.errors part of a loop✕
- Connections
- 8 pairs of types, where a type in build.internal uses a type in build.errors.
- The types involved
scala.build.internal.FetchExternalBinary→scala.build.errors.BuildExceptionscala.build.internal.JavaParserProxy→scala.build.errors.BuildExceptionscala.build.internal.JavaParserProxyBinary→scala.build.errors.BuildExceptionscala.build.internal.JavaParserProxyJvm→scala.build.errors.BuildExceptionscala.build.internal.Runner→scala.build.errors.BuildExceptionscala.build.internal.Runner→scala.build.errors.NoTestFrameworkFoundErrorscala.build.internal.Runner→scala.build.errors.NoTestsRunscala.build.internal.Runner→scala.build.errors.TestError
- Direction
- build.internal uses build.errors, so a change to build.errors can break build.internal, while a change to build.internal can't break build.errors.
- 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→25 build.internal uses build part of a loop✕
- Connections
- 5 pairs of types, where a type in build.internal uses a type in build.
- The types involved
scala.build.internal.FetchExternalBinary→scala.build.Loggerscala.build.internal.JavaParserProxyBinary→scala.build.Loggerscala.build.internal.JavaParserProxyMaker→scala.build.Loggerscala.build.internal.MainClass→scala.build.Loggerscala.build.internal.Runner→scala.build.Logger
- Direction
- build.internal uses build, so a change to build can break build.internal, while a change to build.internal can't break build.
- 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→4 cli.commands.package0 uses build.compiler✕
- Connections
- 1 pair of types, where a type in cli.commands.package0 uses a type in build.compiler.
- The types involved
scala.cli.commands.package0.PackageOptions→scala.build.compiler.ScalaCompilerMaker
- Direction
- cli.commands.package0 uses build.compiler, so a change to build.compiler can break cli.commands.package0, while a change to cli.commands.package0 can't break build.compiler.
- Position
- Below the diagonal: cli.commands.package0 uses a module listed above it, which is the healthy direction.
18→6 cli.commands.package0 uses cli.commands.shared✕
- Connections
- 10 pairs of types, where a type in cli.commands.package0 uses a type in cli.commands.shared.
- The types involved
scala.cli.commands.package0.Package→scala.cli.commands.shared.HelpGroupscala.cli.commands.package0.Package→scala.cli.commands.shared.MainClassOptionsscala.cli.commands.package0.Package→scala.cli.commands.shared.SharedOptionsscala.cli.commands.package0.PackageOptions→scala.cli.commands.shared.CrossOptionsscala.cli.commands.package0.PackageOptions→scala.cli.commands.shared.HasSharedOptionsscala.cli.commands.package0.PackageOptions→scala.cli.commands.shared.HasSharedWatchOptionsscala.cli.commands.package0.PackageOptions→scala.cli.commands.shared.MainClassOptionsscala.cli.commands.package0.PackageOptions→scala.cli.commands.shared.SharedJavaOptionsscala.cli.commands.package0.PackageOptions→scala.cli.commands.shared.SharedOptionsscala.cli.commands.package0.PackageOptions→scala.cli.commands.shared.SharedWatchOptions
- Direction
- cli.commands.package0 uses cli.commands.shared, so a change to cli.commands.shared can break cli.commands.package0, while a change to cli.commands.package0 can't break cli.commands.shared.
- Position
- Below the diagonal: cli.commands.package0 uses a module listed above it, which is the healthy direction.
18→8 cli.commands.package0 uses cli.commands.util✕
- Connections
- 1 pair of types, where a type in cli.commands.package0 uses a type in cli.commands.util.
- The types involved
scala.cli.commands.package0.Package→scala.cli.commands.util.BuildCommandHelpers
- Direction
- cli.commands.package0 uses cli.commands.util, so a change to cli.commands.util can break cli.commands.package0, while a change to cli.commands.package0 can't break cli.commands.util.
- Position
- Below the diagonal: cli.commands.package0 uses a module listed above it, which is the healthy direction.
18→13 cli.commands.package0 uses cli.commands✕
- Connections
- 1 pair of types, where a type in cli.commands.package0 uses a type in cli.commands.
- The types involved
scala.cli.commands.package0.Package→scala.cli.commands.ScalaCommand
- Direction
- cli.commands.package0 uses cli.commands, so a change to cli.commands can break cli.commands.package0, while a change to cli.commands.package0 can't break cli.commands.
- Position
- Below the diagonal: cli.commands.package0 uses a module listed above it, which is the healthy direction.
18→17 cli.commands.package0 uses build.internal✕
- Connections
- 1 pair of types, where a type in cli.commands.package0 uses a type in build.internal.
- The types involved
scala.cli.commands.package0.Package→scala.build.internal.ScalaJsLinkerConfig
- Direction
- cli.commands.package0 uses build.internal, so a change to build.internal can break cli.commands.package0, while a change to cli.commands.package0 can't break build.internal.
- Position
- Below the diagonal: cli.commands.package0 uses a module listed above it, which is the healthy direction.
18→20 cli.commands.package0 uses build.options part of a loop✕
- Connections
- 4 pairs of types, where a type in cli.commands.package0 uses a type in build.options.
- The types involved
scala.cli.commands.package0.Package→scala.build.options.BuildOptionsscala.cli.commands.package0.Package→scala.build.options.PackageTypescala.cli.commands.package0.PackageOptions→scala.build.options.BuildOptionsscala.cli.commands.package0.PackageOptions→scala.build.options.PackageType
- Direction
- cli.commands.package0 uses build.options, so a change to build.options can break cli.commands.package0, while a change to cli.commands.package0 can't break build.options.
- 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→23 cli.commands.package0 uses build.errors part of a loop✕
- Connections
- 2 pairs of types, where a type in cli.commands.package0 uses a type in build.errors.
- The types involved
scala.cli.commands.package0.Package→scala.build.errors.BuildExceptionscala.cli.commands.package0.PackageOptions→scala.build.errors.BuildException
- Direction
- cli.commands.package0 uses build.errors, so a change to build.errors can break cli.commands.package0, while a change to cli.commands.package0 can't break build.errors.
- 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→24 cli.commands.package0 uses build.Build part of a loop✕
- Connections
- 1 pair of types, where a type in cli.commands.package0 uses a type in build.Build.
- The types involved
scala.cli.commands.package0.Package→scala.build.Build.Successful
- Direction
- cli.commands.package0 uses build.Build, so a change to build.Build can break cli.commands.package0, while a change to cli.commands.package0 can't break build.Build.
- 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→25 cli.commands.package0 uses build part of a loop✕
- Connections
- 3 pairs of types, where a type in cli.commands.package0 uses a type in build.
- The types involved
scala.cli.commands.package0.Package→scala.build.Loggerscala.cli.commands.package0.PackageOptions→scala.build.BuildThreadsscala.cli.commands.package0.PackageOptions→scala.build.Logger
- Direction
- cli.commands.package0 uses build, so a change to build can break cli.commands.package0, while a change to cli.commands.package0 can't break build.
- 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→2 cli.commands.publish uses build.options.publish✕
- Connections
- 2 pairs of types, where a type in cli.commands.publish uses a type in build.options.publish.
- The types involved
scala.cli.commands.publish.Ivy→scala.build.options.publish.Developerscala.cli.commands.publish.PublishUtils→scala.build.options.publish.Signer
- Direction
- cli.commands.publish uses build.options.publish, so a change to build.options.publish can break cli.commands.publish, while a change to cli.commands.publish can't break build.options.publish.
- Position
- Below the diagonal: cli.commands.publish uses a module listed above it, which is the healthy direction.
19→3 cli.commands.publish uses cli.commands.github.GitHubApi✕
- Connections
- 1 pair of types, where a type in cli.commands.publish uses a type in cli.commands.github.GitHubApi.
- The types involved
scala.cli.commands.publish.SetSecret→scala.cli.commands.github.GitHubApi.Secret
- Direction
- cli.commands.publish uses cli.commands.github.GitHubApi, so a change to cli.commands.github.GitHubApi can break cli.commands.publish, while a change to cli.commands.publish can't break cli.commands.github.GitHubApi.
- Position
- Below the diagonal: cli.commands.publish uses a module listed above it, which is the healthy direction.
19→4 cli.commands.publish uses build.compiler✕
- Connections
- 2 pairs of types, where a type in cli.commands.publish uses a type in build.compiler.
- The types involved
scala.cli.commands.publish.Publish→scala.build.compiler.ScalaCompilerMakerscala.cli.commands.publish.SharedPublishOptions→scala.build.compiler.ScalaCompilerMaker
- Direction
- cli.commands.publish uses build.compiler, so a change to build.compiler can break cli.commands.publish, while a change to cli.commands.publish can't break build.compiler.
- Position
- Below the diagonal: cli.commands.publish uses a module listed above it, which is the healthy direction.
19→6 cli.commands.publish uses cli.commands.shared✕
- Connections
- 24 pairs of types, where a type in cli.commands.publish uses a type in cli.commands.shared.
- The types involved
scala.cli.commands.publish.Publish→scala.cli.commands.shared.HelpGroupscala.cli.commands.publish.Publish→scala.cli.commands.shared.MainClassOptionsscala.cli.commands.publish.Publish→scala.cli.commands.shared.SharedOptionsscala.cli.commands.publish.Publish→scala.cli.commands.shared.SharedVersionOptionsscala.cli.commands.publish.PublishLocal→scala.cli.commands.shared.SharedOptionsscala.cli.commands.publish.PublishLocalOptions→scala.cli.commands.shared.CrossOptionsscala.cli.commands.publish.PublishLocalOptions→scala.cli.commands.shared.HasSharedOptionsscala.cli.commands.publish.PublishLocalOptions→scala.cli.commands.shared.HasSharedWatchOptionsscala.cli.commands.publish.PublishLocalOptions→scala.cli.commands.shared.MainClassOptionsscala.cli.commands.publish.PublishLocalOptions→scala.cli.commands.shared.SharedOptionsscala.cli.commands.publish.PublishLocalOptions→scala.cli.commands.shared.SharedWatchOptionsscala.cli.commands.publish.PublishOptions→scala.cli.commands.shared.CrossOptionsscala.cli.commands.publish.PublishOptions→scala.cli.commands.shared.HasSharedOptionsscala.cli.commands.publish.PublishOptions→scala.cli.commands.shared.HasSharedWatchOptionsscala.cli.commands.publish.PublishOptions→scala.cli.commands.shared.MainClassOptionsscala.cli.commands.publish.PublishOptions→scala.cli.commands.shared.SharedOptionsscala.cli.commands.publish.PublishOptions→scala.cli.commands.shared.SharedWatchOptionsscala.cli.commands.publish.PublishSetupOptions→scala.cli.commands.shared.CoursierOptionsscala.cli.commands.publish.PublishSetupOptions→scala.cli.commands.shared.GlobalOptionsscala.cli.commands.publish.PublishSetupOptions→scala.cli.commands.shared.HasGlobalOptionsscala.cli.commands.publish.PublishSetupOptions→scala.cli.commands.shared.SharedInputOptionsscala.cli.commands.publish.PublishSetupOptions→scala.cli.commands.shared.SharedJvmOptionsscala.cli.commands.publish.PublishSetupOptions→scala.cli.commands.shared.SharedVersionOptionsscala.cli.commands.publish.PublishSetupOptions→scala.cli.commands.shared.SharedWorkspaceOptions
- Direction
- cli.commands.publish uses cli.commands.shared, so a change to cli.commands.shared can break cli.commands.publish, while a change to cli.commands.publish can't break cli.commands.shared.
- Position
- Below the diagonal: cli.commands.publish uses a module listed above it, which is the healthy direction.
19→8 cli.commands.publish uses cli.commands.util✕
- Connections
- 1 pair of types, where a type in cli.commands.publish uses a type in cli.commands.util.
- The types involved
scala.cli.commands.publish.Publish→scala.cli.commands.util.BuildCommandHelpers
- Direction
- cli.commands.publish uses cli.commands.util, so a change to cli.commands.util can break cli.commands.publish, while a change to cli.commands.publish can't break cli.commands.util.
- Position
- Below the diagonal: cli.commands.publish uses a module listed above it, which is the healthy direction.
19→9 cli.commands.publish uses build.input✕
- Connections
- 1 pair of types, where a type in cli.commands.publish uses a type in build.input.
- The types involved
scala.cli.commands.publish.Publish→scala.build.input.Inputs
- Direction
- cli.commands.publish uses build.input, so a change to build.input can break cli.commands.publish, while a change to cli.commands.publish can't break build.input.
- Position
- Below the diagonal: cli.commands.publish uses a module listed above it, which is the healthy direction.
19→13 cli.commands.publish uses cli.commands✕
- Connections
- 5 pairs of types, where a type in cli.commands.publish uses a type in cli.commands.
- The types involved
scala.cli.commands.publish.Publish→scala.cli.commands.ScalaCommandscala.cli.commands.publish.Publish→scala.cli.commands.SpecificationLevelscala.cli.commands.publish.PublishLocal→scala.cli.commands.ScalaCommandscala.cli.commands.publish.PublishSetup→scala.cli.commands.ScalaCommandscala.cli.commands.publish.PublishSetup→scala.cli.commands.SpecificationLevel
- Direction
- cli.commands.publish uses cli.commands, so a change to cli.commands can break cli.commands.publish, while a change to cli.commands.publish can't break cli.commands.
- Position
- Below the diagonal: cli.commands.publish uses a module listed above it, which is the healthy direction.
19→14 cli.commands.publish uses cli.commands.pgp✕
- Connections
- 5 pairs of types, where a type in cli.commands.publish uses a type in cli.commands.pgp.
- The types involved
scala.cli.commands.publish.Publish→scala.cli.commands.pgp.PgpScalaSigningOptionsscala.cli.commands.publish.PublishLocalOptions→scala.cli.commands.pgp.PgpScalaSigningOptionsscala.cli.commands.publish.PublishOptions→scala.cli.commands.pgp.PgpScalaSigningOptionsscala.cli.commands.publish.PublishSetupOptions→scala.cli.commands.pgp.PgpScalaSigningOptionsscala.cli.commands.publish.PublishSetupOptions→scala.cli.commands.pgp.SharedPgpPushPullOptions
- Direction
- cli.commands.publish uses cli.commands.pgp, so a change to cli.commands.pgp can break cli.commands.publish, while a change to cli.commands.publish can't break cli.commands.pgp.
- Position
- Below the diagonal: cli.commands.publish uses a module listed above it, which is the healthy direction.
19→15 cli.commands.publish uses cli.config✕
- Connections
- 4 pairs of types, where a type in cli.commands.publish uses a type in cli.config.
- The types involved
scala.cli.commands.publish.PublishRepositoryOptions→scala.cli.config.PasswordOptionscala.cli.commands.publish.PublishSetupOptions→scala.cli.config.PasswordOptionscala.cli.commands.publish.PublishUtils→scala.cli.config.PasswordOptionscala.cli.commands.publish.PublishUtils→scala.cli.config.PublishCredentials
- Direction
- cli.commands.publish uses cli.config, so a change to cli.config can break cli.commands.publish, while a change to cli.commands.publish can't break cli.config.
- Position
- Below the diagonal: cli.commands.publish uses a module listed above it, which is the healthy direction.
19→17 cli.commands.publish uses build.internal✕
- Connections
- 1 pair of types, where a type in cli.commands.publish uses a type in build.internal.
- The types involved
scala.cli.commands.publish.Ivy→scala.build.internal.License
- Direction
- cli.commands.publish uses build.internal, so a change to build.internal can break cli.commands.publish, while a change to cli.commands.publish can't break build.internal.
- Position
- Below the diagonal: cli.commands.publish uses a module listed above it, which is the healthy direction.
19→20 cli.commands.publish uses build.options part of a loop✕
- Connections
- 3 pairs of types, where a type in cli.commands.publish uses a type in build.options.
- The types involved
scala.cli.commands.publish.Publish→scala.build.options.BuildOptionsscala.cli.commands.publish.PublishLocal→scala.build.options.BuildOptionsscala.cli.commands.publish.PublishUtils→scala.build.options.BuildOptions
- Direction
- cli.commands.publish uses build.options, so a change to build.options can break cli.commands.publish, while a change to cli.commands.publish can't break build.options.
- 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→23 cli.commands.publish uses build.errors part of a loop✕
- Connections
- 4 pairs of types, where a type in cli.commands.publish uses a type in build.errors.
- The types involved
scala.cli.commands.publish.GitRepoError→scala.build.errors.BuildExceptionscala.cli.commands.publish.OptionCheck→scala.build.errors.BuildExceptionscala.cli.commands.publish.Publish→scala.build.errors.BuildExceptionscala.cli.commands.publish.PublishUtils→scala.build.errors.BuildException
- Direction
- cli.commands.publish uses build.errors, so a change to build.errors can break cli.commands.publish, while a change to cli.commands.publish can't break build.errors.
- 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→24 cli.commands.publish uses build.Build part of a loop✕
- Connections
- 1 pair of types, where a type in cli.commands.publish uses a type in build.Build.
- The types involved
scala.cli.commands.publish.Publish→scala.build.Build.Successful
- Direction
- cli.commands.publish uses build.Build, so a change to build.Build can break cli.commands.publish, while a change to cli.commands.publish can't break build.Build.
- 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 cli.commands.publish uses build part of a loop✕
- Connections
- 7 pairs of types, where a type in cli.commands.publish uses a type in build.
- The types involved
scala.cli.commands.publish.GitRepo→scala.build.Loggerscala.cli.commands.publish.OptionChecks→scala.build.Loggerscala.cli.commands.publish.Publish→scala.build.Buildsscala.cli.commands.publish.Publish→scala.build.Loggerscala.cli.commands.publish.PublishLocal→scala.build.Loggerscala.cli.commands.publish.PublishSetup→scala.build.Loggerscala.cli.commands.publish.PublishUtils→scala.build.Logger
- Direction
- cli.commands.publish uses build, so a change to build can break cli.commands.publish, while a change to cli.commands.publish can't break build.
- 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→2 build.options uses build.options.publish✕
- Connections
- 4 pairs of types, where a type in build.options uses a type in build.options.publish.
- The types involved
scala.build.options.PublishContextualOptions→scala.build.options.publish.ConfigPasswordOptionscala.build.options.PublishContextualOptions→scala.build.options.publish.Signerscala.build.options.PublishOptions→scala.build.options.publish.Developerscala.build.options.PublishOptions→scala.build.options.publish.Vcs
- Direction
- build.options uses build.options.publish, so a change to build.options.publish can break build.options, while a change to build.options can't break build.options.publish.
- Position
- Below the diagonal: build.options uses a module listed above it, which is the healthy direction.
20→6 build.options uses cli.commands.shared✕
- Connections
- 5 pairs of types, where a type in build.options uses a type in cli.commands.shared.
- The types involved
scala.build.options.BuildOptions→scala.cli.commands.shared.ScalaJsOptionsscala.build.options.BuildOptions→scala.cli.commands.shared.ScalaNativeOptionsscala.build.options.BuildOptions→scala.cli.commands.shared.SourceGeneratorOptionsscala.build.options.BuildOptions→scala.cli.commands.shared.SuppressWarningOptionsscala.build.options.ScalaOptions→scala.cli.commands.shared.SemanticDbOptions
- Direction
- build.options uses cli.commands.shared, so a change to cli.commands.shared can break build.options, while a change to build.options can't break cli.commands.shared.
- Position
- Below the diagonal: build.options uses a module listed above it, which is the healthy direction.
20→10 build.options uses cli.commands.repl✕
- Connections
- 1 pair of types, where a type in build.options uses a type in cli.commands.repl.
- The types involved
scala.build.options.PostBuildOptions→scala.cli.commands.repl.ReplOptions
- Direction
- build.options uses cli.commands.repl, so a change to cli.commands.repl can break build.options, while a change to build.options can't break cli.commands.repl.
- Position
- Below the diagonal: build.options uses a module listed above it, which is the healthy direction.
20→15 build.options uses cli.config✕
- Connections
- 1 pair of types, where a type in build.options uses a type in cli.config.
- The types involved
scala.build.options.PublishContextualOptions→scala.cli.config.PasswordOption
- Direction
- build.options uses cli.config, so a change to cli.config can break build.options, while a change to build.options can't break cli.config.
- Position
- Below the diagonal: build.options uses a module listed above it, which is the healthy direction.
20→17 build.options uses build.internal✕
- Connections
- 2 pairs of types, where a type in build.options uses a type in build.internal.
- The types involved
scala.build.options.PublishOptions→scala.build.internal.Licensescala.build.options.ScalaJsOptions→scala.build.internal.ScalaJsLinkerConfig
- Direction
- build.options uses build.internal, so a change to build.internal can break build.options, while a change to build.options can't break build.internal.
- Position
- Below the diagonal: build.options uses a module listed above it, which is the healthy direction.
20→18 build.options uses cli.commands.package0✕
- Connections
- 1 pair of types, where a type in build.options uses a type in cli.commands.package0.
- The types involved
scala.build.options.PostBuildOptions→scala.cli.commands.package0.PackageOptions
- Direction
- build.options uses cli.commands.package0, so a change to cli.commands.package0 can break build.options, while a change to build.options can't break cli.commands.package0.
- Position
- Below the diagonal: build.options uses a module listed above it, which is the healthy direction.
20→19 build.options uses cli.commands.publish✕
- Connections
- 1 pair of types, where a type in build.options uses a type in cli.commands.publish.
- The types involved
scala.build.options.PostBuildOptions→scala.cli.commands.publish.PublishOptions
- Direction
- build.options uses cli.commands.publish, so a change to cli.commands.publish can break build.options, while a change to build.options can't break cli.commands.publish.
- Position
- Below the diagonal: build.options uses a module listed above it, which is the healthy direction.
20→22 build.options uses build.preprocessing.directives part of a loop✕
- Connections
- 9 pairs of types, where a type in build.options uses a type in build.preprocessing.directives.
- The types involved
scala.build.options.BuildOptions→scala.build.preprocessing.directives.JavaHomescala.build.options.BuildOptions→scala.build.preprocessing.directives.JavaOptionsscala.build.options.BuildOptions→scala.build.preprocessing.directives.Platformscala.build.options.BuildRequirements→scala.build.preprocessing.directives.Platformscala.build.options.JavaOptions→scala.build.preprocessing.directives.JavaHomescala.build.options.PublishContextualOptions→scala.build.preprocessing.directives.ComputeVersionscala.build.options.ScalaOptions→scala.build.preprocessing.directives.Platformscala.build.options.SourceGeneratorOptions→scala.build.preprocessing.directives.ComputeVersionscala.build.options.WithBuildRequirements→scala.build.preprocessing.directives.Platform
- Direction
- build.options uses build.preprocessing.directives, so a change to build.preprocessing.directives can break build.options, while a change to build.options can't break build.preprocessing.directives.
- 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→23 build.options uses build.errors part of a loop✕
- Connections
- 7 pairs of types, where a type in build.options uses a type in build.errors.
- The types involved
scala.build.options.BuildOptions→scala.build.errors.BuildExceptionscala.build.options.BuildOptions→scala.build.errors.Diagnosticscala.build.options.ComputeVersion→scala.build.errors.BuildExceptionscala.build.options.ScalaJsOptions→scala.build.errors.BuildExceptionscala.build.options.ScalaJsOptions→scala.build.errors.UnrecognizedJsEsVersionErrorscala.build.options.ScalaJsOptions→scala.build.errors.UnrecognizedJsOptModeErrorscala.build.options.ScalaVersionUtil→scala.build.errors.ScalaVersionError
- Direction
- build.options uses build.errors, so a change to build.errors can break build.options, while a change to build.options can't break build.errors.
- 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→25 build.options uses build part of a loop✕
- Connections
- 11 pairs of types, where a type in build.options uses a type in build.
- The types involved
scala.build.options.BuildOptions→scala.build.Artifactsscala.build.options.BuildOptions→scala.build.Loggerscala.build.options.BuildOptions→scala.build.Positionedscala.build.options.ClassPathOptions→scala.build.Positionedscala.build.options.ComputeVersion→scala.build.Positionscala.build.options.InternalOptions→scala.build.Positionedscala.build.options.JavaOptions→scala.build.Positionedscala.build.options.PublishOptions→scala.build.Positionedscala.build.options.ScalaJsOptions→scala.build.Loggerscala.build.options.ScalaOptions→scala.build.Positionedscala.build.options.TestOptions→scala.build.Positioned
- Direction
- build.options uses build, so a change to build can break build.options, while a change to build.options can't break build.
- 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→7 build.directives uses build.preprocessing✕
- Connections
- 1 pair of types, where a type in build.directives uses a type in build.preprocessing.
- The types involved
scala.build.directives.DirectiveValueParser→scala.build.preprocessing.ScopePath
- Direction
- build.directives uses build.preprocessing, so a change to build.preprocessing can break build.directives, while a change to build.directives can't break build.preprocessing.
- Position
- Below the diagonal: build.directives uses a module listed above it, which is the healthy direction.
21→13 build.directives uses cli.commands✕
- Connections
- 1 pair of types, where a type in build.directives uses a type in cli.commands.
- The types involved
scala.build.directives.DirectiveLevel→scala.cli.commands.SpecificationLevel
- Direction
- build.directives uses cli.commands, so a change to cli.commands can break build.directives, while a change to build.directives can't break cli.commands.
- Position
- Below the diagonal: build.directives uses a module listed above it, which is the healthy direction.
21→20 build.directives uses build.options✕
- Connections
- 4 pairs of types, where a type in build.directives uses a type in build.options.
- The types involved
scala.build.directives.HasBuildOptions→scala.build.options.BuildOptionsscala.build.directives.HasBuildOptionsWithRequirements→scala.build.options.BuildOptionsscala.build.directives.HasBuildOptionsWithRequirements→scala.build.options.WithBuildRequirementsscala.build.directives.HasBuildRequirements→scala.build.options.BuildRequirements
- Direction
- build.directives uses build.options, so a change to build.options can break build.directives, while a change to build.directives can't break build.options.
- Position
- Below the diagonal: build.directives uses a module listed above it, which is the healthy direction.
21→23 build.directives uses build.errors part of a loop✕
- Connections
- 4 pairs of types, where a type in build.directives uses a type in build.errors.
- The types involved
scala.build.directives.DirectiveValueParser→scala.build.errors.BuildExceptionscala.build.directives.HasBuildOptions→scala.build.errors.BuildExceptionscala.build.directives.HasBuildOptionsWithRequirements→scala.build.errors.BuildExceptionscala.build.directives.HasBuildRequirements→scala.build.errors.BuildException
- Direction
- build.directives uses build.errors, so a change to build.errors can break build.directives, while a change to build.directives can't break build.errors.
- 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.
22→7 build.preprocessing.directives uses build.preprocessing✕
- Connections
- 5 pairs of types, where a type in build.preprocessing.directives uses a type in build.preprocessing.
- The types involved
scala.build.preprocessing.directives.PartiallyProcessedDirectives→scala.build.preprocessing.Scopedscala.build.preprocessing.directives.PreprocessedDirectives→scala.build.preprocessing.Scopedscala.build.preprocessing.directives.ProcessedDirective→scala.build.preprocessing.Scopedscala.build.preprocessing.directives.ScopedDirective→scala.build.preprocessing.ScopePathscala.build.preprocessing.directives.ScopedValue→scala.build.preprocessing.ScopePath
- Direction
- build.preprocessing.directives uses build.preprocessing, so a change to build.preprocessing can break build.preprocessing.directives, while a change to build.preprocessing.directives can't break build.preprocessing.
- Position
- Below the diagonal: build.preprocessing.directives uses a module listed above it, which is the healthy direction.
22→13 build.preprocessing.directives uses cli.commands✕
- Connections
- 1 pair of types, where a type in build.preprocessing.directives uses a type in cli.commands.
- The types involved
scala.build.preprocessing.directives.DirectiveHandler→scala.cli.commands.SpecificationLevel
- Direction
- build.preprocessing.directives uses cli.commands, so a change to cli.commands can break build.preprocessing.directives, while a change to build.preprocessing.directives can't break cli.commands.
- Position
- Below the diagonal: build.preprocessing.directives uses a module listed above it, which is the healthy direction.
22→15 build.preprocessing.directives uses cli.config✕
- Connections
- 1 pair of types, where a type in build.preprocessing.directives uses a type in cli.config.
- The types involved
scala.build.preprocessing.directives.DirectiveHandler→scala.cli.config.Key
- Direction
- build.preprocessing.directives uses cli.config, so a change to cli.config can break build.preprocessing.directives, while a change to build.preprocessing.directives can't break cli.config.
- Position
- Below the diagonal: build.preprocessing.directives uses a module listed above it, which is the healthy direction.
22→16 build.preprocessing.directives uses cli.config.PasswordOption✕
- Connections
- 3 pairs of types, where a type in build.preprocessing.directives uses a type in cli.config.PasswordOption.
- The types involved
scala.build.preprocessing.directives.DirectiveUtil→scala.cli.config.PasswordOption.Filescala.build.preprocessing.directives.PreprocessedDirectives→scala.cli.config.PasswordOption.Filescala.build.preprocessing.directives.StrictDirective→scala.cli.config.PasswordOption.File
- Direction
- build.preprocessing.directives uses cli.config.PasswordOption, so a change to cli.config.PasswordOption can break build.preprocessing.directives, while a change to build.preprocessing.directives can't break cli.config.PasswordOption.
- Position
- Below the diagonal: build.preprocessing.directives uses a module listed above it, which is the healthy direction.
22→20 build.preprocessing.directives uses build.options✕
- Connections
- 51 pairs of types, where a type in build.preprocessing.directives uses a type in build.options. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
scala.build.preprocessing.directives.Benchmarking→scala.build.options.BuildOptionsscala.build.preprocessing.directives.BuildInfo→scala.build.options.BuildOptionsscala.build.preprocessing.directives.ComputeVersion→scala.build.options.BuildOptionsscala.build.preprocessing.directives.CustomJar→scala.build.options.BuildOptionsscala.build.preprocessing.directives.CustomJar→scala.build.options.WithBuildRequirementsscala.build.preprocessing.directives.Dependency→scala.build.options.BuildOptionsscala.build.preprocessing.directives.Dependency→scala.build.options.WithBuildRequirementsscala.build.preprocessing.directives.DirectivesPreprocessingUtils→scala.build.options.BuildOptionsscala.build.preprocessing.directives.DirectivesPreprocessingUtils→scala.build.options.BuildRequirementsscala.build.preprocessing.directives.DirectivesPreprocessingUtils→scala.build.options.WithBuildRequirementsscala.build.preprocessing.directives.Exclude→scala.build.options.BuildOptionsscala.build.preprocessing.directives.JavaHome→scala.build.options.BuildOptionsscala.build.preprocessing.directives.JavaOptions→scala.build.options.BuildOptionsscala.build.preprocessing.directives.JavaOptions→scala.build.options.WithBuildRequirementsscala.build.preprocessing.directives.JavaProps→scala.build.options.BuildOptionsscala.build.preprocessing.directives.JavaProps→scala.build.options.WithBuildRequirementsscala.build.preprocessing.directives.JavacOptions→scala.build.options.BuildOptionsscala.build.preprocessing.directives.JavacOptions→scala.build.options.WithBuildRequirementsscala.build.preprocessing.directives.Jvm→scala.build.options.BuildOptionsscala.build.preprocessing.directives.MainClass→scala.build.options.BuildOptionsscala.build.preprocessing.directives.ObjectWrapper→scala.build.options.BuildOptionsscala.build.preprocessing.directives.Packaging→scala.build.options.BuildOptionsscala.build.preprocessing.directives.Platform→scala.build.options.BuildOptionsscala.build.preprocessing.directives.Plugin→scala.build.options.BuildOptionsscala.build.preprocessing.directives.PreprocessedDirectives→scala.build.options.BuildOptions
- Direction
- build.preprocessing.directives uses build.options, so a change to build.options can break build.preprocessing.directives, while a change to build.preprocessing.directives can't break build.options.
- Position
- Below the diagonal: build.preprocessing.directives uses a module listed above it, which is the healthy direction.
22→21 build.preprocessing.directives uses build.directives✕
- Connections
- 36 pairs of types, where a type in build.preprocessing.directives uses a type in build.directives. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
scala.build.preprocessing.directives.Benchmarking→scala.build.directives.HasBuildOptionsscala.build.preprocessing.directives.BuildInfo→scala.build.directives.HasBuildOptionsscala.build.preprocessing.directives.ComputeVersion→scala.build.directives.HasBuildOptionsscala.build.preprocessing.directives.CustomJar→scala.build.directives.HasBuildOptionsWithRequirementsscala.build.preprocessing.directives.Dependency→scala.build.directives.HasBuildOptionsWithRequirementsscala.build.preprocessing.directives.Exclude→scala.build.directives.HasBuildOptionsscala.build.preprocessing.directives.JavaHome→scala.build.directives.HasBuildOptionsscala.build.preprocessing.directives.JavaOptions→scala.build.directives.HasBuildOptionsWithRequirementsscala.build.preprocessing.directives.JavaProps→scala.build.directives.HasBuildOptionsWithRequirementsscala.build.preprocessing.directives.JavacOptions→scala.build.directives.HasBuildOptionsWithRequirementsscala.build.preprocessing.directives.Jvm→scala.build.directives.HasBuildOptionsscala.build.preprocessing.directives.MainClass→scala.build.directives.HasBuildOptionsscala.build.preprocessing.directives.ObjectWrapper→scala.build.directives.HasBuildOptionsscala.build.preprocessing.directives.Packaging→scala.build.directives.HasBuildOptionsscala.build.preprocessing.directives.Platform→scala.build.directives.HasBuildOptionsscala.build.preprocessing.directives.Plugin→scala.build.directives.HasBuildOptionsscala.build.preprocessing.directives.Publish→scala.build.directives.HasBuildOptionsscala.build.preprocessing.directives.Python→scala.build.directives.HasBuildOptionsscala.build.preprocessing.directives.Repository→scala.build.directives.HasBuildOptionsscala.build.preprocessing.directives.RequirePlatform→scala.build.directives.HasBuildRequirementsscala.build.preprocessing.directives.RequireScalaVersion→scala.build.directives.HasBuildRequirementsscala.build.preprocessing.directives.RequireScalaVersionBounds→scala.build.directives.HasBuildRequirementsscala.build.preprocessing.directives.RequireScope→scala.build.directives.HasBuildRequirementsscala.build.preprocessing.directives.Resources→scala.build.directives.HasBuildOptionsWithRequirementsscala.build.preprocessing.directives.ScalaJs→scala.build.directives.HasBuildOptions
- Direction
- build.preprocessing.directives uses build.directives, so a change to build.directives can break build.preprocessing.directives, while a change to build.preprocessing.directives can't break build.directives.
- Position
- Below the diagonal: build.preprocessing.directives uses a module listed above it, which is the healthy direction.
22→23 build.preprocessing.directives uses build.errors part of a loop✕
- Connections
- 41 pairs of types, where a type in build.preprocessing.directives uses a type in build.errors. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
scala.build.preprocessing.directives.Benchmarking→scala.build.errors.BuildExceptionscala.build.preprocessing.directives.BuildInfo→scala.build.errors.BuildExceptionscala.build.preprocessing.directives.ComputeVersion→scala.build.errors.BuildExceptionscala.build.preprocessing.directives.CustomJar→scala.build.errors.BuildExceptionscala.build.preprocessing.directives.Dependency→scala.build.errors.BuildExceptionscala.build.preprocessing.directives.DirectiveHandler→scala.build.errors.BuildExceptionscala.build.preprocessing.directives.Exclude→scala.build.errors.BuildExceptionscala.build.preprocessing.directives.ImportMapNotFound→scala.build.errors.BuildExceptionscala.build.preprocessing.directives.JavaHome→scala.build.errors.BuildExceptionscala.build.preprocessing.directives.JavaOptions→scala.build.errors.BuildExceptionscala.build.preprocessing.directives.JavaProps→scala.build.errors.BuildExceptionscala.build.preprocessing.directives.JavacOptions→scala.build.errors.BuildExceptionscala.build.preprocessing.directives.Jvm→scala.build.errors.BuildExceptionscala.build.preprocessing.directives.MainClass→scala.build.errors.BuildExceptionscala.build.preprocessing.directives.ObjectWrapper→scala.build.errors.BuildExceptionscala.build.preprocessing.directives.Packaging→scala.build.errors.BuildExceptionscala.build.preprocessing.directives.Platform→scala.build.errors.BuildExceptionscala.build.preprocessing.directives.Plugin→scala.build.errors.BuildExceptionscala.build.preprocessing.directives.ProcessedDirective→scala.build.errors.BuildExceptionscala.build.preprocessing.directives.Publish→scala.build.errors.BuildExceptionscala.build.preprocessing.directives.PublishContextual→scala.build.errors.BuildExceptionscala.build.preprocessing.directives.Python→scala.build.errors.BuildExceptionscala.build.preprocessing.directives.Repository→scala.build.errors.BuildExceptionscala.build.preprocessing.directives.RequirePlatform→scala.build.errors.BuildExceptionscala.build.preprocessing.directives.RequireScalaVersion→scala.build.errors.BuildException
- Direction
- build.preprocessing.directives uses build.errors, so a change to build.errors can break build.preprocessing.directives, while a change to build.preprocessing.directives can't break build.errors.
- 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.
22→25 build.preprocessing.directives uses build part of a loop✕
- Connections
- 28 pairs of types, where a type in build.preprocessing.directives uses a type in build. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
scala.build.preprocessing.directives.Benchmarking→scala.build.Positionedscala.build.preprocessing.directives.ComputeVersion→scala.build.Positionedscala.build.preprocessing.directives.CustomJar→scala.build.Positionedscala.build.preprocessing.directives.Dependency→scala.build.Positionedscala.build.preprocessing.directives.Directive→scala.build.Positionscala.build.preprocessing.directives.DirectiveHandler→scala.build.Loggerscala.build.preprocessing.directives.DirectiveUtil→scala.build.Positionscala.build.preprocessing.directives.Exclude→scala.build.Positionedscala.build.preprocessing.directives.JavaHome→scala.build.Positionedscala.build.preprocessing.directives.JavaOptions→scala.build.Positionedscala.build.preprocessing.directives.JavaProps→scala.build.Positionedscala.build.preprocessing.directives.JavacOptions→scala.build.Positionedscala.build.preprocessing.directives.Jvm→scala.build.Positionedscala.build.preprocessing.directives.Packaging→scala.build.Positionedscala.build.preprocessing.directives.Platform→scala.build.Positionedscala.build.preprocessing.directives.Plugin→scala.build.Positionedscala.build.preprocessing.directives.Publish→scala.build.Positionedscala.build.preprocessing.directives.PublishContextual→scala.build.Positionedscala.build.preprocessing.directives.RequirePlatform→scala.build.Positionedscala.build.preprocessing.directives.RequireScope→scala.build.Positionedscala.build.preprocessing.directives.Resources→scala.build.Positionedscala.build.preprocessing.directives.ScalaJs→scala.build.Positionedscala.build.preprocessing.directives.ScalacOptions→scala.build.Positionedscala.build.preprocessing.directives.ScopedValue→scala.build.Positionedscala.build.preprocessing.directives.Sources→scala.build.Positioned
- Direction
- build.preprocessing.directives uses build, so a change to build can break build.preprocessing.directives, while a change to build.preprocessing.directives can't break build.
- 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.
23→1 build.errors uses build.bsp.protocol✕
- Connections
- 1 pair of types, where a type in build.errors uses a type in build.bsp.protocol.
- The types involved
scala.build.errors.Diagnostic→scala.build.bsp.protocol.TextEdit
- Direction
- build.errors uses build.bsp.protocol, so a change to build.bsp.protocol can break build.errors, while a change to build.errors can't break build.bsp.protocol.
- Position
- Below the diagonal: build.errors uses a module listed above it, which is the healthy direction.
23→22 build.errors uses build.preprocessing.directives✕
- Connections
- 1 pair of types, where a type in build.errors uses a type in build.preprocessing.directives.
- The types involved
scala.build.errors.SingleValueExpectedError→scala.build.preprocessing.directives.StrictDirective
- Direction
- build.errors uses build.preprocessing.directives, so a change to build.preprocessing.directives can break build.errors, while a change to build.errors can't break build.preprocessing.directives.
- Position
- Below the diagonal: build.errors uses a module listed above it, which is the healthy direction.
23→25 build.errors uses build part of a loop✕
- Connections
- 6 pairs of types, where a type in build.errors uses a type in build.
- The types involved
scala.build.errors.BuildException→scala.build.Positionscala.build.errors.Diagnostic→scala.build.Positionscala.build.errors.FetchingDependenciesError→scala.build.Positionscala.build.errors.ForbiddenPathReferenceError→scala.build.Positionscala.build.errors.UnsupportedFeatureError→scala.build.Positionscala.build.errors.UnsupportedGradleModuleVariantError→scala.build.Position
- Direction
- build.errors uses build, so a change to build can break build.errors, while a change to build.errors can't break build.
- 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.
24→9 build.Build uses build.input✕
- Connections
- 3 pairs of types, where a type in build.Build uses a type in build.input.
- The types involved
scala.build.Build.Cancelled→scala.build.input.Inputsscala.build.Build.Failed→scala.build.input.Inputsscala.build.Build.Successful→scala.build.input.Inputs
- Direction
- build.Build uses build.input, so a change to build.input can break build.Build, while a change to build.Build can't break build.input.
- Position
- Below the diagonal: build.Build uses a module listed above it, which is the healthy direction.
24→20 build.Build uses build.options✕
- Connections
- 6 pairs of types, where a type in build.Build uses a type in build.options.
- The types involved
scala.build.Build.Cancelled→scala.build.options.BuildOptionsscala.build.Build.Cancelled→scala.build.options.Scopescala.build.Build.Failed→scala.build.options.BuildOptionsscala.build.Build.Failed→scala.build.options.Scopescala.build.Build.Successful→scala.build.options.BuildOptionsscala.build.Build.Successful→scala.build.options.Scope
- Direction
- build.Build uses build.options, so a change to build.options can break build.Build, while a change to build.Build can't break build.options.
- Position
- Below the diagonal: build.Build uses a module listed above it, which is the healthy direction.
24→23 build.Build uses build.errors✕
- Connections
- 1 pair of types, where a type in build.Build uses a type in build.errors.
- The types involved
scala.build.Build.Successful→scala.build.errors.BuildException
- Direction
- build.Build uses build.errors, so a change to build.errors can break build.Build, while a change to build.Build can't break build.errors.
- Position
- Below the diagonal: build.Build uses a module listed above it, which is the healthy direction.
24→25 build.Build uses build part of a loop✕
- Connections
- 12 pairs of types, where a type in build.Build uses a type in build.
- The types involved
scala.build.Build.Cancelled→scala.build.Buildscala.build.Build.Failed→scala.build.Artifactsscala.build.Build.Failed→scala.build.Buildscala.build.Build.Failed→scala.build.Projectscala.build.Build.Failed→scala.build.Sourcesscala.build.Build.Successful→scala.build.Artifactsscala.build.Build.Successful→scala.build.Buildscala.build.Build.Successful→scala.build.CrossKeyscala.build.Build.Successful→scala.build.GeneratedSourcescala.build.Build.Successful→scala.build.Loggerscala.build.Build.Successful→scala.build.Projectscala.build.Build.Successful→scala.build.Sources
- Direction
- build.Build uses build, so a change to build can break build.Build, while a change to build.Build can't break build.
- 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.
25→5 build uses build.internals✕
- Connections
- 2 pairs of types, where a type in build uses a type in build.internals.
- The types involved
scala.build.Logger→scala.build.internals.FeatureTypescala.build.PersistentDiagnosticLogger→scala.build.internals.FeatureType
- Direction
- build uses build.internals, so a change to build.internals can break build, while a change to build can't break build.internals.
- Position
- Below the diagonal: build uses a module listed above it, which is the healthy direction.
25→9 build uses build.input✕
- Connections
- 2 pairs of types, where a type in build uses a type in build.input.
- The types involved
scala.build.Build→scala.build.input.Inputsscala.build.Sources→scala.build.input.Inputs
- Direction
- build uses build.input, so a change to build.input can break build, while a change to build can't break build.input.
- Position
- Below the diagonal: build uses a module listed above it, which is the healthy direction.
25→16 build uses cli.config.PasswordOption✕
- Connections
- 2 pairs of types, where a type in build uses a type in cli.config.PasswordOption.
- The types involved
scala.build.Bloop→scala.cli.config.PasswordOption.Filescala.build.Project→scala.cli.config.PasswordOption.File
- Direction
- build uses cli.config.PasswordOption, so a change to cli.config.PasswordOption can break build, while a change to build can't break cli.config.PasswordOption.
- Position
- Below the diagonal: build uses a module listed above it, which is the healthy direction.
25→17 build uses build.internal✕
- Connections
- 1 pair of types, where a type in build uses a type in build.internal.
- The types involved
scala.build.GeneratedSource→scala.build.internal.WrapperParams
- Direction
- build uses build.internal, so a change to build.internal can break build, while a change to build can't break build.internal.
- Position
- Below the diagonal: build uses a module listed above it, which is the healthy direction.
25→20 build uses build.options✕
- Connections
- 16 pairs of types, where a type in build uses a type in build.options.
- The types involved
scala.build.BloopBuildClient→scala.build.options.Scopescala.build.Build→scala.build.options.BuildOptionsscala.build.Build→scala.build.options.Scopescala.build.Builds→scala.build.options.Scopescala.build.ConsoleBloopBuildClient→scala.build.options.Scopescala.build.CrossKey→scala.build.options.MaybeScalaVersionscala.build.CrossKey→scala.build.options.Scopescala.build.CrossSources→scala.build.options.BuildOptionsscala.build.CrossSources→scala.build.options.WithBuildRequirementsscala.build.Project→scala.build.options.ScalacOptscala.build.Project→scala.build.options.Scopescala.build.ScopedSources→scala.build.options.BuildOptionsscala.build.ScopedSources→scala.build.options.HasScopescala.build.ScopedSources→scala.build.options.Scopescala.build.Sources→scala.build.options.BuildOptionsscala.build.Sources→scala.build.options.Scope
- Direction
- build uses build.options, so a change to build.options can break build, while a change to build can't break build.options.
- Position
- Below the diagonal: build uses a module listed above it, which is the healthy direction.
25→22 build uses build.preprocessing.directives✕
- Connections
- 2 pairs of types, where a type in build uses a type in build.preprocessing.directives.
- The types involved
scala.build.CrossKey→scala.build.preprocessing.directives.Platformscala.build.ScopedSources→scala.build.preprocessing.directives.BuildInfo
- Direction
- build uses build.preprocessing.directives, so a change to build.preprocessing.directives can break build, while a change to build can't break build.preprocessing.directives.
- Position
- Below the diagonal: build uses a module listed above it, which is the healthy direction.
25→23 build uses build.errors✕
- Connections
- 9 pairs of types, where a type in build uses a type in build.errors.
- The types involved
scala.build.Bloop→scala.build.errors.BuildExceptionscala.build.ConsoleBloopBuildClient→scala.build.errors.Diagnosticscala.build.CrossSources→scala.build.errors.BuildExceptionscala.build.Logger→scala.build.errors.BuildExceptionscala.build.Logger→scala.build.errors.Diagnosticscala.build.Logger→scala.build.errors.Severityscala.build.PersistentDiagnosticLogger→scala.build.errors.BuildExceptionscala.build.PersistentDiagnosticLogger→scala.build.errors.Diagnosticscala.build.ScopedSources→scala.build.errors.BuildException
- Direction
- build uses build.errors, so a change to build.errors can break build, while a change to build can't break build.errors.
- Position
- Below the diagonal: build uses a module listed above it, which is the healthy direction.
25→24 build uses build.Build✕
- Connections
- 2 pairs of types, where a type in build uses a type in build.Build.
- The types involved
scala.build.Build→scala.build.Build.Successfulscala.build.Builds→scala.build.Build.Successful
- Direction
- build uses build.Build, so a change to build.Build can break build, while a change to build can't break build.Build.
- Position
- Below the diagonal: build uses a module listed above it, which is the healthy direction.
26→1 build.actionable.ActionableDiagnostic uses build.bsp.protocol✕
- Connections
- 1 pair of types, where a type in build.actionable.ActionableDiagnostic uses a type in build.bsp.protocol.
- The types involved
scala.build.actionable.ActionableDiagnostic.ActionableDependencyUpdateDiagnostic→scala.build.bsp.protocol.TextEdit
- Direction
- build.actionable.ActionableDiagnostic uses build.bsp.protocol, so a change to build.bsp.protocol can break build.actionable.ActionableDiagnostic, while a change to build.actionable.ActionableDiagnostic can't break build.bsp.protocol.
- Position
- Below the diagonal: build.actionable.ActionableDiagnostic uses a module listed above it, which is the healthy direction.
26→23 build.actionable.ActionableDiagnostic uses build.errors✕
- Connections
- 2 pairs of types, where a type in build.actionable.ActionableDiagnostic uses a type in build.errors.
- The types involved
scala.build.actionable.ActionableDiagnostic.ActionableDependencyUpdateDiagnostic→scala.build.errors.Diagnosticscala.build.actionable.ActionableDiagnostic.ActionableDependencyUpdateDiagnostic→scala.build.errors.Severity
- Direction
- build.actionable.ActionableDiagnostic uses build.errors, so a change to build.errors can break build.actionable.ActionableDiagnostic, while a change to build.actionable.ActionableDiagnostic can't break build.errors.
- Position
- Below the diagonal: build.actionable.ActionableDiagnostic uses a module listed above it, which is the healthy direction.
26→25 build.actionable.ActionableDiagnostic uses build✕
- Connections
- 1 pair of types, where a type in build.actionable.ActionableDiagnostic uses a type in build.
- The types involved
scala.build.actionable.ActionableDiagnostic.ActionableDependencyUpdateDiagnostic→scala.build.Position
- Direction
- build.actionable.ActionableDiagnostic uses build, so a change to build can break build.actionable.ActionableDiagnostic, while a change to build.actionable.ActionableDiagnostic can't break build.
- Position
- Below the diagonal: build.actionable.ActionableDiagnostic uses a module listed above it, which is the healthy direction.
27→20 build.bsp.BspImpl uses build.options✕
- Connections
- 2 pairs of types, where a type in build.bsp.BspImpl uses a type in build.options.
- The types involved
scala.build.bsp.BspImpl.LoggingBspClient→scala.build.options.Scopescala.build.bsp.BspImpl.PreBuildData→scala.build.options.BuildOptions
- Direction
- build.bsp.BspImpl uses build.options, so a change to build.options can break build.bsp.BspImpl, while a change to build.bsp.BspImpl can't break build.options.
- Position
- Below the diagonal: build.bsp.BspImpl uses a module listed above it, which is the healthy direction.
27→23 build.bsp.BspImpl uses build.errors✕
- Connections
- 1 pair of types, where a type in build.bsp.BspImpl uses a type in build.errors.
- The types involved
scala.build.bsp.BspImpl.PreBuildProject→scala.build.errors.Diagnostic
- Direction
- build.bsp.BspImpl uses build.errors, so a change to build.errors can break build.bsp.BspImpl, while a change to build.bsp.BspImpl can't break build.errors.
- Position
- Below the diagonal: build.bsp.BspImpl uses a module listed above it, which is the healthy direction.
27→25 build.bsp.BspImpl uses build✕
- Connections
- 6 pairs of types, where a type in build.bsp.BspImpl uses a type in build.
- The types involved
scala.build.bsp.BspImpl.LoggingBspClient→scala.build.BloopBuildClientscala.build.bsp.BspImpl.LoggingBspClient→scala.build.GeneratedSourcescala.build.bsp.BspImpl.PreBuildData→scala.build.Artifactsscala.build.bsp.BspImpl.PreBuildData→scala.build.GeneratedSourcescala.build.bsp.BspImpl.PreBuildData→scala.build.Projectscala.build.bsp.BspImpl.PreBuildData→scala.build.Sources
- Direction
- build.bsp.BspImpl uses build, so a change to build can break build.bsp.BspImpl, while a change to build.bsp.BspImpl can't break build.
- Position
- Below the diagonal: build.bsp.BspImpl uses a module listed above it, which is the healthy direction.
27→38 build.bsp.BspImpl uses build.bsp part of a loop✕
- Connections
- 2 pairs of types, where a type in build.bsp.BspImpl uses a type in build.bsp.
- The types involved
scala.build.bsp.BspImpl.LoggingBspClient→scala.build.bsp.BspClientscala.build.bsp.BspImpl.LoggingBspClient→scala.build.bsp.LoggingBuildClient
- Direction
- build.bsp.BspImpl uses build.bsp, so a change to build.bsp can break build.bsp.BspImpl, while a change to build.bsp.BspImpl can't break build.bsp.
- 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.
28→3 cli.commands.config uses cli.commands.github.GitHubApi✕
- Connections
- 1 pair of types, where a type in cli.commands.config uses a type in cli.commands.github.GitHubApi.
- The types involved
scala.cli.commands.config.ThrowawayPgpSecret→scala.cli.commands.github.GitHubApi.Secret
- Direction
- cli.commands.config uses cli.commands.github.GitHubApi, so a change to cli.commands.github.GitHubApi can break cli.commands.config, while a change to cli.commands.config can't break cli.commands.github.GitHubApi.
- Position
- Below the diagonal: cli.commands.config uses a module listed above it, which is the healthy direction.
28→6 cli.commands.config uses cli.commands.shared✕
- Connections
- 6 pairs of types, where a type in cli.commands.config uses a type in cli.commands.shared.
- The types involved
scala.cli.commands.config.ConfigOptions→scala.cli.commands.shared.CoursierOptionsscala.cli.commands.config.ConfigOptions→scala.cli.commands.shared.GlobalOptionsscala.cli.commands.config.ConfigOptions→scala.cli.commands.shared.HasGlobalOptionsscala.cli.commands.config.ConfigOptions→scala.cli.commands.shared.SharedJvmOptionsscala.cli.commands.config.ThrowawayPgpSecret→scala.cli.commands.shared.CoursierOptionsscala.cli.commands.config.ThrowawayPgpSecret→scala.cli.commands.shared.SharedJvmOptions
- Direction
- cli.commands.config uses cli.commands.shared, so a change to cli.commands.shared can break cli.commands.config, while a change to cli.commands.config can't break cli.commands.shared.
- Position
- Below the diagonal: cli.commands.config uses a module listed above it, which is the healthy direction.
28→13 cli.commands.config uses cli.commands✕
- Connections
- 2 pairs of types, where a type in cli.commands.config uses a type in cli.commands.
- The types involved
scala.cli.commands.config.Config→scala.cli.commands.ScalaCommandscala.cli.commands.config.Config→scala.cli.commands.SpecificationLevel
- Direction
- cli.commands.config uses cli.commands, so a change to cli.commands can break cli.commands.config, while a change to cli.commands.config can't break cli.commands.
- Position
- Below the diagonal: cli.commands.config uses a module listed above it, which is the healthy direction.
28→14 cli.commands.config uses cli.commands.pgp✕
- Connections
- 1 pair of types, where a type in cli.commands.config uses a type in cli.commands.pgp.
- The types involved
scala.cli.commands.config.ConfigOptions→scala.cli.commands.pgp.PgpScalaSigningOptions
- Direction
- cli.commands.config uses cli.commands.pgp, so a change to cli.commands.pgp can break cli.commands.config, while a change to cli.commands.config can't break cli.commands.pgp.
- Position
- Below the diagonal: cli.commands.config uses a module listed above it, which is the healthy direction.
28→15 cli.commands.config uses cli.config✕
- Connections
- 3 pairs of types, where a type in cli.commands.config uses a type in cli.config.
- The types involved
scala.cli.commands.config.Config→scala.cli.config.ConfigDbscala.cli.commands.config.Config→scala.cli.config.Keyscala.cli.commands.config.Config→scala.cli.config.PasswordOption
- Direction
- cli.commands.config uses cli.config, so a change to cli.config can break cli.commands.config, while a change to cli.commands.config can't break cli.config.
- Position
- Below the diagonal: cli.commands.config uses a module listed above it, which is the healthy direction.
28→20 cli.commands.config uses build.options✕
- Connections
- 1 pair of types, where a type in cli.commands.config uses a type in build.options.
- The types involved
scala.cli.commands.config.ThrowawayPgpSecret→scala.build.options.ScalaSigningCliOptions
- Direction
- cli.commands.config uses build.options, so a change to build.options can break cli.commands.config, while a change to cli.commands.config can't break build.options.
- Position
- Below the diagonal: cli.commands.config uses a module listed above it, which is the healthy direction.
28→23 cli.commands.config uses build.errors✕
- Connections
- 2 pairs of types, where a type in cli.commands.config uses a type in build.errors.
- The types involved
scala.cli.commands.config.Config→scala.build.errors.BuildExceptionscala.cli.commands.config.ThrowawayPgpSecret→scala.build.errors.BuildException
- Direction
- cli.commands.config uses build.errors, so a change to build.errors can break cli.commands.config, while a change to cli.commands.config can't break build.errors.
- Position
- Below the diagonal: cli.commands.config uses a module listed above it, which is the healthy direction.
28→25 cli.commands.config uses build✕
- Connections
- 2 pairs of types, where a type in cli.commands.config uses a type in build.
- The types involved
scala.cli.commands.config.Config→scala.build.Loggerscala.cli.commands.config.ThrowawayPgpSecret→scala.build.Logger
- Direction
- cli.commands.config uses build, so a change to build can break cli.commands.config, while a change to cli.commands.config can't break build.
- Position
- Below the diagonal: cli.commands.config uses a module listed above it, which is the healthy direction.
29→6 cli.commands.doc uses cli.commands.shared✕
- Connections
- 4 pairs of types, where a type in cli.commands.doc uses a type in cli.commands.shared.
- The types involved
scala.cli.commands.doc.Doc→scala.cli.commands.shared.SharedOptionsscala.cli.commands.doc.DocOptions→scala.cli.commands.shared.CrossOptionsscala.cli.commands.doc.DocOptions→scala.cli.commands.shared.HasSharedOptionsscala.cli.commands.doc.DocOptions→scala.cli.commands.shared.SharedOptions
- Direction
- cli.commands.doc uses cli.commands.shared, so a change to cli.commands.shared can break cli.commands.doc, while a change to cli.commands.doc can't break cli.commands.shared.
- Position
- Below the diagonal: cli.commands.doc uses a module listed above it, which is the healthy direction.
29→8 cli.commands.doc uses cli.commands.util✕
- Connections
- 1 pair of types, where a type in cli.commands.doc uses a type in cli.commands.util.
- The types involved
scala.cli.commands.doc.Doc→scala.cli.commands.util.BuildCommandHelpers
- Direction
- cli.commands.doc uses cli.commands.util, so a change to cli.commands.util can break cli.commands.doc, while a change to cli.commands.doc can't break cli.commands.util.
- Position
- Below the diagonal: cli.commands.doc uses a module listed above it, which is the healthy direction.
29→13 cli.commands.doc uses cli.commands✕
- Connections
- 2 pairs of types, where a type in cli.commands.doc uses a type in cli.commands.
- The types involved
scala.cli.commands.doc.Doc→scala.cli.commands.ScalaCommandscala.cli.commands.doc.Doc→scala.cli.commands.SpecificationLevel
- Direction
- cli.commands.doc uses cli.commands, so a change to cli.commands can break cli.commands.doc, while a change to cli.commands.doc can't break cli.commands.
- Position
- Below the diagonal: cli.commands.doc uses a module listed above it, which is the healthy direction.
29→20 cli.commands.doc uses build.options✕
- Connections
- 1 pair of types, where a type in cli.commands.doc uses a type in build.options.
- The types involved
scala.cli.commands.doc.Doc→scala.build.options.BuildOptions
- Direction
- cli.commands.doc uses build.options, so a change to build.options can break cli.commands.doc, while a change to cli.commands.doc can't break build.options.
- Position
- Below the diagonal: cli.commands.doc uses a module listed above it, which is the healthy direction.
29→23 cli.commands.doc uses build.errors✕
- Connections
- 1 pair of types, where a type in cli.commands.doc uses a type in build.errors.
- The types involved
scala.cli.commands.doc.Doc→scala.build.errors.BuildException
- Direction
- cli.commands.doc uses build.errors, so a change to build.errors can break cli.commands.doc, while a change to cli.commands.doc can't break build.errors.
- Position
- Below the diagonal: cli.commands.doc uses a module listed above it, which is the healthy direction.
29→24 cli.commands.doc uses build.Build✕
- Connections
- 1 pair of types, where a type in cli.commands.doc uses a type in build.Build.
- The types involved
scala.cli.commands.doc.Doc→scala.build.Build.Successful
- Direction
- cli.commands.doc uses build.Build, so a change to build.Build can break cli.commands.doc, while a change to cli.commands.doc can't break build.Build.
- Position
- Below the diagonal: cli.commands.doc uses a module listed above it, which is the healthy direction.
29→25 cli.commands.doc uses build✕
- Connections
- 2 pairs of types, where a type in cli.commands.doc uses a type in build.
- The types involved
scala.cli.commands.doc.Doc→scala.build.CrossBuildParamsscala.cli.commands.doc.Doc→scala.build.Logger
- Direction
- cli.commands.doc uses build, so a change to build can break cli.commands.doc, while a change to cli.commands.doc can't break build.
- Position
- Below the diagonal: cli.commands.doc uses a module listed above it, which is the healthy direction.
30→4 cli.commands.fix uses build.compiler✕
- Connections
- 1 pair of types, where a type in cli.commands.fix uses a type in build.compiler.
- The types involved
scala.cli.commands.fix.ScalafixRules→scala.build.compiler.ScalaCompilerMaker
- Direction
- cli.commands.fix uses build.compiler, so a change to build.compiler can break cli.commands.fix, while a change to cli.commands.fix can't break build.compiler.
- Position
- Below the diagonal: cli.commands.fix uses a module listed above it, which is the healthy direction.
30→6 cli.commands.fix uses cli.commands.shared✕
- Connections
- 5 pairs of types, where a type in cli.commands.fix uses a type in cli.commands.shared.
- The types involved
scala.cli.commands.fix.BuiltInRules→scala.cli.commands.shared.SuppressWarningOptionsscala.cli.commands.fix.Fix→scala.cli.commands.shared.SharedOptionsscala.cli.commands.fix.FixOptions→scala.cli.commands.shared.HasSharedOptionsscala.cli.commands.fix.FixOptions→scala.cli.commands.shared.SharedOptionsscala.cli.commands.fix.ScalafixRules→scala.cli.commands.shared.SharedOptions
- Direction
- cli.commands.fix uses cli.commands.shared, so a change to cli.commands.shared can break cli.commands.fix, while a change to cli.commands.fix can't break cli.commands.shared.
- Position
- Below the diagonal: cli.commands.fix uses a module listed above it, which is the healthy direction.
30→7 cli.commands.fix uses build.preprocessing✕
- Connections
- 1 pair of types, where a type in cli.commands.fix uses a type in build.preprocessing.
- The types involved
scala.cli.commands.fix.BuiltInRules→scala.build.preprocessing.ExtractedDirectives
- Direction
- cli.commands.fix uses build.preprocessing, so a change to build.preprocessing can break cli.commands.fix, while a change to cli.commands.fix can't break build.preprocessing.
- Position
- Below the diagonal: cli.commands.fix uses a module listed above it, which is the healthy direction.
30→8 cli.commands.fix uses cli.commands.util✕
- Connections
- 2 pairs of types, where a type in cli.commands.fix uses a type in cli.commands.util.
- The types involved
scala.cli.commands.fix.BuiltInRules→scala.cli.commands.util.CommandHelpersscala.cli.commands.fix.ScalafixRules→scala.cli.commands.util.CommandHelpers
- Direction
- cli.commands.fix uses cli.commands.util, so a change to cli.commands.util can break cli.commands.fix, while a change to cli.commands.fix can't break cli.commands.util.
- Position
- Below the diagonal: cli.commands.fix uses a module listed above it, which is the healthy direction.
30→9 cli.commands.fix uses build.input✕
- Connections
- 4 pairs of types, where a type in cli.commands.fix uses a type in build.input.
- The types involved
scala.cli.commands.fix.BuiltInRules→scala.build.input.Inputsscala.cli.commands.fix.BuiltInRules→scala.build.input.ScalaCliInvokeDatascala.cli.commands.fix.ScalafixRules→scala.build.input.Inputsscala.cli.commands.fix.ScalafixRules→scala.build.input.ScalaCliInvokeData
- Direction
- cli.commands.fix uses build.input, so a change to build.input can break cli.commands.fix, while a change to cli.commands.fix can't break build.input.
- Position
- Below the diagonal: cli.commands.fix uses a module listed above it, which is the healthy direction.
30→13 cli.commands.fix uses cli.commands✕
- Connections
- 1 pair of types, where a type in cli.commands.fix uses a type in cli.commands.
- The types involved
scala.cli.commands.fix.Fix→scala.cli.commands.ScalaCommand
- Direction
- cli.commands.fix uses cli.commands, so a change to cli.commands can break cli.commands.fix, while a change to cli.commands.fix can't break cli.commands.
- Position
- Below the diagonal: cli.commands.fix uses a module listed above it, which is the healthy direction.
30→15 cli.commands.fix uses cli.config✕
- Connections
- 1 pair of types, where a type in cli.commands.fix uses a type in cli.config.
- The types involved
scala.cli.commands.fix.BuiltInRules→scala.cli.config.Key
- Direction
- cli.commands.fix uses cli.config, so a change to cli.config can break cli.commands.fix, while a change to cli.commands.fix can't break cli.config.
- Position
- Below the diagonal: cli.commands.fix uses a module listed above it, which is the healthy direction.
30→16 cli.commands.fix uses cli.config.PasswordOption✕
- Connections
- 1 pair of types, where a type in cli.commands.fix uses a type in cli.config.PasswordOption.
- The types involved
scala.cli.commands.fix.BuiltInRules→scala.cli.config.PasswordOption.File
- Direction
- cli.commands.fix uses cli.config.PasswordOption, so a change to cli.config.PasswordOption can break cli.commands.fix, while a change to cli.commands.fix can't break cli.config.PasswordOption.
- Position
- Below the diagonal: cli.commands.fix uses a module listed above it, which is the healthy direction.
30→20 cli.commands.fix uses build.options✕
- Connections
- 2 pairs of types, where a type in cli.commands.fix uses a type in build.options.
- The types involved
scala.cli.commands.fix.BuiltInRules→scala.build.options.BuildOptionsscala.cli.commands.fix.ScalafixRules→scala.build.options.BuildOptions
- Direction
- cli.commands.fix uses build.options, so a change to build.options can break cli.commands.fix, while a change to cli.commands.fix can't break build.options.
- Position
- Below the diagonal: cli.commands.fix uses a module listed above it, which is the healthy direction.
30→22 cli.commands.fix uses build.preprocessing.directives✕
- Connections
- 1 pair of types, where a type in cli.commands.fix uses a type in build.preprocessing.directives.
- The types involved
scala.cli.commands.fix.BuiltInRules→scala.build.preprocessing.directives.StrictDirective
- Direction
- cli.commands.fix uses build.preprocessing.directives, so a change to build.preprocessing.directives can break cli.commands.fix, while a change to cli.commands.fix can't break build.preprocessing.directives.
- Position
- Below the diagonal: cli.commands.fix uses a module listed above it, which is the healthy direction.
30→23 cli.commands.fix uses build.errors✕
- Connections
- 2 pairs of types, where a type in cli.commands.fix uses a type in build.errors.
- The types involved
scala.cli.commands.fix.BuiltInRules→scala.build.errors.BuildExceptionscala.cli.commands.fix.ScalafixRules→scala.build.errors.BuildException
- Direction
- cli.commands.fix uses build.errors, so a change to build.errors can break cli.commands.fix, while a change to cli.commands.fix can't break build.errors.
- Position
- Below the diagonal: cli.commands.fix uses a module listed above it, which is the healthy direction.
30→25 cli.commands.fix uses build✕
- Connections
- 5 pairs of types, where a type in cli.commands.fix uses a type in build.
- The types involved
scala.cli.commands.fix.BuiltInRules→scala.build.CrossSourcesscala.cli.commands.fix.BuiltInRules→scala.build.Loggerscala.cli.commands.fix.BuiltInRules→scala.build.Sourcesscala.cli.commands.fix.Fix→scala.build.Loggerscala.cli.commands.fix.ScalafixRules→scala.build.Logger
- Direction
- cli.commands.fix uses build, so a change to build can break cli.commands.fix, while a change to cli.commands.fix can't break build.
- Position
- Below the diagonal: cli.commands.fix uses a module listed above it, which is the healthy direction.
31→6 cli.commands.fmt uses cli.commands.shared✕
- Connections
- 4 pairs of types, where a type in cli.commands.fmt uses a type in cli.commands.shared.
- The types involved
scala.cli.commands.fmt.Fmt→scala.cli.commands.shared.HelpGroupscala.cli.commands.fmt.Fmt→scala.cli.commands.shared.SharedOptionsscala.cli.commands.fmt.FmtOptions→scala.cli.commands.shared.HasSharedOptionsscala.cli.commands.fmt.FmtOptions→scala.cli.commands.shared.SharedOptions
- Direction
- cli.commands.fmt uses cli.commands.shared, so a change to cli.commands.shared can break cli.commands.fmt, while a change to cli.commands.fmt can't break cli.commands.shared.
- Position
- Below the diagonal: cli.commands.fmt uses a module listed above it, which is the healthy direction.
31→13 cli.commands.fmt uses cli.commands✕
- Connections
- 1 pair of types, where a type in cli.commands.fmt uses a type in cli.commands.
- The types involved
scala.cli.commands.fmt.Fmt→scala.cli.commands.ScalaCommand
- Direction
- cli.commands.fmt uses cli.commands, so a change to cli.commands can break cli.commands.fmt, while a change to cli.commands.fmt can't break cli.commands.
- Position
- Below the diagonal: cli.commands.fmt uses a module listed above it, which is the healthy direction.
31→20 cli.commands.fmt uses build.options✕
- Connections
- 1 pair of types, where a type in cli.commands.fmt uses a type in build.options.
- The types involved
scala.cli.commands.fmt.FmtOptions→scala.build.options.BuildOptions
- Direction
- cli.commands.fmt uses build.options, so a change to build.options can break cli.commands.fmt, while a change to cli.commands.fmt can't break build.options.
- Position
- Below the diagonal: cli.commands.fmt uses a module listed above it, which is the healthy direction.
31→23 cli.commands.fmt uses build.errors✕
- Connections
- 1 pair of types, where a type in cli.commands.fmt uses a type in build.errors.
- The types involved
scala.cli.commands.fmt.FmtOptions→scala.build.errors.BuildException
- Direction
- cli.commands.fmt uses build.errors, so a change to build.errors can break cli.commands.fmt, while a change to cli.commands.fmt can't break build.errors.
- Position
- Below the diagonal: cli.commands.fmt uses a module listed above it, which is the healthy direction.
31→25 cli.commands.fmt uses build✕
- Connections
- 2 pairs of types, where a type in cli.commands.fmt uses a type in build.
- The types involved
scala.cli.commands.fmt.Fmt→scala.build.Loggerscala.cli.commands.fmt.FmtUtil→scala.build.Logger
- Direction
- cli.commands.fmt uses build, so a change to build can break cli.commands.fmt, while a change to cli.commands.fmt can't break build.
- Position
- Below the diagonal: cli.commands.fmt uses a module listed above it, which is the healthy direction.
32→3 cli.commands.github uses cli.commands.github.GitHubApi✕
- Connections
- 7 pairs of types, where a type in cli.commands.github uses a type in cli.commands.github.GitHubApi.
- The types involved
scala.cli.commands.github.GitHubApi→scala.cli.commands.github.GitHubApi.EncryptedSecretscala.cli.commands.github.GitHubApi→scala.cli.commands.github.GitHubApi.PublicKeyscala.cli.commands.github.GitHubApi→scala.cli.commands.github.GitHubApi.SecretListscala.cli.commands.github.SecretCreate→scala.cli.commands.github.GitHubApi.PublicKeyscala.cli.commands.github.SecretCreate→scala.cli.commands.github.GitHubApi.Secretscala.cli.commands.github.SecretList→scala.cli.commands.github.GitHubApi.Secretscala.cli.commands.github.SecretList→scala.cli.commands.github.GitHubApi.SecretList
- Direction
- cli.commands.github uses cli.commands.github.GitHubApi, so a change to cli.commands.github.GitHubApi can break cli.commands.github, while a change to cli.commands.github can't break cli.commands.github.GitHubApi.
- Position
- Below the diagonal: cli.commands.github uses a module listed above it, which is the healthy direction.
32→6 cli.commands.github uses cli.commands.shared✕
- Connections
- 5 pairs of types, where a type in cli.commands.github uses a type in cli.commands.shared.
- The types involved
scala.cli.commands.github.HasSharedSecretOptions→scala.cli.commands.shared.GlobalOptionsscala.cli.commands.github.HasSharedSecretOptions→scala.cli.commands.shared.HasGlobalOptionsscala.cli.commands.github.SecretCreateOptions→scala.cli.commands.shared.CoursierOptionsscala.cli.commands.github.SharedSecretOptions→scala.cli.commands.shared.GlobalOptionsscala.cli.commands.github.SharedSecretOptions→scala.cli.commands.shared.HasGlobalOptions
- Direction
- cli.commands.github uses cli.commands.shared, so a change to cli.commands.shared can break cli.commands.github, while a change to cli.commands.github can't break cli.commands.shared.
- Position
- Below the diagonal: cli.commands.github uses a module listed above it, which is the healthy direction.
32→13 cli.commands.github uses cli.commands✕
- Connections
- 4 pairs of types, where a type in cli.commands.github uses a type in cli.commands.
- The types involved
scala.cli.commands.github.SecretCreate→scala.cli.commands.ScalaCommandscala.cli.commands.github.SecretCreate→scala.cli.commands.SpecificationLevelscala.cli.commands.github.SecretList→scala.cli.commands.ScalaCommandscala.cli.commands.github.SecretList→scala.cli.commands.SpecificationLevel
- Direction
- cli.commands.github uses cli.commands, so a change to cli.commands can break cli.commands.github, while a change to cli.commands.github can't break cli.commands.
- Position
- Below the diagonal: cli.commands.github uses a module listed above it, which is the healthy direction.
32→15 cli.commands.github uses cli.config✕
- Connections
- 1 pair of types, where a type in cli.commands.github uses a type in cli.config.
- The types involved
scala.cli.commands.github.SharedSecretOptions→scala.cli.config.PasswordOption
- Direction
- cli.commands.github uses cli.config, so a change to cli.config can break cli.commands.github, while a change to cli.commands.github can't break cli.config.
- Position
- Below the diagonal: cli.commands.github uses a module listed above it, which is the healthy direction.
32→23 cli.commands.github uses build.errors✕
- Connections
- 1 pair of types, where a type in cli.commands.github uses a type in build.errors.
- The types involved
scala.cli.commands.github.LibSodiumJni→scala.build.errors.BuildException
- Direction
- cli.commands.github uses build.errors, so a change to build.errors can break cli.commands.github, while a change to cli.commands.github can't break build.errors.
- Position
- Below the diagonal: cli.commands.github uses a module listed above it, which is the healthy direction.
32→25 cli.commands.github uses build✕
- Connections
- 3 pairs of types, where a type in cli.commands.github uses a type in build.
- The types involved
scala.cli.commands.github.LibSodiumJni→scala.build.Loggerscala.cli.commands.github.SecretCreate→scala.build.Loggerscala.cli.commands.github.SecretList→scala.build.Logger
- Direction
- cli.commands.github uses build, so a change to build can break cli.commands.github, while a change to cli.commands.github can't break build.
- Position
- Below the diagonal: cli.commands.github uses a module listed above it, which is the healthy direction.
33→2 cli.commands.publish.checks uses build.options.publish✕
- Connections
- 1 pair of types, where a type in cli.commands.publish.checks uses a type in build.options.publish.
- The types involved
scala.cli.commands.publish.checks.PgpSecretKeyCheck→scala.build.options.publish.ConfigPasswordOption
- Direction
- cli.commands.publish.checks uses build.options.publish, so a change to build.options.publish can break cli.commands.publish.checks, while a change to cli.commands.publish.checks can't break build.options.publish.
- Position
- Below the diagonal: cli.commands.publish.checks uses a module listed above it, which is the healthy direction.
33→15 cli.commands.publish.checks uses cli.config✕
- Connections
- 1 pair of types, where a type in cli.commands.publish.checks uses a type in cli.config.
- The types involved
scala.cli.commands.publish.checks.PgpSecretKeyCheck→scala.cli.config.PasswordOption
- Direction
- cli.commands.publish.checks uses cli.config, so a change to cli.config can break cli.commands.publish.checks, while a change to cli.commands.publish.checks can't break cli.config.
- Position
- Below the diagonal: cli.commands.publish.checks uses a module listed above it, which is the healthy direction.
33→19 cli.commands.publish.checks uses cli.commands.publish✕
- Connections
- 23 pairs of types, where a type in cli.commands.publish.checks uses a type in cli.commands.publish.
- The types involved
scala.cli.commands.publish.checks.CheckUtils→scala.cli.commands.publish.PublishSetupOptionsscala.cli.commands.publish.checks.ComputeVersionCheck→scala.cli.commands.publish.OptionCheckscala.cli.commands.publish.checks.ComputeVersionCheck→scala.cli.commands.publish.PublishSetupOptionsscala.cli.commands.publish.checks.DeveloperCheck→scala.cli.commands.publish.OptionCheckscala.cli.commands.publish.checks.DeveloperCheck→scala.cli.commands.publish.PublishSetupOptionsscala.cli.commands.publish.checks.LicenseCheck→scala.cli.commands.publish.OptionCheckscala.cli.commands.publish.checks.LicenseCheck→scala.cli.commands.publish.PublishSetupOptionsscala.cli.commands.publish.checks.NameCheck→scala.cli.commands.publish.OptionCheckscala.cli.commands.publish.checks.NameCheck→scala.cli.commands.publish.PublishSetupOptionsscala.cli.commands.publish.checks.OrganizationCheck→scala.cli.commands.publish.OptionCheckscala.cli.commands.publish.checks.OrganizationCheck→scala.cli.commands.publish.PublishSetupOptionsscala.cli.commands.publish.checks.PasswordCheck→scala.cli.commands.publish.OptionCheckscala.cli.commands.publish.checks.PasswordCheck→scala.cli.commands.publish.PublishSetupOptionsscala.cli.commands.publish.checks.PgpSecretKeyCheck→scala.cli.commands.publish.OptionCheckscala.cli.commands.publish.checks.PgpSecretKeyCheck→scala.cli.commands.publish.PublishSetupOptionsscala.cli.commands.publish.checks.RepositoryCheck→scala.cli.commands.publish.OptionCheckscala.cli.commands.publish.checks.RepositoryCheck→scala.cli.commands.publish.PublishSetupOptionsscala.cli.commands.publish.checks.ScmCheck→scala.cli.commands.publish.OptionCheckscala.cli.commands.publish.checks.ScmCheck→scala.cli.commands.publish.PublishSetupOptionsscala.cli.commands.publish.checks.UrlCheck→scala.cli.commands.publish.OptionCheckscala.cli.commands.publish.checks.UrlCheck→scala.cli.commands.publish.PublishSetupOptionsscala.cli.commands.publish.checks.UserCheck→scala.cli.commands.publish.OptionCheckscala.cli.commands.publish.checks.UserCheck→scala.cli.commands.publish.PublishSetupOptions
- Direction
- cli.commands.publish.checks uses cli.commands.publish, so a change to cli.commands.publish can break cli.commands.publish.checks, while a change to cli.commands.publish.checks can't break cli.commands.publish.
- Position
- Below the diagonal: cli.commands.publish.checks uses a module listed above it, which is the healthy direction.
33→23 cli.commands.publish.checks uses build.errors✕
- Connections
- 11 pairs of types, where a type in cli.commands.publish.checks uses a type in build.errors.
- The types involved
scala.cli.commands.publish.checks.ComputeVersionCheck→scala.build.errors.BuildExceptionscala.cli.commands.publish.checks.DeveloperCheck→scala.build.errors.BuildExceptionscala.cli.commands.publish.checks.LicenseCheck→scala.build.errors.BuildExceptionscala.cli.commands.publish.checks.NameCheck→scala.build.errors.BuildExceptionscala.cli.commands.publish.checks.OrganizationCheck→scala.build.errors.BuildExceptionscala.cli.commands.publish.checks.PasswordCheck→scala.build.errors.BuildExceptionscala.cli.commands.publish.checks.PgpSecretKeyCheck→scala.build.errors.BuildExceptionscala.cli.commands.publish.checks.RepositoryCheck→scala.build.errors.BuildExceptionscala.cli.commands.publish.checks.ScmCheck→scala.build.errors.BuildExceptionscala.cli.commands.publish.checks.UrlCheck→scala.build.errors.BuildExceptionscala.cli.commands.publish.checks.UserCheck→scala.build.errors.BuildException
- Direction
- cli.commands.publish.checks uses build.errors, so a change to build.errors can break cli.commands.publish.checks, while a change to cli.commands.publish.checks can't break build.errors.
- Position
- Below the diagonal: cli.commands.publish.checks uses a module listed above it, which is the healthy direction.
33→25 cli.commands.publish.checks uses build✕
- Connections
- 12 pairs of types, where a type in cli.commands.publish.checks uses a type in build.
- The types involved
scala.cli.commands.publish.checks.CheckUtils→scala.build.Loggerscala.cli.commands.publish.checks.ComputeVersionCheck→scala.build.Loggerscala.cli.commands.publish.checks.DeveloperCheck→scala.build.Loggerscala.cli.commands.publish.checks.LicenseCheck→scala.build.Loggerscala.cli.commands.publish.checks.NameCheck→scala.build.Loggerscala.cli.commands.publish.checks.OrganizationCheck→scala.build.Loggerscala.cli.commands.publish.checks.PasswordCheck→scala.build.Loggerscala.cli.commands.publish.checks.PgpSecretKeyCheck→scala.build.Loggerscala.cli.commands.publish.checks.RepositoryCheck→scala.build.Loggerscala.cli.commands.publish.checks.ScmCheck→scala.build.Loggerscala.cli.commands.publish.checks.UrlCheck→scala.build.Loggerscala.cli.commands.publish.checks.UserCheck→scala.build.Logger
- Direction
- cli.commands.publish.checks uses build, so a change to build can break cli.commands.publish.checks, while a change to cli.commands.publish.checks can't break build.
- Position
- Below the diagonal: cli.commands.publish.checks uses a module listed above it, which is the healthy direction.
34→6 cli.commands.setupide uses cli.commands.shared✕
- Connections
- 5 pairs of types, where a type in cli.commands.setupide uses a type in cli.commands.shared.
- The types involved
scala.cli.commands.setupide.SetupIde→scala.cli.commands.shared.SharedBspFileOptionsscala.cli.commands.setupide.SetupIde→scala.cli.commands.shared.SharedOptionsscala.cli.commands.setupide.SetupIdeOptions→scala.cli.commands.shared.HasSharedOptionsscala.cli.commands.setupide.SetupIdeOptions→scala.cli.commands.shared.SharedBspFileOptionsscala.cli.commands.setupide.SetupIdeOptions→scala.cli.commands.shared.SharedOptions
- Direction
- cli.commands.setupide uses cli.commands.shared, so a change to cli.commands.shared can break cli.commands.setupide, while a change to cli.commands.setupide can't break cli.commands.shared.
- Position
- Below the diagonal: cli.commands.setupide uses a module listed above it, which is the healthy direction.
34→9 cli.commands.setupide uses build.input✕
- Connections
- 1 pair of types, where a type in cli.commands.setupide uses a type in build.input.
- The types involved
scala.cli.commands.setupide.SetupIde→scala.build.input.Inputs
- Direction
- cli.commands.setupide uses build.input, so a change to build.input can break cli.commands.setupide, while a change to cli.commands.setupide can't break build.input.
- Position
- Below the diagonal: cli.commands.setupide uses a module listed above it, which is the healthy direction.
34→13 cli.commands.setupide uses cli.commands✕
- Connections
- 1 pair of types, where a type in cli.commands.setupide uses a type in cli.commands.
- The types involved
scala.cli.commands.setupide.SetupIde→scala.cli.commands.ScalaCommand
- Direction
- cli.commands.setupide uses cli.commands, so a change to cli.commands can break cli.commands.setupide, while a change to cli.commands.setupide can't break cli.commands.
- Position
- Below the diagonal: cli.commands.setupide uses a module listed above it, which is the healthy direction.
34→20 cli.commands.setupide uses build.options✕
- Connections
- 1 pair of types, where a type in cli.commands.setupide uses a type in build.options.
- The types involved
scala.cli.commands.setupide.SetupIde→scala.build.options.BuildOptions
- Direction
- cli.commands.setupide uses build.options, so a change to build.options can break cli.commands.setupide, while a change to cli.commands.setupide can't break build.options.
- Position
- Below the diagonal: cli.commands.setupide uses a module listed above it, which is the healthy direction.
34→23 cli.commands.setupide uses build.errors✕
- Connections
- 1 pair of types, where a type in cli.commands.setupide uses a type in build.errors.
- The types involved
scala.cli.commands.setupide.SetupIde→scala.build.errors.BuildException
- Direction
- cli.commands.setupide uses build.errors, so a change to build.errors can break cli.commands.setupide, while a change to cli.commands.setupide can't break build.errors.
- Position
- Below the diagonal: cli.commands.setupide uses a module listed above it, which is the healthy direction.
34→25 cli.commands.setupide uses build✕
- Connections
- 2 pairs of types, where a type in cli.commands.setupide uses a type in build.
- The types involved
scala.cli.commands.setupide.SetupIde→scala.build.Artifactsscala.cli.commands.setupide.SetupIde→scala.build.Logger
- Direction
- cli.commands.setupide uses build, so a change to build can break cli.commands.setupide, while a change to cli.commands.setupide can't break build.
- Position
- Below the diagonal: cli.commands.setupide uses a module listed above it, which is the healthy direction.
35→3 cli.commands.update uses cli.commands.github.GitHubApi✕
- Connections
- 1 pair of types, where a type in cli.commands.update uses a type in cli.commands.github.GitHubApi.
- The types involved
scala.cli.commands.update.Update→scala.cli.commands.github.GitHubApi.Secret
- Direction
- cli.commands.update uses cli.commands.github.GitHubApi, so a change to cli.commands.github.GitHubApi can break cli.commands.update, while a change to cli.commands.update can't break cli.commands.github.GitHubApi.
- Position
- Below the diagonal: cli.commands.update uses a module listed above it, which is the healthy direction.
35→6 cli.commands.update uses cli.commands.shared✕
- Connections
- 2 pairs of types, where a type in cli.commands.update uses a type in cli.commands.shared.
- The types involved
scala.cli.commands.update.UpdateOptions→scala.cli.commands.shared.GlobalOptionsscala.cli.commands.update.UpdateOptions→scala.cli.commands.shared.HasGlobalOptions
- Direction
- cli.commands.update uses cli.commands.shared, so a change to cli.commands.shared can break cli.commands.update, while a change to cli.commands.update can't break cli.commands.shared.
- Position
- Below the diagonal: cli.commands.update uses a module listed above it, which is the healthy direction.
35→13 cli.commands.update uses cli.commands✕
- Connections
- 2 pairs of types, where a type in cli.commands.update uses a type in cli.commands.
- The types involved
scala.cli.commands.update.Update→scala.cli.commands.ScalaCommandscala.cli.commands.update.Update→scala.cli.commands.SpecificationLevel
- Direction
- cli.commands.update uses cli.commands, so a change to cli.commands can break cli.commands.update, while a change to cli.commands.update can't break cli.commands.
- Position
- Below the diagonal: cli.commands.update uses a module listed above it, which is the healthy direction.
35→15 cli.commands.update uses cli.config✕
- Connections
- 1 pair of types, where a type in cli.commands.update uses a type in cli.config.
- The types involved
scala.cli.commands.update.UpdateOptions→scala.cli.config.PasswordOption
- Direction
- cli.commands.update uses cli.config, so a change to cli.config can break cli.commands.update, while a change to cli.commands.update can't break cli.config.
- Position
- Below the diagonal: cli.commands.update uses a module listed above it, which is the healthy direction.
35→23 cli.commands.update uses build.errors✕
- Connections
- 1 pair of types, where a type in cli.commands.update uses a type in build.errors.
- The types involved
scala.cli.commands.update.Update→scala.build.errors.CheckScalaCliVersionError
- Direction
- cli.commands.update uses build.errors, so a change to build.errors can break cli.commands.update, while a change to cli.commands.update can't break build.errors.
- Position
- Below the diagonal: cli.commands.update uses a module listed above it, which is the healthy direction.
35→25 cli.commands.update uses build✕
- Connections
- 1 pair of types, where a type in cli.commands.update uses a type in build.
- The types involved
scala.cli.commands.update.Update→scala.build.Logger
- Direction
- cli.commands.update uses build, so a change to build can break cli.commands.update, while a change to cli.commands.update can't break build.
- Position
- Below the diagonal: cli.commands.update uses a module listed above it, which is the healthy direction.
36→6 cli.exportCmd uses cli.commands.shared✕
- Connections
- 4 pairs of types, where a type in cli.exportCmd uses a type in cli.commands.shared.
- The types involved
scala.cli.exportCmd.MillProjectDescriptor→scala.cli.commands.shared.ScalaJsOptionsscala.cli.exportCmd.MillProjectDescriptor→scala.cli.commands.shared.ScalaNativeOptionsscala.cli.exportCmd.SbtProjectDescriptor→scala.cli.commands.shared.ScalaJsOptionsscala.cli.exportCmd.SbtProjectDescriptor→scala.cli.commands.shared.ScalaNativeOptions
- Direction
- cli.exportCmd uses cli.commands.shared, so a change to cli.commands.shared can break cli.exportCmd, while a change to cli.exportCmd can't break cli.commands.shared.
- Position
- Below the diagonal: cli.exportCmd uses a module listed above it, which is the healthy direction.
36→20 cli.exportCmd uses build.options✕
- Connections
- 7 pairs of types, where a type in cli.exportCmd uses a type in build.options.
- The types involved
scala.cli.exportCmd.JsonProjectDescriptor→scala.build.options.BuildOptionsscala.cli.exportCmd.MavenProjectDescriptor→scala.build.options.BuildOptionsscala.cli.exportCmd.MavenProjectDescriptor→scala.build.options.Scopescala.cli.exportCmd.MillProjectDescriptor→scala.build.options.BuildOptionsscala.cli.exportCmd.ProjectDescriptor→scala.build.options.BuildOptionsscala.cli.exportCmd.SbtProjectDescriptor→scala.build.options.BuildOptionsscala.cli.exportCmd.SbtProjectDescriptor→scala.build.options.Scope
- Direction
- cli.exportCmd uses build.options, so a change to build.options can break cli.exportCmd, while a change to cli.exportCmd can't break build.options.
- Position
- Below the diagonal: cli.exportCmd uses a module listed above it, which is the healthy direction.
36→22 cli.exportCmd uses build.preprocessing.directives✕
- Connections
- 1 pair of types, where a type in cli.exportCmd uses a type in build.preprocessing.directives.
- The types involved
scala.cli.exportCmd.JsonProject→scala.build.preprocessing.directives.BuildInfo
- Direction
- cli.exportCmd uses build.preprocessing.directives, so a change to build.preprocessing.directives can break cli.exportCmd, while a change to cli.exportCmd can't break build.preprocessing.directives.
- Position
- Below the diagonal: cli.exportCmd uses a module listed above it, which is the healthy direction.
36→23 cli.exportCmd uses build.errors✕
- Connections
- 5 pairs of types, where a type in cli.exportCmd uses a type in build.errors.
- The types involved
scala.cli.exportCmd.JsonProjectDescriptor→scala.build.errors.BuildExceptionscala.cli.exportCmd.MavenProjectDescriptor→scala.build.errors.BuildExceptionscala.cli.exportCmd.MillProjectDescriptor→scala.build.errors.BuildExceptionscala.cli.exportCmd.ProjectDescriptor→scala.build.errors.BuildExceptionscala.cli.exportCmd.SbtProjectDescriptor→scala.build.errors.BuildException
- Direction
- cli.exportCmd uses build.errors, so a change to build.errors can break cli.exportCmd, while a change to cli.exportCmd can't break build.errors.
- Position
- Below the diagonal: cli.exportCmd uses a module listed above it, which is the healthy direction.
36→25 cli.exportCmd uses build✕
- Connections
- 14 pairs of types, where a type in cli.exportCmd uses a type in build.
- The types involved
scala.cli.exportCmd.JsonProject→scala.build.Projectscala.cli.exportCmd.JsonProjectDescriptor→scala.build.Loggerscala.cli.exportCmd.JsonProjectDescriptor→scala.build.Sourcesscala.cli.exportCmd.MavenProject→scala.build.Projectscala.cli.exportCmd.MavenProjectDescriptor→scala.build.Loggerscala.cli.exportCmd.MavenProjectDescriptor→scala.build.Sourcesscala.cli.exportCmd.MillProject→scala.build.Projectscala.cli.exportCmd.MillProjectDescriptor→scala.build.Loggerscala.cli.exportCmd.MillProjectDescriptor→scala.build.Sourcesscala.cli.exportCmd.ProjectDescriptor→scala.build.Projectscala.cli.exportCmd.ProjectDescriptor→scala.build.Sourcesscala.cli.exportCmd.SbtProject→scala.build.Projectscala.cli.exportCmd.SbtProjectDescriptor→scala.build.Loggerscala.cli.exportCmd.SbtProjectDescriptor→scala.build.Sources
- Direction
- cli.exportCmd uses build, so a change to build can break cli.exportCmd, while a change to cli.exportCmd can't break build.
- Position
- Below the diagonal: cli.exportCmd uses a module listed above it, which is the healthy direction.
37→17 cli.internal.ScalaJsLinker uses build.internal✕
- Connections
- 1 pair of types, where a type in cli.internal.ScalaJsLinker uses a type in build.internal.
- The types involved
scala.cli.internal.ScalaJsLinker.LinkJSInput→scala.build.internal.ScalaJsLinkerConfig
- Direction
- cli.internal.ScalaJsLinker uses build.internal, so a change to build.internal can break cli.internal.ScalaJsLinker, while a change to cli.internal.ScalaJsLinker can't break build.internal.
- Position
- Below the diagonal: cli.internal.ScalaJsLinker uses a module listed above it, which is the healthy direction.
37→25 cli.internal.ScalaJsLinker uses build✕
- Connections
- 1 pair of types, where a type in cli.internal.ScalaJsLinker uses a type in build.
- The types involved
scala.cli.internal.ScalaJsLinker.longRunningProcess→scala.build.Logger
- Direction
- cli.internal.ScalaJsLinker uses build, so a change to build can break cli.internal.ScalaJsLinker, while a change to cli.internal.ScalaJsLinker can't break build.
- Position
- Below the diagonal: cli.internal.ScalaJsLinker uses a module listed above it, which is the healthy direction.
38→4 build.bsp uses build.compiler✕
- Connections
- 1 pair of types, where a type in build.bsp uses a type in build.compiler.
- The types involved
scala.build.bsp.BloopSession→scala.build.compiler.BloopCompiler
- Direction
- build.bsp uses build.compiler, so a change to build.compiler can break build.bsp, while a change to build.bsp can't break build.compiler.
- Position
- Below the diagonal: build.bsp uses a module listed above it, which is the healthy direction.
38→9 build.bsp uses build.input✕
- Connections
- 7 pairs of types, where a type in build.bsp uses a type in build.input.
- The types involved
scala.build.bsp.BloopSession→scala.build.input.Inputsscala.build.bsp.Bsp→scala.build.input.Inputsscala.build.bsp.BspImpl→scala.build.input.Inputsscala.build.bsp.BspServer→scala.build.input.Inputsscala.build.bsp.BuildServerProxy→scala.build.input.Inputsscala.build.bsp.HasGeneratedSources→scala.build.input.Inputsscala.build.bsp.HasGeneratedSourcesImpl→scala.build.input.Inputs
- Direction
- build.bsp uses build.input, so a change to build.input can break build.bsp, while a change to build.bsp can't break build.input.
- Position
- Below the diagonal: build.bsp uses a module listed above it, which is the healthy direction.
38→20 build.bsp uses build.options✕
- Connections
- 5 pairs of types, where a type in build.bsp uses a type in build.options.
- The types involved
scala.build.bsp.BspImpl→scala.build.options.Scopescala.build.bsp.BspReloadableOptions→scala.build.options.BuildOptionsscala.build.bsp.BuildServerProxy→scala.build.options.Scopescala.build.bsp.HasGeneratedSources→scala.build.options.Scopescala.build.bsp.HasGeneratedSourcesImpl→scala.build.options.Scope
- Direction
- build.bsp uses build.options, so a change to build.options can break build.bsp, while a change to build.bsp can't break build.options.
- Position
- Below the diagonal: build.bsp uses a module listed above it, which is the healthy direction.
38→23 build.bsp uses build.errors✕
- Connections
- 3 pairs of types, where a type in build.bsp uses a type in build.errors.
- The types involved
scala.build.bsp.BspClient→scala.build.errors.BuildExceptionscala.build.bsp.BspClient→scala.build.errors.Diagnosticscala.build.bsp.DiagnosticExt→scala.build.errors.Diagnostic
- Direction
- build.bsp uses build.errors, so a change to build.errors can break build.bsp, while a change to build.bsp can't break build.errors.
- Position
- Below the diagonal: build.bsp uses a module listed above it, which is the healthy direction.
38→24 build.bsp uses build.Build✕
- Connections
- 1 pair of types, where a type in build.bsp uses a type in build.Build.
- The types involved
scala.build.bsp.BloopSession→scala.build.Build.Watcher
- Direction
- build.bsp uses build.Build, so a change to build.Build can break build.bsp, while a change to build.bsp can't break build.Build.
- Position
- Below the diagonal: build.bsp uses a module listed above it, which is the healthy direction.
38→25 build.bsp uses build✕
- Connections
- 9 pairs of types, where a type in build.bsp uses a type in build.
- The types involved
scala.build.bsp.BspClient→scala.build.BloopBuildClientscala.build.bsp.BspClient→scala.build.GeneratedSourcescala.build.bsp.BspClient→scala.build.Loggerscala.build.bsp.BspReloadableOptions→scala.build.Loggerscala.build.bsp.BspThreads→scala.build.BuildThreadsscala.build.bsp.BuildServerProxy→scala.build.GeneratedSourcescala.build.bsp.HasGeneratedSources→scala.build.GeneratedSourcescala.build.bsp.HasGeneratedSourcesImpl→scala.build.GeneratedSourcescala.build.bsp.PositionExt→scala.build.Position
- Direction
- build.bsp uses build, so a change to build can break build.bsp, while a change to build.bsp can't break build.
- Position
- Below the diagonal: build.bsp uses a module listed above it, which is the healthy direction.
38→27 build.bsp uses build.bsp.BspImpl✕
- Connections
- 1 pair of types, where a type in build.bsp uses a type in build.bsp.BspImpl.
- The types involved
scala.build.bsp.BspImpl→scala.build.bsp.BspImpl.PreBuildProject
- Direction
- build.bsp uses build.bsp.BspImpl, so a change to build.bsp.BspImpl can break build.bsp, while a change to build.bsp can't break build.bsp.BspImpl.
- Position
- Below the diagonal: build.bsp uses a module listed above it, which is the healthy direction.
39→6 cli.commands.export0 uses cli.commands.shared✕
- Connections
- 4 pairs of types, where a type in cli.commands.export0 uses a type in cli.commands.shared.
- The types involved
scala.cli.commands.export0.Export→scala.cli.commands.shared.SharedOptionsscala.cli.commands.export0.ExportOptions→scala.cli.commands.shared.HasSharedOptionsscala.cli.commands.export0.ExportOptions→scala.cli.commands.shared.MainClassOptionsscala.cli.commands.export0.ExportOptions→scala.cli.commands.shared.SharedOptions
- Direction
- cli.commands.export0 uses cli.commands.shared, so a change to cli.commands.shared can break cli.commands.export0, while a change to cli.commands.export0 can't break cli.commands.shared.
- Position
- Below the diagonal: cli.commands.export0 uses a module listed above it, which is the healthy direction.
39→9 cli.commands.export0 uses build.input✕
- Connections
- 1 pair of types, where a type in cli.commands.export0 uses a type in build.input.
- The types involved
scala.cli.commands.export0.Export→scala.build.input.Inputs
- Direction
- cli.commands.export0 uses build.input, so a change to build.input can break cli.commands.export0, while a change to cli.commands.export0 can't break build.input.
- Position
- Below the diagonal: cli.commands.export0 uses a module listed above it, which is the healthy direction.
39→13 cli.commands.export0 uses cli.commands✕
- Connections
- 2 pairs of types, where a type in cli.commands.export0 uses a type in cli.commands.
- The types involved
scala.cli.commands.export0.Export→scala.cli.commands.ScalaCommandscala.cli.commands.export0.Export→scala.cli.commands.SpecificationLevel
- Direction
- cli.commands.export0 uses cli.commands, so a change to cli.commands can break cli.commands.export0, while a change to cli.commands.export0 can't break cli.commands.
- Position
- Below the diagonal: cli.commands.export0 uses a module listed above it, which is the healthy direction.
39→20 cli.commands.export0 uses build.options✕
- Connections
- 2 pairs of types, where a type in cli.commands.export0 uses a type in build.options.
- The types involved
scala.cli.commands.export0.Export→scala.build.options.BuildOptionsscala.cli.commands.export0.Export→scala.build.options.Scope
- Direction
- cli.commands.export0 uses build.options, so a change to build.options can break cli.commands.export0, while a change to cli.commands.export0 can't break build.options.
- Position
- Below the diagonal: cli.commands.export0 uses a module listed above it, which is the healthy direction.
39→23 cli.commands.export0 uses build.errors✕
- Connections
- 1 pair of types, where a type in cli.commands.export0 uses a type in build.errors.
- The types involved
scala.cli.commands.export0.Export→scala.build.errors.BuildException
- Direction
- cli.commands.export0 uses build.errors, so a change to build.errors can break cli.commands.export0, while a change to cli.commands.export0 can't break build.errors.
- Position
- Below the diagonal: cli.commands.export0 uses a module listed above it, which is the healthy direction.
39→25 cli.commands.export0 uses build✕
- Connections
- 1 pair of types, where a type in cli.commands.export0 uses a type in build.
- The types involved
scala.cli.commands.export0.Export→scala.build.Logger
- Direction
- cli.commands.export0 uses build, so a change to build can break cli.commands.export0, while a change to cli.commands.export0 can't break build.
- Position
- Below the diagonal: cli.commands.export0 uses a module listed above it, which is the healthy direction.
39→36 cli.commands.export0 uses cli.exportCmd✕
- Connections
- 4 pairs of types, where a type in cli.commands.export0 uses a type in cli.exportCmd.
- The types involved
scala.cli.commands.export0.Export→scala.cli.exportCmd.JsonProjectDescriptorscala.cli.commands.export0.Export→scala.cli.exportCmd.MavenProjectDescriptorscala.cli.commands.export0.Export→scala.cli.exportCmd.MillProjectDescriptorscala.cli.commands.export0.Export→scala.cli.exportCmd.SbtProjectDescriptor
- Direction
- cli.commands.export0 uses cli.exportCmd, so a change to cli.exportCmd can break cli.commands.export0, while a change to cli.commands.export0 can't break cli.exportCmd.
- Position
- Below the diagonal: cli.commands.export0 uses a module listed above it, which is the healthy direction.
40→1 cli.internal uses build.bsp.protocol✕
- Connections
- 1 pair of types, where a type in cli.internal uses a type in build.bsp.protocol.
- The types involved
scala.cli.internal.CliLogger→scala.build.bsp.protocol.TextEdit
- Direction
- cli.internal uses build.bsp.protocol, so a change to build.bsp.protocol can break cli.internal, while a change to cli.internal can't break build.bsp.protocol.
- Position
- Below the diagonal: cli.internal uses a module listed above it, which is the healthy direction.
40→5 cli.internal uses build.internals✕
- Connections
- 1 pair of types, where a type in cli.internal uses a type in build.internals.
- The types involved
scala.cli.internal.CliLogger→scala.build.internals.FeatureType
- Direction
- cli.internal uses build.internals, so a change to build.internals can break cli.internal, while a change to cli.internal can't break build.internals.
- Position
- Below the diagonal: cli.internal uses a module listed above it, which is the healthy direction.
40→14 cli.internal uses cli.commands.pgp✕
- Connections
- 1 pair of types, where a type in cli.internal uses a type in cli.commands.pgp.
- The types involved
scala.cli.internal.PgpProxyMakerSubst→scala.cli.commands.pgp.PgpProxy
- Direction
- cli.internal uses cli.commands.pgp, so a change to cli.commands.pgp can break cli.internal, while a change to cli.internal can't break cli.commands.pgp.
- Position
- Below the diagonal: cli.internal uses a module listed above it, which is the healthy direction.
40→23 cli.internal uses build.errors✕
- Connections
- 4 pairs of types, where a type in cli.internal uses a type in build.errors.
- The types involved
scala.cli.internal.CliLogger→scala.build.errors.BuildExceptionscala.cli.internal.CliLogger→scala.build.errors.Diagnosticscala.cli.internal.CliLogger→scala.build.errors.Severityscala.cli.internal.ScalaJsLinker→scala.build.errors.BuildException
- Direction
- cli.internal uses build.errors, so a change to build.errors can break cli.internal, while a change to cli.internal can't break build.errors.
- Position
- Below the diagonal: cli.internal uses a module listed above it, which is the healthy direction.
40→24 cli.internal uses build.Build✕
- Connections
- 1 pair of types, where a type in cli.internal uses a type in build.Build.
- The types involved
scala.cli.internal.CachedBinary→scala.build.Build.Successful
- Direction
- cli.internal uses build.Build, so a change to build.Build can break cli.internal, while a change to cli.internal can't break build.Build.
- Position
- Below the diagonal: cli.internal uses a module listed above it, which is the healthy direction.
40→25 cli.internal uses build✕
- Connections
- 5 pairs of types, where a type in cli.internal uses a type in build.
- The types involved
scala.cli.internal.BouncycastleSignerMakerSubst→scala.build.Loggerscala.cli.internal.CliLogger→scala.build.Loggerscala.cli.internal.CliLogger→scala.build.Positionscala.cli.internal.ProcUtil→scala.build.Loggerscala.cli.internal.ScalaJsLinker→scala.build.Logger
- Direction
- cli.internal uses build, so a change to build can break cli.internal, while a change to cli.internal can't break build.
- Position
- Below the diagonal: cli.internal uses a module listed above it, which is the healthy direction.
40→37 cli.internal uses cli.internal.ScalaJsLinker✕
- Connections
- 1 pair of types, where a type in cli.internal uses a type in cli.internal.ScalaJsLinker.
- The types involved
scala.cli.internal.ScalaJsLinker→scala.cli.internal.ScalaJsLinker.LinkJSInput
- Direction
- cli.internal uses cli.internal.ScalaJsLinker, so a change to cli.internal.ScalaJsLinker can break cli.internal, while a change to cli.internal can't break cli.internal.ScalaJsLinker.
- Position
- Below the diagonal: cli.internal 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 | 311 | High / Critical |
| A02:2025 — Security Misconfiguration | 15 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 8 | Medium |
Roadmap
Begin by establishing a formal process for recording significant design decisions in a dedicated ADR folder to ensure architectural clarity. Simultaneously, reconcile documentation discrepancies with the actual codebase and remove 44 orphaned files to maintain knowledge freshness and accuracy. Finally, strengthen type safety by enabling explicit null checks in the build configuration and refactoring Java API boundaries to eliminate unhandled null assertions.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +8.5 pts | Low | ADR Quality |
| 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. | +6.7 pts | Medium | Architecture documentation |
| Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with Licenses.scala. | +3.1 pts | Low | Knowledge Freshness |
| Reconcile the README with reality: website/docs/guides/advanced/scala-wasm.md names Node.js 24, but the repository declares pinned 12; website/docs/guides/advanced/scala-wasm.md names Node.js 25, but the repository declares pinned 12; website/docs/guides/advanced/scala-wasm.md names Node.js 23, but the repository declares pinned 12. | +5.0 pts | Medium | Documentation accuracy |
| Resolve the 44 Orphaned file finding(s) in Knowledge Freshness — start with PgpSecretKeyCheck.scala, DirectiveHandler.scala, CliLogger.scala. | +4.3 pts | Medium | Knowledge Freshness |
| 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. | +3.8 pts | Medium | Nullable reference types |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +1.7 pts | Low | Bus Factor |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +1.7 pts | Low | Bus Factor |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.9 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.5 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.6 | Mixed | Cyclomatic Complexity: Config.runCommand (cyclomatic 40) |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala | 6.0 | Mixed | Explicit Debt: FixmeComment |
| modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| modules/cli/src/main/scala/scala/cli/commands/publish/PublishSetup.scala | 6.0 | Mixed | Explicit Debt: FixmeComment |
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. 63 of 63 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 — 63 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, 695 of 709 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 · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic 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) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — 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 repository's dependency manifest (package.json) was found, but this pass cannot parse it for hygiene, so no package was assessed. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED — a gap in the analyzer, not a verdict about this repository. This row is about dependency HYGIENE — outdated, deprecated or unmaintained direct dependencies; known CVEs in the same dependency graph are a separate question, reported under D30 wherever the manifest is OSV-readable.
- D14 License Compliance — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository's package manifest is not parsed for licence data yet. A gap in the analyzer's language coverage, NOT a finding that the repository's licenses are compliant (package.json), which this pass does not parse yet — so this dimension asserts nothing about this repository's licensing in either direction.
- D19 Documentation Quality — 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. 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.
- D19 Documentation Quality — 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 kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — 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 (project/settings/package.mill), 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.
- D26 Project Cohesion — 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. Project size and spread are measured over build units (a .NET project, a Maven or Gradle module, an npm, Deno or JSR package, a Go module, a Cargo crate, a Python, Composer, Bundler, RubyGems, Mix, rebar3, sbt, SwiftPM or pub package, an OTP application, an Xcode project or XcodeGen spec, or a checkout that declares no build at all) whose source a code model reads. This repository's production source is in a language no model reads, or in units whose build tool D26 does not recognise. That is a gap in this analyzer's language reach — not a finding that the repository's projects are cohesive.
- 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. `modules/cli/src/main/scala/scala/cli/commands/RestrictableCommand.scala`, `modules/cli/src/main/scala/scala/cli/commands/compile/Compile.scala`, `modules/cli/src/main/scala/scala/cli/commands/export0/Export.scala`, `modules/cli/src/main/scala/scala/cli/commands/fix/Fix.scala`, `modules/cli/src/main/scala/scala/cli/commands/fix/ScalafixRules.scala`, … (+9 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D44 Platform End-of-Life — not measured this run — 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 REDACTED) 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.
- M3 Folder & project structure — 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. Whether the tests sit apart from production code is not visible here, because the suite is not in a form this pass reads. The test-separation credit is granted rather than withheld: this is a gap in the analyzer's language coverage, not a finding about the repository's tests. You can widen what we reach: keep the test surface somewhere a reader can find it without opening a binary — an exported/checked-in test source tree beside the production code makes the suite reviewable, diffable and discoverable by tooling.
- 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.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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
36 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Package.doPackage at 86.
What to do
- Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with Package.doPackage (cyclomatic 86). — Refactoring it lifts Cyclomatic Complexity from 6.2 to about 6.5/10.
- 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
64 method(s) exceeded the cognitive complexity threshold of 15; the worst was Config.runCommand at 154.
What to do
- Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with Config.runCommand (cognitive 154). — Refactoring it lifts Cognitive Complexity from 5.1 to about 5.5/10.
- 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
16 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 7 FileTooLong finding(s) in God Classes — start with Package.scala, Publish.scala, Artifacts.scala. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 5 FunctionTooLong finding(s) in God Classes — start with REDACTED (2), FeaturesStickyNav.tsx, InstallStickyNav.tsx. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 MethodTooLong finding(s) in God Classes — start with Run.scala (2), Artifacts.scala, Publish.scala. — One of this dimension's main actionable groups (4 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
23 duplicated block group(s) detected. 3 of the 23 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 2 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with Publish.scala, PasswordCheck.scala. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with PgpPull.scala, AsmTestRunner.scala. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with BloopExit.scala, New.scala. — One of this dimension's main actionable groups (2 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
18 production modules (Mill), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a Mill module a helper method defines, a moduleDeps a function computes, and a module directory computed other than as a path over super.moduleDir are not visible there; 5 module(s) off the main sequence, with abstractness counted on 17 of the 18 (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 5 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (5 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 21 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with BspServer.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
1374 test methods: 456 unit, 918 integration, 0 BDD, 0 e2e. The Scala suite contributes 1374 test case(s) across 167 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
Top hotspots: modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala (7×86=602); modules/cli/src/main/scala/scala/cli/commands/run/Run.scala (5×49=245); modules/options/src/main/scala/scala/build/options/BuildOptions.scala (4×36=144)
What to do
- Resolve the 8 Hotspot finding(s) in Churn × Complexity Hotspots — start with Package.scala, Run.scala, BuildOptions.scala. — One of this dimension's main actionable groups (8 warning-level).
D16 · Bus Factor
33 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is modules/options/src/main/scala/scala/build/options/ScalaVersionUtil.scala. Counted over 145 of the 512 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 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 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
142 deducted task-comment markers across 52308 LoC (0.3/KLoC) → score 9.5. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 81 TodoComment finding(s) in Explicit Debt — start with SbtProjectDescriptor.scala (9), RunWithWatchTestDefinitions.scala (6), JmhTests.scala (4). — One of this dimension's main actionable groups (81 warning-level).
- Resolve the 61 FixmeComment finding(s) in Explicit Debt — start with NativePackagerTests.scala (3), CustomWindowsEnvVarUpdater.scala (3), Artifacts.scala (2). — One of this dimension's main actionable groups (61 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 95 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — 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)
311 finding(s): 0 critical, 309 high, 0 medium, 2 low. 289 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 15 file(s) — `.github/scripts/verify_old_cpus.sh` (line 7), `gifs/demo-magic.sh` (line 106), `modules/cli/src/main/scala/scala/cli/commands/compile/Compile.scala`, `modules/cli/src/main/scala/scala/cli/commands/export0/Export.scala`, `modules/cli/src/main/scala/scala/cli/commands/fix/Fix.scala`, … (+10 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8). — One of this dimension's main actionable groups (8 issue-level).
- Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
- No action in Static Analysis (SAST) — all 289 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 (289 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D31 · IaC & Container Security
15 finding(s): 0 critical, 7 high, 7 medium, 1 low.
What to do
- Resolve the 7 High IaC finding(s) in IaC & Container Security — start with REDACTED (7). — One of this dimension's main actionable groups (7 issue-level).
- Resolve the 7 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (7). — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
45 of 145 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is modules/core/src/main/scala/scala/build/internals/Licenses.scala. Counted over 145 of the 512 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 44 Orphaned file finding(s) in Knowledge Freshness — start with PgpSecretKeyCheck.scala, DirectiveHandler.scala, CliLogger.scala. — One of this dimension's main actionable groups (44 recommendation-level).
- Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with Licenses.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: ScalaJsOptions.scala↔ScalaJsLinkerConfig.scala 67%; RestrictedCommandsParser.scala↔ScalaCommand.scala 62%; DependencyUpdate.scala↔Export.scala 60%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with ScalaJsOptions.scala. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 4 Change coupling finding(s) in Change Coupling — start with DependencyUpdate.scala (2), RestrictedCommandsParser.scala, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
D36 · Supply-chain Provenance & Signing
2/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
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
- `Logger` declares 20 abstract members: `error`, `message`, `log`, `log`, `debug`, `log`, `log`, `debug`, `exit`, `coursierLogger`, `bloopRifleLogger`, `scalaJsLogger`, `scalaNativeTestLogger`, `scalaNativeCliInternalLoggerOptions`, `compilerOutputStream`, `verbosity`, `experimentalWarning`, `flushExperimentalWarnings`, `deprecationWarning`, `flushDeprecationWarnings`. 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. Those 20 declarations carry 16 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 16 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. — modules/core/src/main/scala/scala/build/Logger.scala:13
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX8 · Test isolation
GD1 · Unfinished & placeholder code
- A placeholder string ("//> using publish.description \"Lorem ip…") is still in shipped code — typical of generated boilerplate that was never filled in. — modules/directives/src/main/scala/scala/build/preprocessing/directives/Publish.scala:22
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
- `noArgs` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — modules/options/src/main/scala/scala/build/CoursierUtils.scala:9
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×2) — modules/integration/src/test/scala/scala/cli/integration/RunTestDefinitions.scala:465, modules/integration/src/test/scala/scala/cli/integration/RunTestsDefault.scala:356
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
- Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
M1 · Documentation (README)
What to do
- 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.
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
- website/docs/guides/advanced/scala-wasm.md names Node.js 24, but the repository declares pinned 12. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — website/docs/guides/advanced/scala-wasm.md:61
- website/docs/guides/advanced/scala-wasm.md names Node.js 25, but the repository declares pinned 12. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — website/docs/guides/advanced/scala-wasm.md:74
- website/docs/guides/advanced/scala-wasm.md names Node.js 23, but the repository declares pinned 12. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — website/docs/guides/advanced/scala-wasm.md:76
What to do
- Reconcile the README with reality: website/docs/guides/advanced/scala-wasm.md names Node.js 24, but the repository declares pinned 12; website/docs/guides/advanced/scala-wasm.md names Node.js 25, but the repository declares pinned 12; website/docs/guides/advanced/scala-wasm.md names Node.js 23, but the repository declares pinned 12.
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
P3 · Security & performance tooling
What to do
- Dependabot is configured but does not watch `gitsubmodule` — 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
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 34 use(s) across 52,438 production line(s) (~0.6/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.
PF3 · Async & latency hygiene
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. (×9) — modules/build/src/main/scala/scala/build/input/ElementsUtils.scala:82, modules/build/src/main/scala/scala/build/input/Inputs.scala:117, modules/build/src/main/scala/scala/build/postprocessing/SemanticdbProcessor.scala:117, …
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. This repository constructs a collision-broken hash (MD5/SHA1) at 9 sites, not one: `modules/build/src/main/scala/scala/build/input/ElementsUtils.scala:82` (MessageDigest.getInstance("SHA-1")), `modules/build/src/main/scala/scala/build/input/Inputs.scala:117` (MessageDigest.getInstance("SHA-1")), `modules/build/src/main/scala/scala/build/postprocessing/SemanticdbProcessor.scala:117` (MessageDigest.getInstance("MD5")), `modules/build/src/main/scala/scala/build/postprocessing/SlothPatcher.scala:321` (MessageDigest.getInstance("SHA-1")), `modules/build/src/main/scala/scala/build/postprocessing/SlothPatcher.scala:608` (MessageDigest.getInstance("SHA-1")), `modules/cli/src/main/scala/scala/cli/internal/CachedBinary.scala:19` (MessageDigest.getInstance("SHA-1")), `modules/cli/src/main/scala/scala/cli/internal/CachedBinary.scala:29` (MessageDigest.getInstance("SHA-1")), `modules/cli/src/main/scala/scala/cli/internal/CachedBinary.scala:64` (MessageDigest.getInstance("SHA-1")), and 1 further site(s). Each is a separate decision — fixing only the line this row cites leaves the others in place.
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. (×2) — modules/core/src/main/scala/scala/build/internals/NativeWrapper.scala:124, modules/cli/src/main/scala/scala/cli/commands/shared/SharedCompilationServerOptions.scala:160
- `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. — modules/core/src/main/scala/scala/build/internals/NativeWrapper.scala:156
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 605 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 | 61% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 96% | Exemplary | Strongest area. |
| Maturity | 53% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 75% | Strong | Solid. |
| Security | 75% | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 79% | Strong | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- 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 — ~43020 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 — no .scala test runner
- D12 Dependency Hygiene — Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
- D14 License Compliance — Package manifest not parsed for licence data — analyzer language-coverage gap
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Java, Scala, TypeScript 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, .ts, .tsx, 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
- D26 Project Cohesion — D26 measured no build unit over this repository's .java, .scala source. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — 14 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): 276 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 318 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge modules/core/src/main/scala/scala/build/internals/Licenses.scala:1
- Boundary-crossing change coupling: ScalaJsOptions.scala ↔ ScalaJsLinkerConfig.scala modules/cli/src/main/scala/scala/cli/commands/shared/ScalaJsOptions.scala:1
Serious — 326 finding(s)
- TodoComment modules/test-runner/src/main/scala/scala/build/testrunner/AsmTestRunner.scala:382
- TodoComment modules/options/src/main/scala/scala/build/CoursierUtils.scala:9
- TodoComment modules/cli/src/main/scala/scala/cli/commands/ScalaCommand.scala:158
- TodoComment modules/options/src/main/scala/scala/build/internals/Util.scala:157
- TodoComment modules/integration/src/test/scala/scala/cli/integration/BloopTests.scala:141
- TodoComment modules/integration/src/test/scala/scala/cli/integration/RunWithWatchTestDefinitions.scala:10
- TodoComment modules/integration/src/test/scala/scala/cli/integration/RunWithWatchTestDefinitions.scala:337
- TodoComment modules/integration/src/test/scala/scala/cli/integration/RunWithWatchTestDefinitions.scala:443
- TodoComment modules/integration/src/test/scala/scala/cli/integration/RunWithWatchTestDefinitions.scala:481
- TodoComment modules/integration/src/test/scala/scala/cli/integration/BspTestDefinitions.scala:1432
- TodoComment modules/integration/src/test/scala/scala/cli/integration/BspTestDefinitions.scala:2173
- TodoComment modules/integration/src/test/scala/scala/cli/integration/BspTestDefinitions.scala:2199
- TodoComment modules/integration/src/test/scala/scala/cli/integration/CompileTestDefinitions.scala:819
- TodoComment modules/integration/src/test/scala/scala/cli/integration/CompilerPluginTestDefinitions.scala:71
- TodoComment modules/integration/src/test/scala/scala/cli/integration/ExportSbtTestDefinitions.scala:55
- TodoComment modules/integration/src/test/scala/scala/cli/integration/ExportSbtTestDefinitions.scala:56
- TodoComment modules/integration/src/test/scala/scala/cli/integration/ExportScalaOrientedBuildToolsTestDefinitions.scala:30
- TodoComment modules/integration/src/test/scala/scala/cli/integration/GitHubTests.scala:70
- TodoComment modules/integration/src/test/scala/scala/cli/integration/GitHubTests.scala:71
- TodoComment modules/integration/src/test/scala/scala/cli/integration/GitHubTests.scala:72
- TodoComment modules/integration/src/test/scala/scala/cli/integration/JmhTests.scala:28
- TodoComment modules/integration/src/test/scala/scala/cli/integration/JmhTests.scala:53
- TodoComment modules/integration/src/test/scala/scala/cli/integration/JmhTests.scala:111
- TodoComment modules/integration/src/test/scala/scala/cli/integration/JmhTests.scala:141
- TodoComment modules/integration/src/test/scala/scala/cli/integration/NativePackagerTests.scala:410
- FixmeComment modules/test-runner/src/main/scala/scala/build/testrunner/AsmTestRunner.scala:130
- FixmeComment modules/test-runner/src/main/scala/scala/build/testrunner/FrameworkUtils.scala:262
- FixmeComment modules/options/src/main/scala/scala/build/Artifacts.scala:826
- FixmeComment modules/options/src/main/scala/scala/build/Artifacts.scala:840
- FixmeComment modules/options/src/main/scala/scala/build/TemporaryInMemoryRepository.scala:57
- FixmeComment modules/options/src/main/scala/scala/build/options/InternalOptions.scala:17
- FixmeComment modules/options/src/main/scala/scala/build/options/JavaOptions.scala:101
- FixmeComment modules/options/src/main/scala/scala/build/options/scalajs/ScalaJsLinkerOptions.scala:22
- FixmeComment modules/options/src/main/scala/scala/build/internal/FetchExternalBinary.scala:78
- FixmeComment modules/integration/src/test/scala/scala/cli/integration/NativePackagerTests.scala:121
- FixmeComment modules/integration/src/test/scala/scala/cli/integration/NativePackagerTests.scala:417
- FixmeComment modules/integration/src/test/scala/scala/cli/integration/NativePackagerTests.scala:432
- FixmeComment modules/integration/src/test/scala/scala/cli/integration/PackageTestDefinitions.scala:1005
- FixmeComment modules/integration/src/test/scala/scala/cli/integration/TestNativeImageOnScala3.scala:36
- FixmeComment modules/integration/src/test/scala/scala/cli/integration/RunScalaJsTestDefinitions.scala:252
- FixmeComment modules/integration/src/test/scala/scala/cli/integration/TestTestDefinitions.scala:1042
- FixmeComment modules/integration/src/test/scala/scala/cli/integration/RunScalacCompatTestDefinitions.scala:79
- FixmeComment modules/integration/src/test/scala/scala/cli/integration/RunScalacCompatTestDefinitions.scala:449
- FixmeComment modules/integration/src/test/scala/scala/cli/integration/RunTestDefinitions.scala:281
- FixmeComment modules/integration/src/test/scala/scala/cli/integration/SparkTestDefinitions.scala:117
- FixmeComment modules/integration/src/test/scala/scala/cli/integration/TestTestDefinitions.scala:812
- FixmeComment modules/directives/src/main/scala/scala/build/directives/DirectiveValueParser.scala:59
- FixmeComment modules/core/src/main/scala/scala/build/internals/CustomProgressBarRefreshDisplay.scala:190
- FixmeComment modules/core/src/main/scala/scala/build/internals/OsLibc.scala:56
- FixmeComment modules/config/src/main/scala/scala/cli/config/ConfigDb.scala:97
- Weak hash algorithm modules/build/src/main/scala/scala/build/input/ElementsUtils.scala:82
- Weak hash algorithm modules/build/src/main/scala/scala/build/input/Inputs.scala:117
- Weak hash algorithm modules/build/src/main/scala/scala/build/postprocessing/SemanticdbProcessor.scala:117
- Weak hash algorithm modules/build/src/main/scala/scala/build/postprocessing/SlothPatcher.scala:321
- Weak hash algorithm modules/build/src/main/scala/scala/build/postprocessing/SlothPatcher.scala:608
- Weak hash algorithm modules/cli/src/main/scala/scala/cli/internal/CachedBinary.scala:19
- Weak hash algorithm modules/cli/src/main/scala/scala/cli/internal/CachedBinary.scala:29
- Weak hash algorithm modules/cli/src/main/scala/scala/cli/internal/CachedBinary.scala:64
- Weak hash algorithm modules/options/src/main/scala/scala/build/options/BuildOptions.scala:613
- Hotspot: modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:268
- Hotspot: modules/cli/src/main/scala/scala/cli/commands/run/Run.scala modules/cli/src/main/scala/scala/cli/commands/run/Run.scala:460
- Hotspot: modules/options/src/main/scala/scala/build/options/BuildOptions.scala modules/options/src/main/scala/scala/build/options/BuildOptions.scala:352
- Hotspot: modules/options/src/main/scala/scala/build/Artifacts.scala modules/options/src/main/scala/scala/build/Artifacts.scala:197
- Hotspot: modules/cli/src/main/scala/scala/cli/commands/shared/SharedOptions.scala modules/cli/src/main/scala/scala/cli/commands/shared/SharedOptions.scala:364
- Hotspot: modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:497
- Hotspot: modules/build/src/main/scala/scala/build/CrossSources.scala modules/build/src/main/scala/scala/build/CrossSources.scala:165
- Hotspot: modules/cli/src/main/scala/scala/cli/commands/repl/Repl.scala modules/cli/src/main/scala/scala/cli/commands/repl/Repl.scala:284
- FileTooLong: package0/Package.scala modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala
- FileTooLong: publish/Publish.scala modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala
- FileTooLong: build/Artifacts.scala modules/options/src/main/scala/scala/build/Artifacts.scala
- FileTooLong: shared/SharedOptions.scala modules/cli/src/main/scala/scala/cli/commands/shared/SharedOptions.scala
- FileTooLong: run/Run.scala modules/cli/src/main/scala/scala/cli/commands/run/Run.scala
- FileTooLong: doc/GenerateReferenceDoc.scala modules/generate-reference-doc/src/main/scala/scala/cli/doc/GenerateReferenceDoc.scala
- FileTooLong: options/BuildOptions.scala modules/options/src/main/scala/scala/build/options/BuildOptions.scala
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FunctionTooLong: index.SearchPageContent REDACTED:54
- FunctionTooLong: FeaturesStickyNav.FeaturesStickyNav website/src/components/FeaturesStickyNav.tsx:35
- FunctionTooLong: InstallStickyNav.InstallStickyNav website/src/components/InstallStickyNav.tsx:36
- FunctionTooLong: ScalaCliWordmark.ScalaCliWordmark website/src/components/ScalaCliWordmark.tsx:10
- FunctionTooLong: index.Index website/src/pages/index.tsx:14
- Off the main sequence: build-macros
- Off the main sequence: tasty-lib
- Off the main sequence: specification-level
- Off the main sequence: test-runner
- Off the main sequence: scala-cli-bsp
- MethodTooLong: Artifacts.apply modules/options/src/main/scala/scala/build/Artifacts.scala:197
- MethodTooLong: Publish.prepareFilesAndUpload modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:802
- MethodTooLong: Run.runOnce modules/cli/src/main/scala/scala/cli/commands/run/Run.scala:460
- MethodTooLong: Run.runCommand modules/cli/src/main/scala/scala/cli/commands/run/Run.scala:117
- Change coupling: RestrictedCommandsParser.scala ↔ ScalaCommand.scala modules/cli/src/main/scala/scala/cli/commands/RestrictedCommandsParser.scala:1
- Change coupling: DependencyUpdate.scala ↔ Export.scala modules/cli/src/main/scala/scala/cli/commands/dependencyupdate/DependencyUpdate.scala:1
- Change coupling: DependencyUpdate.scala ↔ SetupIde.scala modules/cli/src/main/scala/scala/cli/commands/dependencyupdate/DependencyUpdate.scala:1
- Change coupling: REDACTED ↔ PgpSecretKeyCheck.scala REDACTED:1
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (13 lines × 2) modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:247
- Duplicated block (13 lines × 2) modules/cli/src/main/scala/scala/cli/commands/publish/checks/PasswordCheck.scala:22
- Duplicated block (12 lines × 2) modules/cli/src/main/scala/scala/cli/commands/pgp/PgpPull.scala:18
- Duplicated block (12 lines × 2) modules/test-runner/src/main/scala/scala/build/testrunner/AsmTestRunner.scala:112
- Duplicated block (10 lines × 2) modules/cli/src/main/scala/scala/cli/commands/bloop/BloopExit.scala:33
- Duplicated block (10 lines × 2) modules/cli/src/main/scala/scala/cli/commands/new/New.scala:40
- Duplicated block (9 lines × 2) modules/directives/src/main/scala/scala/build/preprocessing/directives/DirectiveHandler.scala:175
- Duplicated block (9 lines × 2) modules/test-runner/src/main/scala/scala/build/testrunner/AsmTestRunner.scala:132
- Duplicated block (8 lines × 2) modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:150
- Duplicated block (8 lines × 2) modules/test-runner/src/main/scala/scala/build/testrunner/AsmTestRunner.scala:98
- Duplicated block (7 lines × 2) modules/cli/src/main/scala/scala/cli/commands/publish/checks/PgpSecretKeyCheck.scala:325
- Duplicated block (7 lines × 2) modules/cli/src/main/scala/scala/cli/commands/update/Update.scala:196
- Swallowed exception (empty catch) modules/core/src/main/scala/scala/build/internals/NativeWrapper.scala:124
- Swallowed exception (empty catch) modules/cli/src/main/scala/scala/cli/commands/shared/SharedCompilationServerOptions.scala:160
- Package.doPackage (cyclomatic 86) modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:268
- Publish.prepareFilesAndUpload (cyclomatic 60) modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:802
- Run.runOnce (cyclomatic 49) modules/cli/src/main/scala/scala/cli/commands/run/Run.scala:460
- Inputs.validateArgs (cyclomatic 43) modules/build/src/main/scala/scala/build/input/Inputs.scala:233
- Config.runCommand (cyclomatic 40) REDACTED:26
- PublishSetup.runCommand (cyclomatic 38) modules/cli/src/main/scala/scala/cli/commands/publish/PublishSetup.scala:38
- BuildOptions.computeScalaParams (cyclomatic 36) modules/options/src/main/scala/scala/build/options/BuildOptions.scala:352
- Artifacts.apply (cyclomatic 35) modules/options/src/main/scala/scala/build/Artifacts.scala:197
- Run.runCommand (cyclomatic 32) modules/cli/src/main/scala/scala/cli/commands/run/Run.scala:117
- Export.runCommand (cyclomatic 31) modules/cli/src/main/scala/scala/cli/commands/export0/Export.scala:138
- MillProject.writeTo (cyclomatic 25) modules/cli/src/main/scala/scala/cli/exportCmd/MillProject.scala:39
- SemanticdbProcessor.postProcess (cyclomatic 23) modules/build/src/main/scala/scala/build/postprocessing/SemanticdbProcessor.scala:14
- DirectiveHandler.deriveParserImpl (cyclomatic 23) modules/directives/src/main/scala/scala/build/preprocessing/directives/DirectiveHandler.scala:132
- CrossSources.forInputs (cyclomatic 21) modules/build/src/main/scala/scala/build/CrossSources.scala:165
- GenerateReferenceDoc.cliOptionsContent (cyclomatic 21) modules/generate-reference-doc/src/main/scala/scala/cli/doc/GenerateReferenceDoc.scala:124
- ScalaCli.main0 (cyclomatic 20) modules/cli/src/main/scala/scala/cli/ScalaCli.scala:240
- Compile.runCommand (cyclomatic 20) modules/cli/src/main/scala/scala/cli/commands/compile/Compile.scala:44
- GitTag.get (cyclomatic 20) modules/options/src/main/scala/scala/build/options/ComputeVersion.scala:31
- FeaturesStickyNav.FeaturesStickyNav (cyclomatic 20) website/src/components/FeaturesStickyNav.tsx:35
- InstallStickyNav.InstallStickyNav (cyclomatic 20) website/src/components/InstallStickyNav.tsx:36
- Build.watch (cyclomatic 19) modules/build/src/main/scala/scala/build/Build.scala:788
- PgpSecretKeyCheck.defaultValue (cyclomatic 19) modules/cli/src/main/scala/scala/cli/commands/publish/checks/PgpSecretKeyCheck.scala:278
- Build.buildProject (cyclomatic 18) modules/build/src/main/scala/scala/build/Build.scala:1013
- Publish.maybePublish (cyclomatic 18) modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:381
- Publish.buildFileSet (cyclomatic 18) modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:497
- Build.build (cyclomatic 17) modules/build/src/main/scala/scala/build/Build.scala:364
- Inputs.forNonEmptyArgs (cyclomatic 17) modules/build/src/main/scala/scala/build/input/Inputs.scala:331
- ExtractedDirectives.from (cyclomatic 17) modules/build/src/main/scala/scala/build/preprocessing/ExtractedDirectives.scala:25
- RepositoryParser.repositoryOpt (cyclomatic 17) modules/cli/src/main/scala/scala/cli/commands/publish/RepositoryParser.scala:10
- CustomProgressBarRefreshDisplay.display (cyclomatic 17) modules/core/src/main/scala/scala/build/internals/CustomProgressBarRefreshDisplay.scala:153
- index.SearchPageContent (cyclomatic 17) REDACTED:54
- Build.scalaNativeSupported (cyclomatic 16) modules/build/src/main/scala/scala/build/Build.scala:644
- SlothPatcher.patchJar (cyclomatic 16) modules/build/src/main/scala/scala/build/postprocessing/SlothPatcher.scala:447
- SharedOptions.buildOptions (cyclomatic 16) modules/cli/src/main/scala/scala/cli/commands/shared/SharedOptions.scala:364
- WrappedSourceItem.equals (cyclomatic 16) modules/scala-cli-bsp/src/main/java/scala/build/bsp/WrappedSourceItem.java:73
- index.SearchResultItem (cyclomatic 16) REDACTED:287
- Config.runCommand (cognitive 154) REDACTED:26
- Package.doPackage (cognitive 113) modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:268
- Publish.prepareFilesAndUpload (cognitive 100) modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:802
- Run.runOnce (cognitive 94) modules/cli/src/main/scala/scala/cli/commands/run/Run.scala:460
- PublishSetup.runCommand (cognitive 85) modules/cli/src/main/scala/scala/cli/commands/publish/PublishSetup.scala:38
- Run.runCommand (cognitive 60) modules/cli/src/main/scala/scala/cli/commands/run/Run.scala:117
- GenerateReferenceDoc.cliOptionsContent (cognitive 58) modules/generate-reference-doc/src/main/scala/scala/cli/doc/GenerateReferenceDoc.scala:124
- Inputs.validateArgs (cognitive 57) modules/build/src/main/scala/scala/build/input/Inputs.scala:233
- Artifacts.apply (cognitive 48) modules/options/src/main/scala/scala/build/Artifacts.scala:197
- Export.runCommand (cognitive 45) modules/cli/src/main/scala/scala/cli/commands/export0/Export.scala:138
- MillProject.writeTo (cognitive 41) modules/cli/src/main/scala/scala/cli/exportCmd/MillProject.scala:39
- SlothPatcher.patchJar (cognitive 40) modules/build/src/main/scala/scala/build/postprocessing/SlothPatcher.scala:447
- PgpSecretKeyCheck.defaultValue (cognitive 40) modules/cli/src/main/scala/scala/cli/commands/publish/checks/PgpSecretKeyCheck.scala:278
- GitTag.get (cognitive 37) modules/options/src/main/scala/scala/build/options/ComputeVersion.scala:31
- Compile.runCommand (cognitive 36) modules/cli/src/main/scala/scala/cli/commands/compile/Compile.scala:44
- Build.buildProject (cognitive 32) modules/build/src/main/scala/scala/build/Build.scala:1013
- Build.watch (cognitive 31) modules/build/src/main/scala/scala/build/Build.scala:788
- DefaultFile.runCommand (cognitive 30) modules/cli/src/main/scala/scala/cli/commands/default/DefaultFile.scala:58
- Build.build (cognitive 29) modules/build/src/main/scala/scala/build/Build.scala:364
- SemanticdbProcessor.postProcess (cognitive 29) modules/build/src/main/scala/scala/build/postprocessing/SemanticdbProcessor.scala:14
- ScalaCli.main0 (cognitive 29) modules/cli/src/main/scala/scala/cli/ScalaCli.scala:240
- CustomProgressBarRefreshDisplay.update (cognitive 29) modules/core/src/main/scala/scala/build/internals/CustomProgressBarRefreshDisplay.scala:55
- Publish.buildFileSet (cognitive 28) modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:497
- CustomProgressBarRefreshDisplay.display (cognitive 28) modules/core/src/main/scala/scala/build/internals/CustomProgressBarRefreshDisplay.scala:153
- CrossSources.forInputs (cognitive 26) modules/build/src/main/scala/scala/build/CrossSources.scala:165
- BspClient.updatedPublishDiagnosticsParams (cognitive 26) modules/build/src/main/scala/scala/build/bsp/BspClient.scala:25
- Inputs.forNonEmptyArgs (cognitive 26) modules/build/src/main/scala/scala/build/input/Inputs.scala:331
- InstallHome.runCommand (cognitive 26) modules/cli/src/main/scala/scala/cli/commands/installhome/InstallHome.scala:69
- NativeImage.buildNativeImage (cognitive 26) modules/cli/src/main/scala/scala/cli/packaging/NativeImage.scala:83
- DirectiveHandler.deriveParserImpl (cognitive 26) modules/directives/src/main/scala/scala/build/preprocessing/directives/DirectiveHandler.scala:132
- Fix.runCommand (cognitive 25) modules/cli/src/main/scala/scala/cli/commands/fix/Fix.scala:19
- Publish.maybePublish (cognitive 25) modules/cli/src/main/scala/scala/cli/commands/publish/Publish.scala:381
- Build.scalaNativeSupported (cognitive 24) modules/build/src/main/scala/scala/build/Build.scala:644
- PgpPush.runCommand (cognitive 24) modules/cli/src/main/scala/scala/cli/commands/pgp/PgpPush.scala:17
- Repl.runRepl (cognitive 24) modules/cli/src/main/scala/scala/cli/commands/repl/Repl.scala:284
- ExtractedDirectives.from (cognitive 23) modules/build/src/main/scala/scala/build/preprocessing/ExtractedDirectives.scala:25
- BspImpl.compile (cognitive 22) modules/build/src/main/scala/scala/build/bsp/BspImpl.scala:290
- Doc.generateScaladocDirPath (cognitive 22) modules/cli/src/main/scala/scala/cli/commands/doc/Doc.scala:229
- BuiltInRules.migrateDirectives (cognitive 21) modules/cli/src/main/scala/scala/cli/commands/fix/BuiltInRules.scala:153
- ScalafixRules.runRules (cognitive 21) modules/cli/src/main/scala/scala/cli/commands/fix/ScalafixRules.scala:19
- CliLogger.printDiagnostic (cognitive 21) modules/cli/src/main/scala/scala/cli/internal/CliLogger.scala:57
- BuildOptions.artifacts (cognitive 21) modules/options/src/main/scala/scala/build/options/BuildOptions.scala:476
- FeaturesStickyNav.FeaturesStickyNav (cognitive 21) website/src/components/FeaturesStickyNav.tsx:35
- InstallStickyNav.InstallStickyNav (cognitive 21) website/src/components/InstallStickyNav.tsx:36
- Fmt.runCommand (cognitive 20) modules/cli/src/main/scala/scala/cli/commands/fmt/Fmt.scala:42
- Package.runCommand (cognitive 19) modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:81
- RepositoryParser.repositoryOpt (cognitive 19) modules/cli/src/main/scala/scala/cli/commands/publish/RepositoryParser.scala:10
- WrappedSourceItem.equals (cognitive 19) modules/scala-cli-bsp/src/main/java/scala/build/bsp/WrappedSourceItem.java:73
- index.SearchPageContent (cognitive 19) REDACTED:54
- ScalaCli.loadJavaProperties (cognitive 18) modules/cli/src/main/scala/scala/cli/ScalaCli.scala:183
- Package.resolvePackageType (cognitive 18) modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:1370
- MavenProjectDescriptor.dependencySettings (cognitive 18) modules/cli/src/main/scala/scala/cli/exportCmd/MavenProjectDescriptor.scala:80
- ConfigDb.permsString (cognitive 18) modules/config/src/main/scala/scala/cli/config/ConfigDb.scala:174
- Build.prepareBuild (cognitive 17) modules/build/src/main/scala/scala/build/Build.scala:1183
- WrapperUtils.mainObjectInScript (cognitive 17) modules/build/src/main/scala/scala/build/internal/WrapperUtils.scala:28
- SlothPatcher.stripSignatures (cognitive 17) modules/build/src/main/scala/scala/build/postprocessing/SlothPatcher.scala:369
- ScalaJsLinkerConfig.linkerCliArgs (cognitive 17) modules/options/src/main/scala/scala/build/internal/ScalaJsLinkerConfig.scala:18
- ConsoleBloopBuildClient.printFileDiagnostic (cognitive 16) modules/build/src/main/scala/scala/build/ConsoleBloopBuildClient.scala:160
- SlothPatcher.publishCached (cognitive 16) modules/build/src/main/scala/scala/build/postprocessing/SlothPatcher.scala:562
- SheBang.partitionOnShebangSection (cognitive 16) modules/build/src/main/scala/scala/build/preprocessing/SheBang.scala:6
- Ivy.create (cognitive 16) modules/cli/src/main/scala/scala/cli/commands/publish/Ivy.scala:87
- Repl.runCommand (cognitive 16) modules/cli/src/main/scala/scala/cli/commands/repl/Repl.scala:70
- JavaOptions.javaHomeLocationOpt (cognitive 16) modules/options/src/main/scala/scala/build/options/JavaOptions.scala:59
- index.SearchResultItem (cognitive 16) REDACTED:287
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (23–27 lines × 2) modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:302
- Duplicated block (24 lines × 2) modules/cli/src/main/scala/scala/cli/commands/publish/checks/PasswordCheck.scala:101
- Duplicated block (20–23 lines × 2) modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:405
- Duplicated block (15 lines × 2) modules/cli/src/main/scala/scala/cli/commands/publish/PublishSetup.scala:308
- Duplicated block (14–15 lines × 2) modules/cli/src/main/scala/scala/cli/commands/shared/SharedOptions.scala:882
- Duplicated block (13–14 lines × 2) modules/directives/src/main/scala/scala/build/preprocessing/directives/DirectiveHandler.scala:35
- Duplicated block (12–13 lines × 2) modules/cli/src/main/scala/scala/cli/exportCmd/MillProjectDescriptor.scala:139
- Duplicated block (9–12 lines × 2) modules/cli/src/main/scala/scala/cli/exportCmd/MavenProject.scala:49
- Duplicated block (11 lines × 2) modules/cli/src/main/scala/scala/cli/internal/ProfileFileUpdater.scala:51
- Duplicated block (5–6 lines × 2) modules/build-macros/src/main/scala/scala/build/Ops.scala:134
- Duplicated block (5 lines × 2) modules/config/src/main/scala/scala/cli/config/internal/JavaHelper.scala:66
- Low cohesion: BspServer (LCOM4 8) modules/build/src/main/scala/scala/build/bsp/BspServer.scala:19
- Empty method body — does nothing with its inputs modules/options/src/main/scala/scala/build/CoursierUtils.scala:9
- Swallowed exception (caught, then discarded) modules/core/src/main/scala/scala/build/internals/NativeWrapper.scala:156
Minor — 65 finding(s)
- Orphaned file modules/cli/src/main/scala/scala/cli/commands/publish/checks/PgpSecretKeyCheck.scala:1
- Orphaned file modules/directives/src/main/scala/scala/build/preprocessing/directives/DirectiveHandler.scala:1
- Orphaned file modules/cli/src/main/scala/scala/cli/internal/CliLogger.scala:1
- Orphaned file modules/config/src/main/scala/scala/cli/config/ConfigDb.scala:1
- Orphaned file modules/cli/src/main/scala/scala/cli/commands/fmt/FmtUtil.scala:1
- Orphaned file modules/options/src/main/scala/scala/build/options/ScalaNativeOptions.scala:1
- Orphaned file modules/options/src/main/scala/scala/build/options/ComputeVersion.scala:1
- Orphaned file modules/directives/src/main/scala/scala/build/preprocessing/directives/PublishContextual.scala:1
- Orphaned file modules/options/src/main/scala/scala/build/options/JavaOptions.scala:1
- Orphaned file modules/options/src/main/scala/scala/build/info/BuildInfo.scala:1
- Orphaned file modules/core/src/main/scala/scala/build/internals/CustomProgressBarRefreshDisplay.scala:1
- Orphaned file modules/build-macros/src/main/scala/scala/build/Ops.scala:1
- Orphaned file modules/cli/src/main/scala/scala/cli/commands/dependencyupdate/DependencyUpdate.scala:1
- Orphaned file modules/cli/src/main/scala/scala/cli/commands/CustomWindowsEnvVarUpdater.scala:1
- Orphaned file modules/cli/src/main/scala/scala/cli/commands/installhome/InstallHome.scala:1
- Orphaned file modules/cli/src/main/scala/scala/cli/commands/util/JvmUtils.scala:1
- Orphaned file modules/cli/src/main/scala/scala/cli/ScalaCliCommands.scala:1
- Orphaned file modules/cli/src/main/scala/scala/cli/commands/publish/checks/PasswordCheck.scala:1
- Orphaned file modules/cli/src/main/scala/scala/cli/internal/ProcUtil.scala:1
- Orphaned file modules/cli/src/main/scala/scala/cli/commands/publish/checks/UserCheck.scala:1
- Orphaned file modules/config/src/main/scala/scala/cli/config/PasswordOption.scala:1
- Orphaned file modules/options/src/main/scala/scala/build/options/BuildRequirements.scala:1
- Orphaned file modules/directives/src/main/scala/scala/build/preprocessing/directives/Platform.scala:1
- Orphaned file modules/core/src/main/scala/scala/build/Position.scala:1
- Orphaned file modules/core/src/main/scala/scala/build/Logger.scala:1
- README/code drift website/docs/guides/advanced/scala-wasm.md:61
- README/code drift website/docs/guides/advanced/scala-wasm.md:74
- README/code drift website/docs/guides/advanced/scala-wasm.md:76
- Duplicated predicate website/src/components/FeaturesStickyNav.tsx:150
- Duplicated predicate website/src/components/FeaturesStickyNav.tsx:20
- Duplicated predicate modules/cli/src/main/scala/scala/cli/commands/package0/Package.scala:446
- REDACTED
- REDACTED
- Disabled test modules/integration/src/test/scala/scala/cli/integration/RunTestDefinitions.scala:465
- Disabled test modules/integration/src/test/scala/scala/cli/integration/RunTestsDefault.scala:356
- Fat interface: Logger (20 abstract members) modules/core/src/main/scala/scala/build/Logger.scala:13
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found
- REDACTED
- Further orphaned files (smaller)
- REDACTED
- Placeholder literal left in code modules/directives/src/main/scala/scala/build/preprocessing/directives/Publish.scala:22
- No ADRs
- Scala's null is not held to the type system everywhere
- Silent fallback default in catch modules/core/src/main/scala/scala/build/internals/NativeWrapper.scala:156
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-063f5224d0004e4895596558d90a6ff7/history.json --exit-code 0 --source . | 1 | 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-063f5224d0004e4895596558d90a6ff7/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 . | 311 | 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 config --format json --quiet . | 15 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 14 file(s) — `modules/cli/src/main/scala/scala/cli/commands/RestrictableCommand.scala`, `modules/cli/src/main/scala/scala/cli/commands/compile/Compile.scala`, `modules/cli/src/main/scala/scala/cli/commands/export0/Export.scala`, `modules/cli/src/main/scala/scala/cli/commands/fix/Fix.scala`, `modules/cli/src/main/scala/scala/cli/commands/fix/ScalafixRules.scala`, … (+9 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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 |