Executive summary
scalacenter/bloop falls short of our standard for production, held back most by its Code Health lens, the quality of the code itself. It scores 66 out of 100 and is rated Adequate, and 36 of its 37 critical findings are security problems.
Code Health, at 60, is the weakest lens and counts most in the score. The best first step is declaring which values may be missing, worth about 5 points. Handling the errors the code catches and ignores comes next, worth about 4 points. Raising Code Health to 70 would lift the score to about 71.
Twenty-nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three secrets can leak from the build pipeline, and two pipeline steps run downloads nobody checks. Pinning each tool to an exact version, limiting each secret to its own step and checking each download against a checksum would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and updating the vulnerable packages would deal with the package with a known security hole. The package under a licence on your banned list needs replacing, or clearing with your legal team.
The product code is 34,485 lines, about €70,000 to rebuild.
If Code Health rose from 60 to 70, the lowest score rated Strong, the score would rise from 66 to about 71.
New since the last survey: 19 findings
- Cognitive Complexity · CommandsDocGenerator.main (cognitive 19) frontend/src/main/scala/bloop/util/CommandsDocGenerator.scala
- Code Duplication · Edited copy of a member (75 corresponding lines) bridges/scala-native-0.4/src/main/scala/bloop/scalanative/NativeBridge.scala
- Code Duplication · Edited copy of a member (61 corresponding lines) backend/src/main/scala/sbt/internal/inc/bloop/internal/BloopAnalysisCallback.scala
- Code Duplication · Edited copy of a member (45 corresponding lines) backend/src/main/scala/bloop/task/Task.scala
- Code Duplication · Edited copy of a member (26 corresponding lines) frontend/src/main/scala/bloop/engine/tasks/LinkTask.scala
- Code Duplication · Edited copy of a member (30 corresponding lines) frontend/src/main/scala/bloop/dap/BloopDebuggee.scala
- Code Duplication · Edited copy of a member (18 corresponding lines) bloop-rifle/src/main/scala/bloop/rifle/internal/nailgun/Nailgun.scala
- Code Duplication · Edited copy of a member (13 corresponding lines) integrations/sbt-bloop/src/main/scala-2.12/bloop/integrations/sbt/CompatPlatform.scala
- Code Duplication · Edited copy of a member (19 corresponding lines) backend/src/main/scala/sbt/internal/inc/bloop/internal/BloopAnalysisCallback.scala
- Code Duplication · Edited copy of a member (4 corresponding lines) backend/src/main/scala/sbt/internal/inc/bloop/internal/BloopAnalysisCallback.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) bridges/scalajs-0.6/src/main/scala/bloop/scalajs/JsBridge.scala
- Code Duplication · Edited copy of a member (10 corresponding lines) frontend/src/main/scala/bloop/testing/JUnit5FrameworkDependency.scala
- Code Duplication · Edited copy of a member (4 corresponding lines) backend/src/main/scala/sbt/internal/inc/bloop/internal/BloopAnalysisCallback.scala
- Code Duplication · Edited copy of a member (11 corresponding lines) backend/src/main/scala/sbt/internal/inc/bloop/internal/BloopAnalysisCallback.scala
- Code Duplication · Edited copy of a member (5 corresponding lines) frontend/src/main/scala/bloop/data/Project.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) frontend/src/main/scala/bloop/engine/tasks/toolchains/ScalaJsToolchain.scala
- Code Duplication · Edited copy of a member (22 corresponding lines) docs-gen/src/main/scala/bloop/docs/ReleasesModifier.scala
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
Fixed since the last survey: 7 findings
- Code Duplication · Duplicated block (16 lines × 2) backend/src/main/scala/sbt/internal/inc/bloop/internal/BloopAnalysisCallback.scala
- Code Duplication · Duplicated block (7 lines × 2) frontend/src/main/scala/bloop/cli/completion/FishFormat.scala
- Static Analysis (SAST) · Medium: watchdog-regexp-from-parameter-ts REDACTED
- Static Analysis (SAST) · Medium: watchdog-regexp-from-parameter-ts REDACTED
- Static Analysis (SAST) · Medium: watchdog-regexp-from-parameter-ts REDACTED
- Static Analysis (SAST) · Medium: watchdog-regexp-from-parameter-ts REDACTED
- Documentation (README) · README may be stale
Rebuild cost: about €70,000 · Estimate
| Cost to rebuild | €23,000 to €120,000, for 388 to 1,230 hours of work, about 0.5 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 66. 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: 34,485 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 bloop.Compiler | 2 bloop.rifle | 3 bloop.task | 4 bloop.cli.options | 5 bloop.data.ClientInfo | 6 bloop.io.Paths | 7 bloop.reporter | 8 bloop.rifle.internal.nailgun | 9 bloop.tracing | 10 bloop.bsp | 11 bloop.logging | 12 bloop.util | 13 bloop.data | 14 bloop.engine.Dag | 15 bloop.io | 16 bloop.CompilerCache | 17 bloop.cli.Commands | 18 bloop.engine.Build | 19 bloop.engine.tasks.compilation | 20 bloop.engine.tasks.toolchains | 21 bloop.logging.CompilationEvent | 22 buildpress | 23 bloop.data.Platform | 24 bloop.engine.caches | 25 bloop.engine | 26 bloop.engine.tasks.compilation.CompileGatekeeper | 27 bloop.cli | 28 bloop.engine.tasks.compilation.CompileClientStore | 29 bloop | 30 bloop.Cli | 31 bloop.cli.completion | 32 bloop.dap | 33 bloop.engine.State | 34 bloop.exec | 35 bloop.Compiler.Result | 36 bloop.engine.caches.StateCache | 37 bloop.testing | 38 sbt.internal.inc.bloop | 39 sbt.internal.inc.bloop.internal | 40 bloop.engine.tasks |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 bloop.Compiler | ||||||||||||||||||||||||||||||||||||||||
| 2 bloop.rifle | ||||||||||||||||||||||||||||||||||||||||
| 3 bloop.task | ||||||||||||||||||||||||||||||||||||||||
| 4 bloop.cli.options | 5 | 3 | ||||||||||||||||||||||||||||||||||||||
| 5 bloop.data.ClientInfo | 4 | 2 | ||||||||||||||||||||||||||||||||||||||
| 6 bloop.io.Paths | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 bloop.reporter | 5 | 3 | 7 | |||||||||||||||||||||||||||||||||||||
| 8 bloop.rifle.internal.nailgun | 3 | |||||||||||||||||||||||||||||||||||||||
| 9 bloop.tracing | 3 | |||||||||||||||||||||||||||||||||||||||
| 10 bloop.bsp | 4 | 1 | 3 | 4 | 4 | 3 | 1 | |||||||||||||||||||||||||||||||||
| 11 bloop.logging | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 bloop.util | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 13 bloop.data | 1 | 1 | 1 | 1 | 5 | 2 | 2 | |||||||||||||||||||||||||||||||||
| 14 bloop.engine.Dag | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 bloop.io | 4 | 1 | 5 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 16 bloop.CompilerCache | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 bloop.cli.Commands | 1 | 27 | ||||||||||||||||||||||||||||||||||||||
| 18 bloop.engine.Build | 1 | 5 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 bloop.engine.tasks.compilation | 5 | 2 | 4 | 6 | 3 | 9 | 3 | 3 | 3 | 5 | ||||||||||||||||||||||||||||||
| 20 bloop.engine.tasks.toolchains | 2 | 3 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 21 bloop.logging.CompilationEvent | 2 | 5 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 buildpress | 4 | |||||||||||||||||||||||||||||||||||||||
| 23 bloop.data.Platform | 4 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 24 bloop.engine.caches | 1 | 4 | 4 | 4 | 4 | 2 | 4 | 2 | ||||||||||||||||||||||||||||||||
| 25 bloop.engine | 4 | 1 | 4 | 4 | 13 | 1 | 4 | 1 | 2 | 7 | 1 | |||||||||||||||||||||||||||||
| 26 bloop.engine.tasks.compilation.CompileGatekeeper | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 27 bloop.cli | 2 | 1 | 5 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 28 bloop.engine.tasks.compilation.CompileClientStore | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 29 bloop | 3 | 4 | 3 | 5 | 2 | 1 | 6 | 1 | 1 | |||||||||||||||||||||||||||||||
| 30 bloop.Cli | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 bloop.cli.completion | 4 | 8 | ||||||||||||||||||||||||||||||||||||||
| 32 bloop.dap | 4 | 2 | 2 | 5 | 4 | |||||||||||||||||||||||||||||||||||
| 33 bloop.engine.State | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 bloop.exec | 4 | 5 | 4 | 5 | ||||||||||||||||||||||||||||||||||||
| 35 bloop.Compiler.Result | 8 | 3 | 6 | 4 | ||||||||||||||||||||||||||||||||||||
| 36 bloop.engine.caches.StateCache | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 bloop.testing | 1 | 6 | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 38 sbt.internal.inc.bloop | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 39 sbt.internal.inc.bloop.internal | 3 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 bloop.engine.tasks | 4 | 1 | 1 | 4 | 5 | 4 | 1 | 2 | 2 | 5 | 1 | 1 | 3 |
4→2 bloop.cli.options uses bloop.rifle✕
- Connections
- 5 pairs of types, where a type in bloop.cli.options uses a type in bloop.rifle.
- The types involved
bloop.cli.options.DefaultOptions→bloop.rifle.BloopRifleConfigbloop.cli.options.OutputOptions→bloop.rifle.BloopRifleConfigbloop.cli.options.SharedCompilationServerOptions→bloop.rifle.BloopRifleConfigbloop.cli.options.StartOptions→bloop.rifle.BloopRifleConfigbloop.cli.options.StatusOptions→bloop.rifle.BloopRifleConfig
- Direction
- bloop.cli.options uses bloop.rifle, so a change to bloop.rifle can break bloop.cli.options, while a change to bloop.cli.options can't break bloop.rifle.
- Position
- Below the diagonal: bloop.cli.options uses a module listed above it, which is the healthy direction.
4→27 bloop.cli.options uses bloop.cli part of a loop✕
- Connections
- 3 pairs of types, where a type in bloop.cli.options uses a type in bloop.cli.
- The types involved
bloop.cli.options.LoggingOptions→bloop.cli.Loggerbloop.cli.options.SharedCompilationServerOptions→bloop.cli.Loggerbloop.cli.options.SharedDirectoriesOptions→bloop.cli.Directories
- Direction
- bloop.cli.options uses bloop.cli, so a change to bloop.cli can break bloop.cli.options, while a change to bloop.cli.options can't break bloop.cli.
- 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→13 bloop.data.ClientInfo uses bloop.data part of a loop✕
- Connections
- 4 pairs of types, where a type in bloop.data.ClientInfo uses a type in bloop.data.
- The types involved
bloop.data.ClientInfo.BspClientInfo→bloop.data.ClientInfobloop.data.ClientInfo.BspClientInfo→bloop.data.Projectbloop.data.ClientInfo.CliClientInfo→bloop.data.ClientInfobloop.data.ClientInfo.CliClientInfo→bloop.data.Project
- Direction
- bloop.data.ClientInfo uses bloop.data, so a change to bloop.data can break bloop.data.ClientInfo, while a change to bloop.data.ClientInfo can't break bloop.data.
- 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→15 bloop.data.ClientInfo uses bloop.io part of a loop✕
- Connections
- 2 pairs of types, where a type in bloop.data.ClientInfo uses a type in bloop.io.
- The types involved
bloop.data.ClientInfo.BspClientInfo→bloop.io.AbsolutePathbloop.data.ClientInfo.CliClientInfo→bloop.io.AbsolutePath
- Direction
- bloop.data.ClientInfo uses bloop.io, so a change to bloop.io can break bloop.data.ClientInfo, while a change to bloop.data.ClientInfo can't break bloop.io.
- 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→15 bloop.io.Paths uses bloop.io part of a loop✕
- Connections
- 1 pair of types, where a type in bloop.io.Paths uses a type in bloop.io.
- The types involved
bloop.io.Paths.AttributedPath→bloop.io.AbsolutePath
- Direction
- bloop.io.Paths uses bloop.io, so a change to bloop.io can break bloop.io.Paths, while a change to bloop.io.Paths can't break bloop.io.
- 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→11 bloop.reporter uses bloop.logging part of a loop✕
- Connections
- 5 pairs of types, where a type in bloop.reporter uses a type in bloop.logging.
- The types involved
bloop.reporter.BspProjectReporter→bloop.logging.BspServerLoggerbloop.reporter.LogReporter→bloop.logging.Loggerbloop.reporter.ObservedReporter→bloop.logging.Loggerbloop.reporter.ObservedReporter→bloop.logging.ObservedLoggerbloop.reporter.Reporter→bloop.logging.Logger
- Direction
- bloop.reporter uses bloop.logging, so a change to bloop.logging can break bloop.reporter, while a change to bloop.reporter can't break bloop.logging.
- 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→13 bloop.reporter uses bloop.data part of a loop✕
- Connections
- 3 pairs of types, where a type in bloop.reporter uses a type in bloop.data.
- The types involved
bloop.reporter.BspProjectReporter→bloop.data.Projectbloop.reporter.LogReporter→bloop.data.Projectbloop.reporter.ReporterInputs→bloop.data.Project
- Direction
- bloop.reporter uses bloop.data, so a change to bloop.data can break bloop.reporter, while a change to bloop.reporter can't break bloop.data.
- 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→15 bloop.reporter uses bloop.io part of a loop✕
- Connections
- 7 pairs of types, where a type in bloop.reporter uses a type in bloop.io.
- The types involved
bloop.reporter.BspProjectReporter→bloop.io.AbsolutePathbloop.reporter.ConfigurableReporter→bloop.io.AbsolutePathbloop.reporter.LogReporter→bloop.io.AbsolutePathbloop.reporter.ObservedReporter→bloop.io.AbsolutePathbloop.reporter.Reporter→bloop.io.AbsolutePathbloop.reporter.ReporterInputs→bloop.io.AbsolutePathbloop.reporter.ZincReporter→bloop.io.AbsolutePath
- Direction
- bloop.reporter uses bloop.io, so a change to bloop.io can break bloop.reporter, while a change to bloop.reporter can't break bloop.io.
- 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→2 bloop.rifle.internal.nailgun uses bloop.rifle✕
- Connections
- 3 pairs of types, where a type in bloop.rifle.internal.nailgun uses a type in bloop.rifle.
- The types involved
bloop.rifle.internal.nailgun.Client→bloop.rifle.BloopRifleLoggerbloop.rifle.internal.nailgun.SocketClient→bloop.rifle.BloopRifleLoggerbloop.rifle.internal.nailgun.TcpClient→bloop.rifle.BloopRifleLogger
- Direction
- bloop.rifle.internal.nailgun uses bloop.rifle, so a change to bloop.rifle can break bloop.rifle.internal.nailgun, while a change to bloop.rifle.internal.nailgun can't break bloop.rifle.
- Position
- Below the diagonal: bloop.rifle.internal.nailgun uses a module listed above it, which is the healthy direction.
9→3 bloop.tracing uses bloop.task✕
- Connections
- 3 pairs of types, where a type in bloop.tracing uses a type in bloop.task.
- The types involved
bloop.tracing.BraveTracer→bloop.task.Taskbloop.tracing.BraveTracerInternal→bloop.task.Taskbloop.tracing.NoopTracer→bloop.task.Task
- Direction
- bloop.tracing uses bloop.task, so a change to bloop.task can break bloop.tracing, while a change to bloop.tracing can't break bloop.task.
- Position
- Below the diagonal: bloop.tracing uses a module listed above it, which is the healthy direction.
10→3 bloop.bsp uses bloop.task✕
- Connections
- 4 pairs of types, where a type in bloop.bsp uses a type in bloop.task.
- The types involved
bloop.bsp.BloopBspServices→bloop.task.Taskbloop.bsp.BloopLanguageClient→bloop.task.Taskbloop.bsp.BloopLanguageServer→bloop.task.Taskbloop.bsp.BspServer→bloop.task.Task
- Direction
- bloop.bsp uses bloop.task, so a change to bloop.task can break bloop.bsp, while a change to bloop.bsp can't break bloop.task.
- Position
- Below the diagonal: bloop.bsp uses a module listed above it, which is the healthy direction.
10→5 bloop.bsp uses bloop.data.ClientInfo✕
- Connections
- 1 pair of types, where a type in bloop.bsp uses a type in bloop.data.ClientInfo.
- The types involved
bloop.bsp.BloopBspServices→bloop.data.ClientInfo.BspClientInfo
- Direction
- bloop.bsp uses bloop.data.ClientInfo, so a change to bloop.data.ClientInfo can break bloop.bsp, while a change to bloop.bsp can't break bloop.data.ClientInfo.
- Position
- Below the diagonal: bloop.bsp uses a module listed above it, which is the healthy direction.
10→11 bloop.bsp uses bloop.logging part of a loop✕
- Connections
- 3 pairs of types, where a type in bloop.bsp uses a type in bloop.logging.
- The types involved
bloop.bsp.BloopBspServices→bloop.logging.BspServerLoggerbloop.bsp.BloopBspServices→bloop.logging.DebugFilterbloop.bsp.BspServer→bloop.logging.DebugFilter
- Direction
- bloop.bsp uses bloop.logging, so a change to bloop.logging can break bloop.bsp, while a change to bloop.bsp can't break bloop.logging.
- 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→13 bloop.bsp uses bloop.data part of a loop✕
- Connections
- 4 pairs of types, where a type in bloop.bsp uses a type in bloop.data.
- The types involved
bloop.bsp.BloopBspServices→bloop.data.ClientInfobloop.bsp.BloopBspServices→bloop.data.Projectbloop.bsp.BloopBspServices→bloop.data.WorkspaceSettingsbloop.bsp.ProjectUris→bloop.data.Project
- Direction
- bloop.bsp uses bloop.data, so a change to bloop.data can break bloop.bsp, while a change to bloop.bsp can't break bloop.data.
- 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→15 bloop.bsp uses bloop.io part of a loop✕
- Connections
- 4 pairs of types, where a type in bloop.bsp uses a type in bloop.io.
- The types involved
bloop.bsp.BloopBspServices→bloop.io.AbsolutePathbloop.bsp.BspServer→bloop.io.RelativePathbloop.bsp.BspServer→bloop.io.ServerHandlebloop.bsp.ProjectUris→bloop.io.AbsolutePath
- Direction
- bloop.bsp uses bloop.io, so a change to bloop.io can break bloop.bsp, while a change to bloop.bsp can't break bloop.io.
- 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 bloop.bsp uses bloop.engine part of a loop✕
- Connections
- 3 pairs of types, where a type in bloop.bsp uses a type in bloop.engine.
- The types involved
bloop.bsp.BloopBspServices→bloop.engine.Statebloop.bsp.BspServer→bloop.engine.Statebloop.bsp.ProjectUris→bloop.engine.State
- Direction
- bloop.bsp uses bloop.engine, so a change to bloop.engine can break bloop.bsp, while a change to bloop.bsp can't break bloop.engine.
- 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→29 bloop.bsp uses bloop part of a loop✕
- Connections
- 1 pair of types, where a type in bloop.bsp uses a type in bloop.
- The types involved
bloop.bsp.BloopBspServices→bloop.ScalaInstance
- Direction
- bloop.bsp uses bloop, so a change to bloop can break bloop.bsp, while a change to bloop.bsp can't break bloop.
- 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→7 bloop.logging uses bloop.reporter✕
- Connections
- 1 pair of types, where a type in bloop.logging uses a type in bloop.reporter.
- The types involved
bloop.logging.ObservedLogger→bloop.reporter.ReporterAction
- Direction
- bloop.logging uses bloop.reporter, so a change to bloop.reporter can break bloop.logging, while a change to bloop.logging can't break bloop.reporter.
- Position
- Below the diagonal: bloop.logging uses a module listed above it, which is the healthy direction.
11→10 bloop.logging uses bloop.bsp✕
- Connections
- 1 pair of types, where a type in bloop.logging uses a type in bloop.bsp.
- The types involved
bloop.logging.BspServerLogger→bloop.bsp.BloopLanguageClient
- Direction
- bloop.logging uses bloop.bsp, so a change to bloop.bsp can break bloop.logging, while a change to bloop.logging can't break bloop.bsp.
- Position
- Below the diagonal: bloop.logging uses a module listed above it, which is the healthy direction.
12→7 bloop.util uses bloop.reporter✕
- Connections
- 1 pair of types, where a type in bloop.util uses a type in bloop.reporter.
- The types involved
bloop.util.AnalysisUtils→bloop.reporter.ProblemPerPhase
- Direction
- bloop.util uses bloop.reporter, so a change to bloop.reporter can break bloop.util, while a change to bloop.util can't break bloop.reporter.
- Position
- Below the diagonal: bloop.util uses a module listed above it, which is the healthy direction.
12→11 bloop.util uses bloop.logging✕
- Connections
- 2 pairs of types, where a type in bloop.util uses a type in bloop.logging.
- The types involved
bloop.util.ProxySetup→bloop.logging.Loggerbloop.util.SystemProperties→bloop.logging.Logger
- Direction
- bloop.util uses bloop.logging, so a change to bloop.logging can break bloop.util, while a change to bloop.util can't break bloop.logging.
- Position
- Below the diagonal: bloop.util uses a module listed above it, which is the healthy direction.
12→15 bloop.util uses bloop.io part of a loop✕
- Connections
- 2 pairs of types, where a type in bloop.util uses a type in bloop.io.
- The types involved
bloop.util.BestEffortUtils→bloop.io.AbsolutePathbloop.util.Environment→bloop.io.AbsolutePath
- Direction
- bloop.util uses bloop.io, so a change to bloop.io can break bloop.util, while a change to bloop.util can't break bloop.io.
- 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→3 bloop.data uses bloop.task✕
- Connections
- 1 pair of types, where a type in bloop.data uses a type in bloop.task.
- The types involved
bloop.data.Project→bloop.task.Task
- Direction
- bloop.data uses bloop.task, so a change to bloop.task can break bloop.data, while a change to bloop.data can't break bloop.task.
- Position
- Below the diagonal: bloop.data uses a module listed above it, which is the healthy direction.
13→6 bloop.data uses bloop.io.Paths✕
- Connections
- 1 pair of types, where a type in bloop.data uses a type in bloop.io.Paths.
- The types involved
bloop.data.Origin→bloop.io.Paths.AttributedPath
- Direction
- bloop.data uses bloop.io.Paths, so a change to bloop.io.Paths can break bloop.data, while a change to bloop.data can't break bloop.io.Paths.
- Position
- Below the diagonal: bloop.data uses a module listed above it, which is the healthy direction.
13→11 bloop.data uses bloop.logging✕
- Connections
- 1 pair of types, where a type in bloop.data uses a type in bloop.logging.
- The types involved
bloop.data.Project→bloop.logging.Logger
- Direction
- bloop.data uses bloop.logging, so a change to bloop.logging can break bloop.data, while a change to bloop.data can't break bloop.logging.
- Position
- Below the diagonal: bloop.data uses a module listed above it, which is the healthy direction.
13→12 bloop.data uses bloop.util✕
- Connections
- 1 pair of types, where a type in bloop.data uses a type in bloop.util.
- The types involved
bloop.data.Origin→bloop.util.CacheHashCode
- Direction
- bloop.data uses bloop.util, so a change to bloop.util can break bloop.data, while a change to bloop.data can't break bloop.util.
- Position
- Below the diagonal: bloop.data uses a module listed above it, which is the healthy direction.
13→15 bloop.data uses bloop.io part of a loop✕
- Connections
- 5 pairs of types, where a type in bloop.data uses a type in bloop.io.
- The types involved
bloop.data.ClientInfo→bloop.io.AbsolutePathbloop.data.JdkConfig→bloop.io.AbsolutePathbloop.data.Origin→bloop.io.AbsolutePathbloop.data.Project→bloop.io.AbsolutePathbloop.data.SourcesGlobs→bloop.io.AbsolutePath
- Direction
- bloop.data uses bloop.io, so a change to bloop.io can break bloop.data, while a change to bloop.data can't break bloop.io.
- 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 bloop.data uses bloop.engine part of a loop✕
- Connections
- 2 pairs of types, where a type in bloop.data uses a type in bloop.engine.
- The types involved
bloop.data.Project→bloop.engine.Dagbloop.data.Project→bloop.engine.SourceGenerator
- Direction
- bloop.data uses bloop.engine, so a change to bloop.engine can break bloop.data, while a change to bloop.data can't break bloop.engine.
- 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→29 bloop.data uses bloop part of a loop✕
- Connections
- 2 pairs of types, where a type in bloop.data uses a type in bloop.
- The types involved
bloop.data.ClientInfo→bloop.ClientClassesObserverbloop.data.Project→bloop.ScalaInstance
- Direction
- bloop.data uses bloop, so a change to bloop can break bloop.data, while a change to bloop.data can't break bloop.
- 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→13 bloop.engine.Dag uses bloop.data✕
- Connections
- 2 pairs of types, where a type in bloop.engine.Dag uses a type in bloop.data.
- The types involved
bloop.engine.Dag.DagResult→bloop.data.Projectbloop.engine.Dag.RecursiveTrace→bloop.data.Project
- Direction
- bloop.engine.Dag uses bloop.data, so a change to bloop.data can break bloop.engine.Dag, while a change to bloop.engine.Dag can't break bloop.data.
- Position
- Below the diagonal: bloop.engine.Dag uses a module listed above it, which is the healthy direction.
14→25 bloop.engine.Dag uses bloop.engine part of a loop✕
- Connections
- 1 pair of types, where a type in bloop.engine.Dag uses a type in bloop.engine.
- The types involved
bloop.engine.Dag.DagResult→bloop.engine.Dag
- Direction
- bloop.engine.Dag uses bloop.engine, so a change to bloop.engine can break bloop.engine.Dag, while a change to bloop.engine.Dag can't break bloop.engine.
- 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 bloop.io uses bloop.task✕
- Connections
- 4 pairs of types, where a type in bloop.io uses a type in bloop.task.
- The types involved
bloop.io.ClasspathHasher→bloop.task.Taskbloop.io.ParallelOps→bloop.task.Taskbloop.io.SourceHasher→bloop.task.Taskbloop.io.SourceWatcher→bloop.task.Task
- Direction
- bloop.io uses bloop.task, so a change to bloop.task can break bloop.io, while a change to bloop.io can't break bloop.task.
- Position
- Below the diagonal: bloop.io uses a module listed above it, which is the healthy direction.
15→9 bloop.io uses bloop.tracing✕
- Connections
- 1 pair of types, where a type in bloop.io uses a type in bloop.tracing.
- The types involved
bloop.io.ClasspathHasher→bloop.tracing.BraveTracer
- Direction
- bloop.io uses bloop.tracing, so a change to bloop.tracing can break bloop.io, while a change to bloop.io can't break bloop.tracing.
- Position
- Below the diagonal: bloop.io uses a module listed above it, which is the healthy direction.
15→11 bloop.io uses bloop.logging✕
- Connections
- 5 pairs of types, where a type in bloop.io uses a type in bloop.logging.
- The types involved
bloop.io.ClasspathHasher→bloop.logging.Loggerbloop.io.ParallelOps→bloop.logging.Loggerbloop.io.SourceHasher→bloop.logging.Loggerbloop.io.SourceWatcher→bloop.logging.DebugFilterbloop.io.Timer→bloop.logging.Logger
- Direction
- bloop.io uses bloop.logging, so a change to bloop.logging can break bloop.io, while a change to bloop.io can't break bloop.logging.
- Position
- Below the diagonal: bloop.io uses a module listed above it, which is the healthy direction.
15→12 bloop.io uses bloop.util✕
- Connections
- 1 pair of types, where a type in bloop.io uses a type in bloop.util.
- The types involved
bloop.io.SourceHasher→bloop.util.HashedSource
- Direction
- bloop.io uses bloop.util, so a change to bloop.util can break bloop.io, while a change to bloop.io can't break bloop.util.
- Position
- Below the diagonal: bloop.io uses a module listed above it, which is the healthy direction.
15→13 bloop.io uses bloop.data✕
- Connections
- 1 pair of types, where a type in bloop.io uses a type in bloop.data.
- The types involved
bloop.io.SourceHasher→bloop.data.Project
- Direction
- bloop.io uses bloop.data, so a change to bloop.data can break bloop.io, while a change to bloop.io can't break bloop.data.
- Position
- Below the diagonal: bloop.io uses a module listed above it, which is the healthy direction.
15→25 bloop.io uses bloop.engine part of a loop✕
- Connections
- 2 pairs of types, where a type in bloop.io uses a type in bloop.engine.
- The types involved
bloop.io.SourceHasher→bloop.engine.SourceGeneratorbloop.io.SourceWatcher→bloop.engine.State
- Direction
- bloop.io uses bloop.engine, so a change to bloop.engine can break bloop.io, while a change to bloop.io can't break bloop.engine.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→11 bloop.CompilerCache uses bloop.logging✕
- Connections
- 1 pair of types, where a type in bloop.CompilerCache uses a type in bloop.logging.
- The types involved
bloop.CompilerCache.BloopJavaCompiler→bloop.logging.Logger
- Direction
- bloop.CompilerCache uses bloop.logging, so a change to bloop.logging can break bloop.CompilerCache, while a change to bloop.CompilerCache can't break bloop.logging.
- Position
- Below the diagonal: bloop.CompilerCache uses a module listed above it, which is the healthy direction.
16→15 bloop.CompilerCache uses bloop.io✕
- Connections
- 1 pair of types, where a type in bloop.CompilerCache uses a type in bloop.io.
- The types involved
bloop.CompilerCache.JavacKey→bloop.io.AbsolutePath
- Direction
- bloop.CompilerCache uses bloop.io, so a change to bloop.io can break bloop.CompilerCache, while a change to bloop.CompilerCache can't break bloop.io.
- Position
- Below the diagonal: bloop.CompilerCache uses a module listed above it, which is the healthy direction.
17→15 bloop.cli.Commands uses bloop.io✕
- Connections
- 1 pair of types, where a type in bloop.cli.Commands uses a type in bloop.io.
- The types involved
bloop.cli.Commands.UnixLocalBsp→bloop.io.AbsolutePath
- Direction
- bloop.cli.Commands uses bloop.io, so a change to bloop.io can break bloop.cli.Commands, while a change to bloop.cli.Commands can't break bloop.io.
- Position
- Below the diagonal: bloop.cli.Commands uses a module listed above it, which is the healthy direction.
17→27 bloop.cli.Commands uses bloop.cli part of a loop✕
- Connections
- 27 pairs of types, where a type in bloop.cli.Commands uses a type in bloop.cli. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
bloop.cli.Commands.About→bloop.cli.CliOptionsbloop.cli.Commands.Autocomplete→bloop.cli.CliOptionsbloop.cli.Commands.Bsp→bloop.cli.BspProtocolbloop.cli.Commands.Bsp→bloop.cli.CliOptionsbloop.cli.Commands.Clean→bloop.cli.CliOptionsbloop.cli.Commands.Command→bloop.cli.CliOptionsbloop.cli.Commands.Compile→bloop.cli.CliOptionsbloop.cli.Commands.Compile→bloop.cli.ReporterKindbloop.cli.Commands.CompilingCommand→bloop.cli.ReporterKindbloop.cli.Commands.Configure→bloop.cli.CliOptionsbloop.cli.Commands.Console→bloop.cli.CliOptionsbloop.cli.Commands.Console→bloop.cli.ReplKindbloop.cli.Commands.Console→bloop.cli.ReporterKindbloop.cli.Commands.Help→bloop.cli.CliOptionsbloop.cli.Commands.Link→bloop.cli.CliOptionsbloop.cli.Commands.Link→bloop.cli.OptimizerConfigbloop.cli.Commands.Link→bloop.cli.ReporterKindbloop.cli.Commands.LinkingCommand→bloop.cli.OptimizerConfigbloop.cli.Commands.Projects→bloop.cli.CliOptionsbloop.cli.Commands.Run→bloop.cli.CliOptionsbloop.cli.Commands.Run→bloop.cli.OptimizerConfigbloop.cli.Commands.Run→bloop.cli.ReporterKindbloop.cli.Commands.TcpBsp→bloop.cli.CliOptionsbloop.cli.Commands.Test→bloop.cli.CliOptionsbloop.cli.Commands.Test→bloop.cli.ReporterKind
- Direction
- bloop.cli.Commands uses bloop.cli, so a change to bloop.cli can break bloop.cli.Commands, while a change to bloop.cli.Commands can't break bloop.cli.
- 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→12 bloop.engine.Build uses bloop.util✕
- Connections
- 1 pair of types, where a type in bloop.engine.Build uses a type in bloop.util.
- The types involved
bloop.engine.Build.ReadConfiguration→bloop.util.CacheHashCode
- Direction
- bloop.engine.Build uses bloop.util, so a change to bloop.util can break bloop.engine.Build, while a change to bloop.engine.Build can't break bloop.util.
- Position
- Below the diagonal: bloop.engine.Build uses a module listed above it, which is the healthy direction.
18→13 bloop.engine.Build uses bloop.data✕
- Connections
- 5 pairs of types, where a type in bloop.engine.Build uses a type in bloop.data.
- The types involved
bloop.engine.Build.AvoidReload→bloop.data.WorkspaceSettingsbloop.engine.Build.ForceReload→bloop.data.WorkspaceSettingsbloop.engine.Build.InvalidatedInMemoryProject→bloop.data.Projectbloop.engine.Build.ReadConfiguration→bloop.data.Originbloop.engine.Build.UpdateState→bloop.data.WorkspaceSettings
- Direction
- bloop.engine.Build uses bloop.data, so a change to bloop.data can break bloop.engine.Build, while a change to bloop.engine.Build can't break bloop.data.
- Position
- Below the diagonal: bloop.engine.Build uses a module listed above it, which is the healthy direction.
18→15 bloop.engine.Build uses bloop.io✕
- Connections
- 1 pair of types, where a type in bloop.engine.Build uses a type in bloop.io.
- The types involved
bloop.engine.Build.UpdateState→bloop.io.AbsolutePath
- Direction
- bloop.engine.Build uses bloop.io, so a change to bloop.io can break bloop.engine.Build, while a change to bloop.engine.Build can't break bloop.io.
- Position
- Below the diagonal: bloop.engine.Build uses a module listed above it, which is the healthy direction.
19→3 bloop.engine.tasks.compilation uses bloop.task✕
- Connections
- 5 pairs of types, where a type in bloop.engine.tasks.compilation uses a type in bloop.task.
- The types involved
bloop.engine.tasks.compilation.CompilerPluginAllowlist→bloop.task.Taskbloop.engine.tasks.compilation.PartialCompileResult→bloop.task.Taskbloop.engine.tasks.compilation.PartialEmpty→bloop.task.Taskbloop.engine.tasks.compilation.PartialFailure→bloop.task.Taskbloop.engine.tasks.compilation.PartialSuccess→bloop.task.Task
- Direction
- bloop.engine.tasks.compilation uses bloop.task, so a change to bloop.task can break bloop.engine.tasks.compilation, while a change to bloop.engine.tasks.compilation can't break bloop.task.
- Position
- Below the diagonal: bloop.engine.tasks.compilation uses a module listed above it, which is the healthy direction.
19→7 bloop.engine.tasks.compilation uses bloop.reporter✕
- Connections
- 2 pairs of types, where a type in bloop.engine.tasks.compilation uses a type in bloop.reporter.
- The types involved
bloop.engine.tasks.compilation.SuccessfulCompileBundle→bloop.reporter.ObservedReporterbloop.engine.tasks.compilation.SuccessfulCompileBundle→bloop.reporter.ReporterAction
- Direction
- bloop.engine.tasks.compilation uses bloop.reporter, so a change to bloop.reporter can break bloop.engine.tasks.compilation, while a change to bloop.engine.tasks.compilation can't break bloop.reporter.
- Position
- Below the diagonal: bloop.engine.tasks.compilation uses a module listed above it, which is the healthy direction.
19→9 bloop.engine.tasks.compilation uses bloop.tracing✕
- Connections
- 4 pairs of types, where a type in bloop.engine.tasks.compilation uses a type in bloop.tracing.
- The types involved
bloop.engine.tasks.compilation.CompileGatekeeper→bloop.tracing.BraveTracerbloop.engine.tasks.compilation.CompileGraph→bloop.tracing.BraveTracerbloop.engine.tasks.compilation.CompilerPluginAllowlist→bloop.tracing.BraveTracerbloop.engine.tasks.compilation.SuccessfulCompileBundle→bloop.tracing.BraveTracer
- Direction
- bloop.engine.tasks.compilation uses bloop.tracing, so a change to bloop.tracing can break bloop.engine.tasks.compilation, while a change to bloop.engine.tasks.compilation can't break bloop.tracing.
- Position
- Below the diagonal: bloop.engine.tasks.compilation uses a module listed above it, which is the healthy direction.
19→11 bloop.engine.tasks.compilation uses bloop.logging✕
- Connections
- 6 pairs of types, where a type in bloop.engine.tasks.compilation uses a type in bloop.logging.
- The types involved
bloop.engine.tasks.compilation.CompileGatekeeper→bloop.logging.DebugFilterbloop.engine.tasks.compilation.CompileGatekeeper→bloop.logging.Loggerbloop.engine.tasks.compilation.CompilerPluginAllowlist→bloop.logging.Loggerbloop.engine.tasks.compilation.SuccessfulCompileBundle→bloop.logging.Loggerbloop.engine.tasks.compilation.SuccessfulCompileBundle→bloop.logging.LoggerActionbloop.engine.tasks.compilation.SuccessfulCompileBundle→bloop.logging.ObservedLogger
- Direction
- bloop.engine.tasks.compilation uses bloop.logging, so a change to bloop.logging can break bloop.engine.tasks.compilation, while a change to bloop.engine.tasks.compilation can't break bloop.logging.
- Position
- Below the diagonal: bloop.engine.tasks.compilation uses a module listed above it, which is the healthy direction.
19→12 bloop.engine.tasks.compilation uses bloop.util✕
- Connections
- 3 pairs of types, where a type in bloop.engine.tasks.compilation uses a type in bloop.util.
- The types involved
bloop.engine.tasks.compilation.FinalNormalCompileResult→bloop.util.CacheHashCodebloop.engine.tasks.compilation.PartialFailure→bloop.util.CacheHashCodebloop.engine.tasks.compilation.PartialSuccess→bloop.util.CacheHashCode
- Direction
- bloop.engine.tasks.compilation uses bloop.util, so a change to bloop.util can break bloop.engine.tasks.compilation, while a change to bloop.engine.tasks.compilation can't break bloop.util.
- Position
- Below the diagonal: bloop.engine.tasks.compilation uses a module listed above it, which is the healthy direction.
19→13 bloop.engine.tasks.compilation uses bloop.data✕
- Connections
- 9 pairs of types, where a type in bloop.engine.tasks.compilation uses a type in bloop.data.
- The types involved
bloop.engine.tasks.compilation.CompileClientStore→bloop.data.Projectbloop.engine.tasks.compilation.CompileDependenciesData→bloop.data.Projectbloop.engine.tasks.compilation.CompileGatekeeper→bloop.data.ClientInfobloop.engine.tasks.compilation.CompileGatekeeper→bloop.data.Projectbloop.engine.tasks.compilation.CompileGraph→bloop.data.ClientInfobloop.engine.tasks.compilation.CompileGraph→bloop.data.Projectbloop.engine.tasks.compilation.FinalNormalCompileResult→bloop.data.Projectbloop.engine.tasks.compilation.PartialFailure→bloop.data.Projectbloop.engine.tasks.compilation.SuccessfulCompileBundle→bloop.data.Project
- Direction
- bloop.engine.tasks.compilation uses bloop.data, so a change to bloop.data can break bloop.engine.tasks.compilation, while a change to bloop.engine.tasks.compilation can't break bloop.data.
- Position
- Below the diagonal: bloop.engine.tasks.compilation uses a module listed above it, which is the healthy direction.
19→15 bloop.engine.tasks.compilation uses bloop.io✕
- Connections
- 3 pairs of types, where a type in bloop.engine.tasks.compilation uses a type in bloop.io.
- The types involved
bloop.engine.tasks.compilation.CompileDependenciesData→bloop.io.AbsolutePathbloop.engine.tasks.compilation.CompileSourcesAndInstance→bloop.io.AbsolutePathbloop.engine.tasks.compilation.SuccessfulCompileBundle→bloop.io.AbsolutePath
- Direction
- bloop.engine.tasks.compilation uses bloop.io, so a change to bloop.io can break bloop.engine.tasks.compilation, while a change to bloop.engine.tasks.compilation can't break bloop.io.
- Position
- Below the diagonal: bloop.engine.tasks.compilation uses a module listed above it, which is the healthy direction.
19→24 bloop.engine.tasks.compilation uses bloop.engine.caches part of a loop✕
- Connections
- 3 pairs of types, where a type in bloop.engine.tasks.compilation uses a type in bloop.engine.caches.
- The types involved
bloop.engine.tasks.compilation.CompileGatekeeper→bloop.engine.caches.LastSuccessfulResultbloop.engine.tasks.compilation.ResultBundle→bloop.engine.caches.LastSuccessfulResultbloop.engine.tasks.compilation.SuccessfulCompileBundle→bloop.engine.caches.LastSuccessfulResult
- Direction
- bloop.engine.tasks.compilation uses bloop.engine.caches, so a change to bloop.engine.caches can break bloop.engine.tasks.compilation, while a change to bloop.engine.tasks.compilation can't break bloop.engine.caches.
- 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 bloop.engine.tasks.compilation uses bloop.engine part of a loop✕
- Connections
- 3 pairs of types, where a type in bloop.engine.tasks.compilation uses a type in bloop.engine.
- The types involved
bloop.engine.tasks.compilation.CompileClientStore→bloop.engine.Dagbloop.engine.tasks.compilation.CompileGatekeeper→bloop.engine.Dagbloop.engine.tasks.compilation.CompileGraph→bloop.engine.Dag
- Direction
- bloop.engine.tasks.compilation uses bloop.engine, so a change to bloop.engine can break bloop.engine.tasks.compilation, while a change to bloop.engine.tasks.compilation can't break bloop.engine.
- 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→29 bloop.engine.tasks.compilation uses bloop part of a loop✕
- Connections
- 5 pairs of types, where a type in bloop.engine.tasks.compilation uses a type in bloop.
- The types involved
bloop.engine.tasks.compilation.CompileGatekeeper→bloop.UniqueCompileInputsbloop.engine.tasks.compilation.CompileSourcesAndInstance→bloop.ScalaInstancebloop.engine.tasks.compilation.SuccessfulCompileBundle→bloop.ClientClassesObserverbloop.engine.tasks.compilation.SuccessfulCompileBundle→bloop.CompileOutPathsbloop.engine.tasks.compilation.SuccessfulCompileBundle→bloop.UniqueCompileInputs
- Direction
- bloop.engine.tasks.compilation uses bloop, so a change to bloop can break bloop.engine.tasks.compilation, while a change to bloop.engine.tasks.compilation can't break bloop.
- 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→3 bloop.engine.tasks.toolchains uses bloop.task✕
- Connections
- 2 pairs of types, where a type in bloop.engine.tasks.toolchains uses a type in bloop.task.
- The types involved
bloop.engine.tasks.toolchains.ScalaJsToolchain→bloop.task.Taskbloop.engine.tasks.toolchains.ScalaNativeToolchain→bloop.task.Task
- Direction
- bloop.engine.tasks.toolchains uses bloop.task, so a change to bloop.task can break bloop.engine.tasks.toolchains, while a change to bloop.engine.tasks.toolchains can't break bloop.task.
- Position
- Below the diagonal: bloop.engine.tasks.toolchains uses a module listed above it, which is the healthy direction.
20→11 bloop.engine.tasks.toolchains uses bloop.logging✕
- Connections
- 3 pairs of types, where a type in bloop.engine.tasks.toolchains uses a type in bloop.logging.
- The types involved
bloop.engine.tasks.toolchains.ScalaJsToolchain→bloop.logging.Loggerbloop.engine.tasks.toolchains.ScalaNativeToolchain→bloop.logging.Loggerbloop.engine.tasks.toolchains.ToolchainCompanion→bloop.logging.Logger
- Direction
- bloop.engine.tasks.toolchains uses bloop.logging, so a change to bloop.logging can break bloop.engine.tasks.toolchains, while a change to bloop.engine.tasks.toolchains can't break bloop.logging.
- Position
- Below the diagonal: bloop.engine.tasks.toolchains uses a module listed above it, which is the healthy direction.
20→13 bloop.engine.tasks.toolchains uses bloop.data✕
- Connections
- 2 pairs of types, where a type in bloop.engine.tasks.toolchains uses a type in bloop.data.
- The types involved
bloop.engine.tasks.toolchains.ScalaJsToolchain→bloop.data.Projectbloop.engine.tasks.toolchains.ScalaNativeToolchain→bloop.data.Project
- Direction
- bloop.engine.tasks.toolchains uses bloop.data, so a change to bloop.data can break bloop.engine.tasks.toolchains, while a change to bloop.engine.tasks.toolchains can't break bloop.data.
- Position
- Below the diagonal: bloop.engine.tasks.toolchains uses a module listed above it, which is the healthy direction.
20→15 bloop.engine.tasks.toolchains uses bloop.io✕
- Connections
- 2 pairs of types, where a type in bloop.engine.tasks.toolchains uses a type in bloop.io.
- The types involved
bloop.engine.tasks.toolchains.ScalaJsToolchain→bloop.io.AbsolutePathbloop.engine.tasks.toolchains.ScalaNativeToolchain→bloop.io.AbsolutePath
- Direction
- bloop.engine.tasks.toolchains uses bloop.io, so a change to bloop.io can break bloop.engine.tasks.toolchains, while a change to bloop.engine.tasks.toolchains can't break bloop.io.
- Position
- Below the diagonal: bloop.engine.tasks.toolchains uses a module listed above it, which is the healthy direction.
21→7 bloop.logging.CompilationEvent uses bloop.reporter✕
- Connections
- 2 pairs of types, where a type in bloop.logging.CompilationEvent uses a type in bloop.reporter.
- The types involved
bloop.logging.CompilationEvent.Diagnostic→bloop.reporter.Problembloop.logging.CompilationEvent.EndCompilation→bloop.reporter.Problem
- Direction
- bloop.logging.CompilationEvent uses bloop.reporter, so a change to bloop.reporter can break bloop.logging.CompilationEvent, while a change to bloop.logging.CompilationEvent can't break bloop.reporter.
- Position
- Below the diagonal: bloop.logging.CompilationEvent uses a module listed above it, which is the healthy direction.
21→11 bloop.logging.CompilationEvent uses bloop.logging✕
- Connections
- 5 pairs of types, where a type in bloop.logging.CompilationEvent uses a type in bloop.logging.
- The types involved
bloop.logging.CompilationEvent.Diagnostic→bloop.logging.CompilationEventbloop.logging.CompilationEvent.EndCompilation→bloop.logging.CompilationEventbloop.logging.CompilationEvent.NoDiagnostic→bloop.logging.CompilationEventbloop.logging.CompilationEvent.ProgressCompilation→bloop.logging.CompilationEventbloop.logging.CompilationEvent.StartCompilation→bloop.logging.CompilationEvent
- Direction
- bloop.logging.CompilationEvent uses bloop.logging, so a change to bloop.logging can break bloop.logging.CompilationEvent, while a change to bloop.logging.CompilationEvent can't break bloop.logging.
- Position
- Below the diagonal: bloop.logging.CompilationEvent uses a module listed above it, which is the healthy direction.
21→15 bloop.logging.CompilationEvent uses bloop.io✕
- Connections
- 1 pair of types, where a type in bloop.logging.CompilationEvent uses a type in bloop.io.
- The types involved
bloop.logging.CompilationEvent.EndCompilation→bloop.io.AbsolutePath
- Direction
- bloop.logging.CompilationEvent uses bloop.io, so a change to bloop.io can break bloop.logging.CompilationEvent, while a change to bloop.logging.CompilationEvent can't break bloop.io.
- Position
- Below the diagonal: bloop.logging.CompilationEvent uses a module listed above it, which is the healthy direction.
22→15 buildpress uses bloop.io✕
- Connections
- 4 pairs of types, where a type in buildpress uses a type in bloop.io.
- The types involved
buildpress.Buildpress→bloop.io.AbsolutePathbuildpress.BuildpressParams→bloop.io.AbsolutePathbuildpress.ClonedRepository→bloop.io.AbsolutePathbuildpress.RepositoryCache→bloop.io.AbsolutePath
- Direction
- buildpress uses bloop.io, so a change to bloop.io can break buildpress, while a change to buildpress can't break bloop.io.
- Position
- Below the diagonal: buildpress uses a module listed above it, which is the healthy direction.
23→13 bloop.data.Platform uses bloop.data✕
- Connections
- 4 pairs of types, where a type in bloop.data.Platform uses a type in bloop.data.
- The types involved
bloop.data.Platform.Js→bloop.data.Platformbloop.data.Platform.Jvm→bloop.data.JdkConfigbloop.data.Platform.Jvm→bloop.data.Platformbloop.data.Platform.Native→bloop.data.Platform
- Direction
- bloop.data.Platform uses bloop.data, so a change to bloop.data can break bloop.data.Platform, while a change to bloop.data.Platform can't break bloop.data.
- Position
- Below the diagonal: bloop.data.Platform uses a module listed above it, which is the healthy direction.
23→15 bloop.data.Platform uses bloop.io✕
- Connections
- 1 pair of types, where a type in bloop.data.Platform uses a type in bloop.io.
- The types involved
bloop.data.Platform.Jvm→bloop.io.AbsolutePath
- Direction
- bloop.data.Platform uses bloop.io, so a change to bloop.io can break bloop.data.Platform, while a change to bloop.data.Platform can't break bloop.io.
- Position
- Below the diagonal: bloop.data.Platform uses a module listed above it, which is the healthy direction.
23→20 bloop.data.Platform uses bloop.engine.tasks.toolchains✕
- Connections
- 3 pairs of types, where a type in bloop.data.Platform uses a type in bloop.engine.tasks.toolchains.
- The types involved
bloop.data.Platform.Js→bloop.engine.tasks.toolchains.ScalaJsToolchainbloop.data.Platform.Jvm→bloop.engine.tasks.toolchains.JvmToolchainbloop.data.Platform.Native→bloop.engine.tasks.toolchains.ScalaNativeToolchain
- Direction
- bloop.data.Platform uses bloop.engine.tasks.toolchains, so a change to bloop.engine.tasks.toolchains can break bloop.data.Platform, while a change to bloop.data.Platform can't break bloop.engine.tasks.toolchains.
- Position
- Below the diagonal: bloop.data.Platform uses a module listed above it, which is the healthy direction.
24→1 bloop.engine.caches uses bloop.Compiler✕
- Connections
- 1 pair of types, where a type in bloop.engine.caches uses a type in bloop.Compiler.
- The types involved
bloop.engine.caches.ResultsCache→bloop.Compiler.Result
- Direction
- bloop.engine.caches uses bloop.Compiler, so a change to bloop.Compiler can break bloop.engine.caches, while a change to bloop.engine.caches can't break bloop.Compiler.
- Position
- Below the diagonal: bloop.engine.caches uses a module listed above it, which is the healthy direction.
24→3 bloop.engine.caches uses bloop.task✕
- Connections
- 4 pairs of types, where a type in bloop.engine.caches uses a type in bloop.task.
- The types involved
bloop.engine.caches.LastSuccessfulResult→bloop.task.Taskbloop.engine.caches.ResultsCache→bloop.task.Taskbloop.engine.caches.SourceGeneratorCache→bloop.task.Taskbloop.engine.caches.StateCache→bloop.task.Task
- Direction
- bloop.engine.caches uses bloop.task, so a change to bloop.task can break bloop.engine.caches, while a change to bloop.engine.caches can't break bloop.task.
- Position
- Below the diagonal: bloop.engine.caches uses a module listed above it, which is the healthy direction.
24→11 bloop.engine.caches uses bloop.logging✕
- Connections
- 4 pairs of types, where a type in bloop.engine.caches uses a type in bloop.logging.
- The types involved
bloop.engine.caches.ResultsCache→bloop.logging.Loggerbloop.engine.caches.SemanticDBCache→bloop.logging.Loggerbloop.engine.caches.SourceGeneratorCache→bloop.logging.Loggerbloop.engine.caches.StateCache→bloop.logging.Logger
- Direction
- bloop.engine.caches uses bloop.logging, so a change to bloop.logging can break bloop.engine.caches, while a change to bloop.engine.caches can't break bloop.logging.
- Position
- Below the diagonal: bloop.engine.caches uses a module listed above it, which is the healthy direction.
24→13 bloop.engine.caches uses bloop.data✕
- Connections
- 4 pairs of types, where a type in bloop.engine.caches uses a type in bloop.data.
- The types involved
bloop.engine.caches.ResultsCache→bloop.data.ClientInfobloop.engine.caches.ResultsCache→bloop.data.Projectbloop.engine.caches.StateCache→bloop.data.ClientInfobloop.engine.caches.StateCache→bloop.data.WorkspaceSettings
- Direction
- bloop.engine.caches uses bloop.data, so a change to bloop.data can break bloop.engine.caches, while a change to bloop.engine.caches can't break bloop.data.
- Position
- Below the diagonal: bloop.engine.caches uses a module listed above it, which is the healthy direction.
24→15 bloop.engine.caches uses bloop.io✕
- Connections
- 4 pairs of types, where a type in bloop.engine.caches uses a type in bloop.io.
- The types involved
bloop.engine.caches.LastSuccessfulResult→bloop.io.AbsolutePathbloop.engine.caches.SemanticDBCache→bloop.io.AbsolutePathbloop.engine.caches.SourceGeneratorCache→bloop.io.AbsolutePathbloop.engine.caches.StateCache→bloop.io.AbsolutePath
- Direction
- bloop.engine.caches uses bloop.io, so a change to bloop.io can break bloop.engine.caches, while a change to bloop.engine.caches can't break bloop.io.
- Position
- Below the diagonal: bloop.engine.caches uses a module listed above it, which is the healthy direction.
24→19 bloop.engine.caches uses bloop.engine.tasks.compilation✕
- Connections
- 2 pairs of types, where a type in bloop.engine.caches uses a type in bloop.engine.tasks.compilation.
- The types involved
bloop.engine.caches.ResultsCache→bloop.engine.tasks.compilation.FinalCompileResultbloop.engine.caches.ResultsCache→bloop.engine.tasks.compilation.ResultBundle
- Direction
- bloop.engine.caches uses bloop.engine.tasks.compilation, so a change to bloop.engine.tasks.compilation can break bloop.engine.caches, while a change to bloop.engine.caches can't break bloop.engine.tasks.compilation.
- Position
- Below the diagonal: bloop.engine.caches uses a module listed above it, which is the healthy direction.
24→25 bloop.engine.caches uses bloop.engine part of a loop✕
- Connections
- 4 pairs of types, where a type in bloop.engine.caches uses a type in bloop.engine.
- The types involved
bloop.engine.caches.SourceGeneratorCache→bloop.engine.SourceGeneratorbloop.engine.caches.StateCache→bloop.engine.Buildbloop.engine.caches.StateCache→bloop.engine.ClientPoolbloop.engine.caches.StateCache→bloop.engine.State
- Direction
- bloop.engine.caches uses bloop.engine, so a change to bloop.engine can break bloop.engine.caches, while a change to bloop.engine.caches can't break bloop.engine.
- 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→27 bloop.engine.caches uses bloop.cli part of a loop✕
- Connections
- 2 pairs of types, where a type in bloop.engine.caches uses a type in bloop.cli.
- The types involved
bloop.engine.caches.SourceGeneratorCache→bloop.cli.CommonOptionsbloop.engine.caches.StateCache→bloop.cli.CommonOptions
- Direction
- bloop.engine.caches uses bloop.cli, so a change to bloop.cli can break bloop.engine.caches, while a change to bloop.engine.caches can't break bloop.cli.
- 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→3 bloop.engine uses bloop.task✕
- Connections
- 4 pairs of types, where a type in bloop.engine uses a type in bloop.task.
- The types involved
bloop.engine.Build→bloop.task.Taskbloop.engine.BuildLoader→bloop.task.Taskbloop.engine.Interpreter→bloop.task.Taskbloop.engine.SourceGenerator→bloop.task.Task
- Direction
- bloop.engine uses bloop.task, so a change to bloop.task can break bloop.engine, while a change to bloop.engine can't break bloop.task.
- Position
- Below the diagonal: bloop.engine uses a module listed above it, which is the healthy direction.
25→6 bloop.engine uses bloop.io.Paths✕
- Connections
- 1 pair of types, where a type in bloop.engine uses a type in bloop.io.Paths.
- The types involved
bloop.engine.BuildLoader→bloop.io.Paths.AttributedPath
- Direction
- bloop.engine uses bloop.io.Paths, so a change to bloop.io.Paths can break bloop.engine, while a change to bloop.engine can't break bloop.io.Paths.
- Position
- Below the diagonal: bloop.engine uses a module listed above it, which is the healthy direction.
25→11 bloop.engine uses bloop.logging✕
- Connections
- 4 pairs of types, where a type in bloop.engine uses a type in bloop.logging.
- The types involved
bloop.engine.Build→bloop.logging.Loggerbloop.engine.BuildLoader→bloop.logging.Loggerbloop.engine.SourceGenerator→bloop.logging.Loggerbloop.engine.State→bloop.logging.Logger
- Direction
- bloop.engine uses bloop.logging, so a change to bloop.logging can break bloop.engine, while a change to bloop.engine can't break bloop.logging.
- Position
- Below the diagonal: bloop.engine uses a module listed above it, which is the healthy direction.
25→12 bloop.engine uses bloop.util✕
- Connections
- 4 pairs of types, where a type in bloop.engine uses a type in bloop.util.
- The types involved
bloop.engine.Aggregate→bloop.util.CacheHashCodebloop.engine.Build→bloop.util.CacheHashCodebloop.engine.Leaf→bloop.util.CacheHashCodebloop.engine.Parent→bloop.util.CacheHashCode
- Direction
- bloop.engine uses bloop.util, so a change to bloop.util can break bloop.engine, while a change to bloop.engine can't break bloop.util.
- Position
- Below the diagonal: bloop.engine uses a module listed above it, which is the healthy direction.
25→13 bloop.engine uses bloop.data✕
- Connections
- 13 pairs of types, where a type in bloop.engine uses a type in bloop.data.
- The types involved
bloop.engine.Build→bloop.data.LoadedProjectbloop.engine.Build→bloop.data.Projectbloop.engine.Build→bloop.data.WorkspaceSettingsbloop.engine.BuildLoader→bloop.data.JavaSemanticdbSettingsbloop.engine.BuildLoader→bloop.data.LoadedProjectbloop.engine.BuildLoader→bloop.data.Originbloop.engine.BuildLoader→bloop.data.Projectbloop.engine.BuildLoader→bloop.data.ScalaSemanticdbSettingsbloop.engine.BuildLoader→bloop.data.WorkspaceSettingsbloop.engine.Feedback→bloop.data.Projectbloop.engine.Interpreter→bloop.data.Projectbloop.engine.SourceGenerator→bloop.data.SourcesGlobsbloop.engine.State→bloop.data.ClientInfo
- Direction
- bloop.engine uses bloop.data, so a change to bloop.data can break bloop.engine, while a change to bloop.engine can't break bloop.data.
- Position
- Below the diagonal: bloop.engine uses a module listed above it, which is the healthy direction.
25→14 bloop.engine uses bloop.engine.Dag✕
- Connections
- 1 pair of types, where a type in bloop.engine uses a type in bloop.engine.Dag.
- The types involved
bloop.engine.Feedback→bloop.engine.Dag.RecursiveTrace
- Direction
- bloop.engine uses bloop.engine.Dag, so a change to bloop.engine.Dag can break bloop.engine, while a change to bloop.engine can't break bloop.engine.Dag.
- Position
- Below the diagonal: bloop.engine uses a module listed above it, which is the healthy direction.
25→15 bloop.engine uses bloop.io✕
- Connections
- 4 pairs of types, where a type in bloop.engine uses a type in bloop.io.
- The types involved
bloop.engine.Build→bloop.io.AbsolutePathbloop.engine.BuildLoader→bloop.io.AbsolutePathbloop.engine.Feedback→bloop.io.AbsolutePathbloop.engine.SourceGenerator→bloop.io.AbsolutePath
- Direction
- bloop.engine uses bloop.io, so a change to bloop.io can break bloop.engine, while a change to bloop.engine can't break bloop.io.
- Position
- Below the diagonal: bloop.engine uses a module listed above it, which is the healthy direction.
25→17 bloop.engine uses bloop.cli.Commands✕
- Connections
- 1 pair of types, where a type in bloop.engine uses a type in bloop.cli.Commands.
- The types involved
bloop.engine.Interpreter→bloop.cli.Commands.CompilingCommand
- Direction
- bloop.engine uses bloop.cli.Commands, so a change to bloop.cli.Commands can break bloop.engine, while a change to bloop.engine can't break bloop.cli.Commands.
- Position
- Below the diagonal: bloop.engine uses a module listed above it, which is the healthy direction.
25→24 bloop.engine uses bloop.engine.caches✕
- Connections
- 2 pairs of types, where a type in bloop.engine uses a type in bloop.engine.caches.
- The types involved
bloop.engine.State→bloop.engine.caches.ResultsCachebloop.engine.State→bloop.engine.caches.SourceGeneratorCache
- Direction
- bloop.engine uses bloop.engine.caches, so a change to bloop.engine.caches can break bloop.engine, while a change to bloop.engine can't break bloop.engine.caches.
- Position
- Below the diagonal: bloop.engine uses a module listed above it, which is the healthy direction.
25→27 bloop.engine uses bloop.cli part of a loop✕
- Connections
- 7 pairs of types, where a type in bloop.engine uses a type in bloop.cli.
- The types involved
bloop.engine.Exit→bloop.cli.ExitStatusbloop.engine.Interpreter→bloop.cli.CliOptionsbloop.engine.Interpreter→bloop.cli.Loggerbloop.engine.Print→bloop.cli.CommonOptionsbloop.engine.SourceGenerator→bloop.cli.CommonOptionsbloop.engine.State→bloop.cli.CommonOptionsbloop.engine.State→bloop.cli.ExitStatus
- Direction
- bloop.engine uses bloop.cli, so a change to bloop.cli can break bloop.engine, while a change to bloop.engine can't break bloop.cli.
- 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→29 bloop.engine uses bloop part of a loop✕
- Connections
- 1 pair of types, where a type in bloop.engine uses a type in bloop.
- The types involved
bloop.engine.State→bloop.CompilerCache
- Direction
- bloop.engine uses bloop, so a change to bloop can break bloop.engine, while a change to bloop.engine can't break bloop.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→7 bloop.engine.tasks.compilation.CompileGatekeeper uses bloop.reporter✕
- Connections
- 1 pair of types, where a type in bloop.engine.tasks.compilation.CompileGatekeeper uses a type in bloop.reporter.
- The types involved
bloop.engine.tasks.compilation.CompileGatekeeper.RunningCompilation→bloop.reporter.ReporterAction
- Direction
- bloop.engine.tasks.compilation.CompileGatekeeper uses bloop.reporter, so a change to bloop.reporter can break bloop.engine.tasks.compilation.CompileGatekeeper, while a change to bloop.engine.tasks.compilation.CompileGatekeeper can't break bloop.reporter.
- Position
- Below the diagonal: bloop.engine.tasks.compilation.CompileGatekeeper uses a module listed above it, which is the healthy direction.
26→11 bloop.engine.tasks.compilation.CompileGatekeeper uses bloop.logging✕
- Connections
- 1 pair of types, where a type in bloop.engine.tasks.compilation.CompileGatekeeper uses a type in bloop.logging.
- The types involved
bloop.engine.tasks.compilation.CompileGatekeeper.RunningCompilation→bloop.logging.LoggerAction
- Direction
- bloop.engine.tasks.compilation.CompileGatekeeper uses bloop.logging, so a change to bloop.logging can break bloop.engine.tasks.compilation.CompileGatekeeper, while a change to bloop.engine.tasks.compilation.CompileGatekeeper can't break bloop.logging.
- Position
- Below the diagonal: bloop.engine.tasks.compilation.CompileGatekeeper uses a module listed above it, which is the healthy direction.
26→13 bloop.engine.tasks.compilation.CompileGatekeeper uses bloop.data✕
- Connections
- 1 pair of types, where a type in bloop.engine.tasks.compilation.CompileGatekeeper uses a type in bloop.data.
- The types involved
bloop.engine.tasks.compilation.CompileGatekeeper.RunningCompilation→bloop.data.ClientInfo
- Direction
- bloop.engine.tasks.compilation.CompileGatekeeper uses bloop.data, so a change to bloop.data can break bloop.engine.tasks.compilation.CompileGatekeeper, while a change to bloop.engine.tasks.compilation.CompileGatekeeper can't break bloop.data.
- Position
- Below the diagonal: bloop.engine.tasks.compilation.CompileGatekeeper uses a module listed above it, which is the healthy direction.
26→24 bloop.engine.tasks.compilation.CompileGatekeeper uses bloop.engine.caches✕
- Connections
- 1 pair of types, where a type in bloop.engine.tasks.compilation.CompileGatekeeper uses a type in bloop.engine.caches.
- The types involved
bloop.engine.tasks.compilation.CompileGatekeeper.RunningCompilation→bloop.engine.caches.LastSuccessfulResult
- Direction
- bloop.engine.tasks.compilation.CompileGatekeeper uses bloop.engine.caches, so a change to bloop.engine.caches can break bloop.engine.tasks.compilation.CompileGatekeeper, while a change to bloop.engine.tasks.compilation.CompileGatekeeper can't break bloop.engine.caches.
- Position
- Below the diagonal: bloop.engine.tasks.compilation.CompileGatekeeper uses a module listed above it, which is the healthy direction.
27→2 bloop.cli uses bloop.rifle✕
- Connections
- 2 pairs of types, where a type in bloop.cli uses a type in bloop.rifle.
- The types involved
bloop.cli.Exit→bloop.rifle.BloopRifleConfigbloop.cli.Logger→bloop.rifle.BloopRifleLogger
- Direction
- bloop.cli uses bloop.rifle, so a change to bloop.rifle can break bloop.cli, while a change to bloop.cli can't break bloop.rifle.
- Position
- Below the diagonal: bloop.cli uses a module listed above it, which is the healthy direction.
27→3 bloop.cli uses bloop.task✕
- Connections
- 1 pair of types, where a type in bloop.cli uses a type in bloop.task.
- The types involved
bloop.cli.Validate→bloop.task.Task
- Direction
- bloop.cli uses bloop.task, so a change to bloop.task can break bloop.cli, while a change to bloop.cli can't break bloop.task.
- Position
- Below the diagonal: bloop.cli uses a module listed above it, which is the healthy direction.
27→4 bloop.cli uses bloop.cli.options✕
- Connections
- 5 pairs of types, where a type in bloop.cli uses a type in bloop.cli.options.
- The types involved
bloop.cli.Default→bloop.cli.options.DefaultOptionsbloop.cli.Exit→bloop.cli.options.ExitOptionsbloop.cli.Output→bloop.cli.options.OutputOptionsbloop.cli.Start→bloop.cli.options.StartOptionsbloop.cli.Status→bloop.cli.options.StatusOptions
- Direction
- bloop.cli uses bloop.cli.options, so a change to bloop.cli.options can break bloop.cli, while a change to bloop.cli can't break bloop.cli.options.
- Position
- Below the diagonal: bloop.cli uses a module listed above it, which is the healthy direction.
27→11 bloop.cli uses bloop.logging✕
- Connections
- 2 pairs of types, where a type in bloop.cli uses a type in bloop.logging.
- The types involved
bloop.cli.CliOptions→bloop.logging.DebugFilterbloop.cli.CliParsers→bloop.logging.DebugFilter
- Direction
- bloop.cli uses bloop.logging, so a change to bloop.logging can break bloop.cli, while a change to bloop.cli can't break bloop.logging.
- Position
- Below the diagonal: bloop.cli uses a module listed above it, which is the healthy direction.
27→15 bloop.cli uses bloop.io✕
- Connections
- 1 pair of types, where a type in bloop.cli uses a type in bloop.io.
- The types involved
bloop.cli.CommonOptions→bloop.io.AbsolutePath
- Direction
- bloop.cli uses bloop.io, so a change to bloop.io can break bloop.cli, while a change to bloop.cli can't break bloop.io.
- Position
- Below the diagonal: bloop.cli uses a module listed above it, which is the healthy direction.
27→25 bloop.cli uses bloop.engine✕
- Connections
- 2 pairs of types, where a type in bloop.cli uses a type in bloop.engine.
- The types involved
bloop.cli.Validate→bloop.engine.Actionbloop.cli.Validate→bloop.engine.State
- Direction
- bloop.cli uses bloop.engine, so a change to bloop.engine can break bloop.cli, while a change to bloop.cli can't break bloop.engine.
- Position
- Below the diagonal: bloop.cli uses a module listed above it, which is the healthy direction.
28→13 bloop.engine.tasks.compilation.CompileClientStore uses bloop.data✕
- Connections
- 2 pairs of types, where a type in bloop.engine.tasks.compilation.CompileClientStore uses a type in bloop.data.
- The types involved
bloop.engine.tasks.compilation.CompileClientStore.ConcurrentStore→bloop.data.Projectbloop.engine.tasks.compilation.CompileClientStore.NoStore→bloop.data.Project
- Direction
- bloop.engine.tasks.compilation.CompileClientStore uses bloop.data, so a change to bloop.data can break bloop.engine.tasks.compilation.CompileClientStore, while a change to bloop.engine.tasks.compilation.CompileClientStore can't break bloop.data.
- Position
- Below the diagonal: bloop.engine.tasks.compilation.CompileClientStore uses a module listed above it, which is the healthy direction.
28→19 bloop.engine.tasks.compilation.CompileClientStore uses bloop.engine.tasks.compilation✕
- Connections
- 2 pairs of types, where a type in bloop.engine.tasks.compilation.CompileClientStore uses a type in bloop.engine.tasks.compilation.
- The types involved
bloop.engine.tasks.compilation.CompileClientStore.ConcurrentStore→bloop.engine.tasks.compilation.CompileClientStorebloop.engine.tasks.compilation.CompileClientStore.NoStore→bloop.engine.tasks.compilation.CompileClientStore
- Direction
- bloop.engine.tasks.compilation.CompileClientStore uses bloop.engine.tasks.compilation, so a change to bloop.engine.tasks.compilation can break bloop.engine.tasks.compilation.CompileClientStore, while a change to bloop.engine.tasks.compilation.CompileClientStore can't break bloop.engine.tasks.compilation.
- Position
- Below the diagonal: bloop.engine.tasks.compilation.CompileClientStore uses a module listed above it, which is the healthy direction.
28→25 bloop.engine.tasks.compilation.CompileClientStore uses bloop.engine✕
- Connections
- 2 pairs of types, where a type in bloop.engine.tasks.compilation.CompileClientStore uses a type in bloop.engine.
- The types involved
bloop.engine.tasks.compilation.CompileClientStore.ConcurrentStore→bloop.engine.Dagbloop.engine.tasks.compilation.CompileClientStore.NoStore→bloop.engine.Dag
- Direction
- bloop.engine.tasks.compilation.CompileClientStore uses bloop.engine, so a change to bloop.engine can break bloop.engine.tasks.compilation.CompileClientStore, while a change to bloop.engine.tasks.compilation.CompileClientStore can't break bloop.engine.
- Position
- Below the diagonal: bloop.engine.tasks.compilation.CompileClientStore uses a module listed above it, which is the healthy direction.
29→3 bloop uses bloop.task✕
- Connections
- 3 pairs of types, where a type in bloop uses a type in bloop.task.
- The types involved
bloop.ClientClassesObserver→bloop.task.Taskbloop.CompileBackgroundTasks→bloop.task.Taskbloop.Compiler→bloop.task.Task
- Direction
- bloop uses bloop.task, so a change to bloop.task can break bloop, while a change to bloop can't break bloop.task.
- Position
- Below the diagonal: bloop uses a module listed above it, which is the healthy direction.
29→7 bloop uses bloop.reporter✕
- Connections
- 4 pairs of types, where a type in bloop uses a type in bloop.reporter.
- The types involved
bloop.CompileBackgroundTasks→bloop.reporter.Reporterbloop.CompileInputs→bloop.reporter.ZincReporterbloop.Compiler→bloop.reporter.ProblemPerPhasebloop.Compiler→bloop.reporter.ZincReporter
- Direction
- bloop uses bloop.reporter, so a change to bloop.reporter can break bloop, while a change to bloop can't break bloop.reporter.
- Position
- Below the diagonal: bloop uses a module listed above it, which is the healthy direction.
29→9 bloop uses bloop.tracing✕
- Connections
- 3 pairs of types, where a type in bloop uses a type in bloop.tracing.
- The types involved
bloop.CompileBackgroundTasks→bloop.tracing.BraveTracerbloop.CompileInputs→bloop.tracing.BraveTracerbloop.Compiler→bloop.tracing.BraveTracer
- Direction
- bloop uses bloop.tracing, so a change to bloop.tracing can break bloop, while a change to bloop can't break bloop.tracing.
- Position
- Below the diagonal: bloop uses a module listed above it, which is the healthy direction.
29→11 bloop uses bloop.logging✕
- Connections
- 5 pairs of types, where a type in bloop uses a type in bloop.logging.
- The types involved
bloop.CompileBackgroundTasks→bloop.logging.Loggerbloop.CompileInputs→bloop.logging.Loggerbloop.CompileInputs→bloop.logging.ObservedLoggerbloop.Compiler→bloop.logging.Loggerbloop.DependencyResolution→bloop.logging.Logger
- Direction
- bloop uses bloop.logging, so a change to bloop.logging can break bloop, while a change to bloop can't break bloop.logging.
- Position
- Below the diagonal: bloop uses a module listed above it, which is the healthy direction.
29→12 bloop uses bloop.util✕
- Connections
- 2 pairs of types, where a type in bloop uses a type in bloop.util.
- The types involved
bloop.UniqueCompileInputs→bloop.util.CacheHashCodebloop.UniqueCompileInputs→bloop.util.HashedSource
- Direction
- bloop uses bloop.util, so a change to bloop.util can break bloop, while a change to bloop can't break bloop.util.
- Position
- Below the diagonal: bloop uses a module listed above it, which is the healthy direction.
29→13 bloop uses bloop.data✕
- Connections
- 1 pair of types, where a type in bloop uses a type in bloop.data.
- The types involved
bloop.reporter→bloop.data.Project
- Direction
- bloop uses bloop.data, so a change to bloop.data can break bloop, while a change to bloop can't break bloop.data.
- Position
- Below the diagonal: bloop uses a module listed above it, which is the healthy direction.
29→15 bloop uses bloop.io✕
- Connections
- 6 pairs of types, where a type in bloop uses a type in bloop.io.
- The types involved
bloop.ClientClassesObserver→bloop.io.AbsolutePathbloop.CompileInputs→bloop.io.AbsolutePathbloop.CompileOutPaths→bloop.io.AbsolutePathbloop.Compiler→bloop.io.AbsolutePathbloop.DependencyResolution→bloop.io.AbsolutePathbloop.PartialCompileProducts→bloop.io.AbsolutePath
- Direction
- bloop uses bloop.io, so a change to bloop.io can break bloop, while a change to bloop can't break bloop.io.
- Position
- Below the diagonal: bloop uses a module listed above it, which is the healthy direction.
29→25 bloop uses bloop.engine✕
- Connections
- 1 pair of types, where a type in bloop uses a type in bloop.engine.
- The types involved
bloop.Bloop→bloop.engine.State
- Direction
- bloop uses bloop.engine, so a change to bloop.engine can break bloop, while a change to bloop can't break bloop.engine.
- Position
- Below the diagonal: bloop uses a module listed above it, which is the healthy direction.
29→27 bloop uses bloop.cli✕
- Connections
- 1 pair of types, where a type in bloop uses a type in bloop.cli.
- The types involved
bloop.Bloop→bloop.cli.CliOptions
- Direction
- bloop uses bloop.cli, so a change to bloop.cli can break bloop, while a change to bloop can't break bloop.cli.
- Position
- Below the diagonal: bloop uses a module listed above it, which is the healthy direction.
30→3 bloop.Cli uses bloop.task✕
- Connections
- 1 pair of types, where a type in bloop.Cli uses a type in bloop.task.
- The types involved
bloop.Cli.CliSession→bloop.task.Task
- Direction
- bloop.Cli uses bloop.task, so a change to bloop.task can break bloop.Cli, while a change to bloop.Cli can't break bloop.task.
- Position
- Below the diagonal: bloop.Cli uses a module listed above it, which is the healthy direction.
30→5 bloop.Cli uses bloop.data.ClientInfo✕
- Connections
- 1 pair of types, where a type in bloop.Cli uses a type in bloop.data.ClientInfo.
- The types involved
bloop.Cli.CliSession→bloop.data.ClientInfo.CliClientInfo
- Direction
- bloop.Cli uses bloop.data.ClientInfo, so a change to bloop.data.ClientInfo can break bloop.Cli, while a change to bloop.Cli can't break bloop.data.ClientInfo.
- Position
- Below the diagonal: bloop.Cli uses a module listed above it, which is the healthy direction.
30→27 bloop.Cli uses bloop.cli✕
- Connections
- 1 pair of types, where a type in bloop.Cli uses a type in bloop.cli.
- The types involved
bloop.Cli.CliSession→bloop.cli.ExitStatus
- Direction
- bloop.Cli uses bloop.cli, so a change to bloop.cli can break bloop.Cli, while a change to bloop.Cli can't break bloop.cli.
- Position
- Below the diagonal: bloop.Cli uses a module listed above it, which is the healthy direction.
31→13 bloop.cli.completion uses bloop.data✕
- Connections
- 4 pairs of types, where a type in bloop.cli.completion uses a type in bloop.data.
- The types involved
bloop.cli.completion.BashFormat→bloop.data.Projectbloop.cli.completion.FishFormat→bloop.data.Projectbloop.cli.completion.Format→bloop.data.Projectbloop.cli.completion.ZshFormat→bloop.data.Project
- Direction
- bloop.cli.completion uses bloop.data, so a change to bloop.data can break bloop.cli.completion, while a change to bloop.cli.completion can't break bloop.data.
- Position
- Below the diagonal: bloop.cli.completion uses a module listed above it, which is the healthy direction.
31→27 bloop.cli.completion uses bloop.cli✕
- Connections
- 8 pairs of types, where a type in bloop.cli.completion uses a type in bloop.cli.
- The types involved
bloop.cli.completion.BashFormat→bloop.cli.BspProtocolbloop.cli.completion.BashFormat→bloop.cli.ReporterKindbloop.cli.completion.FishFormat→bloop.cli.BspProtocolbloop.cli.completion.FishFormat→bloop.cli.ReporterKindbloop.cli.completion.Format→bloop.cli.BspProtocolbloop.cli.completion.Format→bloop.cli.ReporterKindbloop.cli.completion.ZshFormat→bloop.cli.BspProtocolbloop.cli.completion.ZshFormat→bloop.cli.ReporterKind
- Direction
- bloop.cli.completion uses bloop.cli, so a change to bloop.cli can break bloop.cli.completion, while a change to bloop.cli.completion can't break bloop.cli.
- Position
- Below the diagonal: bloop.cli.completion uses a module listed above it, which is the healthy direction.
32→3 bloop.dap uses bloop.task✕
- Connections
- 4 pairs of types, where a type in bloop.dap uses a type in bloop.task.
- The types involved
bloop.dap.AttachRemoteDebugAdapter→bloop.task.Taskbloop.dap.BloopDebuggee→bloop.task.Taskbloop.dap.MainClassDebugAdapter→bloop.task.Taskbloop.dap.TestSuiteDebugAdapter→bloop.task.Task
- Direction
- bloop.dap uses bloop.task, so a change to bloop.task can break bloop.dap, while a change to bloop.dap can't break bloop.task.
- Position
- Below the diagonal: bloop.dap uses a module listed above it, which is the healthy direction.
32→13 bloop.dap uses bloop.data✕
- Connections
- 2 pairs of types, where a type in bloop.dap uses a type in bloop.data.
- The types involved
bloop.dap.BloopDebuggeeRunner→bloop.data.ClientInfobloop.dap.BloopDebuggeeRunner→bloop.data.Project
- Direction
- bloop.dap uses bloop.data, so a change to bloop.data can break bloop.dap, while a change to bloop.dap can't break bloop.data.
- Position
- Below the diagonal: bloop.dap uses a module listed above it, which is the healthy direction.
32→15 bloop.dap uses bloop.io✕
- Connections
- 2 pairs of types, where a type in bloop.dap uses a type in bloop.io.
- The types involved
bloop.dap.BloopDebugToolsResolver→bloop.io.AbsolutePathbloop.dap.BloopDebuggeeRunner→bloop.io.AbsolutePath
- Direction
- bloop.dap uses bloop.io, so a change to bloop.io can break bloop.dap, while a change to bloop.dap can't break bloop.io.
- Position
- Below the diagonal: bloop.dap uses a module listed above it, which is the healthy direction.
32→25 bloop.dap uses bloop.engine✕
- Connections
- 5 pairs of types, where a type in bloop.dap uses a type in bloop.engine.
- The types involved
bloop.dap.AttachRemoteDebugAdapter→bloop.engine.Statebloop.dap.BloopDebuggee→bloop.engine.Statebloop.dap.BloopDebuggeeRunner→bloop.engine.Statebloop.dap.MainClassDebugAdapter→bloop.engine.Statebloop.dap.TestSuiteDebugAdapter→bloop.engine.State
- Direction
- bloop.dap uses bloop.engine, so a change to bloop.engine can break bloop.dap, while a change to bloop.dap can't break bloop.engine.
- Position
- Below the diagonal: bloop.dap uses a module listed above it, which is the healthy direction.
32→27 bloop.dap uses bloop.cli✕
- Connections
- 4 pairs of types, where a type in bloop.dap uses a type in bloop.cli.
- The types involved
bloop.dap.AttachRemoteDebugAdapter→bloop.cli.ExitStatusbloop.dap.BloopDebuggee→bloop.cli.ExitStatusbloop.dap.MainClassDebugAdapter→bloop.cli.ExitStatusbloop.dap.TestSuiteDebugAdapter→bloop.cli.ExitStatus
- Direction
- bloop.dap uses bloop.cli, so a change to bloop.cli can break bloop.dap, while a change to bloop.dap can't break bloop.cli.
- Position
- Below the diagonal: bloop.dap uses a module listed above it, which is the healthy direction.
33→11 bloop.engine.State uses bloop.logging✕
- Connections
- 1 pair of types, where a type in bloop.engine.State uses a type in bloop.logging.
- The types involved
bloop.engine.State.XState→bloop.logging.DebugFilter
- Direction
- bloop.engine.State uses bloop.logging, so a change to bloop.logging can break bloop.engine.State, while a change to bloop.engine.State can't break bloop.logging.
- Position
- Below the diagonal: bloop.engine.State uses a module listed above it, which is the healthy direction.
33→25 bloop.engine.State uses bloop.engine✕
- Connections
- 1 pair of types, where a type in bloop.engine.State uses a type in bloop.engine.
- The types involved
bloop.engine.State.XState→bloop.engine.State
- Direction
- bloop.engine.State uses bloop.engine, so a change to bloop.engine can break bloop.engine.State, while a change to bloop.engine.State can't break bloop.engine.
- Position
- Below the diagonal: bloop.engine.State uses a module listed above it, which is the healthy direction.
33→27 bloop.engine.State uses bloop.cli✕
- Connections
- 1 pair of types, where a type in bloop.engine.State uses a type in bloop.cli.
- The types involved
bloop.engine.State.XState→bloop.cli.ExitStatus
- Direction
- bloop.engine.State uses bloop.cli, so a change to bloop.cli can break bloop.engine.State, while a change to bloop.engine.State can't break bloop.cli.
- Position
- Below the diagonal: bloop.engine.State uses a module listed above it, which is the healthy direction.
34→3 bloop.exec uses bloop.task✕
- Connections
- 4 pairs of types, where a type in bloop.exec uses a type in bloop.task.
- The types involved
bloop.exec.Forker→bloop.task.Taskbloop.exec.JvmDebuggingForker→bloop.task.Taskbloop.exec.JvmForker→bloop.task.Taskbloop.exec.JvmProcessForker→bloop.task.Task
- Direction
- bloop.exec uses bloop.task, so a change to bloop.task can break bloop.exec, while a change to bloop.exec can't break bloop.task.
- Position
- Below the diagonal: bloop.exec uses a module listed above it, which is the healthy direction.
34→11 bloop.exec uses bloop.logging✕
- Connections
- 5 pairs of types, where a type in bloop.exec uses a type in bloop.logging.
- The types involved
bloop.exec.Forker→bloop.logging.DebugFilterbloop.exec.Forker→bloop.logging.Loggerbloop.exec.JvmDebuggingForker→bloop.logging.Loggerbloop.exec.JvmForker→bloop.logging.Loggerbloop.exec.JvmProcessForker→bloop.logging.Logger
- Direction
- bloop.exec uses bloop.logging, so a change to bloop.logging can break bloop.exec, while a change to bloop.exec can't break bloop.logging.
- Position
- Below the diagonal: bloop.exec uses a module listed above it, which is the healthy direction.
34→15 bloop.exec uses bloop.io✕
- Connections
- 4 pairs of types, where a type in bloop.exec uses a type in bloop.io.
- The types involved
bloop.exec.Forker→bloop.io.AbsolutePathbloop.exec.JvmDebuggingForker→bloop.io.AbsolutePathbloop.exec.JvmForker→bloop.io.AbsolutePathbloop.exec.JvmProcessForker→bloop.io.AbsolutePath
- Direction
- bloop.exec uses bloop.io, so a change to bloop.io can break bloop.exec, while a change to bloop.exec can't break bloop.io.
- Position
- Below the diagonal: bloop.exec uses a module listed above it, which is the healthy direction.
34→27 bloop.exec uses bloop.cli✕
- Connections
- 5 pairs of types, where a type in bloop.exec uses a type in bloop.cli.
- The types involved
bloop.exec.Forker→bloop.cli.CommonOptionsbloop.exec.Forker→bloop.cli.ExitStatusbloop.exec.JvmDebuggingForker→bloop.cli.CommonOptionsbloop.exec.JvmForker→bloop.cli.CommonOptionsbloop.exec.JvmProcessForker→bloop.cli.CommonOptions
- Direction
- bloop.exec uses bloop.cli, so a change to bloop.cli can break bloop.exec, while a change to bloop.exec can't break bloop.cli.
- Position
- Below the diagonal: bloop.exec uses a module listed above it, which is the healthy direction.
35→1 bloop.Compiler.Result uses bloop.Compiler✕
- Connections
- 8 pairs of types, where a type in bloop.Compiler.Result uses a type in bloop.Compiler.
- The types involved
bloop.Compiler.Result.Blocked→bloop.Compiler.Resultbloop.Compiler.Result.Cancelled→bloop.Compiler.Resultbloop.Compiler.Result.Empty→bloop.Compiler.Resultbloop.Compiler.Result.Failed→bloop.Compiler.Resultbloop.Compiler.Result.GlobalError→bloop.Compiler.Resultbloop.Compiler.Result.NotOk→bloop.Compiler.Resultbloop.Compiler.Result.Ok→bloop.Compiler.Resultbloop.Compiler.Result.Success→bloop.Compiler.Result
- Direction
- bloop.Compiler.Result uses bloop.Compiler, so a change to bloop.Compiler can break bloop.Compiler.Result, while a change to bloop.Compiler.Result can't break bloop.Compiler.
- Position
- Below the diagonal: bloop.Compiler.Result uses a module listed above it, which is the healthy direction.
35→7 bloop.Compiler.Result uses bloop.reporter✕
- Connections
- 3 pairs of types, where a type in bloop.Compiler.Result uses a type in bloop.reporter.
- The types involved
bloop.Compiler.Result.Cancelled→bloop.reporter.ProblemPerPhasebloop.Compiler.Result.Failed→bloop.reporter.ProblemPerPhasebloop.Compiler.Result.Success→bloop.reporter.ZincReporter
- Direction
- bloop.Compiler.Result uses bloop.reporter, so a change to bloop.reporter can break bloop.Compiler.Result, while a change to bloop.Compiler.Result can't break bloop.reporter.
- Position
- Below the diagonal: bloop.Compiler.Result uses a module listed above it, which is the healthy direction.
35→12 bloop.Compiler.Result uses bloop.util✕
- Connections
- 6 pairs of types, where a type in bloop.Compiler.Result uses a type in bloop.util.
- The types involved
bloop.Compiler.Result.Blocked→bloop.util.CacheHashCodebloop.Compiler.Result.Cancelled→bloop.util.CacheHashCodebloop.Compiler.Result.Empty→bloop.util.CacheHashCodebloop.Compiler.Result.Failed→bloop.util.CacheHashCodebloop.Compiler.Result.GlobalError→bloop.util.CacheHashCodebloop.Compiler.Result.Success→bloop.util.CacheHashCode
- Direction
- bloop.Compiler.Result uses bloop.util, so a change to bloop.util can break bloop.Compiler.Result, while a change to bloop.Compiler.Result can't break bloop.util.
- Position
- Below the diagonal: bloop.Compiler.Result uses a module listed above it, which is the healthy direction.
35→29 bloop.Compiler.Result uses bloop✕
- Connections
- 4 pairs of types, where a type in bloop.Compiler.Result uses a type in bloop.
- The types involved
bloop.Compiler.Result.Cancelled→bloop.CompileBackgroundTasksbloop.Compiler.Result.Failed→bloop.CompileBackgroundTasksbloop.Compiler.Result.Success→bloop.CompileBackgroundTasksbloop.Compiler.Result.Success→bloop.CompileProducts
- Direction
- bloop.Compiler.Result uses bloop, so a change to bloop can break bloop.Compiler.Result, while a change to bloop.Compiler.Result can't break bloop.
- Position
- Below the diagonal: bloop.Compiler.Result uses a module listed above it, which is the healthy direction.
36→24 bloop.engine.caches.StateCache uses bloop.engine.caches✕
- Connections
- 2 pairs of types, where a type in bloop.engine.caches.StateCache uses a type in bloop.engine.caches.
- The types involved
bloop.engine.caches.StateCache.CachedState→bloop.engine.caches.ResultsCachebloop.engine.caches.StateCache.CachedState→bloop.engine.caches.SourceGeneratorCache
- Direction
- bloop.engine.caches.StateCache uses bloop.engine.caches, so a change to bloop.engine.caches can break bloop.engine.caches.StateCache, while a change to bloop.engine.caches.StateCache can't break bloop.engine.caches.
- Position
- Below the diagonal: bloop.engine.caches.StateCache uses a module listed above it, which is the healthy direction.
36→25 bloop.engine.caches.StateCache uses bloop.engine✕
- Connections
- 1 pair of types, where a type in bloop.engine.caches.StateCache uses a type in bloop.engine.
- The types involved
bloop.engine.caches.StateCache.CachedState→bloop.engine.Build
- Direction
- bloop.engine.caches.StateCache uses bloop.engine, so a change to bloop.engine can break bloop.engine.caches.StateCache, while a change to bloop.engine.caches.StateCache can't break bloop.engine.
- Position
- Below the diagonal: bloop.engine.caches.StateCache uses a module listed above it, which is the healthy direction.
36→29 bloop.engine.caches.StateCache uses bloop✕
- Connections
- 1 pair of types, where a type in bloop.engine.caches.StateCache uses a type in bloop.
- The types involved
bloop.engine.caches.StateCache.CachedState→bloop.CompilerCache
- Direction
- bloop.engine.caches.StateCache uses bloop, so a change to bloop can break bloop.engine.caches.StateCache, while a change to bloop.engine.caches.StateCache can't break bloop.
- Position
- Below the diagonal: bloop.engine.caches.StateCache uses a module listed above it, which is the healthy direction.
37→3 bloop.testing uses bloop.task✕
- Connections
- 1 pair of types, where a type in bloop.testing uses a type in bloop.task.
- The types involved
bloop.testing.TestInternals→bloop.task.Task
- Direction
- bloop.testing uses bloop.task, so a change to bloop.task can break bloop.testing, while a change to bloop.testing can't break bloop.task.
- Position
- Below the diagonal: bloop.testing uses a module listed above it, which is the healthy direction.
37→11 bloop.testing uses bloop.logging✕
- Connections
- 6 pairs of types, where a type in bloop.testing uses a type in bloop.logging.
- The types involved
bloop.testing.JUnit5FrameworkDependency→bloop.logging.Loggerbloop.testing.LoggingEventHandler→bloop.logging.Loggerbloop.testing.TestInternals→bloop.logging.DebugFilterbloop.testing.TestInternals→bloop.logging.Loggerbloop.testing.TestNGFrameworkDependency→bloop.logging.Loggerbloop.testing.TestServer→bloop.logging.DebugFilter
- Direction
- bloop.testing uses bloop.logging, so a change to bloop.logging can break bloop.testing, while a change to bloop.testing can't break bloop.logging.
- Position
- Below the diagonal: bloop.testing uses a module listed above it, which is the healthy direction.
37→15 bloop.testing uses bloop.io✕
- Connections
- 3 pairs of types, where a type in bloop.testing uses a type in bloop.io.
- The types involved
bloop.testing.JUnit5FrameworkDependency→bloop.io.AbsolutePathbloop.testing.TestInternals→bloop.io.AbsolutePathbloop.testing.TestNGFrameworkDependency→bloop.io.AbsolutePath
- Direction
- bloop.testing uses bloop.io, so a change to bloop.io can break bloop.testing, while a change to bloop.testing can't break bloop.io.
- Position
- Below the diagonal: bloop.testing uses a module listed above it, which is the healthy direction.
37→27 bloop.testing uses bloop.cli✕
- Connections
- 1 pair of types, where a type in bloop.testing uses a type in bloop.cli.
- The types involved
bloop.testing.TestInternals→bloop.cli.CommonOptions
- Direction
- bloop.testing uses bloop.cli, so a change to bloop.cli can break bloop.testing, while a change to bloop.testing can't break bloop.cli.
- Position
- Below the diagonal: bloop.testing uses a module listed above it, which is the healthy direction.
37→34 bloop.testing uses bloop.exec✕
- Connections
- 1 pair of types, where a type in bloop.testing uses a type in bloop.exec.
- The types involved
bloop.testing.TestInternals→bloop.exec.JvmProcessForker
- Direction
- bloop.testing uses bloop.exec, so a change to bloop.exec can break bloop.testing, while a change to bloop.testing can't break bloop.exec.
- Position
- Below the diagonal: bloop.testing uses a module listed above it, which is the healthy direction.
38→3 sbt.internal.inc.bloop uses bloop.task✕
- Connections
- 1 pair of types, where a type in sbt.internal.inc.bloop uses a type in bloop.task.
- The types involved
sbt.internal.inc.bloop.BloopZincCompiler→bloop.task.Task
- Direction
- sbt.internal.inc.bloop uses bloop.task, so a change to bloop.task can break sbt.internal.inc.bloop, while a change to sbt.internal.inc.bloop can't break bloop.task.
- Position
- Below the diagonal: sbt.internal.inc.bloop uses a module listed above it, which is the healthy direction.
38→7 sbt.internal.inc.bloop uses bloop.reporter✕
- Connections
- 1 pair of types, where a type in sbt.internal.inc.bloop uses a type in bloop.reporter.
- The types involved
sbt.internal.inc.bloop.BloopZincCompiler→bloop.reporter.ZincReporter
- Direction
- sbt.internal.inc.bloop uses bloop.reporter, so a change to bloop.reporter can break sbt.internal.inc.bloop, while a change to sbt.internal.inc.bloop can't break bloop.reporter.
- Position
- Below the diagonal: sbt.internal.inc.bloop uses a module listed above it, which is the healthy direction.
38→9 sbt.internal.inc.bloop uses bloop.tracing✕
- Connections
- 1 pair of types, where a type in sbt.internal.inc.bloop uses a type in bloop.tracing.
- The types involved
sbt.internal.inc.bloop.BloopZincCompiler→bloop.tracing.BraveTracer
- Direction
- sbt.internal.inc.bloop uses bloop.tracing, so a change to bloop.tracing can break sbt.internal.inc.bloop, while a change to sbt.internal.inc.bloop can't break bloop.tracing.
- Position
- Below the diagonal: sbt.internal.inc.bloop uses a module listed above it, which is the healthy direction.
38→11 sbt.internal.inc.bloop uses bloop.logging✕
- Connections
- 1 pair of types, where a type in sbt.internal.inc.bloop uses a type in bloop.logging.
- The types involved
sbt.internal.inc.bloop.BloopZincCompiler→bloop.logging.ObservedLogger
- Direction
- sbt.internal.inc.bloop uses bloop.logging, so a change to bloop.logging can break sbt.internal.inc.bloop, while a change to sbt.internal.inc.bloop can't break bloop.logging.
- Position
- Below the diagonal: sbt.internal.inc.bloop uses a module listed above it, which is the healthy direction.
38→29 sbt.internal.inc.bloop uses bloop✕
- Connections
- 1 pair of types, where a type in sbt.internal.inc.bloop uses a type in bloop.
- The types involved
sbt.internal.inc.bloop.BloopZincCompiler→bloop.UniqueCompileInputs
- Direction
- sbt.internal.inc.bloop uses bloop, so a change to bloop can break sbt.internal.inc.bloop, while a change to sbt.internal.inc.bloop can't break bloop.
- Position
- Below the diagonal: sbt.internal.inc.bloop uses a module listed above it, which is the healthy direction.
39→3 sbt.internal.inc.bloop.internal uses bloop.task✕
- Connections
- 3 pairs of types, where a type in sbt.internal.inc.bloop.internal uses a type in bloop.task.
- The types involved
sbt.internal.inc.bloop.internal.BloopHighLevelCompiler→bloop.task.Tasksbt.internal.inc.bloop.internal.BloopIncremental→bloop.task.Tasksbt.internal.inc.bloop.internal.BloopNameHashing→bloop.task.Task
- Direction
- sbt.internal.inc.bloop.internal uses bloop.task, so a change to bloop.task can break sbt.internal.inc.bloop.internal, while a change to sbt.internal.inc.bloop.internal can't break bloop.task.
- Position
- Below the diagonal: sbt.internal.inc.bloop.internal uses a module listed above it, which is the healthy direction.
39→9 sbt.internal.inc.bloop.internal uses bloop.tracing✕
- Connections
- 1 pair of types, where a type in sbt.internal.inc.bloop.internal uses a type in bloop.tracing.
- The types involved
sbt.internal.inc.bloop.internal.BloopIncremental→bloop.tracing.BraveTracer
- Direction
- sbt.internal.inc.bloop.internal uses bloop.tracing, so a change to bloop.tracing can break sbt.internal.inc.bloop.internal, while a change to sbt.internal.inc.bloop.internal can't break bloop.tracing.
- Position
- Below the diagonal: sbt.internal.inc.bloop.internal uses a module listed above it, which is the healthy direction.
39→11 sbt.internal.inc.bloop.internal uses bloop.logging✕
- Connections
- 1 pair of types, where a type in sbt.internal.inc.bloop.internal uses a type in bloop.logging.
- The types involved
sbt.internal.inc.bloop.internal.BloopLookup→bloop.logging.DebugFilter
- Direction
- sbt.internal.inc.bloop.internal uses bloop.logging, so a change to bloop.logging can break sbt.internal.inc.bloop.internal, while a change to sbt.internal.inc.bloop.internal can't break bloop.logging.
- Position
- Below the diagonal: sbt.internal.inc.bloop.internal uses a module listed above it, which is the healthy direction.
39→29 sbt.internal.inc.bloop.internal uses bloop✕
- Connections
- 1 pair of types, where a type in sbt.internal.inc.bloop.internal uses a type in bloop.
- The types involved
sbt.internal.inc.bloop.internal.BloopIncremental→bloop.UniqueCompileInputs
- Direction
- sbt.internal.inc.bloop.internal uses bloop, so a change to bloop can break sbt.internal.inc.bloop.internal, while a change to sbt.internal.inc.bloop.internal can't break bloop.
- Position
- Below the diagonal: sbt.internal.inc.bloop.internal uses a module listed above it, which is the healthy direction.
40→3 bloop.engine.tasks uses bloop.task✕
- Connections
- 4 pairs of types, where a type in bloop.engine.tasks uses a type in bloop.task.
- The types involved
bloop.engine.tasks.CompileTask→bloop.task.Taskbloop.engine.tasks.LinkTask→bloop.task.Taskbloop.engine.tasks.Tasks→bloop.task.Taskbloop.engine.tasks.TestTask→bloop.task.Task
- Direction
- bloop.engine.tasks uses bloop.task, so a change to bloop.task can break bloop.engine.tasks, while a change to bloop.engine.tasks can't break bloop.task.
- Position
- Below the diagonal: bloop.engine.tasks uses a module listed above it, which is the healthy direction.
40→7 bloop.engine.tasks uses bloop.reporter✕
- Connections
- 1 pair of types, where a type in bloop.engine.tasks uses a type in bloop.reporter.
- The types involved
bloop.engine.tasks.CompileTask→bloop.reporter.ReporterInputs
- Direction
- bloop.engine.tasks uses bloop.reporter, so a change to bloop.reporter can break bloop.engine.tasks, while a change to bloop.engine.tasks can't break bloop.reporter.
- Position
- Below the diagonal: bloop.engine.tasks uses a module listed above it, which is the healthy direction.
40→9 bloop.engine.tasks uses bloop.tracing✕
- Connections
- 1 pair of types, where a type in bloop.engine.tasks uses a type in bloop.tracing.
- The types involved
bloop.engine.tasks.CompileTask→bloop.tracing.BraveTracer
- Direction
- bloop.engine.tasks uses bloop.tracing, so a change to bloop.tracing can break bloop.engine.tasks, while a change to bloop.engine.tasks can't break bloop.tracing.
- Position
- Below the diagonal: bloop.engine.tasks uses a module listed above it, which is the healthy direction.
40→11 bloop.engine.tasks uses bloop.logging✕
- Connections
- 4 pairs of types, where a type in bloop.engine.tasks uses a type in bloop.logging.
- The types involved
bloop.engine.tasks.CompileTask→bloop.logging.DebugFilterbloop.engine.tasks.CompileTask→bloop.logging.Loggerbloop.engine.tasks.TestTask→bloop.logging.DebugFilterbloop.engine.tasks.TestTask→bloop.logging.Logger
- Direction
- bloop.engine.tasks uses bloop.logging, so a change to bloop.logging can break bloop.engine.tasks, while a change to bloop.engine.tasks can't break bloop.logging.
- Position
- Below the diagonal: bloop.engine.tasks uses a module listed above it, which is the healthy direction.
40→13 bloop.engine.tasks uses bloop.data✕
- Connections
- 5 pairs of types, where a type in bloop.engine.tasks uses a type in bloop.data.
- The types involved
bloop.engine.tasks.CompileTask→bloop.data.Projectbloop.engine.tasks.LinkTask→bloop.data.Projectbloop.engine.tasks.Tasks→bloop.data.JdkConfigbloop.engine.tasks.Tasks→bloop.data.Projectbloop.engine.tasks.TestTask→bloop.data.Project
- Direction
- bloop.engine.tasks uses bloop.data, so a change to bloop.data can break bloop.engine.tasks, while a change to bloop.engine.tasks can't break bloop.data.
- Position
- Below the diagonal: bloop.engine.tasks uses a module listed above it, which is the healthy direction.
40→15 bloop.engine.tasks uses bloop.io✕
- Connections
- 4 pairs of types, where a type in bloop.engine.tasks uses a type in bloop.io.
- The types involved
bloop.engine.tasks.CompileTask→bloop.io.AbsolutePathbloop.engine.tasks.LinkTask→bloop.io.AbsolutePathbloop.engine.tasks.Tasks→bloop.io.AbsolutePathbloop.engine.tasks.TestTask→bloop.io.AbsolutePath
- Direction
- bloop.engine.tasks uses bloop.io, so a change to bloop.io can break bloop.engine.tasks, while a change to bloop.engine.tasks can't break bloop.io.
- Position
- Below the diagonal: bloop.engine.tasks uses a module listed above it, which is the healthy direction.
40→17 bloop.engine.tasks uses bloop.cli.Commands✕
- Connections
- 1 pair of types, where a type in bloop.engine.tasks uses a type in bloop.cli.Commands.
- The types involved
bloop.engine.tasks.LinkTask→bloop.cli.Commands.LinkingCommand
- Direction
- bloop.engine.tasks uses bloop.cli.Commands, so a change to bloop.cli.Commands can break bloop.engine.tasks, while a change to bloop.engine.tasks can't break bloop.cli.Commands.
- Position
- Below the diagonal: bloop.engine.tasks uses a module listed above it, which is the healthy direction.
40→19 bloop.engine.tasks uses bloop.engine.tasks.compilation✕
- Connections
- 2 pairs of types, where a type in bloop.engine.tasks uses a type in bloop.engine.tasks.compilation.
- The types involved
bloop.engine.tasks.CompileTask→bloop.engine.tasks.compilation.CompileClientStorebloop.engine.tasks.CompileTask→bloop.engine.tasks.compilation.FinalCompileResult
- Direction
- bloop.engine.tasks uses bloop.engine.tasks.compilation, so a change to bloop.engine.tasks.compilation can break bloop.engine.tasks, while a change to bloop.engine.tasks can't break bloop.engine.tasks.compilation.
- Position
- Below the diagonal: bloop.engine.tasks uses a module listed above it, which is the healthy direction.
40→24 bloop.engine.tasks uses bloop.engine.caches✕
- Connections
- 2 pairs of types, where a type in bloop.engine.tasks uses a type in bloop.engine.caches.
- The types involved
bloop.engine.tasks.CompileTask→bloop.engine.caches.LastSuccessfulResultbloop.engine.tasks.Tasks→bloop.engine.caches.LastSuccessfulResult
- Direction
- bloop.engine.tasks uses bloop.engine.caches, so a change to bloop.engine.caches can break bloop.engine.tasks, while a change to bloop.engine.tasks can't break bloop.engine.caches.
- Position
- Below the diagonal: bloop.engine.tasks uses a module listed above it, which is the healthy direction.
40→25 bloop.engine.tasks uses bloop.engine✕
- Connections
- 5 pairs of types, where a type in bloop.engine.tasks uses a type in bloop.engine.
- The types involved
bloop.engine.tasks.CompileTask→bloop.engine.Dagbloop.engine.tasks.CompileTask→bloop.engine.Statebloop.engine.tasks.LinkTask→bloop.engine.Statebloop.engine.tasks.Tasks→bloop.engine.Statebloop.engine.tasks.TestTask→bloop.engine.State
- Direction
- bloop.engine.tasks uses bloop.engine, so a change to bloop.engine can break bloop.engine.tasks, while a change to bloop.engine.tasks can't break bloop.engine.
- Position
- Below the diagonal: bloop.engine.tasks uses a module listed above it, which is the healthy direction.
40→27 bloop.engine.tasks uses bloop.cli✕
- Connections
- 1 pair of types, where a type in bloop.engine.tasks uses a type in bloop.cli.
- The types involved
bloop.engine.tasks.LinkTask→bloop.cli.OptimizerConfig
- Direction
- bloop.engine.tasks uses bloop.cli, so a change to bloop.cli can break bloop.engine.tasks, while a change to bloop.engine.tasks can't break bloop.cli.
- Position
- Below the diagonal: bloop.engine.tasks uses a module listed above it, which is the healthy direction.
40→29 bloop.engine.tasks uses bloop✕
- Connections
- 1 pair of types, where a type in bloop.engine.tasks uses a type in bloop.
- The types involved
bloop.engine.tasks.CompileTask→bloop.CompileProducts
- Direction
- bloop.engine.tasks uses bloop, so a change to bloop can break bloop.engine.tasks, while a change to bloop.engine.tasks can't break bloop.
- Position
- Below the diagonal: bloop.engine.tasks uses a module listed above it, which is the healthy direction.
40→37 bloop.engine.tasks uses bloop.testing✕
- Connections
- 3 pairs of types, where a type in bloop.engine.tasks uses a type in bloop.testing.
- The types involved
bloop.engine.tasks.Tasks→bloop.testing.BloopTestSuiteEventHandlerbloop.engine.tasks.TestTask→bloop.testing.DiscoveredTestFrameworksbloop.engine.tasks.TestTask→bloop.testing.LoggingEventHandler
- Direction
- bloop.engine.tasks uses bloop.testing, so a change to bloop.testing can break bloop.engine.tasks, while a change to bloop.engine.tasks can't break bloop.testing.
- Position
- Below the diagonal: bloop.engine.tasks 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 | 40 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 7 | High / Critical |
Roadmap
Top priorities: 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; Swallowed exception (caught, then discarded); Resolve the 1 Banned license finding(s) in License Compliance.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| 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. | +5.3 pts | Medium | Nullable reference types |
| Swallowed exception (caught, then discarded) | +3.8 pts | Medium | Exception handling |
| Resolve the 1 Banned license finding(s) in License Compliance. | +1.6 pts | Low | License Compliance |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. | +1.6 pts | Low | ADR Quality |
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +1.6 pts | Low | Documentation Quality |
| Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +0.8 pts | Low | Supply-chain Provenance & Signing |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +1.4 pts | Medium | Deployment & Rollback |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +1.4 pts | Medium | Release Hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| frontend/src/main/scala/bloop/engine/Interpreter.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| bloop-rifle/src/main/scala/bloop/rifle/internal/Operations.scala | 6.0 | Mixed | Explicit Debt: FixmeComment |
| frontend/src/main/scala/bloop/data/Project.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| frontend/src/main/scala/bloop/bsp/BloopBspServices.scala | 6.0 | Mixed | Explicit Debt: FixmeComment |
| cli/src/main/scala/bloop/cli/util/CustomProgressBarRefreshDisplay.scala | 6.0 | Mixed | Explicit Debt: FixmeComment |
| buildpress/src/main/scala/buildpress/Buildpress.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| frontend/src/main/scala/bloop/dap/BloopDebuggee.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| backend/src/main/scala/bloop/ScalaInstance.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| cli/src/main/scala/bloop/cli/options/DefaultOptions.scala | 6.7 | Mixed | Explicit Debt: FixmeComment |
| bridges/scalajs-0.6/src/main/scala/bloop/scalajs/JsBridge.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| backend/src/main/scala/sbt/internal/inc/bloop/internal/BloopAnalysisCallback.scala | 7.0 | Mixed | Code Duplication: Edited copy of a member (61 corresponding lines) |
| integrations/sbt-bloop/src/main/scala/bloop/integrations/sbt/SbtBloop.scala | 7.0 | Mixed | Cyclomatic Complexity: BloopDefaults.bloopGenerate (cyclomatic 29) |
| frontend/src/main/scala/bloop/engine/tasks/compilation/CompileGraph.scala | 7.1 | Mixed | Cyclomatic Complexity: CompileGraph.setupAndDeduplicate (cyclomatic 38) |
| bridges/scala-native-0.4/src/main/scala/bloop/scalanative/NativeBridge.scala | 7.1 | Mixed | Cyclomatic Complexity: NativeBridge.nativeLink (cyclomatic 20) |
| backend/src/main/scala/bloop/Compiler.scala | 7.2 | Mixed | Cyclomatic Complexity: Compiler.compile (cyclomatic 28) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
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
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 57 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 57 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, 241 of 271 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 or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
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 |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.scala) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) and this repository declares an sbt build (repository root, 168 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its sbt dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `docs-gen/src/main/scala/bloop/docs/ReleasesModifier.scala` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D34 Knowledge Freshness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. File-level freshness contradicts repo activity: 178 commits in the last 90 days, yet 77 of 126 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- 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.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's Scala imports SLF4J but logs through a logger the reading cannot trace to it — a `log` handed down by a trait or passed in as a parameter — so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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
28 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ParallelOps.copyDirectoriesWith at 44. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Interpreter.execute at 20 — they are counted neither in the figure above nor in this dimension's score.
What to do
- Bring the 3 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with ParallelOps.copyDirectoriesWith (cyclomatic 44), CompileGraph.setupAndDeduplicate (cyclomatic 38), Interpreter.autocomplete (cyclomatic 31). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 6.9 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D2 · Cognitive Complexity
51 method(s) exceeded the cognitive complexity threshold of 15; the worst was Interpreter.autocomplete at 71.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with Interpreter.autocomplete (cognitive 71), ParallelOps.copyDirectoriesWith (cognitive 70). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 5.9 to about 6.1/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D3 · God Classes
10 god class(es) detected.
What to do
- Resolve the 4 FileTooLong finding(s) in God Classes — start with BloopBspServices.scala, SbtBloop.scala, Compiler.scala. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 MethodTooLong finding(s) in God Classes — start with CompileTask.scala, ParallelOps.scala, CompileGraph.scala. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with BloopBspServices.scala, SbtBloop.scala. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
21 duplicated block group(s) detected. 3.2 % of the production lines (1,104 of 34,485) are in a reported copy. A further 18 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 2 of the 39 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 3 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with BloopAnalysisCallback.scala (2), NativeBridge.scala. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Edited copy of a member (18 corresponding lines) finding(s) in Code Duplication — start with Traverse.scala, Nailgun.scala. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (4 corresponding lines) finding(s) in Code Duplication — start with BloopAnalysisCallback.scala (2). — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
14 production modules (sbt), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 3 module(s) off the main sequence, with abstractness counted on 8 of the 14 (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 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
1 of 40 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with BloopBspServices.scala. — One of this dimension's main actionable groups (1 warning-level).
D12 · Dependency Hygiene
13 outdated direct sbt declarations. 47 of 63 direct declarations were graded against Maven Central (16 not published there, which is what a private Nexus or Artifactory artifact looks like, 0 declaring a version range rather than an exact version). An sbt declaration names an EXACT version, so the remedy is an edit to the build file — there is no lockfile refresh that would move it. Test-, Provided- and it-scoped declarations are excluded, because a consumer of this project never receives them. A version held in a Scala val is read only when the val is one string literal: sbt is a program rather than a manifest, and evaluating a computed version would invent the measurement rather than take it. Whether any artifact is DEPRECATED or ABANDONED is not graded and cannot be — Maven Central publishes no such marker, and release age does not stand in for one: the most widely depended-upon libraries are routinely the stalest, being finished rather than abandoned. Known CVEs in this dependency graph are D30's question.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
1 of 43 declared sbt dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the production coordinates this repository's 9 sbt build file(s) (REDACTED and project/*.scala) declare with a literal version, directly or through a string-literal val — `%%` resolved to the Scala binary suffix Central publishes under, test-scoped declarations excluded — the same declaration-site closure this analysis reads for dependency currency. sbt has no lockfile a checkout carries, so this is deliberately NOT the transitive closure. A further 20 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's sbt dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
D15 · Churn × Complexity Hotspots
Top hotspots: integrations/sbt-bloop/src/main/scala/bloop/integrations/sbt/SbtBloop.scala (4×29=116); backend/src/main/scala/bloop/Compiler.scala (4×28=112); frontend/src/main/scala/bloop/engine/caches/ResultsCache.scala (3×19=57)
What to do
- Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with SbtBloop.scala, Compiler.scala, ResultsCache.scala. — One of this dimension's main actionable groups (3 warning-level).
D16 · Bus Factor
24 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is frontend/src/main/scala/bloop/cli/Commands.scala. Counted over 126 of the 264 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 4 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (4 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
28 deducted task-comment markers across 34485 LoC (0.1/KLoC) → score 9.8. 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 17 TodoComment finding(s) in Explicit Debt — start with GithubRelease.scala (2), Buildpress.scala (2), DeduplicationSpec.scala. — One of this dimension's main actionable groups (17 warning-level).
- Resolve the 11 FixmeComment finding(s) in Explicit Debt — start with BloopServer.scala (2), Artifacts.scala (2), Operations.scala (2). — One of this dimension's main actionable groups (11 warning-level).
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 35 document(s) read across 2 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 3 build units (npm, sbt) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
40 finding(s): 0 critical, 35 high, 4 medium, 1 low. 29 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `integrations/sbt-bloop/src/sbt-test/sbt-bloop/exclude-filter/narrowed/src/main/scala/Legacy.java` (line 1) — 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.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 29 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 (29 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/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. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
AX8 · Test isolation
GD1 · Unfinished & placeholder code
- `unapply` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — frontend/src/main/scala/bloop/util/ExtraPlatform.scala:6
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
- `unapply` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — frontend/src/main/scala/bloop/util/ExtraPlatform.scala:6
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×4) — frontend/src/test/scala/bloop/BaseCompileSpec.scala:1932, frontend/src/test/scala/bloop/FileWatchingSpec.scala:561, frontend/src/test/scala/bloop/io/ClasspathHasherSpec.scala:19, …
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)
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
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
P3 · Security & performance tooling
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `npm`, `gitsubmodule`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — REDACTED:2
What to do
- Dependabot is configured but does not watch `npm`, `gitsubmodule` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF1 · Benchmark discipline
- A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — benchmarks/src/main/scala/sbt/HotSbtBenchmark.scala
What to do
- Run JMH with the GC profiler (`-prof gc`, or addProfiler(GCProfiler.class)) so allocation rate regressions are visible, not just time.
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. (×2) — backend/src/main/scala/bloop/util/BestEffortUtils.scala:30, backend/src/main/scala/bloop/util/BestEffortUtils.scala:64
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 2 sites, not one: `backend/src/main/scala/bloop/util/BestEffortUtils.scala:30` (MessageDigest.getInstance("SHA-1")), `backend/src/main/scala/bloop/util/BestEffortUtils.scala:64` (MessageDigest.getInstance("SHA-1")). 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
- The JDK pipes both `stdout` and `stderr` of a child started this way — no `redirectErrorStream`, `redirectError`, `redirectOutput` or `inheritIO` is set — and here `process.getInputStream` (stdout) is read while the child's end is awaited, but nothing in this scope ever reads `process.getErrorStream` (stderr). The JDK's own `Process` documentation warns that failing to read a child's output promptly "may cause the process to block, or even deadlock": once the child writes more than the pipe holds to stderr (measured on OpenJDK 25 / Linux: 60,000 bytes finishes, 70,000 hangs forever), it blocks on the write, never exits, and the `waitFor` or end of stream this code waits on never comes. Nothing fails loudly: the thread hangs and the stuck child holds its resources until something kills it. Read both streams (a thread or `Future` per stream), merge them with `redirectErrorStream(true)` before `start()`, discard the unwanted one with `redirectError(ProcessBuilder.Redirect.DISCARD)` (or `redirectOutput`), or use `scala.sys.process`, which pumps both. — backend/src/main/scala/bloop/DependencyResolution.scala:220
What to do
- Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
- `Files.list(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.collect` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(Files.list(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`. — shared/src/main/scala/bloop/io/AbsolutePath.scala:27
- `Files.walk(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.iterator` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(Files.walk(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`. (×3) — bridges/scalajs-0.6/src/main/scala/bloop/scalajs/JsBridge.scala:54, backend/src/main/scala/bloop/util/BestEffortUtils.scala:49, backend/src/main/scala/bloop/util/BestEffortUtils.scala:68
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X19 · Unrestored process-global state
X21 · Side-effecting pattern 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
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×4) — frontend/src/main/scala/bloop/testing/LoggingEventHandler.scala:168, frontend/src/main/scala/bloop/engine/caches/SemanticDBCache.scala:96, backend/src/main/scala/bloop/DependencyResolution.scala:232, …
- `case scala.util.control.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. (×2) — frontend/src/main/scala/bloop/engine/ExecutionContext.scala:21, frontend/src/main/scala/bloop/engine/ExecutionContext.scala:33
- 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. (×10) — frontend/src/main/scala/bloop/bsp/BspServer.scala:158, frontend/src/main/scala/bloop/bsp/BspServer.scala:188, frontend/src/main/scala/bloop/bsp/BspServer.scala:218, …
- `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. — backend/src/main/scala/sbt/internal/inc/BloopComponentCompiler.scala:56
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- No build over this repository's 250 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 | 60% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 92% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 75% | Strong | Solid. |
| Readiness | 67% | Adequate | Acceptable, with room to improve. |
| Security | 70% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 94% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X10 Duplicated predicate — 2 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 — 58 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.
- 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 function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. 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 (`npm run start`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. 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 — ~23493 lines of test source are present (.scala) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .scala suite was found but not re-run
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 2 candidate(s) found and not reported.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .java, .scala source were not judged.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 206 value object(s); 5 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 35 current-state document(s) make no claim of a kind M4 checks. 21 claim(s) of kinds M4 does not check were not checked (path 8, command argument 3, install 1, environment variable 9); M4 checks only links and versions and artefact counts.
- 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 — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Scala and Java were read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter; a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 37 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
- Banned license: org.graalvm.nativeimage:svm
- REDACTED
- REDACTED
Serious — 197 finding(s)
- TodoComment project/GithubRelease.scala:42
- TodoComment project/GithubRelease.scala:118
- TodoComment frontend/src/test/scala/bloop/DeduplicationSpec.scala:756
- TodoComment frontend/src/main/scala/bloop/reporter/LogReporter.scala:68
- TodoComment frontend/src/main/scala/bloop/logging/BspServerLogger.scala:299
- TodoComment frontend/src/main/scala/bloop/engine/Interpreter.scala:869
- TodoComment frontend/src/main/scala/bloop/data/Project.scala:478
- TodoComment frontend/src/main/scala/bloop/dap/BloopDebuggee.scala:75
- TodoComment cli/src/main/scala/bloop/cli/Logger.scala:7
- TodoComment buildpress/src/main/scala/buildpress/Buildpress.scala:475
- TodoComment buildpress/src/main/scala/buildpress/Buildpress.scala:484
- TodoComment buildpress/src/main/scala/buildpress/io/SbtProjectHasher.scala:139
- TodoComment bridges/scalajs-0.6/src/main/scala/bloop/scalajs/JsBridge.scala:91
- TodoComment backend/src/main/scala/sbt/internal/inc/bloop/internal/BloopIncremental.scala:77
- TodoComment backend/src/main/scala/bloop/ScalaInstance.scala:98
- TodoComment backend/src/main/scala/bloop/logging/ObservedLogger.scala:43
- TodoComment backend/src/main/java/bloop/scalasig/CustomAttribute.java:14
- FixmeComment frontend/src/main/scala/bloop/BloopServer.scala:231
- FixmeComment frontend/src/main/scala/bloop/bsp/BloopBspServices.scala:799
- FixmeComment cli/src/main/scala/bloop/cli/Default.scala:65
- FixmeComment cli/src/main/scala/bloop/cli/util/Artifacts.scala:122
- FixmeComment cli/src/main/scala/bloop/cli/util/Artifacts.scala:142
- FixmeComment cli/src/main/scala/bloop/cli/util/CustomProgressBarRefreshDisplay.scala:190
- FixmeComment cli/src/main/scala/bloop/cli/util/OsLibc.scala:58
- FixmeComment cli/src/main/scala/bloop/cli/options/DefaultOptions.scala:112
- FixmeComment bloop-rifle/src/main/scala/bloop/rifle/BloopServer.scala:190
- FixmeComment bloop-rifle/src/main/scala/bloop/rifle/internal/Operations.scala:44
- FixmeComment bloop-rifle/src/main/scala/bloop/rifle/internal/Operations.scala:238
- Swallowed exception (empty catch) frontend/src/main/scala/bloop/bsp/BspServer.scala:158
- Swallowed exception (empty catch) frontend/src/main/scala/bloop/bsp/BspServer.scala:188
- Swallowed exception (empty catch) frontend/src/main/scala/bloop/bsp/BspServer.scala:218
- Swallowed exception (empty catch) frontend/src/main/scala/bloop/bsp/BspServer.scala:221
- Swallowed exception (empty catch) frontend/src/main/scala/bloop/bsp/BspServer.scala:225
- Swallowed exception (empty catch) cli/src/main/scala/bloop/cli/Default.scala:155
- Swallowed exception (empty catch) backend/src/main/scala/sbt/internal/inc/ResourceLoader.scala:30
- Swallowed exception (empty catch) backend/src/main/scala/bloop/tracing/BraveTracer.scala:161
- Swallowed exception (empty catch) backend/src/main/scala/bloop/tracing/BraveTracer.scala:192
- Swallowed exception (empty catch) backend/src/main/scala/bloop/io/ClasspathHasher.scala:145
- Swallowed exception (caught, then discarded) frontend/src/main/scala/bloop/testing/LoggingEventHandler.scala:168
- Swallowed exception (caught, then discarded) frontend/src/main/scala/bloop/engine/ExecutionContext.scala:21
- Swallowed exception (caught, then discarded) frontend/src/main/scala/bloop/engine/ExecutionContext.scala:33
- Swallowed exception (caught, then discarded) frontend/src/main/scala/bloop/engine/caches/SemanticDBCache.scala:96
- Swallowed exception (caught, then discarded) backend/src/main/scala/sbt/internal/inc/BloopComponentCompiler.scala:56
- Swallowed exception (caught, then discarded) backend/src/main/scala/bloop/DependencyResolution.scala:232
- Swallowed exception (caught, then discarded) backend/src/main/scala/bloop/ScalaInstance.scala:145
- FileTooLong: bsp/BloopBspServices.scala frontend/src/main/scala/bloop/bsp/BloopBspServices.scala
- FileTooLong: sbt/SbtBloop.scala integrations/sbt-bloop/src/main/scala/bloop/integrations/sbt/SbtBloop.scala
- FileTooLong: bloop/Compiler.scala backend/src/main/scala/bloop/Compiler.scala
- FileTooLong: engine/Interpreter.scala frontend/src/main/scala/bloop/engine/Interpreter.scala
- Disposable created and abandoned in the function that made it shared/src/main/scala/bloop/io/AbsolutePath.scala:27
- Disposable created and abandoned in the function that made it bridges/scalajs-0.6/src/main/scala/bloop/scalajs/JsBridge.scala:54
- Disposable created and abandoned in the function that made it backend/src/main/scala/bloop/util/BestEffortUtils.scala:49
- Disposable created and abandoned in the function that made it backend/src/main/scala/bloop/util/BestEffortUtils.scala:68
- Hotspot: integrations/sbt-bloop/src/main/scala/bloop/integrations/sbt/SbtBloop.scala integrations/sbt-bloop/src/main/scala/bloop/integrations/sbt/SbtBloop.scala:1015
- Hotspot: backend/src/main/scala/bloop/Compiler.scala backend/src/main/scala/bloop/Compiler.scala:279
- Hotspot: frontend/src/main/scala/bloop/engine/caches/ResultsCache.scala frontend/src/main/scala/bloop/engine/caches/ResultsCache.scala:170
- MethodTooLong: CompileTask.compile frontend/src/main/scala/bloop/engine/tasks/CompileTask.scala:56
- MethodTooLong: ParallelOps.copyDirectoriesWith backend/src/main/scala/bloop/io/ParallelOps.scala:146
- MethodTooLong: CompileGraph.setupAndDeduplicate frontend/src/main/scala/bloop/engine/tasks/compilation/CompileGraph.scala:90
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (13 lines × 2) backend/src/main/scala/sbt/internal/inc/bloop/internal/BloopAnalysisCallback.scala:367
- Duplicated block (13 lines × 2) bridges/scala-native-0.4/src/main/scala/bloop/scalanative/NativeBridge.scala:87
- Duplicated block (13 lines × 2) backend/src/main/scala/sbt/internal/inc/bloop/internal/BloopAnalysisCallback.scala:169
- NativeBridge.nativeLink (cyclomatic 20) bridges/scala-native-0.4/src/main/scala/bloop/scalanative/NativeBridge.scala:29
- NativeBridge.nativeLink (cyclomatic 20) bridges/scala-native-0.5/src/main/scala/bloop/scalanative/NativeBridge.scala:30
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TooManyMethods: BloopBspServices frontend/src/main/scala/bloop/bsp/BloopBspServices.scala:93
- TooManyMethods: BloopDefaults integrations/sbt-bloop/src/main/scala/bloop/integrations/sbt/SbtBloop.scala:150
- Edited copy of a member (18 corresponding lines) buildpress/src/main/scala/buildpress/util/Traverse.scala:7
- Edited copy of a member (18 corresponding lines) bloop-rifle/src/main/scala/bloop/rifle/internal/nailgun/Nailgun.scala:97
- Edited copy of a member (4 corresponding lines) backend/src/main/scala/sbt/internal/inc/bloop/internal/BloopAnalysisCallback.scala:62
- Edited copy of a member (4 corresponding lines) backend/src/main/scala/sbt/internal/inc/bloop/internal/BloopAnalysisCallback.scala:361
- Edited copy of a member (6 corresponding lines) bridges/scalajs-0.6/src/main/scala/bloop/scalajs/JsBridge.scala:37
- Edited copy of a member (6 corresponding lines) frontend/src/main/scala/bloop/engine/tasks/toolchains/ScalaJsToolchain.scala:136
- Duplicated block (9 lines × 2) backend/src/main/scala/sbt/internal/inc/bloop/internal/BloopAnalysisCallback.scala:382
- Duplicated block (9 lines × 2) integrations/sbt-bloop/src/main/scala-2.12/bloop/integrations/sbt/CompatPlatform.scala:38
- Duplicated block (6 lines × 2) frontend/src/main/scala/bloop/bsp/BloopBspServices.scala:1064
- Duplicated block (6 lines × 2) frontend/src/main/scala/bloop/engine/tasks/LinkTask.scala:34
- Duplicated block (5 lines × 2) frontend/src/main/scala/bloop/dap/BloopDebuggee.scala:202
- Duplicated block (5 lines × 2) docs-gen/src/main/scala/bloop/docs/ReleasesModifier.scala:21
- Off the main sequence: buildpressConfig
- Off the main sequence: bloopRifle
- Weak hash algorithm backend/src/main/scala/bloop/util/BestEffortUtils.scala:30
- Weak hash algorithm backend/src/main/scala/bloop/util/BestEffortUtils.scala:64
- ParallelOps.copyDirectoriesWith (cyclomatic 44) backend/src/main/scala/bloop/io/ParallelOps.scala:146
- CompileGraph.setupAndDeduplicate (cyclomatic 38) frontend/src/main/scala/bloop/engine/tasks/compilation/CompileGraph.scala:90
- Interpreter.autocomplete (cyclomatic 31) frontend/src/main/scala/bloop/engine/Interpreter.scala:664
- BloopDefaults.bloopGenerate (cyclomatic 29) integrations/sbt-bloop/src/main/scala/bloop/integrations/sbt/SbtBloop.scala:1015
- Compiler.compile (cyclomatic 28) backend/src/main/scala/bloop/Compiler.scala:279
- Operations.startServer (cyclomatic 28) bloop-rifle/src/main/scala/bloop/rifle/internal/Operations.scala:152
- Cli.parse (cyclomatic 27) frontend/src/main/scala/bloop/Cli.scala:202
- Project.enableMetalsSettings (cyclomatic 27) frontend/src/main/scala/bloop/data/Project.scala:431
- BloopBspServices.run (cyclomatic 24) frontend/src/main/scala/bloop/bsp/BloopBspServices.scala:1007
- Build.checkForChange (cyclomatic 24) frontend/src/main/scala/bloop/engine/Build.scala:52
- CompileTask.compile (cyclomatic 24) frontend/src/main/scala/bloop/engine/tasks/CompileTask.scala:56
- BloopBspServices.compileProjects (cyclomatic 23) frontend/src/main/scala/bloop/bsp/BloopBspServices.scala:518
- BloopBspServices.startDebugSession (cyclomatic 22) frontend/src/main/scala/bloop/bsp/BloopBspServices.scala:733
- BloopHighLevelCompiler.compile (cyclomatic 21) backend/src/main/scala/sbt/internal/inc/bloop/internal/BloopHighLevelCompiler.scala:65
- Interpreter.console (cyclomatic 21) frontend/src/main/scala/bloop/engine/Interpreter.scala:349
- CompileGraph.traverse (cyclomatic 20) frontend/src/main/scala/bloop/engine/tasks/compilation/CompileGraph.scala:375
- ClasspathHasher.hash (cyclomatic 19) backend/src/main/scala/bloop/io/ClasspathHasher.scala:66
- Project.javaVersionAtLeast (cyclomatic 19) frontend/src/main/scala/bloop/data/Project.scala:189
- ResultsCache.loadAsync (cyclomatic 19) frontend/src/main/scala/bloop/engine/caches/ResultsCache.scala:170
- CustomProgressBarRefreshDisplay.display (cyclomatic 17) cli/src/main/scala/bloop/cli/util/CustomProgressBarRefreshDisplay.scala:153
- Validate.bsp (cyclomatic 17) frontend/src/main/scala/bloop/cli/Validate.scala:24
- Buildpress.run (cyclomatic 16) buildpress/src/main/scala/buildpress/Buildpress.scala:42
- BloopBspServices.linkProjects (cyclomatic 16) frontend/src/main/scala/bloop/bsp/BloopBspServices.scala:431
- BloopBspServices.test (cyclomatic 16) frontend/src/main/scala/bloop/bsp/BloopBspServices.scala:839
- BspServer.run (cyclomatic 16) frontend/src/main/scala/bloop/bsp/BspServer.scala:47
- BloopExtraBuildParams.equals (cyclomatic 16) bloop-rifle/src/main/scala/bloop/rifle/bloop4j/BloopExtraBuildParams.java:68
- Interpreter.autocomplete (cognitive 71) frontend/src/main/scala/bloop/engine/Interpreter.scala:664
- ParallelOps.copyDirectoriesWith (cognitive 70) backend/src/main/scala/bloop/io/ParallelOps.scala:146
- BloopDefaults.bloopGenerate (cognitive 48) integrations/sbt-bloop/src/main/scala/bloop/integrations/sbt/SbtBloop.scala:1015
- Compiler.compile (cognitive 47) backend/src/main/scala/bloop/Compiler.scala:279
- Interpreter.console (cognitive 47) frontend/src/main/scala/bloop/engine/Interpreter.scala:349
- Build.checkForChange (cognitive 43) frontend/src/main/scala/bloop/engine/Build.scala:52
- Project.enableMetalsSettings (cognitive 42) frontend/src/main/scala/bloop/data/Project.scala:431
- CompileTask.compile (cognitive 40) frontend/src/main/scala/bloop/engine/tasks/CompileTask.scala:56
- CompileGraph.setupAndDeduplicate (cognitive 40) frontend/src/main/scala/bloop/engine/tasks/compilation/CompileGraph.scala:90
- CompileGraph.traverse (cognitive 39) frontend/src/main/scala/bloop/engine/tasks/compilation/CompileGraph.scala:375
- ClasspathHasher.hash (cognitive 38) backend/src/main/scala/bloop/io/ClasspathHasher.scala:66
- ResultsCache.loadAsync (cognitive 38) frontend/src/main/scala/bloop/engine/caches/ResultsCache.scala:170
- Operations.startServer (cognitive 37) bloop-rifle/src/main/scala/bloop/rifle/internal/Operations.scala:152
- BloopHighLevelCompiler.compile (cognitive 33) backend/src/main/scala/sbt/internal/inc/bloop/internal/BloopHighLevelCompiler.scala:65
- BloopWhileBusyDropEventsAndSignalOperator.apply (cognitive 33) frontend/src/main/scala/bloop/util/monix/WhileBusyDropEventsAndSignalOperator.scala:18
- BloopBspServices.run (cognitive 31) frontend/src/main/scala/bloop/bsp/BloopBspServices.scala:1007
- BloopClasspathEntryLookup.definesClass (cognitive 29) backend/src/main/scala/bloop/BloopClasspathEntryLookup.scala:32
- Buildpress.cloneGitUri (cognitive 29) buildpress/src/main/scala/buildpress/Buildpress.scala:246
- CustomProgressBarRefreshDisplay.update (cognitive 29) cli/src/main/scala/bloop/cli/util/CustomProgressBarRefreshDisplay.scala:55
- BloopBspServices.compileProjects (cognitive 29) frontend/src/main/scala/bloop/bsp/BloopBspServices.scala:518
- Roots.resolve (cognitive 28) backend/src/main/scala/bloop/PortableAnalysis.scala:169
- CustomProgressBarRefreshDisplay.display (cognitive 28) cli/src/main/scala/bloop/cli/util/CustomProgressBarRefreshDisplay.scala:153
- Project.javaVersionAtLeast (cognitive 28) frontend/src/main/scala/bloop/data/Project.scala:189
- ScalaInstance.scalaInstanceForJavaProjects (cognitive 27) backend/src/main/scala/bloop/ScalaInstance.scala:262
- BspServer.run (cognitive 23) frontend/src/main/scala/bloop/bsp/BspServer.scala:47
- BloopDefaults.findOutPlatform (cognitive 23) integrations/sbt-bloop/src/main/scala/bloop/integrations/sbt/SbtBloop.scala:859
- CompilerPluginAllowlist.enableCachingInScalacOptions (cognitive 22) frontend/src/main/scala/bloop/engine/tasks/compilation/CompilerPluginAllowlist.scala:76
- Buildpress.press (cognitive 21) buildpress/src/main/scala/buildpress/Buildpress.scala:72
- BloopBspServices.linkProjects (cognitive 21) frontend/src/main/scala/bloop/bsp/BloopBspServices.scala:431
- BloopBspServices.startDebugSession (cognitive 20) frontend/src/main/scala/bloop/bsp/BloopBspServices.scala:733
- BspProjectReporter.reportRemainingProblems (cognitive 20) frontend/src/main/scala/bloop/reporter/BspProjectReporter.scala:228
- Operations.bsp (cognitive 19) bloop-rifle/src/main/scala/bloop/rifle/internal/Operations.scala:366
- BloopBspServices.test (cognitive 19) frontend/src/main/scala/bloop/bsp/BloopBspServices.scala:839
- SourceHasher.findAndHashSourcesInProject (cognitive 19) frontend/src/main/scala/bloop/io/SourceHasher.scala:56
- BspProjectReporter.processEndCompilation (cognitive 19) frontend/src/main/scala/bloop/reporter/BspProjectReporter.scala:312
- CommandsDocGenerator.main (cognitive 19) frontend/src/main/scala/bloop/util/CommandsDocGenerator.scala:58
- BloopExtraBuildParams.equals (cognitive 19) bloop-rifle/src/main/scala/bloop/rifle/bloop4j/BloopExtraBuildParams.java:68
- Compiler.adjustScalacReleaseOptions (cognitive 18) backend/src/main/scala/bloop/Compiler.scala:918
- DefaultReporterFormat.formatSource (cognitive 18) backend/src/main/scala/bloop/reporter/DefaultReporterFormat.scala:29
- Task.parSequence (cognitive 18) backend/src/main/scala/bloop/task/Task.scala:389
- Task.parSequenceUnordered (cognitive 18) backend/src/main/scala/bloop/task/Task.scala:440
- Buildpress.parseUris (cognitive 18) buildpress/src/main/scala/buildpress/Buildpress.scala:398
- Dag.inverseDependencies (cognitive 18) frontend/src/main/scala/bloop/engine/Dag.scala:213
- Interpreter.test (cognitive 18) frontend/src/main/scala/bloop/engine/Interpreter.scala:556
- Interpreter.run (cognitive 18) frontend/src/main/scala/bloop/engine/Interpreter.scala:833
- SourceWatcher.watch (cognitive 18) frontend/src/main/scala/bloop/io/SourceWatcher.scala:44
- DependencyResolution.findInPath (cognitive 17) backend/src/main/scala/bloop/DependencyResolution.scala:174
- BloopDefaults.projectDependencyName (cognitive 17) integrations/sbt-bloop/src/main/scala/bloop/integrations/sbt/SbtBloop.scala:664
- DefaultOptions.bloopRifleConfig (cognitive 16) cli/src/main/scala/bloop/cli/options/DefaultOptions.scala:53
- Cli.parse (cognitive 16) frontend/src/main/scala/bloop/Cli.scala:202
- TestServer.listenToTests (cognitive 16) frontend/src/main/scala/bloop/testing/TestServer.scala:55
- ClassTooLong: Buildpress buildpress/src/main/scala/buildpress/Buildpress.scala:30
- REDACTED
- Members sharing a duplicated core (6 members, 50+ identical tokens) frontend/src/main/scala/bloop/bsp/BloopBspServices.scala:1359
- Edited copy of a member (75 corresponding lines) bridges/scala-native-0.4/src/main/scala/bloop/scalanative/NativeBridge.scala:36
- Edited copy of a member (61 corresponding lines) backend/src/main/scala/sbt/internal/inc/bloop/internal/BloopAnalysisCallback.scala:408
- Edited copy of a member (45 corresponding lines) backend/src/main/scala/bloop/task/Task.scala:389
- Edited copy of a member (26 corresponding lines) frontend/src/main/scala/bloop/engine/tasks/LinkTask.scala:28
- Edited copy of a member (30 corresponding lines) frontend/src/main/scala/bloop/dap/BloopDebuggee.scala:196
- Edited copy of a member (13 corresponding lines) integrations/sbt-bloop/src/main/scala-2.12/bloop/integrations/sbt/CompatPlatform.scala:36
- Edited copy of a member (19 corresponding lines) backend/src/main/scala/sbt/internal/inc/bloop/internal/BloopAnalysisCallback.scala:143
- Edited copy of a member (10 corresponding lines) frontend/src/main/scala/bloop/testing/JUnit5FrameworkDependency.scala:78
- Edited copy of a member (11 corresponding lines) backend/src/main/scala/sbt/internal/inc/bloop/internal/BloopAnalysisCallback.scala:116
- Edited copy of a member (5 corresponding lines) frontend/src/main/scala/bloop/data/Project.scala:101
- Duplicated block (44 lines × 2) bridges/scala-native-0.4/src/main/scala/bloop/scalanative/NativeBridge.scala:37
- Duplicated block (25 lines × 2) bridges/scala-native-0.4/src/main/scala/bloop/scalanative/NativeBridge.scala:116
- Duplicated block (19 lines × 2) buildpress/src/main/scala/buildpress/io/BuildpressPaths.scala:21
- Duplicated block (22 lines × 2) backend/src/main/scala/sbt/internal/inc/bloop/internal/BloopAnalysisCallback.scala:309
- Duplicated block (15–16 lines × 2) integrations/sbt-bloop/src/main/scala/bloop/integrations/sbt/SbtBloop.scala:356
- Duplicated block (15 lines × 2) backend/src/main/scala/sbt/internal/inc/bloop/internal/BloopAnalysisCallback.scala:219
- Duplicated block (14 lines × 2) backend/src/main/scala/sbt/internal/inc/bloop/internal/BloopAnalysisCallback.scala:393
- Duplicated block (10 lines × 6) frontend/src/main/scala/bloop/bsp/BloopBspServices.scala:1372
- Duplicated block (9–10 lines × 2) cli/src/main/scala/bloop/cli/Exit.scala:28
- Duplicated block (7–8 lines × 2) frontend/src/main/scala/bloop/bsp/BloopBspServices.scala:463
- Duplicated block (7 lines × 2) buildpress/src/main/scala/buildpress/util/Traverse.scala:8
- Duplicated block (8 lines × 2) backend/src/main/scala/sbt/internal/inc/bloop/internal/BloopAnalysisCallback.scala:276
- Edited copy of a member (22 corresponding lines) docs-gen/src/main/scala/bloop/docs/ReleasesModifier.scala:10
- Low cohesion: BloopBspServices (LCOM4 4) frontend/src/main/scala/bloop/bsp/BloopBspServices.scala:93
- Unfinished stub — body is `???` frontend/src/main/scala/bloop/util/ExtraPlatform.scala:6
- Unfinished stub — body is ??? / NotImplementedError frontend/src/main/scala/bloop/util/ExtraPlatform.scala:6
- JavaScript dependencies are not locked package.json:2
- Redirected process stream is never drained (deadlock) backend/src/main/scala/bloop/DependencyResolution.scala:220
Minor — 23 finding(s)
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Off-boarding risk: anonymized user #3
- Off-boarding risk: anonymized user #4
- Disabled test frontend/src/test/scala/bloop/BaseCompileSpec.scala:1932
- Disabled test frontend/src/test/scala/bloop/FileWatchingSpec.scala:561
- Disabled test frontend/src/test/scala/bloop/io/ClasspathHasherSpec.scala:19
- Disabled test frontend/src/test/scala/bloop/io/ClasspathHasherSpec.scala:58
- Duplicated predicate integrations/sbt-bloop/src/main/scala/bloop/integrations/sbt/SbtBloop.scala:1456
- Duplicated predicate backend/src/main/scala/sbt/internal/inc/bloop/internal/BloopAnalysisCallback.scala:311
- Further sole-owners (lower concentration)
- Documentation: no build, run or usage example README.md:1
- No ADRs found REDACTED:141
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Dependabot does not watch npm/gitsubmodule REDACTED:2
- No release approval gate
- No changelog
- Benchmarks don't track allocations benchmarks/src/main/scala/sbt/HotSbtBenchmark.scala
- Scala's null is not held to the type system everywhere
Minor — 14 finding(s)
- Outdated: com.github.alexarchambault:case-app_3
- Outdated: com.github.plokhotnyuk.jsoniter-scala:jsoniter-scala-core_3
- Outdated: com.github.plokhotnyuk.jsoniter-scala:jsoniter-scala-macros_3
- Outdated: com.github.scopt:scopt_2.12
- Outdated: io.get-coursier:interface-svm-subs
- Outdated: io.get-coursier.util:directories-jni
- Outdated: io.monix:monix_3
- Outdated: io.zipkin.brave:brave
- Outdated: io.zipkin.reporter2:zipkin-sender-urlconnection
- Outdated: org.eclipse.jgit:org.eclipse.jgit
- Outdated: org.eclipse.jgit:org.eclipse.jgit.ssh.jsch
- Outdated: org.scala-sbt:librarymanagement-ivy_3
- Outdated: org.scala-sbt:zinc_3
- Off the main sequence: bloopShared
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-14b8dd40547c4fadaf75ee72cab6897b/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/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-14b8dd40547c4fadaf75ee72cab6897b/tree.json --exit-code 0 --source . | 1 | 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/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 40 | 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/** . | 1 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `docs-gen/src/main/scala/bloop/docs/ReleasesModifier.scala` — so the PII/GDPR sweep did not cover them at all. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |